PaaK Observations

[VindictivePantz]

For my '21 Job 1, I've learned more about how Paak, BT, and Sync and its backend potentially works, through sheer stumbling my way through an issue I was having.

The experience:

• I got a new phone, followed all instructions for removing PaaK, and then for setting up the new phone.
  • All good - except - the new phone whined about wanting to disconnect Bluetooth to support enhanced contact features, so I did so. I removed the Bluetooth connection from the car and phone, and then reconnected the Bluetooth connection
• Things then got interesting: Some PaaK functionality still worked (remote start, departure times,) but I no longer received notifications on my phone that the car was locking when I walked away. The car still locked, but I also carry my fob 100%, so I assume the car was locking because of the fob, not the phone.
  • At this point, I think PaaK from a Bluetooth perspective was dead, but the car still recognized my phone as authorized for remote actions
    • I could no longer open the car with PaaK while I was nearby
  • In short, manually removing the phone's Bluetooth connection killed PaaK. Not surprising.
• To get things back to where they should be, I went through the PaaK reset process, reconnected, and the car was happy for walk away, remote start, BUT not departure times and it still will not unlock if I am nearby (no fob)
  • I did NOT remove the BT connection that was still present after I reset PaaK
  • Departure times are being set successfully, but are not actually being executed. FordPass shows they're active and accurate and so does the car

I suspect something on the backend w/ Ford needs to synchronize for all of the functionality to work. Just a hunch. The "system" knows my phone is authorized to do things, but it's not actually executing some of those things. I suspect some data issue or a clean-up job of some sort on the backend has to be fixed, as I would think that their backend controls the initial authorization since it takes some time for PaaK to configure, and then tells the car everything is authorized so things can work locally from that point on.

I am going to give it another couple of days, and then completely remove PaaK and the BT connection, and start from scratch.

Only sharing because it's potentially revealing how the pieces/parts/process fit together. I'll post updates as I have them.

Sponsored

 

[RickMachE]

I just did this. Here is what I did.

1) In the vehicle, delete PaaK.
2) In the vehicle, delete phones.
3) In the vehicle, add phone.
4) In FordPass, add the phone as a key.
5) Set passcode.

 

[VindictivePantz]

I just did this. Here is what I did.

1) In the vehicle, delete PaaK.
2) In the vehicle, delete phones.
3) In the vehicle, add phone.
4) In FordPass, add the phone as a key.
5) Set passcode.

Thank you! That's what I was planning on doing next.

This "half" working state is odd and for those with less patience than me, I can only imagine how frustrating it might be.

 

[RickMachE]

Thank you! That's what I was planning on doing next.

This "half" working state is odd and for those with less patience than me, I can only imagine how frustrating it might be.

I concur.

With my new phone, I was hoping to find out that the process was smooth, because in 2021 it was a cluster. While it's not a cluster, it's still not smooth. No mention that you have to do TWO things - connect for PaaK and connect for phone features.

 

[ATL]

I concur.

With my new phone, I was hoping to find out that the process was smooth, because in 2021 it was a cluster. While it's not a cluster, it's still not smooth. No mention that you have to do TWO things - connect for PaaK and connect for phone features.

Yes, and it follows that if you check you phone Bluetooth, I think you'll find there are actually 2 different connections with different names in the device list. One is named logically, the other is a bit coded, for the PAAK.

 

[dmc23]

For my '21 Job 1, I've learned more about how Paak, BT, and Sync and its backend potentially works, through sheer stumbling my way through an issue I was having.

The experience:

• I got a new phone, followed all instructions for removing PaaK, and then for setting up the new phone.
  • All good - except - the new phone whined about wanting to disconnect Bluetooth to support enhanced contact features, so I did so. I removed the Bluetooth connection from the car and phone, and then reconnected the Bluetooth connection
• Things then got interesting: Some PaaK functionality still worked (remote start, departure times,) but I no longer received notifications on my phone that the car was locking when I walked away. The car still locked, but I also carry my fob 100%, so I assume the car was locking because of the fob, not the phone.
  • At this point, I think PaaK from a Bluetooth perspective was dead, but the car still recognized my phone as authorized for remote actions
    • I could no longer open the car with PaaK while I was nearby
  • In short, manually removing the phone's Bluetooth connection killed PaaK. Not surprising.
• To get things back to where they should be, I went through the PaaK reset process, reconnected, and the car was happy for walk away, remote start, BUT not departure times and it still will not unlock if I am nearby (no fob)
  • I did NOT remove the BT connection that was still present after I reset PaaK
  • Departure times are being set successfully, but are not actually being executed. FordPass shows they're active and accurate and so does the car

I suspect something on the backend w/ Ford needs to synchronize for all of the functionality to work. Just a hunch. The "system" knows my phone is authorized to do things, but it's not actually executing some of those things. I suspect some data issue or a clean-up job of some sort on the backend has to be fixed, as I would think that their backend controls the initial authorization since it takes some time for PaaK to configure, and then tells the car everything is authorized so things can work locally from that point on.

