FIXED - PaaK Broken on Google Pixel January 5 Update - APPLY FEB TO FIX

[JM22681]

Feb update definitely fixed it. Working for me now. I'll update the thread title.

Sponsored

 

[Free-Roaming]

As JM22681 suggested, I also deleted the old PaaK from the car rather than the phone. To review the specific steps, go to FordPass, scroll down to Settings, select Phone as A Key, scroll to the bottom of the page to the Resources section and select the Reset Instructions menu.

 

[DeusEx]

The annoying part is that you have to remove Paak and then add again. Once added, restarting phone or turning Bluetooth off and on still maintains your Paak.

For reference, you may need to do the below:

In Ford Pass, vehicle, settings, phone as a key, delete the key for your Pixel.

In your car, click on the car icon, phone list, click trash bin for your phone.

Then click the profile picture in top right of the screen. Click pencil icon, select unlink phone.

This should remove any remnants of a Paak registration. After all that start the process to link phone again from Ford Pass.

 

[phil]

Feb update definitely fixed it. Working for me now. I'll update the thread title.

I confirmed this with my own half-assed testing.

Thanks for letting us know!

 

[fpasta]

Mine doesn't connect anymore. It WAS working. The best I can get it to do is show the car available to pair.(This is after setting up key phone). When I try to pair it it just thinks for a bit and the "# Mustang" just disappears.

 

[Eraser]

I installed the February update, deleted the PaaK from FP app, then re-added it. Connected back perfectly and still works fine even after rebooting. Happy to discover my original expectations were wrong. I'm honestly shocked it fixed the problem, I guess Google was the culprit this time.

 

[GrayWolf]

Mine doesn't connect anymore. It WAS working. The best I can get it to do is show the car available to pair.(This is after setting up key phone). When I try to pair it it just thinks for a bit and the "# Mustang" just disappears.

Assuming that you are using a Google Pixel phone - please update to the February 2025 build of the OS. This has proven to resolve the issue for folks who've been posting to this thread (myself included).

 

[MetalCord]

I got the February update last night. This morning, I deleted PaaK from the Ford Pass app, set it back up, then rebooted and tested. PaaK is working for me again. I have a Pixel 6a.

 

[bbhaag]

Here is one more confirmation that the February update fixed whatever the January update broke.

I used the instructions listed in FP to reset PAAK on my P7P and so far it is working again. After multiple phone resets and toggling BT on and off my phone is still able to connect to the vehicle.

 

[hartmms]

Also can confirm the Feb. Pixel update on my 8 pro fixed this issue.

 

[Snakebitten]

This thread echoes the same exact scenario that took place 30 days prior with the Samsung Galaxy series phones.

December Samsung security update breaks PAAK
The affected mostly calls foul on Ford.
January Samsung security update fixes PAAK

Immediately following in Samsung's wake, Google's January security update breaks Pixel PAAK
The affected pretty much ignore the identical play by play and demand Ford to acknowledge and fix the Pixel issue.
Google's February security update fixes Pixel PAAK.

Thank goodness LG exited the market. ???

 

[hack-e]

I too got the Feb 2025 update on my P9P and confirmed that PaaK works now after a reboot. I want to attribute the fix to the Android update but I also noticed that my FordPass updated to 5.12.0. So I cannot tell if just one or both fixed the issue.

 

[DeusEx]

I too got the Feb 2025 update on my P9P and confirmed that PaaK works now after a reboot. I want to attribute the fix to the Android update but I also noticed that my FordPass updated to 5.12.0. So I cannot tell if just one or both fixed the issue.

It's the Feb update. I'm still running Ford Pass 5.11.

The one annoying thing I can't seem to fix is getting the car to recognize my profile settings when the phone is linked to my account. Paak keeps defaulting to weird settings, mirrors stay folded when I open the car, and my seat keeps needing to be adjusted back to the 1st profile setting.

 

[JM22681]

Assuming that you are using a Google Pixel phone - please update to the February 2025 build of the OS. This has proven to resolve the issue for folks who've been posting to this thread (myself included).

Agreed!

It's the Feb update. I'm still running Ford Pass 5.11.

The one annoying thing I can't seem to fix is getting the car to recognize my profile settings when the phone is linked to my account. Paak keeps defaulting to weird settings, mirrors stay folded when I open the car, and my seat keeps needing to be adjusted back to the 1st profile setting.

I've noticed some of the same behavior. I think that may be a FordPass 5.11 thing. I am now on 5.12 and it's a bit better.

 

[sockmeister]

Just a quick note that I encountered this too, but it was resolved (P6Pro) simply by removing/re-adding the FordPass key. I did not install the February patch yet.

Sponsored