I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
fhblake04 said:
I was wondering if anyone else was experiencing KnockON inconsistencies with their G2. Turning off always works properly. But if the phone has been idle long, it hardly will ever turn on the first one, two, or even three times I knock on it. Sometimes I have to tap it rather hard to function. I've tried different locations on the screen, as well as the center where the phone actually instructs you to do so. Then I tried faster and slowerand it makes no difference. The tips of my fingers are hurting now lol.
Thanks!
Click to expand...
Click to collapse
Surprised you're the first to bring this up, lol! Been watching this device closely on on youtube reviews on this device you can see it right infront of your eyes. Doesn't ALWAYS wake on double tap but does ALWAYS turn off, weird. Idk what to tell ya but yes it isn't just you...
Are you using the stock launcher?
I switched to Nova and noticed its very finicky for me ever since I stopped using the stock launcher.
Still on stock launcher.
I just tap it 4 times when turning on, no big deal.
The only time it fails for me is if I tap too softly. I notice that when turning it on, it does take two distinct forceful taps. It seems to register anything else as a touch. So, while I think it could be better, I don't see it as inconsistent. If it was too sensitive, it might end up turning on in your pocket.
I think it has to do with the motion sensor in the phone. Mine works fine if I just tap it twice while it's in a steady position (even in my hand), but when I'm riding my bicycle I can't get it to tap "on" most of the time (unless I stop). Tap off works much more reliably.
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Tapping near top of screen seems to work much better.
geoff5093 said:
I just tap it 4 times when turning on, no big deal.
Click to expand...
Click to collapse
Exactly.
Can't have both battery life and also expect the Knock feature not to go to deep sleep. I prefer to eat my cake.
Also, I like that it does not accidentally turn in my pocket or when gripping the screen in my hands, etc.
The Korean version has gotten a few updates to make KnockOn smoother, so you might not have that update yet.
Well, I have a VZW version so updates will not be plentiful lol. Knocking on it several times, rather than twice seems to work better. Thank you guys for your suggestions.
jayochs said:
i'm pretty sure there's a deep sleep issue, but that's to be expected..once the process that controls knockon goes to a deep sleep, of course it won't work right away.
Click to expand...
Click to collapse
Maybe we should shake it a few times and then double-tap the screen. It would be like a Moto X/LG G2 hybrid!
I’m doing a study right now with this feature by recording the time and results. So far 3 quick knocks resulted in successful power ups 100% of the time (7 for 7). When doing 2 knocks (prior to the study) it was intermittent to the point of driving me crazy.
Come to think about it when you knock on someone’s door do you knock 3 times or 2? I always knock 3 times but the video reviews of this feature messed my thought process up with 2. First world problems I guess. LOL
I will report back with my results tonight.
BaronInkjet said:
Tapping near top of screen seems to work much better.
Click to expand...
Click to collapse
Same for me. It says you need to either tap in the middle or top of screen. Anywhere else doesn't work as well.
Sent from my LG-D801 using xda app-developers app
Seems to work best if you tap where the lock screen widgets are located -- top center, but not at very top.
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
I have an explanation. I think this happens because when the phones asleep (screen and touch panel is off), knockon uses the motion of the phone, read by the accelerometer, to recognize that two-tap pattern and subsequently turn on.
When the phone and screen are on though, the mechanism happens by direct touch input and is much more reliable, so it should happen every time.
This would explain why in moving situations like riding a bike, or when I was trying to turn it on while it was on the bed, which probably absorbed the motion from the taps it doesn't work as well.
I did hear that the Korean version got a firmware update that helped, though who knows when we'll see that in America.
razball said:
Anyone having a problem with the phone going unto deep sleep and then just shutting down?
Sent from my LG-D801 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a defective phone.
Factory reset time!
Good to know dam lol that's annoying well I guess I'll wait till it happens again to be really sure
Sent from my LG-D801 using Tapatalk 2
Related
I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
C3LL0PHANE said:
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
Click to expand...
Click to collapse
Basic stuff for an android phone. High memory usage is nothing to worry about, it's actually almost the opposite, more the merrier.
Hmm I think I've experienced most of those things. They're odd occurances. But be glad they're software issues, because software can be changed/fixed!
As for rooting vs jailbreaking an iphone... the thing is, since iPhone is locked down so much, jailbreaking an iPhone can make a big difference than a stock iPhone. Rooted android allows access to hidden system files, so can allow for more tweaking, but an unrooted Android phone already does so much, as opposed to an unjailbroken iPhone. Rooted android can by far do way more than a jailbroken iPhone. And even in some ways, an unrooted Android phone can do more than a jailbroken iPhone as well.
PS: can you share the numbers of some of you girlfriends? maybe I can help them out with their technical issues
C3LL0PHANE said:
I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
Click to expand...
Click to collapse
1) I've noticed this. The pattern I notice is that this only happens when you're receiving text and typing. Since in the options for the keyboard you can enable vibration when u type I believe this is the problem. I haven't tested it but the way the phone seems to respond, it seems to be so. It seems to be able to only output one vibration feedback at a time. So in effect it delays those linked to your typing until the vibration for receiving text has ended. I could be wrong though.
2) It is most probably being used by background running processes. Typically you only really close a process by pushing the back button until it closes. If you continually open new tasks after pushing the center button you're essentially putting the current program in the background.
3)What you can do is enable a simple swipe pattern lock to help this, but even so you run the risk of locking your phone if you "guess" the pattern lock too many times. So I would recommend you buying a case for it if you don't have one. I have not had any problem like this and I use a case.
4)It sounds like your proximity sensor isn't working or isn't being properly activated by your cheek. What you can do is go to a mirror and call someone, while speaking to them shift the phone a little bit at a time until you see the screen black. This indicates the proximity sensor has detected your face being close to the phone. While you are at it you can also slide the phone a bit to get peak volume with your phone. From what I can see the in-call speaker is very directional.
EDIT: Yea you can consider rooting to be the android equivalent to jail breaking. Considering you're asking that I am guessing you have not rooted your phone yet. If you don't have the latest firmware it might be a good idea since it fixes some little oddities on the x10 as well as offering battery and speed improvements.
There's an easier way to test the proximity sensor:
While in lockscreen, press: Menu Back Back Menu Back Menu Menu Back
This opens the service menu. Go to Service Tests-Proximity Switch.
Now just move a finger over the sensor to test. It also gives you a sound so you can also try holding it to your cheek!
Hope that helps!
@beno1 cooooolll thanks man.
Sent from my X10a using XDA App
So I went into the testing part and checked the proximity switch and it says it is off. That's not what I want now is it? I couldn't figure out how to get it on.
As for pressing the Home button instead of Back.. wouldn't Advanced Task Killer close those applications anyways?
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Tri3Dent said:
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Click to expand...
Click to collapse
I tried that and it beeps, but goes back to off
C3LL0PHANE said:
I tried that and it beeps, but goes back to off
Click to expand...
Click to collapse
That's what it should do! It will only go to on when it is covered then as soon as you uncover it then it swiches back to off.
This is as it should be in the service test. It is working.
Ok, this is getting old. I moved to seattle. I get here off the train and my phone's screen freezes. im talking game over freezes. I get a replacement. If i am inside, i am fine. The minute i walk outside, bam! Frozen screen. Once i walk inside, im fine. If i boot to windows, i don't have any issue. I have had screen rotation turned off. Is there ANYTHING i am missing? I would like to use my phone. I tried a lot of builds off of here.
same here indoors i have no problems but as soon as i step outside everything goes to ****.
Could it be because you r walking outside? If so,then the accelerometer might have been overwhelmed with your body movement. Happens to me too, it improves by using thephone stand still.
One option is to disable screen auto rotation, that would help alot.
fakepooh said:
Could it be because you r walking outside? If so,then the accelerometer might have been overwhelmed with your body movement. Happens to me too, it improves by using thephone stand still.
One option is to disable screen auto rotation, that would help alot.
Click to expand...
Click to collapse
Today was dry, a little chilly, and sunny. No issue. The slightest bit of moisture in the air and it goes to ****. If i am walking home from the bar, and it starts to get misty out or rains, its over. done. And i know for sure how to kill the screen anytime outside. Turn on the gps. Once it locks, on EVERY build i used, it locks it. You have to hit power, wait for it to eventually turn off, and its unlocked again, for a few seconds. (Hopefully enough to get out of whatever app your using that uses gps)
I love android, and i am dealing with it, but its very annoying and i do hope that one day it will get fixed, and it will i know it.
djdanska said:
Today was dry, a little chilly, and sunny. No issue. The slightest bit of moisture in the air and it goes to ****. If i am walking home from the bar, and it starts to get misty out or rains, its over. done. And i know for sure how to kill the screen anytime outside. Turn on the gps. Once it locks, on EVERY build i used, it locks it. You have to hit power, wait for it to eventually turn off, and its unlocked again, for a few seconds. (Hopefully enough to get out of whatever app your using that uses gps)
I love android, and i am dealing with it, but its very annoying and i do hope that one day it will get fixed, and it will i know it.
Click to expand...
Click to collapse
I do not have any of these issues. What exactly is your setup? Phone model, version, winmo rom, radio, and android version. Memory card class, mfg, and capacity.
I sometimes get this if the light sensor is on (auto brightness), turning it off fixes it
I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?
Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.
Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.
As the poster above said, turn off automatic brightness and see if that fixes it.
Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?
Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl
new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.
I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.
I am experiencing a similar issue. Does setting a manual brightness fix the issue?
It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted
Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Well what case have you got?
I have no such problem on my Portenzo hardback case.
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Click to expand...
Click to collapse
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
sfhub said:
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
Click to expand...
Click to collapse
Same. WiFi on or off seems to work okay... WiFi on and searching is always touch and go for me. Hopefully it can be fixed pretty easily in software down the road... before it starts to actually bother me.
Noticed this on mine as well. Different than my 2012 model but not a real problem
Sent from my Nexus 7 using Tapatalk 4
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
WilliamG said:
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
Click to expand...
Click to collapse
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
negroplasty said:
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
Click to expand...
Click to collapse
Yeah. All I know is I have the wifi set to not run during sleep, and all seems fine, - just that it takes the Nexus a good number of seconds to come alive after it's been asleep a while.
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
RKight said:
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Same for me.
I noticed if WIFI is ON, or device is connecting to power/USB. The wake will works perfectly and instantly.
But if WIFI is OFF or not USB connection, the wake is not function after closed the cover for few seconds.
WilliamG said:
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Click to expand...
Click to collapse
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
hyperxguy said:
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
Click to expand...
Click to collapse
That's impressive! I'm sure it's a bug that affects all Nexus 7 2013 devices, but it's still lame.
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
Are we sure this is actually an issue? Based on the threads I'm reading about this, the cover only seems to wake the screen when you open it while things are running that would normally keep the N7 out of deep sleep. Isn't the tablet being able to enter deep sleep mode successfully a good thing?
The reason I say this is because a lot of you, including myself are reporting that when Wifi is off, and the tablet is unplugged, opening the cover won't wake the screen if it's been closed for a long time but it will after just short periods. This indicates deep sleep being entered successfully. If the cover is able to wake the screen in that mode, I'd be more worried that deep sleep mode isn't being entered successfully.
I guess the main question is: Is 4.3 along with the Nexus 7 hardware actually designed to only be able to be powered on by the power button itself during deep sleep? Do not services have to be running in the background constantly in order to allow something else to wake the screen? For example, in order for one of those 3rd party screen apps that use either proximity sensors, or light sensors or position sensors (shake) in order to wake your screen to work, all of the better ones I've seen not only require administrator permission, but also running background services.
In other words, they use the hardware sensors inside the Nexus 7 to wake the screen but also require some kind of additional resources running in the background. Which means resources being consumed. Smart covers also use hardware inside the N7 to wake the screen but without an app consuming resources in the background to so do. Which means NO resources consuming battery or memory, which is a good thing.
I'm not so sure I even WANT this fixed if it's going to mean my tablet has to have stuff running in the background in order for it to work. If Google can make it so that's not the case, then I have no problem with it. I could be completely wrong as well, I'm just speculating so if Google says it is actually a software bug then I guess I am.
omnius1 said:
Do not services have to be running in the background constantly in order to allow something else to wake the screen?
Click to expand...
Click to collapse
I guess that depends on the magnetometer chip they are using. If it can generate an async interrupt on a change in magnetic field, then that is one thing, if it has to be polled, that's something else. I don't find it too great a hardship to occasionally have to press the button, so if it is doing this to save more power, that suits me.
I think this thread is about all the "odd" things happening, specifically to the some 2013 Nexus 7 (some people don't have this problem).
I also have the 2012 N7 and the Nook HD+ with smart covers, both are running JB4.3.
Both can go into deep sleep and whatever (wifi on/off, things running or not) and will wake up in an instant as normal.
This is not normal !!
By the way, I received the replacement and similar results. I didn't expect it to fix the issue anyway as I think this is similar
to the tough issue with some N7s (I don't have this issue) which is a google problem.
A little off-topic about deep sleep... my Nook HD+ can sleep for a whole day and only take 1% of the battery.. best I've seen.
Edit: just in case somebody thinking about a ROM problem, I've tried multiple ROMs including stock.. all have same issue.
Moko smart cover is the best
It should wake up within a second, at worst, period. Ideally it'll wake up "almost instantaneously". There's something wrong.
I wish the mods would merge these two threads so the nonsense is at least in one place.
Mine sometimes will wake after a delay and will sometimes just sit and do nothing at all until I press the power button. It has turned on after a 30 second delay, after being idle all night, but has also completely failed to turn on after being idle for just five minutes. This thread is definitely aimed toward the odd inconsistences and what I indeed perceive to be a problem.
Sent from my Nexus 7 using xda app-developers app
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