PAAK and Android 16

[delao13]

I have a Pixel 8 Pro. Although I occasional have to reset and reinstall the PAAK, it generally works flawlessly. However, after I updated my Pixel 8 Pro to Android 16 a few days ago, the PAAK stopped working. As I've done every other time, I deleted the PAAK in the phone and reset it on the car display. I then tried to install it on the phone but my phone refuses to recognize the car and install the PAAK. Has anyone else had a problem with PAAK after updating to Android 16?

Sponsored

 

[kodiakng]

dang, sorry this is happening for you.

i have a pixel 7 and PaaK has continued to work consistently for me after Android 16 update on tuesday.

 

[delao13]

Good to know. Maybe I just need to wipe all connections from the phone to the car and reconnect everything.

 

[phil]

I have the same Pixel phone, but still on Android 15. I have only once had to re-make the phone key - that was in January this year, when they had that problem with a security upgrade/patch that took a couple weeks to fix. Otherwise, it's been solid.

I do know that there is an extra step that sometimes needs to be completed to re-make the key. It's a "reset" option somewhere on the Settings menu in the car, not on the phone. You can tell that this extra reset is needed when PaaK gives your phone a new name, like "Pixel Pro 2" rather than just "Pixel Pro". It is not clear to me from your OP whether you have done that reset, but if not it's worth a try. If you've already done that, then I got nothing.

 

[delao13]

I've taken that step. I delete the key on the phone and reset on the car. This is the one time it's not working.

 

[PedroDaGr8]

I've taken that step. I delete the key on the phone and reset on the car. This is the one time it's not working.

MY wife has that phone and it works fine for her (other than the issue in January of this year).

 

[Gungrave223]

I'm on the second beta of A16 and the app doesn't work at all.... So I've been carrying my keys for the last few days til I fix is release, hopefully soon.

 

[delao13]

Which phone do you have?
What's strange is the Fordpass app works for me, it starts the AC remotely, unlocks it, etc. What it will not do is start the car.

 

[Gungrave223]

Which phone do you have?
What's strange is the Fordpass app works for me, it starts the AC remotely, unlocks it, etc. What it will not do is start the car.

I have the Pixel 9pro XL and after I installed qpr1 beta 2, the app just crash immediately after opening.

So if you rely on paak, avoid the latest qpr1 beta 2.

 

[MacherAWD]

I have a pixel 6a, I have run all of the beta for 16 on day 1, I am currently on beta 2. Zero issues with Paak. In previous years I remember the 15 beta hosing my PaaK, but no issues in 16.

 

[Gungrave223]

I have a pixel 6a, I have run all of the beta for 16 on day 1, I am currently on beta 2. Zero issues with Paak. In previous years I remember the 15 beta hosing my PaaK, but no issues in 16.

I just wiped the app storage and cache and it loads now... but now I gotta set back up paak.

 

[macchiaz-o]

PaaK is working on my Pixel 7 Pro with Android 16 build "BP2A.250605.031.A2". (Official release.)

Just giving you another data point.

 

[GrayWolf]

PaaK is also working well on my Pixel 8 Pro with the release build of Android 16. I hope that the OP's problem is resolved soon!

 

[Mustangor]

Last time I had this problem I did this :

1/ Clear Fordpass application cache
2/ Uninstall Fordpass
3/ Reboot Phone
4/ Install Fordpass
5/ Go to Car, unpair phone, erase PAAK profile
6/ Pair phone (Bt)
7/ Add Android Auto connection
8/ Add PAAK when suggested

Hope this helps.

 

[iNeedANameHere]

Pixel 9 Pro here, no issues with the app or PaaK at all on Android 16 (non-beta)

Sponsored