A while ago, I was able to connect my device and have it be detected on Android Studio. But now that's no longer the case. I've tried it with two separate phones and ADB is unable to detect either of them. After doing some research, I've tried a couple of things:
*Enabled USB debugging
*ADB kill-server/start-server
*Switching phone from MTP to PTP
*Switching USB ports/cables.
Is there anything else that might be useful to try that I haven't tried?
Thanks!
-T
Connect your device and select Connect to PC Software option. MTP and PTP won't work.
Edit:
If you are using a Samsung Galaxy device you might have to use a powered USB hub as suggested in this post
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'm trying to test an Android application and have a device connected via USB. The device detects (and charges off) the USB connection but I can't seem to find any record on the computer (running Windows 7) that the device is connected. I looked in Device Manager and did not see an "Android Devices" category, nor did I see an "Other Devices" category. I looked on the device manufacturer's website to see if they had drivers; I could not find any. Does anyone have any idea as to how I could get the device to show on the computer? Thanks!
Most probably windows and especially android adb will see your android device after installing the Google USB Driver
I had the same problem for many of my android devices and most of them are running fine with the driver from google. Only for some sony devices I had to install special drivers.
In Android Studio go to Tools -> Android -> Android Device Monitor. Once it opens close it, this will reset your adb and you should be able to see your device
Your problem sounds related with drivers
the Google USB Driver works only for some android models, some other drivers are installed as plug and play but some others you have to install manually.
http://developer.android.com/intl/es/tools/extras/oem-usb.html
Also sometimes it happened to me that the adb didn't recognize the device while the screen was locked so you could also check that out.
It turned out that the USB cable I was using was a charge-only cable. After switching the cable out, the device showed on ADB.
I went through this link to connect my tablet with my LINUX machine for USB debugging. It was not working for me. I can able to connect other devices such as CANVAS HD and SAMSUNG smart phones.When trying to connect the AZPEN tablet, No devices are found.
Any suggestion?
I had similar problems with my Azpen A1048 running Lollipop versus Android Studio on Windows 7. I enabled USB debugging on the Azpen, but adb on Windows could not see it. Also, though I could mount it via USB and transfer files, the Azpen never showed up in Windows' Devices and Printers screen.
The tablet did appear under Windows' Device Manager as A1048, but reinstalling Windows' driver for it gave no success with adb. Meanwhile another device called HP 7 G2 seemed to come and go with the Azpen. I initially dismissed it as a phantom but finally used it to make adb work with the Azpen! Here's how:
Install USB Driver Tool *;
Run UsbDriverTool.exe as administrator;
Right click on the HP 7 G2 device;
Select Install Android ADB Driver from the popup menu;
Restart adb from a command prompt using adb kill-server then adb devices -l.
Here is the resulting output from adb:
List of devices attached
033818f698d500000000 device product:astar_h7 model:A1048 device:astar-h7
Also the tablet now appears in Windows' Devices and Printers and Eject screens as "MTP".
I'm guessing the identifier disparities are a slip on Azpen's part, but at least I can deploy to the Azpen directly from Android Studio now.
*I'm not certain USB Driver Tool was a requirement; it's just how I happened to fix this problem.
I had requested to the manufacturer of AZPEN tablet regarding this issue, they told that, there is no such facility available in Azpen tablet. Sorry for the late answer.
I have two Android phones
Alcatel One Touch 4030D, Android version 4.1.1, kernel version 3.4.0
Highscreen Spark, Android version 4.0.4, kernel version 3.0.21-perf.
adb devices detects the Alcatel phone, but not the Highscreen phone.
I tried to run adb kill-server; adb start-server, but it didn't help. Switching between different connection modes (Media device (MTP), USB storage) didn't help either. USB debugging is enabled.
Here are the screenshots of the Developer options settings:
How can I make adb recognize the Highscreen device?
Update 1 (03.08.2013 19:00 MSK): Adding the line 0454 to adb_usb.ini didn't help.
Update 2 (03.08.2013 19:59 MSK): My attempt to follow the official Google recommendations failed because I couldn't find the drivers for the Highscreen Spark device.
If you could setup an ADT on Linux or Mac, it will work out of the box.
We were able to connect all sorts of devices to adb easily with ADT on Linux/Mac.
If you haven't managed to connect it through usb, you can try the network connection.
Add your device to the same network, then type in the command prompt:
adb connect your_device_ip_address
Hey try to dig for drivers at Official website.
May be search other sites for USB drivers, that may help you to come out of your problem.
I had the same problem .Try it again by activating the usb mass storage.
Without adb driver for device (in your case Highscreen Spark) it is almost impossible to create a bridge(connection) between your program and device, as adb (Android Debug bridge) makes a connection between your PC/laptop to your android device And without Adb in windows Pc/Laptops its not easily possible to debug.
Because of this, Companies like samsung, lg, htc are providing adb drivers to users for easy debugging, if you dont have a adb driver for Your Device you have only one choice left , Change your operating System into linux and then see the magic.
I had this same problem. Turns out, the issue was the USB Port I plugged in to. The port directly on my laptop does not allow for ADB to see the device. The port on the back of my docking station does allow ADB to see the device. I believe it has to do with USB 3.0 vs. 2.0. I believe 3.0 blocks the protocol ADB needs to use.
You will actually require the device drivers to connect it, so try insatalling Highscreen Spark's PC Suite.
If that dosen't work or you don't find the PC Suite you can download Moborobo from here which is a universal PC Suite for smart phones and connect the device with it and then try connecting the device from abd
It may be a problem with your adb.exe. I had the same problem earlier for connecting HCL G1 tablet. I also added lines in android_winusb.ini, but could not connect yet. Then I found out this link. I got solution by changing the adb.exe file. Try this link : http://www.slatedroid.com/topic/37692-adb-drivers-problem/ Or just download the adb.exe from following link and replace it with you adb.exe file. http://sdrv.ms/NepKED It is also suggested run this command to make adb_usb.ini effective for respective adb after modifying. echo 0x2207 >> %USERPROFILE%.android\adb_usb.ini
Try these drivers
x86
x64
It works for me.
After head banging for more than a day - a small thing saved my life on my RK3066 based device:
after you update the adb_usb.ini and everything else,
and after you do a
adb kill-server
do a
adb usb
and only then do a
adb devices
saved my life
By the way
Adding the line 0454 to adb_usb.ini didn't help.
you should be adding 0x454
I was having issues with my android phone showing up when I typed adb devices but found out that it was the usb cable which caused the issue, members in my family have two different android phones each with their own charging cable. I was using one phone with the other phones usb cable just because it was the nearest and I didn't think it would make a difference but it did.
Try a different usb cable and that might help.
I have the same issue in the past but i don't found the driver on my computer today, so :
You can go on http://www.alcatelonetouch.com and find the call center for your land.
Call them , and explain the issue , they have to send you a driver to connect your phone to the computer. This drivers is very easy to install.
I have make that and i can use it for debbuging
I whish you good luck... Sorry for my English
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"