I have a Wi-Fi Motorola Xoom that I am connecting via ADB for development. I am seeing an intermittent problem where the device (with ID number) shows up in the adb devices list, but will present as being offline.
The device and computer both show the tablet as being connected. I've tried a combination of rebooting each device and swapping USB ports, but the only thing that solves the issue is switching out the cable. Furthermore, a cable that I used yesterday doesn't work today -- I am having to use a previously non-functioning cable to connect.
Is this a driver issue? Device port issue? I have seen this issue with several versions of the Motorola drivers as well as the PdaNet drivers. I am currently using Motorola Mobile Drivers 4.7.1.
WARNING: this question referred to an older device and as such the answers may no longer be relevant to current ADB connection issues.
I met the same problems like yours, and I found out that the USB cable has mal-functions in the PIN of head USB. So I switch to the new USB cable, it just works fine and detect device as online.
I had the same problem, and switching from the USB port on the front of my machine to the port on the back made things work. It could be related to a difference in port power or USB type.
From XDA: nouvelle_adr http://forum.xda-developers.com/showthread.php?t=2247471
I downloaded the adb version and it worked.
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window"
Related
I'm stuck in "authorizing" status on ADB. I can't bring the "USB debug authorization view" back. On the other hand my phone does says "USB debugging connected. Tap to turn off USB debugging".
❯ adb devices
List of devices attached
xxxxxxxx authorizing
This used to work properly (for 2-3 years), I haven't changed my setup (same host, same physical device, same USB port, same cable). I updated OSX a few days ago so this may be related to this issue.
❯ adb --version
Android Debug Bridge version 1.0.41
Version 31.0.3-7562133
❯ sw_vers
ProductName: macOS
ProductVersion: 11.6.1
BuildVersion: 20G224
The mobile device is a ONEPLUS A6013, running on android 11.
I've tried several things:
unplug/replug the USB cable (changing cable/port)
restart both my machine and mobile
quit/join again the developper mode on my mobile
revoking USB authorizations on my mobile
removing private/public ADB keys on my laptop (I also tried completely recreating ~/.android)
uninstalling/reinstalling all android build/platform tools (in android studio)
updating one plus' Oxygen OS
None of these allowed me to show the prompt asking for the USB debug authorization on my phone.
EDIT
We've also tried connecting another phone to my laptop (it didn't work either). We tried connecting my phone to another laptop and it worked as expected (I also was able to check "always allow", then I successfully revoked this authorization). So it's definitively a problem on my laptop side.
I found something weird too, I have two ADB installed, one in ${ANDROID_HOME}/platform-tools/adb and another in /usr/local/bin/adb. I tried repeating all above tests using explicitly ${ANDROID_HOME}/platform-tools/adb, yielding the same results.
One thing that worked for me was to change the USB hub I was connecting to on my MacBook M1. I had daisy chained two hubs and the device was connected to the second one.
So if your issue is with a USB hub, you can troubleshoot here as well.
Thank you for bringing this loop. The problem appears with hubs that are not officially made or approved by apple. With an official(very expensive) hub it's working as expected. I hope this helps. (mine is a satechi usb-c hub)
Am having a problem in connecting my huawei Y7 2018 phone with android studio,each time i try connecting it via the usb option it still doesnt appear on my android studio even after allowing the usb debugging option on and the weird part of it, it connects to other phones.Kindly help to solve this problem.
check for ADB drivers are properly installed n are compatible with your device. Connect your phone to pc n open terminal n-type adb devices check whether your device shows up or not, if not you have to install your device compatible drivers(optional try universal ADB drivers or google ADB drivers).
Android Studio is not recognizing any external emulators (phones) connected to it.
I have tried the following mentioned things without any success:
Installed the device driver. (It is working fine. The device recognizes my
phone.)
Turned on USB Debugging.
Kill-server and then start-server commands.
I am using Android Studio for Windows.
Probably you haven't installed the driver for your phone (if you use Windows). For instance, if you use Nexus or Pixel phones, you should install this. If you use Samsung phones, try this link.
It worked for me. If you still cannot see any of the devices, try calling 'Invalidate Caches / Restart' in the File menu in the Android Studio and restarting the system.
Hope it helps!
I had the same problem, my problem was I was using a cable that cam with the phone that acsually would not transfer any data from\to the phone, the moment I changed the cable it worked like magic.
Just try changing a cable 1st, the PC has to recognize the device even if You have no drivers, if Your phone doesnt ask You to give permission to access from PC than the cable is just a charging cable!
Hope it helps.
Set up a device for development (android documentation) :
On the device, open the Settings app, select Developer options, and
then enable USB debugging.
Set up your system to detect your device.
For Windows: Install a USB driver for Android Debug Bridge (adb). For an installation guide and links to OEM drivers, see the
Install OEM USB Drivers document.
When you connect a device running Android 4.2.2 (API level 17) or
higher to your computer, the system shows a dialog asking whether to
accept an RSA key that allows debugging through this computer. This
security mechanism protects user devices because it ensures that USB
debugging and other adb commands cannot be executed unless you're able
to unlock the device and acknowledge the dialog.
Hello stackoverflow mighty community,
Please help !
I have a Datalogic DL-AXIST (http://www.datalogic.com/eng/products/automatic-data-capture/mobile-computers/dl-axist-pd-702.html) which is an android device but i guess the company fiddled a bit with its core. Also I have a windows 7 toshiba pc.
Anyway my concern is that it is not showing on the adb devices chooser.
Here is what i've tried so far:
I'm using Eclipse IDE, my SDK is up to date and i can test my application on all the other devices i tried so far.
The datalogic device has Android 4.1.1, driver is correctly installed on my pc i'm sure, enabled developer options.
I tried connecting it as MTP and PTP but will not work, there is also a CD-ROM installer connection which i tried as well, followed through the installation on my pc but still does not work.
It gets even stranger, when i used the third pc connection type and installed the device with its own adb on pc, i even copied those adb files in that folder and pasted them my eclipse's own adb. This worked ! my device was recognized but it changed for a reason i do not know.
I tried uninstalling the device driver and re-installing it from windows device manager, tried rebooting device and restarting eclipse and pc.
I really need some help because making this device work will greatly benefit my work.
Thanks !
This is genuine issue which may come frequently,but the soln is simple you may try these steps:
step 1;
try swictching developer options on and off
if the above dont works then go to device manager in your pc check portables devices select device and update driver software-->browse my comp-->let me pick list of device drivers-->select android as in option or MTP
if your device dont show in portable devices just update the device which comes in portable devices list trust me it works all time
try to do this once
1. Check if authorized:
\platform-tools>adb devices List of devices attached 4df798d76f98cf6d unauthorized
2. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" (tested with JellyBean & Samsung GalaxyIII).
Restart ADB Server:
Then restarted adb server
adb kill-server adb start-server
4. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
Now Check the device
It is now authorized!
adb devices \platform-tools>adb devices List of devices attached 4df798d76f98cf6d device
I recently purchased the MK802; Android 4.0 Mini PC. However, I am unable to install the apps I developed. I have tried using the 'adb devices' command but the device does not appear on the list. I have also downloaded the Andorid 4.0 SDK (the version used in th MK802) on my computer but still no luck. I also made sure to enable 'USB Debugging' and 'Unknown Sources' in the device settings.
I realize I can load my app from an SD card (but I would have to buy one); or that I can download my app onto the device by making it available on a server or the android marketplace but these options seem like too much effort just to install an app.
Any suggestions or recommendations would be greatly appreciated.
Simply adb over USB doesn't work (for now)
The only thing that you can do is: USE WIRELESS ADB!
This widget can help you on enabling it.
Once you got everything up and running do an
adb connect xxx.xxx.xxx.xxx
using as IP the ip address of the MK802. Once connected run an
adb shell
as usual to access the remote shell. Still the system is in heavy development (at least allwinner told so)
EDIT: Using a shorter USB cable could solve the issue!
I managed to connect mine to ADB, even using the included USB cable.
Connect you computer to the dongle's OTG port (it's marked on the dongle).
Go into settings and enabled ADB debugging.
And finally (here's the trick) enable the special Connect to PC setting.
Google for the drivers. Installing the Android SDK will not ensure that your device gets detected.
Connect device
Install drivers downloaded from internet
Disconnect & reconnect
ADB !
In all likelihood, this will solve things for you.