A friend of mine also tried plugging in his HTC G2 (with Cyanogenmod), which also did not work. And I've been looking for a solution all around the place, and it seems to be a problem with Android phones in general; however, I know it's possible to get it working somehow because not everyone has the issue.
Basically, no matter if I have the USB connected via charge only or mass storage, the car display flashes "UNSUPPORTED". I've tried it with and without USB debugging enabled. And with all those combinations, I've tried having a music application open/no music apps running.
I also tried a solution here, which also did not do anything different.
I've also seen a few responses saying to just use Bluetooth instead. My car does not have Bluetooth capabilities. Using an AUX cable is a possibility, though I'd rather have the USB working.
Thanks!
Seems like the system wants to recognize your phone, but USB mode takes a few seconds to enable and therefore the system just rejects it. Disk mode will DEFINITELY have to be activated at some point, but the question is when. Try these steps:
1. With the car on, turn on the radio but don't have it in USB mode yet. Use radio, aux, cd, whatever. This will likely power the USB port at least.
2. Plug in your phone, make sure to select disk/mass storage mode.
3. Wait like 10-15 seconds for it to settle in, THEN select USB mode.
If that doesn't work, try different combinations. Like start with the radio completely off or something. If you have more than one USB port, try a different one. Other than that... I'm stumped. I got it working in a rental Ford Fiesta, but I don't remember the exact method. But it was something like this.
Try the radio with a USB stick drive to see if the radio even works that way
Sent From My Pocket
Sorry thegregbradley, I tried it but it didn't work.
I tried doing a couple of different things similar to that too, and it didn't work either.
As far as using a regular USB drive with some music files on it, it works fine! My friend used her iPod and that worked fine too. I don't see why it has such a problem with Android though...
In doing some reading, I have discovered information that says you need to turn USB debugging OFF for this to work...
Info comes from this thread:
http://www.hondacivicforum.com/foru...nics-10/2012-usb-android-support-88695/page2/
If not that, then I wonder if it's a problem of file management on your SD card? Just as a test, try putting your songs directly in your root folder. Or at most, one folder deep. The Fiesta I rented had bluetooth functionality, so I ended up doing it that way, as it was faster and less problematic. But I definitely would rather just plug it in if it just worked that way.
Iv found that running a rooted rom with debugging off and in mounted mode works great in my car.... No other combo has worked for me
@pwncloud, did you ever get this to work with USB debugging off? Just curious
I have debugging off in my car too and no mods to my android, it's a G2 and I get the same error on my 2012 Civic LX.
To update, no I never got it to work. I've settled with an aux cable.
Related
Interesting problem I have had on and off. When I plug my phone into my desktop, it will connect normally, then a few seconds later it acts like I unplugged it. It's not the rom as it does it in recovery as well(both with usb-ms activated and without). I have HTC Sync installed. Rebooting either the computer and/or phone doesn't fix it, it just goes away after awhile and starts working again. I've experienced the problem FAR less when connecting it to my laptop, it will typically work there and not on my desktop when the problem crops up.
it's like this problem but it's not constantly http://forum.xda-developers.com/showthread.php?t=711616
-Edit- the device also doesn't show it's charging even when it 'disconnects'
I have the same problem. just keeps discontenting over and over it sees it for a few seconds then disconnects reconnects then off again.
sasigns said:
I have the same problem. just keeps discontenting over and over it sees it for a few seconds then disconnects reconnects then off again.
Click to expand...
Click to collapse
Mine doesn't reconnect, it 'disconnects' and stays that way(as if i unplugged it) until i actually do unplug it and reconnect it.
-edit- 1,000th post, YAY
I was having the same problem on my MacBook until I realized the MacBook must be plugged into power. Once plugged in everything was good. I wonder if the Evo demands more power through USB then other devices.
Yeah, sounds like a power issue to me. If you're using a USB port on a hub or on a keyboard, try one on the PC itself. Also, it could be a slow USB port or a bad cable if you are continuing to have issues. Try another computer if you can, and if you still have the problem try a different cable. Still have the issue, reflash (if you're running a custom rom) or contact Sprint for service.
Same issue here, but on a desktop PC (Dell Studio XPS) using the front-mounted USB port (not a hub). Keeps disconnecting/reconnecting, but often takes 10-15 minutes between cycles. Using stock ROM (for now, at least). Will try other ports & another PC and will report back.
Already tried different ports, only motherboard ports
Rom doesn't matter as the problem exists in both android and recovery
Don't have a different cable, however the same cable will work fine on my laptop then not work on my desktop
mrono said:
Already tried different ports, only motherboard ports
Rom doesn't matter as the problem exists in both android and recovery
Don't have a different cable, however the same cable will work fine on my laptop then not work on my desktop
Click to expand...
Click to collapse
If it works on a laptop, but not the desktop, then it appears to be an issue with your desktop. Any other USB devices doing it?
I would check your motherboards manufacturer and make sure you've got the right USB drivers, a bios update might be in order as well.
But before all that, I've got an idea. First and foremost, try this:
Go to device manage (either from control panel, right-clicking my computer and going to properties, or searching for devmgmt.msc in the start menu search.)
Navigate down to Universal Serial Bus controllers, double click on USB Root Hub (you probably have 1 for every USB Port, so you may have to do them all.)
Click on the Power Management tab, and uncheck the "Allow the computer to turn off this device to save power." check box and see if that solves your problem.
i had this issue on my hero. it was corrected for me after i did a wipe of data and cache. i restored from titanium afterwards. YMMV
good luck
one thing you might try is disabling sense and using the android launcher. then reset the phone. once it boots up try and connect it to your pc. This was how I got mine to connect. when I was using the sense launcher it somehow blocked that options screen and the default I selected wouldn't stick. once I got the connection to my pc working this way I was able to re-enable sense and it's worked perfectly ever since.
I do not take credit for this fix, someone else on here told me to try this n it worked perfectly.
tarheelsmj12001 said:
one thing you might try is disabling sense and using the android launcher. then reset the phone. once it boots up try and connect it to your pc. This was how I got mine to connect. when I was using the sense launcher it somehow blocked that options screen and the default I selected wouldn't stick. once I got the connection to my pc working this way I was able to re-enable sense and it's worked perfectly ever since.
I do not take credit for this fix, someone else on here told me to try this n it worked perfectly.
Click to expand...
Click to collapse
it was nothing with the rom, since it was doing the same thing in recovery.
it turned out to be the short little usb extender cable that was going a foot and ahalf from behind my pc to the side so i could plug it in easier.
Sirchuk said:
...Navigate down to Universal Serial Bus controllers, double click on USB Root Hub (you probably have 1 for every USB Port, so you may have to do them all.)
Click on the Power Management tab, and uncheck the "Allow the computer to turn off this device to save power." check box and see if that solves your problem.
Click to expand...
Click to collapse
I can confirm this works on my HTC Desire - had been racking up my brains for the past couple of days now with no solution! Thanks a lot. This is on PC with Win7 Ultimate.
Hello all. I'm TK, newb who has been lurking for a while. The forum has led me to some awesome changes with my Evo, but that may be catching up with me. I'm still rooted and running CM 7 with SZ 1.01, and none of my computers are able to recognize the USB drive on my phone, regardless of which cable I use.
I can't get ADB to work on my PC, so I'm not able to perform any commands for the phone.
Can anyone help me with this issue? It would be much appreciated. Thanks!
Do you have debugging(in application settings) on when trying to use adb? What about allow mock locations? Try turning debugging off and then turn it back on(while plugged in USB). If that doesn't work you could always go to recovery mode and enable USB toggle and get it connected that way. Also make sure you're actually pulling down the notification bar and selecting "mount".
Sent from my PC36100 using Tapatalk
CrucialTK said:
Hello all. I'm TK, newb who has been lurking for a while. The forum has led me to some awesome changes with my Evo, but that may be catching up with me. I'm still rooted and running CM 7 with SZ 1.01, and none of my computers are able to recognize the USB drive on my phone, regardless of which cable I use.
I can't get ADB to work on my PC, so I'm not able to perform any commands for the phone.
Can anyone help me with this issue? It would be much appreciated. Thanks!
Click to expand...
Click to collapse
Does your phone get recognized at all on your computer when you plug it in? If not you may have a hardware problem -> usb port is loose.
On my original cord that came with the phone I had to trim off about 2 centimeters off of the plastic to go in far enough to have my Toshiba laptop to read it. I have had to do the same thing to several cords since. Maybe your usb?
alexisprz said:
Does your phone get recognized at all on your computer when you plug it in? If not you may have a hardware problem -> usb port is loose.
Click to expand...
Click to collapse
Yes, my computer just says that it doesn't recognize the hardware. it charges just fine by the computer.
I'm running ClockworkMod for my recovery, I'll check for USB Toggle there.
No joy on finding USB Toggle.
It's called something different. Can't remember but it's there, I believe. I've only been in Clockwork recovery like once.
Hi all. Long time lurker, first time poster here.
I have had my Galaxy Nexus for around a year now and have never had any problems - I've flashed countless ROMs and kernels, etc. However, just recently my phone has stopped being recognized by my computer(s). I've searched and searched and read every thread remotely related to the problem and still the problem persists.
At first I thought it was the new Macbook I was using, or OSX, but I've tried everything I can think of in Windows, OSX, and Linux.
When plugged in, I get nothing in OSX - finder won't find it, android file transfer won't find it, adb won't find it. In Windows, I get an unknown device in device manager, and a popup on the toolbar saying the device has malfunctioned. I've tried all three driver installs with Wug's toolkit, switching from MTP to PTP, turning Debugging on and off, flashing new roms and kernels, installing drivers manually, installing drivers through the Android SDK, even different computers - but every time I get "The USB Device has malfunctioned," or nothing at all in OSX's case. I've even tried a laptop running Ubuntu - still a no go. All the while the phone shows it is charging fine, but no indication of being connected to a PC like it used to do.
I've even tried bending the USB port a little as I've read in some guides and cleaning out the port - no luck. I have yet to try a different cable - one is on the way - but my next step is to replace the USB port board myself, unless anyone has ANY ideas.
It charges fine and never has any problems, it's just I cannot get it to be recognized by anything I plug it into.
I don't have an option to enable/disable fast charge in this ROM (currently on CM10) but I have disabled it in one of the ROMs I flashed to and still no luck.
Is there anything I've yet to try, besides using a different cable? Maybe fast charge was enabled in another kernel and it's screwed up some stuff? Although that seems impossible because I've factory reset/wiped everything and flashed different ROMs and kernels and still nothing. I just don't know at this point.
Any input at all would be great, but I understand if there's nothing else I can do besides trying a new cable and then replacing the board. I finally get going in Android development and this brick wall stops me in my tracks.
Thanks guys.
Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port
The two options you came up with yourself sounds most plausible. I've been through a ton of MiniUSB cables that have gone bad out of nowhere (just lying in my briefcase). So test that one first before buying a new USB port.
Well what do you know, it was the USB cable. I cannot fathom how a USB cable just stops working on the data side of things but still charges after just sitting around. I found another cable in a drawer, plugged it in, and voila, everything's working. Glad I don't have to replace anything, though. Woo!
Good thing is though I now know my way around the drivers and the SDK and am pretty sure I could write a guide on everything you could do to fix a USB issue. The more you know!
tuk1maar said:
Try to clean the port (by blowing all the dust out of the usb-port)
For now, just use 'Wifi-explorer'. I use it ALOT just to save my USB-port
Click to expand...
Click to collapse
I had been using AirDroid before and loved it. And even though it was a cable problem, I know know my USB port is squeaky clean, ha.
Just wondering if Android Auto for connected car displays stopped working for anyone as of yesterday or today. I'm skeptical of another Google "back end experiment" that caused it to stop working. I have a Ford with Sync 3
Symptom: Plug phone into car, nothing happens. Phone only charges and will even say USB is connected.
I've done some basic and partially in depth trouble shooting. It most likely couldn't be caused by any updates on Car infotainment system or my Phone because it has been working (unless there was a back end play services update that was pushed out).
From the obvious to less obvious:
-Tried rebooting phone and restarted car
-Tried using a different USB A to C cable (Anker ones have worked perfectly for me)
-Tried using secondary USB port in car
-Tested phones ability to connect to a PC and transfer data, no issue
-Threw music onto a USB flash drive and plugged it into car, no issue
-Tried turning on USB debugging on phone, no change (not sure if this would have even helped in first place).
I'm at a loss right now. It does not make any sense.
I do not have another android phone to try or an iPhone to test CarPlay unfortunately.
Literally had the same thing happen to me on Sync 3 last week. I just deleted the car from the Android Auto app and deleted the phone from Sync 3. After that I was able to use Android Auto again after going through the setup prompts. No issues since.
Works fine for me on my 2018 silverado
no issues on 2017 Sierra
Here it works perfectly
bigblueshock said:
Just wondering if Android Auto for connected car displays stopped working for anyone as of yesterday or today. I'm skeptical of another Google "back end experiment" that caused it to stop working. I have a Ford with Sync 3
Symptom: Plug phone into car, nothing happens. Phone only charges and will even say USB is connected.
I've done some basic and partially in depth trouble shooting. It most likely couldn't be caused by any updates on Car infotainment system or my Phone because it has been working (unless there was a back end play services update that was pushed out).
From the obvious to less obvious:
-Tried rebooting phone and restarted car
-Tried using a different USB A to C cable (Anker ones have worked perfectly for me)
-Tried using secondary USB port in car
-Tested phones ability to connect to a PC and transfer data, no issue
-Threw music onto a USB flash drive and plugged it into car, no issue
-Tried turning on USB debugging on phone, no change (not sure if this would have even helped in first place).
I'm at a loss right now. It does not make any sense.
I do not have another android phone to try or an iPhone to test CarPlay unfortunately.
Click to expand...
Click to collapse
happens to me every 3-6 months.
Swapping out the cable resolved it every time.
ya dude you need to try some different cables. that should always be your first step if there have been no updates.
Thanks for the replies. I deleted and unpaired AA from my phone and my car with no luck.
I actually had my coworker who has a Pixel 2 XL plug his phone in to my car. He had no issues at all even after multiple tries. Mine still wont connect. We're both on Pie with same security patch level. Did try tried Multiple new cables and still no luck (the anker high quality ones).
I found this thread incase it starts happening to anyone...
https://productforums.google.com/fo.../PWBrDUXzR4o;context-place=forum/android-auto
Something I picked off of that topic was some USB patches/features that went in to effect between Pie release and last month security patch.
I may just wait a month. Maybe another security patch which tweaks USB or 9.1 will drop fixing my issue. We shall see. At least I know its not my car or my cables.
Go into apps and check your "play services" versions between the two phones. Google controls a lot of **** through that app
Or just try to clear your usb port
Thanks for the replies. After the October patch I'm back up and running.
Lack of communication between departments at Google baffles my mind.
I have an S22 with Stock Android and bought Gamesir X2 to play XBOX Cloud and Retroarch games with it.
For some reason I decided to buy the USB-C version over the Bluetooth (I thought I was neat to be able to charge the phone while playing and also less input lag due to BT delays).
Thing is, gamepad arrived, I rushed to plug it in and found out nothing happened. Gamepad blue light stays blinking (its supposed to stay blu when connected) and the phone doesnt even detects anything.
This is supposed to be a simple OTG gamepad, so should be plug-n-play.
I reached to Samsung about 'how do I enable OTG to use my gamepad' and the answer was 'OTG is enabled by default'
I also reached out to Gamesir, they told me to try press G+S buttons on the pad while connected, but nothing happened
There's a Gamesir app that is suppsed to be used to detect it (and also map the gamepad on some touch screen games) but doesnt work for me
I also found some guy on youtube claiming I should enable ADB debug and set USB default to 'File transfer'. Doesnt work either
Anyone having the same issue?
Anyone having a USB-C Gamepad working?
Any ideas on what to try out to get it working?
Thanks in advance
I've recently run into a similar issue however on a S23+. The device I'm trying to use is a Seek CompactPro FF USB-C which uses powered OTG. No need of a cable as it has USB-C built into the device itself.
It didn't work at first, it detected it and tried to open the "Seek Thermal" app which is normal but in the app itself the device was not being detected. Did a ton of searching until finally I found another person having a similar issue where the work around was to plug in the OTG device, then reboot the phone with the device still plugged in.
Give that a try? IMO it shouldn't be like this, and it isn't very well documented anywhere I look...but that worked for me for my device. Did not work any other way. Device works perfectly fine after rebooting phone with it plugged in.
86brown said:
I've recently run into a similar issue however on a S23+. The device I'm trying to use is a Seek CompactPro FF USB-C which uses powered OTG. No need of a cable as it has USB-C built into the device itself.
It didn't work at first, it detected it and tried to open the "Seek Thermal" app which is normal but in the app itself the device was not being detected. Did a ton of searching until finally I found another person having a similar issue where the work around was to plug in the OTG device, then reboot the phone with the device still plugged in.
Give that a try? IMO it shouldn't be like this, and it isn't very well documented anywhere I look...but that worked for me for my device. Did not work any other way. Device works perfectly fine after rebooting phone with it plugged in.
Click to expand...
Click to collapse
Thanks for your reply 86, tried that but didnt work for me. I saw a couple of videos where the blinking blue light might mean that its not connecting well (its supposed to stay blue) so I guess its something to do with how the cable is connecting. Since Gamesir already told me I have no warranty nor support from them as I bought it on Amazon instead of their site I'm thinking on tearing it appart during the weekend.
If I break it I'll end up with a nice pouch case for my cables (the most expensive pouch ever).