On my 2022 BMW iX, i keep getting a connection failed error, "check Bluetooth & WiFi settings".
It is very strange because the same phone connects flawlessly on a 2020 BMW x7 and also other cars which support wireless AA.
Similarly, i tried other phones to connect to the iX, and they also get connection failed error.
I contacted BMW, they said its because AA isn't officially supported in this region (Qatar), while I checked Google's website and it is true, Qatar is not listed in supported countries, it still doesn't make sense because I am able to use it just fine on many other cars. The issue is only the iX, and BMW is assuring me the issue is with Google and not supporting it in this region. Can this be true?
While it is not officially supported, it works on some cars ( pretty much all cars which have it enabled) except a newer 2022 model BMW iX?
All this time i thought AA was officially supported, otherwise how has it been working for so many years and still working on my other car.
Related
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
Can you guys test the bluetooth and tell me if the pairing bug is still present, under certain circumstances? I've been waiting for bluetooth to actually work properly via OTA's but so far nothing's been done.
The issue is:
On most newer bluetooth devices (2012+ car stereos, A2DP headsets/speakers, etc), the bluetooth will pair both the A2DP and HFP/HSP profiles just fine, at the same time, and if for some reason one or the other doesn't pair immediately, then they will link up within a few seconds of each other. However, I've tried to use bluetooth on my Pioneer Premier FH-P800BT, my bluetooth 99% of the time will only pair the HFP/HSP and not A2DP, and then when I try to pair up just the A2DP portion (or it tries to autoconnect) it fails out and my Moto X gets stuck on connecting, and won't ever leave this. I can manually pair the 2 devices EVERY time I turn the radio from off to on, but it's a pain and sometimes, even that doesn't work. Other users have had this issue with other car stereos and other bluetooth hardware, so I'm anxious to know if this is present. I wish I would've bought the Dev edition for Verizon because now I'm having to deal with a problem that I could've fixed, if I had an unlocked bootloader (missed out on the Chinese middleman)
Absolutely no issues here with linking on my Ford SYNC or KIA UVO, OEM systems.
So it was announced today at Google I/O that Android Auto is going to be updated soon to be able to function over Wi-Fi. My 2015 Hyundai Sonata has a Wi-Fi connection. I can connect to any hotspot that I want. So, my question is do you think that the automaker will actually have to support this functionality and make some change in the car or is this all done on Google's side? Obviously, if the car maker has to make a change to support this then I'm guessing it is highly unlikely that existing car models will be updated to support this.
i wonder how it will impact audio quality
Hi there,
i use a Kenwood Headunit (8019DABS) and Wireless Android Auto. After changing my network provider (moved to a better network) I can't reply or send messages anymore using Android Auto. It keeps saying "the network connection isn't strong enough" (I don't know the exact term in english because I hear it in german). On the other hand it reads my messages flawlessly and i can perfectly ask Google playing any Spotify song - so voice commands work in theory. Also i am constantly streaming and I have a great 50MBit LTE connection. So really no issues of the network.
First I thought it might be a problem with the phone or the android auto app beeing messed up but even with a completely new phone the message doesn't disappear. So reinstalling Android Auto or Google Play services wouldn't be a solution.
What the heck occurs this? How can I prove Google my internet connection is great?
Thanks
Odd. The Kenwood UK product page doesn't say that unit support Wireless AA, only wired (it does say it supports Wireless Apple Carplay and wireless Android mirroring). https://www.kenwood-electronics.co.uk/car/nav_mm/carplay-mm/DMX8019DABS/
What does it do if you use a wired connection?
I have this problem also.
Did you found a solution?
It worked again without me doing anything.
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