Gear S3 sensors not working after Tizen 3.0.0.2 update.

[Ajey Surya]

After the update of Samsung gear s3 to Tizen 3.0.0.2. Sensors are not working. Also battery drainage is very high. 

Hardware & Software Details:

Model - SM-R760

Software Version - R760XXU2CRH1

Tizen Version - 3.0.0.2

Already did the following workarounds,

1. Soft Reset (using Reset in settings)

2. Change of Phone 

3. Hard Reset (using Reset in boot)

None of the above helped me. 

[userbcMKA9DSlI]

seems like not the software related but the hardware itself. i would call 1800samsung to exchange

[ChrisPP]

Disagree.

Have a look around the forums and FB groups, many people have reported that since Tizen 3.0.0.2 the sensors on their watches have stopped working, including mine.

It is not a hardware issue.

[SamsungLarryK · Accepted solution]

The pedometer and heart rate sensor may not work properly on some watches with a specific software version. The issue will be resolved by a software update. For a temporary solution, reboot the watch when the problem is detected, and then disable the Elliptical trainer and Rowing machine setting. (The menu options may vary by the watch.)

Note: Use the paired phone to check for software updates via the Galaxy Wearable app for the watch.

From the Apps screen, touch Samsung Health.
Rotate the bezel to and touch Settings.
Touch Workout detection.
Touch the switch to turn Off the Elliptical trainer and Rowing machine. (The icon will turn gray when the function is turned off.)

[Ajey Surya]

Thanks. 

Any idea on when the next update will be out? 

[SamsungLarryK]

We can not speculate on future updates.

[Ajey Surya]

What about the battery drainage problem?

Will that also get fixed on coming update? 

[Samsung_Stephanie]

I'm sorry we do not know, we cannot speculate on this information. 

[Ajey Surya]

Turning Off the Elliptical trainer and Rowing machine doesn't help me in anyway. 

Any other solution or when can I expect the next update? 

[Samsung_Stephanie]

I've gone ahead and mark Larry's post as the solution as it lists the temporary work-around steps. The issue will be solved in a future update, however, we cannot speculate on the date that this will be released. I'm sorry for any inconveniences caused.