Eclipse Cross Forum banner
1 - 9 of 9 Posts

Registered
Joined
2 Posts
Discussion Starter · #1 ·
Hey team

I've been having issues with Android Auto on my 2018 EC XLS. I'm pretty sure this is Android Auto related but want to check if others have had similar experience.

In a nutshell, everything that works well on the phone itself (navigation, youtube music, news, etc) goes bananas when I plug the cable and Android Auto kicks in.

Google Maps navigation becomes not as precise. The car on the display drifts on corners and will go the other way for a few seconds.

If I ask Google to read me the news, or if I press the News app, I'll get a "Sorry, I don't understand." reply. (When unplugged it works perfectly)

Asking to play music will result in a "Requesting to play Pantera" (馃), but it never plays. Sometimes it starts playing an unrelated podcast. Unplugged, google correctly replies with "Playing XXXXXX on Youtube Music."

My phone is a OnePlus 7 Pro with all system and app updates (Android 10).

Has anyone seen anything similar?
 

Registered
Joined
2 Posts
Discussion Starter · #2 ·
Just realised I can run Android Auto directly on the phone without plugging it to the car. Voice commands have the same issues, so not a car thing.

Also remembered that I find the touchscreen on the car multimedia display not as responsive/precise as one would expect. Sometimes I need to press a button 2 or 3 times until I hit the right spot. Is it normal or have I got a worn-out unit? My car was a rental prior to me buying it.
 

Registered
Joined
188 Posts
I'm by no means an expert on Android, but I've noticed that AA can have a life of its own, compared to just regular Android on your phone. So, yes - it's in large part a software issue.
You maybe have already checked voice match settings on AA, and re-calibrated it to work with your voice?

On the screen, do you see that perhaps there's a screen protector on it? I've found that sometimes, screen protectors can mess with responsiveness of the screen itself. Forget about using that damn touch pad (if you have it) with AA - it's more frustrating as critical functions (e.g., volume, navigation controls) just have never worked, with no resolution in sight.

As for the rest, mine seems to be relatively responsive on the EC. Though, it's a case-by-case basis. As a last-ditch resort (again you may have already checked this), try un-pairing Bluetooth and on AA, and then reenabling.

I'd also go into a dealership to see if they can sort this out. Perhaps they have an update for the head unit - and if so, you might be in luck! Pick a reputable one with a good service department though. Not all dealerships are created equally :)

Good luck!
 

Super Moderator
Joined
466 Posts
I am an Android expert (sort of ... at least I've been a moderator over at Androidforums.com for 10 years now -- GOD! has it been that long?). I've got a Pixel 4XL running Android 11 and have had no issues with AA and the Mitsubishi head unit. This is on an 2019 SEL with the Rockford sound system so there may be some differences in the firmware.

A couple of things to check: Check the version of the head unit firmware you are running. I think it's under settings>information. I have "software version O" whatever that means. Next make sure plugging your phone into ANY USB powered port doesn't change the mode, mute the mic or change volumes. One of the whacky things Android did on many devices with 10 and later is that when you plug it in, it goes to "Charge Only" by default. Not sure how OnePlus implemented that one, but it's something to look at. While this shouldn't interfere with AA, it might. And finally, the really obvious one ... try a different USB cable. Samsung phones are REALLY touchy about the cables they use. I myself have had really strange behavior from a cable that wasn't quite right. I make it a point to use high-end cables for everything, but sometimes there's just a disconnect between one device that has no reason NOT to work, but still doesn't.

Let us know how you make out.
 

Registered
Joined
2 Posts
I am an Android expert (sort of ... at least I've been a moderator over at Androidforums.com for 10 years now -- GOD! has it been that long?). I've got a Pixel 4XL running Android 11 and have had no issues with AA and the Mitsubishi head unit. This is on an 2019 SEL with the Rockford sound system so there may be some differences in the firmware.

A couple of things to check: Check the version of the head unit firmware you are running. I think it's under settings>information. I have "software version O" whatever that means. Next make sure plugging your phone into ANY USB powered port doesn't change the mode, mute the mic or change volumes. One of the whacky things Android did on many devices with 10 and later is that when you plug it in, it goes to "Charge Only" by default. Not sure how OnePlus implemented that one, but it's something to look at. While this shouldn't interfere with AA, it might. And finally, the really obvious one ... try a different USB cable. Samsung phones are REALLY touchy about the cables they use. I myself have had really strange behavior from a cable that wasn't quite right. I make it a point to use high-end cables for everything, but sometimes there's just a disconnect between one device that has no reason NOT to work, but still doesn't.

Let us know how you make out.
Hi Lunatic59
I have problem with navigator Waze. After connecting to car (EC 1919 Invite) via USB port App Google Maps is working properly, bud if I switch it to navigator Waze, then navigation immediate stopt. While Waze is working only on my MT (Shaomi Mi9 Lite - Android 10 Instructions arm64-v8a) separately, every functions working prproperly. I do not know, where i make a mistake. Can you advise please?
 

Super Moderator
Joined
466 Posts
I don't use Waze for navigation so I don't know all that much about it, but I do know that Android want's to use AA for default navigation, so you may have to change some preferences. Here's something I found that might help.

 

Registered
Joined
126 Posts
These issues are all settings and software compatibility issue between Android and Google
The operation between the 2 are not refine and they seems not to be working together to solve or iron out issues.
But if your a techie you can make adjustments to settings n solve most if not all issues.
My advice is to get latest of both apps.
Using Google as default voice control is best... you dont wanna be using default voice control as its shitty.. you have to allow all permissions.
Waze have issuse if its not first launch on phone.
But after u get pass these setting n tweak its works all good 馃憤
 

Registered
Joined
2 Posts
I don't use Waze for navigation so I don't know all that much about it, but I do know that Android want's to use AA for default navigation, so you may have to change some preferences. Here's something I found that might help.

Hi Lunatic
I bought a Sygic navigator for the special Christmas price because I learned that producent Sygic signed a contract with Google to connect it with AndroidAuto. So far, a version compatible with AndroidAuto is not available, but developers allow those interested to participate in testing. I also signed up and downloaded a Beta version. Yet,
According to the first experience with the Beta version, the connection and function run without problems (unlike WAZE). The advantage of Sygic is that it can run without access to data on stored maps, which are updated monthly. Especially suitable in places where it is not possible to connect a mobile phone to the network.
 
1 - 9 of 9 Posts
Top