Hello all
I have an issue with the HEART Rate/O2 sensor on my NOTE 4 (5.0.1). When the phone is on the table (screen up) the red light of the sensor is ON and stays on until it drains all the battery out (or the phone is lifted).
Apparently the sensor "senses" the proximity of the table and activates...
I have uninstalled Google Fit. And SHealth is turned OFF.
How can I fix it. Any ideas ?
thank you
I am having the same problem. It will turn off after a while can't figure what timing it is.Now I just tried it, been sitting on my table, and it was off and was not triggering on. As soon as I hit the power button to wake the phone up, LED triggered as soon as I put my finger on it.
Both my apps are not disabled. I did notice if I got my heartrate, which is reading in low 90s, which is way wrong, unless it's elevated because of my issues , it will turn off, until i hit the power button to wake up the phone again.
Other issue I'm having is do not disturb turns itself off after random intervals.
I turned off the smart lock and not seeing the problem. Perhaps smart lock is buggy?
Facing same issue. How do you turn off Smart Lock?
It's under security and it's the last option. Unfortunately for me don't think that's it. I tried S Health before I went to bed looked down at stand and I could see the red glow from the sensor. So I'm leaning towards S Health now. Going to do a system cache wipe again see if that resets it.
There is a bug with Google Fit and our version of 5.0.1. I heard it elsewhere I just confirmed it for myself. Uninstall Google Fit and then reboot your Note 4.
I hope this is fixed soon.
After Factory Reset. The LED light up is gone. =D
I have the same problem. Can't figure out how to solve this yet...
uninstalled google fit, restarted.... problem gone
rahulganatra said:
uninstalled google fit, restarted.... problem gone
Click to expand...
Click to collapse
yup that's the fix!
Anyone figured out the fix for this when google fit isn't installed and is listed as incompatible on the google play store?
Related
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.
I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....
I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.
I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.
I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.
thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings
taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control
bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.
taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app
bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked
Noticed recently in Gsam that my proximity sensor is pretty much on all the time. The sensor itself is working fine, when making calls. I don't use it for any gestures (have all the stuff turned off besides knock-on). I am on xdabbeb's 3.1.0 and smart cover option is removed from it. Even before, on micromod's extreme 1.1 I noticed this but disregard it. All I could find was that the viber could be an issue, tried uninstallin it, didn't help. As I said, sensor works just fine with phone calls and it's not covered, dirty or anything. How could I locate whatccould be triggering it? Going through all the apps is kinda waste of time, probably most of them are not even using it. Gsam always shows like the system is using it. There are no wakelocks to go with it, the phone sleeps just fine. All the other sensors are acting normal. I wish someone could help me figuring this one out because I don't think this is normal. Maybe app or lollipop related? Maybe rom? How to get a log or something to see what triggers it when I turn of the screen. Btw, it happens only when the screen is off.
Update
I think I figured out what causes this (but not why). If anyone else is having this issue, this might help. I know sensor doesn't use as much battery, but still. Why it should be working when not in use.
So apparently, proximity sensor in Gsam shows sensor working when phone is idle and the phone is placed with it's rear cover down. When you place your phone screen down, thus making your sensor covered, there is no proximity sensor battery usage registered in Gsam.
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Devany said:
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Click to expand...
Click to collapse
Disable finger print lock.
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Devany said:
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Click to expand...
Click to collapse
Glad your issue resolved.
Hi folks,
Just recently I have noticed that the screen is staying awake on my Nexus 6P. My phone is sat on my desk in front of me now and hasn't been touched for 5 minutes and the screen is still on. I have the screen timeout set to 15s so it should be long since off by now.
Does anyone know what the fix might be for this or how to diagnose the cause?
Thanks
gk141054 said:
Hi folks,
Just recently I have noticed that the screen is staying awake on my Nexus 6P. My phone is sat on my desk in front of me now and hasn't been touched for 5 minutes and the screen is still on. I have the screen timeout set to 15s so it should be long since off by now.
Does anyone know what the fix might be for this or how to diagnose the cause?
Thanks
Click to expand...
Click to collapse
Did u try to reboot? Did you enable or install anything thatll keep the display on? If enabled the proximity sensor will detect motion and keep the display on.
While charging/not charging or both ?
therock3181 said:
While charging/not charging or both ?
Click to expand...
Click to collapse
Both.
KLit75 said:
Did u try to reboot? Did you enable or install anything thatll keep the display on? If enabled the proximity sensor will detect motion and keep the display on.
Click to expand...
Click to collapse
Yes, tried a reboot but still happening.
Not enabled anything purposefully but i'm always installing apps although not necessarily anything that should keep the display on. I was hoping there might be an app / menu that could tell me what app was keeping the screen on.
RE: proximity sensor - the screen stays on even when its laid face up on my desk with nothing near it, so can't see it being that.
gk141054 said:
Yes, tried a reboot but still happening.
Not enabled anything purposefully but i'm always installing apps although not necessarily anything that should keep the display on. I was hoping there might be an app / menu that could tell me what app was keeping the screen on.
RE: proximity sensor - the screen stays on even when its laid face up on my desk with nothing near it, so can't see it being that.
Click to expand...
Click to collapse
Boot into safe mode and see if it's still doing it. If not, then it's an app that is keeping it awake.
Thanks for the help guys.
I installed Wakelock Detector last night and instantly identified a rogue app - an IP Camera app I was using - that was keeping the screen on. Uninstalled and all fine now.
Cheers again.