This is driving me nuts. I have a Verizon S3 running stock JB (4.1.something), and I'm using the latest version of the ADT bundle. Connected to my main machine I was not able to get the device to work with the debugger. Running "adb devices" showed the device id and "offline."
So I connected it to my laptop, which is on the same subnet. On that machine if I restart the phone the device shows up as "online." At that point I can do "adb tcpip 5555" on the laptop, and then on the dev machine "adb connect xxx.xxx.xxx.xxx" and get a connection. Thereafter "adb devices" on the dev machine will show the device id and ip. Works great.
Except the damn thing still randomly drops offline. I'll try to debug and Eclipse will complain that there is no valid target. Exec "adb devices" on the dev machine shows empty list. On the laptop shows device id as "offline" again. Nothing in logcat other than "Device disconnected."
I've Googled the crap out of this. Normally I discount "solutions" that recommend trying another usb cable, but I saw enough of those replies that I had to give them some credence. Tried four cables that all work fine with other devices. No change in behavior. Just went through a frustrating cycle of four device restarts trying to get it to go online and stay online long enough to debug.
I can probably do the bit I'm working on now using an emulator, but eventually I'm gonna have to get this sorted out. If anyone has any ideas would love to hear them.
[Update] - turns out this was indeed caused by usb issues. I dug out a usb extension cable and plugged the phone into a high speed port on the back of my system instead of the powered hub it had been plugged into, and it is now stable. Don't know why it's so sensitive but the common wisdom turned out to be accurate.
So I connected it to my laptop, which is on the same subnet. On that machine if I restart the phone the device shows up as "online." At that point I can do "adb tcpip 5555" on the laptop, and then on the dev machine "adb connect xxx.xxx.xxx.xxx" and get a connection. Thereafter "adb devices" on the dev machine will show the device id and ip. Works great.
Except the damn thing still randomly drops offline. I'll try to debug and Eclipse will complain that there is no valid target. Exec "adb devices" on the dev machine shows empty list. On the laptop shows device id as "offline" again. Nothing in logcat other than "Device disconnected."
I've Googled the crap out of this. Normally I discount "solutions" that recommend trying another usb cable, but I saw enough of those replies that I had to give them some credence. Tried four cables that all work fine with other devices. No change in behavior. Just went through a frustrating cycle of four device restarts trying to get it to go online and stay online long enough to debug.
I can probably do the bit I'm working on now using an emulator, but eventually I'm gonna have to get this sorted out. If anyone has any ideas would love to hear them.
[Update] - turns out this was indeed caused by usb issues. I dug out a usb extension cable and plugged the phone into a high speed port on the back of my system instead of the powered hub it had been plugged into, and it is now stable. Don't know why it's so sensitive but the common wisdom turned out to be accurate.
Last edited:
Facebook
Twitter