Software Updates
4.3.2 2 nights ago, 4.3.3 last night. Anyone figure out what the tailgate improvements are they refer to???? I did verify that opening the electric tailgate still does not work via keypad like the non-electric
All it does is update the IPC strategy. It is to prep the truck for future updates. These updates don't give you anything different as far as anyone has been able to tell.
On the issues I saw with my iPhone and Apple Car Play after downloading 4.2.1 yesterday, I found the Cellular Data on my phone was toggled off. I did not do that and all was working fine driving 2 miles from home to the store. Turning that back on restored Apple Maps, but I am still having issues with Google Maps. If I bring up Google Maps on my phone, then it starts working on Apple Car Play. Closing the app on my phone causes Google Maps to freeze on the Apple Car Maps display.
I had not noticed it before, but when Apple Care Play is active, the WIFI connection on the phone is disabled.
I had not noticed it before, but when Apple Care Play is active, the WIFI connection on the phone is disabled.
I've been out of town for a week (not w/ my truck) and anticipated another update should be done or at least in the queue when I got back home. Sure enough 853588-1118232 (4.3.2) was available on 6/21. Decided to do some experimenting since the last status from PTS was "Trigger created on TMC" back on 6/21.
First thing I did was unlock and lock the truck from the FOB. That alone was enough to trigger the "OTA Trigger Available" deployment status but then nothing further (expected result).
I waited a little while and since there were no further changes, I decided to do a remote start. Wasn't sure if that'd be enough to trigger another event -- and turns out that it is not. No OTA deployment status changes.
While it was still "on" from the remote start I went out to the truck and "fully started" it. As soon as I did that it kicked off the next deployment steps (fully expected).
What I didn't expect is that when I hit the "Update details" button in Sync the second time it was reporting 4.3.2 had been installed - which was a total lie! (I had gone into that because I wanted to change the install time from 10pm to 1am since this particular update is marked in PTS as a vehicle inhibit update and I wanted it to get installed tonight.)
Proof that the "update details" screen was a lie is that when I come back inside and check PTS it still hadn't even downloaded the second of the 2 files in this update.
I wish I had set the update time to 2am because by time the files were downloaded and the deployment status got set to 'Update files are ready to activate" it was 1:02am. D'oh! :-D
No biggie but I just got a grimacing chuckle out of the sync screen reporting a power up version that hadn't actually been installed yet.
First thing I did was unlock and lock the truck from the FOB. That alone was enough to trigger the "OTA Trigger Available" deployment status but then nothing further (expected result).
I waited a little while and since there were no further changes, I decided to do a remote start. Wasn't sure if that'd be enough to trigger another event -- and turns out that it is not. No OTA deployment status changes.
While it was still "on" from the remote start I went out to the truck and "fully started" it. As soon as I did that it kicked off the next deployment steps (fully expected).
What I didn't expect is that when I hit the "Update details" button in Sync the second time it was reporting 4.3.2 had been installed - which was a total lie! (I had gone into that because I wanted to change the install time from 10pm to 1am since this particular update is marked in PTS as a vehicle inhibit update and I wanted it to get installed tonight.)
Proof that the "update details" screen was a lie is that when I come back inside and check PTS it still hadn't even downloaded the second of the 2 files in this update.
I wish I had set the update time to 2am because by time the files were downloaded and the deployment status got set to 'Update files are ready to activate" it was 1:02am. D'oh! :-D
No biggie but I just got a grimacing chuckle out of the sync screen reporting a power up version that hadn't actually been installed yet.
I've been out of town for a week (not w/ my truck) and anticipated another update should be done or at least in the queue when I got back home. Sure enough 853588-1118232 (4.3.2) was available on 6/21. Decided to do some experimenting since the last status from PTS was "Trigger created on TMC" back on 6/21.
First thing I did was unlock and lock the truck from the FOB. That alone was enough to trigger the "OTA Trigger Available" deployment status but then nothing further (expected result).
I waited a little while and since there were no further changes, I decided to do a remote start. Wasn't sure if that'd be enough to trigger another event -- and turns out that it is not. No OTA deployment status changes.
While it was still "on" from the remote start I went out to the truck and "fully started" it. As soon as I did that it kicked off the next deployment steps (fully expected).
What I didn't expect is that when I hit the "Update details" button in Sync the second time it was reporting 4.3.2 had been installed - which was a total lie! (I had gone into that because I wanted to change the install time from 10pm to 1am since this particular update is marked in PTS as a vehicle inhibit update and I wanted it to get installed tonight.)
Proof that the "update details" screen was a lie is that when I come back inside and check PTS it still hadn't even downloaded the second of the 2 files in this update.
I wish I had set the update time to 2am because by time the files were downloaded and the deployment status got set to 'Update files are ready to activate" it was 1:02am. D'oh! :-D
No biggie but I just got a grimacing chuckle out of the sync screen reporting a power up version that hadn't actually been installed yet.
First thing I did was unlock and lock the truck from the FOB. That alone was enough to trigger the "OTA Trigger Available" deployment status but then nothing further (expected result).
I waited a little while and since there were no further changes, I decided to do a remote start. Wasn't sure if that'd be enough to trigger another event -- and turns out that it is not. No OTA deployment status changes.
While it was still "on" from the remote start I went out to the truck and "fully started" it. As soon as I did that it kicked off the next deployment steps (fully expected).
What I didn't expect is that when I hit the "Update details" button in Sync the second time it was reporting 4.3.2 had been installed - which was a total lie! (I had gone into that because I wanted to change the install time from 10pm to 1am since this particular update is marked in PTS as a vehicle inhibit update and I wanted it to get installed tonight.)
Proof that the "update details" screen was a lie is that when I come back inside and check PTS it still hadn't even downloaded the second of the 2 files in this update.
I wish I had set the update time to 2am because by time the files were downloaded and the deployment status got set to 'Update files are ready to activate" it was 1:02am. D'oh! :-D
No biggie but I just got a grimacing chuckle out of the sync screen reporting a power up version that hadn't actually been installed yet.
Same happened to me and a few other members over at f150gen14 forum. Happened on 6/20. My screen says 4.3.2 installed, but PTS shows it never even downloaded a file before it failed with error code "ecuId":"1824". I've seen that error code countless times checking trucks for people, but I do not know what it means. Just like you said: The OTA trigger gets sent to the vehicle, but until you turn the truck on (either KOEO or KOER), it will not issue "consent" to the mothership for the file downloads to start. If the OTA requires the vehicle to be inhibited, once the files download, it will not install until your auto-updates schedule comes around, or unless you manually kick-off the install via the touchscreen. In my case, I didn't get that far and I still waiting for the OTA to be resent to me.
Both files downloaded successfully, hopefully it just does its thing (can't decide if I can un-lazy myself to go out and try to kick it off or just see what happens overnight tonight once the scheduled time comes around).
Among the other things Ford needs to get working better are the push notifications from FordPass. When I opened it up it was happy to tell me that a new PowerUp was installed but I'd rather have gotten a push notification 10 minutes prior that an update had been installed. (Yeah, yeah... wishful thinking!)
Among the other things Ford needs to get working better are the push notifications from FordPass. When I opened it up it was happy to tell me that a new PowerUp was installed but I'd rather have gotten a push notification 10 minutes prior that an update had been installed. (Yeah, yeah... wishful thinking!)
Gen Y or Z?

And not that it matters, but I'm a quinquagenarian.









