How to downgrade OTA?

[PWRPNY]

Got an OTA for something about PAAK and customer satisfaction so thought I should update it but um, yeah.... Now I experience "key not found" almost constantly, car no longer auto locks when I walk away and I cannot connect android auto wirelessly any more. Nice "update"?

Anyone know how to roll it back?

Oh, and first post!

Sponsored

 

[generaltso]

Anyone know how to roll it back?

That‘s not really a thing.

But welcome!

 

[Gimme_my_MME]

Got an OTA for something about PAAK and customer satisfaction so thought I should update it but um, yeah.... Now I experience "key not found" almost constantly, car no longer auto locks when I walk away and I cannot connect android auto wirelessly any more. Nice "update"?

Anyone know how to roll it back?

Oh, and first post!

I would suggest removing your phone Bluetooth pairing as well as PaaK and resetting them up

 

[HGxxx]

Before you do anything, you can delete the existing key, in vehicle go to settings and general settings and reset all PAAK keys and reconnect

 

[PWRPNY]

Thanks for the replies. I will do the full "reboot" as suggested and post back.

It's annoying the "free" apps just work but the $73k app breaks with updates.?

I hope some software company makes a 3rd party system that works with Ford's "hardware" as it doesn't seem like Ford is very good at software.

 

[hprose]

Thanks for the replies. I will do the full "reboot" as suggested and post back.

It's annoying the "free" apps just work but the $73k app breaks with updates.?

I hope some software company makes a 3rd party system that works with Ford's "hardware" as it doesn't seem like Ford is very good at software.

Whenever you get an OTA, a Ford Pass Update or an update to your phone OS you should reboot your phone. Virtually all PAAK, Car Play or AA issues are phone related. The phone is the transmitter and it doesn’t always transmit. I have never used the fob but occasionally I have to unlock my phone or bring Ford Pass to the foreground or on rare occasions reboot my phone. Same with GM and other Fords. These are all computers and we have all had to reboot those from time to time. If you read the Tesla forum they have similar complaints.

 

[dtbaker61]

Whenever you get an OTA, a Ford Pass Update or an update to your phone OS you should reboot your phone. Virtually all PAAK, Car Play or AA issues are phone related. The phone is the transmitter and it doesn’t always transmit. I have never used the fob but occasionally I have to unlock my phone or bring Ford Pass to the foreground or on rare occasions reboot my phone. Same with GM and other Fords. These are all computers and we have all had to reboot those from time to time. If you read the Tesla forum they have similar complaints.

this is exact;y why I turned off OTA auto-updates.... I have not been impressed with Ford's software update stability; too many regressions, surprises, and setting resets for my taste. I haven't seen anything in Release Notes for available updates that I want.

the only times I've had problems with PAAK over the last 2 years have been from Phone updates tweaking bluetooth. Once I had to update FordPass, and once I had to delete and re-install Fordpass and re-configure PAAK from the beginning.

I'd suggest:
- update FordPass app on phone
- reboot phone
- restart FordPass
- turn BT on phone off, and back on, make sure that FordPass shows 'connected' when you are within range.

if not.... THEN you might consider deleting and re-installing and re-configuring PAAK.... but plan on a good hour of farting around to make sure everything is deleted before re-installing.

https://www.macheforum.com/site/thr...on-android-to-enable-a-backup-startcode.4544/

 

[Kaplan]

Got an OTA for something about PAAK and customer satisfaction so thought I should update it but um, yeah.... Now I experience "key not found" almost constantly, car no longer auto locks when I walk away and I cannot connect android auto wirelessly any more. Nice "update"?

Anyone know how to roll it back?

Oh, and first post!

Same as my 2021, spoke to Ford customer Service. Need to reprogram the existing modular. Need to take it in for service. Gave me an reference #for the reprograming.

 

[Mike G]

Y'all know that OTAs sometimes cause things to not work correctly for one or two keycycles right?

