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 have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.
BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0
Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.
Up
Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.
Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.
Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.
I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV
Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.
I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.
It doesn't matter how many times I turn the wifi off on my nexus 6, it seems something keeps turning it back on. Im not sure how long it will take to turn back on, but I will look at my phone and notice that its back on again. It also doesn't matter what wireless AP I am by.
Is there a way to see what app, or whatever, is turning it on so that when I disable wifi, it's actually disabled until I change it otherwise?
I've been having something similar, coupled with my wifi disconnecting and reconnecting in a loop every thirty seconds. I'll notice my wifi looping like this, so I'll turn wifi off, only to have it turn back on by itself within ten seconds and start looping again. Really strange. This began about two days ago out of the blue. I haven't been able to pin it down to anything.
I'm running stock 6.0.1, Jan 2016 OTA.
therealcrazy8 said:
It doesn't matter how many times I turn the wifi off on my nexus 6, it seems something keeps turning it back on. Im not sure how long it will take to turn back on, but I will look at my phone and notice that its back on again. It also doesn't matter what wireless AP I am by.
Is there a way to see what app, or whatever, is turning it on so that when I disable wifi, it's actually disabled until I change it otherwise?
Click to expand...
Click to collapse
Just wanted to follow up so you could check if this applies in your situation.
I finally found the culprit! I decided to reboot into Safe Mode to disable all third party apps and see if it still happened. When in Safe Mode the wifi was rock solid! That told me it was some app causing my problems. So I uninstalled several apps to try to narrow it down, especially those that had been updated recently and rebooted normally. It still looped the wifi.
After banging my head against the wall, I decided to go to developer options, show running processes, and see what apps were running that could be messing with the wifi. The normal apps you would expect to be running were listed, plus the MyAccount app from StraightTalk.
Why the heck would that app be running a process? I opened the ST app and looked through it's options. Low and behold was a section called wifi management. Holy crap, this could be it! I look in that section, and it was set to manage my wifi and connect and disconnect when sufficient access points are nearby. I turned that off, closed that app, and verified in Running Processes that it was indeed gone. It was, and my wifi has been solid ever since.
Stupid, stupid app!
OH MY GOD. This has been driving me nuts. Thank you so much!
Hi, a few months ago I've noticed that when I try to turn on bluetooth (which is usually turned off) everything freezes the moment I 'click' on the turn on/off switch. After the freeze it takes around one-two minutes to restart the phone and then I can normally turn the bluetooth on.
The strange thing is that I can turn it off and on then and it will work, but when I turn it off and leave it off for a few days, and then try to turn it on the phone will freeze again...
Did anyone had the same issue?
Android version: 7.0 (B394)
I installed B395, but the problem hasn't gone away. Anyway, for the first time after this 'freeze' the message box saying that 'the interface app stopped working' showed up and I could 'stop' the interface app.
However, the update did not solve the problem.
Same problem here did you find a solution?
Same problem here for years! Android 7.0. Did anyone found any solution yet?
My build number is EVA-L09C432B505. Stock firmware, regulary updated.
@zozo77, Have you regularly updated your stock firmware?
What is your full build name/number, like EVA-L09c432b504 or what?
PS: @Chelmiannin
Since this was a question for help, it should have been opened as a regular thread, not for voting, so that people can normally cite and answer
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.