So I know Sync 3.4 has had this audio skip issue due to CPU usage forever. It doesn’t happen too often, but when it does it’s a bit annoying. Is there any way for me to downgrade to an older version that didn’t have this issue? 3.3 or 3.2? Any ideas? I know Ford fixing it is a lost cause at this point. Dealer just told me it was a software bug with no fix at the moment when I initially went in.
For reference I’m running 3.4 Build 23188
I’ve actually never had this once 3.4.21265 came out and don’t have it on 3.4.23188
I’ve got 145Gb of 320k mp3s on a SanDisk nano (exFAT format) and use BlueTooth from my phone.
What year/model and was this a 3.0-3.4 upgrade or is the car 3.4 native?
Did you have the issue before? Any way for me to downgrade to the version number you’re on? I’m in a 24’ Ford Maverick Lariat and it’s had the issue since the day i bought it. 3.4 native I believe. Didn’t notice it in test drives but in the following days it was more obvious.
Like me @warlock12118 is currently on version 3.4.23188, as you are.
I have never had an issue either with stuttering or skipping music with a 3.4.23188 upgrade or any previous version with my 2017 model. I have around 2300 songs MP3 on USB.
Have you tried a master reset?
The times I did experience it were on MFT conversions or G/H series APIMS that were running 3.2/3.4.x prior to 3.4.21265.
So nothing native 3.2/3.4.x
I’ve always felt that the folks claiming it to be a bug never looked at other possible causes, like cheap USBs, old USBs with bad blocks, bad USB ports, USB extension cables, wrong drive format, actual phone issues (nobody ever tries a good external BT speaker to see if they hear it there), etc.
A bit like the post we had a while back where the blame was put on Sync3 because the speed shown in Waze was way off from what the speedometer showed, the guy never bothered to actually run the app disconnected from Sync to see if the behavior changed and when he did, it behaved the same so it wasn’t Sync3.