Unfortunately, your bluetooth has stopped. How do I fix this?

[Jfquicksell]

I found a fix! There seems to be a glitch with the messages linking to the bluetooth on my 2015 GMC Sierra. When I told it not to allow messages to sync with the vehicle the Bluetooth worked fine!!! I made this change 3 weeks ago and have had no issues with the Bluetooth since!

 

[crankyyankee]

I seem to have found a permanent fix. I had this problem with my LGG2 and solved it by cleaning caches and FORCE STOPPING the Bluetooth app, despite warnings of unstable phone, blahdi blah blah. It works perfectly now, going on three weeks.

 

[Johnnyangel16]

I did the same thing, changed the setting to not allow access to text messages in a 2016 Cadillac and it seems to be working now- changing access to contacts didn't do anything. I'm thinking it's the same basic issue triggered by different access permissions depending upon what you're pairing it with- in a GM vehicle it might be access to messages, in another brand it might be access to contacts, etc. I'll let you guys know if it pops back up again, I work for a Cadillac dealer and I'm driving a different car every night, I've had my Note 5 for 2 weeks and this is the first time it's given me this problem. Oddly enough, it was fine in the same car going home last night and started doing the disconnect/reconnect cycle immediately when I got in the car this morning. I've also had a customer with an S6 complaining of this issue in a new Escalade (who insists it must be the car's fault, despite my forwarding the many forum posts about exactly this issue across the Galaxy lineup to him).

 

[erezerez]

Samsung S5 disconnects from car (ford focus) - Solved
After lots of research and losts of trial the problem was sloved for me.
The reason was the charger that was plugged into the cigarretes lighter plug.
It generated interference that caused bluetooth connection to break.
Once I replaced it with another, the problem was sloved.

 

[Johnnyangel16]

