You are right to be skeptical of the answers already give you. Clearly, adb is running. But what is not clear is whether or not adb has already got itself into a confused state.
Although I have not had the exact same problem you report, I have been able to address similar problems by stopping and then restarting the adb server: that is what I do when I know the device is there, but adb devices does not report it. And although I cannot think of why it would make a difference, it seems to work more reliably if I do this as superuser (on my development system, which runs Linux) than if I do it as a regular user. Of course, that is not much help to you if you have to run a monkey over night. But it might at least help you narrow down what the problem is. On Wednesday, July 18, 2012 12:00:45 AM UTC-7, Sreedhar Reddy V wrote: > > Hi > > I connected My android ICS device to my windows PC using USB. > > I executed "adb devices" from my pc. > > The output > --------------------------------------------------------------------------- > List of devices attached > XXXXXXXXid device > --------------------------------------------------------------------------- > > > After a long time of say 12 hours, i ran the same command "adb devices" > from my pc. > > The output > --------------------------------------------------------------------------- > List of devices attached > XXXXXXXXid offline > --------------------------------------------------------------------------- > > I am not sure what went wrong. i did not even touch my pc, and my device. > I made settings in my PC so that it will never sleep. > I am running monkey scripts which wont make android device to lock as well. > > Many people said that ur device is offline because adbd deamon is not > running on android device. > But this is wrong, why because if adbd is not running then the device will > not be listed at all. > > > I came across adbd deamon process which will be running on my android > device. > For my device to get detected by adb(server on my pc) adbd must be > running. > > I went to adb shell > I stopped adbd using the command "stop adbd" > This stopped my adbd deamon on android device.because adbd is stopped mt > adb(server on my pc will not detect my device) > Now adbd is not running, I execute the "adb devices" command the output > is, list of devices with empty list. > The output > --------------------------------------------------------------------------- > List of devices attached > --------------------------------------------------------------------------- > > because the device it self is not detected i cannot log in to adb shell > again to "start adbd" adbd deamon on my device. > so I shutdown and rebooted my android device, this made my adbd deamon to > run again. > > Now when i executed "adb devices" on my PC > The output > --------------------------------------------------------------------------- > List of devices attached > XXXXXXXXid device > --------------------------------------------------------------------------- > > > By seeing this output it is very clear that adbd deamon is running on > device, because if adbd is not running then the device will not be listed > at all. > > Now the question is? > what is the reason for the device to go to offline? (i am very sure that > "adbd deamon not running" is not at all a reason for this.) > How can i switch the device from online -> offline viceversa? > > I am very very thank full to any android expert who solve my confusion. > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
