I have been successfully using an S2 sport and then switched to a classic with no problems on either watch. I use a Nexus 6 running AICP, an LP ROM based on Cyanogenmod. Yesterday a totally new problem emerged: After the watch disconnects from Bluetooth and then reconnects it no longer will receive notifications of any kind from the phone. Note that I do not use WiFi connectivity, just Bluetooth. All other communication with the phone like weather or incoming phone notifications still work after a reconnection.
If I light reset the watch and then restore the data I will get all notifications again so everything is set correctly on the phone and the watch. I then tried the following steps to see if I could fix the problem:
Uninstalled/reinstalled all Gear apps from the phone with no change in behavior.
Factory reset the watch with no change in behavior.
Uninstalled/reinstalled all Gear apps from the phone and factory reset the watch with no change in behavior.
Turned the watch off/on with no change.
Went back to the last nightly build of my ROM that I know was working correctly with the same behavior.
I can't think of anything else to do to try and fix the problem, anybody have any other ideas?
I did discover that once the watch stops receiving notifications, I can just restore the data without doing the light reset to reestablish notifications. It will be really annoying once I get back to work because I routinely walk away from my phone and the watch becomes disconnected. Having to restore the phone data in order to receive notifications will be problematic.
Any help will be appreciated.
Thanks,
Fred
Edited in 2015-12-21 - Solved Problem, Very Strange
So it turned out that the problem is that I switched the band to one of the nylon bands that loops under the watch (I like those because they are very light and indestructible). You would think the problem would be charging the watch with one of those bands that goes behind the watch but that was not a problem. However, something about the different stress pattern caused by the band on the watch case caused the watch to not accept notifications. Other communications worked fine and it would work if I reset the watch. When I did all the debugging described above I left the watch on my wrist.
However, just for a lark I took the band off today and everything worked as it should.
The original strap still work perfectly.
Go figure.
Fred
I may have a similar issue on my S2 with AT&T numbersync enabled (paired to a stock S5 active) where notifications stop appearing on the watch for apparently no reason. I have the sport watch with the stock band though. I've done a light reset twice so far. It might be related to the bluetooth reconnecting. I'll have to try it out a few times to see. Thanks for the info on doing restore data to get notifications working again. Much better than a light reset.
Related
Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.
ruggs1234 said:
Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have the same phone and watch combo and mine connects back up again without any problems. Is your S3 rooted and if so, with which ROM? I am guessing your watch is on the latest firmware.
I am using a 4.1.2 ROM called BoneStock, but will flash one of the new 4.3 ROMs (now leaning towards MOAR TW 4.3).
ruggs1234 said:
Ive had my Smartwatch 2 for 3 months and it and my Samsung Galaxy S3 are running up to date software on Smart Connect and Smartwatch 2.
The problem I have is that because of the shape of my house (long and thin) when i'm at home my watch will often lose its bluetooth link with the phone and simply reconnect when I come back in to range. At least it does MOST of the time.
But randomly I get the message "Pairing with device will clear data from previously paired device". It then requires a reset on the watch and unpairing the watch and repairing on the phone.
There seems to be no logic to these "lock-ups". Sometimes I can go in and out of range once and it locks...sometimes I get no lock-ups all day. Sometimes i'm out of range for a few seconds, sometimes minutes. It seems as though something prevents the automatic repairing on some occassions and not others. And sometimes you have no idea the watch has failed to repair because that message sometimes also fails to appear.
Everything else about the watch I like...but this is driving me nuts.
Are there any rules to how the watch handles bluetooth. As nobody else on here seems to have mentioned this maybe its something i'm doing wrong.
Any advice would be appreciated.
Click to expand...
Click to collapse
I have a different phone, htc one sv on stock Rom and I have never experienced the issue you described. Always reconnects without an issue.
Sent from my HTC One SV using Tapatalk
Thankyou very much for your replies.
I am now more confused as it does seem there is some sort of problem with my set-up between the watch and my Samsung S3.
The firmware on the watch is up to date as is the Smart Connect app and the Smartwatch 2 app.
My S3 is running stock 4.1.2 (and not rooted) and I have no desire to update it with all the problems that might bring.
It doesn't seem as though there are any further settings on the watch I could try adjusting. There doesn't seem to be any further Bluetooth settings on my S3 but I would love to be corrected if i'm wrong.
Any ideas?
I have an S4 and mine has locked up and refused to reconnect again. the first few times i had to reset the watch to get it going again but i figured out how to fix it without having to reset.
if they are refusing to reconnect i just goto my phone and unpair the watch, then do a scan for bluetooth devices and it should find the watch ... pair and everything should be fine. no resets or uninstalls needed.
Danny-B- said:
I have an S4 and mine has locked up and refused to reconnect again. the first few times i had to reset the watch to get it going again but i figured out how to fix it without having to reset.
if they are refusing to reconnect i just goto my phone and unpair the watch, then do a scan for bluetooth devices and it should find the watch ... pair and everything should be fine. no resets or uninstalls needed.
Click to expand...
Click to collapse
Thankyou for the suggestion. This will make the re-pairing process a little simpler and I will try it.
But I am hoping to work out why the phone and watch sometimes lock up when they they should reconnect automatically.
I go out of range often and lose the connection, it then often won't reconnect. I've found the fastest way to get it to reconnect is to turn the Bluetooth off on the watch and then back on again. As long as the smart connect app is running on the phone it will then reconnect, most of the time. This is using an s3 and omnirom.
Sent from my GT-I9300 using Tapatalk
I use a HTC One (4.3) and I´ve never experienced this problem.
My Gear S2 has recently started disconnecting, then reconnecting a few seconds later. The S2 and my phone both vibrate - when I check my mssages, nothing new but the phone says disconnected. I have a stock (non-rooted) Verizon S7 Edge.
Here's what I've done so far:
1. Powered both off and back on - didn't work
2. Reset the watch and app - didn't help
3. Disconnected the watch from my phone and connected it to my son's S7 (verizon) - HAD NO DISCONNECTS
4. Did a factory reset on both the phone and the watch and reinstalled to my S7 edge....disconnects resumed.
My next logical assumption would be since it happens on mine but not his phone, it must be my phone. But it never disconnects from my Ford Sync or my BT radio.
Anyone had this issue - or better yet, figured out this issue?
No one else has this issue?
I am in the Nougat beta for s7 and have had this happen frequently. They have said to wait for the final update and see if it's fixed then. It did not happen as often to me as you are describing
Same here, but I suspect more my S7E to be the issue since it happened also with my Pebble Time.
(also posted in another thread on disconnects) After working with three different S7's (2 edge's and one regular) as well as a Droid Maxx, I found that the phones would regularly disconnect when I had High Accuracy GPS set to on (with disconnects occurring multiple times per hour). If I switched the phones to power-saving GPS, disconnects would never occur.
Not sure why this would be but I don't recall it happening before the latest S2 update. I have always used High Accuracy GPS because I use the Tile app which requires it....HOWEVER, the disconnects were SO irritating, I guess I'd rather lose my keys and/or wallet because I turned the GPS to power saving to eliminate the disconnects because it was SOOOOO annoying.
Hey guys, I'm currently in possession of two Gear S3 watches (one European and one U.S.) and two different phones (GS7 and Pixel, both 5 in versions). I am having a horrendous time trying to get a stable connection between my watch and the phones via bluetooth. I basically can't use the watch because of how frequently it disconnects from my phone.
On my GS7, the watch would not hold a BT connection long enough out of the box to be set up properly for about an hour. It would always disconnect during setup and kick me back to the beginning. Ultimately I lucked out and managed to get it to set up after trying over and over by resetting, clearing data/cache, reinstalling app, etc. Used it for the last week or so and I definitely had a number of random BT disconnects but overall it seemed to get the job done without being too much of a distraction.
Now I have a pixel I'm trying to set up with and it's been a nightmare. I just can't get the watch to connect long enough to the pixel software to actually get going. The same message always pops up about the connection failing. "Please try again." When I look at the watch, I notice that the watch's BT radio is actually what appears to be fluctuating. It will frequently turn itself on and off in a matter of seconds. After enough connects/disconnects, the watch remains in standalone mode and manually toggling BT will not enable it anymore. A reset temporarily solves the toggle issue but not the frequent disconnect issue. I've disabled battery optimizations on the Samsung software and plugins but again the watch seems to be the bigger culprit. I can still pair to my GS7 albeit now with more frequent disconnects though not as bad as the pixel. I've tried factory resetting a bazillion times and also re flashed the software images through net odin from these forums. Nothing seems to solve this issue.
The European model was having similar quality connection with my pixel but I haven't tried it with the S7 yet. Is anyone else having these major BT issues with this watch or did I just get a few stinkers? Thanks!
I've had my watch about a month now and I've had zero Bluetooth problems.
Sent from my SM-T530NU using Tapatalk
zero.... mate 9
Guess it's time for an exchange then. Thanks!
A Friend of mine had the same issue. It seems hardware related. He exchanged it for a new one. Problem solved.
Verstuurd vanaf mijn SM-G930F met Tapatalk
Sounds like a problem with your watch. Are your phones rooted or modded in any ways? My friend was having that issue and realized it's because he was closing the Gear app instead of leaving it open in the background (non Samsung phone)...
I have a similar problem but is the phone's fault. When too many apps are open, the bluetooth disconnects and then reconnects (resets?). My device has only 2Gb of RAM, I think it's closing apps to free up memory because when I'm not using the device it never disconnects, but as soon as I'm playing a game or using a Navigation app, it disconnects randomly.
Check if this is your case. How many apps have you installed/running in the background? I've disabled a lot of apps that start on boot.
Also when pairing it for the first time I couldn't do it on a certain custom ROM (LG phone). Looking at the logcat it was due to some missing libraries. After changing the ROM it paired successfully.
Anyone else? I can't see any other threads about people experiencing bugs with these latest updates.
I'm forever losing connection, calendar notifications come through despite being on my blocked list, it's a bit laggy and google assistant works when it feels like it.
sunking101 said:
Anyone else? I can't see any other threads about people experiencing bugs with these latest updates.
I'm forever losing connection, calendar notifications come through despite being on my blocked list, it's a bit laggy and google assistant works when it feels like it.
Click to expand...
Click to collapse
Mine works without any problem o.o
I've been reading people with lag or buggy screens but at least not in my case.
Model: LEO-DLXX
have you tried:
- turn off Bluetooth
- clean data and cache from wear os (Android wear) app
- Uninstall wear os app
- 'forget' your watch from Bluetooth devices
- restart phone
- factory reset your watch
With this procedure it should be a clean install again. Good luck!
working good here for me
I also got this problem too, I tried factory reset the watch but still no connection:crying:
Same problem here with bluetooth. Connection gets broken at half the distance that I could go with the old OS on it.
And worse, it will not reconnect when i'm close to my phone. I have to shut down the watch and start it again.
it also uses it own GPS for location services and not the one on the phone when connected, so batterylife goes down.
pkaak said:
Same problem here with bluetooth. Connection gets broken at half the distance that I could go with the old OS on it.
And worse, it will not reconnect when i'm close to my phone. I have to shut down the watch and start it again.
it also uses it own GPS for location services and not the one on the phone when connected, so batterylife goes down.
Click to expand...
Click to collapse
I have the very same problem described here.
BT connection breaks down and the watch won't reconnect. Since the update, it's connected to my wifi all the time now when I'm at home, but not to my phone anymore. After a restart of the watch, Bluetooth connection works for a few minutes, but once it loses the connection, it's back to wifi only.
Never had such problems before...
I can confirm the GPS problem as well.
In addition to that, I noticed that every time I restart the watch, it downloads some Google TTS data. Again and again. Strange. (Btw, it says it needs wifi for the download, so maybe this is related?)
i had a problem when mine updated the other month and I had to reset Watch and AW a few times to get it working again. It seems unlike the older versions unless you use the watch for answering calls, it will not show as connected under the phone BT settings, but if go into the Wear app it will say connected.
I'm not sure when last got an update, but last night it never tracked my sleep, so restarted watch today and noticed it is now on March 2018 security update and today i have also received an update on my phone for Wear OS.
A factory reset of the watch, reinstallation of the Wear OS app on my phone and allowing the Wear OS app to override the deep sleep settings on my phone fixed this problem for me.
This is an odd one for me and I've tried a bunch of things to fix this.
My wife works where she can't have her phone out but she is allow a smartwatch. So what she did before was leave her phone in the car or in the break room. when she had her previous phone and watch it worked fine but that was a note10 and active2 but now she has a pixel 6 and a watch4.
Now the issue is that throughout the day the watch stops or doesn't even connect to the mobile network when she gets out of Bluetooth range of her phone even with the connection setting set to always on or auto. And this issue is definitely not constant, it is intermittent but I've tried resetting network settings, I've tried resetting the watch idk how many times, when I spoke with T-Mobile about it, they reset the esim in the watch and and paired it to her line again just refresh it, even went as far as resetting the pixel phone to factory settings once and this issue persists. I'm considering just getting her the watch5 pro but I'd hate for this problem to continue onto that watch too.
What confuses me is that I had a pixel 6 pro and a watch4 and no issues ever.