KnightSnake

Thanks.

Yes mine is a nav. There are no other Continental's in Europe. In total there are about 10 or so here. And I am talking Europe wide. As for the files like I said (and as people can see now) the files are the same for all regions as it is VIN based. The only thing to keep in mind if you yourself did not retrieve the update from Ford. Pay attention to the fact if you install the nav version of the software or not. Mine was.

Besides. Like I said I flashed back the version that did work as intended with Android auto. Version 2.2. So case closed for me.

Trust me. The software is the same. I asked an official dealer to check for any other version that might be current in the US. The dealer said for the Continental build 19205 of sync3 is the current one. Regardless of the fact if downloaded from owner.lincoln.com or from the sync3 update section of ford.de the dealer confirmed the USA has the same build. After all like I said the European sync3 update site identifies USA cars by their VIN and spits out the appropriate software to download. Try it yourself... Here is the site I used https://www.ford.de/service/betriebsanleitungen-hilfe/ford-sync-bluetooth/karten-software-update#/

Actually they are the same contents pretty much. Ford uses virtually the same hardware across all sync3 vehicles. I for instance used an f150 file to roll back to 2.2, seeing I am not able to find an actual Continental file from a Continental owner. Doesn't matter works perfectly fine. The cars' VIN and hardware then tells the software what skin it should load and which contents. Yes I am in Europe.

That's the funny part. The car was correctly identified by the Ford website based on its own VIN. So the update was not from another car.

I have it written in the topic description build nr 19205. Download was from Ford Europe server. On the US Lincoln server it is the exact same version. There are no major noticable differences for me anyway. So I am perfectly happy running 2.2 again for now. I indicated this bug to Ford and Lincoln. But it seems issues with updating are common but random it seems for some APIF's even though the same update runs fine on others. Definitely something Ford and QNX/BlackBerry (sync3 developer) needs to improve.

Well I mean it was on 3.0. Now it is on good old 2.2 obviously.

It is on 3.0 now. Since then I have these issues. I did everything with AA clear delete everything. I ended up reinstalling 2.2 and all is well again. Definitely an issue related to my headunit and v 3.0.

It is on 3.0 now. Since then I have these issues. I did everything with AA clear delete everything. I ended up reinstalling 2.2 and all is well again. Definitely an issue related to my headunit and v 3.0.

I think I am going to do a roll back to v2.2. The locan US certified Ford dealer here said they have no clue and said they never heard of this issue, a quick search on the internet tells me otherwise. People say try different cables, delete the phone, repair etc etc. Unfortunately none of this works for me, and Ford is not helping either. I would understand things to go wrong with an unofficial update, but this was one which was on the Ford servers and suggested for the car. Anyway like I said I will rollback to 2.2 as I think that was the version it came with. Anybody advising against it?

I am just puzzled how the apim could be defective after a successful update. Everything else works fine mind you.

I will try a bunch of things. The same cable was fine before the update. And also used someone else's phone and cable. No go. I contacted Ford certified US partner in Cologne. See what they say. If I could somehow reflash the original build it should be fine already.

However I will try some resets and reinstalls over the weekend.

No unfortunately in Android 10 it is no longer a separate app. It is embedded and gets triggered only after connected to a compatible headunit. I installed the apk and yet it is not showing as a separate app. It did before the q update I had.