Thank u ranjit i tried it, but this does not work, this will only restart the adb server in pc, i strongly feel the problem is with adbd deamon which is running in android device. we cannot restart it as it need root permissions
On Tuesday, 24 July 2012 12:14:24 UTC+5:30, ranjit R wrote: > > hi, > > try this command > > adb kill-server > > adb start-server > > > it disconnects and again tries to establish contact with your device via > ADB > > On Wednesday, July 18, 2012 12:30:45 PM UTC+5:30, 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
