When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Folks, I'm quite frustrated, I need to be able to get Android navigation on my 2018 SYNC 3.0 Screen every time, not just hit and miss. So far, I've only been able to do it once, and it worked flawlessly, I even was able to adjust the "Prompt" volume. What I believe I really need is a step-by-step procedure for reproducing this, and thanks in advance to anyone who can document the way to make this happen every time.
My details:
Android phone is on and USB cable is plugged into phone and in the bottom-most USB connector in center stack of truck
I then key start the truck every time (no remote start)
My phone is detected by SYNC
Android Auto is on, but no directions on the SYNC screen yet, but they are on the phone's screen, so I normally press "Start" on the phone to begin the navigation.
The Audio Source is my phone
However, these steps are not reliable every time.
Is you AA up to date? There was a new update recently. I have to make sure bluetooth detection is on along with auto launch. Make sure pocket detection is turned off. Also make sure first and foremost your cable is QC3.0 capable as the other cables don't work for me.
[QUOTE=12Farmer;19139518]Folks, I'm quite frustrated, I need to be able to get Android navigation on my 2018 SYNC 3.0 Screen every time, not just hit and miss. So far, I've only been able to do it once, and it worked flawlessly, I even was able to adjust the "Prompt" volume. What I believe I really need is a step-by-step procedure for reproducing this, and thanks in advance to anyone who can document the way to make this happen every time.
My details:
Android phone is on and USB cable is plugged into phone and in the bottom-most USB connector in center stack of truck
I then key start the truck every time (no remote start)
My phone is detected by SYNC
Android Auto is on, but no directions on the SYNC screen yet, but they are on the phone's screen, so I normally press "Start" on the phone to begin the navigation.
The Audio Source is my phone
However, these steps are not reliable every time.
Can someone please help me out with this?[/QUOTE
Since it worked for you before, you might want to try a Master Reset of the SYNC system.
Doing this won’t hurt anything but many times it’ll clear up weird problems such as the one you’re having.
Do you know how to so this?
Also and just as 390 mentioned, you must use the cable that came with your phone or one that you know for sure is Android approved and not some cheap Chinese cable that can be found online or at your local gas station.
Can you provide some details Scott your truck model ? see signature for details
What version if sync 3 are you running? Version 3,0 Build 17276
What version of android are you using? Nougat 7.0
Is you AA up to date? There was a new update recently. I have to make sure bluetooth detection is on along with auto launch. Make sure pocket detection is turned off. Also make sure first and foremost your cable is QC3.0 capable as the other cables don't work for me.
AA is version 5.0.500224-release
Pocket detection is off.
Bluetooth is on and auto launches.
My USB cable is a short 1 foot, US made Anker.
Folks, I'm quite frustrated, I need to be able to get Android navigation on my 2018 SYNC 3.0 Screen every time, not just hit and miss. So far, I've only been able to do it once, and it worked flawlessly, I even was able to adjust the "Prompt" volume. What I believe I really need is a step-by-step procedure for reproducing this, and thanks in advance to anyone who can document the way to make this happen every time.
My details:
Android phone is on and USB cable is plugged into phone and in the bottom-most USB connector in center stack of truck
I then key start the truck every time (no remote start)
My phone is detected by SYNC
Android Auto is on, but no directions on the SYNC screen yet, but they are on the phone's screen, so I normally press "Start" on the phone to begin the navigation.
The Audio Source is my phone
However, these steps are not reliable every time.
Can someone please help me out with this?[/QUOTE
Since it worked for you before, you might want to try a Master Reset of the SYNC system.
Doing this won’t hurt anything but many times it’ll clear up weird problems such as the one you’re having.
Do you know how to so this? Yes, thanks for the suggestion. I'll check the Owner's Manual, as i know it's in there.
Also and just as 390 mentioned, you must use the cable that came with your phone or one that you know for sure is Android approved and not some cheap Chinese cable that can be found online or at your local gas station.
My USB cable is a 1 foot quality Anker brand cable.
I was having connectivity issues as well. The phone would not always connect when I plugged it in, and it would disconnect any time I moved the phone around. I bought a 3 pack of 1.5 foot USB-C cables off Amazon for about $10. The new cable solved the problem - the phone now connects immediately and Android Auto opens up every time and stays connected even if the phone is moved around.
I did not order the nav because I use Mapquest on my phone and I planned to plug in and use it on my sync 3 screen. As the OP noted I was able to get everything connected and despite what I felt were intrusive requests for permissions to access everything... I had a trip with full functionality.When I went to use it again I had to start from square one all over again. Including the loading of Android auto. I feel as though its a combination of things including the Android auto program. I got frustrated and stopped messing with it. My truck was delivered in May of 2019 and whatever version of Sync was current at the time is what I have. I believe there may have been an update recently.
I cant understand all the permissions ... and why the phone cant simply link to Sync and be used as a component. Much the same as an MP3 player just using the screen as a display. The more complex the interface the more likely the issues.
I will keep up on this thread because I just gave up.