Anthony
Well-Known Member
- First Name
- Anthony
- Joined
- Feb 6, 2019
- Threads
- 43
- Messages
- 693
- Reaction score
- 1,278
- Location
- Connecticut
- Vehicle(s)
- 2019 Ford Ranger XLT FX4 SCrew
- Occupation
- COO
- Vehicle Showcase
- 1
Sponsored
Yeah, it is weird. My wife's 2018 Edge does not have the Sirius logos for each channel, but my 2019 Ranger does. Why??!?!They have always done this! Very disappointing year after year to only get current if you own a new model. I know I change vehicles more than average and each year you only get the version it came with. IE 2018 3.3 and 2019 3.3.
Could be hardware. Maybe newer vehicles have upgraded hardware or there is different hardware between vehicles.I am too am curious and beyond a business decision would there be any other technical reason why FORD would not update 2019 Sync3 systems to the latest iteration of the software?
So without the icon how can you control climate functions like fan speed. Did you go back to 3.3My understanding is that the APIM for v3.x of Sync is update capable within the Sync v3 versions. We will not be able to go to Sync 4 as the APIM hardware is different. In fact, the upgrade process (commonly referenced as USB1, USB2 & USB3) has a reformat utility on USB1 to get the Sync File System formatted correctly. If you're running v3.2 or newer already, this step is not required. Even though I was already at v3.3 before upgrading to v3.4, I went ahead and did the reformat in an attempt to eliminate the missing Climate icon. It didn't help.
I can't find any references to my particular problem anywhere but most of the articles are from people with F Series trucks, not 2019 Rangers. So if anyone with a 19 Ranger has done the v3.4 upgrade, was it successful? If yes, can you post the process you followed if different from the F Series posts reference in this thread? Thanks
It is potentially possible that a subtle hardware difference from Ranger to F150 APIM may have tripped off the Climate icon when going to v3.4 but it would need confirmation from another member here to confirm if they had same issue.