Sync 3 Memory Issue
Jesus guys. This is a nothing but a SYNC update issue. The idiot that programmed it screwed up and it will a folder completely up and the APIM can no longer read/write to it and that is the issue. The new update seems to solve the problem.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
5 Year Member
Joined: Mar 2015
Posts: 2,456
Likes: 789
From: Anchorage, AK
Jesus guys. This is a nothing but a SYNC update issue. The idiot that programmed it screwed up and it will a folder completely up and the APIM can no longer read/write to it and that is the issue. The new update seems to solve the problem.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
5 Year Member
Joined: May 2019
Posts: 112
Likes: 27
Jesus guys. This is a nothing but a SYNC update issue. The idiot that programmed it screwed up and it will a folder completely up and the APIM can no longer read/write to it and that is the issue. The new update seems to solve the problem.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
I know the thread is really long but it’s worth the read as you begin to understand what the problems are, the early solutions that were not a fix, and then a work around, and now the new update.
Check posts #381 & #393. My guess is the update is one that got leaked from Ford or somebody coded it themselves. You can continue to wait for the gods at the blue oval to release the update via their website or fix it yourself.
Last edited by djfllmn; Aug 7, 2023 at 04:12 PM. Reason: Language
Member
Joined: Apr 2023
Posts: 86
Likes: 59
From: Oldsmar, FL
Mine too. It was frustrating, but in the grand scheme of things, far lesser of a problem than it could be. I did the jailbreak/update and the issue is resolved. No big deal.
5 Year Member
Joined: Aug 2012
Posts: 152
Likes: 14
Re latest Sync sw
I logged into my Ford pass, and it shows at the I have latest version: 3.4.22251. Confirmed with the version on my truck.
There is no option to update to a newer version.
Good news is Ford is replacing my radio and my APIM under extended warranty
I logged into my Ford pass, and it shows at the I have latest version: 3.4.22251. Confirmed with the version on my truck.
There is no option to update to a newer version.
Good news is Ford is replacing my radio and my APIM under extended warranty
Last edited by Soundrulz; Aug 6, 2023 at 10:12 AM.
Junior Member
Joined: Jan 2017
Posts: 4
Likes: 2
Add me to the list with the same problem. My truck is a 2019 F150 Limited with 54,000. The problem started in May at about 49,000 miles. I've read this lengthy thread and I will wait to see what Ford does. I did file a complaint with the NHTSA and a complaint to Sync Customer Service.
5 Year Member
Joined: Nov 2017
Posts: 922
Likes: 447
From: New England
No, but the symptoms of those bugs can and do.
In this case, it appears that the 3.4.22251 release has a flaw that causes the log files to not self-purge. After a while, the partition that they're stored in fills up. Apparently, this partition is also responsible for storing certain preferences including the responses to the initial setup questions. The result is a system that can no longer remember the last radio station, number of preset pages, whether the diagnostics prompt was accepted, the rear view camera delay setting on/off, etc.
In this case, it appears that the 3.4.22251 release has a flaw that causes the log files to not self-purge. After a while, the partition that they're stored in fills up. Apparently, this partition is also responsible for storing certain preferences including the responses to the initial setup questions. The result is a system that can no longer remember the last radio station, number of preset pages, whether the diagnostics prompt was accepted, the rear view camera delay setting on/off, etc.