I have had my Samsung Galaxy watch 3 for a few days now, litterally as it came out, I had it.
I was really excited for the watch but there are a few issues with it, mainly the deep sleep tracker is not working properly.
For the first 3 days when I bought it, the deep sleep tracking was working fine. But since then, it keeps telling me that I have 0% deep sleep, or very low percentage like 3%. I know this is wrong as I feel energised.
I have so far read a few articles on people with the same issues.
I have tried doing four things:
1. Factory reset
2. Go to the hidden diagnostic section of the watch by dialling #*0*# (or something like that)
It gave me access to the sensors etc, and I reset the settings, calibrating the sensors with a PASS feedback on all sensors.
3. In the screen wake up section of the advanced setting of the watch, I turned off Wake-up Gesture and touch wake up. I have bezel wake up turned on.
4. Touch sensitivity, do not disturb,goodnight mode and theatre mode are all turned off.
Please let me know how I can fix this issue... I am very disappointed with the watch so far even though I am a great Samsung fan.
It's now become obvious that Samsung really do not care about us, the customers - They have given us ZERO input and ZERO fixes on this issue.
I am so angry that I upgraded from my V2 watch the v3 and now have a broken OS, it's disgusting!
I doubt my next watch will be a Samsung tbh!
This is a Youtube link of a guy who makes comparison between different brand of smartwatches and scientific accurate equipment (ex. for sleep tracking)
In his new video he tests Samsung Galaxy Watch 3.
It is useful to watch it.
I too have 0% deep sleep. I see others have the same comment as to a solution. Why should we be jumping through hoops to rectify this issue? A software update/fix from Samsung would be the proper correction, or maybe we are all suffering from poor sleep...
I actually have the Watch three and am very disappointed with the coronary heart charge screen. I have it set to non-stop and it continuously drops out. I also have the Active 2 which is a lot higher so much in order that I've switched back to carrying that full time and am thinking of buying any other for operating out with JRS. The other you can actually the be on the charger.
I can't believe the Samsung Health app now gives me the following notification. Hey Samsung, my deep sleep appears to be "a little low" (one minute!) because your watch doesn't record it properly, lol
Well, it's good to see there are others having the same issue. I have this very same issue with the Active Watch 2 and it's been frustrating. I wear my FitBit charge 2 watch on my other wrist and the sleep tracking on it shows I get an 1hr+ of Deep sleep vs. 0 to 15min on the Active 2. Someone had mentioned to change the heart rate measurement from all the time to intervals and even that doesn't work.
So I just bought a GW4 figuring maybe the newer model will have a better sensor.....NOPE! Same results. On my Active 2/GW4, my sleep by score ranges from 50-60 and even sometimes in the high 40's but on my FitBit Charge 2 it's constantly in the 80-90 range. That watch is like 5 years old and does a better job at sleep tracking than my brand new $350 GW4. Ridiculous! I'm taking it back.
Here's comparison screenshots I took as example, from my sleep last night (top one is from my GW4 and bottom one is from FitBit Charge 2):
If you want a shocker guys, I upgraded to the Watch 4, thinking that this fiasco with deep sleep would end.
Sadly, the watch 4 is just the same, the deep sleep states average at 8 minutes, I have had the watch since its day of release, it's had 1 update but that did not fix it.
I am so angry at Samsunbg for not getting this right, it's such a fundamental part of why we buy these things, and for it not to work AGAIN is quite shocking!
Same here. Sleep As Android reported deep sleep times, but when I switched to SH (on my new GW4), I have nearly zero deep sleep.
I don't think this is a sensor thing, I understand this is estimated upon different sensors readings. So, a SW update COULD fix this, but I already received two and nothing changed.