Phone as a key PAAK Tip

[Wall-E]

Recently there was a update that broke my PAAK function so I tried deleting the app and enrolling again. But this time the app was never able to connect to my car no matter how many ways I tried. Like the sync reset, unlock cycle 10 times, and everything else troubleshooting with Ford wanted to do. Eventually Ford told me it would be fixed in the future update ?

But low and behold something made me check the phone Bluetooth settings. I saw my old Bluetooth file and just tried to forget it. Boom the next time I tried adding PAAK it worked perfectly.

TLDR: forget the old Bluetooth profile on your phone

Sponsored

 

[Space_Pony]

I've found that you need to go into fordpass vehicle-stettings-phone as a key, then select the key that you want to fix and delete it. I haven't found it necessary to uninstall fordpass as long as you delete the key.

 

[Maquis]

Recently there was a update that broke my PAAK function so I tried deleting the app and enrolling again. But this time the app was never able to connect to my car no matter how many ways I tried. Like the sync reset, unlock cycle 10 times, and everything else troubleshooting with Ford wanted to do. Eventually Ford told me it would be fixed in the future update ?

But low and behold something made me check the phone Bluetooth settings. I saw my old Bluetooth file and just tried to forget it. Boom the next time I tried adding PAAK it worked perfectly.

TLDR: forget the old Bluetooth profile on your phone

Apple or Android? Maybe it doesn’t matter?

 

[GreaseMonkey]

What is “this” in did this work? The tip or the PaaK?

 

[bbulkow]

I discussed PAAK problems with a BEV specialist at Ford a few months ago while calling about a flaw in the Android app. ( That's the flaw where, at least on my account, the app shows "plug and charge" is disabled - good news is it's enabled, bad news, that slider still misbehaves, 2 months later ).

The problem I have with PAAK is not that it occasionally fails - which is true - but adding a key to a phone often fails. I might do this more than most people - sometimes I have to factory reset my phone, or switch from one phone to another. Being in the tech industry, I have a lot of phones, and move between versions and such.

As of two days ago (less than 24 hours after the BC 1.3 update, but not immediately after), PAAK stopped working for me. The car now always won't start with PAAK and I need the fob.

I'm on latest (but production, not beta) Android 14 on a Pixel 8.

