Related
Ive had the Gear 2 for 6 days. I bought it last thursday, put it on and paired it in the parking lot and then went to the gym. While riding the recumbent bike I noticed the heart rate monitor was accurate and matched up with the bike's up until around 125 bpm and then it would either give me the "cannot measure" error or would give back a really inaccurate reading... like 71 bpm when it should have been around 148-150. This has been the case every time i go to the gym, no matter how i wear the Gear 2, on the top side of my wrist or the bottom side. I actually live chatted with a Samsung Customer service rep and he told me to do a factory reset to see if that would help. I haven't gone to the gym to see if this helped.
Is this a known issue? I also shaved the hair off my wrist and am now wearing it a bit further up on my arm to test it again today when i go to the gym.
Also another question i had is when you turn the volume all the way up (level 6) when using the gear 2 as a speaker phone is it normal for the speaker to buzz slightly when a person is talking to you?
Epic Nightmare said:
Ive had the Gear 2 for 6 days. I bought it last thursday, put it on and paired it in the parking lot and then went to the gym. While riding the recumbent bike I noticed the heart rate monitor was accurate and matched up with the bike's up until around 125 bpm and then it would either give me the "cannot measure" error or would give back a really inaccurate reading... like 71 bpm when it should have been around 148-150. This has been the case every time i go to the gym, no matter how i wear the Gear 2, on the top side of my wrist or the bottom side. I actually live chatted with a Samsung Customer service rep and he told me to do a factory reset to see if that would help. I haven't gone to the gym to see if this helped.
Is this a known issue? I also shaved the hair off my wrist and am now wearing it a bit further up on my arm to test it again today when i go to the gym.
Also another question i had is when you turn the volume all the way up (level 6) when using the gear 2 as a speaker phone is it normal for the speaker to buzz slightly when a person is talking to you?
Click to expand...
Click to collapse
I have this issue for only a few minutes in an hour workout... but then it will go back to normal. I compared it to a strap heart rate monitor and it would stay +1-5 versus the strap. Otherwise it even gets up to 170 when I go hard. I usually start with it higher on my arm because my bone sticks out sometimes it doesn't get a good connection, but it usually falls and still tells accurately. Otherwise I would say it is accurate a majority of the time.
smeiff said:
I have this issue for only a few minutes in an hour workout... but then it will go back to normal. I compared it to a strap heart rate monitor and it would stay +1-5 versus the strap. Otherwise it even gets up to 170 when I go hard. I usually start with it higher on my arm because my bone sticks out sometimes it doesn't get a good connection, but it usually falls and still tells accurately. Otherwise I would say it is accurate a majority of the time.
Click to expand...
Click to collapse
Yeah it must be how close I wear it to that bone. I actually took my first one back thinking there was something wrong with it... The problem is i have a big wrist... I think I will replace the band. Thanks for the reply!
As in the title, now that I have turned on the lock which should only activate when I take off the watch I find that it activates while still on my wrist. This is happening seemingly randomly several times a day and is quite annoying. I like the security of it locking if it's not on my wrist but it is becoming a nuisance. Anyone having a similar problem?
I'm having the same problem. I found this post from a Google search, hoping to find a solution.
Were you able to figure it out?
same issue here. very annoying. i've ended up disabling the PIN lock because it keeps happening (i assume because it's not super tight on my wrist, but i don't want it too tight).
It seems to be one of a few glitches on the gear S2 (i also can't tag HR measurements, and the weather app often won't refresh if my Note4 hasn't been used in a few hours).
pretty disappointed with Samsung since these issues have been around for months.
It's weird because mine does too, yet my bf's doesn't. I'm thinking to just reset to factory and start over.
This is an old thread, but did anyone ever find a solution? Mine was working fine until I started disabling things to extend battery life... now it locks as soon as the screen blanks. I have a feeling there's something it needs for heartrate monitor that I disabled... any ideas? Thanks
I know that this sounds ridiculous, yet I have observed this issue for the third year in a row.
My Neo 003 smartphone (Android 4.2, 2013) fails to read out its sensors (gravity, compass, location etc) during the summer months!
All apps reading the sensor data will 'freeze' or 'hang', or simply report 'waiting for event'.
The values for xyz are stuck at odd values, or change once or twice before hanging.
I can provide more details on the sensor hardware used, screen shots of these weird freezes if interested.
It took a while before I noticed this obvious dependency, as it is so odd and unexplainable.
After working flawlessly for several months the sensor readouts would start to hang more often in later spring of 2014.
The effect got worse over time; I suspected a hardware failure and was pissed when they got stuck for several months in the summer. I contacted the manufacturer and was brushed off - FU! So I kept trying.
To my surprise the sensors would start returning values more often in early fall, and would run perfect again around October, for the entire winter!
And then the SAME happened in 2015 again! And again this year!! Currently all sensors react flawlessly to motion, shaking, rotation. They had become flaky around April, hardly worked in May and failed during the summer, came back to life several weeks ago: I checked them almost daily to see this drift of functionality. Just WHAT is going on here?
I have tried to fool my phone by resetting the date and not going online to keep the wrong time - it did not affect the dependency. It failed to run in summer when set to winter dates.
I use the phone at home exclusively and always in the same rooms. There is no significant environmental change I can think of that could affect this (temperature, pressure, humidity). The problem occurs as well on the road anyways.
I am a phycist by trade, in fact I was quite involved in electronic measurement and data collection for many years.
This phone is driving me nuts, because I can not come up with a resasonable explanation for its odd behavior?
Android seems to use a quite thick layer of software drivers and event handles to manage the sensor readouts; it looked rather confusing to me and was not straight forward as I hoped for.
Since the failing mechanism is NOT hard but 'soft' (slowly shifting from working to failure over several weeks, and back to functionality in a similar way) it can not really be a software 'numbers' glitch, or?
Could other apps (about 600 are installed) interfere and block the readout? But why only in the summertime months??
I REALLY want to learn about this phenomenon, because it is about the weirdest problem I ever saw on an electronic device.
Who can shed some light on this, who can explain how Android initiates the sensor chips and reads them out?
Who has seen the same effect on other phones or devices?
What tests should I conduct to isolate this unique failure pattern (phone in the fridge, in a Faraday cage etc).
I do not want to break my Neo, despite its age it works quite well and runs stable, with its original ROM in place.
It took me THREE years to come forward with this issue, because I could not believe my own observations.
Now it is time to bring it up.
Please explain my spooky phone to me - thanks a lot!
m
mw210461 said:
I know that this sounds ridiculous, yet I have observed this issue for the third year in a row.
My Neo 003 smartphone (Android 4.2, 2013) fails to read out its sensors (gravity, compass, location etc) during the summer months!
All apps reading the sensor data will 'freeze' or 'hang', or simply report 'waiting for event'.
The values for xyz are stuck at odd values, or change once or twice before hanging.
I can provide more details on the sensor hardware used, screen shots of these weird freezes if interested.
It took a while before I noticed this obvious dependency, as it is so odd and unexplainable.
After working flawlessly for several months the sensor readouts would start to hang more often in later spring of 2014.
The effect got worse over time; I suspected a hardware failure and was pissed when they got stuck for several months in the summer. I contacted the manufacturer and was brushed off - FU! So I kept trying.
To my surprise the sensors would start returning values more often in early fall, and would run perfect again around October, for the entire winter!
And then the SAME happened in 2015 again! And again this year!! Currently all sensors react flawlessly to motion, shaking, rotation. They had become flaky around April, hardly worked in May and failed during the summer, came back to life several weeks ago: I checked them almost daily to see this drift of functionality. Just WHAT is going on here?
I have tried to fool my phone by resetting the date and not going online to keep the wrong time - it did not affect the dependency. It failed to run in summer when set to winter dates.
I use the phone at home exclusively and always in the same rooms. There is no significant environmental change I can think of that could affect this (temperature, pressure, humidity). The problem occurs as well on the road anyways.
I am a phycist by trade, in fact I was quite involved in electronic measurement and data collection for many years.
This phone is driving me nuts, because I can not come up with a resasonable explanation for its odd behavior?
Android seems to use a quite thick layer of software drivers and event handles to manage the sensor readouts; it looked rather confusing to me and was not straight forward as I hoped for.
Since the failing mechanism is NOT hard but 'soft' (slowly shifting from working to failure over several weeks, and back to functionality in a similar way) it can not really be a software 'numbers' glitch, or?
Could other apps (about 600 are installed) interfere and block the readout? But why only in the summertime months??
I REALLY want to learn about this phenomenon, because it is about the weirdest problem I ever saw on an electronic device.
Who can shed some light on this, who can explain how Android initiates the sensor chips and reads them out?
Who has seen the same effect on other phones or devices?
What tests should I conduct to isolate this unique failure pattern (phone in the fridge, in a Faraday cage etc).
I do not want to break my Neo, despite its age it works quite well and runs stable, with its original ROM in place.
It took me THREE years to come forward with this issue, because I could not believe my own observations.
Now it is time to bring it up.
Please explain my spooky phone to me - thanks a lot!
m
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like defective hardware and something that is pretty much out of scope. There are several sensor testing/calibrating apps you could try to test your sensors. That is all I can suggest really
Good Luck
Sawdoctor
Thanks for looking!
It has NOTHING to do with calibration.
If the sensors do not react during the summer, they can not be accessed anyway.
I installed and tried a dozen or so sensor apps, all show the problem, if in different ways (frozen, 'waiting for event' etc).
Noticable is that the orientation readout is consistently showing the same '(fixed) value 0.0130 for x, while y and z show flat 0, every time the error occurs. The compass is entirely frozen during these times as well.
The Neo uses different sensors for magnetic, gyroscopic and gravitation measurements.
I would not have asked here, if I had ANY clue about this causality.
WHAT is throwing the orientation/gyro sensors off for several months and ONLY in the summer? Inside my own house, at fixed environmental conditions?..
mw210461 said:
Thanks for looking!
It has NOTHING to do with calibration.
If the sensors do not react during the summer, they can not be accessed anyway.
I installed and tried a dozen or so sensor apps, all show the problem, if in different ways (frozen, 'waiting for event' etc).
Noticable is that the orientation readout is consistently showing the same '(fixed) value 0.0130 for x, while y and z show flat 0, every time the error occurs. The compass is entirely frozen during these times as well.
The Neo uses different sensors for magnetic, gyroscopic and gravitation measurements.
I would not have asked here, if I had ANY clue about this causality.
WHAT is throwing the orientation/gyro sensors off for several months and ONLY in the summer? Inside my own house, at fixed environmental conditions?..
Click to expand...
Click to collapse
I'm out of ideas then all it can be is faulty hardware. Maybe try asking in android q&a to see if you can find any other Neo 003 users see if they have the same issue or not
I have raised this issue in the NEO 003 thread, without results. I read about other phones acting up on their sensors, but never due to DATE patterns; typically they fail entirely or due to firmware mods, driver issues etc.
I AM willing to believe that the temporary failure of my NEO 003 sensors is hardware related, BUT:
which miniscule environmental variable change could possibly let the sensors fail to respond to reading them during the summer months, inside a regular home?
What IS different in July compared to March? Neither gravity nor magnetic fields fluctuate in any reasonable range throughout the year.
Nor does temperature (which varies far more depending on other factors; the phone shows board temperatures of anything between 39C and 60C depending on CPU load).
Room humidity is lower in the summer than in the winter time (heating in Central Europe), but then the problem happens inside a home as well as outside on the road. And there humidity can be anything from 30-100% during the day.
I even thought of electro-magnetic interferences, but there is nothing in my home that would only disturb electronics in the summer. Plus the problem is not limited to my own home anyways.
As a physicist I AM at the end of my wits. For me this is downright 'spooky'.
Never would I have brought this up if I had the faintest reasonable explanation, yet I can prove that the observation is true. It took me THREE years (winters and summers) to notice the regular, season related, repeatability of the problem!!!
I have two more choices:
- entirely resetting the phone and rebuilding it; with 600 apps installed this may take months to get them all tweaked and running again
- conduct more thorough system time modifications (prohibiting date adjustments for several days in a row, while booting the phone frequently and using it offline), trying to enforce it to accept SUMMER as the current season. First tests failed to trigger the reported sensor failure.
The fact that failures do not occur 'black/white' but slowly (more and more often failing to return data, from 'alive' to 'dead' and vice versa, over several weeks) does NOT speak for the software dependency. A number glitch would kill the readout hard at a given date; yet it does NOT.
As you can see I AM pondering quite a bit, unwilling to accept a phenomenon that defies my understanding of this universe. This IS my 'Einstein moment': spooky behavior beyond my horizon, unknown entanglements, as mentioned earlier.
Who knows, they might find this thread and act
To kick it off:
1) Heart rate sensor is more miss than hit. I see a lot of 'clean the sensor and move it backward' messages. Nonsense of course, it should just work.
2) Floor count is totally 1000% off. Today I climbed well over 20 stairs (3-4 meter stairs) and the S3 indicates a glorious total of 3. Yes THREE Samsung, 3.
3) Altitude meter tells me I live 16 meters below sea level. I live in Amsterdam which is 3 meters below (really). But it gets better. During my yesterday's run it registered an elevation of -112 meter.
4) Messages from the phone do not always arrive on the S3. Maybe aliens interfere but that's unlikely so Samsung, please fix this. nr 1 missed is GMail, then Whatsapp.
5) This is not a bug but I would really like to see an option to permanently disable this watch as a Bluetooth device to take phone calls. I have my car for that, or my phone. Not the stupid watch.
OK, over to you guys, bring it on!
For your point 5, I think you can do this in the bluetooth settings for the watch on the phone - just turn off 'call audio'. NB: I have not tried this...
veletron said:
For your point 5, I think you can do this in the bluetooth settings for the watch on the phone - just turn off 'call audio'. NB: I have not tried this...
Click to expand...
Click to collapse
If it worked... But it keeps switching back on, also after a soft and full reset.
blackspp said:
If it worked... But it keeps switching back on, also after a soft and full reset.
Click to expand...
Click to collapse
I was able to get it to stick permanently by repairing my car bluetooth and setting it to Phone Calls while having the watch disabled.
I'll try it again tomorrow, who knows!
Spotify
Advertising Spotify compatibility when as of right now, there is not.
Wrist gestures like in Android Wear
I always thought that you had to calibrate the altimeter at sea level???
Regarding #4: are you using AOD? If not, try using AOD and see if your notifications are more consistent.
PLS give me options for Google maps directions. I need nothing more than the direction arrows on the watch. No map needed. Anyway screen is too small for that. Just xxx meter +arrow
But I am super happy with the rest (off topic)
edit. I have found possible solution for the nav arrows Directions gears s2, which works with google maps.
Both on Phone and on gear an app is needed.
odyseus said:
I always thought that you had to calibrate the altimeter at sea level???
Click to expand...
Click to collapse
Tried both ways, Calibrate known height and altimeter.
Googling this there are loads of S2 complaints regarding this, I guess this is not much improved.
most people complaining about altimeter don't know how a barometer works
also the best altimeter based on atmosferic pressure must be calibrated every time is possible to give good results
when the weather change a variation in pressure can be of 3-5 Hpa in 30 minutes and on altimeter more than 50m
weather change is a storm but also a fairy wind
when s3 measure a floor it register a .3 Hpa variation that must be in 5 to 20 sec
also a slap on the watch can be seen as a floor and the immersion in 50 cm of water can be 10 floors and also a shower and a storm
after a shower o a swimming pool the barometer is out of order for hours
samsung is most of times a good tech but can't do miracles
sorry for english
hallo
g
odyseus said:
I always thought that you had to calibrate the altimeter at sea level???
Click to expand...
Click to collapse
It is a good thing to do. However it's based on barometric pressure so really doesn't matter that much. The key is to do it near something you know has a known elevation that way you know if it's correct. Like a sign in a national park or something that tells you, "you are at such and such El. ..."
BTW, a lot of you take things too seriously on this device. It's a watch, as long as the time is accurate all else are fun gimmicky gadgets for your wrist. If serious accuracy of data is important to you, buy the right tool for the job. It's like owning a repair business and trying to run it using a Leatherman tool.
Well, I live in Amsterdam, pressure has been 1027 hpa all day, we're at 3m below sea-level but the watch is all over the place and I've calibrated it like 209 times. Hasn't been wet, smacked, dropped. It's a watch with a barometer that's not too good.
blackspp said:
OK, over to you guys, bring it on!
Click to expand...
Click to collapse
1. hair, tattoo, excessive sweat, a large band can and will interfere with HR
2. floors / stairs / floors / stairs / verdieping / trap (used GT for dutch) -- or maybe you're trying to tell something else because 20 stairs are relatively close to 3 floors
3. atmospheric pressure is pretty unstable even at known sea levels and when is taken into account for altitude can be messy
4. I don't know, it never happened to me but it could be an issue I suppose
5. connections, disconnect BT
20 floors, some 60.meters.
When wanting to look at widgets from the clock face the bezel it turned clockwise - but the display animation rotates anti clockwise
The opposite is true to see notifications.
This just seems wrong to me and I often turn the bezel the wrong way.
I cant see Samsung changing the default behavior and I am starting to get used to it but an option to make it work 'correctly for my head' would be nice.
Hey guys, I did a full test of the gear s3 heart rate against my chest strap and Apple Watch 2 Nike. I did indoor running and indoor biking for three days. My findings are that it's almost perfect, with 2 or 3 bpms difference with my chest strap. This difference is not always, some most of the time gear s3 was matching my chest strap. The Apple Watch was good too.
Method: chest strap + wahoo iPhone app. Gear s3 below my wrist ( this is key, when you find the sweet spot, it's super accurate) + s-health on iPhone. Apple Watch + workouts app.
Let me know your findings!
Is the step count accurate and for everyone. For me I think it counts too many...,
Sent from my Nexus 6P
Techvir said:
Is the step count accurate and for everyone. For me I think it counts too many...,
Sent from my Nexus 6P
Click to expand...
Click to collapse
It does.
It should only count arm movements combined with forward motion but it also incidentally counts just arm movements. Plus, this morning, it showed 54 steps when I picked it up from the drawer. Obviously it should have been zero.
Than again, on a full day it's pretty good, about the same as my Pebble Time Steel (which I compared it with over the weekend).
I've had my Gear for about 10 days and have piled up over 12000 steps each day, but have only been credited with 1 floor climbed. My house has 3 stories so I'm pretty sure that total should be closer to 100. Anyone else having this issue?
Don't hold onto any railings and make sure your arm swings as if you are walking.
Sent from my SM-G935F using Tapatalk
ardsar said:
Don't hold onto any railings and make sure your arm swings as if you are walking.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
LOL, all I could thing of was Seinfeld when I read your response. "How's this? Or this?" "You seem to be getting the hang of it." Seriously, though, I deliberately hold the rail with the opposite hand when climbing stairs so that I can swing the one with the Gear on it. Still nothing. Not sure what's up. Any other ideas?
I walk up and down to the sixth floor at work a couple of times a day and typically that adds up to 2 or 3 floor. I have a 3 story house, same thing. The floor counter sucks...
Thanks. Definitely sounds like it's not just me. Maybe a firmware update will fix it.
Well, at least now I know it's not just me having this issue
same problem never counts my stair climbs
If it is basing floors on the altimeter, that might explain the problem. The altimeter on this thing is trash. It's rarely within 100 feet of my actual elevation, even after a calibration. Doubt that can be fixed, but I'll keep my fingers crossed.
Thinks I'm riding a bike when I get in the car sometimes. Also the pace in S Health is way off. Not the best fitness tracker around but we don't have any other options.
Though not accurate; mine is working fine. I remember reading something like 'one floor is calculated as approximately 3 metres'.
Can someone confirm this?
Floor count
I've done at least 10 floors today and the Gear shows 1. It was OK yesterday. Any ideas?
---------- Post added at 06:35 PM ---------- Previous post was at 06:12 PM ----------
A reboot got it counting floors accurately again
Same problem. Altimeter has me at -6M! Fitbit shows 10 floors to S3 2 floors. Rubish
On the flip side of the problem - Mine detects elevator rides as stairs climbed.
I think it is the same "rules" as the FitBit I was wearing before the S3. They only register a floor if the flight of stairs consist of 10 continuous steps.
I have a split level house, two flights of 8 steps.
If I walk up one it doesn't register as a 'floor' but if I walk up both (as long as I don't delay on the landing) it increases my S3's floor count by 1 floor.
On my outside walks a steady climb up a hill does register floor counts as well.
boogsta161 said:
On the flip side of the problem - Mine detects elevator rides as stairs climbed.
Click to expand...
Click to collapse
Lol that's funny
Sent from my iPhone using Tapatalk
Same issue for me too. Had the watch for about 3 weeks and very few floor counts
I've noticed the same as all, I get a very low stair count. I have one set of stairs in the house and I'm up and down them all day, but the count stays low. I had a Fitbit that would give me a very accurate count of my stairs. I've turned off floor count since it's almost useless.
Sent from my SM-T530NU using Tapatalk
Yeah it's not accurate at all....I get less than 5 floors a day and I have 2 stair wells at home which I dash through hourly...It's flawed for sure.
Sent from my SM-N930V using Tapatalk
I've been trying out different functions; floor count is definitely buggy, so is the heart rate monitor especially when you are working out, the distance counter too counted an extra 1 kilometre on my run, the Calorie counter is also buggy for Other Workout option as it confuses vigorous and moderate intensity.
I've tried turning it on and off, I've tried cleaning the ram, I've tried swinging mu arms, I've tried to walk slower and faster but it's still there. I would send an email to S Health, but they'll like send me to another guy and ask me to detail it again, and I'm jist too lazy.
To be honnest, all the sensors on the GEAR S3 are totally screwed up.
Floor count, steps, heart rate, altimeter, barometer all terrible. The most inccurate looks to be the altimeter. Staying in my house for a week, altimeter fluctuate between -71m and +70m... USELESS! Not too sure if a firmware upgrade can fix those sensors or if they are low cost pieces of crap. Will see... or not