PSA - Phone as a Key Disruption on Android Devices (12/19/24)

[mattsaradan]

I wonder if it's related but the fordpass app on my Galaxy Watch 6 crashes instantly now when I try to open it. Had worked properly since release until about the time I got the december security update on my phone.

Interesting. I'm having the same experience. Not sure the two problems are related though.

Sponsored

 

[Snakebitten]

PAAK could be 100's, or even a few thousand lines of code in FordPass.
Imbedded in that code are probably multiple properties and parameters spelled out for leveraging the Bluetooth LE protocol.

The Bluetooth hardware on the 3rd party device is obviously not Ford. Nor is the OS and security software on the device.

PAAK and FordPass still function properly on Motorola, Google, and even many Samsung devices. But obviously something in the latest Android 14/One-UI Samsung security patch is not playing nicely with the FordPass Bluetooth LE protocol code stack. And according to those affected, it seems that the Bluetooth LE connectivity with the Mach-E actually succeeds, but only momentarily, and then disconnects.

It's anyone's guess just what parameter or property or code snippet that Ford would have to address/edit to make FordPass PAAK just as compatible with the Mach-E as it appears to be with the Lightning. And I personally believe that it's quite possible that some folks in the development staff already have a clue what is different between the two vehicles PAAK coding. (whether it is code in the firmware of the hardware onboard the vehicle, or elsewhere)

I don't know if Samsung would be compelled to alter their security software just to accommodate the tiny fraction of Samsung smartphones their patch caused this problem for. They may well be willing to "work with" Ford to identify the portion of the security code that stepped on FordPass's existing Bluetooth LE failure.

 

[emichnov]

And according to those affected, it seems that the Bluetooth LE connectivity with the Mach-E actually succeeds, but only momentarily, and then disconnects.

So is this really a Bluetooth connectivity issue, and that is what is causing the problems? I noticed that not only PaaK no longer works on my Samsung S23, but Bluetooth doesn't connect anymore either.

 

[Snakebitten]

So is this really a Bluetooth connectivity issue, and that is what is causing the problems? I noticed that not only PaaK no longer works on my Samsung S23, but Bluetooth doesn't connect anymore either.

So you can't make Bluetooth handsfree phone calls, nor stream music and such?

Or are you talking about the FordPass Bluetooth functions?

FordPass Bluetooth functions for the Mach-E are all riding on the LowEnergy connectivity, if I'm not mistaken.

 

[emichnov]

I'm talking about the FordPass Bluetooth functions. Fordpass no longer seems to connect to the car through Bluetooth. Paak doesn't work either.

 

[Dan the Man]

So you can't make Bluetooth handsfree phone calls, nor stream music and such?

Or are you talking about the FordPass Bluetooth functions?

FordPass Bluetooth functions for the Mach-E are all riding on the LowEnergy connectivity, if I'm not mistaken.

I believe you are correct I think the functions on the Ford pass for the car controls are on low energy. My Bluetooth connects to sync so Android auto is working.

I bought a Garmin launch monitor for golf. The launch monitor would not connect to my Samsung s22 (at this time I did not know about the Bluetooth security patch issue) . Looking at the Bluetooth connectivity it looks like these were also LE functions. I called Garmin and we could not figure it out for the hell of it I had an older phone (LG) and I loaded the app onto that phone and it worked. The strange thing is after I I try to connect it again to the Samsung s22 and it connected. Very weird.

I was in IT for over 30 years and when you have systems interacting with other systems any little change can just screw up many things.

Since the phone is not connecting to the machine software and it had a hard time connecting it to the Garmin launch equipment I think Samsung will address the issue because my guess is that other devices that are using LE Bluetooth connectivity are not working with this new security patch

Happy New Year!

 

[Glen Boise]

This problem may not be on just Mach-E's. A friend with a recently delivered Chevy Equinox(?) complained about similar problems with his Samsung cell phone not connecting to his new car.

 

[Snakebitten]

If the recent security patch is breaking LE functionality on multiple "devices", then no doubt Samsung will be pressured to address the solution themselves.

And that certainly supports the theory that this wasn't an oversight or failure on Ford.

 

[rboettcher]

Interesting. I'm having the same experience. Not sure the two problems are related though.

Same problem with my 7 Pro. Worked fine until the security update that killed my PAAK. ?

 

[Mosworthy]

Just got the new 14 update yesterday on my S22+
No PAAK today...
Gotta go find the fobs I stashed away 4 years ago

 

[Paisano]

Well, I'm done with AA. Samsung failed big time with this so much, I turned it off. I do miss the features but do not miss the intermittent drops, locks, and connections issues.

 

[benk016]

Well, I'm done with AA. Samsung failed big time with this so much, I turned it off. I do miss the features but do not miss the intermittent drops, locks, and connections issues.

The issue in this thread has nothing to do with android auto. That still works normally.

 

[Paisano]

The issue in this thread has nothing to do with android auto. That still works normally.

Well Ben that's the problem. I've been troubleshooting everything to do with Bluetooth, Paak, AA and i can't find a common denominator so I can't say what sub system is causing the issues. It could be a basic communications bug on the Samsung Galaxy, could be handshaking between them, could be version and software updates, might be settings issues, or wireless (although my issue persists with wired connection). Mach E might have nothing to do with it. So PAAK disruption on Android could very well be the same foundational issue. Sorry for the ramble but I'm pissed that i have a beautiful car and can't use AA consistently.

 

[Teslawho]

I have same issue and wrote a review on Google play store. Ford commented and told me to go through the help section within the Ford pass app to troubleshoot or to call directly. Luckily cars at Ford getting the windshield wiper recall fixed but once I get it back I'll try to reach out to them.

 

[Dan the Man]

As I said before Bluetooth Android auto works fine. I believe the problem is with bluetooth LE (low energy) protocol.

I did see another member had this issue on a non Samsung phone. With that said I don't believe it is phone specific or for that matter Android operating system version. Specific It's the new version of Bluetooth that is causing the problem.

Just my two cents.

Sponsored