Develop Bugs

3.5mm to USB-C Adapter Not Detected

So today I tried to use the 3.5mm to USB-C adapter to use wired headphones on my phone. It's been over a month since I've used the adapter and it was working fine. Today it's not working.
The strangest part is if I plug it in one way nothing happens at all. However, if I unplug it and flip it around the phone does detect it but instead of playing music it behaves as if I plugged it into my computer and I get the "Android System - USB supplying power to attached device" where I can tap and select between "Charge this device", "Supply power", "Transfer files", "Transfer photos (PTP)" and "Use device as MIDI".
Has anyone ever had this issue? Phone hardware issue? Adapter issue? Software issue?

I started having this issues while a go and it escalated fast, now everytime I plug my phone to any source of power it turns off
It could be the adapter as well but there is a small group of people having the same issue as me

Same issue here, I have to unplug and plug again my adapter for it to work. It has been several times that I accidently started playing music loudly on the bus.

humo091501 said:
I started having this issues while a go and it escalated fast, now everytime I plug my phone to any source of power it turns off
It could be the adapter as well but there is a small group of people having the same issue as me
Click to expand...
Click to collapse
Well, I haven't had that issue......yet. I contacted Google support. They are sending out a new adapter. Not sure if that's the issue but it's the easiest place to start. Otherwise it's a phone hardware issue or a software bug.
allweknowisa said:
Same issue here, I have to unplug and plug again my adapter for it to work. It has been several times that I accidently started playing music loudly on the bus.
Click to expand...
Click to collapse
Do you just have to unplug and plug in one to get it to work? Do you ever see the power/file transfer menu? That's all I get and only if I plug it in one way. When the connector flipped over I don't even get that menu.

jimv1983 said:
So today I tried to use the 3.5mm to USB-C adapter to use wired headphones on my phone. It's been over a month since I've used the adapter and it was working fine. Today it's not working.
The strangest part is if I plug it in one way nothing happens at all. However, if I unplug it and flip it around the phone does detect it but instead of playing music it behaves as if I plugged it into my computer and I get the "Android System - USB supplying power to attached device" where I can tap and select between "Charge this device", "Supply power", "Transfer files", "Transfer photos (PTP)" and "Use device as MIDI".
Has anyone ever had this issue? Phone hardware issue? Adapter issue? Software issue?
Click to expand...
Click to collapse
I am on my third device because of this issue.
https://productforums.google.com/fo...!msg/phone-by-google/-p-F-7Rgtak/zUay6YIZBgAJ
Massive thread about it, Google doesn't have a fix for it yet.
Restarting the phone/unplugging & replugging the adapter usually sorts it out for a little bit, Sometimes it won't stop doing it, Completely random!

