PaaK stopped working about 1 week ago (Android / Pixel 7)

[Farfapapa]

I am not exactly sure how long ago (certainly since Wednesday 12/21 which is the first time i wasn't able to use PaaK), but my PaaK stopped working completely for the first time since i got the car (May 2021, so more than 18 months ago).

I was hopeful to find others with the same issue, but the only post i saw with a similar description didn't help me: resetting PaaK completely on the car and the phone didn't help. I did the reset a few times, and it's always the same problem: i can setup the phone as a key, but then it never manages to connect via bluetooth to get the car started. The app displays a "Bluetooth trying to connect" for a while, then blimps "Bluetooth disconnected", then start over again.

I have a 2021 Mach 1 (march 2021 build), and my Phone is an Android (Pixel 7). Power up 3.6.1 is installed (has been for some time, i have to assume something is off with the phone more than the car, but the phone can connect over bluetooth just fine for other things like infotainement in the car (plays music just fine, or handles calls). Fordpass was last updated on 12/05/2023, and so was Android actually (last update also on 12/05/2023). Nothing matches the time it stopped working for me.

Anyone else faced this and couldn't solve it via a hard reset of the PaaK (uninstall/etc, the DIY procedure documented in this forum)? I was semi-hopeful that one of the SSM articles about the modem could apply, but unfortunately i see the modem serial number just fine in my car. This time of the year is really not the best time for a dealer visit!

Sponsored

 

[twcoult]

I too have the same issue. My FP app decided to stop working altogether a few weeks ago (frozen). I had trouble reinstalling and called the helpline who were quite responsive. I had several tracking features turned off on my iPhone and this was the issue with the app installation. Everything on the app works with both my F250 and the Mach E GT, except PaaK feature, which worked fine prior for the last year. So no solution yet and I’ve tried several times to reestablish the feature. No luck. It simply can’t find the BT connection to the car for this function but is connected with all other BT functions.

 

[Devbloggs]

I also have issues pairing the PAAK to my 22 mach-e

Was working fine, was having issues with Ford pass and had to reset everything and start over again. Since then, Fordpass is working fine, but cant get past the "Copy And Continue" part, Just sayings connecting to vehicle Bluetooth and it never does anything after

 

[macchiaz-o]

Just a data point, but mine is working fine. '21 job 1 Mach-E. Pixel 7 Pro with the 12/22 security update and 11/22 play store update. FordPass 4.23.0, with Ford's recommended access permissions for PaaK.

 

[Farfapapa]

Well, in my case, I reopened the app after a week off/away, and magic: it connected after all to the car and I could complete the setup (creating the door code/startup code). I suppose I wasn't patient enough with some offline magic after the reset/reconfiguration, or the car needed a vacation from me!

 

[the golden eel]

I also have issues pairing the PAAK to my 22 mach-e

Was working fine, was having issues with Ford pass and had to reset everything and start over again. Since then, Fordpass is working fine, but cant get past the "Copy And Continue" part, Just sayings connecting to vehicle Bluetooth and it never does anything after

This is EXACTLY where I am. Samsung S22 plus.

Although they updated the fordpass app yesterday (4.23.1) so I should try Paak setup again. Yesterday's update at least allows me to access departure times again.

 

[superdave80]

I'm still surprised that people are surprised when a phone/app/bluetooth setup doesn't work. Ask me how long it takes to get my phone to connect to a bluetooth speaker...

 

[Farfapapa]

When the phone is meant to be a primary option to start the car, it shouldn't stop working like it did for me, and reinstalling/resetting shouldn't take days either. I'm relatively tech savvy, and having to fight to make it work makes no sense, i couldn't see my parents going through that for example, and i'm pretty sure my wife would never think of doing what i did (come here, read forums, understand the proper way to completely reset-reconnect your phone if something like that happens to you out of the blue for no reason, and re-try one last time a few days later if the last attempt couldn't complete successfully). That's why she carries the key and i use my phone.

I don't know how things evolved since i got my car, but we got a single key for it, and we're 2 people often driving it, so the phone has to be a viable option for us. I think i wouldn't mind as much if we had 2 keys.

I'm also glad i read this forum because i learned how to reset Sync.. I am really getting annoyed by another stupid problem (profiles don't load up sometimes, it just won't let me select one after starting the car). I discovered that a Sync reset solves that. Maybe i should have tried a sync reset too when i had these keys issues, looks like Sync operates on some old Windows 95/98 platform..

 

[dtbaker61]

I am not exactly sure how long ago (certainly since Wednesday 12/21 which is the first time i wasn't able to use PaaK), but my PaaK stopped working completely for the first time since i got the car (May 2021, so more than 18 months ago).

I was hopeful to find others with the same issue, but the only post i saw with a similar description didn't help me: resetting PaaK completely on the car and the phone didn't help. I did the reset a few times, and it's always the same problem: i can setup the phone as a key, but then it never manages to connect via bluetooth to get the car started. The app displays a "Bluetooth trying to connect" for a while, then blimps "Bluetooth disconnected", then start over again.

I have a 2021 Mach 1 (march 2021 build), and my Phone is an Android (Pixel 7). Power up 3.6.1 is installed (has been for some time, i have to assume something is off with the phone more than the car, but the phone can connect over bluetooth just fine for other things like infotainement in the car (plays music just fine, or handles calls). Fordpass was last updated on 12/05/2023, and so was Android actually (last update also on 12/05/2023). Nothing matches the time it stopped working for me.

Anyone else faced this and couldn't solve it via a hard reset of the PaaK (uninstall/etc, the DIY procedure documented in this forum)? I was semi-hopeful that one of the SSM articles about the modem could apply, but unfortunately i see the modem serial number just fine in my car. This time of the year is really not the best time for a dealer visit!

the only way thru it that worked for me was to remove EVERYTHING, and re-install and re-configure as if it were a new delivery.

remove FordPass, and BOTH blue tooth pairings from phone
remove all phones and BT pairings from MME
reset PAAK in MME
.... re-install Fordpass on phone
.... re-configure PAAK and re-set backup code
.... re-add 'regular' phone bt pairing LAST, after PAAK is working

 

[Devbloggs]

just decided to try the PAAK setup again yesterday, worked first time

Also, the instant error when trying to open the departure menu in the Ford Pass app is suddenly fixed

was clearly a Ford Pass side issue

Sponsored