Hello all. Since updating to Android 13 Beta 2 on Pixel 6 Pro, my Hyundai Santa Fe is having issues connecting to GPS. If I connect my phone and open Maps, I get an audio message "cannot connect to GPS". If I disconnect my phone and open Maps on phone and then connect it to my car, Maps connects to GPS fine on car's unit. Anyone else facing this issue? Any solutions?
Related
I have a Captivate (i896) running CM9 (the latest nightly build) and am enjoying CM9 immensely. The only problem I have with it is that the Bluetooth will not automatically connect to devices that it is already paired with.
Here is an example, I get in my car and the car tries to connect to the phone but cannot, even though bluetooth is on and ready to go. It will connect if I go into the bluetooth settings on the phone and tell it to connect. If it helps, it is the Ford sync system in the car. I am having the problem though to varying degrees with any bluetooth device.
Any thoughts?
Hi,
After several months using AA in a Golf MY16 with two different smarphones with Android 5.0 & 5.1, using different AA releases, then I have found one "use case" when the AA "fails" (=disconnects from the HU):
* When you're driving inside a tunnel and the car's GPS losses the signal, in this case the AA *always* disconnects from the Head Unit.
Did you have a similar experience?
Hi,
No one with similar behaviour? :silly:
No problem with my 2016 Jetta. Google Maps says me that GPS signal was lost but there is no error. Are you sure it's using the car GPS ? I find it is not very accurate at some places.. Which phones do you use ? I found Marshallow more stable than Lollipop with Android Auto. I had connection drops with 5..1.1 but it was random and not related to GPS signal lost. No problem at all with 6.0.
marcjero said:
I found Marshallow more stable than Lollipop with Android Auto. I had connection drops with 5..1.1 but it was random and not related to GPS signal lost. No problem at all with 6.0.
Click to expand...
Click to collapse
Thank you for the report! I'm using Lollipop 5.0 & 5.1 in two different smartphones. I'll check with some spare MM 6.0 when I have time.
:good:
you are welcome.
It seems that Android Auto is using the phone GPS (at keast with the VW head unit) Just try to disable the phone GPS before connecting the phone to the car and start Maps : you will be asked to enable the GPS. Really sad.
Hi,
If it's true that AA is using internal (phone) GPS instead of car GPS (almost in a Golf MY16), then the problem can be when the PHONE losses the GPS data... Even, I feel the real problem is: the phone likes to say "GPS disconnected" and the disconnection ocurs because some trouble exists with the audio output.
I also detected that sometimes when a WhatsApp is received, also the AA is disconnected. I hope Google can fix this trouble with the "AUDIO OUTPUT".
You have a similar problem?
manos78 said:
Hi,
If it's true that AA is using internal (phone) GPS instead of car GPS (almost in a Golf MY16), then the problem can be when the PHONE losses the GPS data... Even, I feel the real problem is: the phone likes to say "GPS disconnected" and the disconnection ocurs because some trouble exists with the audio output.
I also detected that sometimes when a WhatsApp is received, also the AA is disconnected. I hope Google can fix this trouble with the "AUDIO OUTPUT".
You have a similar problem?
Click to expand...
Click to collapse
Yes I got something similar when trying to run Waze in the background. Waze audio notification made the connection drop. It was with 5.1..1. I can have a try with Marshallow.
UPDATE : no problem at all with Marshallow (CM13) : I was able to run Maps and Waze at the same time. Got Waze audio notifications. No USB connection drop. The only issue is my Nexus 4 did a shutdown because it was overheating but it's a common issue with the Nexus.
marcjero said:
UPDATE : no problem at all with Marshallow (CM13) : I was able to run Maps and Waze at the same time. Got Waze audio notifications. No USB connection drop. The only issue is my Nexus 4 did a shutdown because it was overheating but it's a common issue with the Nexus.
Click to expand...
Click to collapse
Thanks for the info! :good:
I suspect the problem is then related to the audio route inside Android 5.x
Hi,
More info:
Using Android 5.x, VW Golf MY2016 with CAR GPS, and last AndroidAuto App, the GPS signal is comming... FROM THE PHONE! So, yes, VW is not sending GPS signal to the AA process. In this case, when the phone losses the GPS signal, the AA process crashes. This is then the problem in my system: when GPS signal is lost inside a tunnel, then the HeadUnit disconnects with the AA process.
I hope Google fixes soon this problem. Also, I hope VW can upgrade the MIB software for sending ALL car data (including GPS position and ORIENTATION) to the AA process.
Regards.
And hope a droid will accept that data.
Sent from my SM-T520 using Tapatalk
Nova5 said:
And hope a droid will accept that data.
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
Yes I'm afraid AA is too much complicated. It crashes for many phones. Manufacturers doesn't implement all the features but imagine you have to build a head unit with GPS, Car Play, Android Auto, MIrrorlink... and all these subsystems (that does the same job : screen mirroring) have to send car and gps data to phones. using all the protocols. That's just crazy. And when it works you get frustrated because of usage limitations.
Hi guys!
I have a Nexus 5 and a Golf Sportwagen 2016 with android auto and it works great! But there's a problem.
When I disconnect my phone after I used android auto, it won't reconnect automaticly (even after the car stopped and restarted) with the bluetooth. The radio sends this message : Do you want to etablish connection with Nexus 5?
If I say YES, it tries to connect to the nexus 5 but need (again) to confirm the passcode on the cellphone. It is very anoying! So each time I use android auto, I have to re-pair my Nexus 5. Do you know why?
Thanks for helping me!
yaaa4
Mine had an odd hidden permission when I first set mine up earlier this week, add it as a trusted device and this should solve the re-auth every time!
Hi everyone,
I have a problem with my Mi9 together with Android Car.
If I connect my Mi9 via USB-C to the car the GPS signal breaks down and also Google maps goes into offline mode.
I have a VW Passat B9 and my Mi9 is on MIUI 11.0.6 stable (Android 10).
With my second phone Samsung Galaxy Note 10+ the setup is working fine...
Looking forward to some tips or tricks.
Kind regards,
Lucas
Has anyone experienced bluetooth issues since yesterday's (January patch) update? My device remains connected to my watch, but refuses to connect to my car audio. I hope I'm not left waiting until February for a potential fix.
Pumpino said:
Has anyone experienced bluetooth issues since yesterday's (January patch) update? My device remains connected to my watch, but refuses to connect to my car audio. I hope I'm not left waiting until February for a potential fix.
Click to expand...
Click to collapse
Exact same problem here, Pixel 4a (not 5G) from Italy and Ford Focus MK3 2011 bluetooth. Everything OK with my Galaxy Band 2 but the car connects and disconnects continuosly. I unpaired the phone and then I wasn't able to reconnect until I disconnected car's head unit fuse (the car won't give me the PIN for connecting). After the reset I was able to connect again wit the Pixel 4a, but it showed the same loop of connections/disconnections. Tried with a Nokia 4.2 and everything works, so January update must have messed something with the "old" Bluetooth standards
bandagufo said:
Exact same problem here, Pixel 4a (not 5G) from Italy and Ford Focus MK3 2011 bluetooth. Everything OK with my Galaxy Band 2 but the car connects and disconnects continuosly. I unpaired the phone and then I wasn't able to reconnect until I disconnected car's head unit fuse (the car won't give me the PIN for connecting). After the reset I was able to connect again wit the Pixel 4a, but it showed the same loop of connections/disconnections. Tried with a Nokia 4.2 and everything works, so January update must have messed something with the "old" Bluetooth standards
Click to expand...
Click to collapse
I'm glad it's not just me then (I mean that in the nicest possible way). I unpaired my phone from my Toyota Camry too and when I attempt to pair it, the phone says it's connected but the car remains searching. I tried with my Galaxy S21, and it worked fine. I'd also used the 4a 5G in the car an hour or two before installing the update, so I'm confident that it's the update that broke it.
I don't know if I should wait a month (which is annoying, as it means no music, Google Maps or phone calls through the car audio), or flash a custom ROM. Not having it work for (at least) one month is pretty bad.
Exactly, pretty bad. I chatted with the Google Pixel help and they told me to reset the phone connections and retry. I've done it (VERY annoying because it also resets ALL the Wi-Fi stored passwords and unpairs every Bluetooth device on the phone). I'll try to pair it again with the car when I'll go home later and I'll let you know
Nope, even after the reset of all phone's connections the behaviour with my car remains unchanged. Let's hope that February update fixes everything
bandagufo said:
Nope, even after the reset of all phone's connections the behaviour with my car remains unchanged. Let's hope that February update fixes everything
Click to expand...
Click to collapse
I might look into whether other Pixel models are impacted, too. I'll let you know if I find out anything.
Some Google Pixels are failing to connect to in-car Bluetooth after installing January's security patch
No, it's not just you — some Pixel owners are experiencing Bluetooth connection issues after updating to January's patch
www.androidpolice.com
The Pixel's January software update has broken auto Bluetooth pairing for some
Some Pixel owners are experiencing an issue with Google's latest software update that is breaking auto Bluetooth pairing.
www.androidauthority.com