OK, it's been about a week and I can reliably say that, for a Note 5 and the Cadillac CUE entertainment system, disabling access to messages solves the constant disconnect/reconnect problem. I've driven probably 10 different 2015-16 Cadillacs with that system since my last post, and every one of them has had that problem with the phone (after having no problems at all for the first week of having the phone, so it's definitely an issue with the phone) until I disable access to messages. If I turn access back on, it disconnects within a minute or so. I don't particularly care if the car can read my texts to me or not, so no big deal for me, but for someone else it may be a big deal. Honestly, I've been screamed at worse by someone whose phone wouldn't pair to their car than I ever was because someone's engine blew up- I don't know what the hell is wrong with people these days.

 

[bhbinc]

This fix also worked for me. I denied access to my phone and contacts. So far so good. Going on a road trip tomorrow (to the Superbowl) and I want my music on the car radio. fingers crossed for the Bluetooth and the Broncos

 

[BlkDrgn28]

Just disabled the sharing of my contacts on my LG G4 will see if that works for me.. thank you for the idea.. never thought to do that.. don't have an option to stop messages though but I don't think my Kenwood stereo has that ability anyways.. been fighting this with my last Optimus G Pro and got the G4 hoping it would just stop.. no suck luck.. will keep the community updated!!

 

[Robert Burgers]

As has been suggested, this worked for me.
-unpaired the phone from the car
-deleted the connection on both sides
-deny access to my messages
-allow access to contacts and phone log

It drove me mad though, the weird thing was that it used to work fine, even with access to message, so I suspect some sort of update must have caused it.

 

[imamuse]

This is not a Samsung issue it's an Android issue. I have an LG G Flex with the same problem - it's in the Android OS itself - I've found out that the bluetooth searches and stores all the Bluetooth signals it comes into contact with while it is on no matter what - whether you tell it to search or not. The problem lies in the code not telling the system to dump the files so it keeps storing them with no way to get rid of them (that is until Google finally fixes the huge problem!) The only way to clear the files is to factory reset or there is an app on google play by Radius called BLE Crash Fix - but it hasn't worked yet on my phone but it says over time it's supposed - why it can't fix it as soon as it's installed I'm not sure but other people seem to be having a little luck.

you can try either. I'm at my wits end with this issue!

 

[imamuse]

Bluetooth Stopped working GOOGLE Fix the BLUETOOTH ISSUE NOW!!!!!!!!!

I have an LG G FLEX and clearing the Cache Data didn't work on my phone - it still has the issue - which is getting to be a Royal Pain in the you-know-what! I can't connect to my bluetooth speakers WTHeck!

It's not a 3rd party app issue it's the Android OS - it's a growing issue!

I"m about ready to quit Android and go to Apple or Microsoft! I never had this problem before so why now????

Oh and by the way it's not an Android 5.0 issue as I'm running Android 4.4.2 / and I'm not pairing my phone to my car at all as my car isn't even capable of that.

It's now Dread instead of Droid.....

 

[imamuse]

My LG Flex is just having issues connection to any bluetooth device

It keeps connecting and reconnecting to my bluetooth headset and I'm less than 3 ft. away from the darn thing and it now happens so frequently that I've stopped wearing my headset all together which is more dangerous in the car. Not that I answer my phone but I need to see who is calling because I'm on-call.

GOOGLE GET YOUR ACT TOGETHER!

 

[M Skak]

This is not a Samsung issue it's an Android issue. I have an LG G Flex with the same problem - it's in the Android OS itself - I've found out that the bluetooth searches and stores all the Bluetooth signals it comes into contact with while it is on no matter what - whether you tell it to search or not. The problem lies in the code not telling the system to dump the files so it keeps storing them with no way to get rid of them (that is until Google finally fixes the huge problem!) The only way to clear the files is to factory reset or there is an app on google play by Radius called BLE Crash Fix - but it hasn't worked yet on my phone but it says over time it's supposed - why it can't fix it as soon as it's installed I'm not sure but other people seem to be having a little luck.

you can try either. I'm at my wits end with this issue!

Hi Imamuse,

Thank you for your information, it was very interesting. Most of us don't have your ability to dig into the code, so it was really nice to hear from someone who has actually taken the time to study what happens.

Your explanation sounds very plausible, but how can you explain that my phone kept connecting and re-connecting, even after a factory reset? That should have cleared the log, as I read your post? The only thing that has worked perfectly for me ever since I started having this problem is denying access to messages.

Thanks for contributing!

 

[M Skak]

Just disabled the sharing of my contacts on my LG G4 will see if that works for me.. thank you for the idea.. never thought to do that.. don't have an option to stop messages though but I don't think my Kenwood stereo has that ability anyways.. been fighting this with my last Optimus G Pro and got the G4 hoping it would just stop.. no suck luck.. will keep the community updated!!

Hi Blkdrgn28,

It will be interesting to hear if you can solve the problem by just disabling access to contacts! Keep us posted, please!

 

[awkwardlyinsinc]

My tablet keeps saying " unfortunately Bluetooth has stopped " right after the logo screen comes on and it wont let me do anything. It won't even let me turn off my tablet

 

[lucianus_luciferus]

this is the s6 forum... you might want to post in your specific device forum. you will get better support

 

[HBzz]

i've been using LG Magna with android lollipop for a year now and got a notification last night about an android os upgrade. i downloaded it and got android marshmallow 6.0. everything was working just fine but today when i turned on my bluetooth (to transfer some files), it didnt turn on. instead it showed an error message saying: "unfortunately bluetooth has stopped"
i went to app manager, tapped on "Bluetooth" (having the blue bluetooth icon), cleared cache and cleared data. did the same with another app "Bluetooth" (having the settings icon) and an app "Bluetooth MIDI Service". then i tried to turn on bluetooth but same problem occured. then i restarted my phone. when it booted and i unlocked it, the same error message appeared "unfortunately bluetooth has stopped" (even though i hadnt even tried to turn on bluetooth yet). i still tried to turn on bluetooth and of course the same error message appeared. i've never had this problem before the upgrade so im pretty sure that the problem lies with the upgrade.
i also went to 'app manager - menu - configure apps - ignore optimisations' cuz i had a feeling that maybe the battery saving feature of marshmallow must have something to do with the problem so i checked the three apps i mentioned before ("Bluetooth" "Bluetooth" and "Bluetooth MIDI Service"). still didnt solve my problem :'(
the only solution left in my mind is to factory reset my phone but i really dont want to go through all the hassle after doing so especially if theres a possibility that my problem wont even be fixed by resetting. please help.

sorry for the long post. way too lazy to post a potato

 

[Brett Anderson]

Old man here with my first reply to the tech world smart folks. Same as you this was Fricken driving me nuts, started happening to my Note 4 not long after a platform upgrade. My fix ended up being simple. . .

In the Bluetooth menu simply set the "visibility timeout" to NEVER. I haven't had a problem sense.

 

[Tameikarose]

I tried that and it worked for a little while now it's back. literally once I clear the cache or data before I can close app manager the cache was back full

 

[nhannon9]

I believe there are two main Bluetooth issues that people are facing. Here are the solutions which worked for me:

1.) "Unfortunately, Bluetooth has stopped."