I was advised by the BEV specialist months ago a few things, none of which works this time:
* Remove all wifi and Bluetooth memory of the car from the phone (all saved Bluetooth connections and Wi-Fi connections that look like the car)
* Remove the phone from the car (but don't clear the keys, just the phone)
* Remove the phone from home wifi (my car is also on my home wifi when near, I've several times just driven a few blocks away)

Then, attempt to refresh the key.

[ By the way, if you're listening, Ford, your advice to move the car to "a clear area" is hilarious. You mean like a large patch of desert with no cell service? That's a clear area. What you mean is an area with good ATT connectivity. That's not a "clear" area, or, not a clear request. ]

This advice was pretty good up until 48 hours ago, it doesn't work now. Out of 3 attempts, I was not able to connect from car to phone to exchange keys. The Ford backend did seem up and available, as I could download a key from Ford (it's server mediated, as you'd expect), just the car and phone wouldn't communicate.

I've tried a lot of things.... But it's all gone south. I'm now stuck between taking the car to my incompetent dealer, and spending a few more hours fooling with it. I don't see calling Ford making a difference, I already have their opinion, my last call with them got a ton of sympathetic words and no fixes (another hour of my life gone).

Sigh.

 

[Space_Pony]

I discussed PAAK problems with a BEV specialist at Ford a few months ago while calling about a flaw in the Android app. ( That's the flaw where, at least on my account, the app shows "plug and charge" is disabled - good news is it's enabled, bad news, that slider still misbehaves, 2 months later ).

The problem I have with PAAK is not that it occasionally fails - which is true - but adding a key to a phone often fails. I might do this more than most people - sometimes I have to factory reset my phone, or switch from one phone to another. Being in the tech industry, I have a lot of phones, and move between versions and such.

As of two days ago (less than 24 hours after the BC 1.3 update, but not immediately after), PAAK stopped working for me. The car now always won't start with PAAK and I need the fob.

I'm on latest (but production, not beta) Android 14 on a Pixel 8.

I was advised by the BEV specialist months ago a few things, none of which works this time:
* Remove all wifi and Bluetooth memory of the car from the phone (all saved Bluetooth connections and Wi-Fi connections that look like the car)
* Remove the phone from the car (but don't clear the keys, just the phone)
* Remove the phone from home wifi (my car is also on my home wifi when near, I've several times just driven a few blocks away)

Then, attempt to refresh the key.

[ By the way, if you're listening, Ford, your advice to move the car to "a clear area" is hilarious. You mean like a large patch of desert with no cell service? That's a clear area. What you mean is an area with good ATT connectivity. That's not a "clear" area, or, not a clear request. ]

This advice was pretty good up until 48 hours ago, it doesn't work now. Out of 3 attempts, I was not able to connect from car to phone to exchange keys. The Ford backend did seem up and available, as I could download a key from Ford (it's server mediated, as you'd expect), just the car and phone wouldn't communicate.

I've tried a lot of things.... But it's all gone south. I'm now stuck between taking the car to my incompetent dealer, and spending a few more hours fooling with it. I don't see calling Ford making a difference, I already have their opinion, my last call with them got a ton of sympathetic words and no fixes (another hour of my life gone).

Sigh.

Did you delete your problem phone from paak settings in Ford pass before doing anything else?

 

[Wall-E]

Apple or Android? Maybe it doesn’t matter?

It doesn't matter. Go to the phone Bluetooth settings and forget all Mach E profiles and try again.

 

[Wall-E]

What is “this” in did this work? The tip or the PaaK?

The tip. Updated the poll to reflect that.

 

[Mach-Lee]

[ By the way, if you're listening, Ford, your advice to move the car to "a clear area" is hilarious. You mean like a large patch of desert with no cell service? That's a clear area. What you mean is an area with good ATT connectivity. That's not a "clear" area, or, not a clear request. ]

Agree on that, they should mention the "cellular coverage" not "clear area".

Have you tried a cold boot on both your phone and the car? That means shutting down your phone completely and disconnecting the 12V battery on the Mach-E for a few minutes. Then booting both back up and attempting again after the've been on for about 5 minutes.

 

[bbulkow]

I discussed PAAK problems with a BEV specialist at Ford a few months ago while calling about a flaw in the Android app. ( That's the flaw where, at least on my account, the app shows "plug and charge" is disabled - good news is it's enabled, bad news, that slider still misbehaves, 2 months later ).

The problem I have with PAAK is not that it occasionally fails - which is true - but adding a key to a phone often fails. I might do this more than most people - sometimes I have to factory reset my phone, or switch from one phone to another. Being in the tech industry, I have a lot of phones, and move between versions and such.

As of two days ago (less than 24 hours after the BC 1.3 update, but not immediately after), PAAK stopped working for me. The car now always won't start with PAAK and I need the fob.

I'm on latest (but production, not beta) Android 14 on a Pixel 8.

I was advised by the BEV specialist months ago a few things, none of which works this time:
* Remove all wifi and Bluetooth memory of the car from the phone (all saved Bluetooth connections and Wi-Fi connections that look like the car)
* Remove the phone from the car (but don't clear the keys, just the phone)
* Remove the phone from home wifi (my car is also on my home wifi when near, I've several times just driven a few blocks away)

Then, attempt to refresh the key.

[ By the way, if you're listening, Ford, your advice to move the car to "a clear area" is hilarious. You mean like a large patch of desert with no cell service? That's a clear area. What you mean is an area with good ATT connectivity. That's not a "clear" area, or, not a clear request. ]

This advice was pretty good up until 48 hours ago, it doesn't work now. Out of 3 attempts, I was not able to connect from car to phone to exchange keys. The Ford backend did seem up and available, as I could download a key from Ford (it's server mediated, as you'd expect), just the car and phone wouldn't communicate.

I've tried a lot of things.... But it's all gone south. I'm now stuck between taking the car to my incompetent dealer, and spending a few more hours fooling with it. I don't see calling Ford making a difference, I already have their opinion, my last call with them got a ton of sympathetic words and no fixes (another hour of my life gone).

Sigh.

After a bunch of trying, it did seem to accept the PAAK, but the key didn't work, until the next morning it did. I guess that's OK. SIgh again.

 

[pikepilot]

Just had issues with repairing my wife's PAAK and turning off the wifi (after reading this thread) was what did the trick. Thanks.

 

[Wall-E]

Just had issues with repairing my wife's PAAK and turning off the wifi (after reading this thread) was what did the trick. Thanks.

Glad it worked for you!

 

[ChuckA]

I've found that you need to go into fordpass vehicle-stettings-phone as a key, then select the key that you want to fix and delete it. I haven't found it necessary to uninstall fordpass as long as you delete the key.

Correct…you can’t finish setting up a broken PaaK without deleting the broken one from FordPass. I haven’t had a PaaK issue in 1 1/2 years.

Sponsored