So Sunday I rolled into our family favorite Honda dealership, and I rolled out with a 2012 Honda CR-V AWD EX-L. Didn't get the Navigational system, as per reviews it looked outdated and cheesy, and I have the Galaxy Nexus official car dock with charger coming from expansys any day now.
Paired the phone at the dealership, and was able to play some music. But the connection dropped briefly, causing music to play out of the phone. Then about 20-30 seconds later it reconnected, and a few seconds later the music played out the car speakers.
Didn't think too much of this, but I drove it home and the next day noticed the disconnect / reconnect issue was pretty consistent. And every time it happens, you can't control the Radio or do other things, cause the screens talking about the connection prevent changes. Not life or death, but certainly annoying on occasion.
Yesterday, I determined that by connected an AC Adapter to the phone, the disconnects go away and things work normally. That was a pleasant surprise, and while I don't want to take the phone out of my holster and connect it EVERY time I get in the car, at least I have a work around, right?
The odd thing is, this never happened with my Sony BT Car Deck I had in my Civic. Obviously it wasn't a stock solution, but when the volume knob on the stock deck was failing, a new stock deck was $400. I got the Sony solution for $150 installed at Circult City, and it had bluetooth which allowed me to make and take calls, stream music, etc.
The only catch I've found so far is the car seems to inquire about me transferring my contacts into the car so the phone book is available through the dash. But every time I click allow... it doesn't seem to do anything and the message shows shortly again in the "notification bar" of the phone. I'm ignoring it for now.
I did root the phone and apply the 4.04D update, then the system update saw the 4.04I update and applied that. Wondering if a factory reset might not put me back to 4.01 or something, but might not resolve this issue. Unless I have any advice, I think that's what I'll try next.
I thought about updating the baseband radio, but as I didn't install CMW or anything, pushing the radio update is a little more work that I'm ready for at the moment.
Thanks to any who took the time to look at this. Best wishes!!!
Little update. I had unlocked my phone, but hadn't properly rooted it, flashed the ROM, etc. Took me a while this morning, but I rooted it, installed CWM on the recovery partition, and then updated the radio to UGLA4.
Despite the above, the car still "drops" the BT connection about once every two minutes, and then makes the connection again about 10-20 seconds later. If the phone is plugged into the car so it has extra power, the connection stays up and reliable until it is unplugged or the car is turned off.
Not sure what to try next, if Honda doesn't have a BT update for the radio in this car. Here's hopiing!!!
FIXED!!! So here is the problem AND the solution.
Dunno why, but something about the default bluetooth.apk that is in the Galaxy Nexus, even after the 4.0.4 update was NOT working between my phone and my CR-V.
The "hint" to the fix was found here. http://forum.xda-developers.com/showpost.php?p=14249943&postcount=11
After killing this process, my connectivity issue between phone and car disappeared. But the phonebook STILL wouldn't update.
Feeling I was getting somewhere, I did searches for the BluetoothPbapService, and so forth. After some looking, I finally found THIS site. http://forum.android-rsap.com/viewtopic.php?f=33&t=221
I had unlocked my phone once, but hadn't rooted it properly. While trying to fix this issue, I'd rooted it, installed the CWM recovery menu, and tried a couple different "broadband" software packages that control the radio. That hadn't fixed the problem, but I COULD use Root Explorer with SU rights afterward.
So I downloaded the file for Android 4.0 to the Downloads folder on my GN. Then I created a new folder on the SDCard called backup. I moved the Bluetooth.apk and .odex files that were in /system/app into that directory, moved the .apk file I downloaded from that site back into /system/app, and made sure the permissions were as directed. Then I rebooted the phone.
Once down at my car, I removed ALL Bluetooth profiles from the car, clearing the BT settings completely. And then I deleted the BT profile from my phone. Then I turned on BT on the phone, pressed the phone button on the dash, and paired the phone as before. Only THIS time, the phone paired normally, didn't disconnected, and when I clicked phonebook, it seemed to do nothing as before. But a SECOND click on Phonebook, and instead of trying to download again... I GOT LETTERS to lookup names!!!!!
I tried a couple calls, and people didn't answer, but I can call and use the BT in my car normally!!! OH HAPPY DAY!!!
Took the CR-V in, got my proper plates put on, they washed the car for me (looks great!), and I ran a few errands. Having sat around doing laundry and watching Batman Begins, I wondered about getting the Media option on my Galaxy Nexus to disable like I'd tried in the past. That way, I can listen to the radio, but if I'm using my turn-by-turn directions over Google Maps, I can her Nav instructions through the phone.
I did a BUNCH of searching, and lots of people had similar issues. But one one had found a way to disable the "media" part of the Bluetooth stack. Remembering some people found that killing the PBAP process of the Bluetooth stack in Apps allowed them to sync their phone to their car, I wondered if it would help with my media issue. So I disabled it and went down to the car.
At first, there was no difference. Media went through the car, and nothing was any different. I unpaired the phone from the car, cleared the car BT setup from all devices, and started over. Once again it popped up as it always had, and I tried telling it NOT to pair every time automatically, but don't pop the HandsFreeLink message. This didn't seem to work, as the phone would disconnect and reconnect as it had in the past.
Frustrated, and ready to give up, I cleared the pairing on both sides, and went to put it back how I started. But when I cleared the car and went to pair again, I added my Galaxy Nexus, and waited for the message to come up about pairing going forward. It never came. And ironically, the car was NOT paired for media, just the phone.
Feeling brave, I connected the phone to the car with the media checkbox. It connected, and I was able to play a song through the car stereo. Figuring it wouldn't disconnect, I tried anyway... and it DID! I then turned off the phone, and off the car. Turned the phone on, the car back on, and everything KEPT working!!!
Obviously, I need a little more testing to be certain. But lt looks like I may have stumbled across a setting or something that allows me to use the phone however I wish. And that is a VERY good feeling.
Have no issues in a '12 Civic. You know, other than the recall.
Well, I'm back to having trouble.
Upgraded to Jelly Bean. Love the voice search which works great for me, the speed is still excellent, etc. But even after replacing the bluetooth stack the way I did in 4.0.4, I can't permenantly disconnect bluetooth audio for MUSIC through the phone. I've tried the usual fixes as above, and it just ALWAYS stays connected, assuming the car is on, and bluetooth on the phone is enabled.
SO FRUSTRATING, as then I can't listen to the radio AND use my turn-by-turn directions!!!
The wife and I have been troubleshooting this problem ourselves with weird results.
We purchased GNex's from Bell in Canada at the same time (yakjuux builds). About a month later, we leased a 2012 CR-V. Her phone has always had this connect/disconnect issue, while mine hasn't. We have returned her phone to both Bell and Samsung on separate occasions; all they have done is flashed it and sent it back. Of course that hasn't solved the problem. Provincial law in Newfoundland requires the use of hands-free when on the phone while driving, so this is issue is more than just an annoyance.
I got tired of waiting on Bell and Samsung Canada to get their act together with 4.1.1, and recently rooted my phone and moved it to a 4.0.4 takju build in order to get the system update. No problems with any of that, and it works with our CR-V, same as it always has. We hoped that doing the same to her phone would put this issue to bed once and for all, but after having run hers through the same process this evening, it still does the same trick of connecting and disconnecting endlessly (unless you force-stop the phonebook service, of course).
Now that both phones are rooted, I'm about to try copying my Bluetooth.apk on to her phone and seeing if that fixes anything.
Related
I have a Sprint Touch Pro2 running stock 6.5 ROM and a 2005 Acura TL. When I got the phone a few weeks ago, I was able to pair the two without problems and it persisted reliably. I was able to shut BT off and turn it back on and the pairing would take place immediately.
Four or five days ago, though, the pairing would drop periodically, forcing me to re-pair, and now, the pairing will disappear almost immediately if I'm able to get them to pair at all. Most of the time I can't get the phone to 'see' the car.
FWIW, I use my own 4-number PIN, and when the phone sees the car, I'm able to enter that PIN and pair them.
I of course was installing a lot of stuff on the phone, although nothing that one would expect might affect the BT, so I flashed back to the stock 6.5 ROM last night to see if it helped (it didn't- same prob today).
Before I take this thing back to Sprint and smash it on their counter, anyone have any ideas about settings I might not be aware of that could affect this?
Thanks in advance for any help.
PS: I'm going to be testing my old phone (Treo 800w) on the car later to see if it still pairs to eliminate the car as the problem.
I have had my evo since June 4. but lately it started randomly going to the car panel. So I disabled the car panel auto launch. But the evo always thinks it is connected to a car dock. When I plug in a headset the volume is locked to a medium setting. If I use the rocker switch it has no effect on the volume even though the screen shows it going up and down. That is the main reason why I want this to be fixed so I can use headphones at the level I want. I did a full reset and when the phone restarts right into car dock. I flashed different roms and first thing car dock... This leads me to believe it is a hardware issue. There is another post but the info is limited and no solution was found. Also The hd2 had a similar problem but no real solutions were found. I would appreciate any input on how to solve or work around this... thank you
Possible work around: If bluetooth is turned on and uncheck the car dock box the volume control on the headset works
cphancock1 said:
I have had my evo since June 4. but lately it started randomly going to the car panel. So I disabled the car panel auto launch. But the evo always thinks it is connected to a car dock. When I plug in a headset the volume is locked to a medium setting. If I use the rocker switch it has no effect on the volume even though the screen shows it going up and down. That is the main reason why I want this to be fixed so I can use headphones at the level I want. I did a full reset and when the phone restarts right into car dock. I flashed different roms and first thing car dock... This leads me to believe it is a hardware issue. There is another post but the info is limited and no solution was found. Also The hd2 had a similar problem but no real solutions were found. I would appreciate any input on how to solve or work around this... thank you
Click to expand...
Click to collapse
The best thing to try is to install an original Sprint EVO RUU. It should completely reset your phone to the correct settings. See if that helps. Make sure as always, you wipe everything before hand. This should let you know if it actually is something wrong with the hardware, i.e.; one of the pins on the phone connection is bent or somehow signaling to the phone that it should be in car mode.
Any word on if you got this fixed? My phone is doing the exact same thing even after a hard reset.
Sent from my Evo
If i have bluetooth turned on then everything works fine... its not a fix but it seems to work for me .... and my battery life doesnt seem that much worse either
I started having this problem when I bought a cheap ass usb cable, and I was.charging on my work pc. I got a new cable, and it stopped
Sent from the bowels of my mind....
BUMP BUMP! Wake up thread! I'm having the problem too!
My rooted EVO 4G running baked snack 1.8 is having the following issues, and they seem related as they started happening at the same time:
Cannot change headset volume (when volume rocker is pressed, graphical slider moves, but audio stuck at a low-to-medium level)
Car Mode launches sporadically without reason, even when phone is locked (had to turn off "auto launch" to stop it from popping up...it's as if the phone thinks it's being plugged into a car dock, which I don't own)
When sending/receiving a call, the external speaker turns on, I have to shut it off each time I answer a call (SO DAMN ANNOYING):
SOME MORE INFO:
This all started happening at once while I was walking down the road listening to music on my phone (i.e., no software was downloaded/changed)
I have done a nand restore to a previous point where there were no problems and the issue persists
It's not because of baked snack. This happened to me once before when I was running the stock ROM, but one day it just suddenly fixed itself. But it's been weeks and I'm tired of it.
ANY IDEAS??
kyle4miller said:
BUMP BUMP! Wake up thread! I'm having the problem too!
My rooted EVO 4G running baked snack 1.8 is having the following issues, and they seem related as they started happening at the same time:
Cannot change headset volume (when volume rocker is pressed, graphical slider moves, but audio stuck at a low-to-medium level)
Car Mode launches sporadically without reason, even when phone is locked (had to turn off "auto launch" to stop it from popping up...it's as if the phone thinks it's being plugged into a car dock, which I don't own)
When sending/receiving a call, the external speaker turns on, I have to shut it off each time I answer a call (SO DAMN ANNOYING):
SOME MORE INFO:
This all started happening at once while I was walking down the road listening to music on my phone (i.e., no software was downloaded/changed)
I have done a nand restore to a previous point where there were no problems and the issue persists
It's not because of baked snack. This happened to me once before when I was running the stock ROM, but one day it just suddenly fixed itself. But it's been weeks and I'm tired of it.
ANY IDEAS??
Click to expand...
Click to collapse
Im pretty sure it was the charger i was using just like the other post said. I got a dock charger and after a week or so the problem just stopped. Im not sure if something is getting bent or shorted or what. Try turning on bluetooth for a work around until the charger straitens things out
No headphone volume/InCar App starts...solved
Have owned the HTC EVO 4G about 18 months with no problems. These issues just started happening yesterday out of the blue.
What didn't work:
cleaned charging port w/toothbrush
toggled bluetooth settings (don't use bluetooth)
Restart
HTC update
PRL update
What did work:
Uninstalling Vlingo
-Peace Out
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
TomSilverSpring said:
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
Click to expand...
Click to collapse
Are you using an experimental ROM or stock rooted?
Jedi Mind Trick XI (although the problem has been growing worse and has happened across the last several JMT versions). I will give a stock rooted ICS a try.
I just tried a stock rom and the problem persisted.
I have the same problem
I have scoured the net looking for an answer, any answer, to this problem. It seems that a few people are having the same issue. But before it is ever answered, some dip$#!t always jumps in and says "I have the same problem, my phone won't connect to my car." Then the conversation goes off into other people that can't connect their bluetooth to their car or their headset- or their cat... That is not the same problem!!!
I cannot turn my bluetooth on unless I soft reset the phone. Even after I've gotten the bluetooth working, if I restart my phone the bluetooth turns off and when you try to turn it on, it says "Turning on Bluetooth..." It cycles for about a minute and a half and then goes back to "To see devices, turn on Bluetooth."
I bought this phone on Amazon for what appeared (at the time) to be a reasonable price. Since then, I believe that I have read at least one of the seller's post about bluetooth not coming on (no proof, just an educated guess). The seller probably got rid of the phone because noone could or would give an answer to this problem. Heck, it's possible that every post that I've read so far is by someone who owned this phone at one point or another. :silly:
I am sending this post to XDA because even the adminstrators on android forums say that you guys are the smartest and most responsive forum available. (Okay, they didn't say smartest- it was implied). Please help me resolve this issue.
I rooted this phone the moment that I pulled it out of the box. In other words, I don't know if the bluetooth issue is caused by the root, or if the previous owner didn't root the phone and also couldn't get the bluetooth to work. I believe that, because the phone is rooted, I should be able to remove and reinstall the app that bluetooth is based upon.
I am not a techie, the only reason I know anything about root is because I was complaining to someone about my old phone and how all of the bloatware that seems to constantly run eventually kills my battery. He told me about rooting, and it was easy enough - the rest is history. In other words, if you ask me for more information- I promise that I can give it to you. Yet, have patience with me if I ask you a question that you believe that any person that has rooted their phone should know.
I really hope that you guys can help me without bricking my phone. I truly appreciate any suggestions or thoughts on this matter.
jzxpw6;34880517I cannot turn my bluetooth on unless I soft reset the phone. [/QUOTE said:
I may have figured out what is going on, although I can't understand why it is (maybe someone more versed with processes can help me figure this out).
Using Titanium Backup, I first froze the two bluetooth items (Bluetooth Share and Bluetooth Test). Of course, that didn't remove anything, but I wanted to make sure that I could. Then I wanted to see how Bluetooth Share would react without Bluetooth Test. I unfroze Bluetooth Share.
I was then able to turn on and off Bluetooth fine. I restarted the phone and Bluetooth came in just like it did on my old phone. I guess I want to know:
1) Is the Bluetooth Test the cause of my problem?
2) Why is it there?
3) If I uninstalled it, would I experience a major hiccup?
There is still the possibility that this was simply a fluke, and very soon I will go back to the old bluetooth soft reset problem.
There is, however, one distinct difference between this phone and the last and may be the "drop out" that everyone else seems to be having. I have a Chevy Malibu with bluetooth in the stereo. On my old phone, when I started the car and got going, the word "Bluetooth" would appear on the digital display for about 10 seconds, which means that the vehicle detected and connected the bluetooth pairing. Yesterday, as I was driving in the car, every 5 minutes or so, "Bluetooth" would appear on the digital display.
This leads me to the conclusion that Bluetooth is dropping out and being picked up continuously by my vehicle. Does anyone have any thoughts on this? I'm okay with that as long as when I am talking to someone for more than 5 minutes I don't have to keep calling them back. I simply want to know what you guys think about this issue.
Click to expand...
Click to collapse
I am beginning to think that the problems I have had are related to the condition of the battery contacts.I have several third party batteries with contacts that are somewhat damaged from the pins on an external charger that came with them. I seem to experience a variety of problems when I try to use them.my original factory battery seems to work most of the time. I have several new Samsung batteries on order and will post again if they seem to solve the problem.
Sent from my SGH-T989 using Tapatalk 2
i had the same problem and it started with JMT so I switched roms countless times and the problem kept coming back. It would work for a little bit but when i turned it off it would not turn back on. I decided to go back to stock to see if the problem was still there and it was gone. Since then I have rerooted and once again flashing diff. rom every other day and bluetooth works just fine.
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
enveous said:
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
aaronchili said:
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Click to expand...
Click to collapse
Hey thanks! I switched to JMT JB4 and it's not happening (much) now, I'll try to flash it and see if it fixes something :good:
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.
So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!
JWhipple said:
So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
I've never had this issue before, even when I was on custom ROM. My Bluetooth works fine in car, at home, and with wireless headphones.
Sent from my Pixel 3 XL
I cleared out the bluetooth cache and storage then rebooted this morning - going to see if it makes any difference. Usually it takes a day or two before a device disappears after I re-pair with the phone. Unless anyone has any other suggestions I may do a factory reset in a few days if it happens again.
Not bluetooth but I did have all my saved wifi networks wiped after a reboot a few weeks ago. Oddly, I rebooted because my phone wouldn't connect to my Fitbit via bluetooth to sync. I rebooted and the screen was black, not responding at all. If I pressed the power button it would vibrate slightly as it does when the power menu pops up, but nothing else. After trying a few button combos I got it to reboot again and everything was fine except wifi networks were all gone.