Search results

OS X or Windows? What does the file structure look like on the USB drive? Make sure you didn't un-TAR any of the individual packages within /SyncMyRide.

https://syncnavigation.com/ford/home

That means it couldn't find one of the files. May have just been an issue with the file being in an incorrect path.

Yeah, if you're running v3.4 it should show 18Q1 correctly. That's correct. It doesn't look like it's updated based solely on the About screen info, but the actual map and voice data have been updated.

Yep. It's fixed in v3.4. I forget what the problem was in v3.3 with the version info being wrong / not updated. I heard about it when I was testing the map update update back before it went live.

That's a known glitch with the update on v3.3. It's actually 18Q1 after the update, but that version string doesn't change. You can double check the package versions in the diag menu and compare them against the ones on the update stick to confirm.

What version do you have now? That'll tell you if you update to v3.0 or v3.3.

Check that you have it enabled on the phone side in the BT settings. an try a toggle off/on to see if it starts working again. Most likely the messages aren't being pushed across from the phone.

China destination APIMs only have China map data on them. I *believe* for Vietnam you'd need the Nav module with NNG Nav on it.

The official v3.2/v3.3 -> v3.4 upgrade will be a later release than what is currently available today. Not sure when exactly, but I'd guess a few months out.

Also, what was the exact error message you saw?

FYI, if Gracenotes mixes up artist names, etc. you can always shut off GN management in the Media Player settings. I've done that as some of my lesser known artists link up with another one in the database so the artist name displayed ends up wrong.

Did you use stuffit to unzip it on the Mac? That's been an issue for a few folks that haven't used the utility.

The OTA update not working? Dealer should've updated it for you.

Files are on the drive incorrectly. The fact it is indexing is the give away. The .MSA file tells SYNC not to index the drive. That and the autoinstall need to be at the base/root level. Then the other packages are in the SyncMyRide folder.

Hmm, since it's only the first minute or so, it almost seems like some high load perhaps. Though, in that case I wouldn't expect to see the button presses actually react on screen. At least, based on my running into those situations, usually no action is seen on screen and then it will catch up...

Score one for voice. OK, so back to being a bit stumped. When you touch the buttons on screen, do they react like they are being pressed? Do you hear the beep tone (if you have it turned on)?

Anytime I ran into some issue where voice said tuning and it didn't, or tuned to something other than what it responded with, it was an ACM/AHU issue. So, could be some SYNC side thing, but this test might point elsewhere. Video shows the buttons responding to the touch which also made me wonder...

When it's happening, give a simple voice command like a station name. If it responds back that it's tuning, and nothing happens, there's an ACM/AHU issue vs a SYNC side issue.

No idea to be honest. An updated build for v3.4 is starting to hit plants now. It's usually a few builds in before an update will go live for previous MY releases to update. That's a good thing though as it means more issues will be ironed out. Happy to help where I can.