Fasteddiec
Well-Known Member
- Joined
- Jun 6, 2019
- Threads
- 4
- Messages
- 163
- Reaction score
- 77
- Location
- South Florida
- First Name
- Ed
- Vehicle(s)
- 2019 Mustang GT Premium convertible
Nope, still nothing sitting in the garage.Good thought, I’ll try that!
Nope, still nothing sitting in the garage.Good thought, I’ll try that!
I’m getting same message when I tried to download fileStill getting this error.
I'd guess it had some background activity going on at the time, possibly indexing. Usually you'd get a browsing unavailable or similar pop-up though. If it had finished indexing, it's possible there was some linkage issue in the database such that it thought there was no media linked to that artist. MR may have cleared the latter up with the forced re-index.Mine works but had an issue when using voice command "search artist ***** " in USB. It would say the name then "make a selection from the screen" but nothing was there as it kept the same screen it was on before that. I did a master reset and it worked after that.
By 'reflashed' you meant having to re-install the whole damn thing again from scratch, right?reflashed the updated map files and Sync 3.4 shows 1.19
Well, that email is long gone. I get tons of emails a day, so I don't keep them unless important. Didn't think that one was. Oh well. Now what? Any suggestions what to do about that? In the mean time, I can install 3.4 when it's available again, and maybe call it a day. I'd like to have the map version corrected, but it's not the end of the world, especially if nav keeps working correctly after the update. Thx.Yes, when you run an update with v3.4, the version string will update. So, if you want it to display 19, update the map with v3.4. You can re-download the map update via the link in the confirmation e-mail.
You can e-mail/call ALOM (map distributor) and they should be able to send you the link again. I know of a few others that went that route. You can verify the install via the IVSU Versions diag screen. Then it’s just a matter of how much annoyance the string being incorrect is as functionally it’ll be fine.Well, that email is long gone. I get tons of emails a day, so I don't keep them unless important. Didn't think that one was. Oh well. Now what? Any suggestions what to do about that? In the mean time, I can install 3.4 when it's available again, and maybe call it a day. I'd like to have the map version corrected, but it's not the end of the world, especially if nav keeps working correctly after the update. Thx.
You can get the contact at info on the syncnavigation.com site. Personally I’d just leave it be. It’s a long process to go through again just for the sake of the version text. It’ll correct the next time anyway as is if you have updated to 3.4.I could do that, but where do I get the ALOM contact info? And if it turns out to be a big risk, or a PITA, would just leave the damn thing alone man. At least it works fine. I'd try to get another free map download, so it corrects next time without having to redo this crap again. Thank you.
after installing Sync 3.4, i performed a master reset and then reflashed the map files. 40 minutes later the reflash was complete (i removed the USB when prompted) and after restarting my car, i verified maps and nav voice was working.By 'reflashed' you meant having to re-install the whole damn thing again from scratch, right?.
OT, but this reminds me of the old/early days of the PC 'revolution' when you wanted/needed to do a BIOS update. It was a white knuckle experience, because if you hosed your BIOS your PC could be completely bricked. Eventually, the motherboard manufacturers got smart and installed additional non-volatile memory so if your update went TU you could at least go back to where you were. That was, like, 30 years ago; c'mon Ford!Dang, first the map update problems and now this.
Oh, my, I remember getting my first dual-BIOS motherboard from Gigabyte for my Q6600 system. If something went wrong in the boot process due to settings or corruption, it would restart and use the back-up BIOS. Changed the game 15-ish years ago.OT, but this reminds me of the old/early days of the PC 'revolution' when you wanted/needed to do a BIOS update. It was a white knuckle experience, because if you hosed your BIOS your PC could be completely bricked. Eventually, the motherboard manufacturers got smart and installed additional non-volatile memory so if your update went TU you could at least go back to where you were. That was, like, 30 years ago; c'mon Ford!