UK 2015 Focus ST 3.5 - Retrofitted Sync3 sucessfully updated from 3.4.23188. Took about 15-20mins without issues. Maps were not updated at same time. No issues so far.
Have been been running 3.4.26057 for a few days now on my retrofitted system that was supplied with 23188 pre-installed and the upgraded thinner screen. I didn’t master reset after upgrading as it wasn’t a major upgrade and it seems to have been running ok with no obvious issues / errors but if I do encounter any…I may try a master reset to see if it helps.
All the standard Ford Sync3 audio and navigation functionality seems to be performing as it did before and the performance seems comparable. Only minor issue I have noticed is that FM Radio 2 logo is missing, but is correctly displayed on the DAB version. Tried re-scanning but hasn’t cleared the issue. I guess a Master Reset might…but not worth the hassle of setting it back up again lol.
I mainly use wireless Android Auto with an Android Auto / Apple CarPlay unbranded USB dongle that was supplied with the Sync3 unit. One thing I have noticed with 26057 is that wireless Android Auto seems to connect noticeably and consistently quicker than it did with 23188. I also used to experience a very occasional USB error message during Sync3 system power up which sometimes had to be manually acknowledged. This definitely slowed the Android Auto start up so assume it was the dongle that triggered it. On 23188, this always sorted itself out automatically and eventually Android Auto would just start. To be fair the only times I really noticed this issue was when it took so long for Android Auto to launch that Sync3 would default back to an alternative Audio source, which was often much louder than I was expecting. Since installing 26057, I have not had any of these errors…so far.
Android Auto performs pretty much as it did before and I am very happy with how this really makes the system a joy to use. The only minor issue is with Google maps and the repeated navigation info on the dash, which is still a bit patchy. With 23188, it would always start displaying navigation info on the centre dash but more often than not, this would give up at some point during the journey. I initially though this must be an issue with Google Maps / Android Auto updates and occasionally an update would improved the reliability of the navigation repeats but then a few days later it would regress again. There has never seemed to be any obvious trigger points for this behaviour and I had no idea if it is an Android Auto, Google Maps or Sync3 (or combined) issue.
With 26057, however, things definitely seem to have improved…but it is still not perfect. As such at the start of a navigated journey you do get all the correct repeats but if your journey includes a long element without any junctions, it seems to give up and returns my repeater screen to the non-navigation display. With 23188, this remained until the “you have reached your destination” notification, which did always display correctly on the dash repeat screen. On 26057, it still seems to give up on longer straight elements of a route but if you proceed through a junction and there is an additional direction change required on the route then the dash repeater does seem to spring back to life again but can revert again if you have more long straight elements. It is definitely better than 23188 so I am hoping Ford will continue to tweak this and maybe we will see another update appearing? Whilst testing, I did try using the Sync3 navigation without Android Auto and this repeated navigation info on the centre dash screen without any problems at all. I have also tried using Android Auto both in wired / wireless mode and there is no notable difference.
Such a weird release cycle for Ford though and will be interested to see if any other updates appear? If Google is to be believed, 23188 was released Sep 2023, is that right? so almost a two year gap until 26057 popped up.
I just updated our Mondeo and Puma to the new 3.4.26057 update. Everything seems in order only the FMods Video player mode V3.0 or V 3.2 does not seem to work. Has anybody else noticed this. Was something changed so it interferes with the logic of the player mod?
That date is correct.
Keep in mind Ford has not made 26057 a GA release, its currently a dealer only install.
Ford does not do regression testing of builds on non-supported vehicles.
I’m only a day in, but our 2019 Expedition upgraded from 3.0.x to this build successfully. So far so good with no signs of regression.
I went from stock 3.0 to 3.4.26057 via Syn3 today and this solved so many issues! I believe some of my files had been corrupted prior to installation. When I used to try the voice assistant. It would display a pop up about not being recognized. Now it works without a hitch! Android auto is awesome since I use a Samsung as my daily driver. I just wanted to thank everyone for their hard work. It is so cool people are taking the time to give these APIMs the love they deserve!
Did you do a master reset after the upload to the car?
If not that is probably the reason you had to turn the car off and on again to load the maps.
I did not good catch! I just edited my comment.
No need to google it, 23188 is the 188th day of 2023, 057 is the 57th day of 2026, obviously build date and release date will be a bit apart.
I may have actually found a bug, so looking for confirmation.
It looks like .26057 doesn’t look at the volume ID of a USB with music on it and just uses the label and model.
This could just be a bug with large volumes (I run 256 GB SanDisk Ultra Fits), so here’s the scenario, 2 identical units, both have around 17k of mp3s, same volume name, (different GUIDs show in Linux and Windows) one I had been running for 2 months, dropped in the other with additional mp3s, same directory format, small other changes (eg Album name had say a random upper case character, mp3 had a typo in the name), ran it for 3 weeks and it still pulls up the old directory structure and names, but shows the added mp3s.
Pull the USB on seperate days when media is open and I’m on the screen to force a re-index, do that with both USBs only 1 actually re-indexes.
Both USBs tried in same model year combination running .23188 and they show correctly, do a master reset and the “new” structure turns up after a reindex, pop in the other USB and it never indexes.