Google Pixel bluetooth dropping during calls

[Mouss]

Hello. Anyone facing Bluetooth droppings during calls with a Google Pixel, and with which model please?

I got an issue with my old Pixel 7, my old pixel 8 Pro and now, Pixel 10 Pro XL. Every 2 or 3 calls, when I take or make a call, Bluetooth drop for no reason and if there is 2 sceneries: my caller heard a loud sound or nothing and the call stop, or the call revert to my Pixel and I have to take it, choose device phone, and choose Bluetooth (MG4) to get the call back to my phone.
It's really annoying and nothing fix this. I got the TBOX swapped in 2024, I got all updates from dealer and no fix yet. Now, I'm running MPU R67 and nothing seems to fix it.

I found someone else who face the same issue with a Pixel 8 and I found a lot of car onwer who have the same issue with Range Rover, and other brand. Fun fact: I got the same with my wife's Samsung S24+ and the guy who has the same issue used to have a Samsung and never got that. It started with his Pixel 8.

I don't know if it's a Pixel issue (I tried everything: reset, WiFi and Bluetooth reset...) or it's a manufacturer issue with infotainment and Pixel devices.

If anyone have the same and could share his observations, it would be nice.

Thanks.

PS: I have an MG4 Luxury MY2022 (EU version of Trophy) running SWI68 build.

 

[Jamesrr]

Sorry but I've never experienced anything like that with either my old Pixel 9 Pro or current Pixel 10 Pro.

I connect Android Auto via a cheap AliExpress wireless adaptor.

My car is the Australian version of the UK Trophy Extended Range known as the MG4 Long Range 77 here

 

[Mouss]

Thanks for feedback. Which build do you have (Australia build are different)?

 

[Jamesrr]

Thanks for feedback. Which build do you have (Australia build are different)?

Yeah, the numbering schemes are different AFAIK.

Mine is SWI165-29176-1100R11
Telecoms ver SNAKP0432A

It was installed on 26-10-2024

I've never bothered even asking them to update it. It works well enough that I really can't be bothered and MG Australia don't even provide a fixed quote "upgrade" cost. A bit pathetic but that's how it is.

My version has not too aggressive LKA/ELK. I never bother turning it off around town. I mostly bother on long country drives, but not always.

It has the "pull down" menu that lets you disable ELK with only a few taps.

It remembers the sensitivity settings (which I have set at 1) and the regen settings, which I set at 3. I have audible alarms muted where possible. It doesn't remember OPD, but I find 3 more than adequate.

 

[Tight Git]

No problem with my last or current Pixel (9 pro) - your issue sounds like it's the car that is the problem which will need a software update to sort (possibly also the Tbox).

Lots of threads about this issue...

 

[Mouss]

The TBOX doesn't manage Bluetooth connection for calls and it's up to date. Ad i Said, my car is fully updated...

 

[Tight Git]

The TBOX doesn't manage Bluetooth connection for calls and it's up to date. Ad i Said, my car is fully updated...

Sorry had realized it was you with the issue as I know you are on top of all the car updates!

 

[STG]

I have BT troubles for 2 years of having the car. First was my apple XR Pro, so changed to Pixel 7a which was a bit better but still usless.
Then got a AA wireless box which worked great for months and then it started to play up and my phone kept getting spammed with BT pairing requests (like 20 a minute). Tried deleting everything from BT on phone and car but it was a never ending story of more requests than I could delete.
So ditched the AA wireless and don't bother connecting the phone anymore.

 

[Mouss]

I used to have Bluetooth pairing request but it was fixed since I get R67 software for infotainment.

My issue here isn't pairing, but Bluetooth droppings. My Pixel and my MG4 stay connected but for some reason, I got one or several droppings during phone calls.

 

[scal]

You're not alone, Mouss. I’m seeing the same issue. Pixel 9 and MG4 Trophy ER here, still on R46.

I normally use Android Auto through a cheap wireless adapter, and I still need to test whether the problem also appears when connected via cable. Even though the issue is clearly Bluetooth‑related, these adapters seem to initiate and mediate the Bluetooth connection, so it might be worth checking.

For me, the first sign is when the green disappears from the top bar and the then black bar claims the call has ended. Switching the audio output away from Bluetooth and then back again in the Android Auto call app brings it back… until it drops again. I also have the impression that braking often triggers it. It doesn’t matter whether it’s a normal mobile call or something like WhatsApp, but it is limited to Bluetooth calls only. No issues at all with music via Android Auto.

 

[Mouss]

This is exactly what I'm facing (except for the trigger), I have droppings even with WhatsApp or same king of app (Snapchat, Messenger, Google Meet).

When the green calling bar disappear, I know something went wrong. And it's happened too by Bluetooth or by wire with Android Auto, or threw the wireless adapter...

 

[Mouss]

Nobody else use a Google Pixel Phone with MG4?

 

[Spaniard]

I have got updated to R73 a couple of weeks ago (after suffering a year of constant pairing requests in R61).
Pixel 7a here, and I indeed had one BT drop in the middle of a call so far with all the symptoms you have described. Will pay more attention to circumstances in future calls to try to find some contributing cause.

 

[Rom]

I've used a pixel 8a, 9 and currently 10 pro. I get the odd call drop, but I think it's when I'm leaving my office and I go out of Wi-Fi range.
The 8a and 9 were a disaster for me with connection issues but the 10 pro is pretty stable so far.

I found the most reliable way to connect is...

Forget the car in your phone settings.

Delete the phone in your car Bluetooth settings+swipe left and choose remove device.

Clear cache and data for Android Auto.

Restart your phone.

Connect your phone to your car with USB.
Android Auto will pair your phone on first connection, accept the pairing request.

Make sure to give contacts and any other permission in the cars Bluetooth settings and on your phones Bluetooth.

I think the main problem for me was I paired my phone to my car before connecting to Android Auto. Doing this, it gives the phone, and the car, two separate identities but they have the same name so I kept getting Bluetooth pairing requests and failures until I only connected by USB and paired using Android Auto.

Calls are more stable too, but not 100% issue free. I do pass areas with signal issues though so I can't fully blame the phone or car.

I'm on the R63 software.

 

[Mouss]

Thanks for your message.
But I think you mostly talking about Bluetooth pairing issues than Bluetooth drops.

I got the same issue until R67, all MG4 could get this odd thing of multi pairing, it's a Bluetooth Mac address issue. For SE/SE ER MY2022 and 2023 (EU/UK), it was fixed with build SWI69-29958-1100R40. For Trophy, it's build SWI68-29958-1300R67.

Since I get it, I never experienced any Bluetooth pairing issue but I still get Bluetooth dropping during calls. It's subtle but quite annoying most time it happen

 

[Rom]

Thanks for your message.
But I think you mostly talking about Bluetooth pairing issues than Bluetooth drops.

I got the same issue until R67, all MG4 could get this odd thing of multi pairing, it's a Bluetooth Mac address issue. For SE/SE ER MY2022 and 2023 (EU/UK), it was fixed with build SWI69-29958-1100R40. For Trophy, it's build SWI68-29958-1300R67.

Since I get it, I never experienced any Bluetooth pairing issue but I still get Bluetooth dropping during calls. It's subtle but quite annoying most time it happen

It was probably a long shot, but I think trying to make sure there's only one Bluetooth connection to the car for the same device might help slightly.