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)
Related
I'm running Android Studio Arctic Fox 2020.3.1 Patch 2 on my Dell XPS 13-9370 running Linux Ubuntu Ubuntu 20.04.3 LTS and when I try to connect either of my two Pixel 2s via USB, Studio fails to see them. I have USB debugging enabled and have tried setting Default USB configuration to both File transfer and PTP, to no effect. I also tried swapping USB cables and all the other steps described in the Android Studio Troubleshoot Device Connections.
I should mention that I have no problem connecting Studio to my Samsung Tab A running Android 11, or to any of the emulated devices. They all connect just fine. When I plug the USB cable into the Pixel 2s, I don't even get the permission prompt, even after revoking USB permissions.
I've been knocking my head against a wall on this for a couple of days now, trying out every relevant suggestion I've found on Stack Overflow. I used to have no problem connecting my two Pixel 2 devices up until a few days ago. The problem also occurs on the previous version of Android Studio. I thought it might have something to do with several new third-party apps I installed, but I forced stop them, rebooted the device and still the problem remains.
You can hard reset your devices because in some cases that works.
Otherwise, You can use the developer options wirelessly on your phone.
Just read this article for a step by step guide for how to do this.
Use Android device for development wirelessly
are you using same usb cable for other devices in which it is working ?
try this once - open developer option and select 'Select USB Configuration' . make it mtp and also check if usb debugging is turned on.
Instead of doing it with a cable you could do it wireless just install the plugin adb wifi rest all the instructions are given when you will install that plugin.
Android WiFi ADB
Steps to do this(in short)
Connect your device to your computer using a USB cable.
Then press the button picture of a button to be pressed on the toolbar and disconnect your USB once the plugin connects your device over WiFi.
You can now deploy, run and debug your device using your WiFi connection.
NOTE: Remember that your device and your computer have to be in the same WiFi connection.
Sometimes it happens for the USB connector manager of your operating system. You can uninstall the USB connector manager from your OS Device manager and then restart your laptop. I faced this issue several times and this solution worked for me.
Try to install Genymotion Emulator and Launch it first before running your app. I did it and it helped me and i think it will be work
I am trying to debug an app on android but found out that my chrome://inspect doesn't show any apps or pages anymore for my device despite showing the device itself.
I followed multiple tutorials, search for my problem on the internet but nothing came in useful and as it used to work I don't really know where to start with this issue. I will try to give you as much informations as possible:
I tested my build on emulator and on another phone (ungoogled rom, android 11.0) and everything worked just fine, I could see and debug the app
USB debugging is enabled in my developer options on the phone
my android version is 11.0
my webview version is 92.0.4515.131.
my build is a debug one (not production)
I recently changed my rom (from paranoid quartz 5 to ArrowOs 11.0) but I didn't use the inspector for a while before changing, so I suspect I affects the issue but I don't know how much
I tested it on MacOS Big Sur and ArchLinux, as well as with multiple chrome versions (eloston chromium, chrome, brave)
When trying to inspect other pages from just chrome from my phone, nothing appears either
The app runs with cordova
What am I missing here and is there a solution for my problem other than change rom again ?
Thank you very much for your answers
First, try to restart adb server. It can be done with these commands on unix if adb command is available to you in terminal. If not, then on unix instead of adb, type path (absolute to be sure) to adb executable.
adb kill-server
adb start-server
adb devices
If you can see your device in output of adb devices (only device ID will be visible), then try to disable ipv6 for your network. Adb server might not work properly when ipv6 is enabled on your computer. In my case, disabling ipv6 have fixed that issue and I could see 'Remote target' section (which was not visible when ipv6 was enabled) and my devices once connected.
I'm trying to connect my phone to Android Studio to follow up with some app development. I am currently struggling with connecting my phone to the computer properly, as ADB never seems to connect to the device.
When attempting to boot the app on the device, this is what Android Studio tells me in the run console
com.android.ddmlib.AdbCommandRejectedException: device still connecting
Error while Installing APK
Which leads me to think that this is a problem with ADB. So when I run adb devices I get this log:
List of devices attached
5210a780f48b44c5 connecting
It stays in the "connecting" state no matter how long I wait. I accepted USB debugging and file transfer.
When in Android studio, the device is listed as
I'm out of ideas as to how to fix this. I recently updated my phone (Samsung A5) to Android 8.0. This phone connects and debugs fine on my work computer. I tried updating Android Studio, rebooting my computer, installing Samsung drivers, rebooting my phone, revoking debug access, to no avail. I was able to work on this computer a while back but I don't know what changed.
How can I fix this problem so I can debug on my device?
[EDIT]
adb version shows this
Android Debug Bridge version 1.0.40
Version 4797878
Installed as C:\Users\Frederic\AppData\Local\Android\sdk\platform-tools\adb.exe
A friend told me to try to swap ports to a USB 2.0 instead of USB 3.0. After doing so it worked instantly as expected.
[EDIT]
It appears that this has more to do with the capabilities of the motherboard than the version of USB the port is. The opposite might be true for you, or just any other port.
I had the same problem and found that the issue was solved by switching off USB debugging on the device, then switching it on again.
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 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"