So, I was looking through the Developer Options on my Android 6.0.1 Galaxy S6 and found a setting for USB Configuration. Now, at first this seemed rather obvious, MTP mode, PTP mode, Charge Only, etc... until I found the Audio Source option. I tried selecting this and connecting to my Windows 10 PC and it detected what it thought was a generic "USB Audio Device", but returned an IO error and couldn't start the device. I'm guessing Windows needs a more specific driver to recognize my phone as an audio source, but where can I find such a driver?
It's not working somehow. The implementation isn't meant to work from what i heard. I wrote to the (German) Samsung twitter account and they said it's not working (idk why). But they said it's not working
Related
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.
Hello everybody!
I have a problem related to connectivity between my desktop (Windows) and tablet (Android 4.1). I bought a new device (Colorovo City Tab Vision 7) and now I want to use it for testing of my applications, because emulation of android is very slow on my computer, although I forced it to create snapshot every run.
I have downloaded SDK with Google drivers and also some unofficial drivers I found on web. When I connect my device, it first appears 'Other device' (label is CTVision7) and it's marked as unknown. I tried to install drivers (Google) for it, but windows said that they aren't suitable for my device, as it's not able to find them in specified directory.
After these attempts I tried unofficial drivers. Their installation worked and now my device appears as Android phone, what seems to be good.
But when I run
Code:
adb devices
or launch application in eclipse, there's not avaible device.
I have turned USB debugging on, so it should work.
Am I missing some step to make my device avaible for debugging, or are my drivers wrong? Is there any way to get drivers which surely work?
Howdy.
I recently updated my YP-G1 from CM10 to CM 11 [4.4.2]. I need to use my device for Android app development (and have used it before way back when it was on stock, but haven't used it in a very long time), but am unable to get ADB/Eclipse to detect that there is a device detected. Using the emulator is not an option at this point, as I need to do some work with a real camera.
I've got the Android USB debugging enabled on the device, and the little notification that debugging is enabled comes up when I plug it in.
Things I've tried:
1) Update Eclipse/ADT (complete uninstall + reinstall)
2) Update Google USB Driver (from SDK manager)
3) Update Samsung Kies
4) Google
The only related forum thread that I've located for this situation is: http://forum.xda-developers.com/showthread.php?t=1776828, which just implies that Windows should be auto-detecting the device. Windows is not doing that.
I have noticed that the YP-G1 drivers do not show up as installed under Device Manager. Perhaps that is the source of the problem? I have not been able to rectify that situation via Kies, so I am unsure. Kies doesn't even detect that the device is connected!
If it matters, I'm running on Windows 8.
Thanks much.
P.S. -- I'd post in the CM11 thread, but since I just registered, I am not allowed to do so, unfortunately.
Edit: I got mine to work finally. I solved my issue by allowing windows to automatically search windows updates for drivers. After I did that it found them and it worked, so try that.
I too am having this issue and it's really bugging me. I've tried everything I can possibly think of but I cannot get the drivers to install. I'm using windows 7 64 bit and it sees the YP-G1 but it doesn't have the drivers so things like kies and adb won't detect it. Any solution would be very helpful.
Strange...that's what the thread I linked to suggested. I've tried that multiple times to no avail. Perhaps Windows 8 doesn't find it, while 7 does for some reason? I've tried doing searches via both Device Manager and Windows Update.
Could you perhaps upload the driver files it found? You should be able to figure out what/where those are by using Device Manager, then right click the YP-G1 and go to Properties, then the driver tab, then driver details. Maybe they'll work on Windows 8 as well as 7. I might try plugging my device into someone else's computer to see if somehow mine is just acting stupid.
Thanks for your reply!
Edit: I've plugged my device into another computer. You're right -- on Windows 7, it can find the drivers just fine. On Windows 8, it can't. Go figure. Now to figure out where to get those files and/or how to get the device recognized..... (??)
Hello. I'm a happy (?!) user of Win 10 Pro x64 since few days.
I want to connect my RN4X Snapdragon to PC, using usb on my pc's motherboard.
However, despite setting option, that I'll listed below, my phone is still not recognisable as useful stuff.
Without changing anything on my phone since my last flashing topics (Feb and March this year), I was fully able to connect easily to pc with win7 x64. I also was able to connect (using Xiaomi's cable, cheap replacement does not seem to work) phone to win 8.1 x64, where only the basic adb fastboot were installed. But, I cannot do the same on newest Windows.
I've done:
1. Installing minimal adb and fastboot 1.4.3. for all users (I'm the only one account here, but not sure if that's matter)
2. Having programming option enabled, usb debugging enabled and all that good stuff.
3. All four elements on that list - https://************/how-to-fix-mtp-devices-not-connecting-on-windows-10/
4. I've tried to install it as adb interface, installing it manually, installing it by using *.cat files from xiaomi_usb_driver archive, that contain that kind of stuff for newer windowses (it's from this side, if I remember it right - https://www.xiaomiusbdrivers.com/2018/02/download-xiaomi-usb-driver-2018-for_4.html)
5. Almost all stuf from here - https://www.jihosoft.com/android-tips/windows-10-cannot-recognize-android.html. Because I do not have Samsung, Odin mode is not an issue
6. I've tried to install my Redmi 4X as MTP device. However, my phone during each connection to PC started himself in charging mode (I can change it). Even changing it doesn't changing anything, though.
7. Editing the bulid.prop, adding there few lines describing how the phone should behave. I've saved it, but my original version of bulid.prop does not have anything in there about types of connection. I don't remember it word by word, but I've could check in history if anyone will find it interesting.
Drivers for usb 3.1 are pre-installed with mine version of win10 (I cannot install drivers given on my motherboard's dvd attached, system says that I'm currently having them).
When I try to install it manually via device manager, on the first time it says, that is other device, identifed briefly as MTP. However, installing it either as Android ADB interface, fastboot interface or third option does not give me anything. What's worse, even when I've pick windows/INF as my source of drivers for this device, it does not list on "lemme pick ddevice type" MTP type devices. I'm using win 10 in polish, so it might be that I'm blind or does NOT understand translate.
What else could I do? I can of course use wife's laptop with 8.1, usb sticks or other stuff, but I would like to have it sorted out.
Does otg still works to your device?
whatpigs said:
Does otg still works to your device?
Click to expand...
Click to collapse
Not sure. How to check it? We use to have 16GB OTG to USB2.0 (other end was micro usb B), but we must have put it somewhere during moving out to new flat, cause I cannot find it now.
gonna bump it, cause there's not any clue yet.
Same here.
Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized,
all drivers installed correcly with hisuite , my cable usb is new,
i changed today the USB charging port of the phone at Huawei care service, and i reset factory the phone , still same problem.
I'm still having the same stock rom on the device,
is the "usb not recognized" problem can be a software problem in the phone? thank you for your experience.
chahine21 said:
Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized
Click to expand...
Click to collapse
I'll try to help you but I'm not an expert, and yet I've had EVERY problem you seem to be speaking about.
a. I have had broken USB ports
b. I have had broken USB cables
c. I have had the USB drivers not install on Windows
etc.
Given I've had some of the same problems, I feel for you, so my first advice is to simply give up on USB for everything that you can.
Specifically, if you can turn on USB debugging and Wireless debugging in the Developer options, you can operate the phone over Wi-Fi using the Windows monitor, keyboard and mouse as shown in my screenshots below.
You don't need anything installed on Android to use these FOSS solutions on Windows to operate the entire phone over Wi-Fi as of Android 12 (which eliminated the need for an initial USB connection to establish the Wi-Fi connection).
In summary, I have had similar problems with USB where I've given up on USB and switched to operating Android over Wi-Fi and even mounting the entire Android file system as a Windows drive letter over Wi-Fi using free software.
a. adb
b. scrcpy
c. vysor
d. webdav
Use Windows Event Viewer to check for error messages on the PC.
If the problem is the PC it will likely show up there and give you more troubleshooting clues.
Thread closed at OP's request.