Glad you all suggested doing more tests. IT'S BACK!!!! 
-
1
- Show All
-
Sign Up! To view all forums and unlock additional cool features
Welcome to the #1 Explorer ST Forum and Explorer ST community dedicated to Explorer ST owners and enthusiasts. Register for an account, it's free and it's easy, so don't hesitate to join the Explorer ST Forum today!
Phone Call Echo
- Thread starter Bwisi96
- Start date
ugh...we were all pulling for you!
I don't know the architecture of the system to say for certain yes or no, but depending on where the setting file is stored it's possible swapping out the APIM wouldn't reset anything
A quick search and I found the following:
The SYNC computer, which Ford calls the Accessory Protocol Interface Module (APIM), is housed separately from the head unit, called the Audio Control Module (ACM), and interfaces with all vehicle audio sources as well as the high-speed and medium-speed vehicle CAN-buses.
Source
If this is accurate (sounds like it is) then replacing the APIM wouldn't reset any settings, that would all be in the ACM. Now the question is could it be something in the ACM that causes this problem?
A quick search and I found the following:
The SYNC computer, which Ford calls the Accessory Protocol Interface Module (APIM), is housed separately from the head unit, called the Audio Control Module (ACM), and interfaces with all vehicle audio sources as well as the high-speed and medium-speed vehicle CAN-buses.
Source
If this is accurate (sounds like it is) then replacing the APIM wouldn't reset any settings, that would all be in the ACM. Now the question is could it be something in the ACM that causes this problem?
Great job finding out that information. Damn!
I'll mention the ACM to see if that's a possible permanent fix. I hate being the guinea pig for Ford to figure out what is going wrong.
I'll mention the ACM to see if that's a possible permanent fix. I hate being the guinea pig for Ford to figure out what is going wrong.
UPDATE: Got a call from my local Ford dealership stating it's a software fix to this issue. Nothing they can do until the latest update comes out. They expect at least a month until the update releases.
Got a free detail out of it. But a big ol' waste of my time.
Got a free detail out of it. But a big ol' waste of my time.
Ford stated: " The big fix was replacing the APIM. If it persists, there is nothing else hardware-wise for Ford to replace. The next steps (if already fully upgraded to the latest build #) is to wait on Ford to push the fix down in an upgrade. Probably a month out." See the Broadcast Message below.
Ford's Service Mgr did provide the number to Ford's consumer affairs hotline 800-392-3673. I think if we all call in on the same issue and expect restitution, perhaps it'll be an avenue to a permanent fix. UPDATE: Case No. CAS-32103368-T6Q9N8
I'm guessing your dealerships said the same?
Ford's Service Mgr did provide the number to Ford's consumer affairs hotline 800-392-3673. I think if we all call in on the same issue and expect restitution, perhaps it'll be an avenue to a permanent fix. UPDATE: Case No. CAS-32103368-T6Q9N8
I'm guessing your dealerships said the same?
Last edited:
-
3
- Show All
First I wanted to say I don't own an explorer, but what I do own are SuperDuty trucks. So I wanted to point out a few things here. The hardware/Software across Fords line is relatively the same from vehicle to vehicle.
This problem ALSO exists in may F-Series trucks as well. I mainly focus on the SuperDuty line being thats what I have in my fleet at work and personally.
To start, 1 out of the bunch (2020 F250) has the exact same issue many of you speak of. This is indeed software related in regards to the APIM. Everything was 100% fine with the bluetooth connectivity and call clarity until I did an update sometime last December 2020. This truck was Built January 2020. That update destroyed the bluetooth call capability and the infamous "ECHO" started. Much testing has been done on both the phone side and the truck module side to see what was at fault. Many phones tested on several trucks and thousands of dollars later.... it still echos.
Being I have Fords dealer software at my fingertips, I usually update my own trucks at my leisure... Like you all with Explorers, I am awaiting a software fix for this issue.
This also came into play when many laws in regards to how your phone listens to you went into affect for things like "Hey Google" or Hey Bixby" or "Hey Siri". There is a disconnect (no pun intended) with when and how the phone starts listening when connected to bluetooth.
Very Frustrating, I have been following this page patiently awaiting to see if anyone came through with a breakthrough.
I have tried every last option one could to test this and have come to the conclusion with Ford that it is indeed software related.
Ford has ALWAYS had whats referred to as the "BlueTooth LAG". But it never really affected the call, only the audio if streaming a video. In the ERA of 5G and digitized calls, things have greatly changed...
As soon as I see a new software update for the APIM I will download it immediately via FDRS (Fords software).
This problem ALSO exists in may F-Series trucks as well. I mainly focus on the SuperDuty line being thats what I have in my fleet at work and personally.
To start, 1 out of the bunch (2020 F250) has the exact same issue many of you speak of. This is indeed software related in regards to the APIM. Everything was 100% fine with the bluetooth connectivity and call clarity until I did an update sometime last December 2020. This truck was Built January 2020. That update destroyed the bluetooth call capability and the infamous "ECHO" started. Much testing has been done on both the phone side and the truck module side to see what was at fault. Many phones tested on several trucks and thousands of dollars later.... it still echos.
Being I have Fords dealer software at my fingertips, I usually update my own trucks at my leisure... Like you all with Explorers, I am awaiting a software fix for this issue.
This also came into play when many laws in regards to how your phone listens to you went into affect for things like "Hey Google" or Hey Bixby" or "Hey Siri". There is a disconnect (no pun intended) with when and how the phone starts listening when connected to bluetooth.
Very Frustrating, I have been following this page patiently awaiting to see if anyone came through with a breakthrough.
I have tried every last option one could to test this and have come to the conclusion with Ford that it is indeed software related.
Ford has ALWAYS had whats referred to as the "BlueTooth LAG". But it never really affected the call, only the audio if streaming a video. In the ERA of 5G and digitized calls, things have greatly changed...
As soon as I see a new software update for the APIM I will download it immediately via FDRS (Fords software).
Since Ford is leaving us on the fence until they get around to finding a permanent fix. I started looking into fixes that would help from the smartphone's side of the equitation. This may not work for everyone, but this could be helpful to those that are Android users.
https://demcrumbliesreviews.com/fix-bluetooth-audio-stuttering-on-android-phones/
I'm scrolling down to this section:
Next, Change Bluetooth Playback Quality In Developer Options
As an Android user (OnePlus 7 Pro), I'll see if this makes any difference what-so-ever!
https://demcrumbliesreviews.com/fix-bluetooth-audio-stuttering-on-android-phones/
I'm scrolling down to this section:
Next, Change Bluetooth Playback Quality In Developer Options
As an Android user (OnePlus 7 Pro), I'll see if this makes any difference what-so-ever!
