My previous phone Mate RS connects with the Samsung S3 perfectly and stays connected all the time. Every since I have switched to my Mate 20x (China Version 256gb), it wouldn't stay connected. I have to manually connect it from time to time. Anyone have the same problem?
jf1972 said:
My previous phone Mate RS connects with the Samsung S3 perfectly and stays connected all the time. Every since I have switched to my Mate 20x (China Version 256gb), it wouldn't stay connected. I have to manually connect it from time to time. Anyone have the same problem?
Click to expand...
Click to collapse
Can't use the trash can on the button in the bottom right it will auto disconnect. You also need to go and turn off battery optimization for all the gear stuff and it will stay connected but my gear's battery life is terrible these days.
I'm having the same issue
I don't know if you're seeing the same but for me the last update has fixed most things, my gear set now syncs and stays connected
Don't kill the gear app from memory and the watch will stay connected. Also disable power management for gear app.
Related
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.
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....
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Mine disconnects if I go over 50ft from my phone but quickly re-connects when I get back in range. I love the watch!
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
Yes, I have the same problem and it's very annoying. Every time I flash a new rom or update a rom(Vanir LP) to my phone(LG G3), I have the hardest time getting it to reconnect. I always have to reset the watch to get it to connect again.
Mine worked, connected and reconnected flawlessly and quickly the first five days that I owned it. However the last few days, it's disconnected when I wake up and I have a hard time reconnecting. Now the watch says that it's connected to the phone, but the phone (Android Wear App) can't see the watch. Very weird. I've reset the watch three times. I've un-paired and re-paired the devices in bluetooth. I've cleared cache and cleared stored data and uninstalled Android Wear App, then re-installed it. The Android Wear App just can't find the watch anymore, but the the Watch still shows it's connected. This is maddening.
mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
FWIW, I don't have any problem with my ZenWatch and Nexus 4. I've had the watch for a few weeks now, and no connection problems with it. I do notice that it doesn't maintain the connection for as large a distance as my old Sony Smartwatch did, but it doesn't have any problem reconnecting. I figure the distance issue is because of the use of Bluetooth v4 instead of v3 with the Sony.
Disconnection to Apple Iphone 5
I have the same problem. Does not reconnect. I've tried everything. The only way to reconnect is to unpair the watch which resets the watch to factory default and establish a new connection to the watch.
After software update cannot answer calls etc.
Functionality wise not very good especially to iphone.
Good looking watch though.
Ok just got the Gear 2 Neo 3 days ago and the setup of the Gear 2 went well. But now every time I move out of range of my phone Gear Manager will not auto-reconnect. The bluetooth will for about 30 sec, then disconnects completely. I had the Gear Fit and NEVER had these issues. I have restarted, reinstalled, and did factory resets on my Gear 2 Neo 3 times so far.
I am running the Galaxy Note 4 running Lollipop 5.0.1 and Gear Manager ver. 2.2.15022599.
cashdude1971 said:
Ok just got the Gear 2 Neo 3 days ago and the setup of the Gear 2 went well. But now every time I move out of range of my phone Gear Manager will not auto-reconnect. The bluetooth will for about 30 sec, then disconnects completely. I had the Gear Fit and NEVER had these issues. I have restarted, reinstalled, and did factory resets on my Gear 2 Neo 3 times so far.
I am running the Galaxy Note 4 running Lollipop 5.0.1 and Gear Manager ver. 2.2.15022599.
Click to expand...
Click to collapse
Mine does this at times lately but only on lollipop, so I just open gear manager disconnect and reconnect my gear, that fixes it for me
thanitos said:
Mine does this at times lately but only on lollipop, so I just open gear manager disconnect and reconnect my gear, that fixes it for me
Click to expand...
Click to collapse
When you say you disconnect then reconnect...what do you exactly mean? I cannot reconnect after coming back in range of the phone.
Thanks.
cashdude1971 said:
When you say you disconnect then reconnect...what do you exactly mean? I cannot reconnect after coming back in range of the phone.
Thanks.
Click to expand...
Click to collapse
For me, in the gear manager app, I can touch the device name then hit disconnect and the reconnect, the way mine messes up is it just constantly says connected when it's not but in the gear app you can just reconnect it there usually
I have had my neo since it came out, the issue was there on my Note 3 KK some, strange thing is I had this issue some on Note4 KK after the first KK update , but none on L. Mine connects every time now. Only think I noticed on all KK versions was it messed up after just upgrading, not factory resetting. When I updated to L, i factory wiped, odin L, factory wiped again, updated OC4 from server, wiped again, then set everything up.
UPDATE: It is now working correctly. When I move away from the phone while wearing my Gear 2 Neo then come back closer to my phone, it reconnects with no issues! I did no changes to my phone or watch. Strange!!!
UPDATE: Stopped working again!!
I have a Samsung Tablet (android 7.0) four CCAs, all on good 5ghz wifi. Ever since the tablet was upgraded to 7.0, it's had an issue where, about half the time, once I select a device to cast to from Spotify/Pandora (either one), it disconnects the WiFi on the tablet. It will physically turn the wifi off, and it will come back on after about 20 seconds. After then it will work for a bit.
I have a LG G5 that has never had this issue. It also is running 7.0.
Could someone shed some light on what is happening when I attempt to cast? Why could it disconnect my tablet WiFi? The wifi comes from a RT-N66U, of which I've tried both old and new firmwares, but it made no difference. I've also done two factory resets on the tablet and turned off battery optimization on Spotify, pandora, and the Home app. Not sure what else to do. Finally, I've also done factory resets on all CCAs. Any input is appreciated. Thanks.