Lost voice control after updating to 3.4 21194

This topic is not really related to cyanlabs as I did the update with official files from Ford. However, as the files are same in syn3 updater and Ford update service, I thought I would get best support from here.

I recently udpated my EU Sync with nav from 3.4 21020 to 21194. Update went smoothly, log file was created etc. Everything was working fine until I tried to give voice commands. Pressing the voice command button on steering wheel only gave “voice recognition not ready” message in sync screen.
Later I tried navigation and noticed that the lovely lady had lost her voice too.

I tried master reset but it did not help.
I tried to reinstall voice files by modifying the autoinstall file to only to install voice files. It didn’t help either.

Has anyone experienced similar issue?
Do you have any suggestions how to get voice control and navigation voice working again?

Edit. My car is Focus 2018 (MK4)

I remember seeing some issues, but with nav voices.
I think there are 2 things you could try:

A) Troubleshooting: create with syn3update and post the output for the interrogator log, redact your vin from the file’s name and content. That will tell us which packages are installed, and maybe you could install then ones missing (if any) to see if that helps.

B) Perform a clean install: since your car is 2018 and as long as you do not have a MY20 or later APIM or screen, you could just reformat the unit and start from scratch. It will wipe all the information on the APIM (even residual information from failed updates).

Ford’s way of updating is called AUTOINSTALL, which can fail due to storage constrain and will not tell you that it failed.

If you ask me, B would be faster…
That’s why we always recommend going with REFORMAT instead of AUTOINSTALL to install maps if it’s possible, it’s cleaner, faster, more reliable.

Thanks for suggestions. I’m hesitant with option B since I’m still under warranty and thus reluctant to do anything that is not directly offered to me from Ford.

I created the interrogator log, but Syn3Updater crashed every time I tried to open the log.
Here’s the raw xml log from which at least I couldn’t interpret what packages are installed (apart from the sync app itself).

