Samsung Gear Sport full discharge overnight

Forums › Gadgets, robotics, home automation, electronics (including wearables) › Samsung Gear Sport full discharge overnight

MikeB4

13373 posts

Uber Geek
+1 received by user: 6286

Trusted

Subscriber

Topic # 242260 18-Oct-2018 09:24

I have a Samsung Gear Sport watch which is approx 6 months old. In the last week it has started to discharge overnight. Normally I could get 2.5 days use between charges. Last night it was on 87% after being fully charged in the morning, this morning when I woke the watch was powered off and when I started the battery was at 0%. The watch was working fine over the weekend.

I have deleted any new Apps etc which was only two new watch faces. This morning I have done a full reset of the watch and declined updates to see how that goes. Are there any Samsung Sport users here and are you experiencing similar issues.

Mike
Retired IT Manager.
The views stated in my posts are my personal views and not that of any other organisation.

Mac user, Windows curser, Chrome OS desired.

The great divide is the lies from both sides.

tripp

3100 posts

Uber Geek
+1 received by user: 783

Trusted

Lifetime subscriber

Reply # 2110283 18-Oct-2018 09:36

In the gear app on your phone you will see an area to look at battery usage, if you notice it doing it again have a look there. I have had that happen on a gear device before and it was a endless sync by samsung health that was doing it, i killed it on both the phone and gear device and it was fine after that.

Blurtie

195 posts

Master Geek
+1 received by user: 43

Reply # 2110284 18-Oct-2018 09:36

I've got the Gear S3 Frontier and was getting the same battery drain issues as you.

I rebooted the watch and it seems to have fixed it for now...

MikeB4

13373 posts

Uber Geek
+1 received by user: 6286

Trusted

Subscriber

Reply # 2110289 18-Oct-2018 09:45

tripp:

In the gear app on your phone you will see an area to look at battery usage, if you notice it doing it again have a look there. I have had that happen on a gear device before and it was a endless sync by samsung health that was doing it, i killed it on both the phone and gear device and it was fine after that.

The problem is when it has been fully discharged I dont get the opportunity to check the usage and when it goes on charge it resets the usage stats. Frustrating. I will turn off sleep monitoring tonight to see what affect that has.

Mike
Retired IT Manager.
The views stated in my posts are my personal views and not that of any other organisation.

Mac user, Windows curser, Chrome OS desired.

The great divide is the lies from both sides.

MikeB4

13373 posts

Uber Geek
+1 received by user: 6286

Trusted

Subscriber

Reply # 2110765 19-Oct-2018 08:28

After reading through these pages here it would appear I am not alone. It also appears I am in the hands of Samsung, I wont hold my breath.

https://eu.community.samsung.com/t5/Smartphones-Tablets-Wearables/Gear-sport-Battery-draining-at-night/td-p/715037/page/19

Mike
Retired IT Manager.
The views stated in my posts are my personal views and not that of any other organisation.

Mac user, Windows curser, Chrome OS desired.

The great divide is the lies from both sides.

MikeB4

13373 posts

Uber Geek
+1 received by user: 6286

Trusted

Subscriber

Reply # 2111730 21-Oct-2018 07:31

I disabled diagnosis and reporting on the watch and battery usage has returned to normal. I had turned this off when I originally set up the watch. The recent update must have reactivated it and there is clearly a bug.

Mike
Retired IT Manager.
The views stated in my posts are my personal views and not that of any other organisation.

Mac user, Windows curser, Chrome OS desired.

The great divide is the lies from both sides.

tripp

3100 posts

Uber Geek
+1 received by user: 783

Trusted

Lifetime subscriber

Reply # 2111754 21-Oct-2018 08:03

MikeB4:

I disabled diagnosis and reporting on the watch and battery usage has returned to normal. I had turned this off when I originally set up the watch. The recent update must have reactivated it and there is clearly a bug.

Good to hear :)