Thank you, we will be expecting your feedback.
The reason I’m saying this is because the flickering has been an issue from the early 3.4 versions, which was resolved for most models in later builds but Focus and Kuga never got it solved.
Your profile says you have a 2017 Focus, which of course should be affected by the flickering.
If 3.4.22110 solves your issue again, then it’s a good workaround for other Focus owners to try!
The auto-dim toggle has been reintroduced several versions ago, but there is some vehicle-specific conditional logic that hides the UI element for the toggle switch. Somebody on FMODS figured out it’s as easy as hard-coding the condition to always be “true” to make the switch appear on all vehicles, and I’ve confirmed it is indeed functional and not just cosmetic. It really does avoid screen flicker on my 2014 Escape and functions just the same as it had on much older Sync 3.4 builds.
[LINK REMOVED]
I keep seeing people on Cyanlabs claiming the toggle is gone, but I think it’s just lack of awareness, since this is a fairly recent discovery. The workaround involves jailbreaking and installing a mod to enable an SSH daemon to modify the required line in DisplaySettings.qml. I don’t think Sync has any native text editor like pico or nano, so the only option is to SFTP the file to your computer, modify it, and SFTP it back to the Sync system. The SSH mod includes the required crypto key to allow SFTP to work (Sync apparently has no password for SSH / SFTP, so a key is used instead).
I know all this probably sounds like gibberish if you aren’t familiar with SSH. It should be extremely easy to also write an autoinstall script so the change can be applied just like any other mod by simply inserting a USB key to perform the changes, instead of having to manually edit the file, but nobody had written one so far. I’d write it myself but am worried about being liable if I somehow messed up other people’s APIMs.
I’m also curious if the Cyanlabs team can auto-patch DisplaySettings.qml. There’s a “community changes” list whenever I update Sync, and I never quite understood what that meant. Is it just changes made by Ford’s engineering team that the community notices, or can the community actually make proposed changes that get applied automatically when you create the update USB stick? If the latter, I feel this patch should be included in the future. I really fail to see any actual downsides to forcing this dim toggle to always be present…
As far as CyanLabs is concerned this toggle has gone, if the workaround is to modify a system file in order to allow the feature it is gone, we do not condone nor allow discussion or sharing of modified IP of which JailBreaking includes.
Unfortunately the first one, just things the community notices
I’ve just confirmed while driving to work today, the issue is definitely not as obvious on this version for some reason and I’m not sure why the behavior is different since the majority of the versions are the same. I’ll stick to 3.4.22110 unless there’s significant changes that occur in the later versions or if they ever reintroduce that toggle for auto brightness.
As far as the flickering goes, there seems to be zero change on my C-Max in that behavior. Definitely has not improved any at the very least.
As far as the auto-dim toggle, at minimum a couple of us C-Max owners have been able to confirm having an updated APIM calibration (My H series is on the -DA level calibration if memory serves? I’d have to load up Forscan again to check.) brings it back. May or may not be the same on the other affected vehicles.
Just updated to 3.4.22251 on my MY18 Raptor. No issues reported so far.
Pics in my update thread:
SiriusXM station icons no longer disappear in the preset row upon a restart. Before they would be text-only until actually listening to a station. Now the logos are present before even listening to a station.
does this version still have the same USB song skip(sometimes at the end of a song it will skip the next song ie: end of song 1 skips 2 goes to 3) and song hiccup(1 or 2 seconds of the song get cut several times while listening) problems as all the other versions?
these problems are the reason why I can’t get any version over 19101 although I still get the song skip issue with this version.
19052 doesn’t have these issues but it has an issue seeing the USB drive when starting the car so 19101 is a happy medium.
I updated to the latest version 22251, and I noticed that the information subtitles, for example radio , gps and others read more sofft, or I will be seeing it wrong. Among other indications of pairing between the cell phone.
I don’t see the climate icon on the screen, Ford Kuga Titanium
Have i done something wrong ?
Thanks
Andy
If you didn’t have it before you won’t have it now, add it with forscan.
After update 22251 i found in my sync3.4 with navi eu and bang olufsen and dab radio that usb playback has a lot of problem like jumping and make noise and “digital noise” so it is a big problem in this version. I have make master reset and battei off to make system reboot and also forscan reset for the audio system.
thanks
Do need to use goolge for the codes ?
Use our database
The center navigation between the Speedo dials doesn’t show roundabouts if they have multiple exits. Also other roundabout symbols show the wrong direction.
This is not anything that cyanlabs can fix but if others report the same I’ll add it to the issues list.
Clock and compass issues still exists, Galaxy 2017 
2018 non-nav USA F150 Lariat here.
Did not have clock and compass issues on 22200, do not have them on 22251.
As a reminder, for those of us with non-nav this is how you upgrade:
Follow all other instructions for install, be sure to factory reset at the end.
I updated to this version today and I lost the radio logos when updating to this version, has this happened to anyone else?