This is an issue that affects Android 4.3 and 4.4. If your device does not support a newer update, check out the solutions listed here: [Bug Watch] Bluetooth Will Begin Crashing After Encountering Too Many BLE Devices, Affects KitKat 4.4 And Jelly Bean 4.3

BLE Crash Resolver did not work for me (LG G Flex). I had luck with the solution that requires root!

--

2.) "Unfortunately, Bluetooth Share has stopped."

This is a different issue than the one above, and involves the sharing of some data via Bluetooth with devices, commonly cars. The solution I found for this is to tap on the gear next to my car in Bluetooth devices, and disable messages/contacts from syncing.

As others have said, you can still receive calls, but with no name tied to the number.

It appears 4.3/4.4 are versions of Android that suffer from severe Bluetooth issues.

 

[Momchi]

i've been using LG Magna with android lollipop for a year now and got a notification last night about an android os upgrade. i downloaded it and got android marshmallow 6.0. everything was working just fine but today when i turned on my bluetooth (to transfer some files), it didnt turn on. instead it showed an error message saying: "unfortunately bluetooth has stopped"
i went to app manager, tapped on "Bluetooth" (having the blue bluetooth icon), cleared cache and cleared data. did the same with another app "Bluetooth" (having the settings icon) and an app "Bluetooth MIDI Service". then i tried to turn on bluetooth but same problem occured. then i restarted my phone. when it booted and i unlocked it, the same error message appeared "unfortunately bluetooth has stopped" (even though i hadnt even tried to turn on bluetooth yet). i still tried to turn on bluetooth and of course the same error message appeared. i've never had this problem before the upgrade so im pretty sure that the problem lies with the upgrade.
i also went to 'app manager - menu - configure apps - ignore optimisations' cuz i had a feeling that maybe the battery saving feature of marshmallow must have something to do with the problem so i checked the three apps i mentioned before ("Bluetooth" "Bluetooth" and "Bluetooth MIDI Service"). still didnt solve my problem :'(
the only solution left in my mind is to factory reset my phone but i really dont want to go through all the hassle after doing so especially if theres a possibility that my problem wont even be fixed by resetting. please help.

sorry for the long post. way too lazy to post a potato

This is a VERY OLD AND KNOWN ISSUE, it has nothing to do with your upgrade, marshmallow 6.0. This existed since Android 4.3 and as much as it pains me, I've had it since then. What I have heard so far is that it is in the implementation of the blue tooth modem driver (stack). Google (or the stack providers, which depends on blue tooth hardware) were saying this was going to be addressed, but I see it was not done so far. The *only way I know to "fix" it is with a reset to factory defaults* - that, however, is also temporary, as the list of bluetooth devices trying to pair will grow (again) and eventually fill up!
When and how this will happen depends on how many devices your device encounters, and/or connects to. With ever increasing number of devices around you that use bluetooth, this happens quickly. It does depend on your usage also, but that's the issue- we want to use it more often, not less often! !!

Searching for a correlation or dependence of conditions to troubleshoot this is in vain, sad to say it! Sad to suggest, but find a good NAND backup tool (full memory backup), backup your data, clear device, restore only data (not system), then create a clean backup point that you will have to come back to anytime this happens. ... Because, sadly, I have not found another permanent solution for this yet .... ( searching for 4 years now)