Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
When I try to eject my Android phone from my Windows 8 laptop (using the "Safely Remove Hardware and Eject Media" icon in the task bar) I get a "Problem Ejecting USB Composite Device" pop-up with the message:
Windows can't stop your 'Android ADB Interface' device because a program is still using it. Close any programs that might be using the device, and then try again later.
I have a number of background and Windows processes running, but no apps, so any idea what could be causing this? One of the background processes is "abd (32 bit)", so should I just end that task? Or would it be better to just unplug the device and not worry about ejecting it first?
Android uses ADB to communicate with physical devices and emulators. To properly disconnect your phone first stop the ADB server and then eject your device.
CD C:\Users\<user_name>\AppData\Local\Android\android-sdk\platform-tools
adb kill-server
Then eject your device.
More info here.
As Andrew Halloran stated, device can be safely removed if you first end Android Debug Bridge adb.
That can be done using the Task Manager
Then click "Safely Remove Hardware and Eject Media"
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
suddenly it started giving me no notification any time i plug it into any PC. I've used different USB cables,turned on my USB debugging mode,restored the factory settings, updated the phone software. I don't know what else to do. I really need help here
Browse to your sdk on studio terminal and type adb devices and check if it shows.
If not try adb killall-server and adb start-server otherwise try updating usb driver for your phone
If you have a Samsung Phone, try installing Samsung Kies on your PC. That should include all drivers.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I want to test my application on my Android phone.
But this phone is connected to pc, but doesn't show up in ADT devices list.
Can someone help me with this?
You need to ensure you have the Developer Options enabled on the device (and 'Allow USB Debugging' selected). Also you need (on Windows) to have the device USB driver installed.
Also, sometimes you need to restart ADB after the device has been connected.
From Eclipse, open the DDMS perspective, and in the devices list, click the upside triangle to access the menu to restart ADB (don't worry about the failed to restart errors you will see those always).
Also, you can restart from the command line with the following commands:
adb kill-server
adb start-server
Try to install Sync(pc suite) of the mobile device in the system and even unable the USB debugging in the mobile
Which phone are you using?
If it's a Nexus device, you have to install the Google USB Driver. You can follow this guide to install the driver.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 9 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Improve this question
My device appears attached from ./adb devices but non in AVD Manager. lsusb result is positive and I also tried ./adb kill-server after that ./adb start-server
I've followed the android's official guide but still no positive response. Does it matter if my device is a tablet?
If you are referring to a "real" device attached to your computer, why would it appear in android "virtual" device manager?
AVD manager lists only virtual devices running on an emulator.
If your real device is connected with USB debugging enabled and and it appears in ADB connected devices, you are good to go.
If your using linux then require your android device entry in 51-android.rules files
plz check the
Setting up a Device for Development in below link
http://developer.android.com/tools/device.html
your device add in 51-android.rules file: /etc/udev/rules.d/51-android.rules
after adb kill-server and adb start-server apply that's working
AVD will list only virtual devices
enable usb debugging and use the monitor tool under sdk/tools dir
http://developer.android.com/tools/help/monitor.html
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
after I rooted a Nexus 10 the app I have written which connects to an Arduino in USB Host mode no longer works properly. I'm pretty sure this is because the USB Host mode is no longer available.
I have checked the original unrooted device with Chainfire's 'USB Host Diagnostics' tool and it recognises the plugged in Arduino whilst scanning for connected devices, but nothing is detected after rooting.
Originally the device had Android 4.3 - build JWR66Y, and USB Host mode worked.
I rooted via the Nexus Root Toolkit and installed a rooted image of the same build, now the device isn't detected.
Any ideas what could be causing this?
Thanks
This is not a question of your app not working. I have seen it plenty of times that when someone roots a device the USB host no longer works. Its a problem with the ROM or method that was used to root the device. Best bet is to reset the device and try something else.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have setup Mint in VirtualBox, and use the GUI.
I followed the instructions to install the GuestAdditions (with root privilege), I run VBoxLinuxAdditions.run and everything is working like a charm. My android device is detected right away.
However, as soon as after I restart Linux, I get a message Unable to Mount LGE Android Phone, the phone keeps trying to be connected without success and pops up this message.
Then if I install again the guest additions then it works.
How could I do in order to get the android device working right away after reboot?
Happened to me something similar in ubuntu, in my case I opened it without privileges, what I did was open the virtualbox with root privileges.
Then I realized I had to add my user to the plugdev group: "$ sudo add $ USER plugdev"
I hope that we can help.