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

[ponEpwr]

Good reminder that if you use PAAK that you should properly set up your door code and set a vehicle start code.

Sponsored

 

[EasyPass]

I have a Samsung S22+ ver. 14 on Verizon, and installed the Dec 1 Update package on Tuesday 12/17. Immediately following I noticed the PaaK Notification showing "trying to connect to your vehicle". I didn't have time to mess with it or think about it until today when I received the Ford email alerting to the "Software Disruption". I immediately verified that my programmed Door Sill Code and Backup Start Passcode on the tablet were still functional......they were. Seems this issue is strictly limited to the Android boundary.

I only rely on PaaK for the occasional convenience function, so this software glitch is a minor annoyance for me; unless the fix will become burn down all the existing configs and start over with PaaK. Then I'll be quite jacked about it! ?‍

 

[benk016]

FWIW I'm on version 14 (OnePlus 9 Pro) no problem with PAAK so far,

So far, it seems to only affect Samsung devices.

 

[Snakebitten]

I kept saying no to the update for the last couple of days.
Driving home from the office today and Sync pops up wanting to know if I want to connect to the phone.

Huh?

Looked down and sure enough the update was in progress. ?

Why ask if I want the update if you are going to install it anyway?

Sure enough. PAAK is dead. Rats!

By the way. S21

 

[garapatisri]

I received a similar email, but I do have Apple 15pro with iOS 18x. but still have the same problem. From last night the Sync between car , CCS and Phone is gone.

happened last month and go dealer fixed it and again resurface. I really hate this Software maintenance ....

 

[garapatisri]

So far, it seems to only affect Samsung devices.

Have it on iOS 18, 15pro max too.

 

[benk016]

I received a similar email, but I do have Apple 15pro with iOS 18x. but still have the same problem. From last night the Sync between car , CCS and Phone is gone.

happened last month and go dealer fixed it and again resurface. I really hate this Software maintenance ....

If your app and the website is not updating with info like charge level and climate controls won't work, that is another issue. The issue in this thread is only causing issues with fordpass Bluetooth connecting directly to the car.

 

[Blake Sacha]

S23 ultra running Android 14. December update broke my PAAK. Using key for now until someone identifies a reinstall fix that works. Walk up doesn't activate lights. Lock and unlock buttons work in the app but says no key detected. December security update.

 

[SteveMach-ee]

What's weird is i received a successful update a couple days ago, but now am scheduled for another on Saturday. Looking at my phone it shows I still have the November security update.

Would be interesting if you could look if you also are still on the November security update.

Same for me. Samsung S22+ with November 1st security update. OneUI update last week. PAAK works okay as it always has. Once in a while I have to unlock the phone to get PAAK to work.

 

[TikmTyler]

I updated S22+ yesterday and started having issues. I did find that BT off and on again worked for a moment but till I hear otherwise will be fob-ing it. Glad to know it was not me. When its not working and says "no key detected" its not very reliable to supply passcode instead or when it does, does not render the keyboard so I can enter it.

 

[CameraCarl]

I just got this email today just after 9 AM PST. I drove into work at 7 AM using PaaK with no issues. I haven't tried again since the message.

Edit: I just noticed the message says Android 14 specifically and not Android 14 or later. Since I'm on Android 15 (Pixel 7 Pro) this issue may not impact me or others on new version of Android.

I just got a notice to update my Pixel 6a to Android 15. If I do this I wonder if I can avoid this potential issue... Or if Ford will discover that there is a problem with Android 15 as well....

 

[PebbleMav]

I have a Samsung S22+ ver. 14 on Verizon, and installed the Dec 1 Update package on Tuesday 12/17. Immediately following I noticed the PaaK Notification showing "trying to connect to your vehicle". I didn't have time to mess with it or think about it until today when I received the Ford email alerting to the "Software Disruption". Seems this issue is strictly limited to the Android boundary.

Exactly the same experiences with my Samsung S23U.

 

[06VistaGT]

S23 ultra running Android 14. December update broke my PAAK. Using key for now until someone identifies a reinstall fix that works. Walk up doesn't activate lights. Lock and unlock buttons work in the app but says no key detected. December security update.

Same here on S23+. As another user said, restarting the phone got me enough time to unlock and start the car. Got "no key detected" shortly thereafter. Did not delete PAAK, but did uninstall and reinstall FordPass. It tries to setup PAAK, but no response from the car. The phone cannot find the PAAK BT connection from the car (the one with the last few digits of the VIN), nevermind connect to it. Fwiw, wireless Android auto works fine.

Using the FOB until this is resolves. I never did get an email.

 

[MachEmpanada]

Yup, I started having PAAK issues a couple of days ago on my Samsung S21. I'm glad Ford seems to be on top of fixing this issue ASAP. But until it's fixed, I'm carrying my FOB with me.

 

[Eraser]

I just got a notice to update my Pixel 6a to Android 15. If I do this I wonder if I can avoid this potential issue... Or if Ford will discover that there is a problem with Android 15 as well....

Unfortunately, the email was so broad in scope I suspect they haven't isolated the problem. Android 14 on Pixel isn't the same as a Samsung or OnePlus, etc. If you're not having issues on your Pixel on Android 14, I suspect you'll be fine on Android 15. I've been in and out of my car multiple times today and haven't had any issues.

Sponsored