Can't stop HR sensor - Samsung Galaxy Watch

Galaxy Watch - I've set the heartrate sensor to Manual Only to save battery power. But the sensor is still flashing continuously. How can I fix this?

Fixed it with a factory reset.

My Galaxy LTE also will do this randomly...

Same here. Annoying.
Though it seems some watch faces obey the setting whilst other do not.. I wonder if a watch face can override the system setting?

Runs the battery down much quicker running 24/7. At least it's a simple fix.

Related

Is GPS accurate in Airplane Mode? What about battery life then?

Hi,
I am planning to use Endomondo for skiing for the whole day (09:00-16:00) to track my progress.
Two questions:
1) To save battery I will switch to Airplane Mode. GPS accuracy will be ok?
2) Endomondo have a setting to save battery. Dont know what it means. It says that accuracy wont change. Strange. Has anybody tried to ski all day long without charging with Endomondo?
Sent from my Galaxy Nexus
bat0nas said:
Hi,
I am planning to use Endomondo for skiing for the whole day (09:00-16:00) to track my progress.
Two questions:
1) To save battery I will switch to Airplane Mode. GPS accuracy will be ok?
2) Endomondo have a setting to save battery. Dont know what it means. It says that accuracy wont change. Strange. Has anybody tried to ski all day long without charging with Endomondo?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
1. No. GPS is disabled when you are in airplane mode. Mobile Data connections (3G, wifi) and your phone connection (you will not be able to make or receive phone calls) when you're in airplane mode.
2. I don't know what endomondo does specifically, but most GPS apps, when they say they save battery, do so by recording your location at longer intervals. For example, the app, in a battery saving mode, may record your location every 8 or 10 seconds, instead of 4 or 5 seconds.
I use my Galaxy Nexus while bicycling, I find that 7 or 8 seconds produces pretty accurate GPS trace (To record where I've been) but it depends if you are surrounded by buildings or lots of trees, which would prevent your device from reading the satellites and getting an accurate device.
Overall, I'd advise you to experiment, 2-3 times for an hour or so for each setting in endomondo (the battery-saver) and non-battery saver and see what's the difference. Don't use airplane mode, you won't be able to get an accurate GPS measurement.
Thanks!!!!!!!
Will try what you suggested.
Sent from my Galaxy Nexus
Actually, it's not. Turning on airplane mode leaves GPS on, at least on a stock Galaxy Nexus. I just tested this. Makes sense, since a GPS receiver does not transmit.
Takes longer to get a position fix, though, without AGPS. Accuracy seems unaffected, though I haven't tested that thoroughly. Just give it a minute or two to lock on to all the satellites.
Also, you can turn back on Wifi in airplane mode as well. Not really relevant here, though.
If it takes time to catch the satelites its a bit risky to lose gps once I will step into gondola to go up the mountain.
Just tested and it really took time to lock on sats without AGPS
Sent from my Galaxy Nexus

[Q] Moto 360 randomly waking up, destroying battery

Hey all, so I'm having a very annoying and strange issue: My Moto 360 will wake up (i.e. screen turns on) randomly and without reason, ranging from within seconds of each wake to minutes, but it absolutely kills the battery (I can't make it more than 10-12 hours with absolute minimal usage). This is with tilt to wake off, theater mode on, all possible apps except the Android Wear app uninstalled. and the watch sitting completely still on a table. It was happening with Android 5.1 and 5.1.1 on my Nexus 6, and is still happening with the recent 5.1.1 Android Wear update.
The only way to "fix" the waking up issue is if I turn on airplane mode on my phone, which obviously disconnects the watch. So clearly my Nexus 6 is waking up the watch remotely, be it through the AW app or through the connection itself somehow. One other note: when I reset the watch and pair it with my 2013 Nexus 7, the issue doesn't occur, so clearly it's not a problem with the watch's hardware or software, but with the way the Nexus 6 communicates with the watch.
Really would appreciate any insight or guidance as to what's going on - I'm truly at a loss, and the only explanation I can possibly come up with is an issue with my phone's internal hardware (maybe something bluetooth-related)? I've even reset my phone on multiple occasions and that won't fix it.
The only other reference on the internet I can find to this issue is here, where this guy seems to be having the same problem, albeit with a different Mororola-produced phone: https://productforums.google.com/forum/#!topic/android-wear/5vB-dKc5IGI.

Seeing equal or better battery life on wifi vs bluetooth

There were lots of comments (and still are) about how wifi is a battery killer on android wear. I'm not seeing this to be the case at all, when it's working like it's supposed to.
Since 5.1.1 my battery use has been around 3% and hour with all features on. Turning off bluetooth on my phone, with a 2/3 wifi signal on the watch, I'm seeing 2.5 to 3%.
Quick drain happens when walking around the edge of bluetooth range, as the watch switches back and forth between bluetooth and wifi. It seems that as long as it's not finding bluetooth, battery use is normal at worst for me.
I know that the moto 360 will switch to a state of only checking for updates occasionally to save battery, but I don't see this happening. Notifications are coming to the phone, and shortly afterward on the watch. I have not seen a time when a notification was delayed more than a few seconds.
The downside to wifi-only use: some apps that communicate with a phone app don't work. My watchmaker face doesn't update the phone battery level. Google voice commands fail too often, maybe half of the time.
I think google should change the frequency of attempting to reestablish bluetooth connection while on wifi.
Has anyone else tried this? Either turn off your phone's bluetooth, or make sure it is well out of range.
I'll give it a go tomorrow at the office and report back.
Sent from my Xperia Z3
Thanks to a heads up by DarkRazorZ, I learned wifi can be turned on in airplane mode. Will be looking to see if this makes any more difference.
Watch maker has been my biggest battery drain. It also makes the drop down menu laggy and impossible to use.
Yeah, I had that problem with watchmaker. I use intelligent and it seems to work well. Other people report facet works too.
I concur. Wi-Fi uses a lot less battery than Bluetooth, with an acceptable lag - 1-2 seconds on notifications. Bluetooth seems like a big battery drain on the phone and on the watch.
Sent from my Xperia Z3+

