Issue with XM preset slider

jon.nielsen · 11 February 2025 13:51

Hello, I have a 2018 Ford F150 with Nav. Initially upgraded from Sync 3.0 to Sync 3.4.23188. The upgrade went fine, but had an issue where the XM slider for the presets not aligning properly. If I slightly move the slider, it does correct itself. This problem occurs everytime I start the truck or leave and return to the radio view. I tried 3 versions of Sync 3.4 (3.4.19101, 3.4.21265, 3.4.23188) and they all do it. Also tried Master resets. Does anyone else have this issue? I tried going down to 3.3.19052 but was missing like 75% of the XM logos, even after several months of using it.

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.21265

New SYNC Version: 3.4.19101

Do you have a error message, if so what is it?
No

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.13.0.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.13.0.0
  Branch: Stable
  Operating System: Microsoft Windows 11 Pro (2009)
  
  PREVIOUS CONFIGURATION
  Version: 3.4.21265
  Region: NA
  Navigation: True
  Install Mode: Auto-Detect (autoinstall)
  Install Mode Overridden: False
  My20 Protection Enabled: Auto-Detect
  
  DESTINATION DETAILS
  Mode: Drive
  Model: SanDisk Ultra USB Device
  Size: 28.6GB
  FileSystem: exFAT
  Partition Type: MBR
  
  AUTOINSTALL.LST
  ; CyanLabs Syn3Updater 2.13.0.0 Stable - Autoinstall Mode - Sync 3.4.19101 NA
  
  [SYNCGen3.0_ALL_PRODUCT]
  Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
  Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
  Item2 = GRACENOTES - 4U5T-14G423-CA_123766.tar.gz
  Open2 = SyncMyRide\4U5T-14G423-CA_123766.tar.gz
  Item3 = APPS - 5U5T-14G381-AP_1555085337000.TAR.GZ
  Open3 = SyncMyRide\5U5T-14G381-AP_1555085337000.TAR.GZ
  Item4 = VOICE - 5U5T-14G391-CL_1580862907000.TAR.GZ
  Open4 = SyncMyRide\5U5T-14G391-CL_1580862907000.TAR.GZ
  Options = AutoInstall
  
  
  FILES (4)
  PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
  4U5T-14G423-CA_123766.tar.gz (724.2MB)
  5U5T-14G381-AP_1555085337000.TAR.GZ (891.2MB)
  5U5T-14G391-CL_1580862907000.TAR.GZ (385.4MB)
  
  LOG
  [2/10/2025 3:15:41 PM] Selected Region: NA - Release: Sync 3.4.19101 - Map Version: Keep Existing Maps 
  [2/10/2025 3:15:41 PM] Install Mode: Auto-Detect (autoinstall) Forced: False 
  [2/10/2025 3:15:41 PM] MY20 Protection: Auto-Detect 
  [2/10/2025 3:15:41 PM] Formatting USB drive
  [2/10/2025 3:15:41 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
  [2/10/2025 3:15:50 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [2/10/2025 3:15:50 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
  [2/10/2025 3:15:50 PM] Checking Existing File: 4U5T-14G423-CA_123766.tar.gz 
  [2/10/2025 3:15:52 PM] Validated: 4U5T-14G423-CA_123766.tar.gz (Skipping Download) 
  [2/10/2025 3:15:52 PM] Checking Existing File: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:15:52 PM] Downloading: 5U5T-14G381-AP_1555085337000.TAR.GZ
  [2/10/2025 3:20:01 PM] Validating: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:20:03 PM] Downloaded: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:20:03 PM] Checking Existing File: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:20:03 PM] Downloading: 5U5T-14G391-CL_1580862907000.TAR.GZ
  [2/10/2025 3:23:05 PM] Validating: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Downloaded: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Preparing USB drive
  [2/10/2025 3:23:06 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [2/10/2025 3:23:06 PM] Checking Existing File: 4U5T-14G423-CA_123766.tar.gz 
  [2/10/2025 3:23:06 PM] Copying: 4U5T-14G423-CA_123766.tar.gz 
  [2/10/2025 3:23:28 PM] Validating: 4U5T-14G423-CA_123766.tar.gz 
  [2/10/2025 3:23:30 PM] Copied: 4U5T-14G423-CA_123766.tar.gz 
  [2/10/2025 3:23:30 PM] Checking Existing File: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:23:30 PM] Copying: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:24:33 PM] Validating: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:24:37 PM] Copied: 5U5T-14G381-AP_1555085337000.TAR.GZ 
  [2/10/2025 3:24:37 PM] Checking Existing File: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:24:37 PM] Copying: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:25:17 PM] Validating: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:25:18 PM] Copied: 5U5T-14G391-CL_1580862907000.TAR.GZ 
  [2/10/2025 3:25:18 PM] Generating Autoinstall.lst
  [2/10/2025 3:25:18 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

warlock12118 · 11 February 2025 23:54

It’s not actually a Sync issue.
The problem is that the ACM wants to provide the logos loaded in it from the factory and the identifiers don’t match what is in Sync3.3+

So, the logos sent by XM don’t match the identifiers in the ACM, so what you get is working logos for things that haven’t changed their logo in forever like Classic Vinyl, or stations that have moved or are seasonal (eg Holly) while others like the Highway either have to old logo or none at all.

I’ve had a couple of cases where I was able to zero out the presets in the ACM with ForScan followed by a Master Reset where they came in and others where I had to plug in a different ACM which caused the XM not registered flag to pop on the APIM. Once that happened everything cleared and I could put back the original one.

jon.nielsen · 12 February 2025 00:58

Ok thanks for the info! You think this would just be isolated to just 3.3 versions? 3.4 seems fine with the logos, just the preset slider. If I can’t get that fixed with 3.4, I’ll probably go down to 3.3 and try your suggestion.

warlock12118 · 12 February 2025 13:22

Have you made any other changes with ForScan to the APIM?
Have you tried pulling the battery cable for ~30 minutes to force a full cold reboot of all of the modules?

jon.nielsen · 12 February 2025 14:54

I have not used ForScan yet. Also did not disconnect the battery for a reset. Do you think that may fix my issue with 3.3 or 3.4? I can try that tonight.

warlock12118 · 12 February 2025 15:27

It’s possible that it will fix it.
Sometimes when you do an unsupported mod like this you have to take everything cold so that nothing is out hanging on the data bus.
It takes around ~25 minutes for the BCM to completely reset, APIM 15-20 minutes, so ~30 minutes is a safe amount of time

jon.nielsen · 12 February 2025 15:47

Ok I will try this on 3.4 and will report back. Thanks.

jon.nielsen · 13 February 2025 15:48

This appears to have fixed the issue! I’m going to move back up to 3.4.23188 and will reply if I have any issues. Thanks!

jon.nielsen · 13 February 2025 22:08

Nevermind it still does it. Think I should try updating the ACM using forscan?

bill32399 · 13 February 2025 22:23

So you have never used Forscan to change any settings on your ACM or APIM? Did you replace the ACM? I feel were missing something here as I have seen this before but it was a bad AB setting with Forscan on a newer ACM.

warlock12118 · 13 February 2025 22:26

If this stopped with 3.4.21265 stay at 3.4.21265
The ACM would be a calibration update with ForScan 2.4.x which would be a paid license and you might not be able to get that due to the Russian sanctions.

BTW if/when you do update the calibration be prepared for a momentary loud boom & pop from the speakers, you haven’t broken anything its just the internal hardware loading the new calibration.

jon.nielsen · 13 February 2025 22:50

Correct, I have never used forscan. As far as I know nothing has been replaced. If that’ seems to be the next course of action, I’ll order the cable and do the update if possible.

Just weird that the update went fine and this doesn’t appear to be a common issue. I saw one other person with this exact issue from a thread several years ago, but had no resolution.

bill32399 · 14 February 2025 03:46

It does not do it with the radio presets?

warlock12118 · 14 February 2025 12:59

From the pic, beyond the more common XM logo issue it appears the preset buttons don’t present correctly on the screen.

jon.nielsen · 14 February 2025 15:04

The missing XM logo issue seems to be isolated to 3.3 for me. Even some old stations such as Classic Vinyl didn’t have a logo, but Lithium did.

With 3.4, I have the station logos but the preset slider alignment is off as seen in my initial post.

F150Chief · 10 March 2025 22:09

This happens more than you think. You can easily fix this by rewriting the APIM asbuilt using FORScan. The free version and a USB OBD adapter is required.

jon.nielsen · 10 March 2025 23:30

Ok thanks, I can give that a try. I’ll probably try to find some Forscan tutorials before I go poking around in there.

F150Chief · 11 March 2025 02:12

Look in the Guides and Information sections of this forum.

jon.nielsen · 22 March 2025 00:25

So I got the adapter and rewrote the apim and ACM as-built in forscan, but did not fix the preset slider issue. Any other suggestions or thoughts?

F150Chief · 22 March 2025 03:12

Reset the ACM and then APIM with FORScan. This will be in the tools menu (wrench icon). Clear the DTC’s and see if that clears it up.