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?
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time
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've had this happen in numerous GM Vehicles from 2016-2018 Chevrolet, Cadillac, GMC units with AA.
While using Waze or Maps I can run fin 90 percent of the time
While using the above and a music source like I heart or Stitcher I get frequent crashes. My phone will reboot. But when it reboots, I dont have bluetooth connectivity. I have to unplug the phone, Reboot a second time and pluf it back in.
This is annoying and hope there is a solution
Im running the latest versions of Apps on my Galaxy S8 with a Samsung Data cable that came with my phone.
I was recently using an oppo r7sf with lineageos installed and had similar problems. Spontaneous Communications error 12 but no reboot. AA would crash on the head unit and I'd have to reboot in order to get it working properly. Tried many many things but in the end got a new phone and havent had an issue since.
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.