PAAK gone again after Samsung s22 update

[Mach T]

I have been really happy with phone as a key lately, then a couple of days ago, my Samsung Galaxy s22 updated and - poof - no more PAAK! Anyone else experiencing this issue?

Sponsored

 

[SteveMach-ee]

My S22+ got the security update yesterday. I just tried it and PAAK unlocks and starts the car. That said, after many months of only using PAAK, I just don't trust it anymore unless I'm driving around town. For example several times over the last few weeks the car would start with PAAK, then give the "Key needed for restart" after shutting down. Then after a bit it decides that it sees the PAAK again. It's also slow to unlock and I sometimes have to unlock the phone to get the door to unlock. Of course I have backup start passwords and the code.

Because of this I got a 3rd keyfob on Amazon for $39 and used the other two to program it. Thanks forum for the procedure! That way I if I lose one, I can program another cheap one.

 

[Mach T]

My S22+ got the security update yesterday. I just tried it and PAAK unlocks and starts the car. That said, after many months of only using PAAK, I just don't trust it anymore unless I'm driving around town. For example several times over the last few weeks the car would start with PAAK, then give the "Key needed for restart" after shutting down. Then after a bit it decides that it sees the PAAK again. It's also slow to unlock and I sometimes have to unlock the phone to get the door to unlock. Of course I have backup start passwords and the code.

Because of this I got a 3rd keyfob on Amazon for $39 and used the other two to program it. Thanks forum for the procedure! That way I if I lose one, I can program another cheap one.

I keep a fob in a faraday bag hidden in my car just in case

 

[Guss-E 2021]

My S23 was recently updated but PaaK worked for me yesterday. I will say walk up unlock has been absolute rubbish lately. More often than not a have to unlock the phone and then pump the door button a few times to get in. So lovely in the cold with my arms full of groceries.

It's probably my imagination but the situation seems to be exacerbated by the cold. This is not the first time a Samsung update has interfered with PaaK. If you are experiencing an issue with actually getting the car to drive, you might try adding your phone all over again. I would also recommend taking your fob just in case. Lastly, set up the door code and start code if you have not already.

 

[Deezul]

Worked fine for me yesterday.

 

[Dan the Man]

I have been really happy with phone as a key lately, then a couple of days ago, my Samsung Galaxy s22 updated and - poof - no more PAAK! Anyone else experiencing this issue?

I have a Samsung s22. I believe there is some type of problem. I don't think it has anything to do with the cars control module I can't pinpoint it but it seems that it's been acting very sporadically since Ford went to the new app but I can't be certain of that. It is either the Ford app or the Samsung phone. I have been experimenting trying to figure out what the issue is I have determined that Bluetooth is getting disconnected from the car sometimes walk up works most of the times it doesn't Walk away works better than the walk-up feature. When I am by the car and I turn Bluetooth off on my phone and turn it back on it connects to the car and I can get in and start the car. Sometimes when I start the car I get no key detected and I take a look at the phone and I see that it's disconnected from the car you can tell this by going to the mobile Ford app screen and touch the controls icon. These controls are all Bluetooth functions IE open windows closed windows open frunk, close trunk. I also experimented by going to my apps and force stopping the ford app and than open the Ford app I see that it does connect to the car. Something has definitely change its either in the mobile Ford app or Samsung phones. I believe it is a Bluetooth connectivity issue Bluetooth is not connecting to the car when it's in the range to connect.

hopefully with with the people on this form that are having this problem we can figure it out. For those having this connection problem try turning off Bluetooth and back to see what happens also try doing a force stop of the app and then open the ford app to see what happens please post your results hopefully we can figure this out.

 

[Dan the Man]

I'm surprised there aren't anymore post on this subject. I be willing to bet there are quite a few people who have this issue

 

[Mach T]

I ended up removing my phone as a key, did the reset in the car, and then reconnected my S22 and PAAK appears to be working again.

 

[Dan the Man]

I deleted the key, did a key reset from the car and deleted the Ford app and reinstalled it. I'm getting the following error.

Error Downloading Key
Something with wrong. Please try again later error code 1104.

Not much info on this code. My phone is connected to the car and Android Auto is working.

Kind I wished I would have not started this process. The PAAK was working sporadically but it was something I was willing to live with.

Any suggestions would be greatly appreciated!

 

[imperator]

Had the same problem this morning. Was working fine when I drove out of the garage. PaaK won’t work again despite resetting when I was heading back. Weirdly enough, the Ford App shows Bluetooth control connected, and I can open the trunk/windows no problem at all. Luckily, I do have my fob in a Faraday Cage bag within the car...

 

[NorthlandPhil]

PAAK is failing for me today. Also with my wife's phone. Both are iPhones. Worked "fine" yesterday (as fine as it ever works, which is a little disappointing especially with door locks).

My wife is currently driving with a fob. I'm hoping something fixes itself here before I reset PAAK and reenable them.

 

[NorthlandPhil]

And now PAAK works. No idea why it would not start an hour ago.

Sponsored