Develop Bugs

Bluetooth issues.

I was wondering if anybody has any issues with bluetooth not been able to reconnect or just not sending sound to the bluetooth device, sometimes on mine I have to reboot the phone cause the BT doesn't turn off....

Here and there
Sent from my SGH-T989 using Tapatalk

off and on... am running digital warfare at the moment... have been wondering if it's something with his kernel as I didn't have this issue with juggernaut 4.1
Using tapatalk on my Galaxy 2 to post this!

me too.
using stock rom.

...I c....I'm running Telus stock, so it seems like is a normal known issue....

Happens to me once in a great while on cm7.
Sent from the neitherworld >:}

Yep, constantly
Sent from my SGH-T989 using xda premium

So I am not the only one this is happening to.
I have the Telus variant of this phone, stock. Talking to their tech support, they would have you believe that this is only happening to you.
When phone is first turned on, bluetooth works fine for trip into work. I turn bluetooth off when I get to work and leave the phone on for the day.
I turn bluetooth back on when leaving work and it is intermittent weather it will connect or not. If you go to the bluetooth screen and tap to turn on bluetooth, it shows "turning on..." but does not turn on, no check mark in the check box. After about 30 seconds it stops trying.
At other times it shows it is on and connected to my speaker-phone. When I get an incoming call, the phone will ring instead of the speaker-phone. If you try to answer using the phone you get nothing because it is connected to the speaker-phone but not transmitting.
I am on my 3rd bluetooth speaker-phone, 2 blueant S4's and a Jabra freeway. I have had connection issues with all devices.
I have sent my phone into Telus repair twice and they did a factory flash the first time. The second time I was given a refurbished S2X. The problem is still there even on the replacement device.
The connection issues don't seem to have any consistency factors, ie after running a certain app and it is hard to recreate for Telus staff at store when trying to show the problem.
Lately if you try multiple times to turn on bluetooth when the connection issue is happening, the phone will lock up and turn itself off. At this point I have to remove and re-install the battery or the phone won't turn on.
We have a hands free driving law in Ontario so I need bluetooth to work.
I hope Telus and Samsung can get their heads together to sort this out. I am really starting to get frustrated with this problem.

[Q] Bluetooth Won't Turn On

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:

Bluetooth Turning On issue

My phone continues to have an issue turning on Bluetooth after a power down/power up cycle or Reboot. It hasn't always been this way, say just the last 3 or 4 months. I'm now running the PartyBoy 4.0.4 ROM and still have this issue. After a new boot, I'll try to turn on Bluetooth from the Settings menu or from the tool bar, but it will just get stuck at "Turning on Bluetooth" message. Sometimes multiple reboots works, but I usually have to do a battery pull, and then it finally comes on. Now, once it turns on, I'm good to go. I can toggle it off, then on over and over and it starts up in just a second or two - until then next new ROM I install or a power cycle... So my Bluetooth works just fine, but only once I can get it enabled. Anybody else? Thanks.

daggerNC said:
My phone continues to have an issue turning on Bluetooth after a power down/power up cycle or Reboot. It hasn't always been this way, say just the last 3 or 4 months. I'm now running the PartyBoy 4.0.4 ROM and still have this issue. After a new boot, I'll try to turn on Bluetooth from the Settings menu or from the tool bar, but it will just get stuck at "Turning on Bluetooth" message. Sometimes multiple reboots works, but I usually have to do a battery pull, and then it finally comes on. Now, once it turns on, I'm good to go. I can toggle it off, then on over and over and it starts up in just a second or two - until then next new ROM I install or a power cycle... So my Bluetooth works just fine, but only once I can get it enabled. Anybody else? Thanks.
Click to expand...
Click to collapse
Bluetooth is very buggy and tempermental (and will make you go mental). I've flashed all sorts of roms until I was blue to try to solve my BT problems.
Try ODIN back to a stock rom and test.
Now, I'm on CM 10.1 nightly and BT is working great. CM 10.1 battery is pretty good now since February 22nd.

wave_sailor said:
Bluetooth is very buggy and tempermental (and will make you go mental). I've flashed all sorts of roms until I was blue to try to solve my BT problems.
Try ODIN back to a stock rom and test.
Now, I'm on CM 10.1 nightly and BT is working great. CM 10.1 battery is pretty good now since February 22nd.
Click to expand...
Click to collapse
Thanks wave, not glad that you also have experienced BT issues and on multiple ROMs - just good to know that it isn't just my device. I've been thinking of going back to a fresh ODIN stock image and starting there. Maybe I should dip my toes back into the CM based ROMs again if you're getting good stability. Cheers.

fixed it by runnig fix permissions from cwm, but lost sound on all voip applications like skype and viber after that.

Resurrecting this thread due to continued Bluetooth issues to see if there is anything "new" that's been discovered but I haven't seen in my searches. I'd say that 8 or 9 times out of 10 restarts, my Bluetooth will not turn on. I've restored to stock, and have tried many different ROMs, but I'm just running 4.1.2 based ROMs now so I can keep WiFi calling on my GS-II. Not this is not an issue of dropping bluetooth connections, but rather just turning it on. I usually have to remove the battery (hard reset) to get it to work, and then it works flawlessly until my next reboot. If anyone has anything new for me to try, it will be much appreciated. Thanks.

[Q] Bluetooth connection request????

A few days ago my S3 developed the most annoying problem. Every time I turn on a bluetooth device I get a notification that says "Bluetooth connection request." Then I have to pull down the notifications, click on the notification and approve the connection. And if I don't do this all within about ten seconds the opportunity to connect disappears and I have to power cycle my BT device.
This is with a paired device that is in the list of known devices, and it has happened with multiple devices.
I've had my S3 for nearly a year and I've never seen this before. And I've never seen it with any previous Android phone. Usually if I turn on a paired device it automatically connects. I have not done anything to my knowledge that would cause this. I am rooted and running completely stock 4.1, I have not upgraded to 4.3 although I'm tempted to upgrade now in hopes that it will clear this up. It is very annoying.
I have searched XDA and Google for a solution to this and there's really nothing out there. What is going on? Please help.
TIA

[Q] Watch continues to disconnect?

Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?

Noticed the same with my 360 and Nexus 5. Both on stock latest versions.

Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.

I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?

I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.

Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.

Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.

this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.

Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.

I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....