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.

Solved: Bluetooth disconnects once...no matter what the rom...

I have a really weird problem.
No matter what ROM I'm using, when I first turn my bluetooth on and connect with any device after about a minute or two the bluetooth turns itself off and if I manually turn it back on.
It's still connected to the device it was connected to and when I turn it back in it works fine but it will do this once each time I connect to any bluetooth device.
Can someone help?
I had downloaded the "auto off unpaired bluetooth" tasker profile and it had an error in it.
I've downloaded a "fixed" version and hopefully this will fix it. In any event, the phone is fine, but the tasker profile was defective.

I use bluetoothkeepalive from the Google play store. It holds the connection all the time, but I still have issues when I disconnect from my car and then reconnect again the next time..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

[Q] Does not auto reconnect anymore

So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.

Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk

droidkevlar said:
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Click to expand...
Click to collapse
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.

I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?

kpjimmy said:
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
JayRyu said:
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
euroclie said:
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
Click to expand...
Click to collapse
Thought this too, but it just happened out of the blue. It wasnt right after the update.
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.

So just tested and it still takes a long time to reconnect. Next step will be wiping watch completely and seeing if it resolves the issue. Will try this over the next few days when I get some free time to really mess with it.

My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.

fwayfarer said:
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
Click to expand...
Click to collapse
Good to hear I am not the only one. Which phone do you have? Mine does reconnect, but takes 1-3mins. Im not using a stop watch, just looking at clock and watching the time before it reconnects.

Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.

fwayfarer said:
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
Click to expand...
Click to collapse
OK, Im on LG G3 Verizon rooted. Its just weird that either I didnt notice it after the update, or it happened shortly after the update. Either way, batt life has been a lot better, I just wanted to make sure something I did didnt screw it up.
And let us know about your test for the disconnect.

droidkevlar said:
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
Click to expand...
Click to collapse
FWIW I don't have Xposed installed (but a custom ROM on a i9502 Dual-SIM Samsung Galaxy S4, which might contain some Xposed stuff even though it's unlikeley).
I didn't notice the same reconnect delay today, so maybe this isn't a permanent phenomenon...

I have same issue with reconnecting after walking away. I have a Galaxy S5.

Walked upstairs and watch disconnected, got alert. Came back down and put phone in my pocket. Took three minutes to reconnect.

Bluetooth reconnect takes ages
Same issue with my 360. I have a xperia z2 and its taking a good 2-3 mins to recconect. Such a pain as this is really important to me and work.
Any ideas on if its a downloaded app or not?

Everyone's timeout is looking about equal. It was probably put in for battery savings.

Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed

fwayfarer said:
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Click to expand...
Click to collapse
robber said:
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
Click to expand...
Click to collapse
Yep. Just wanted to make sure as it seemed to happen not right after the update. Thanks everyone.

[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....

Bluetooth reconnection issues with Nexus 6

Sometimes when my Smartwatch 3 loses the Bluetooth connection to my phone, reconnecting takes minutes or doesn't work at all unless I'm disconnecting and connecting it manually in the Android Wear app.
Moreover, when Cloud syncing is deactivated, it just won't connect via Bluetooth at all.
I'm using the latest version of Android Wear, Play Services and CM12.1 on my Nexus 6. Is this a common issue? Is it normal to take several minutes for the devices to pair again?
Gesendet von meinem Nexus 6 mit Tapatalk

I have had similar problems which turning bluetooth on/off helps. This normally coincides with a battery drain but doesnt happen often. You can always try a factory reset of the watch

I have had the watch for only two days - just bought one from the $99 sale at Verizon. During these two days, there have been at least four times where it would randomly disconnect from my stock Nexus 6 (6.0.1) and will not reconnect. The Nexus 6 shows up under Bluetooth devices, but when I click on the connect button, it will not reconnect. I have turned Bluetooth off and on the phone, and still will not connect. I have had to go in and remove the device and set it up each time to get it connected again. Any help in getting this resolved would be appreciated.