[PSA] - PaaK and Pixel 7 / Pro

[Maxwells4]

Sorry to hijack this thread (and bring more bad news if you haven't heard it), but DO NOT SKIP this update. It patches maybe the worst phone vulnerability I've ever heard of, RCE in the modem baseband firmware, basically a root exploit from nothing more than calling you: https://arstechnica.com/information...ities-allow-some-android-phones-to-be-hacked/ Get the update ASAP. Carry your fob for a while if you have to.


Update: more on-topic, I installed the March update on my Pixel 6a, and PAAK doesn't seem to be working any worse or better than it did before.

Sponsored

 

[babgvant]

Ok so anyone who has a P7/P7P should be aware that the March security update might boink PaaK. The most reliable way I've found to get PaaK working with this update as a momentary solution is to toggle BT on and off and then immediately open FP. It will connect and allow you to drive away. It will disconnect within a very short period and you'll have to do the dance again at the next stop to open the doors and start the vehicle without a code.

Extremely frustrating, but it looks like the blame is on Google for this one unless Ford didn't comply with new procedures that would have been conveyed months ahead.

I was having to do exactly this dance after applying the March update. Oddly, after applying the March Play update it's not as bad. Hard to say if it was the update or that I bounced the phone after though.

 

[Maxwells4]

I take back what I said above, actually. Right after I applied the update, things were fine, but then the next day I drove the car I had similar issues (disabling/re-enabling BT made it work once, but then later I had to use the backup code). Later I rebooted my phone and it did work. So yeah, something has clearly regressed.
Still don't skip this update though...

 

[macchiaz-o]

I'm having issues with PaaK lately too. I didn't notice this on my P7P until the last week or so because I was mostly driving around with PaaK and fob together.

 

[babgvant]

New version of FordPass out ?

 

[Maxwells4]

Wow, not sure I can handle changing the icon ?
So far so good on PAAK though.

 

[Eckless]

Hey folks - chiming in to say that the issues between PAAK and Pixel 7 Pro have gotten bad enough to the point where I have returned to the fob. The bluetooth "toggle off, then back on" does work, but it's just so inconsistent that it becomes a frustration. It's pretty sweet when it works, though...

So if anybody has any inside info or tricks on making it work consistently, would love to hear it...have given feedback on Android beta app and other places that it's gotten rough.

 

[abr]

Todd - sorry, I did remove the phone and PAAK from my FE (and my profile), and then tried to re-set up the PAAK and couldn't get it to work.

Update - seems to be working fine now. Was there an Android update in the last week or so that fixed this??

 

[mdpmdp]

Ok so anyone who has a P7/P7P should be aware that the March security update might boink PaaK. The most reliable way I've found to get PaaK working with this update as a momentary solution is to toggle BT on and off and then immediately open FP. It will connect and allow you to drive away. It will disconnect within a very short period and you'll have to do the dance again at the next stop to open the doors and start the vehicle without a code.

Extremely frustrating, but it looks like the blame is on Google for this one unless Ford didn't comply with new procedures that would have been conveyed months ahead.

I've been searching around the Android/Pixel subreddits and Google support links but couldn't find anything concrete (every update brings out people who say this or that broke), so glad to have this confirmed by somebody else. I actually usually don't apply updates immediately because usually something breaks, but my P7P auto-applied the update overnight for me sometime last week. I didn't notice the PaaK issues at first (I think I didn't drive as much or something, don't remember) but I did notice the insane icon padding issues (not sure if you've experienced that too). This past weekend I've been driving a lot and found the same issue and resolution of toggling BT off/on, although that doesn't even help sometimes and I have to do a full-blown restart of the phone.

FWIW I've also had intermittent connection issues with my Galaxy Watch 5 to the P7P in the same timeframe, though not nearly as bad. Seems to me the issue is easily reproducible by leaving BT range (of the car or phone) and then coming back into BT range. When I do that, I can't even manually connect using the BT menu. Extremely frustrating, as you said.

 

[imstriker]

Still on a Pixel 6 here. PaaK has become just about unusable on it as well.

 

[Sneezy]

PaaK is not working at all on my Pixel Pro 7. I was going to remove the Paak setup and the phone from the car and start over to see if that helps.
This is ridiculous.

 

[gduprey]

Add a datapoint - in the last 2 days, PaaK went from being 97% reliable for me to 0. It just won't work - not walking up to car (thankful I had my backup codes), not in the car and not even when the phone is sitting in the "magic wireless charger" spot.

Rebooted the phone, the car, toggled bluetooth, etc, etc. At some point, I'l submit to the agony of resetting and relinking my phone again (why is that such a PITA!).

I literally NEVER used the fob and it's taking some getting used to again to avoid forgetting it.


No idea why.

Job 1 Mache X4 with 4.2.2 in car and most recent fordpass app on a stock Pixel 6 with all normal updates applied.

Disappointing :-(

 

[rob.todd]

Exact same thing happened to me two weeks ago with the sync 4 update. No work around or solution yet… only I have an iPhone. So you can put your mind at ease thinking this is something that only affects android and will therefore never get any attention (I also have a pixel so used to have this anxiety).

 

[hack-e]

Ok so anyone who has a P7/P7P should be aware that the March security update might boink PaaK. The most reliable way I've found to get PaaK working with this update as a momentary solution is to toggle BT on and off and then immediately open FP. It will connect and allow you to drive away. It will disconnect within a very short period and you'll have to do the dance again at the next stop to open the doors and start the vehicle without a code.

My exact experience (as posted elsewhere around these forums) since the March P7P security update. I have a similar workaround where I keep FordPass open, turn off BT from the P7P pull-down tiles, then wait for P7P to gripe that my Pixel Watch isn't connected, then use the FordPass app's built-in method to turn BT back on:

Press the "Optimize Phone as a Key" text button:

Click on the "Bluetooth" option below, then "Allow" on the popup:

Go back to the main FordPass screen and you will see it connects to the MME. It will stay connected for somewhere between a few seconds to a handful of minutes before it will disconnect again.

I had a take a long trip and that annoying sequence made me start using the key fob until this problem is fixed.

 

[Eraser]

Up until about a week ago I wasn't having any out of the ordinary issues with Paak. Now it either won't connect at all or will randomly disconnect while I'm driving.

Just a hunch, I wonder if this could be related to Google Play Services (GPS). I haven't installed any new system updates on my P7P since the beginning of March yet I'm starting to have issues. GPS on the other hand is updated fairly regularly along with other apps. Today I noticed there was a March 28th update for GPS (ver 23.13.12) so I installed it. I toggled Bluetooth off and on then restarted PaaK service (Ford Pass), then Ford Pass connected, and stayed connected. It might just be a coincidence, but I'll keep an eye on it. Hopefully that fixed the problem.

Sponsored