PSA - DO NOT UPDATE to 3.35.0 on Android if using PaaK without a FOB

[DevSecOps]

No change for me either so it doesn't seem to be a problem on iPhones.

Thanks I removed the "maybe iOS as well" from the title since a couple of you confirmed that it's not an iOS issue.

Sponsored

 

[GoGoGadgetMachE]

I just remembered I never set my backup start code for the new phone. This is a bad time to realize that.

 

[Carsinmyblood]

I tried to get PaaK working... nada.
I tried the backup code. The screen for input didn't come up.

I've got other stuff to do that works, so I carry my fob.

When this overly fragile, totally unnecessary nonsense works, let me know.

 

[skiingj]

Sorry to hear this OP. I gave up on Paak a few months ago. Too many similar embarrassing situations where it took me 5-10 minutes to get the car started. Ford has screwed us early adopters with only one key and terrible software engineering. At least their FP, BC, and OTA development teams all consistently suck.

 

[DevSecOps]

I just remembered I never set my backup start code for the new phone. This is a bad time to realize that.

Part 2 of my dilemma is that I live in rural county, so getting an Uber can take hours sometimes especially since California likes to pay people to NOT work and drivers are a rarity. I still haven't found a driver and it's been at least 20 minutes.

 

[ebeponyan]

Confirmed broken (including no prompt for backup start code) on Android 12 Pixel 4a. Ffs, I just got PaaK working again over the weekend.

 

[JohnnyForensic]

Yup. Can confirm it’s fine on iPhone. (iPhone 13 w/iOS 15.1.1)

 

[timbop]

This kind of crap is exactly why I do the "safe" thing and don't use PaaK.

 

[trutolife27]

Just tested on Google pixel pro android 12 and pakk worked for me when the the update. Could be the person's phone but I don't know. Tried again and worked fine hope yours starts working

 

[trutolife27]

This kind of crap is exactly why I do the "safe" thing and don't use PaaK.

Yep I always take my key fob in case. To many things could be the process problem.

 

[DevSecOps]

Just tested on Google pixel pro android 12 and pakk worked for me when the the update. Could be the person's phone but I don't know. Tried again and worked fine hope yours starts working

I have the exact same phone if you're talking about the 6 Pro and it didn't work. Either way. I could care less if PaaK didn't work. The backup start code not appearing is a MAJOR issue since it's sole purpose is if there's a key fob or PaaK failure this is a last resort. When the last resort doesn't work that's just bad.

For those that have a key fob and they lose it, or the battery dies or something else happens to it, the backup pass code is supposed to be there for any circumstance where the key (regardless of phone or fob) is lost, broken or malfunctioning.

 

[GoGoGadgetMachE]

Anything like "see I told you so" makes you sound like a dick here. Just so you're all aware.

Unless you have never lost a keyfob, and been stranded as a result (I have).

Actually, you still sound like a dick.

 

[SnBGC]

This kind of crap is exactly why I do the "safe" thing and don't use PaaK.

Same. I feel bad for anyone who is affected but the idea of relying on a cell phone to function in order to use my car isn't one that I accept. Historically, cell phones last around 2 years before they start to malfunction......and that is if everything goes as planned. Things usually don't go as planned for me.

 

[alexgorod]

So the new version of the phone app changed the car software and it doesn't display the pass code when the key or PAAK is not present? How else it can happen?

 

[DevSecOps]

So the new version of the phone app changed the car software and it doesn't display the pass code when the key or PAAK is not present? How else it can happen?

The FP app doesn't change the vehicle software. It could be a module update that changed it or an OTA that changed it in the car. This is the issue I'm most upset about. Like I said, PaaK - who cares. The backup code failure is what I'm livid about.

I think the likely situation here is that no one noticed that the backup code wasn't working because we had no need to use it.

Sponsored