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 can't seem to make eclipse recognize my Xperia E1 as an ADB device.
The problem is that in the devices list of eclipse it is detected but it says 427ac413 as serial number and the target is unknown. USB Debugging mode is on, I have tried both MSC and MTP modes, I rebooted the device, the ADB Driver is installed from PC Companion (although it says Sony so0107 and not so0101 as I have seen on some other forums). I'm thinking it could either be a driver problem, maybe the wrong one is installed, because the first time I installed it the adb driver said it was from Samsung, and I had to uninstall it and reinstall it.
Any suggestions on how to make it work?
Here are some steps that may work.
Turn off the USB Debugging mode
Connect your phone with both MSC and MTP modes (check that it is accessible in each mode, this means that at least these 2 drivers are fine)
Disconnect phone
Make sure ADT USB Drivers are up to date.
Check that adb is running, better by task manager (If you try at the same time eclipse and cmd adb they mess themselves, red errors about adb start appearing in eclipse console at this case.)
Turn on the USB Debugging mode on the phone, connect it in MSC.
Connect the phone, it should ask for USB debugging access.
In case everything fails.
Try another USB
Try another USB cable, some idiot phones work better by the "authentic" cable Sony with Sony, Samsung with Samsung etc.
Restart phone
Restart computer
On / Off USB Debugging mode with either the phone connected or not.
Try manually driver installation by pointing the folder of PC Companion or ADB drivers
Restart eclipse
If still resists, lets make sure that android connects:
(Close eclipse) Open cmd run adb command
Connect phone on debug mode adb devices check that is online. If yes, its a matter of chance that eclipse recognize it. If no, you may have issues either with adb or with drivers (?).
In case you have issues with adb. Some Companies install an adb in the Phone Suites in order to update phones or access phone data. This adb sets itself in installation at the PATH and starts instead of the Android ADB which is for development. In this case you can run in cmd adb kill-server navigate to android adb location and adb.exe start-server.
In case of the drivers search the net for Xperia E1 android debug drivers and start testing if anything works.
It seems that this issue can be fixed by manually updating the ADB driver through Windows Device Manager. There is a support thread on the Sony Experia Forum that discusses, and provides detailed steps for a solution, this issue:
http://talk.sonymobile.com/t5/Xperia-E-E-dual/ADB-driver-XPERIA-E/td-p/290337
I have solved my problem by following these steps.
The problem was that the SDK_HOME folder wasn't set properly and the PC wasn't authorised. So i disabled developer tools and enabled them again, revoked USB Debugging authorisations and then plugged it back in. The dialog appeared on my phone and then it all worked.
First, you may used the wrong driver, try to get it from here, here, or here.
Then, force the windows to reinstall the driver again:
Choose the device from [device manager].
update driver ----> browse my computer for driver software ----> let me pick from a list... ----> Have Disk.
Browse and choose the proper driver, the press OK.
Last, restart your adb:
from cmd go to /platform-tools directory then write adb kill-server then adb start-server.
I am trying to debug my application using a real device instead on the emulator. When I try to connect, it gives me the message:
USB device not found
I tried to unplug and plug it again, but it did not work. And I have also enabled USB debugging and unknown sources options in my device.
Any help is appreciated!
Thanks!
I had this problem with a Nexus 7 - it appeared in Device Manager fine but wasn't recognised by Android Studio. The device had USB debugging turned on. Eventually I noticed an icon in the top left hand corner that said "Connected as a media device. Touch for other USB options." When I selected this I was able to change from Media Device (MTP) to Camera (PTP) and then it started working.
If you are on windows, many times it will not recognize the device fully and because of driver issues, the device won't show up.
go to settings
control panel
hardware and sound
device manager
And look for any devices showing an error.
Many androids will show as an unknown USB device.
Select that device and try to update the drivers for it.
This solution works for every unrecognized android device... mostly general brands don´t come with usb debugging drivers...
go to settings
control panel
hardware and sound
device manager
And look for any devices showing an error. Many androids will show as
an unknown USB device or just Android
First thing you need will be your device IDs. You can get them opening up the device manager and finding the "Unknown Device" with a yellow exclamation point. Right click on it and select 'Properties', and then go to the 'Details' tab. Under the 'Property' drop down menu, select hardware IDs. There should be two strings:
USB\VID_2207&PID_0011&REV_0222&MI_01
USB\VID_2207&PID_0011&MI_01
Copy those strings somewhere and then navigate to where you downloaded the Google USB driver. Then you need to open up the file 'android_winusb.inf' in a text editor. I would recommend using Notepad++.
First, create a sub-section for your device. I called mine ';RCA 6378W2' but it doesn't really matter what you call it. Then, under the sub-section you created paste the Device ID strings you copied from the Device Manager, preceded by '%SingleAdbInterface%'. If you need help, look at this screenshot.
NOTE:
If you are using Windows 8 or 8.1, you will need to disable device driver signature checks before you'll be able to install the modified driver. Here's a quick video on how to disable device driver checks http://www.youtube.com/watch?v=NM1MN8QZhnk. Ignore the part at the beginning about 64 bit, your computer architecture doesn't matter.
Please look at this article, for more information and MacOS instructions.
Try a different cable, ideally an official Samsung one.
I had tried a crappy USB cable I had lying around and then tried another which was Samsung and works perfectly now.
Not sure why they would be different though but worked for me.
Found out for Samsung, Installing Kies also update the usb driver which solve my problem with connecting my Samsung Galaxy S Advance with Android 4.1.2 to Android Studio on Windows 7 64bit.
In this case the devise manager shows device driver is updated and working, but when I connect my phone Android Studio does not recognize my device.
I had the same problem with connecting my Galaxy Nexus to win7 x64. I solved it by getting drivers, they can be downloaded from here or also via Android SDK manager.
After you put your phone on developer mode, restart it. That worked for me, maybe it will work for you also. After restarting it, the phone was recognized, drivers were automatically installed. Note - I'm running on Windows 7.
I've been having this issue on Mac OSX Mavericks using Android Studio, using my Samsung Galaxy Express , I did a little trick, Run -> Edit Configurations - > Run -> Show chooser dialog. When I "play" and the dialog appeared, I connected my device and it did appear. ;)
You need to install the driver first. Follow the instructions on the Android's developers website:
http://developer.android.com/tools/extras/oem-usb.html
I had the same problem with a Samsung galaxy note 2. It was recognized on one pc but not on another one (both running windows 7 64b). After hours of struggling, I installed Kies (from the Samsung website) on the pc where Android Studio was unable to detect the smartphone (Kies was installed on the other one).
Like magic, Android Studio detected the phone !!! I noticed that the Kies installer installed some driver for the phone.
Consequently, for those meeting the same detection problem, I would strongly advise to first install Kies.
Galaxy S7, I had to go to Settings, Developer Options and allow USB Debugging. This asked to approve computer it was attached to and it showed up instantly.
I had tried restart the device, and it's work, popup and ask want to trust the mac for debug mode.
I am using Samung S8, I tried to install:
Intel Android Driver
Samsung USB driver
But the adb bridge driver was still missing.
I finally got it to work by installing the Samsung Smart Switch application which is a media manager application.
Updated at 2018-04-20: If you are struggle with the driver, just use http://adbdriver.com/downloads/
If you're using a USB Type-C cable, check if it has the charging and data transfer capability. Many USB Type-C cables are for charging only, and are not recognized by Android Studio.
Check installed drivers. If drivers ok, check device usb-port it could be damaged.
I have a Samsung Galaxy S4. Although visible from Devices, my phone was not listed as connected from Android Studio. I tried a few things independently, and then together, and found that only a combination of steps fixed the issue, so this is for you if measures listed above or on another site did not work on their own.
Enable USB debugging from "Developer Options"
Download Kies from Samsung. I believe Samsung US has replaced Kies with a new software called Smart Switch, but this did not resolve anything for me. I found a Samsung UK download of Kies that worked fine.
After connecting your phone to your PC via USB, go to your phone notifications and click on USB settings at the top. Switch it to Camera mode.
I repeat, only all 3 of these together fixed the issue, so if some fixes you have tried haven't worked, use these 3 and it could fix the problem for you. Best of luck.
Restart Android Studio Worked in my case
For me, this simple trick worked:
I actually enabled and disabled the listed USB Adapter for android in the device manager (Control Panel -> Hardware & Sound -> Device Manager). And holy moly it's working! :D
The solution for me was following the instructions at https://developer.android.com/studio/run/oem-usb.html#InstallingDriver. Specifically, the key part from that link that helped me to find the solution was this: "Install a USB Driver. First, find the appropriate driver for your device from the OEM drivers table below." This means that you cannot find a single link that applies to everyone as the solution. It will depend on your device! "So I visited the page to get OEM Drivers at https://developer.android.com/studio/run/oem-usb.html#Drivers. In my case, the device I was using was an LG K8 LTE. I had to go to http://www.lg.com/us/support/software-firmware-drivers#, Browse by product and I found the driver I needed under the Model Number "LGAS375 KG K8 ACG - AS375", Cell Phone Product. From http://www.lg.com/us/support-mobile/lg-LGAS375 I used the "Install the USB DRIVER" for Windows (http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425).
Depending on the device model you are using, you will need to find the specific drivers that work for your phone, and that should work.
How to get connection to device working using adb command line:
USB debugging enabled on phone and phone connected.
I am exercising these commands on linux(redhat and ubuntu) but same commands work under the hood on windows. The device manager runs adb commands. You can find a console in your device manager or regular command-line works if you set up your paths to SDK.
If you can run adb and see something like ???????? in devices list ..
$ android-studio/sdk/platform-tools/adb devices
List of devices attached
???????????? no permissions
You might be running the adb server as a regular user.
You might have to run the adb server as root.
So kill the server as regular user and start it as root.
$ adb kill-server
$ which adb
$ sudo <fullpath>/android-studio/sdk/platform-tools/adb start-server
Now look at adb devices list, if it is first time this machine connects to this phone you will see "unauthorized".
$ adb devices
List of devices attached
MWS0216A31xxxxxx unauthorized
At this point on phone you should have dialog popped up and you can tap ok to authorize. Then you should see "device" in the devices list and commands like shell/push/pull/sync/backup... should work.
$ adb devices
List of devices attached
MWS0216A31xxxxxx device
$ adb shell "uname -a; df; ls /storage/sdcard0/Download"
Linux localhost 3.10.90-g2ff1b22 #1 SMP PREEMPT Tue Dec 27 17:12:50 CST 2016 aarch64
Filesystem Size Used Free Blksize
/dev 1.3G 108.0K 1.3G 4096
/sys/fs/cgroup 1.3G 12.0K 1.3G 4096
/mnt 1.3G 0.0K 1.3G 4096
/sys/fs/cgroup/pids: Permission denied
/system 2.4G 2.3G 106.8M 4096
/cust 492.0M 327.7M 164.3M 4096
/cache 248.0M 160.0K 247.8M 4096
/splash2: Permission denied
/3rdmodem 59.0M 4.9M 54.1M 1024
/3rdmodemnvm: Permission denied
. .
/storage 1.3G 0.0K 1.3G 4096
/data 25.1G 10.9G 14.2G 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 25.1G 11.2G 13.8G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
.
.
Lovely jubly. Hopefully.
For example:
My file path:
C:\...\sdk\extras\google\usb_driver\android_winusb.inf
My data to paste:
;Tablet PC
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
%CompositeADBInterface% = USB_Install, USB\VID_18D1&PID_0003&REV_0230&MI_01
Well, in my case updating drivers, restarting Android Studio, restarting my phone, changing the USB mode or unplugging USB did not help.
Then I went to the dev settings in my phone, toggled the Dev. Mode off and back on, and it worked. AS was open and phone was plugged at the moment.
I had this problem occurring suddenly in Dell Ubuntu linux machine with Android Developer Studio. I did the following steps
1. I opened "System Settings"
2. Select the listed item "Software and Updates"
3. Click on the tab "Additional Drivers"
4. There was a mention about "Dell Inc: Unknown" and the option "Do not use use the device" selected. I selected the alternate driver mentioned and did an "Apply the Changes".
It started working.
I just ran adb command prompt and hit 'adb devices' and it showed daemon was not running. It installed itself and now i can able to see android devices there.
C:\...\...\source\repos\ABC\ABC\Ex.Android>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZF22Q3T unauthorized
and Reload the project
Windows, many times it will not recognize the device fully and because of driver issues, the device won't show up.
1).go to settings
2).control panel
3).hardware and sound
4).device manager
Restarted my PC and worked in my case.
I want to install the Android USB driver for my Galaxy SII on a Windows 7 Enterprise x64 SP1 machine.
My phone is detected and listed in the device manager as "Other devices" and the status is "The drivers for this device are not installed. (Code 28)".
As I want to install the USB driver I choose "Update driver" and browse to the directory containing the driver, and here's the problem. Windows doesn't find anything, it just says
Windows was unable to install your
SAMSUNG_Android
Windows could not find driver software
for your device.
I can't remember ever having such problem with this... I have set the phone to "USB-troubleshooting" (or what the correct term is in English..) and the drivers previously installed for using it as a mass-storage-device are unistalled.
If anyone knows a solution to this problem and could forward it to me I would greatly appreciate it!
Thank you!
Try to install the driver from Kies, maybe...
Sometimes the Kies reinstallation itself does not help (as happened in my case). I was not able to Update drivers via Device Manager either. Following procedure worked for me (WinXP Prof SP3 32-bit):
I disconnected the phone.
I uninstalled Kies and removed all drivers related to phone with use of USBDeview
I installed Kies
I loaded Kies
I selected “Tools > Troubleshoot connection error” to force drivers install and waited, operation took several minutes
I connected phone in MTP mode (USB Debug mode was off). Windows installed some drivers automatically.
I disconnected phone and reconnected it with USB Debug mode on. Windows installed more drivers automatically (including Samsung Android ADB Interface)
I restarted the computer.
It seems it is vital not to plug the phone in before Kies installation is finished.
I've tried both JohnyCash and Phils answers, but still didn't manage to fix the problem. After couple lost hours, here is how I fixed it:
Go to device manager, select GT I9100 from the list, right click > properties, select Update driver, then Browse my computer for software, then Let me pick from a list of device drivers on my computer, select SAMSUNG Electronics Co., Ltd. > SAMSUNG Android ADB Interface, and install it.
adb was able to see the device after this, finally!
1) Enable USB debugging on your device.
2) Connect your device with a USB cable to your computer. Your Windows OS (vista or win7) will automatically install the required drivers.
3) You can check of the device is connected by executing adb devices from your windows command prompt. It should list the serial no. of your device.
Windows 7 for a Moto G and Samsung make sure USB debugging is disabled. Plug phone in USB. Windows will connect and install a driver to access phone.
Disconnect phone from USB. Enable USB debugging in developer options.
Connect USB again. No Windows installs ADB drivers. All shoulld work.
Enable usb debugging in developer options in phone.
Connect the phone to Computer.
Install the driver Samsung USB driver from the following site.
http://developer.samsung.com/technical-doc/view.do?v=T000000117
This will solve the issue.