Hi All,
I've been extremely excited about the integration of my smartphone with my car for a while. Almost anyone who would be in the market for a motor vehicle with an advanced head unit would also already own a smartphone with data access.
However, like any new use of technology, there are growing pains and Android Auto is no different. I have struggled through a few issues already and continue to grapple with others. A huge difficulty I had was simply finding discussion threads. Do I look on sites that focus on cars? On Android Auto? On Android OS?
So here it is. I'm starting a thread to pull together the most common problems and their solutions. Also, please note - I am not an expert in any of these things, just a user. I will give credit where I have a source but I am just gathering the info into one place and adding it to my own observations.
I haven't decided how this thread is going to look or if it will be small or big, so I will save the first few message placeholders in case and I will add known problems, work-arounds, and identified solutions as they come.
Hopefully this helps out some other users!
Troubleshooting:
I strongly suggest you make sure you have a good quality USB cable and confirm that you are able to connect your phone to your computer and transfer a file (some cables will allow charging but not data transfer).
1. Problem: Bluetooth won't pair, won't connect, etc.
Possible Solution:
It appears that Android Auto will attempt to create a BT profile. So
a) Delete the pairing on your cell phone
b) Delete the pairing on your car head unit
c) Turn OFF bluetooth on your phone
d) Plug your phone into your car's head unit. Depending on your settings, you may need to tell your car to launch Android Auto and you may need to select the device. If so, make sure you are selecting it in Android Auto (NOT Bluetooth pairing). Respond appropriately to any requests for authorization on your phone and car.
This should leave you with a properly paired device and car.
2. Problem: Every time I launch Android Auto, I have to pair my phone again!
Work-around: Once you have a working AA connection between the car and your device, go into the settings in the Android Auto app on your device and turn off the option to "Add new cars to Android Auto."
3. Problem: Android Auto notifies me of a new message but won't read it out loud/but starts to read it and cuts off.
It looks like there is a conflict between Google Now, Android Auto, and the Bluetooth handoff with the car head unit. Kudos to XDA member BuildaWall for discovering that turning off the BT headset option in Google Now fixed it for some people. I did a little more testing and found that forcing Android Auto to make your phone the primary source of audio seems to be the other piece.
UPDATE:I applied the August CM-13 Snapshot and this workaround no longer fixes the problem. I have reheaded it as a possible work-around as it might fix the issue for people on slightly older ROMs
UPDATE Sept 27/2016: I have upgraded to stock Nougat (Android 7). This issue still exists. However, after reading this XDA article, I tested an accessibility option. AA began reading the messages once again.
Possible Work-arounds:
A) Several people reported that their Media volume on their phone was being changed to zero when they plugged into AA. Some also reported that turning USB Debugging OFF fixed this issue. If you don't know what USB debugging is, don't worry about it; you would have to have intentionally turned it on. For volume, tap your volume rocker but then tap the drop down on the pop up volume notification.. It will expand to multiple volume sliders. For simplicity, make sure none are zero.
B) On your phone, go into Google Now, Options, Settings, Voice and then turn off Bluetooth Headset. This was reported to help by some but not didn't help for me.
C) On your car's head unit, in Android Auto, select a music option (I have Spotify and Google Play Music, but I think any audio source app within AA will work). If you don't want to listen to anything, just play and then pause/stop it but you CANNOT go back to the car as a primary source (eg radio or sirusXM).
D) On Nougat (Android 7) go to settings, accessibility, and enable one of the options (I have tested Voice Access, but in theory, activating any accessibility option should reactivate the message reading in AA.
4. Reported with work-around by @ReppinTheSouth - Android auto either being laggy or flat-out disconnecting
ReppinTheSouth observed this on a Pioneer avh 4100 and a galaxy s4 and reported August 7, 2016
Suggested Work-Around: Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
5. Reported by @ReppinTheSouth - When driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive.
I'm not listing this as a work-around, as it doesn't resolve the problem, but is still good to know: @ReppinTheSouth advises: This only happens when voice commands are enabled & Unplugging and replugging the phone gets the head unit out of its frozen state.
More to come!
Tips and Tricks:
I will use this page to list tips to improve performance or usability that don't fit under troubleshooting.
1. Keeping the phone screen alive and accessible.
Please exercise safe driving habits.
TL; DR:
Turn on Developer options
Turn on Stay Awake
Optional: if you have a security lock you may want to add your car Bluetooth as a trusted device for smart lock so it doesn't lock you out.
Details:
Android Auto changes your screen timeout to 15 seconds every time it is activated. When combined with its flaws with hangouts chat notification (no groups, can't initiate a new chat without certain contact book entries, can't access chats that began before connecting to AA) it is VERY frustrating.
Access the Developer Options menu
Settings >>> About Phone
Scroll to the bottom and tap the Build Number option seven times in a row. You will get some sort of message saying you have access to developer options. You only need to do this once.
Settings >>> Developer Options
Make sure they are turned on. Next turn on the Stay Awake option.
Your phone will now allow dimming but won't turn off the display.
Optional:
If you use a security lock on your device, you may want to authorize your car Bluetooth connection as a trusted device under smart lock so it won't lock while connected.
==============================
Links to Other Resources:
https://forums.oneplus.net/threads/...to-connected-to-the-cara-infotainment.488786/
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work.... I changed my phone Bluetooth Headset setting to off and I was playing my spotify music through Android Auto. Am I forgetting something here? what versions of AA and Whatsapp do you use?
Good thread and it is much needed as far as I am concerned. I have a Pioneer avh 4100 and a galaxy s4. One of the issues I have had is with Android auto either being laggy or flat-out disconnecting for no reason. One of the things I have noticed is Android auto seems to be a resource hog. Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
The other issue I'm having which I can't solve is when driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive. I have to unplug my phone and then plug it back up to get it to work. This only happens when voice commands are enabled. I have not been able to resolve this issue.
Sent from my SPH-L720T using XDA-Developers mobile app
NLatuny said:
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work
Click to expand...
Click to collapse
Hi NLatuny & ReppinTheSouth!
@NLatuny - Thanks for the info. I just updated my Nexus 6p to the latest (august 2016) CM13 Snapshot, and the work-around no longer fixes the problem for me either. I've updated the original post. I think your request for version numbers is probably a good idea moving forward. I will update the original post to suggest that people include that in their posts.
@ReppinTheSouth - Thanks! I will look at adding those problems and your possible solutions for the lag to the top of the thread
Might be good to add a list of things you can and cannot do. For example, I found the other day through just trying you could ask various questions.
How old is (enter famous person here). = Correct answer.
I need to remember some of the other ones I've done. Good thread.
---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------
Perhaps also add how to get into Developer Mode, and what the settings in there do? The Force Day or Night mode thing is super useful.
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
duze76 said:
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
Click to expand...
Click to collapse
Check your permissions for Android Auto, you may have missed a few.
You can also uninstall and reinstall it.
I have tried all that, with no luck unfortunately
Having had a courtesy car for a few days that had an android auto system in I'm looking to purchase an android auto headunit for my car, probably after Christmas.
Until then I've been using my handsets connected to the aux input on my factory system. However since I got my Pixel handset last week I've encountered a couple of issues that weren't an issue on my m9 handset previously. I've reported then to the relevant support sites but as yet have received no response, so thought I would try you knowledgeable lot.
Firstly, when making or recurving phone calls with the aux cable connected the Pixel defaults to using the loudspeaker on the handset rather than putting through the aux to my car speakers.
Secondly, when receiving a message on WhatsApp i touch the screen too get it to read the message, it does so fine, then tells me I can press the mic soon symbol and say reply. When I do so I'm told "this chat app is not installed or needs an update". The app is installed and is up to date. I can send WhatsApp messages by saying "send a WhatsApp message to...." but can't reply.
Lastly, when I ask it to play specific tracks on Spotify it often comes back with no search results. Songs that I used to ask it to play regularly on my previous device come back as no search results found. Searching manually the tracks are there and can be played. And it isn't all tracks, some tracks are found without issue.
Thanks in advance.
Also hope this is in the right thread, I notice you seem to be taking mainly about the in car systems but as it can now be used on most android phones without a dedicated in car system I figured many would be doing so.
Hi folks, sorry for the absence. My N6P died on me in November and was sent away for warranty repair. Long story short, I'm very disappointed with Huawei and futuretel. Two months later, the process ended with me owning an unfixed Nexus 6P which is still under warranty until February 2017. It has a defective motherboard according the repair center but they will not repair it. So, after 2 months of making do with an iPhone 6 with a broken screen (wife's old phone), I have moved on to a One Plus 3T.
Irritatingly, Apple Carplay worked flawlessly for that time. Typical of Apple it was very locked down and had limited options. But in fairness, it executed those few features very well. Come on Google!
[/end rant]
I'm back and will try to get the thread up to date.
MM
Sent from my ONEPLUS A3000 using Tapatalk
Hello, thank you very much for this information, is very useful.
In my case, I have a Le Pro 3 X720 and is nightmare with AA, when I plug the phone on my Hyundai car the phone only charge so I had to change their ROM to lineage is 14.1 (Android 7.1.2) and with this AA starts quickly but after 5 minutes the screen is freeze then change the cable but it doesn't work, I change the cable again with the same result, so I back to use the original leeco cable and change their ROM again, with the same result, after 5 minutes the screen is freeze, the last one is AICP 12.1 (Android 7.1.2).
Do you know how to fix this?
Thank you in advance for your response.
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
mikefavro said:
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
Click to expand...
Click to collapse
Hi Mike,
You should say what phone and android version you are using. I have used both a One Plus 3T on Oreo beta and an LG V30 on 7.1.2.
The screen timeout sets to 15 sec when I plug in, but returns to normal when I unplug.
Sent from my LG-H933 using Tapatalk
Hey Folks:
I have googled this issue and the best I could find were out-of-date questions about only partially-similar problems, and all these posts (to the very limited extent I found them) were generally between 3 and 6 years old.
Please note that I have experienced this on two different Nexus phones spanning Android 5.1 -> Android 7, though this has become far worse under 6 and 7.
Here's my current configuration and history:
Device: Nexus 6 32GB model, U.S.
OS: Factory Stock Android 7
Rooted: No
Bluetooth Headset: Plantronics Marque 2, or M70
The behavior goes something like the following...
At some point, I will be using a media player on my phone. This could be Google Play Music, VLC, etc. [The exception to this is I have not seen this behavior involving YouTube.] Having thus used one of several different media players, this will become the "last media player used".
So, I'm on a phone call, whether I made or received it. I get to the end of the call, and I hang up. Sometimes, the call was terminated because the other end disconnected, so I haven't even "ended" the call on my end. When I am the one who ended the call, sometimes I've ended it using the button on my BT headset, and sometimes I've used the on-screen hang-up button in the Phone app.
Then, the call being terminated, randomly the "last used media player" (which could last have been used a few days earlier, a couple weeks earlier, etc.) launches and starts playing what I assume was the last thing I opened.
I used to use the Marque 2, but it was damaged when it got rained on, so I replaced it with the M70.
When no Bluetooth device is paired, this behavior NEVER occurs.
Troubleshooting I've Tried:
I have completely wiped the phone clean of all data using fastboot erase ... for each of the partitions and doing a completely from-the-ground-up clean install of the current version of whichever OS I was running, which of course now includes Android 7. I've also looked through my phone in Settings and the Phone app, and I've found no relevant settings options I can either establish or change.
Any help or thoughts would be appreciated. Thanks!
Dear all
First post so here goes. Had my 7 plus exactly a week.
Specs as follows:
Model TA 1055
Android 8.1
1st June 2018 Security patch
unrooted but themed with Substratum (Swift Black)
So my phone won't detect either my amazon bluetooth adapter plugged into my bedside radio or my creative bluetooth speakers. My lenovo p2 can find these without issue. Strangely it can connect to my PC's bluetooth which gives a passcode. I've cleared bluetooth cache and still not fixed. Anybody else had bluetooth issues?
TA-1046 here with June patch and I have bluetooth issues as well.
I was not able to connect my Gear S3 smartwatch to my phone, untill I decided to turn off BT and turn it back on again.
Suddenly it worked.
Then I was not able to update my S3 apps from the Samsung App Store, untill I stopped BT and turned it back on again.
It seems to me that there is a BT issues in the June patch.
How it was before, I don't know as I received this phone 2 days ago and it updated automatically to June update.
Sorry for adding more negativity to this forum than assistance.
I am also having similar problem with connecting to my LG sound bar. It picks it up when i search, saves it but does not connect.
BT issues
Well unfortunately I have to say same. BT even can't see any device during scanning. Other devices each between other works. Other devices also see N7+ and can pair with it. Seems like scanning doesn't work for me on N7+.
I tried reset networks, clear BT cache couple of times - didn't changed anything. Still wanna avoid factory reset.
No mods, no root.
I'm bit surprised (in the sad way) by this device :-/
In the meantime BT has worked quite well for a couple of days, untill today.....
I could connect to my Gear S3, but not much later I notice new notifications on my phone but no popup on my watch.
It turned out that BT was not connected anymore.
Manually connected and the same process happens again.
Untill I rebooted my phone. From then on, my watch stayed paired with the phone and didn't loose connection.
speedme said:
In the meantime BT has worked quite well for a couple of days, untill today.....
I could connect to my Gear S3, but not much later I notice new notifications on my phone but no popup on my watch.
It turned out that BT was not connected anymore.
Manually connected and the same process happens again.
Untill I rebooted my phone. From then on, my watch stayed paired with the phone and didn't loose connection.
Click to expand...
Click to collapse
I lose the connection to my Gear S3 several times a day.
AlfredENeumann said:
I lose the connection to my Gear S3 several times a day.
Click to expand...
Click to collapse
Try resetting your Gear S3 to factory defaults and remove BT settings on phone.
(also clear BT cache).
I had to set up my watch a couple of times.
Still it disconnects sometimes, but then a normal reboot of the phone helps to get the connection back.
Submitted this to another thread, but I'll copy paste it here.
I recently got Bluetooth headphones and found that playback easily got choppy if a part of my body was in between my headset and phone, or if the phone got locked. I did find a solution to this however, and not sure if it would work for everyone that has Bluetooth issues as well.
It seems as if Bluetooth has its own app on Android 8.1, and due to this, it's getting managed by Doze or the automatic app power saving that's on by default. I switched off battery management using the following steps:
1. Go to Settings
2. Apps & Notifications
3. Tap on the option that says "See all x apps"
4. Tap on the top right hand 3 dots.
5. Tap on "Show system"
6. Scroll down until you find "Bluetooth" and tap on it
7. Tap on Battery
8. Tap on Battery Optimisation
9. Press the blue dropdown that should say "Not optimised", and select "All apps"
10. Find Bluetooth again, tap on it.
11. Optimise should be ticked, tick "Don't Optimise" instead, then press Done.
My Nokia 7 plus cannot find other Bluetooth devices.
I cleared cache, went to battery optimisation settings, ticked on the Bluetooth icon and selected *"Don't optimise"* turned on my Bluetooth to search for other devices and still this same problem persists. Can't find other Bluetooth devices including phones, tablets and headsets. I'm really confused on why there should be such a problem. I don't want to Reset to Factory settings. But I'm not being left with any other choice. I'm so upset that I have to spend so much and yet other cheap phones can search for other devices so easily.. please I need a solution immediately
I finally managed to get Bixby Routines reinstalled on my phone (it was in the Galaxy store and I somehow either missed it every single time I looked, or they just added it). I am using it to send Spotify to my various bluetooth devices while all my notifications play on the phone. I have it set up with 3 devices - an Anker Soundcore, a pair of SkullCandy Ink'd Wireless earbuds, and my 2015 VW Golf. I'm running into some weird issues, though. Note that all 3 routines are set up the same way - IF BT is connected to X, THEN App: Spotify / Audio Device: Bluetooth
1. Whenever Separate App Sound is initiated, either on the previously connected device or a different device, it throws up the "Change main audio output device?" notification, meaning every time I connect to BT, I have to do that. If that's the case, why bother with the routine and not just toggle the SAS with each device manually since I need to interact anyway? When I do toggle it manually and hit OK on the notification, it works flawlessly, sending Spotify to BT and everything else (IG, Messages, YouTube, etc.) through the phone's speakers.
2. With the way the Golf head unit connects to BT, it kind of connects, then disconnects, then connects again, making the phone get weird mixed messages which triggers the routine in a weird way. Is there a way to delay the BT connection on the phone until the head unit is fully booted up?
The only thing I can figure is that maybe I'm not technically following the "make sure you choose an audio device that is different from your main audio output device." rule since when I'm connected to BT, that's the main audio output.
I recently purchased a pair of Samsung Galaxy Buds+. They are working, however the Samsung Wearable & Galaxy Buds+ plugin don't work properly.
I followed the instructions on getting them paired - Install the Galaxy Wearable app from the Playstore, open it and allow all the permissions, connect (pair) to the Buds+, let it install the Buds+ plugin and then again allow all the permissions. At this point it says I'm all set, however the app says 'Your earbuds aren't connected to your phone'. I click connect and I just get 'Couldn't connect to your earbuds' and can click 'try again'.
Bluetooth wise they are connected and I can play music and answer calls etc, however the Galaxy Wearable/Buds+ plugin app aren't working. I need this to be able to update the firmware on the Buds+.
I've downloaded the Windows Galaxy Buds Manager software and installed it on my Windows 10 notebook (that has Bluetooth...). This cannot connect to them at all. The instructions say to put the buds+ back into the charging case, close it and then re-open it. I do this and nothing happens. The buds+ don't appear to be in pairing mode in the case at all. I can pair them with Windows natively and they work for audio OK.
I am starting to wonder if they are counterfeit?
I have also tried with another Pixel 3a phone and the behaviour is exactly the same.
They work best with Samsung phones. Only Samsung devices support the SSC codec which is the highest resolution codec for these. If your device supports LDAC use this codec, it's supported.
Try a network reset and clear the system cache.
Make sure Wearables has all needed permissions or it will not load. (I'm not sure if Wearables works on non Samsung phones.)
Test by trying them in a phone call to see if bt is connecting. You should also hear a brief tone when you place them in your ears.
Once Wearable is working properly it will prompt you if they're are updates or you can request it check.
Updating; leave case open. Make sure both buds are nested. Do not interrupt the process, it may take a few minutes. Don't move or use the phone. A bad flash can't be corrected except by Samsung.
I've updated them in my ears but that's not the preferred method.
My Buds+ thread, more details:
Galaxy Buds, Buds+ Set up
Install the Galaxy Wearable and Galaxy Buds software. Update software and Buds firmware, this is important because the old versions sound sucks. Turn on/go to Developer Options in Settings and on the Bluetooth Codec setting toggle on Samsung's...
forum.xda-developers.com
blackhawk said:
They work best with Samsung phones. Only Samsung devices support the SSC codec which is the highest resolution codec for these. If your device supports LDAC use this codec, it's supported.
Try a network reset and clear the system cache.
Make sure Wearables has all needed permissions or it will not load. (I'm not sure if Wearables works on non Samsung phones.)
Test by trying them in a phone call to see if bt is connecting. You should also hear a brief tone when you place them in your ears.
Once Wearable is working properly it will prompt you if they're are updates or you can request it check.
Updating; leave case open. Make sure both buds are nested. Do not interrupt the process, it may take a few minutes. Don't move or use the phone. A bad flash can't be corrected except by Samsung.
I've updated them in my ears but that's not the preferred method.
My Buds+ thread, more details:
Galaxy Buds, Buds+ Set up
Install the Galaxy Wearable and Galaxy Buds software. Update software and Buds firmware, this is important because the old versions sound sucks. Turn on/go to Developer Options in Settings and on the Bluetooth Codec setting toggle on Samsung's...
forum.xda-developers.com
Click to expand...
Click to collapse
They were counterfeit. I returned them to the seller and got a refund. I have since bought a refurbished set that are genuine and the app works fine with them.