TheBraydenKyle
Well-Known Member
- First Name
- Brayden
- Joined
- Aug 5, 2022
- Threads
- 8
- Messages
- 87
- Reaction score
- 111
- Location
- Austin, TX
- Vehicles
- 2022 Mustang Mach E Premium ER RWD
- Occupation
- Sales Management
I’m still rocking 3.6.1
Sponsored
Their deployment process is broken. There shouldn’t be this much disparity between versions on cars that are on the road. This is ridiculous. I’m still on 3.5.4, and I’m starting to wonder if I’m missing updates that are blocking. Imagine if Apple deployed their OS’ like this. 100% Unacceptable.I’m still rocking 3.6.1
The 4.2.x updates are a re-release of software that was already on the car, but with bug fixes. Ford rarely ever lists bug fixes though, so they probably just needed to write something and chose this lesser known feature to highlight.really weird, wonder if this is not for 2023 machines. my car already had the voice feedback thing from the factory.
It’s been two years, it’s not happening. Ever.On the Frunk button thing for '21J1...here's the part I don't understand....
It would have been SO easy to fix.
Search all the '21J1 asbuilts and update the one segment that adds the frunk softbutton to Sync. This is a server update. They can do it from their end.....just like they corrected the BCM data for the TPMS system on the new Lightnings they sent out with the wrong tire low pressure warning threshold.
Then push an OTA for the BCM and GFM updates as a technical update just for those cars. Unless there's something else I'm not aware of that should update this issue for everybody who has it.
The only thing I can think of that's keeping them from doing this is that they aren't confident that either a BCM or GFM update will actually work OTA. Why else would they put a procedure into FDRS specifically for the techs to enable that softbutton on the Sync screen?
![]()
If doing this by OTA isn't an option then @Ford Motor Company ought to identify those '21J1 vehicles in the asbuilt database that specifically still do not have the Sync frunk softbutton enabled and send the owners a notification letter of a Customer Satisfaction Program that will enable them to get the BCM/GFM updated and the frunk Sync screen softbutton enabled by a tech at Ford's cost.
I think if they put one...maybe two interns on this they could have it done by this time next week (if you can get them off their phones).
Agreed. On the other hand, after seeing so many people complain about the newer updates, perhaps I should be satisfied with the outdated version.Their deployment process is broken. There shouldn’t be this much disparity between versions on cars that are on the road. This is ridiculous. I’m still on 3.5.4, and I’m starting to wonder if I’m missing updates that are blocking. Imagine if Apple deployed their OS’ like this. 100% Unacceptable.
Happened to me on a failed install FP noting car stuck where it updated for a month. No ford pass no conductivity to the car but Bluetooth (paak) continued to work. Do you have control of your conductivity settings in sync or are they locked? Had to be fix in the shop here.Got 4.2.4 installed last night to update the Telematics Control Unit. Now my car won't phone home to the Ford mothership.
![]()
FordPass is stuck at last nights SOC reading as well (16 hours ago). I drove the car 30 miles to work today....no update. Force close FP and rebooted phone. Weird.
![]()
Are you going to try the TCU fuse?Got 4.2.4 installed last night to update the Telematics Control Unit. Now my car won't phone home to the Ford mothership.
![]()
FordPass is stuck at last nights SOC reading as well (16 hours ago). I drove the car 30 miles to work today....no update. Force close FP and rebooted phone. Weird.
![]()
That's a thought. I'd have to look up how to do that.Are you going to try the TCU fuse?
Hoping mine was not a matter of pulling a fuse. Why did I wait a month to get it in for them to do that?Are you going to try the TCU fuse?
Thanks for the recommendation. It worked!!Are you going to try the TCU fuse?
I did the fuse pull awhile back and it worked, but then the issue kept coming back and I was pulling the fuse every few days. I eventually deleted PaaK cleared out my phone and re-paired everything, I havent gotten that issue since. It was one of the early 4.1.x updates that did it to me.Thanks for the recommendation. It worked!!