Hello everyone,
I have a Gear S3 Frontier bluetooth only model, and I noticed that if go outside the bluetooth range (10-15m from the phone) after I come back within the bluetooth range, the watch doesn't reconnect automatically, and I must reconnect it manually from the Gear Manager app.
My phone is a Samsung S6 edge+, and until now I had a Garmin Vivoactive which didn't had this problem.
I found in the Gear S forum a similar problem, and one proposed solution was to unpair it and pair it again.
I tried that and it worked, the watch reconnected automatically 2-3 times, but after 30min-1 hour the problem appeared again.
Does anyone else has this problem ?
Thanks
Septoman said:
Hello everyone,
I have a Gear S3 Frontier bluetooth only model, and I noticed that if go outside the bluetooth range (10-15m from the phone) after I come back within the bluetooth range, the watch doesn't reconnect automatically, and I must reconnect it manually from the Gear Manager app.
My phone is a Samsung S6 edge+, and until now I had a Garmin Vivoactive which didn't had this problem.
I found in the Gear S forum a similar problem, and one proposed solution was to unpair it and pair it again.
I tried that and it worked, the watch reconnected automatically 2-3 times, but after 30min-1 hour the problem appeared again.
Does anyone else has this problem ?
Thanks
Click to expand...
Click to collapse
I did yesterday, all I had to to was turn on airplane mode then turn it back off, reconnected in seconds.
I also had this problem. Since I switched off WLAN, Bluetooth reconnects automatically.
Try this
Septoman said:
Hello everyone,
I have a Gear S3 Frontier bluetooth only model, and I noticed that if go outside the bluetooth range (10-15m from the phone) after I come back within the bluetooth range, the watch doesn't reconnect automatically, and I must reconnect it manually from the Gear Manager app.
My phone is a Samsung S6 edge+, and until now I had a Garmin Vivoactive which didn't had this problem.
I found in the Gear S forum a similar problem, and one proposed solution was to unpair it and pair it again.
I tried that and it worked, the watch reconnected automatically 2-3 times, but after 30min-1 hour the problem appeared again.
Does anyone else has this problem ?
Thanks
Click to expand...
Click to collapse
I had this problem and it was driving me nuts but did a hard reset of my watch and now everything is working ok.
It looks though I had something else competing with my watch and by unpairing the watch, doing a reset and then resetting up my watch, cleared whatever was causing the issue.
I have nearly the same problem with watchmaker App.
When the Bluetooth connection is disconnected because out of range and the BT is reconnected again, the watchmaker has problems to sync with gears s3.
No data like phone battery, etc .. . Also sending watchfaces over BT is not working anymore.
But with other apps (Samsung Gear App), BT is always working great.
To solve the problem, I have to switch off BT on the smartphone and enable again.
After that the sync between watchmaker and Gears S3 is working well again until reconnect.
I have informed the watchmaker developer, but until now, I have gotten no feedback.
Android 6.0.1
Watchmaker App: 4.8.2
Thats a very old version of WatchMaker.
Related
All,
I run into problems with the combination of items mentioned in the subject...
A while ago I bought the Samsung EI-HS10 body scale. This pairs with the Note 3 and sends info via Bluetooth to the Note 3. This was working fine, until I recently got myself a Gear 2.
As far as I noticed so far, is that on the stock 4.4.2 ROM on my Note3, the SensorService picks up the message from the scale and sends this to S Health. After pairing the Gear 2 (which did not go as smooth as expected), the scale indicates sending its data, but the phone does not pick it up anymore. So now and then SensorService even crashes.
When I remove the connection to my Gear 2 (by removing the BT registration in the phone, not by just simply disconnecting the BT signal) and when I then clear the data of S Health and SensorService, the scale data comes back to the phone.
However, when I then try to connect the Gear 2, I need to try to connect it multiple times as it does not connect straight away.
For now, I prefer that my watch works instead of the scale, but I also notice that the BT connection to the watch is still buggy. Sometimes the watch remains connected for days, sometimes it starts disconnecting every couple of minutes. This is mainly very very annoying when I am tracking a bike trip or something, as losing connection ends the exercise. I sometimes even need to reset the watch and pair it again to make it actually work. Luckily the Gear Manager then sees a backup and restores this to the watch, but it is very annoying.
Does anyone else experience the fragile BT connection between Note 3 and Gear 2 (without using the EI-HS10)? Anyone else out there has the same combination of 3 devices working together as it should?
Gerco
gschot said:
All,
I run into problems with the combination of items mentioned in the subject...
A while ago I bought the Samsung EI-HS10 body scale. This pairs with the Note 3 and sends info via Bluetooth to the Note 3. This was working fine, until I recently got myself a Gear 2.
As far as I noticed so far, is that on the stock 4.4.2 ROM on my Note3, the SensorService picks up the message from the scale and sends this to S Health. After pairing the Gear 2 (which did not go as smooth as expected), the scale indicates sending its data, but the phone does not pick it up anymore. So now and then SensorService even crashes.
When I remove the connection to my Gear 2 (by removing the BT registration in the phone, not by just simply disconnecting the BT signal) and when I then clear the data of S Health and SensorService, the scale data comes back to the phone.
However, when I then try to connect the Gear 2, I need to try to connect it multiple times as it does not connect straight away.
For now, I prefer that my watch works instead of the scale, but I also notice that the BT connection to the watch is still buggy. Sometimes the watch remains connected for days, sometimes it starts disconnecting every couple of minutes. This is mainly very very annoying when I am tracking a bike trip or something, as losing connection ends the exercise. I sometimes even need to reset the watch and pair it again to make it actually work. Luckily the Gear Manager then sees a backup and restores this to the watch, but it is very annoying.
Does anyone else experience the fragile BT connection between Note 3 and Gear 2 (without using the EI-HS10)? Anyone else out there has the same combination of 3 devices working together as it should?
Gerco
Click to expand...
Click to collapse
Metal case or defective gear 2? those are my guesses
maybe try deleting the scale and gear 2 bluetooth profiles and start w/ pairing the gear 2 first and see if it works perfect then the scale.
enko420 said:
Metal case or defective gear 2? those are my guesses
maybe try deleting the scale and gear 2 bluetooth profiles and start w/ pairing the gear 2 first and see if it works perfect then the scale.
Click to expand...
Click to collapse
The Gear just has its own case. The problems with Gear are mainly related to connecting to Gear Manager. When connecting through the Bluetooth profiles it always immediately connects phone audio.
I tried removing profiles and connecting the devices back in any possible order, but as soon as I add the Gear, my Note 3 stops receiving the messages from the scale.
Do you have this combination working then?
Gerco
gschot said:
The Gear just has its own case. The problems with Gear are mainly related to connecting to Gear Manager. When connecting through the Bluetooth profiles it always immediately connects phone audio.
I tried removing profiles and connecting the devices back in any possible order, but as soon as I add the Gear, my Note 3 stops receiving the messages from the scale.
Do you have this combination working then?
Gerco
Click to expand...
Click to collapse
Just the gear 2 neo and the note 3, no problems here running 4.4.2
I dont know if this is specific to Android Auto or just my pioneer 4100nex, but it seems when i connect or disconnect the phone to android auto the S2 disconnects and does not reconnect until i go to the screen below and turn it on.
Im trying hard to like this watch, but this is frustrating.
I have the exact same issue!!!
Sent from my SM-N920T using Tapatalk
This does not happen to my Gear S2. I have Android Auto through my 2015 Sonata.
Sent from my SM-G925P using Tapatalk
When using my carkit( 13 Chevy VOLT with MYLINK) I have to turn Bluetooth off on the watch or else I can not connect to my carkit. After it connects I can turn the watch Bluetooth back on and they work fine.
It is like the Gear S2 is taking priority and not allowing me to connect to another Bluetooth device that isn't just A2DP
I do have a Gear S2 3G
I have similar issue Note 4 and Gear S using 4000NEX. when phone detects android auto it kicks my Gear S out. I think it's a safety thing but it does not reconnect even when android auto is complete. The only work around i have set is to have a rule in Automatelt "free app" that will launch gear manager app when the Gear is is disconnected from the Bluetooth. This way it reminds me to reconnect to my watch or else the Gear S stays disconnected. It is annoying, hoping for a better workaround or a fix.
Arghhh just swapped to a Kuga with SYNC 3 and my Gear S3 has the same issue, it just kicks it out and you later realise and manually reconnect.
Reading this the idea for safety makes sense but reading Android forums it should not happen on Google Wear so ...
Sent from my SM-G935F using XDA-Developers mobile app
Same thing. Brand new Chevy Silverado...my link...android auto...gear s2 and samsung note 3. Everytime I get in the truck, android auto disconnects my watch. From my phone, I don't see dates for these posts. (For me 12-26-2016) Hopefully these are recent issues and a fix will show up in an update???
Just adding to the list. Same issue.
I have a Gear S2 classic, Pioneer 4100NEX and Note5. My Gear will usually disconnect with I plug up to the head unit for Android Auto and will not automatically reconnect later. I always have to manually connect to the Gear in the app on the phone.
I have Gear S2 3G, and it disconnects me as well. 2017 Elantra. Only problem is, with the 3G, phone is on, and it tries to forward calls and screws up. So i have missed calls.
Just got a gear s3 frontier and same trouble. Open the android auto app while not connected to your vehicle. Go to settings, check the switch for use bluetooth. Seems to have solved my issue. Not sure why this is defaulted off.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Hi everyone,
Could you guys answer me this: Is the Gear S3 supposed to disconnect the bluetooth connection to my phone every 2 minutes or so? I can't get it to stay connected no matter what i try. I need to reboot my phone everyday because if i don't.. it won't connect at all.
After the reboot everything seems good and i can connect the gear through the Gear app. it only keeps disconnecting every 2 minutes... I've contacted Samsung about this and they told me that the bluetooth version on my phone was insufficient. They suggested i upgraded my phone from an Oneplus one to a Galaxy S8. I bought a Oneplus 5T instead but the problem remains. After i contacted Samsung for a second time they told me that's its probably a hardware related issue. Sounds unlikely to me since rebooting the phone allows me to connect to the watch.
Anyone having the same problem?
anyone?
no problems here, using oneplus 3T (so not the 5T) (On beta OS: A3003_28_180112) and gear s3 frontier on 3.0.1
jbrugger said:
no problems here, using oneplus 3T (so not the 5T) (On beta OS: A3003_28_180112) and gear s3 frontier on 3.0.1
Click to expand...
Click to collapse
Hmm ok. I think it's really weird i need to restart my phone every morning in order to connect to the phone.. Makes no sense
I am experiencing a similar issue with my 5T and Gear S3. Sometimes all the system sound (not multimedia ones though) are being routed to the ear speaker instead of the multimedia speaker. I missed an alarm several times. The fix for me is the same - to toggle BT connection with Gear S3.
I have lockscreen sounds enabled. So, I realize the issue reproduces when the lockscreen sound starts to be very quite and is being emitted via the ear speaker.
Another issue with the Gear S3 I am experiencing is as follows. If I start Google Play Music on my phone, Gear S3 does not see the player is started. Anyway I can start the player from the watch. Also, if I toggle the BT, everything works perfectly. Could you check this on your side as well?
I had a similar situation, the Gear S3 was disconnecting very often. In the end, I found that it was the battery saving settings on my N8 Sirocco that killed the connection to my Gear S3. I turned settings and blacklist off, and now it stays connected.
I have a Galaxy S9+, Gear S3 and a 2018 Jeep with Android Auto. Every time I unplug my S9+ from the car's USB port (which breaks the Android Auto connection) the Bluetooth connection between my phone and watch is dropped. I then have to manually reconnect my phone and watch via the Gear app on my phone. Highly frustrating.
Anyone else have this, or a similar, problem?
pieces of cake said:
I have a Galaxy S9+, Gear S3 and a 2018 Jeep with Android Auto. Every time I unplug my S9+ from the car's USB port (which breaks the Android Auto connection) the Bluetooth connection between my phone and watch is dropped. I then have to manually reconnect my phone and watch via the Gear app on my phone. Highly frustrating.
Anyone else have this, or a similar, problem?
Click to expand...
Click to collapse
Yes mate, having exactly the same issue, got a new Kenwood in car system and now my gear S3 and S9+ looses Bluetooth connectivity every time I get out of the car and have to manually reconnect them each time.... Really annoying!!!
I have a similar issue. I have a S9+ and often when I'm connected to my Sony AA head unit, my phone loses it's connection to my watch. Sometimes this happens immediately after AA launches. Often I will have to reconnect my phone and watch 3-4 times during my 1 hour commute. It also happens sometimes when I'm connected to my Bluetooth headphones.
pieces of cake said:
I have a Galaxy S9+, Gear S3 and a 2018 Jeep with Android Auto. Every time I unplug my S9+ from the car's USB port (which breaks the Android Auto connection) the Bluetooth connection between my phone and watch is dropped. I then have to manually reconnect my phone and watch via the Gear app on my phone. Highly frustrating.
Anyone else have this, or a similar, problem?
Click to expand...
Click to collapse
I think I am having this problem too! I couldn't figure out when it would happen but this makes sense.
Hi,
I hope someone can help me! I have a galaxy Watch 4 and it was paired with my Galaxy S7 phone. Everything worked perfectly. I had to send my watch for repair. Now it's back and my phone absolutely doesn't recognize the watch at all. The watch is not in the bluetooth device list. I cannot pair the watch with my phone.
I tried pairing the watch with another device to see if the watch was the problem. I was able to pair the watch with another android phone (galaxy A5). So the watch is not the problem. It seems that the problems lies within my galaxy S7 phone.
I tried rebooting both the watch and the phone. Didn't do anything.
I tried uninstalling and reinstalling the WEARABLE app. Didn't do anything. (the wearable app can't find the watch either).
I tried erasing cache memory of WEARABLE app. Didn't help.
I unpaired every bluetooth device from my phone, then tried to find the watch to pair, but the phone doesn't see the watch. Note that the phone can recognize and pair with every other devices: earbuds, car, speaker,etc.
I tried to find my phone from my watch bluetooth menu, but the watch doesn't see the phone.
I hope I explained the problem clearly. Does anyone have a solution to suggest? I hope so, because without being paired to my phone, my watch is basically useless...
Thanks!