Related
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)
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
with me Meizu m1 note is exactly the same
barraker said:
with me Meizu m1 note is exactly the same
Click to expand...
Click to collapse
I guess to have Android 5.0 is not the only requisite to use Android Auto... maybe Google should take a look on this..
chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse
try to experiment with other phone with android 511 or higher and with a good quality USB cable
war1 said:
try to experiment with other phone with android 511 or higher and with a good quality USB cable
Click to expand...
Click to collapse
I tried with Huawei P8 lite and Moto G 1st gen (both 5.0) and I got nothing. It works with Nexus 5
Moto G 1st gen the same
Also Moto G 4G
I had the same problem in my Astra.
I've solved it following this steps:
- Wait until the bluetooth connection is fully established.
- Unlock the smartphone (i think is key for this problem)
- Plug the USB cable.
I'm doing it that way since last two weeks and i haven't seen the black screen again on my Intellilink.
Hope it helps.
I have same problem whit samsung A5 (android 5.1).
And secound problem with android auto app (ver. 1.5) in huawei p8lite.
I try connecting phone (android 5.0.1) to opel Astra k.
It works but doesn't refresh screan.
I must tourn on or down the volumne and then screan updates.
Any idea ?
Any workaround about this issue? I'm having the same problem with my Honor 7. Already contacted the Opel Team but that issue seemed to be new to them. I guess it's rather and android/google problem than that of the carmaker. A friend of mine is having the same problems with his Huawei Smartphone, while his wife's Samsung is working.
Both Huwaei/Honor phones run with Android 5 and 6, respectively....
I have an Opel Adam with the Intellilink system. I have the same problem, when connecting Android Auto all I get is a black screen. Sometimes it works and when it does it's really reliable. But it is very rare that it works. I have tried a dozen different phones.
I was wondering if you have Flexdock on your Astra? I have Flexdock on my Adam and I have been thinking if this has something to do with it.
By the way, Apple Carplay seems to work okay. It connects every time but I would prefer using Android.
chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse
erke_ms said:
I had the same problem in my Astra.
I've solved it following this steps:
- Wait until the bluetooth connection is fully established.
- Unlock the smartphone (i think is key for this problem)
- Plug the USB cable.
I'm doing it that way since last two weeks and i haven't seen the black screen again on my Intellilink.
Hope it helps.
Click to expand...
Click to collapse
I am also having this problem despite following these steps... any suggestions? So frustrating as it work sometimes....
Luke.bartholomew1 said:
I am also having this problem despite following these steps... any suggestions? So frustrating as it work sometimes....
Click to expand...
Click to collapse
Same here. These steps didn't help me.
And to add to the misery, AA stopped working completely. The app won't launch anymore when connecting the phone to the car. I'm not getting the black AA splash screen anymore and the car's head unit won't recognize the connection. So I kinda got rid of the black screen problem I have tried clearing cache, uninstall followed by reinstall, pretty much everything besides restoring the phone to factory settings.
chema88 said:
I´ve bought an Opel Astra K and I want to use Android Auto, but the car screen is always black.
The supossed requirements to run Android Auto is to have a phone with Android 5.0. I have an Elephone P7000 with Android 5.0 and Android Auto installed. When I try to use it in my car, Android Auto starts in my phone (I see the black screen which shows "Android Auto" title) but the screen in my car is always in black.
Could someone tell me what I need to run Android Auto with my phone and my car?
Should I buy a new phone for this end?
Thanks and regards
Click to expand...
Click to collapse
There appears to be major problems with Android Auto and Intellilink 4.0. My car has been into the dealer 3 times in 3 weeks (only just bought it!) And Vauxhall have drawn a blank on what's going on, although Vauxhall have confirmed they know there are problems with their system. I've also got Google on the case analysing debug outputs from my phone by the Android Auto team at Mountain View.
So long as you have installed Android Auto on your phone and responded to the setup prompts, that's all you can do. My car touchscreen often just blanks when I connect the phone too. It is driving me mad.
mjt0801 said:
There appears to be major problems with Android Auto and Intellilink 4.0. My car has been into the dealer 3 times in 3 weeks (only just bought it!) And Vauxhall have drawn a blank on what's going on, although Vauxhall have confirmed they know there are problems with their system. I've also got Google on the case analysing debug outputs from my phone by the Android Auto team at Mountain View.
So long as you have installed Android Auto on your phone and responded to the setup prompts, that's all you can do. My car touchscreen often just blanks when I connect the phone too. It is driving me mad.
Click to expand...
Click to collapse
Okay, that figures. I remember now reading something about Opel/Vauxhall knowing about this problem before. I contacted Opel too and they told me visit the dealer but after what you told, I guess I will pass and let them work it out first.
smatty1 said:
Okay, that figures. I remember now reading something about Opel/Vauxhall knowing about this problem before. I contacted Opel too and they told me visit the dealer but after what you told, I guess I will pass and let them work it out first.
Click to expand...
Click to collapse
I've booked my car in with the vauxhall dealer to have it looked at... However when i said my problem was with android auto, the guy said "what's android auto?" :crying:
So I'm not filled with hope.... On the upside however, I contacted vauxhall head office and a very helpful lady (who knew what android auto was!) said that because it works sometimes, the issue lies with their system and not android auto (so potentially fixable without Google...
She said that there have been a few similar complaints aswell but these were resolved....fingers crossed because it's great when it works... Will update
Luke.bartholomew1 said:
I've booked my car in with the vauxhall dealer to have it looked at... However when i said my problem was with android auto, the guy said "what's android auto?" :crying:
So I'm not filled with hope.... On the upside however, I contacted vauxhall head office and a very helpful lady (who knew what android auto was!) said that because it works sometimes, the issue lies with their system and not android auto (so potentially fixable without Google...
She said that there have been a few similar complaints aswell but these were resolved....fingers crossed because it's great when it works... Will update
Click to expand...
Click to collapse
Would you mind letting us know if the dealer was able to do anything to fix this? I would be interested to hear anything you could tell after the service.
I really hate being stuck on an iPhone and Carplay, which has its problems too, it keeps dropping connection randomly
smatty1 said:
Would you mind letting us know if the dealer was able to do anything to fix this? I would be interested to hear anything you could tell after the service.
I really hate being stuck on an iPhone and Carplay, which has its problems too, it keeps dropping connection randomly
Click to expand...
Click to collapse
Will do. Taking it in tomorrow.
With your issues does it ever work? As i tested it an hour ago and everything was fine.... Tested it 5 minutes ago... Black screen is back
Luke.bartholomew1 said:
Will do. Taking it in tomorrow.
With your issues does it ever work? As i tested it an hour ago and everything was fine.... Tested it 5 minutes ago... Black screen is back
Click to expand...
Click to collapse
It used to work at times, but most of the time I would just get that same annoying black screen. But now it won't even give black screen anymore, nothing happens when plugging an Android phone.
smatty1 said:
It used to work at times, but most of the time I would just get that same annoying black screen. But now it won't even give black screen anymore, nothing happens when plugging an Android phone.
Click to expand...
Click to collapse
So I took it to the dealer and after explaining to them what android auto actually is!! We plugged the phone in and it worked. 10 times in a row....I hate intermittent problems .
So the guy said there was nothing they could do since it was working now but to bring it back if it stops again.... Getting the S7 edge next week so will wait and see how that works.... Apologies i haven't got a better answer for you...
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.
I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?
Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.
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.