I am going to give it another couple of days, and then completely remove PaaK and the BT connection, and start from scratch.

Only sharing because it's potentially revealing how the pieces/parts/process fit together. I'll post updates as I have them.

What you're saying makes sense as an IT professional but makes me worry about what happens when I turn the car in at the end of the lease. If their systems are that disconnected I am not confident they will delete my information.

 

[VindictivePantz]

Update:

Followed the steps above, and it still is not working 100%. Remote start works intermittently, departure times set but don't actually execute (even when set from inside the vehicle,) and I am not able to unlock the car with just having my phone present.

"Walk-away" works, and remote start does work most of the time, but fails enough where it's not reliable.

I think I'm at the point of pulling the magic fuse and/or calling Ford.

 

[Maquis]

Update:

Followed the steps above, and it still is not working 100%. Remote start works intermittently, departure times set but don't actually execute (even when set from inside the vehicle,) and I am not able to unlock the car with just having my phone present.

"Walk-away" works, and remote start does work most of the time, but fails enough where it's not reliable.

I think I'm at the point of pulling the magic fuse and/or calling Ford.

The only issue that you mention here that has anything to do with PaaK is the inability of the car to unlock when you have your phone. Make sure FP is running on your phone (don’t force-stop it).

Everything else uses a different mechanism.

 

[VindictivePantz]

The only issue that you mention here that has anything to do with PaaK is the inability of the car to unlock when you have your phone. Make sure FP is running on your phone (don’t force-stop it).

Everything else uses a different mechanism.

FordPass is active/running (walk-away locking supports that.)

I have "both" BT connections, everything checks out. I know PaaK is partially working via BT because walk-away works.

I'll perform some reboots and such and see what happens.

 

[jaypinkney]

Good day everyone! 2023 MME Premium AWD… Got it October 2023… PAAK worked great up until now… Similar situation. iPhone 13 with latest iOS. All apps including Ford Pass up to date. Similar symtoms: Connects BT for car play, can remote start, set departure times, set charging schedul… but “Controls” won’t work such as opening the Frunk, Tailgate, windows… and the BT symbol in controls is grayed out… Did all as above… Reset PAAK in car, deleted phone.. removed app from phone… hard reset, re-installed, re-activated PAAK and backup start code… works!… For a day!! Next day, no BT connectivity once again!… car won’t recognize PAAK… start over… next day, same thing!… About to call Ford!! ?‍??‍?‍

 

[Mosworthy]

Since October of '21 I've only had two issues with PAAK....
I use it exclusively and lock away my fobs in a faraday bag in a drawer in my house.
I set up the BT and PAAK connection with each new phone I've got, and the wife's, through FordPass, I've never had to connect two different ways. Obviously, fully deleting everything on Sync and the phones at each reconnection.
I've had zero issues connecting five different android phones to the car

Problem #1:
PAAK just stopped working, but all other BT and FordPass activities worked fine. After a lot of talking here on the forum and playing around, what fixed it was pulling the "latent BT" fuse in the cabin fuse box for 2min then reinstalling it. Worked perfect after that.

Problem #2:
The Android/Google issue from Dec '24 until the next update on the phone in late Jan '25.

 

[GrayWolf]

FordPass is active/running (walk-away locking supports that.)

I have "both" BT connections, everything checks out. I know PaaK is partially working via BT because walk-away works.

I'll perform some reboots and such and see what happens.

Not to be annoying here but when you say "Active" - do you have FP open/unlocked and showing the car before you walk up to it? If not, would you mind giving this a test? Stinks to have a frustrating experience - I am in agreement with you on that!

 

[VindictivePantz]

Not to be annoying here but when you say "Active" - do you have FP open/unlocked and showing the car before you walk up to it? If not, would you mind giving this a test? Stinks to have a frustrating experience - I am in agreement with you on that!

I've tried having the application literally running on the screen, as well as just having it open and running in the background. It's really odd, as I suspected it was the phone might be putting the app to sleep, but that's not the case. It's one of a couple of applications that I allow to NOT be managed for power usage.

 

[jaypinkney]

Since October of '21 I've only had two issues with PAAK....
I use it exclusively and lock away my fobs in a faraday bag in a drawer in my house.
I set up the BT and PAAK connection with each new phone I've got, and the wife's, through FordPass, I've never had to connect two different ways. Obviously, fully deleting everything on Sync and the phones at each reconnection.
I've had zero issues connecting five different android phones to the car

Problem #1:
PAAK just stopped working, but all other BT and FordPass activities worked fine. After a lot of talking here on the forum and playing around, what fixed it was pulling the "latent BT" fuse in the cabin fuse box for 2min then reinstalling it. Worked perfect after that.

Problem #2:
The Android/Google issue from Dec '24 until the next update on the phone in late Jan '25.

Hmmm, I’ll have to try that next… Never thought of pulling a fuse… or as we say in aviation, cycling a circuit breake! ??

Sponsored