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.
Related
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 am using Android Studio for Windows but it doesn't show any list of devices in the "choose a running device" option. In a Command Tool, adb devices also shows nothing.
Things I have tried:
I have tried this with 2 devices, an Xperia Sola as well as a Lenovo tablet, with the same results.
I have enabled USB Debugging via Developer's Options on each device.
I have tried adb kill-server followed by adb start-server, and adb devices still shows nothing. However, I can see the device in Windows File Explorer.
I checked that the driver is up-to-date.
Can anyone help solve this problem?
I had the same problem. So here is what i did
reinstalled the device driver
changed the USB computer connection from MTP to Mass storage(UMS)
And it worked.
check out this thread Android Studio doesn't recognize my device
Following on from ADB not recognising Nexus 4 under Windows 7 I am having problems getting the Eclipse android development environment to recognise my new Nexus 4. My privious Nexus S had no problems.
I believe I have followed all the advice in this previous post but am still stuck.
Can anybody who has succeeded getting the nexus 4 available for android development on windows 7, tell me what their driver detail are for the "Android Composite ABD Interface"? Mine say:
* Driver Provider: "Google Inc"
* Driver Date: 27/08/12
* Driver Version: 7.0.0.1
When my phone storage is set to either PTP or MTP, I still can't see it through the eclipse "android virtual device manager".
When set to PTP, if I run the "adb devices" command described in the linked article, I do get an entry appearing in the dos box, but nothing in the "android virtual device manager" in eclipse.
The solution is to connect your device with PTP instead of MTP and, it works.
Connected devices are not visible in AVD manager. AVD manager is for emulators.
To show connected devices, you use only ADB with this command :
adb devices
This is great step by step tutor for it:
http://androidsecurity.wordpress.com/2013/06/05/install-google-nexus-4-adb-usb-drivers-on-windows-android-studio/
Uninstall the device driver completely from Windows and re-install it.
If you dont see the device in the Devices lists:
First, you need to make sure USB debugging is enabled on your device. Settings->DeveloperOptions: Turn on debugging and enable USB debugging. Ideally, you will install the USB drivers from google, and it will work fine: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver. There are some cases that new installation may mess up the device connection. You may want to try these:
It may lost the connection, so you can try:
adb kill-server
adb start-server
adb devices
Updating to new tools may mess up the settings:
Go to Storage Options and try to set as Media(MTP) or Camera(PTP) connection. Swtiching to one of them will help
Revoke authorizations, disable usb debugging and then enable
Your Nexus 4 isn't a virtual device, so won't show in Virtual Devices Manager.
If you open the Devices view, then you should see your Nexus 4 listed, and when you run your app it should prompt for running it on as physical or virtual device.
I'm trying to test an Android Application on my Galaxy Nexus (from Google). I use Windows 7 Home Premium 64 bit and Eclipse Java EE IDE for Web Developers.
My device doesn't show in Eclipse DDMS view. My device also doesn't show when I run adb devices in cmd.
I have USB debugging enabled.
When I try to install the USB driver as shown here I get a message that my device software is up to date.
I also tried killing the adb server and starting it again.
Give the Universal Naked Driver a try? Be sure to follow the steps in the forum post.
Nexus devices require the Google USB Drivers, you can get them through the SDK Manager.
If you have them installed and the device still is not detected try the following:
Use a different USB port (for me the USB 3.0 port is always making problems)
Restart the device and the computer
Restart ADB
Also take a look here, which explains how to install drivers for the Nexus S.
I had a similar problem. I could not get my device to show up in my Eclipse devices window. When I typed adb devices, no devices were discovered. Fortunately, I discovered this website. It basically had me install a generic driver for my Motorola (Android 2). It had other drivers for Samsung and other manufacturers. After the install, my Motorola phone became visible with ADB.
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"