I need help reviewing my AsBuilt configuration (APIM / BdyCM / ACM).
I upgrade SYNC 2 8” with NAV to SYNC 3 8” with NAV in my Ford Escape 2015 but have issues with few errors and no sound with Bluetooth call
Loaded .abt for APIM and BdyCM
Configured using CyanLabs AsBuilt For both. I check every number!
Set speakers, navigation, Bluetooth hands-free (BdyCM Main setup)
Selected in SYNC settings Use phone melody
Call Audio Behavior (4 scenarios): Bluetooth call both→ no sound Android Auto call → no sound iPhone Bluetooth call → no sound iPhone CarPlay → sound works (ringtone + call audio)
Important:
Microphone works in all cases (people hear me)
Bluetooth music works fine
Only call audio routing to speakers is broken
Feels like I tried all SYNC settings already
Please help check which AsBuilt parameters control call audio (HFP routing).
Maybe I missed something or ACM/APIM mismatch.
Of course also I have few errors
after Sync 2 - to Sync 3 upgrade
U2101:00-2F — Configuration Incompatible (BdyCM)
U0264:87-2F — Lost Communication with Rear Camera (but camera working, just back camera from Amazon, because OEM broken)
B13DC:13-0B — CD Slot Illumination (but CD source available in SYNC3)
I completely forgot to mention. When I first connected, when Sync version was 2.2.16280, everything worked! After updating to version 3.4.23188, I never heard any sound again.
CD slot illumination is referring to the small 2 pin cable to the right next to the slot under the top hat, any chance you missed it or damaged it when you pulled the top hat?
Was this a 4” to 8” conversion or ?
If this is a non-NAV APIM you probably need to drop down to 3.4.21265 due to hardware compatibility issues with older non-Sync3 native vehicles.
As this is an Escape, I would find the AB for a 2016 Escape and compare it with yours using ASBuilt Explorer.
Thanks for the advice. I’ll definitely check this cable. This is an update from an 8" SYNC 2 (3.10) with Touchscreen and NAV to a SYNC 3 8" (2.2.16280) with NAV. When the SYNC 3 had firmware 2.2.16280, audio worked during calls, but I didn’t check for errors because it was the first time I used it after the update from old Sync and I was really curious to see if it was working. After updating to 3.4.23188, the problem arose. When the problem appeared, I checked Forscan and saw all these errors. I took four different VINs from 2016 and 2017 Ford Escapes with the same specs as mine. I compared each as-built parameter for my VIN and four others. I checked the database for each parameter… But I still couldn’t find the answer. I’ll try downgrading to 3.4.21265. Thanks for the idea!