Dec '24 Android Update - Bluetooth Connection Problems

[JHawk4Prez]

Anyone else having issues with Bluetooth connectivity after updating Android this month?

My OS updated this morning after driving to work. Go out this afternoon and PaaK will not work. I restarted my phone and BT connected and Android Auto works just fine. Get home and attempt to start the car again...same thing, phone is "connecting" and will not start the car. Restart again, connects long enough to start the car and then "connecting" again. AA works the whole time, phone shows BT connected to car, nothing else affected except for automatically unlocking and then starting the car. Really frustrating and almost got stuck at work this afternoon. Pics below of FordPass screen and Android info.

Sponsored

 

[benk016]

I have an S24 ultra just had an update a few days ago with no issue.

It appears I already have another one with that security patch level. I'll apply it now and see if I have any issues after and report back.

 

[RickMachE]

This is why people shouldn't rely on PaaK. Through no fault of Ford, an OS update hoses it.

 

[benk016]

Yeah I'm getting the same thing after the update. I'm in the beta program for fordpass and going to submit the bug report now.

 

[JHawk4Prez]

Yeah I'm getting the same thing after the update. I'm in the beta program for fordpass and going to submit the bug report now.

Thanks! Appreciate the info!

 

[benk016]

Tried deleting the paak setup, and reading it. It shows connected for about 30 seconds and then loses connection and can't reconnect.

 

[cgorske]

Yep, I have a Galaxy S24+, and I got the security update last night, and now my PAAK isn't working today. Hopefully there will be another phone update to fix what they broke, or maybe Ford will release an update to FordPass to work around whatever Android did.

 

[JHawk4Prez]

Tried deleting the paak setup, and reading it. It shows connected for about 30 seconds and then loses connection and can't reconnect.

Tried the same, with the same results. Connects just long enough and then shows "connecting".

 

[ShawnMakie]

Yes, same issues here on my Galaxy Fold 6 after the December uldate.

Thankfully restarting the phone let's it temporarily start the car because today the Sync screen asked for the password to start the car, but wouldn't pop the keyboard so I could type anything... Thanks Ford.

 

[Snakebitten]

Is this update for all carriers?
I thought I read somewhere it was a few folks with Samsung Galaxy 24's and they were all Verizon.

But I see now that it's not just the Samsung/24/Verizon?

I'm still good. But an older Samsung and not Verizon.

 

[zhackwyatt]

Ever since Android 15 on my Pixel 7, I've had to restart Bluetooth to get it to work. I don't have the Dec update.

 

[JHawk4Prez]

Is this update for all carriers?
I thought I read somewhere it was a few folks with Samsung Galaxy 24's and they were all Verizon.

But I see now that it's not just the Samsung/24/Verizon?

I'm still good. But an older Samsung and not Verizon.

I'm T-Mobile. Galaxy S24.

 

[Skip Towne]

YES! I've been very happy with FordPass for years (early days, not so much ? ) And now this.

I've been locked out twice in the past two weeks, but both times restarting the phone worked- temporarily. And, as you point out wireless AA works and cellular connections all seem OK (Remote start etc)

In my case, I had just updated the Android OS on my S24+ and the FordPass app, so I couldn't figure out the culprit.

But before we throw the Android OS update entirely under the bus, I'd note that I have a number of BT items thta connect to my phone - watch, headphones, various audio devices, other carts etc) NONE of these other users of a BT connection to my phone are experiencing a problem after the update.

This seem painfully reminiscent of the early FP unreliability issues, which I recall were at least in part related to BT issues thta were fixed by an update to both the car and the FP app.

Just when you thought you didn't heed to carry your FOB...

 

[benk016]

Is this update for all carriers?
I thought I read somewhere it was a few folks with Samsung Galaxy 24's and they were all Verizon.

But I see now that it's not just the Samsung/24/Verizon?

I'm still good. But an older Samsung and not Verizon.

It may be limited to just any Samsung device. I have an S24 Ultra on ATT, but the unlocked variant of the phone.

 

[mattsaradan]

This is on a couple of threads. I don't think it matters what carrier but it does seem limited to the latest security update on Samsung S24 series phones, maybe other current Samsung phone models. Not all Android, not even older Samsung (although those may not be getting the most recent security patch anyway). All having same experience - BT connection for PaaK works about 30 seconds after phone reboot and then disconnects, shows "connecting" endlessly. Seems like the car and phone still recognized but something in security update kicking in and preventing handshake completion. Wonder if there is a way to roll back the update? Hopefully a fix from Ford or Samsung soon.

Sponsored