CT3
Active Member
- First Name
- Joe
- Joined
- Aug 9, 2021
- Threads
- 1
- Messages
- 32
- Reaction score
- 28
- Location
- Santa Barbara CA
- Vehicles
- Ford Fusion Ford Flex
- Occupation
- Retirement
how do you know what version you have?
Sponsored
Ford determines when your vehicle is ready for OTA updatesMine just got 4.2.4 a few weeks ago. Is there something wrong with my car that it's receiving old updates?
Edit: never mind, I found the thread on FDRS lookups. I can check it out there
That is most likely because the batteries are cold when first starting off and therefore consumption is higher until they warm up. The higher consumption will calculate to more being required. Need to drive for a while until it warms up or set a departure schedule plugged into L2 and see if that fixes your problem.I have really become super reliant on that Apple Maps SOC% in how it updates while you travel to a destination. I'm spoiled with that from my previous Tesla. Why Ford omits that from their active Nav is beyond me. You have to jump through a few places in the Ford nav to see Arrival SOC%.
Anyway there are times where my Apple maps will not be reflecting accurate SOC%. Like in the morning it might show my trip to work will arrive at 52%. and I know that's way off because I usually arrive around 77 or 78%. I've tried rebooting Sync, my phone, Stopping and starting carplay and I can't for the life of me to figure out a solid way to get that data to update. If anyone knows please share!.![]()
No sorry for the confusion. I know what your referring to but this is a Carplay glitch where it must lose communication with the vehicle when it gathers the SOC% because the DIS shows the correct SOC but Apple Maps is way off. Also there is usually a message that pops up and a Nav Voice from Apple Maps that announces the Battery level may no longer be accurate. If I can figure out how to force Apple Maps to communicate with the Vehicle and re-fetch the data it would probably be back to working fine but I am not sure how to do that.That is most likely because the batteries are cold when first starting off and therefore consumption is higher until they warm up. The higher consumption will calculate to more being required. Need to drive for a while until it warms up or set a departure schedule plugged into L2 and see if that fixes your problem.
I don’t actually pay much attention to what sync version I have. The sync updates tend to either be behind the scenes items or updates to the UI that are readily apparent. Perhaps someone who follows that particular aspect of the update process can comment.Ah, brilliant -- thanks very much! That makes sense. So, is the version number that I have (4.0.23031) something that I should pay attention to?
Again, thanks!!