I work at a company that programs for Android devices. As such, I connect and have connected hundreds of Android devices to my computer. Each time I connect a new device (which can be the same model as another device that I had previously connected) Windows runs the Driver Software Installation process.
When I first got this computer it would take about a minute to detect the device. Maybe a little longer the very first time, but not too long.
Now, after hundreds of devices have been connected to push software to them, the Driver Software Installation dialog takes about 20 minutes to detect one device.
Is there a way to speed this process up at all? I looked online and have uninstalled all the Android drivers for old devices under Device Manager, but even after uninstalling them all it still takes about 20 minutes to detect one device.
Thanks for any help or insight as to fix this issue.
Adam
There are these drivers available for each company like Motorola, samsung etc for android. You need to install just all the available i.e. on driver for all samsung one for all motorola. That way you could just start off as soon as you plug-in. Just google for motorola driver android , you'll get it.
It seems to be a driver bug. I tried different Android phones in many computers with windows XP, 7, and 8 and the connection process is very slow in all of them, you have to live with it.
Related
Persistent error on Samsung Galaxy Note 5
this is a weird issue that i am having for almost a year now, i'll try to be brief.
background story (What i think happened)
I own a Chinese aftermarket car infotainment system, running android 4.4. So, being the obsolete piece of **** that it is, i started digging around, and found out that it has something called Device link or something along those lines.
you have to download an app called EasyConnection from the play store, enable developer mode, and enable usb debugging, i know that's not the safest thing to do with Chinese stuff, but that's the only option i have at my disposal, so i have to manage.
anyway, it worked flawlessly for a year or so, then suddenly it refused to connect, with an endless connecting message. and my phone started giving me the Attention message, this was a year ago, and never worked since.
Attention
The connected device is unable to access data on this device. Reconnect the USB cable and try again.
Android File Transfer or Samsung Smart Switch must be installed on Mac OS X devices. To download Android File Transfer, go to https://www.android.com/filetransfer, or to download Samsung Smart Switch, go to https://www.samsung.com/smartswitch.
Phone behavior
Since then, whenever i connect my phone to my PC, either running windows or linux, it displays the Attention message. i can access files on my phone no problem, and it is not driver related, as this happens regardless of what driver is installed, or in the case of linux, no driver is required.
Android development
Now, a couple of months back, i decided to dabble in android development , as i have a couple of sysadmin years under my belt, and a beginner level knowledge of a couple of programming languages, so i thought android development would be fun, but here is the problem.
While my device is hooked up to android studio, i get this aforementioned error on random long intervals, but i am able to run my apps from android studio to my phone no problem. So i started to link everything together, and thought to seek help here on reddit after some fruitless internet diving.
note
I did a factory reset for my phone a month or so ago, so the only step remaining in my mind right now is to re-flash the stock firmware (i'm on stock for security reasons), but i am reluctant to do so because of the hassle of re-configuring my device again.
I'm hoping to accomplish the following :
Resolve the cause of the error.
See if my car system works with my phone after the error is resolved
Any help would be greatly appreciated.
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
I've started developing for android. I'm using different computers with different operating systems. (A Windows desktop PC and a Macintosh at home and a Windows Notebook at work)
Most of the time I am using my desktop pc for development but since yesterday my Nexus 4 is displayed as offline in the Eclipse ADT Devices view. This problem only occurs on my desktop pc. On the other computers I don't have any problems getting the device online in eclipse.
I already tried a lot of things like:
- unplugging/plugging the nexus 4
- switching off/on usb debugging
- restarting computer, nexus 4 and the adb server
- reinstalling nexus 4 usb drivers (I'm using the Android Composite ADB Interface Drivers from the Android SDK)
I was about to give up but then I remembered something. After connecting the nexus via usb the "Allow USB debugging" dialog shows up and on my desktop pc I checked the "Always allow from this computer" option.
My hope is that disabling this "Always Allow"-permission could help to get my device back online. I already searched in the developer options to find a way to reset the "Always Allow" permission without success. Maybe it is possible to reset the permission by clearing the data of the App/Service (Settings->Apps(All)) which stores this information but I didn't find the name of it in Google.
So does anyone know the name of the App/Service whose data has to be cleared to reset the permission? Or is there another way to get the device back online that I have not tought of?
You can use your device with multiple computers with that enabled as well. I can use my Nexus 7 and Galaxy Nexus, both running 4.2.2 and having checked the always allow option on 3 machines right now.
Make sure all your machines are running the latest update for ADT and the SDK Tools, as the adb in the previous versions does not support the 4.2.2 security measures. One of my machines had the same problem, and it got fixed when I updated my tools.
Also, sometimes you have multiple Eclipse installs (I have about 11, for various reasons). If all of them aren't updated with the latest tools, make sure your PATH points to the adb in the newest update, and not any other.
I need an android phone to test my apps with that will work with Eclipse. It has to be low cost, run Gingerbread with modest memory and CPU.
Thinking that any android phone would work I recently purchased a Virgin Mobil Chaser but as it turns out, it cannot be seen by either Eclipse or adb (but device manager does see the phone). Another developer has also had the same identical problem with the Chaser.
I could keep buying phones and see if they work but that could be long and frustrating. I hope to find a "no contract" phone.
Is there any list of phones that work with Eclipse. Does anyone know of any other Virgin Mobil phones that will work?
thanks, Gary
Any android phone should work. And it is not Eclipse you need it to be compatible with. You need ADB drivers for the device so ADT tools can communicate with device. So what you need is to install ADB drivers for your phone and then, once installed, you should be able to see your device once you enable USB debugging on the device. Then ADB should be able to see it (either in Eclipse plugin or via command line adb devices).
EDIT if you are on Windows, then enabling USB Debugging on the device and connecting it to the computer should result in Windows asking for ADB drivers. You may try if "stock" (these available with SDK in <SDK>\extras\google\usb_driver) are suitable. If not, check manufacturer website (for HTC you may need to install HTC Sync) and if this fail, just google for your device name along with "ADB drivers" and you should get something usable shortly.
One correct answer to my question is: the LG Optimus Elite works fine as a test phone. Drivers installed immediately. Also, it's less than $100 with no contract.
I still haven't found anyone who has gotten the PCD Chaser to work.
Gary
Any ideas where I can begin to find out what's going wrong?
I have a T-Mobile Pulse Mini (Huawei) which I'd like to get working for developing and testing apps on. I can't get it to be seen by Android Debug Bridge despite restarting the adb server. (and emulators are seen by adb any way so that's unlikely to be the problem).
In the device manager the phone is displayed as a CD-ROM and when I select 'transfer files' from the auto 'PcOptions.exe' it is then displayed as a USB driver but in either case I can't see it in adb. I have enabled debugging on the phone. I remember it took me ages to get it to work on my previous Vista 32-bit. I can't figure out where to search from here. The drivers used to install the phone are on the phone itself.
Thanks very much.
Drivers. If you can't see the phone in ADB, it's almost always a driver issue and this is especially common on Windows. The regular user drivers are sometimes different from the ADB drivers. If you can find the OEM dev drivers directly that's ideal, otherwise there's a way to modify the INF file which you'll have to Google for unless someone else provides it, as I don't remember the details at the moment.