Watch lags to display watch face when woken up

Since the 1.4 update my watch seems to lag displaying the watch face. It seems to happen more on certain stock faces than others.
I don't use always on mode so normally I would tilt my wrist and the normal face would show straight away. Now I've updated to 1.4 when I tilt my wrist the watch shows the ambient face for a second then the normal face.
I've tried unpairing the watch which now performs a factory restore as of 1.4 but this hasn't resolved the problem.
Has anyone else noticed this? I can get around the lag by having always on mode enabled but I don't know how this effects battery life.
Thanks all.
Sent from my SM-G925F using Tapatalk
I use always on in combination with SWApp Dark app to reduce brightness of ambient screen and getting 2 days out of battery for my usage.
Not a solution to your problem, though.
Yep, same here. It like wakes up in Ambient mode for about 1 to 2 seconds from time to time. Not always and I notice it a mix on some faces more than others.
My daily driver face does not do it but my secondary does it all the time.
This issue is happening to Moto 360 Gen 1 and 2 watches as well. Loads of people are experiencing it, hopefully it'll be fixed soon.

anybody having issues with HRM?

Anybody noticed the little green light on the back of the watch staying on, even when you take it off and pop it in charger?
Tried changing from frequent to never in settings but stayed on.
The only way I got it off was switching off the watch?
well, mine doesnt have green light on, it is on only when measuring heart rate, and even measuring, the green light will only keep blinking rapidly. So i couldn't find a moment where the green light would stay on, like your situation..
EDIT: I think this may be your problem. On your watch, go to Samsung Health app, scroll a little bit down, and click on the Heart Rate, on the right side, you will see 3 vertical dots, click on it. Then, click on the "Gear" icon to go to Heart Rate Settings. Change it to Frequent or Never.
I think you may had the Heart Rate Monitor set to Always measure, which is why the green light keep lighting up as it was measuring your heart rate every second.
DrViruser said:
well, mine doesnt have green light on, it is on only when measuring heart rate, and even measuring, the green light will only keep blinking rapidly. So i couldn't find a moment where the green light would stay on, like your situation..
EDIT: I think this may be your problem. On your watch, go to Samsung Health app, scroll a little bit down, and click on the Heart Rate, on the right side, you will see 3 vertical dots, click on it. Then, click on the "Gear" icon to go to Heart Rate Settings. Change it to Frequent or Never.
I think you may had the Heart Rate Monitor set to Always measure, which is why the green light keep lighting up as it was measuring your heart rate every second.
Click to expand...
Click to collapse
No, as I said - Tried changing from frequent to never in settings but stayed on. Never used always since new.
One correction though, when I say it stays on, I meant it stays on flickering fast as if it's taking a reading.... it's just not on my wrist and won't stop flickering
sorry, I missed out your statement. It could be other apps installed is using your heart rate sensor.. or even watch faces. does resetting your watch to factory help? I guess that is the last resort
Just tried the reset I read about in another thread (after I backed up of course)
Not easy holding down power then multi pressing, pressing the back key to select reset from miniscule letter choices.
Anyway it seemed to reset, but not sure if it was the right one!
Didn't realise Samsung pay loses all your cards even with backup and restore. Today's steps also gone, all it 'knows' is my target
I'll report back if it works.
I am having the same issue and I have it set to never. I know it turns on for sleep monitoring but it seems to be on all night. I wonder if the last update messed with it.
I have this problem too after updating to the latest tizen 4.0.0.1 , mine is 42mm.
Whenever the HRM breaks, the altimeter and barometer breaks too.
Reset from settings menu or doing hard reset with button will not fix this issue, but sometimes it fixed itself without me doing anything.
Only god knows what happen with this "perfect" tizen.
I tried a factory reset that didn't help at all. I then went into Best Buy and got a replacement watch because I have the protection plan and the watch did the same thing last night. I'm beginning to think it may be a glitch in the S Health app and not the watch
I think I figured out the issue for me. I noticed that in S Health on the watch, if you have REM sleep monitoring turned on the HRM has to be on too . There is actually a message to that effect on that setting. Sure enough, turned off REM sleep setting last night, no green light all night long.
Further update, if I turn off the REM sleep feature, it records me as restless all night - - no recorded sleep time
Faye Reagan said:
I have this problem too after updating to the latest tizen 4.0.0.1 , mine is 42mm.
Whenever the HRM breaks, the altimeter and barometer breaks too.
Reset from settings menu or doing hard reset with button will not fix this issue, but sometimes it fixed itself without me doing anything.
Only god knows what happen with this "perfect" tizen.
Click to expand...
Click to collapse
i am not experiencing issue with HRM but with having huge issues with altimeter - when running for an hour i am getting -500m or so indications. seems watch does not like sweat and humidity
masi0 said:
i am not experiencing issue with HRM but with having huge issues with altimeter - when running for an hour i am getting -500m or so indications. seems watch does not like sweat and humidity
Click to expand...
Click to collapse
I got mine RMAed, got the whole motherboard replaced and every single sensor works well with tizen 4.0.0.1 (for now) :highfive:
really? wow. are you running by any chance and you can share screen from s-health with altitude data?

Categories

Resources