<?xml version="1.0" encoding="UTF-8"?>
<p:OTAModuleSnapShot xmlns:d2p1="urn:ford/Vehicle/Module/Information/v3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="urn:ford/com/productdesign/ipp/ModuleSnapshot/v2.0" version="2021-09-18" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
  <p:VIN></p:VIN>
  <p:ModuleName>ECU</p:ModuleName>
  <p:RequestRole>
    <d2p1:Role>CONSUMER</d2p1:Role>
    <d2p1:RoleSource>OTA</d2p1:RoleSource>
    <d2p1:RoleDesc>SYNCGEN3</d2p1:RoleDesc>
    <d2p1:RoleID>OTA</d2p1:RoleID>
  </p:RequestRole>
  <p:BroadcastDTCType/>
  <p:Node isFlashed="false" specificationCategory="GGDS">
    <d2p1:Address>7D0</d2p1:Address>
    <d2p1:ECUAcronym name="APIM">
      <d2p1:State>
        <d2p1:Gateway gatewayType="NONE">
          <d2p1:DID didFormat="ASCII" didType="Embedded Consumer Operating System Part Number" didValue="8033" responseLength="24">
            <d2p1:Response>5U5T-14G381-ET</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8060" responseLength="384">
            <d2p1:Response>315535542d3134473432312d424148000000000000000000315535542d3134473432312d424248000000000000000000315535542d3134473635382d414700000000000000000000315535542d3134473432312d424348000000000000000000315535542d3134473432312d424448000000000000000000315535542d3134473432312d424548000000000000000000315535542d3134473432312d424648000000000000000000315535542d3134473432312d424748000000000000000000345535542d3134473432332d414300000000000000000000315535542d3134473432312d424848000000000000000000355535542d3134473339312d415000000000000000000000315535542d3134473432342d424b00000000000000000000315535542d3134473432312d424a48000000000000000000345535542d3134473432322d424146000000000000000000345535542d3134473432322d424246000000000000000000345535542d3134473432322d424346000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8061" responseLength="384">
            <d2p1:Response>345535542d3134473432322d424446000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 1" didValue="D704" responseLength="4">
            <d2p1:Response>2747efc6</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
            <d2p1:Response>8eff8359</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
            <d2p1:Response>8a6a05925002ec4440c2</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
            <d2p1:Response>4649010bc00b48902cb46a05</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
            <d2p1:Response>0000010000</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
            <d2p1:Response>00001d8002010b</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
            <d2p1:Response>190519052653</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
            <d2p1:Response>80</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
            <d2p1:Response>0b0033000000005ef100005656600061</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="On-line Diagnostic Database Reference Number" didValue="F110" responseLength="24">
            <d2p1:Response>DS-1U5T-14G371-AE</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
            <d2p1:Response>1U5T-14G380-FD</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
            <d2p1:Response>3U5T-14G371-GDD</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Calibration Data #1 Number" didValue="F124" responseLength="24">
            <d2p1:Response>1U5T-14G375-HA</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Private Sub Node #1 Serial Number" didValue="F141" responseLength="16">
            <d2p1:Response>LX8J00H9</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Software Download Specification Version" didValue="F162" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Vehicle Manufacturer ECU Software Number" didValue="F188" responseLength="24">
            <d2p1:Response>1U5T-14G374-AE</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Serial Number" didValue="F18C" responseLength="16">
            <d2p1:Response></d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
            <d2p1:Response>f4:e1:1e:db:10:a1</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
            <d2p1:Response>f4:e1:1e:db:10:a2</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
        </d2p1:Gateway>
      </d2p1:State>
    </d2p1:ECUAcronym>
    <d2p1:ODLNetwork d2p1:NetworkDataRate="500" d2p1:NetworkName="HS-CAN" d2p1:NetworkProtocol="CAN" d2p1:DLCName="SAE J1962" d2p1:Pins="6,14"/>
    <d2p1:AdditionalAttributes logGeneratedDateTime="2021-09-18T18:39:42+00:00" RAM="1126555648" vmcuVersion="Vector_VMCU_02.02.20">
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.1G" available="892K"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.8G" available="14M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.3G" available="14M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.5G" available="7.9M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.2G" available="17M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.7G" available="21M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="38M" available="396K"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.2G" available="5.7M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="3.1G" available="24M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="4.7G" available="27M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="4.9G" available="29M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="4.3G" available="25M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="3.6G" available="35M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="1.9G" available="8.4M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/grace" total="1003M" available="21M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/" total="1.2G" available="521M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="35M" available="35M"/>
      <d2p1:PartitionHealth type="/fs/mp/" total="1.4G" available="132M"/>
      <d2p1:PartitionHealth type="/fs/mp/resources" total="71M" available="476K"/>
      <d2p1:PartitionHealth type="/fs/images/" total="54G" available="11G"/>
      <d2p1:InstallationLog/>
      <d2p1:SyncData>MIIEtAYJKoZIhvcNAQcDoIIEpTCCBKECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAEQ/DtkPIvlE01MjQzXAb7iJyOOseR3zd0oEdlW+flye+VZKcywE5Zqgx6841gi5gFENLKFmULhSjkqmTv9C9ef/ZNijFVBoTGL0fe77YGKqQHIVNtDXDyB56o7ieiVKLfxGz+e3cBhAB1nk1yqWJdS/XjUxrKO4TomZOEKM60ajfgUcSF/AeLO4x/thLRCwKYT0x/Yy1Pr1qHR21chuTRNwF5SY7QXRz3DQdjBMJfsgjWZ6Jk4vtOTTh4aOo9USrLvwDUzNaHbki1WPEH4K+GVZ7o8L/rT3QqYgAlrzS5h9vV9Q0rdKTlL9BJovNjGRz+oRHuYNHcFaCg3cSh2dWgYwggLeBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBBSdXULGgNjSZM3+4QyaNRHgIICsADSnuSGVnOwlwv/hdS9VLA1XLbL1JJj09MEdIM90LP9/2ldAnl4WFWB0iqnAcTtjHmlswJG8YEIG4BueZxbn0rKthiRUlcXnTTK5/qVgJQmuSlftiT7M2BoQFDHu2saA8hJI3dWisubh7B4nfQlCNynM1Fim1Ma8qsCyKftKdpQyppswmcs3SLbdWOZS4TNClJX2e9w2y3dJ6D4AwuCtSQZEB+CZEhLHRT7cbDML5iipYpB943eBypV8K5V1Pkzr/HjPaODjaHOXPZgo1jeJny+Mh4vtN9liHjpVgq128O05Iyzifgf/W/53722bEmGxB4uoOehIQN13KXth2fp4PkVePf+7dy3ui56qgvqkOxmC2ULSUlbnAy8O8xFwH0x/LFZXTcN1GOBVJNUf/6ka4XqXCFcQ1attkPwuHQ2HMQM5EGCEafT85KbC9n2rzGlTvYuQwp3glR13lq6pv8KMaR/8iPipvKWjttwj/FruW4s9cHg+pa/uKY8n1fxDG7PUhMxCQjU4nuyasaexwuUFstQin/VmlH6aOwjf6JCpdT7hh5L9Bofcrndzs7UZq0IApzprXVYuOSm1Hvo/d2RAyCb6YXhep6SZIrtwgqz9h+VKe+0fJyjeujv7dDlQwgIe1kb/GEL1pRQnbb45l4zM4OBOPIDHne+qyjko+EZnrYqOeuTOavZbaX10+9HwVXktKJCgpDqawBExfnOr848YleYVrlVh712Ti2oD3SbJ6HZK5Sx2iMaEziq5BbHygp1yQQ2T/lOr40tdrW4eQtcIH9oSGOB/yBufz9FIBvpxxGqAJovi5QoaBflzjcKoJ1WZetoQarLjomuvOgBH8dalut/jeODOG44m8SxkVKQbfwT9RnoeINx1exSmRUAEICWaNZyIBS14wUiICexCvfv2iE=</d2p1:SyncData>
    </d2p1:AdditionalAttributes>
  </p:Node>
