FordPass 5.10.1 destroyed Paak for me

[JCHLi]

I saw one other report if this in another thread, wondering if we are the only ones to have issues. Update came early morning, today Paak didn't work. I know many people have issues but I've used it for 4 years with no major issues (can be slow or require a phone restart occasionally but I always get it to work).

Sponsored

 

[Strykerwsu]

I didn't have time to restart phone to test but after updated PAAK didn't work for me either. Will test in the morning.

 

[Snakebitten]

It didn't break PAAK for me. But I'm not a Pixel, but rather a Samsung that only recently got PAAK back after a Samsung update broke it, and then another fixed it.

 

[Space_Pony]

It kind of makes me wonder what and why Android is making changes to bluetooth.

 

[JCHLi]

It didn't break PAAK for me. But I'm not a Pixel, but rather a Samsung that only recently got PAAK back after a Samsung update broke it, and then another fixed it.

They must have an agreement, only one style of phone can work at a time... So they fixed Samsung and had to break others...

I think they must have a new motto, Move slow and break stuff...

 

[Papaye]

Same issue with my pixel 7a on android 15 (security update 01.05.2025) and FordPass 5.10.1 updated yesterday

 

[Briguy]

I have also noticed that my PAAK has stopped working. Pixel 9 Pro running 5.10.1. Ugh

 

[JCHLi]

Good thing for me that I noticed this while in my garage instead of in the below zero temperatures outside!!!

 

[HGxxx]

Yup pixel 8, and paak has been horrible since 5.10.1 Started carrying my fob. I reset Paak in car and deleted and reinstalled the key a couple times, works for a day and then stops

 

[JCHLi]

Hey Ford, it is super nice and all that you fixed a bug you created for public charging, but next time, maybe don't break the main feature of your app!!! It's cold, VERY COLD, and I'd like to be able to rely on being able to get into my vehicle!!!

 

[Space_Pony]

Hey Ford, it is super nice and all that you fixed a bug you created for public charging, but next time, maybe don't break the main feature of your app!!! It's cold, VERY COLD, and I'd like to be able to rely on being able to get into my vehicle!!!

Samsung owners were without paak for a month so you got a ways to go.

 

[JCHLi]

Samsung owners were without paak for a month so you got a ways to go.

I imagine!! At least they were nice enough to push a notification to the app letting people know about the impact that time.. Wonder when they will do that for this time they broke it?

 

[HGxxx]

@Ford Motor Company

 

[JM22681]

I started another thread for Pixel owners.

https://www.macheforum.com/site/thr...y-disappears-but-fordpass-shows-active.42329/

From what Ive found so far, you can get the PaaK key and use it for a period of time, but if you reboot your phone on Pixel you can't get it back.

 

[JCHLi]

I started another thread for Pixel owners.

https://www.macheforum.com/site/thr...y-disappears-but-fordpass-shows-active.42329/

From what Ive found so far, you can get the PaaK key and use it for a period of time, but if you reboot your phone on Pixel you can't get it back.

I've used my Paak with a variety of phones, including pixels. It worked to varying degrees, but it always worked. I do not believe I've ever had to remove and add Paak before except when I switched phones. This has been for just about 4 years...

This latest issues is different, at least for me, in that it occurred following the 5.10.1 FordPass update and could not be corrected by the normal means (rebooting, toggling Bluetooth, or opening the FordPass app).

If Ford is serious about Paak being a feature for their future vehicles, I'd strongly recommend they separate it entirely from their current FordPass app or reevaluate their priorities on the app. A Paak should be a working key...

Sponsored