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....
Related
I just got my Sprint GN a few weeks ago, and love using the bluetooth to connect to my car audio, but every 3rd or 4th time I get into my car I notice the bluetooth doesn't pair, so I take out my phone and look and the bluetooth icon is gray (instead of blue, indicating it has connected), I toggle the bluetooth off, and then when I try to turn the bluetooth radio back on it just sits there saying "bluetooth is turning on...". Bluetooth stops working until I reboot my phone
Does anyone have any incites into this or anyone else experiencing this?
I have the same issue. It's no solution but you can enable/disable Flightmode to get Bluetooth up and running again (but quicker then reboot).
Sent from my Galaxy Nexus using Tapatalk 2
I'll give that a try (again) next time.. I am 100% certain I had tried that, though, unfortunately.
Yeah, I tried your solution again, and it just keeps saying "bluetooth is turning on..." even after I've turned *on* airplane mode.
Need some more information to be able to help you properly >_>
Stock ROM or Custom?
Rooted/Unrooted?
Or alternatively (Because it sounds like you're running a stock Galaxy Nexus...) ave you tried unpairing, and the repairing the devices?
Hi Zach,
Completely stock & unrooted (so far)
I actually did a complete factory reset a couple days ago, and the problem has yet to resurface, so I'm crossing my fingers and hoping it's gone, but the issue was intermittent so there is no way to be completely sure it won't show up again.
If it does, I'll try your suggestion, thanks
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:
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
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.
Hey guys. My watch keeps constantly disconnecting and connecting all day long. I've tried everything and still no luck. Is it a bug with the latest android wear update do you think? The app even sort of freezes when I open it sometimes where it doesn't display the watch I'm connected to and you can't do anything. Thanks for your help.
It seems to happen each time there is a notification. Ill do a test text to myself and when it comes through on my phone, instead of receiving it on my watch it starts the whole disconnect / connect process and by the time it finally connects, the notification is missed.
Thanks for your help.
Ryan.
I also have this issue. Then I reset the watch and everything runs fine for a few weeks. But then it suddenly acts up really badly. I've just done a reset after a complete malfunction, where it wouldn't even connect anymore.
EDIT: I contacted Huawei regarding this issue and they offered a waranty case as they suspect a defective BT unit.
I'm doubting. Especially if I would get a red-glow unit after a replacement, it would really be bad.