</p:OTAModuleSnapShot>

Reload the system voice file manually and them perform another Master Reset. This is not uncommon.

Sync Voice…
5U5T-14G391-AP

These are the other installed files, all look ok.
Maps…
1U5T-14G421-BAH
1U5T-14G421-BBH
1U5T-14G421-BCH
1U5T-14G421-BDH
1U5T-14G421-BEH
1U5T-14G421-BFH
1U5T-14G421-BGH
1U5T-14G421-BHH
1U5T-14G421-BJH
Map License…
1U5T-14G424-BK
Nav Voice…
4U5T-14G422-BAF
4U5T-14G422-BBF
4U5T-14G422-BCF
4U5T-14G422-BDF
DAB…
1U5T-14G658-AG
Gracenotes…
4U5T-14G423-AC

To manually install 5U5T-14G391-AP follow the instructions below. You can do this with the Syn3 Updater also if you like.

  1. Create a USB drive (format as EXFAT) with a SyncMyRide folder.
  2. Copy the file downloaded above into the SyncMyRide folder.
  3. In the root of the USB is the autoinstall.lst and DONTINDX.MSA files which you can obtain from any upgrade you previously performed.
  4. You will need to edit the autoinstall.lst file so it looks like the example below:

[SYNCGen3.0_ALL]
Item1 = 5U5T-14G391-AP_1626914045000.TAR.GZ
Open1 = SyncMyRide\5U5T-14G391-AP_1626914045000.TAR.GZ
Options = AutoInstall

  1. Insert USB in vehicle and wait for the installation to complete. You should see a message indicating completion.
  2. Remove the USB drive and reboot the APIM. If necessary, perform another Master Reset.

Thanks for the suggestion.
I have already tried to reinstall voice file as you instructed, but it didn’t help. What I didn’t do though was master reset after installation. Do you think that another master reset after the voice file reinstallation would do any difference?

Quick recap what I have done so far:

  1. Installed official 21194 update via USB → voice control lost
  2. Master reset → issue still present
  3. Reinstalled only voice file 14G391 by modifying autoinstall.lst → issue still present
  4. Created interrogator log file which I have added to this thread

I parsed interrogator log created in step 4 manually and 5U5T-14G391-AP was shown in applications part numbers, so it should be installed.

P.S. I’m too lazy to create GitHub issue, but package detection from hex string in method Cyanlabs.Syn3Updater.Converter.SyncHexToAscii.ConvertPackages needs a fix. Currently if a package’s last byte happens to end in 0, package splits will be created at incorrect locations. I worked around this by reading the packageHex byte by byte and reacting to 0x00 appropriately.

Rebooting the APIM after loading the new voice file is mandatory , or the system will not delete the old voice.img and install files and rename voice_new.img to voice.img. It is best to Master Reset after that.

The file is installed but the installation could be corrupted. I would install the -AN version and see if the voice works. You will need to reinstall -AP again to be current.

If that does not work, reformat is the best option. Don’t worry, Ford can’t tell, they will just know the software is updated as all of the files are the same with the same hashes.

I use this… Hex to ASCII | Hex to Text converter (rapidtables.com)

Voice control started working again after I downgraded voice file to AN. Unfortunately, updating back to AP broke voice control once again.

I will probably stick with AN voice file for now. Are you aware of any version dependencies, i.e. does a sync app version require specific voice file version? Is it possible to run into some issue when using old AN voice file with 21194 sync app?

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Yes often this is the case but you can always try

1 Like

You’ll get a few different answers on this, but the overall general answer is not really. There is a fix in -AP for some specific instance that I cannot remember, and some of the commands have been abbreviated, more concise. I have not heard of any issues yet with running -AN with 3.4.21194. Ford however, does recommend using the -AP file.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.