Dec '24 Android Update - Bluetooth Connection Problems

[mattsaradan]

Switching Bluetooth off and on also doesn't work. Only fix is a phone reboot, which works for about 30 seconds. Gotta jump in and start the car!

Sponsored

 

[Snakebitten]

Yeah, I'm an older model Samsung and the current security patch is back in October.

PAAK is functioning just fine

 

[machguy22]

Can confirm, S34 stopped working with Paak today after yesterday's security patch. Get the same results, work briefly after the phone resets then stops. You can see it connect in the notification then loses connectivity with the car. Unfortunately, this one may not be on Ford.

 

[Electric Goat]

I also submitted a bug report on this on Tuesday.

 

[valfam]

Well add one more S24 user that PAAK stopped working. Like everyone one else AA works perfectly, I called Ford using Bluetooth in the car while the car was saying no key fob found. i can even open the door but the cars says no Fob found. What I don't understand how can I open the car with no key fob oh the lights do not turn on when I'm walking to the car.
I have deleted the phone from the car and readded it. No change. I reset the car now i can't readd my phone.

 

[lanebk]

I have the same issue after the December update. I have an unlocked fold 5. I'm using the ford pass beta, which updated today. I thought maybe that was the issue, but it sounds like it was the security update.

 

[valfam]

I hope to dedicate some time tomorrow and get this working again, im so glad it happed at home. It would be a serious problem if i was out.

 

[CarsIMBwife]

@Carsinmyblood is having the same issues with an S24 Verizon.

 

[JM22681]

I do think there was a change made at the app layer. My Bluetooth always used to show a MAC Address for the Mach-E (beginning with 90-CE-B8) instead of a friendly name in the list of Bluetooth connections. Now it is labeled as 5 random digits followed by MACH E (mine happens to be "86891 MACH E"). I am on Pixel 8 Pro and while it's been relatively stable I've seen more blips where a Bluetooth restart fixes it. I do wonder if 5.9.0 caused this because I had Android 15 on here right when it came out with the older version of the Ford app, and no issues up until very recently.

 

[valfam]

@Carsinmyblood is having the same issues with an S24 Verizon.

Im on T-Mobile and I'm having the same problem so I think it's every provider.

 

[CarsIMBwife]

Im on T-Mobile and I'm having the same problem so I think it's every provider.

I suggested he take his fob tomorrow ?

 

[wewinsor69]

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.

Yes, I'm having the same issue with BT. BT still works for things like playing music, but the BT that handles the Controls (windows, frunk, hatch) will not work. The app will let me start/stop/unlock/lock, but that's it. I've set it up as a required PAAK device; SYNC confirms it's a required device (I assume) by telling me the setup was successful...because then my center consol asks for a backup password, and that fails telling me no required devices found. That's the part that stumps me. Before getting there, it asked me to select a required device, which I did, but then says it can't find a required device. I have a case open with Ford on this issue. I spent 3 hours on the phone with Ford yesterday trying to resolve it. At one point, they had me do a full reset (not factory reset), and now 2 of my trial subscriptions are not showing up on my connected services....case with Ford on that too. Ugh. Hope it's fixed soon. Following this thread in hopes of good news.

 

[benk016]

Yeah it's definitely an issue just limited to fordpass and it's BLE implementation. Let's just hope that Ford can fix it with an app update and not have to wait for a January Android update and hope they actually address it.

 

[benk016]

I also received Fordpass beta 5.10.0 overnight and the issue remains.

 

[Art]

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

If anyone relies on using your phone to control the car, then DON'T.
Ford can't possibly be responsible for tracking all updates to your Android and Apple phones.
1. Use the FOB to control your car.
2. Use the phone with bluetooth. If it doesn't work on bluetooth, try the USB port. One or the other will work.
I have a four-year old phone that stopped working on bluetooth, so I used USB for two years.
Last week bluetooth inexplicitly started working. Was it a phone update or a Ford update that caused this change. Who knows?
Try work arounds before posting.

Sponsored