This is sort of a dumb questions but is there any preferred order when using Android Auto to turn the car radio off? What I mean is should I unplug the USB from my phone first when Android Auto is active, or should I shut the car down (radio turns off), then unplug my phone, or does it not matter?
It took a while to get my Android Auto to work, I just kept trying and it looks pretty cool. I'm using a AVIC-8100NEX with a Sony Xperia Z3 compact unlocked running 5.0.2. The only bug I've had is for some reason, my phone lost the bluetooth pairing with my radio after the 3rd time I used Android Auto. I never had this problem before with this phone or radio during normal use. I was curious if it was the way I shut it off.
Thanks for any help
Jason
For me, it seems best to turn off the car then unplug the phone.
But here, it is much more important how you connect than disconnect. If I turn on bluetooth on the phone, start the car and wait for bluetooth to connect, and then plug it in, everything works fine. But if the phone is plugged in before the NEX is on, it will create a new pairing in favor of the old one. And sometimes it will delete the pairing entirely.
Weird.
Solutions Etcetera said:
For me, it seems best to turn off the car then unplug the phone.
Click to expand...
Click to collapse
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Solutions Etcetera said:
For me, it seems best to turn off the car then unplug the phone.
But here, it is much more important how you connect than disconnect. If I turn on bluetooth on the phone, start the car and wait for bluetooth to connect, and then plug it in, everything works fine. But if the phone is plugged in before the NEX is on, it will create a new pairing in favor of the old one. And sometimes it will delete the pairing entirely.
Weird.
Click to expand...
Click to collapse
Wow, I've been searching everywhere for someone with the same issue as me and tried figuring out why my phone keeps (intermittently) forgetting my car as a bluetooth device after I've connected it to Android Auto. I will be testing out your suggestion, thanks beforehand though, I never would've guessed it had to do with the order you connect it in, rather than disconnect.
mrnmukkas said:
Wow, I've been searching everywhere for someone with the same issue as me and tried figuring out why my phone keeps (intermittently) forgetting my car as a bluetooth device after I've connected it to Android Auto. I will be testing out your suggestion, thanks beforehand though, I never would've guessed it had to do with the order you connect it in, rather than disconnect.
Click to expand...
Click to collapse
My comments were based on using AA with a Moto X. Now that a Nexus 6P is my daily driver, I just plug it in, make sure it is unlocked, and start the engine. I don't even turn BT on anymore as AA does that automatically.
No issues this way in over a week. Nice to be Nexusing again!
Solutions Etcetera said:
My comments were based on using AA with a Moto X. Now that a Nexus 6P is my daily driver, I just plug it in, make sure it is unlocked, and start the engine. I don't even turn BT on anymore as AA does that automatically.
No issues this way in over a week. Nice to be Nexusing again!
Click to expand...
Click to collapse
Odd, I've been having these issues first with my Nexus 6 and now Nexus 6P. It just sometimes removes my car from the saved bluetooth devices list and the next time I get in the car it demands to be paired again. Anyway, I'll try your solution and report back.
Alright, so I tried letting the bluetooth connect and then plugged in the cable, unfortunately that still made my phone forget about the car as soon as I disconnected it.
However, your last message got me thinking, maybe I'm overcomplicating this. I've noticed that the phone indeed does get connected to bluetooth, regardless of whether I pair it if/when it prompts me or not, Android Auto does seem to handle the pairing by itself.
I've only once noticed that the phone actually failed connecting and that was with my Nexus 6 which always felt like it had a wonky bluetooth. That time I couldn't place a call with the car handsfree, or even start the "phone app" on the Auto screen. So far the phone app has never refused to work on my Nexus 6P, regardless of if I skipped the pairing request.
So the best method I've found is to plug the phone to the USB before starting the car, this way it doesn't even prompt me to make a bluetooth connection, it just starts Android Auto right away and does the pairing automatically.
The only nuisance with this solution is that I get a new Smart Lock notification every time the phone connects, but I guess I can live with that (though it's not very elegant).
mrnmukkas said:
The only nuisance with this solution is that I get a new Smart Lock notification every time the phone connects, but I guess I can live with that (though it's not very elegant).
Click to expand...
Click to collapse
Yeah, I've seen that with all my phones. Be nice to turn that off but haven't found a way short of completely turning off smartlock.
Would this imply that you are alone? Here is the reason for my question:
Pull into the train station, Wife will be driving the rest of the way to work. I unplug my phone because i take it with me. HU goes back to Main Menu, she plugs her phone in and says "Play Music" ,she then drives to work listening to her own music. I dont think using AA should force us to power off the car before unplugging. We do this scenario everyday and have never had an issue. Just wanted to throw that into the conversation.
mikereidis said:
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Click to expand...
Click to collapse
BPryde said:
Would this imply that you are alone? Here is the reason for my question:
Pull into the train station, Wife will be driving the rest of the way to work. I unplug my phone because i take it with me. HU goes back to Main Menu, she plugs her phone in and says "Play Music" ,she then drives to work listening to her own music. I dont think using AA should force us to power off the car before unplugging. We do this scenario everyday and have never had an issue. Just wanted to throw that into the conversation.
Click to expand...
Click to collapse
In the end, I don't think it's a big deal to worry about order, unless one method crashes or has other bad results.
The reasonings I gave are IMO rather tiny, and "split some hairs", just to come down in slight favor of one order over another.
Do whatever works for you and save your worry for the bigger issues in life...
New hybrid or electric drivers may ask "How do I drive it". Answer: just like any other car or however suits you.
mikereidis said:
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Click to expand...
Click to collapse
I have had the opposite experience in my 2016 VW gti. I have to unplug before shutting the car off.
With 3 different HTC(m9, a9, 10) phones, and the galaxy s7, if I turn the car off before unplugging I will have to pair the phone again. AA will auto pair it, but I still have to give the car message access and dismiss the new smart lock notification.
Old but relevant thread
I am using a Samsung A8 with a 2019 Subaru HU. I too have been having success with unplugging the USB cable first before turning off the radio/engine. Without power to the USB port as on turning off the engine, it seems to mess with the handshake randomly. For now, every time I stop and park I pull the cord first. Seems to better handle the disconnect better, but time will tell.
Wilbour said:
I am using a Samsung A8 with a 2019 Subaru HU. I too have been having success with unplugging the USB cable first before turning off the radio/engine. Without power to the USB port as on turning off the engine, it seems to mess with the handshake randomly. For now, every time I stop and park I pull the cord first. Seems to better handle the disconnect better, but time will tell.
Click to expand...
Click to collapse
I rarely do this because I am lazy. But for me the best way to disconnect is to pull the notification that is telling me that android auto is connect to my phone and then touching the option to disconnect it. Sometimes when i simply disconnect the USB the android auto app on my phone complains about a connection error code xxx (I forgot the exact code)
Workaround that works 100% of the time for those having trouble connecting.
Unlock phone and turn on car or head unit. Note you should have android auto installed already before this will work. Plug in the cable to your phone and you will hear the link sound and the screen on your phone will flash off for just a second. As quickly as possible once the screen goes black on your phone uncable the phone and reconnect it. I know this sounds janky, but it really works. You can tell it is working by the screen on your head unit going black in the background and you will see the android auto icon sI have tried all suggested fixes and this is the only one that works 100% of the time. It also does not take over the telephone's display so you can navigate to other apps and still have android auto running. It is quick and gives you the best of both worlds. I almost returned my 2016 gti due to the frustration from this issue, but now it is no big deal.
Hope this helps guys and gals.
No. For what I read , the only API available for 3rd parties are to send messages and music, and that, using google interface. No other developer can do anything with AA.
I upgraded my Z3C to MM a few months ago, and since then I've started noticing that bluetooth seems to be off most of the time. Under KK it was on all the time and rock solid - it was always there, and for example the phone would always connect to my car when I started the engine. Now, BT on the phone is off more often than on, which is tedious, especially when I don't notice that the phone doesn't connect to the car, and then a call comes in
I've verified that BT doesn't come back on after a manual restart, which it always used to. The phone always restarts after running its Titanium backup overnight, so that could be why BT is more usually off than on. But as I say, it didn't used to be like that. I will be keeping a closer eye on it in future to see if BT turns off at other times for no apparent reason.
Does anyone know if there is a new setting in MM that could be causing this, or have any other suggestions as to how to go about preventing this extremely annoying behaviour?
TIA
OK, so it now seems to be confirmed that Bluetooth doesn't come back after a restart. The question is: why? It never used to behave that way. I'm pretty sure now that it's since I upgraded to Marshmallow that it's being doing this.
I'd dearly love to find a way to fix this!
Update on this problem: around the turn of the month it went away - bluetooth came back on after a reboot just like it had always used to. No idea why, or what if anything caused the change. Most likely a app somewhere was my guess, since that's all that changes on the device these days.
However, after a week or two the problem came back. Again, I'd changed nothing apart from allowing apps to update.
In order to investigate the app hypothesis further, I tried restarting the phone in safe mode. No joy. Normal mode, bluetooth on; restart in safe mode: bluetooth doesn't come back on. Safe mode, bluetooth on; restart in safe mode: bluetooth doesn't come back on.
So it looks like it's not an app after all.
I have now found a workaround using the Smart Connect app to schedule a task which turns bluetooth on in the early hours of the morning. But it's annoying that I have to do this when the problem simply shouldn't be happening.
Bluetooth is a ***** on MM
Try the following: Switch BT on - Be sure that it can connect to any device. Leave it on - Do not switrch BT off now.
Reboot and wait until system full stated.
Now it should work stable - even if you switch it on/off.
After that: Be sure that you have BT ON before reboot.
Hi
I have a strange issue when using Android Auto on car head unit through my Mi9 MIUI Global 11.0.5.
Everything connects fine as expected and everything displays correctly until the phone screen times out, then the car head unit loses roughly a quarter of the right hand display (has overlay of black bar from top to bottom of screen). The icons / screens still work if pressed where graphics would be, but they are not displayed.
i have tried altering notch setting / full screen display settings but nothing corrects the issue.
......any ideas?
Thanks in advance.
Mr E Weasel
This is the same problem as in a non MIUI (AOSP) rom. Disable HW overlay in developer option solves this.
However. This shouldn't be a problem on a MIUI rom that's why I don't use the AOSP ROMs for now.
So it's very weird.
......thanks for the reply and good call @KaiseRRUby. I tried that but as you probably suspected it did not solve the issue, also the state does not persist after a reboot.
DUPE
Having the same issue since updating to Miui 11. Have you found a solution?
taliesyn said:
Having the same issue since updating to Miui 11. Have you found a solution?
Click to expand...
Click to collapse
......not yet, I will endeavour to post back with any successes
Same problem on Mi 9T Pro here.
I have enabled developer options and enabled the option to keep phone awake while charging.
taliesyn said:
Having the same issue since updating to Miui 11. Have you found a solution?
Click to expand...
Click to collapse
I did a workarround by using the free Android application "Automate" by LLamaLab. I setup a basic script looking if i am in my car (Check car bluetooth connectivity) and then delay the screen lock. When not in my car anymore (no more car bluetooth connectivity) re enable the screen lock as it was.
It is working like a charm.
I had same problem, you can turn on Always on display it will fix it
UPDATE:
Only way round it I have found so far is to use tasker (https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm) to display full black screen and set screen time out to max time when it see Android Auto launched.
discerrrr said:
I had same problem, you can turn on Always on display it will fix it
Click to expand...
Click to collapse
I've always had AOD activated and it does not help.
The solution for me was to enable keep screen on while charging in developer settings. Since the phone is always plugged in for AA, it works fine.
I don't know why some resolve to using scripting apps for this. Did you try this setting and it did not help, or maybe you don't want to keep the screen on while charging ? You can always turn it off by pressing the power button, so it seems like the almost perfect solution to me.
I recently started getting a lot of AA disconnects from my Samsung phone and my AA stereos - I have an Android Chinese unit as well as a Kenwood Excelon in my second car. Thought the cable might be the issue but that didn't seem like it.
I went in to the apps menu and found that under system apps, there are 2 more AA related apps. Proceeded to turn off battery optimizations for all 3 and now it seems to be running stable.
The apps are:
Android Auto (DUH!)
android.auto_generated_rro_product__
android.auto_generated_rro_vendor__
You're the f'ing man! I could kiss you.
Didn't work for me.. only fix I have found is tap the usb options [while plugged in] on phone and tell the phone that the plugged in device manages connection.. unfortunately this setting does not remain set after use.