this whole thing is a nightmare, at least in windows. I had my phone connected and everything was ok. I have a Samsung Galaxy, I've installed the USB driver and it was okay, I could run apps from eclipse directly on my phone. Now nothing is differentm but when I type adb devices it recognizes my phone but its offline. USB debug option is checked, and I have the right drivers installed. Any idea? thanks!
相关问题
- How can I create this custom Bottom Navigation on
- Bottom Navigation View gets Shrink Down
- How to make that the snackbar action button be sho
- Listening to outgoing sms not working android
- How to create Circular view on android wear?
相关文章
- android开发 怎么把图片放入drawable的文件夹下
- android上如何获取/storage/emulated/下的文件列表
- androidStudio有个箭头不认识
- SQLite不能创建表
- Windows - Android SDK manager not listing any plat
- Animate Recycler View grid when number of columns
- Why is the app closing suddenly without showing an
- Android OverlayItem.setMarker(): Change the marker
Have you also tried to change the USB socket in which you plugged the USB cable?
Sometimes one thinks about unplugging/replugging, but not about changing the USB socket in which to plug the cable. All the more since it is correctly recognized by Windows.
I had the same symptoms (Windows recognizing my Samsung Galaxy, but not ADB), and changing the place where I plugged the USB cable did worked for me.
Make sure your phone's SD card isn't mounted as a drive on your Windows machine. Whenever that happens to me, I can't connect via adb.
I ve seen multiple times this problem and there is no common answer. i'll make a list of solutions that I have seen across severals forums:
Restart ADB server with the following commands:
adb kill-server
and thenadb start-server
Change the USB cable you are using: I've seen a lot of complaints about Samsung's USB cable.
Change the USB socket you are using
Try to reinstall the drivers (for instance, for Samsung devices, installing Kies; this solved the problem for me)
Try to reboot your phone
Unset the
debug mode
on the device and set it againAdb seems to often cause troubles, not the best piece of software I've seen!
Have you tried restarting the adb server?
Run: