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)
My Nexus 6 keeps forgetting my Bluetooth pairs. I'll wake up and notice that my pairs are gone. Which is an annoyance with my car and Android Wear watch. It happened once before but then when it happened last night I know there is an issue. It started after I upgraded to Marshmallow. I'm running the MRA58R build. Any ideas?
I have the same issue...ever since marshmallow...both 6.0.0 official and 6.0.1 official, both times before installs the phone was wiped...but never the less it always forgets my bluetooth pairs
it seems to correlate to when the phone fully dies. If the phone fully dies 1-2 out of 5 times it will boot back up without the bluetooth pairings.
Also if I don't pair my Wear watch(original 360) this does not seem to happen either
I'm having this issue as well. My phone will randomly ask to pair with my car, even though it's been paired already. And sometimes it will just ask me to allow it to share Messaging, which was also already set. It's frustrating. I've only noticed it with Marshmallow.
For me it doesn't seem to correlate with charge level.
Having the same problem here and now that you mention it, it does seem to happen when it fully dies. Until someone comes up with a solution I'm going to see about backing them up and restore if it happens again.
Allowing your phone to completely die is a bad idea. The sudden shut down is what is corrupting it.
Also restoring that type of system data is just asking for other random issues, also not a great idea.
While I run an AOSP based rom I have never had my device forget any of my 5 BT pairings.
I agree don't let phone die.
Also if low battery plays a role (before phone dies), it could be related to battery saver features that can activate at low batteries level. (Adjustable in settings)
For the android wear app, turn off battery optimization (to prevent it from being interrupted by doze. )
I have had zero disconnection between my n6 and my moto 360 g1 android wear watch in the last month.
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
My phone has done this now twice in three days on N Preview 3. Has anyone found a solution?
mine does it too. but it will forget ALL my paired devices. it's pretty annoying
This is happening to me as well. Nexus 6 is forgetting all paired bluetooth devices.
Most annoying is the Android Wear issue because I've been having to factory reset the watch to get it to pair again. Some of this might be the watch because I'm running a Samsung Gear 2 with Android Wear but I also have several other devices that I have to repair every time.
Also seems to correlate with the battery dying.
There has to be a common bug. As all my devices have no issue remembering the pairing. Mind you I also dont pair to my car.
Also keep in mind that it was found long ago that OEM put in lists of cars that it will not work with in their roms. We found it on samsung devices years ago where it would block all connections to BMW, Audi and a few others.
N6 running 6.0.1 (no root)
This just started happening to me yesterday but has happened twice so far in two days. My phone has not died as seems to be a symptom for others here. It did get below 10% today but I charged it up without issue. it wasn't until several hours later that it wiped all of its paired devices. below is a list of my paired devices:
Samsung ATIV book 8 (windows 10)
UE Mobile BoomBox
Moto360 2nd Gen
2014 Infiniti Q50
2015 Nissan Murano
After it wiped everything yesterday I re-paired the following:
Samsung ATIV book 8
Infiniti Q50
Moto 360
After the first wipe today I paired the watch and the car.
If anyone has any ideas I would be grateful. This is a GIANT PIA!
Does not look like there is a solution to this forthcoming... is there anyone with this problem that's recently updated to N? And has it gone away? I get this usually after a forced reboot... all bt settings gone. Totally a problem.
Any update on this. I think it started happening after I updated to 7 and then went back to 6 after having battery issues?
rkshack
Giant PIA
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5. I drive a lot for work, and need my phone paired to a JVC headunit (listed as JVC UNIT on my phone) in my van so I can take phone calls handsfree, and listen to podcasts. Every now and again, maybe once a day, with no rhyme or reason that I can discern, I get into the van and notice that my phone is not paired. It's a pain to have to pull over and re-pair the phone, and then set it up a a trusted bluetooth device again (so as to avoid entering my passcode whenever unlocking the screen).
- Definitely nothing to do with battery levels. My phone is normally fully charged and plugged in to a charger.
- I don't lose all paired devices, as my UE Boom 2 (not often used) is still listed as a paired device, whereas the JVC UNIT drops off fairly often.
Please could someone sort this issue out! It sounds like quite a few people are experiencing it.
thanks,
Phil
Phil in NZ said:
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5.
Click to expand...
Click to collapse
Not likely to get sorted for your phone in this N6 thread. [emoji6]
I am on Android 11 and it still happens to me, my car pairing is being forgotten from time to time. Happens to any of you?
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'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.
Whenever i plugin my s21 ultra to my kia seltos for android auto ,
Even on idle without the music playing / navigation the phone heats up like crazy .
I have tried resetting the infotainment on my car as well as the android auto app on my s21 ultra but nothing gets better .
Anyone can help out ?
It heats for me FWIW...I was initially fascinated by android auto but considering the damage it does to the battery I seldom use it...
I don't find mine heating up more when using AA, but I use it wirelessly. Now, my headunit is an Android powered one, so we're comparing apples to oranges, but on on the phone it should be the same.
What I don't like is that lately AA started to control the headunit beyond what it used to : turns on BT and WiFi all the time, because the headunit stays in low power mode for a while after turning off the engine, I find myself at home getting calls and audio gets routed to the car despite me being inside.
I gave up on it....
aj7400 said:
Whenever i plugin my s21 ultra to my kia seltos for android auto ,
Even on idle without the music playing / navigation the phone heats up like crazy .
I have tried resetting the infotainment on my car as well as the android auto app on my s21 ultra but nothing gets better .
Anyone can help out ?
Click to expand...
Click to collapse
I have yet to test it out however will do so . I did check on play and they have a beta programme which is currently full. Maybe use a service like APKMirror to try the beta? See if that fixes your issues
Try clearing system cache.
Disable all power management... destroyer of worlds.
Try using the factory load version of the apps causing trouble.
Parent apks, dependencies... the apk causing the trouble may not be the obvious one
Check memory and individual battery usage to help isolate the apks causing trouble.