Really enjoying the watch but I have an issue with the calorie counter on S Health, it seems to decide I've already burned a significant amount of calories each day by the time I've woken up. For instance, the last couple of nights I have gone to bed with the watch next to me (I don't like sleeping with a watch on), once on aeroplane mode and once just as normal. When I then wake up at 7am and look at the S Health counter on the watch, it seems to decide that I've already burned about 500-600 calories for the day! Whilst I would love to burn that in my sleep, it's obviously well off.
Is it possible to set it so that the calorie counter is at 0 or a realistic level until I put the watch on in the morning? Or is the issue that I'm not sleeping wearing the watch?
you are living and so you burn calories
the value without moving is calculated on your age, weight,sex
gianoit said:
you are living and so you burn calories
the value without moving is calculated on your age, weight,sex
Click to expand...
Click to collapse
But if the poster is not wearing the watch during sex - how is it calculating the calories burned??
Calories Count
Obeg said:
But if the poster is not wearing the watch during sex - how is it calculating the calories burned??
Click to expand...
Click to collapse
The calories count on my S3 are completely wrong.
The actually counting from S3 shows enormus calories burned during the day - more than 11.000 average and at the same time, within calories counting during running it counts just 61 calories during 35 minutes of fast running 12,5 km/hr (my age is 63, height 189 cms and weight 86 kgs). Something is completely wrong.
Any idea how to correct this calculations?
I am having the exact same issue. I burned insanely 25 000 kcal today. Amazing. But when I was running for an hours, I only burned 60 kcal. Better doing nothing
Omg, I am annoyed. Also, it did not show the distance run etc. This is new and I must say, I am sorry that I have purchased this watch. Nothing for fitnessfreaks like me....
Unlike Apple Samsung takes into consideration your basal metabolic rate . So when you plug in your age, sex and weight it's going to use that to calculate your BMR. Any calories burned through actual exercise will just be added onto that.
aGua421 said:
Unlike Apple Samsung takes into consideration your basal metabolic rate . So when you plug in your age, sex and weight it's going to use that to calculate your BMR. Any calories burned through actual exercise will just be added onto that.
Click to expand...
Click to collapse
Well I must have an outstanding metabolic rate. In taking the watch off the charger and putting it on my wrist in the morning I burned 575 kcal!! Come on. Just like several other things it's not working right. Anyone have a work around?
Related
So I'm sort of interested in purchasing a Gear 2 Neo, and am always using runkeeper on my phone to track my distance, pace and calories burned and was wondering if the Gear 2 Neo can do the same?
I'm also curious as to whether it works with RunKeeper or not, as I like to track all my runs with it.
Yes, it can measure calories burned, heart rate, distance traveled, steps taken as well as speed.
Milkeh said:
So I'm sort of interested in purchasing a Gear 2 Neo, and am always using runkeeper on my phone to track my distance, pace and calories burned and was wondering if the Gear 2 Neo can do the same?
I'm also curious as to whether it works with RunKeeper or not, as I like to track all my runs with it.
Click to expand...
Click to collapse
As already mentioned above, yes it can. One of the included apps is called Exercise and it will track your running, walking, cycling, and hiking. I use this for my walking and running (on the elliptical) and it gives me: start time, duration, distance (miles), calories burned, avg speed, max speed, avg pace, max pace, and average heart rate.
kbboykin said:
As already mentioned above, yes it can. One of the included apps is called Exercise and it will track your running, walking, cycling, and hiking. I use this for my walking and running (on the elliptical) and it gives me: start time, duration, distance (miles), calories burned, avg speed, max speed, avg pace, max pace, and average heart rate.
Click to expand...
Click to collapse
Thanks for the replies. I read something about the tracking not being accurate due to not having GPS. Does anybody know how it compares to using runkeeper on my phone?
I dont' understand how it work for bikking because there isnt' steps counts with this sport ... what's happening with this ?
[email protected] said:
I dont' understand how it work for bikking because there isnt' steps counts with this sport ... what's happening with this ?
Click to expand...
Click to collapse
hiking and Biking it user the GPS not the pedometer per Samsung site on the how to instructions...
can anyone point me in the right direction for finding a great fitness app that can connect to a chest strap heart rate monitor? using primarily for monitoring heart rate during weightlifting. Unfortunately samsung health will not track heart rate for weightlifting.....
The UnderArmour suite of apps should be able to do it. I'm not sure I'd call them "great" - I've had some syncing issues, but theoretically, it should do what you're looking for.
cozyjohn said:
can anyone point me in the right direction for finding a great fitness app that can connect to a chest strap heart rate monitor? using primarily for monitoring heart rate during weightlifting. Unfortunately samsung health will not track heart rate for weightlifting.....
Click to expand...
Click to collapse
I use UA Record while doing strength training (basic compound lifts) or conditioning type work in the gym. I just pick "Gym, other" although there are options such as upper/lower body. The only lists that get my heart up are squats and to a lesser extent deadlifts. I can hit 120 BPM on heavy squats.
You get a workout timer on one screen and HR on the other.
When I do conditioning workouts I can get my HR up as high as 190 and show a calorie burn around 500 for a half hour. Which is about right.
For runs I'll use MapMyRun.
arl16 said:
The UnderArmour suite of apps should be able to do it. I'm not sure I'd call them "great" - I've had some syncing issues, but theoretically, it should do what you're looking for.
Click to expand...
Click to collapse
Yeah it takes almost 2 days to update the app on the phone, not syncing with samsung health.
michail71 said:
I use UA Record while doing strength training (basic compound lifts) or conditioning type work in the gym. I just pick "Gym, other" although there are options such as upper/lower body. The only lists that get my heart up are squats and to a lesser extent deadlifts. I can hit 120 BPM on heavy squats.
You get a workout timer on one screen and HR on the other.
When I do conditioning workouts I can get my HR up as high as 190 and show a calorie burn around 500 for a half hour. Which is about right.
For runs I'll use MapMyRun.
Click to expand...
Click to collapse
Hey, it appears that UA Record syncs better than Map my run, thanks!
Anyone have any luck getting this to sync with Samsung Health or myfitnesspal? I can't get it to sync with either... The latter is made by the same company lol.
gettinwicked said:
Anyone have any luck getting this to sync with Samsung Health or myfitnesspal? I can't get it to sync with either... The latter is made by the same company lol.
Click to expand...
Click to collapse
I use Endomondo for weights, spinning & kayaking. Same company as UA. No problems with syncing with Samsung Health.
S3 Heart rate monitor wildly over reporting bpm
I searched, but didn't find a suitable post. I also Googled my querry with no satisfaction. Anyway my S3 has been working like a champ until a few days ago it started reporting 170-201 range. My age heart rate max is 156. After finishing a recent run, I dashed into the house while the HRM was still way over reporting and had my wife take my heart rate. As I suspected, mostly because I'm still alive, my heart rate was fine.
I factory reset the watch, played with heart rate settings and I am still at a loss.
My questions is, anyone else have this or similar issue that they overcome.
Any suggestions are welcome.
Did you try to measure your HR by your own by using ordinary clock and compare with the one on the Gear?
I made a thread about something similar: https://forum.xda-developers.com/gear-s3/help/questions-heart-rate-sensor-monitor-t3665746
However, today I tried something new during my run this morning. Normally, they advise wearing the watch up past your wrist bone, but I decided to push it up even further, almost 3 or 4 inches from my wrist bone. The good news is that the results were much more accurate. Prior to the adjustment, I was getting similar results of 200 bpm, which is just impossible - my max heart rate is 189. The readings I received after the run showed 190 max and 177 average. That appears to be much more accurate and realistic, even if it may be 3 or 5 beats off. It's at least useful now in terms of maintaining peak rates during workouts.
I pushed the band further up my wrist and tightened that sucker like a bale of hay. Heart rate came down, but my wrist hurts now. LOL
I think it's time to try Sammy's support. Although I've had perhaps 8-10 Samsung phones in my life and similar number of other high end phones for family members, I have never had to deal with their support. Wish me luck and thanks for your help.
25% over reporting bpm
Chest hart rate band : 103 avg bpm
Fitbit BLAZE: 105 avg bpm
Samsung Gear: 129 avg bpm
I also have the same problem and could not find a way to real with this problem. I compare it to a new chest hrm and the difference is day and night. My S3 shows me around 190 bpm in a 10K run wheras chest strap hrm shows 150 bpm; so bad.
I have the same problem
I've had my gear3 for about a year and just this week it started reading my daily bpm range between 79-208. My normal resting is under 60 and I can only get it up to 180 in a dead sprint.
I turned it only always read and then watched it. As soon as I woke up the screen it would around 200 but would drop with every beat until it got to around 65 and go back to sleep. When I woke it back up it had climbed high again. I wonder if there is a way to recalibrate it.
You can stop discussing this issue as there is no solution.
In the official Samsung forum, there are hundreds of posts claiming this issue but no solution from Samsung.
It is a design error of the sensor which cannot be solved with SW. Even changing the mainbord several times did not solve the issue.
So finally: heart rate monitoring with Samsung watches (Even the new ones) is useless.
Regards,
Dodger
I have a watch 2 classic and it looks like the heart rate sensor works fine only up to 110-120bpm. After sports when my heart rate is way more than 150bpm it always shows something in the 110-120bpm range.
I don't care if it is off by +-5bpm, but being off by 40+ is definitely not ok. I understand that movement during sports could pose a problem, but that happens after I sit down and am not moving at all.
Does the heart rate sensor work for you normally for higher bpms?
If it does, then I should probably send it to be repaired.
yupi303 said:
I have a watch 2 classic and it looks like the heart rate sensor works fine only up to 110-120bpm. After sports when my heart rate is way more than 150bpm it always shows something in the 110-120bpm range.
I don't care if it is off by +-5bpm, but being off by 40+ is definitely not ok. I understand that movement during sports could pose a problem, but that happens after I sit down and am not moving at all.
Does the heart rate sensor work for you normally for higher bpms?
If it does, then I should probably send it to be repaired.
Click to expand...
Click to collapse
looking at my data via the Huawei Health app over the past few weeks, there have been a few instances (when running) when my heart rate got above 175. maybe the watch is not registering your heart rate during those peak times, so it only catches it on the way down?
jco23 said:
looking at my data via the Huawei Health app over the past few weeks, there have been a few instances (when running) when my heart rate got above 175. maybe the watch is not registering your heart rate during those peak times, so it only catches it on the way down?
Click to expand...
Click to collapse
I doubt it. I have tried it many times using google fit, huawei health or just by launching the heart beat app. My heart rate was definitely much higher at that time than the watch measured.
Does it only peak for you or is it above e.g. 150 for a longer time?
yupi303 said:
I doubt it. I have tried it many times using google fit, huawei health or just by launching the heart beat app. My heart rate was definitely much higher at that time than the watch measured.
Does it only peak for you or is it above e.g. 150 for a longer time?
Click to expand...
Click to collapse
so looking at my 18-min 2-mile run on Tuesday, my heart rate was above 150 from 8:08am to 8:16am. keep in mind that my rest heart rate is about 55. i know that's a small sample, so maybe I'll test on an elliptical machine next time I go to the gym.
jco23 said:
so looking at my 18-min 2-mile run on Tuesday, my heart rate was above 150 from 8:08am to 8:16am. keep in mind that my rest heart rate is about 55. i know that's a small sample, so maybe I'll test on an elliptical machine next time I go to the gym.
Click to expand...
Click to collapse
I think that's a good sample. Now I know that the sensor should be working and it's obviously not. I've only seen it peak a few times above 150 and then it was back to 110-120. I'll check if my brother's watch can measure my bpm correctly and if my watch can measure his bpm correctly. Then I'll definitely know if the watch is a problem or there's something with me
I got a Pixel 7 Pro, my first phone with a pressure sensor, which I thought I'd use in an app to compute the current altitude.
The sensor returns values around 1000, as expected at a pretty low altitude.
I logged a lot of values during several walks, and they weren't quite what I expected: What I find strange is there are periods with pretty accurate readings, where the difference between consecutive readings is around 0.01, alternating with periods where the difference between consecutive readings is around 2, which translates to some 15 meters, which is huge for readings taken less than half a second apart. So the latter readings are pretty much useless, unless processed to smooth the values, which is what I'm trying to do now.
I'm attaching a chart, with the readings from one walk, which should help illustrate the issue.
So I wonder if this is something that happens on other (Android) phones (ideally other Pixel 7's, but there aren't too many of these).
Yes. These are cheap uncalibrated sensors designed for mass production and are by no means intended by be accurate.
V0latyle said:
Yes. These are cheap uncalibrated sensors designed for mass production and are by no means intended by be accurate.
Click to expand...
Click to collapse
Thanks!
My issue isn't as much that they are not accurate, but that accuracy changes suddenly and hugely from time to time.
When translated to altitude, the accuracy is around 15 centimeters for several minutes (which I think is good enough for many applications), and then suddenly jumps to 20 meters, and after a while it's back to 15 centimeters, without at least going gradually from one state to another.
ciobi said:
Thanks!
My issue isn't as much that they are not accurate, but that accuracy changes suddenly and hugely from time to time.
When translated to altitude, the accuracy is around 15 centimeters for several minutes (which I think is good enough for many applications), and then suddenly jumps to 20 meters, and after a while it's back to 15 centimeters, without at least going gradually from one state to another.
Click to expand...
Click to collapse
That's pretty normal, when you consider the fact that barometric pressure drops about 1 PSI (6.9kPa) for every 2300 feet (698m) of altitude. This means that 20 meters (65 feet) of altitude would be a tiny, tiny difference, enough to be lost in the rather large drift inherent to inaccurate devices.
V0latyle said:
That's pretty normal, when you consider the fact that barometric pressure drops about 1 PSI (6.9kPa) for every 2300 feet (698m) of altitude. This means that 20 meters (65 feet) of altitude would be a tiny, tiny difference, enough to be lost in the rather large drift inherent to inaccurate devices.
Click to expand...
Click to collapse
Sorry, I don't think I was able to express my question well enough, so I'll try one last time:
My question isn't about accuracy, but about consistency, namely the lack of consistency.
I get it that these sensors are not that accurate, and I'm fine with 20 meters errors, as long as they are consistent.
What puzzles me that I get 1000 consistently inaccurate readings over several minutes, followed by another 1000 of accurate readings, without any change in the environment. It's the same app, continuously getting pressure notifications and storing them, and the values I get switch between these 2 states every once in a while (could be 1 minute, could be 30, I didn't find any pattern).
Real data from a run, where new values come some 10 times a second:
In the accurate state: 996.58, 996.56, 996.54, 996.51, 996.51, 996.53, 996.54, 996.53, 996.53, 996.53, 996.55 ... (variations of at most 0.03 between a value and the next)
In the inaccurate state: 994.92, 996.03, 998.74, 994.57, 997.03, 996.06, 999.36, 994.96, 995.61, 995.20, 996.15 ... (variations as large as 4.4 between a value and the next)
ciobi said:
Sorry, I don't think I was able to express my question well enough, so I'll try one last time:
My question isn't about accuracy, but about consistency, namely the lack of consistency.
I get it that these sensors are not that accurate, and I'm fine with 20 meters errors, as long as they are consistent.
What puzzles me that I get 1000 consistently inaccurate readings over several minutes, followed by another 1000 of accurate readings, without any change in the environment. It's the same app, continuously getting pressure notifications and storing them, and the values I get switch between these 2 states every once in a while (could be 1 minute, could be 30, I didn't find any pattern).
Real data from a run, where new values come some 10 times a second:
In the accurate state: 996.58, 996.56, 996.54, 996.51, 996.51, 996.53, 996.54, 996.53, 996.53, 996.53, 996.55 ... (variations of at most 0.03 between a value and the next)
In the inaccurate state: 994.92, 996.03, 998.74, 994.57, 997.03, 996.06, 999.36, 994.96, 995.61, 995.20, 996.15 ... (variations as large as 4.4 between a value and the next)
Click to expand...
Click to collapse
Again, this is normal. The sensors are neither accurate nor precise. This means that the pressure measurements may drift constantly.
Think of it as resolution as well as stability. They aren't sensitive enough to detect small changes in atmospheric pressure, and they aren't stable enough to deliver consistent readings all the time. They're cheap mass market consumer devices.
V0latyle said:
Again, this is normal. The sensors are neither accurate nor precise. This means that the pressure measurements may drift constantly.
Think of it as resolution as well as stability. They aren't sensitive enough to detect small changes in atmospheric pressure, and they aren't stable enough to deliver consistent readings all the time. They're cheap mass market consumer devices.
Click to expand...
Click to collapse
But they are quite accurate and plenty sensitive for some periods of time. As you can see in the attached chart, when I'm lucky to catch it in an accurate state, I can absolutely tell based on the sensor data when the phone is placed on a chair vs. on the table or on the floor, let alone when I move to a different floor.
I gave you the most reasonable educated answer I could come up with. If you don't accept that answer, it's up to you to find your own.
Cheers