Powereh said:
I am on my third device because of this issue.
https://productforums.google.com/fo...!msg/phone-by-google/-p-F-7Rgtak/zUay6YIZBgAJ
Massive thread about it, Google doesn't have a fix for it yet.
Restarting the phone/unplugging & replugging the adapter usually sorts it out for a little bit, Sometimes it won't stop doing it, Completely random!
Click to expand...
Click to collapse
It's so strange. It worked for me every time with no issue at all for like 6 months. Only recently did it start having a problem.
Since you are on your 3rd device with the same issue that makes me think it is a software bug not a hardware issue. Otherwise replacing it should fix the problem.
I think the last time I remember it working was late April or early May (hadn't even tried the adapter since then until about a week ago). So maybe a bug in either the May or June update?

I'm having the same issue here. It worked up to within the last month; I didn't notice exactly when it stopped as I'd been using bluetooth headphones more often. Left them at home one day and pulled out the backup USB-C cable for my QC-25 headphones and the phone indicated it was charging the headphones.
Some folks at the other thread said the Android 9 beta resolved the issue, but I updated to the 9 release a couple days ago and I still get the issue. FWIW

HoTWiReZ said:
I'm having the same issue here. It worked up to within the last month; I didn't notice exactly when it stopped as I'd been using bluetooth headphones more often. Left them at home one day and pulled out the backup USB-C cable for my QC-25 headphones and the phone indicated it was charging the headphones.
Some folks at the other thread said the Android 9 beta resolved the issue, but I updated to the 9 release a couple days ago and I still get the issue. FWIW
Click to expand...
Click to collapse
Seems to be resolved for me on Android 9...so far.

My aux dongle isn't the problem for me, I've gotten a replacement and it's still didn't work.

I've started facing the same issue from yesterday, is there any solution to this?

Android Auto not working for anyone as of yesterday?

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.

Android auto disconnecting

My pixel 3 xl will connect to Android auto via USB.... Work for a few minutes then randomly disconnect. Never happened with my pixel 2.
Any suggestions??...I have tried new USB cable.... Still does same thing.
Sent from my Pixel 3 XL using Tapatalk

I have had occassional issues with Android Auto as well -
When I first got the Pixel XL I was able to connect fine via USB and even wirelessly to my Kenwood headunit - but the other day, after connecting to Android Auto, when I tried to make a phone call, Blue Tooth was not connected and I could not get it to connect. I eventualy toggled on and off Airplane Mode - and after that
it connected fine. Havn't had an issue since (knock on wood)
for your situation, have you made sure that USB Debugging i turned off? It won't work with that turned on....

Same problem here.
Never had an issue with my Pixel XL, Pixel 2 or Pixel 2 XL. Yesterday I received my new Pixel 3 XL and Android Auto keeps disconnecting. Sometimes it does last a few minutes, sometimes it does so after a few seconds. It doesn't matter if an app like Spotify or Maps is being started or if I just connect the cable. Android Auto doesn't stop on the phone but only disconnects.
As you can't deinstall Android Auto I already tried wiping cache, wiping data and deactivate. I even tried three different cables.
When I connect my work phone Pixel 2 I don't see this problem. The connection is kept as usual.
I'm getting grey hair over this.

Has anyone found a solution or workaround for this issue?

I've tried absolutely everything, even rolled back to a nano SIM after started with an eSIM.
Gonna RMA this week and cross my fingers.

I wonder if it's a hardware issue or software. Unfortunately I don't have another phone that runs pie so I can't test it. My v30 running nougat works fine. I'm kinda waiting for the next pixel update to see if it fixes it.
If you do rma your phone let us know if that fixes the issue.

Turn off adaptive battery and see if that helps you

Nope, that doesn't help. As I mentioned I have every previous Pixel and all of them work flawlessly with my head unit. All preferences are the same.
There's only one obvious difference: Android Auto is pre-installed on the 3 XL.
Unfortunately I don't know anybody with Android Auto in the car nor owning a Pixel 3 XL to check out if it's something with my head unit.
In a German forum 2 people say they have it working properly...
One of the most frustrating parts is that - for me - it sometimes it works 10 minutes. After I switched back to nano SIM yesterday on my drive home I connected, listened to great music, whatsapped my wife that it is working and boom...disconnect and from then on the known behavior started again.

Did the new rma device fix the issue?

Just send it today and because I bought from provider I've a couple of days for the new one. Used my good ol' Pixel XL today working like a charme...
I'll update when the replacement has arrived.

Experiencing same issue with Pixel 3 non-xl and 2016 Honda Accord. Android Auto disconnects anywhere from 20 minutes to just seconds after I've connected.
I've tried the following:
-Variety of brands of USB-C > A cables
-Disabling all power saving options (whole phone, specific apps)
-Setting screen to stay on when charging (solved AA disconnect issues on my LG V20)
-Re-pairing bluetooth with car
-Re-pairing AA with car
-Resetting car head unit
-Resetting phone

I've had no issues with disconnects, but I use wireless connection with Pioneer headunit.

I got my replacement today and for now the problem looks to be solved but I only sat 20 minutes in the garage messing around with it but that are 19:50 more than my last attempt with the old one.
But I already installed both Android Auto app updates that came in the last couple of days.
/me is crossing his fingers
I'll drive about one hour in the evening and hope everything stays how it is now

It's a pixel 3 software issue. Big thread in the Android Auto support forums. Google doesn't seem to be in a hurry to fix it. Said the November update should, it did not.

Anyone ever find a fix for this? I'm having the same issue, but now cannot connect at all. (Was working. Stopped the car, went into Starbucks, came out and AA won't connect.) My Pixel 2 XL works fine, but I want to sell it.

Like I said I RMAd it and it works flawlessly ever since.

Android Auto Closing Out on Pixel 3
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?

Wahoodean said:
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Click to expand...
Click to collapse
My phone connects fine to AA. It stays connected with the cable. Perhaps try a new cable to connect it. I'm on stock rooted.
Sent from my Pixel 3 XL

Pixel 3 XL - bluetooth issues

So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!

JWhipple said:
So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
I've never had this issue before, even when I was on custom ROM. My Bluetooth works fine in car, at home, and with wireless headphones.
Sent from my Pixel 3 XL

I cleared out the bluetooth cache and storage then rebooted this morning - going to see if it makes any difference. Usually it takes a day or two before a device disappears after I re-pair with the phone. Unless anyone has any other suggestions I may do a factory reset in a few days if it happens again.

