Hey, so since I updated to lollipop, my heart rate sensor now activates every time I put my finger over it. I don't ever use the sensor, but I'm sure it drains some battery life. Is there a way to disable it so this doesn't happen? Is there an app I can disable or a setting I can change? Thanks!
My phone is not rooted.
Sent from my SM-G900V using XDA Free mobile app
Root and remove shealth
The way to stop it not lighting up when you put your finger on it is to factory reset your phone. This is what worked for me, but there might be an easier way.
kane3262 said:
Hey, so since I updated to lollipop, my heart rate sensor now activates every time I put my finger over it. I don't ever use the sensor, but I'm sure it drains some battery life. Is there a way to disable it so this doesn't happen? Is there an app I can disable or a setting I can change? Thanks!
My phone is not rooted.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I disabled SHealth in the App Manager and it seems to have stopped.
Rooting is unfortunately not an option, or I would definitely do that.
After switching to lollipop I had to factory reset it since I had issues with Google play services. I would rather not have to do that again if I can avoid it.
I have S Health disabled, but it doesn't seem to make any difference.
Any other ideas?
Sent from my SM-G900V using XDA Free mobile app
Related
Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.
It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.
So the knock on feature is supposed to be more reliable if I do this?
in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.
Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app
Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....
Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks
I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app
I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4
Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.
jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.
Long story short, my gps just kept coming on by itself even after turning it off multiple times. Even after rooting, installing twrp and flashing Clean Rom 1.1 (THANKS SCOTT) it was still there. Looks like it was the carrier IQ causing the issue. I've done these three steps and haven't seen it since. Step 1: Settings>Location access> check 'Wi-Fi & Mobile network location' then uncheck 'GPS Satellite'. Step 2: On your device go to Settings>apps>runnings>Android System> IQServices> Stop. Step 3: Download 'Disable Services' app, open the app and go to android system the uncheck IQServices. That should solve the problem, also I use Wakelock and Greenify. Wakelock allows me to see what apps run while my phone is suppose to be idle and Greenify lets me put apps in hibernation so they wont do anything or process anything unless I actually open the app. I have an ATT G2 by the way..
Do you have any issues with knock on with greenify?
Sent from my LG-D800 using Tapatalk 4
Nope works perfectly fine for me.
joshuadjohnson22 said:
Do you have any issues with knock on with greenify?
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
joshuadjohnson22 said:
Do you have any issues with knock on with greenify?
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
There was someone talking about how greenify broke knock on, but it ended up he just had a craptastic screen protector out on it. After he took it off it was fine.
Sent from my LG-D800 using Tapatalk 2
Im using greenify and knock on works as it should
Sent from my LG-D802 using xda app-developers app
Alright. I'm getting horrible battery life. Do you guys have any tips? Even after a data wipe its still bad. And tips specifics to this phone or general ones? Thanks
Sent from my SM-N900V using xda app-developers app
Are you in an area with poor reception?
You can try turning GPS and WiFi off when not in use.
You can also root your phone and feeeze/remove bloatware.
Sent from my SM-N900V using Tapatalk
Get wake lock detector and you can find what is draining your battery
Sent from my SM-N900V using xda app-developers app
Well I had good service but had to wipe it and now it seems like my service is terrible and it drops all the time
Sent from my SM-N900V using xda app-developers app
XzxBATTxzX said:
Well I had good service but had to wipe it and now it seems like my service is terrible and it drops all the time
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I had the same issues after my update. I then went and froze mobeam, all Knox services, enterprise.knox, knoxs.eventmanager, and a Security wipe apk. Let my note drain all the way until it powered down. Let it charge full cycle while turned off. So far work 1hr and 45 mins of on screen on time I'm down 15%. I feel like that's decent. Been on xda app pretty heavy and 2 different games straight with no screen timeouts
XzxBATTxzX said:
Alright. I'm getting horrible battery life. Do you guys have any tips? Even after a data wipe its still bad. And tips specifics to this phone or general ones? Thanks
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Best tip I can give in general, whether you're experiencing bad battery life or not, is to learn how to bring down the Google based wakelocks across play store, youtube, account sync, maps, hangouts/talk etc
So how does one do this? First, do the obvious by going into each Google app - Menu key - settings - and untick things such as annoymous usage data, google mob ads etc. Delete apps you don't use if you're rooted too.
Disable Account Sync altogether if you can, location services in gps settings, bluetooth, nfc
More advanced things you can do is learn about "wakelocks" here: http://forum.xda-developers.com/showthread.php?t=1827676
MicheleJ said:
I had the same issues after my update. I then went and froze mobeam, all Knox services, enterprise.knox, knoxs.eventmanager, and a Security wipe apk. Let my note drain all the way until it powered down. Let it charge full cycle while turned off. So far work 1hr and 45 mins of on screen on time I'm down 15%. I feel like that's decent. Been on xda app pretty heavy and 2 different games straight with no screen timeouts
Click to expand...
Click to collapse
thanks, i have 30min of screen time and down 15%
In the latest update of S healh there's a new stress level indicator, here in Canada even with the latest update i can't find it in S health... The change log says available in certain countries... I guess Canada is not one of them. Is there a way to still get the feature working ?
Thank you
Sent from my SM-G900W8 using Tapatalk
I'm in the same boat. Did a tonne of research on the Internet, only to find mildly constructive suggestions such as "reboot your device".
So, like a self-respecting sheep I rebooted and rebooted till my reboot finger fell off and I no longer can reboot.
Since I lost a finger, I was forced to type this with my ear.
Still missing the stress sensor feature on S Health, Rogers SM- G900W8
What versions are your S Health apps? Mine is version 3.2.0.0003 and has the stress level module.
I have the same version and dont have the stress level indicator...
Sent from my SM-G900W8 using Tapatalk
V3.2.0.0003 in Canada doesn't have stress sensor. What kind of devilish taunt is this ?
Sent from my SM-G900W8 using Tapatalk
I have 3.2.0.0003 in South Africa with the stress level module. It appears to just measure your heart rate for a bit longer that normal. Maybe it picks up irregular beats?
Sent from my SM-G900F using Tapatalk
Strange. I'm on the Bell network, running AllianceROM 3.1 and I have the stress level indicator.
Sent from my GT-N5100 using XDA Premium 4 mobile app
drezman said:
Strange. I'm on the Bell network, running AllianceROM 3.1 and I have the stress level indicator.
Sent from my GT-N5100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a feeling that it is because you are running a custom ROM which has disabled country-wise restrictions.
Or maybe one of the Samsung execs got hit by a hockey puck covered in maple syrup and thus now they hate us
Another question about S Health, but slightly off topic..
Has anyone been able to get the Runkeeper app to sync with S Health? In settings I have the sync option turned on, but it doesn't seem to carry over any information, which is extremely frustrating.
I use runkeeper to track my gym training as well as other options that S Health doesn't support (Rowing, Stair climbing, skating, etc) but even with the sync option turned on, nothing that I've tracked in Runkeeper shows up in S Health.
Any info would be great..
Hello is anyone else getting this wake loc it's chewing thru my battery and keeping my phone from sleeping..
Sent from my Nexus 4 using XDA Free mobile app
WelfareBaby said:
Hello is anyone else getting this wake loc it's chewing thru my battery and keeping my phone from sleeping..
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Try googling the wakelock
I'd suggest running a nadroid, then clean flashing your phone to check for wakelocks. Then add your apps back and keep checking.
User-installed apps are responsible for virtually all wakelocks (theoretically a badly built ROM too, but that's unlikely in practice, if you're using a popular one)
It could well be something low-level like Viper4Android, though it does depend on what ROM you're using, and what apps you've installed/installed recently.