Rather odd, never happened to me with any ROM previously.
Devices is a Korean Note 3, rooted, running the latest X-Note. Pin lock is enabled.
Randomly the screen will turn on, and right to the apps, no lock at all.
I disabled xposed, tasker, anything that might be interfering or have special tweaks that could have a bug. I have wakeup detector installed, keeping an eye on screen wake events. There is nothing suggesting what might be causing the screen on, and the strange part of it all bypassing the lock screen altogether.
I usually just read existing topics to find answers, but this one leaves me confused. Is there another logging solution to find out what is activating the screen and bypassing lock?
wayandrs said:
Rather odd, never happened to me with any ROM previously.
Devices is a Korean Note 3, rooted, running the latest X-Note. Pin lock is enabled.
Randomly the screen will turn on, and right to the apps, no lock at all.
I disabled xposed, tasker, anything that might be interfering or have special tweaks that could have a bug. I have wakeup detector installed, keeping an eye on screen wake events. There is nothing suggesting what might be causing the screen on, and the strange part of it all bypassing the lock screen altogether.
I usually just read existing topics to find answers, but this one leaves me confused. Is there another logging solution to find out what is activating the screen and bypassing lock?
Click to expand...
Click to collapse
After days of messing about, found something that appears to stop it. Revoking admin rights from Greenify. Still works otherwise, as it appears.
Also, eight hour standby time, loosing zero % battery. Amazing xnote + some tweaks.
Related
Well those of you like myself that were having the issues of hitting the power button only to see a black screen, here is all I did and its been working flawless for 24 hours. Turn of the screen lock! I haven't tested other screen locks yet so maybe its just the default one
If this dose not work for you please post.
Trying this myself now. It had previously happened 3 times to me with the default lock screen. If this does work, that sucks cause I really liked the lock screen... Does anyone know if either of the firmware updates addresses this particular issue? I haven't done them yet was waiting for the new root method which was just released yesterday.
maybe that's why i never had that problem... i always had a pin from day1
I am updated to the latest firmware and the issue still existed. Are you running a battery monitor widget?
turning off screen lock didn't do the trick for me
what worked for me is disable wifi before turning the screening off or go into option and change it so that it never disconnect from wifi will fix the issue for me though
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
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
97vulcan said:
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
samwathegreat said:
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
Click to expand...
Click to collapse
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
Ok, that is definitely not normal. Are you BL unlocked, or are you using the Pie root exploit? Or Safestrap?
I would suggest flashing the entire 4.4.2 AT&T SBF file using the manual method as described in the Return to Stock thread:
DO NOT DO THIS IF YOU ARE USING SAFESTRAP
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 AT&T SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
As I seem to be telling people often, the only way to fix a corrupted filesystem (OR modifications made by previous exploits like Pwn/SlapMyMoto and MotoWpNoMo) is to flash the entire SBF file. Performing a "factory reset" cannot repair a damaged filesystem.
Often, it will fix ALL of your problems.
Good Luck
Did you install any apps, that plays with those settings after rooting?
thanks for the replies guys...I don't think so on the apps after root. IIRC, it did this before rooting the phone, so I thought it was a 4.4 issue.
it will unlock to the home page after every call, unless I answer, or ignore the call.
I'm using Xposed with these modules:
App Settings
GravityBox
HideCarrierMotoX
MinMinGuard
SoftkeysFadeMod
Twisty Switch
Xblast Tools
XPrivacy.
Again, I do not have a lock screen..when I try to enable one it does something funky with my electronic buttons, even after reboot. Not sure if it's because of SoftKeysFadeMod, or what..
I'm surprised others have not had this issue.
Thanks for you help.
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
rtm1102 said:
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
Click to expand...
Click to collapse
you pretty much hit it on the head...I was hoping the phone's display would not unlock to my desktop if I miss a call, but rather show the missed call on the active display.
I'm going to enable a security setting, and see if this changes the outcome.
Thanks
After enabling the swipe to unlock, I no longer have an issue with my phone unlocking when I miss a call. That seems to be the solution.
Thanks for your help
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.
Has anyone else had this happen? Happens quite often for me. I'll be playing a game at work, get up to do some work while leaving game open. Come back and unlock the phone and it's on home screen. Does the same thing while listening to Pandora.
I've never noticed that happening to me, I just tried to reproduce it with not luck. How are you unlocking the phone?
Either fingerprint or iris. It does it with both. I don't see it happening when turning phone off and on right away. Phone usually sits a few min before it does it.
jeb192004 said:
Either fingerprint or iris. It does it with both. I don't see it happening when turning phone off and on right away. Phone usually sits a few min before it does it.
Click to expand...
Click to collapse
Battery optimization setting probably. Try disabling optimization for an app that currently does it and see what happens
That didn't help
Couldn't replicate issue either. Let Rayman running and screen went off for about 5 mins. Unlocked with fingerprint and went directly to the game. I had power saving off and performance mode set to optimized.
OP do you also lose your place when it directs you to the home page? Or does it resume when you reopen the app?
It resumes when reopened.
Power saving off and performance mode set to optimized as well.
The one app where it does it almost every time is Star Wars: Galaxy of Hero's. Only other app I notice it once and while is Pandora.
Are you sure you aren't iris unlocking it without knowing you are? Sometimes mine unlocks almost instantly when i press the unlock button. Or when I turn my screen on to check the time.
Is "iris unlock when screen turns on" enabled?
Lock screen & security > iris scanner
I'm sure. Most of the time my phone is face down and I grab it by the side and put finger on scanner. Turned iris scanner off just to be sure and it's still doing it.
Also does it with line messanger...
I have this exact problem as well. Seems to happen rather randomly.
I sometimes see the app actually minimizing to the home screen when I unlock the phone, so it's probably not some background task killing it.
The app is only minimized, not killed.
I have this issue as well.
I think I found the problem. Uninstalled bxActions and as of the past 2 hours the problem is gone.
i have this issue but i don't have bxActions so i don't think that is the problem
Are any of you happening to use the long press home option, the one that bypasses the lock screen? Even though you may not be using the home button maybe the option is still affecting the apps that are open and thinks for some reason you're pushing on the home button.
It might be an app causing it. I still haven't had any issues since I uninstalled bxActions. If you don't have that installed it could be a different app causing it.
I was also having this issue. Stopped bxactions and the issue is gone. Started bxActions back up and issue came back.
Same problem here. On Verizon s8 and no bxaction installed. Very irritating!
Unrelated but another problem is when I change to aggressive wifi/cell handover in developer options it allways defaults back off after a reboot? Any ideas??