Not bluetooth but I did have all my saved wifi networks wiped after a reboot a few weeks ago. Oddly, I rebooted because my phone wouldn't connect to my Fitbit via bluetooth to sync. I rebooted and the screen was black, not responding at all. If I pressed the power button it would vibrate slightly as it does when the power menu pops up, but nothing else. After trying a few button combos I got it to reboot again and everything was fine except wifi networks were all gone.

Question Andoid Auto

Got my Fold 3 a few days ago. Got is setup and plugged it into my truc,k and my Android Auto unit reads "No Device'". My Note 10 works fine but not my new phone. My headunit is a Jensen (like I said, worked fined with my Note 10). The Fold3 works find in my Nissan (Pioneer head unit) and my Edge (factory Ford Sync).

Illusive Man said:
Got my Fold 3 a few days ago. Got is setup and plugged it into my truc,k and my Android Auto unit reads "No Device'". My Note 10 works fine but not my new phone. My headunit is a Jensen (like I said, worked fined with my Note 10). The Fold3 works find in my Nissan (Pioneer head unit) and my Edge (factory Ford Sync).
Click to expand...
Click to collapse
I am no expert here, but when I had a similar issue. I believe it is because I transferred everything from my prior phone to the new one. I got the same error when trying to pair my phone with wireless Android Auto in my Kia K5. My solution was to goto Google Play Services and clear the cache there. For some reason that allowed my phone to be found by my reciever. and worked. I didn't experince this with my new ZF3 but I did when I got my Note 20 Ultra last year. So try clearing the cache in Google Play Services.

Hey so try clearing the cache in the Google Play Services app. This worked for me when I had a similar issue with my Kia K5 going from Note 9 to Note 20 Ultra. I got the same error no device. This was going to a wireless head unit for AA. I finally figureout how to clear the cache in the Google Play Services app. Then went back to connect and it worked. Try this. It may work for the ZF3. Thankfully I did not have the same issue going from the Note 20 Ultra to ZF3. But this is what I would have done.

Thanks, man. I did that and to no avail. My phone is still not being recognized by my truck. When I press "Android Auto" on my head unit, I still get the message "No Device"

I'd flip cables for sure. Then I'd go to your setting when plugged in and make sure it's not set to charge only on the phone. Should be adjustable from the notification on charging.

I've having some weird issues with android auto and my fold 3. I've noticed when connected to android auto I often loose cellular data and it switches from 5g/lte/edge and no service. If I disable android auto the phone operates normally. Anyone else seeing anything similar.

Just a thought for OP. Did you happen to try opening Android Auto app in phone and checking to see if truck is an added vehicle and add if not?

The cable seems the most viable option. There is no option to select or deselect charging only, and Android Auto is no longer separate app. It is built into the OS and automatically opens when the phone is plugged into a headunit and there are no options to manipulate. The pain is that the dash has be pulled out to change the cable so I'll have to research a certified cable.

Did you buy chance to to settings > advance settings > then use Android auto there? Not sure if a setting in that will help. When I open it it wantsto attempt to connect to vehicle

Zugshad said:
Did you buy chance to to settings > advance settings > then use Android auto there? Not sure if a setting in that will help. When I open it it wantsto attempt to connect to vehicle
Click to expand...
Click to collapse
When I go there, I get the button to connect to a car, but when I plug the cable in, nothing happens and the head unti still displays no device. I'm thinking that I'm going to have to remove the dash and change the cable.

Illusive Man said:
When I go there, I get the button to connect to a car, but when I plug the cable in, nothing happens and the head unti still displays no device. I'm thinking that I'm going to have to remove the dash and change the cable.
Click to expand...
Click to collapse
Ah well unfortunately don't no more than that, just knew I saw an android auto option in there. My car doesn't support wireless and haven't tried the wired part yet to see

Well, removed the dash and head unit and changed the cable. I tried a Belkin USB-C certifed cable and even the known working cable from my other truck, and got the same thing.
On the phone I get the notification to stop my truck and apply the parking brake to continue and on the head unit I still get the notice of "no device" when I press the screen for Android Auto. At this point, I'm hoping I don't have to change my head unit to get this setup to work.

Weird mine worked just fine.
Did you make sure everything was updated

Yeah. I called Jensen they say it's a phone problem, Samsung says it's a Jensen problem

Got an email from Jensen customer service. My HU uses a bypass to allow certain functions while my truck is moving. I installed the HU myself and also installed the bypass. Jensen engineers found that I need to disconnect the parking brake wire from the bypass and connect it to chassis ground. I did that and was able to connect. I'm so happy to be able to use my phone in my truck.