Like getting an OTA and suddenly Rear Brake Assist declares it's not available...but comes back after a 5 minute drive, things like that?

This happens both with FDRS updates and OTAs...Ford just doesn't tell you it's gonna happen. There are a lot of posts on these forums where people got an OTA, something stopped working...and the next day it was all back to normal. Programming causes interruption on the car's network(s) that result in things getting temporarily "reset" or disconnected. Like everytime there's an OTA for the powertrain modules people suddenly notice that the guess-o-meter is wildly out of wack, but gradually regains it's ability to estimate range again.

 

[PWRPNY]

Whenever you get an OTA, a Ford Pass Update or an update to your phone OS you should reboot your phone. Virtually all PAAK, Car Play or AA issues are phone related. The phone is the transmitter and it doesn’t always transmit. I have never used the fob but occasionally I have to unlock my phone or bring Ford Pass to the foreground or on rare occasions reboot my phone. Same with GM and other Fords. These are all computers and we have all had to reboot those from time to time. If you read the Tesla forum they have similar complaints.

I said "reboot" in regards to the suggestions to delete PaaK and phone from the car and setup again in reference to the running joke about tech support always telling to reboot to fix any issue.

I restart my phone whenever AA won't connect wirelessly so at least 10 times since the OTA.

The "reboot" suggested above is the equivalent to uninstalling an app, reinstalling it and making an entirely new account.

Basically, all settings lost and account banned thanks to an OTA.

 

[PWRPNY]

Y'all know that OTAs sometimes cause things to not work correctly for one or two keycycles right?

Like getting an OTA and suddenly Rear Brake Assist declares it's not available...but comes back after a 5 minute drive, things like that?

This happens both with FDRS updates and OTAs...Ford just doesn't tell you it's gonna happen. There are a lot of posts on these forums where people got an OTA, something stopped working...and the next day it was all back to normal. Programming causes interruption on the car's network(s) that result in things getting temporarily "reset" or disconnected. Like everytime there's an OTA for the powertrain modules people suddenly notice that the guess-o-meter is wildly out of wack, but gradually regains it's ability to estimate range again.

That seems really silly and not very confidence inspiring. It's got an electronic start button so you are saying they just didn't code in a couple of restarts?

 

[Mike G]

That seems really silly and not very confidence inspiring. It's got an electronic start button so you are saying they just didn't code in a couple of restarts?

Well it's just something that over time I've gotten used to. It's not just one big system with one button that controls it all. It's between 43 to 45 individual hardware modules (depending on variants) over 6 different networks, all connected. Maybe they should think about coding in some network reset routine at the end of an update process that sets all modules back to an initialized state. I don't know if that would help or make things worse.

The car's network is always "on" to some degree. Even when parked for days. So an OTA comes along and some modules are shut down or communication on some of the internal nets are interrupted, and the update completes....but because the car is not fully running, the modules that were shut down for the OTA process may be in a different state than normal. So when you press the start button the rest of the car wakes up and the systems need to reconnect as the car gets reoriented and network connections are re-established.

 

[PWRPNY]

Well it's just something that over time I've gotten used to. It's not just one big system with one button that controls it all. It's between 43 to 45 individual hardware modules (depending on variants) over 6 different networks, all connected. Maybe they should think about coding in some network reset routine at the end of an update process that sets all modules back to an initialized state. I don't know if that would help or make things worse.

The car's network is always "on" to some degree. Even when parked for days. So an OTA comes along and some modules are shut down or communication on some of the internal nets are interrupted, and the update completes....but because the car is not fully running, the modules that were shut down for the OTA process may be in a different state than normal. So when you press the start button the rest of the car wakes up and the systems need to reconnect as the car gets reoriented and network connections are re-established.

I guess they'll figure it out with more time. ICE cars can reset all CAN/LIN/Flexray/Ethernet controllers with gateway commands.

Sponsored