Device suddenly not seen by ADB

Roger Garstang

Well-Known Member
Licensed User
Longtime User
I have a device I have used from Day 1 on B4A without issue...in fact it usually works best due to my other devices having MTP and Kies junk kicking in and messing up the connection. Suddenly yesterday afternoon it stopped being seen by ADB. I tried Restarting the ADB Server and Restarting USB without it doing anything. The other devices still work fine. Is there any reason for a device to suddenly not work? When I plug it in I can connect to the SD Card and it reports Debugging active when docked. It just doesn't show in the device list.
 

Roger Garstang

Well-Known Member
Licensed User
Longtime User
That was part of what I already did. Right now I dock it and it shows the Notification of USB debugging connected and gives the option to connect to the SD Card in the other USB connected notification. adb devices shows nothing though. If I plug my Note in it shows it in adb devices and I can usually deploy 1-3 times to it before the stupid Kies garbage messes up the connection.

It is really weird that it does everything else with USB still and even claims Debug is connected, but it doesn't show.
 
Upvote 0

Roger Garstang

Well-Known Member
Licensed User
Longtime User
Can't you disable Kies?

That is the same thing I thought. It comes pre-nstalled with the WiFi version that doesn't even connect by USB from what I see, but I see no way of disabling anything (Kies Air is actually in the Disabled Apps too). A few min in I get a big messagebox that says ATTENTION in big letters and something about not finding software to recognize my device and where to go to get it (That it goes to the Kies folder at samsung.com is the only thing in the box even identifying what it is for). I only test with it every day or two to make sure what I have so far still works in ICS, so have put up with it.

Note that you can always use B4A-Bridge instead of USB debugging.

Does it work over USB yet? I tried it early on and it wouldn't work here because we have Wireless disabled for security reasons.
 
Upvote 0

Roger Garstang

Well-Known Member
Licensed User
Longtime User
Ok. I forgot it had Bluetooth...I thought of that after typing above and got the latest version (Appears to be 2.00 although I thought I saw mention of a 2.2) and saw it had bluetooth. I just got a USB Bluetooth Adapter recently and tried it out now. Took a little bit to get it to connect even though it saw it in scanning I had to make a connection myself then connect in B4A. It works fine other than being a little more manual than before in installing the app. I guess I will connect that way now. I wish I could have figured out why it stopped working to begin with.
 
Upvote 0

warwound

Expert
Licensed User
Longtime User
If you go to Control Panel > Device Manager do you see the device with an entry such as drivers not found?

It might just need a driver re-install.

Martin.
 
Upvote 0
Top