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

[JM22681]

UPDATE - This bug is fixed in Google's February 2025 security update released on Feb 6, 2025. Use the system menu to update your phone and reboot, then delete/re-add your key.

----------------

Hi all, there seem to be increased instability with retaining the PaaK key on PIXEL over the past week or two. Sort of similar to the Samsung thread that was recently resolved by Samsung.,

I have a 2023.5 with all of the OTAs current. I had a very consistent experience for the latter half of 2024 where PaaK worked 99% of the time. When it didn't, I would simply toggle Bluetooth and open FordPass.

January rolled around and I took the January Pixel update right around its release date (Jan 5 or so). PaaK stopped working and I reset it. Within a week it stopped working again, and I reset it. It looks like 5.10.1 updated yesterday, which may have caused it to reset again.

The way I've always known it won't work is when I can't see the Bluetooth name ###### (5 seemingly random digits) followed by MACHE, in my Bluetooth list. Once that is gone, PaaK is hosed even though the app reports an Active key with all 4 checkboxes relative to the configs it wants.

I am wondering - how many others are now going through the same instability on PIXEL in recent weeks? I am adding a poll here to see what gens are impacted.

Sponsored

 

[macchiaz-o]

My Paak stops working within days or a week or so on various generations of Pixel up to my current P7P, since the beginning of my Mach-E ownership (3/6/21). I just toggle Bluetooth off and back on and then Paak is good.

On much older versions of FordPass and/or Android, I think I occasionally had to restart the whole device to restore Paak sometimes.

 

[HGxxx]

Exact thing happened to me. Pixel 8.

 

[DeusEx]

I just recently deleted my Paak on my Pixel 9 Pro since I couldn't control the doors and windows as soon as I walked up to the car. The phone seemed to have trouble getting connected via Bluetooth to the car. I deleted my Paak, added it back, and now it's working again.

It was a bit of a pain to remember the steps since I didn't do this often. Thankfully, I laid out the steps for another member a while back and found my post.
https://www.macheforum.com/site/threads/new-pixel-9-pro-fold-will-not-paak.40547/post-875202

 

[bbhaag]

It broke on my P7P when I installed the January security update. Until then it was working fine. Since then I have tried resetting PAAK but it doesn't work.

 

[JM22681]

It broke on my P7P when I installed the January security update. Until then it was working fine. Since then I have tried resetting PAAK but it doesn't work.

Try deleting FordPass and reinstalling. It should prompt you to re-add the key.

 

[MacherAWD]

Pixel 6a running beta builds and fordpass 5.10 and now 5.10.1 I have had pretty solid Paak over the years, but since mid decemeber I have had to carry my keys it has been so unstable (first time I have needed to in 3 years). In the last few weeks I took the beta Jan pixel update, deleted Paak, cleared cache and storage in app and resetup. It has worked smooth about a week now, and last night I installed android 16 beta and paak still going strong. Keys are now back in the house and I am confident to leave without them (I did double check my backup start code)

 

[GrayWolf]

PaaK is working fine on my Pixel 8 Pro. I only lost it when I swapped out my 12V battery. Had to remove PaaK from the phone and car and start over. It's been rock solid since.

Also - I did notice that the Bluetooth Low Emissions ID doesn't show up in my list of connected devices. This isn't hindering my phone working with PaaK, however.

FordPass version is also on the beta - 5.10.1

 

[JM22681]

PaaK is working fine on my Pixel 8 Pro. I only lost it when I swapped out my 12V battery. Had to remove PaaK from the phone and car and start over. It's been rock solid since.

Also - I did notice that the Bluetooth Low Emissions ID doesn't show up in my list of connected devices. This isn't hindering my phone working with PaaK, however.

I'm noticing the same, did they change from BLE with 5.10.x?

 

[GrayWolf]

I'm noticing the same, did they change from BLE with 5.10.x?

That's a good question. I suspect not and that, instead, Google has opted to move the list of BLE connections or remove them altogether due to the confusion caused by listing devices possibly 2-or-more times?

In an annoying side note - I found that with Android 15, Google also played "Move the cheese" with the Battery Optimization settings. You have to actively click on Settings -> Apps -> FordPass (or other app) -> App Battery Usage -> and then ignore the toggle next to "Allow background usage"... and, instead, click on the words "Allow background usage" to actually get into an unintuitive/hidden menu that has the original "Optimized" and "Unrestricted" options... whoever thought that THIS was smart should probably be fired.

 

[hack-e]

I have mentioned in a couple of threads that I also lost PaaK on my Pixel 9 Pro right about the time I got FordPass 5.10.1 after having 5.10.0. I did try to downgrade to 5.10.0 and it still won't setup and work. I did update back to 5.10.1. I also just tried the Fuse 18/19 pull this morning and that didn't help fix the issue.

To go back a little in time, I also started having a problem when I got the Jan Android update but at that time I was able to delete my phone key and set it up again and then it worked better than ever. But right about the time 5.10.1 came out, PaaK completely stopped working.

 

[jdhzzz]

In an annoying side note - I found that with Android 15, Google also played "Move the cheese" with the Battery Optimization settings. You have to actively click on Settings -> Apps -> FordPass (or other app) -> App Battery Usage -> and then ignore the toggle next to "Allow background usage"... and, instead, click on the words "Allow background usage" to actually get into an unintuitive/hidden menu that has the original "Optimized" and "Unrestricted" options... whoever thought that THIS was smart should probably be fired.

Thanks so much for this. I was SOOOooooo frustrated that I had "Allow background usage" on but FordPass refused to see that it had background usage. Setting it through the hidden link fixed it. One less broken/mis-set thing. On to the getting PAAK back working on the Pixel 8a...

 

[HGxxx]

I just recently deleted my Paak on my Pixel 9 Pro since I couldn't control the doors and windows as soon as I walked up to the car. The phone seemed to have trouble getting connected via Bluetooth to the car. I deleted my Paak, added it back, and now it's working again.

It was a bit of a pain to remember the steps since I didn't do this often. Thankfully, I laid out the steps for another member a while back and found my post.
https://www.macheforum.com/site/threads/new-pixel-9-pro-fold-will-not-paak.40547/post-875202

I did it three times already, reset the paak, usually works good for 3 days and then the connection is dead. The phone does not even see the mach e paak Bluetooth signal.

 

[JCHLi]

Not the same exactly. Mine just stopped working all together with the 5.10.1 update.

I've had minor issues and inconveniences before but this is the first time it broke completely.

Unfortunately with the general issues occurring with other updates it seems likely Ford will just try to lump this in with the other issues.

 

[HGxxx]

Not the same exactly. Mine just stopped working all together with the 5.10.1 update.

I've had minor issues and inconveniences before but this is the first time it broke completely.

Unfortunately with the general issues occurring with other updates it seems likely Ford will just try to lump this in with the other issues.

Did you reset Paak in the car, it's under general settings , under reset tab

Sponsored