Related
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
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
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
Anyone else having trouble with Double Tap to Wake?
Mine will work but I have to tap in a very specific way, and even then I only get success 50% of the time. On my Z3 compact it worked flawlessly regardless of how I tapped.
I flashed to UK firmware so maybe that is an issue? I only used the original US firmware for 5 min before flashing to UK so I never tried Double Tap to Wake before the flash.
I just tested it and mine works fine. Fast double tap or slower double tap, it works for me.
It seems to only work well for me if the screen was already on shortly before trying it.
Ok, thanks for checking. I ended up returning my phone
I own the Verizon variant of the V20. I'm coming from a rooted Samsung Galaxy S5 in which I used Tasker to do a lot of things that are now (allegedly) handled natively in the V20. I've been experimenting with and researching Smart Lock and have had no success.
Thanks to Tasker, I'm used to NOT having to unlock my phone, as long as I'm connected to my WiFi, and having it automatically lock as soon as I'm out of range of my home WiFi. Smart Lock looked like it was going to be a decent replacement for this, as it could be configured based on your location, facial recognition, connection to a trusted device, etc.
However, I'm finding that Smart Lock does not work. At all. None of the options will unlock the phone. I'd continue to use my Tasker tasks and call it a day, but unfortunately, in order to unlock the phone, Secure Settings requires root in order to accomplish this.
I want my phone to be secure as I would someday like to start using Android Pay (not activated at this time). However, I don't want to have to type in my PIN when I'm at home. So, for now, as far as security goes, it's pretty much all or nothing.
I've tried various substitute apps from the Play Store that look at WiFi to unlock the phone, but they don't work, either.
Has anyone else run into this? Were you able to overcome it? If so, how did you do it?
Another oddity I noticed is that no matter what locking method I use to lock my V20, when I unlock the device, I must first swipe the screen before it will bring me to the unlock method I selected. This is my first LG phone. Is this typical behavior for these devices?
Smartlock works for me. I have the Sprint version. When I connect to my home wifi I do have to enter my password once. After that, I only have to enter the password after 4 hours of inactivity.
TVThemeGuy said:
I own the Verizon variant of the V20. I'm coming from a rooted Samsung Galaxy S5 in which I used Tasker to do a lot of things that are now (allegedly) handled natively in the V20. I've been experimenting with and researching Smart Lock and have had no success.
Thanks to Tasker, I'm used to NOT having to unlock my phone, as long as I'm connected to my WiFi, and having it automatically lock as soon as I'm out of range of my home WiFi. Smart Lock looked like it was going to be a decent replacement for this, as it could be configured based on your location, facial recognition, connection to a trusted device, etc.
However, I'm finding that Smart Lock does not work. At all. None of the options will unlock the phone. I'd continue to use my Tasker tasks and call it a day, but unfortunately, in order to unlock the phone, Secure Settings requires root in order to accomplish this.
I want my phone to be secure as I would someday like to start using Android Pay (not activated at this time). However, I don't want to have to type in my PIN when I'm at home. So, for now, as far as security goes, it's pretty much all or nothing.
I've tried various substitute apps from the Play Store that look at WiFi to unlock the phone, but they don't work, either.
Has anyone else run into this? Were you able to overcome it? If so, how did you do it?
Another oddity I noticed is that no matter what locking method I use to lock my V20, when I unlock the device, I must first swipe the screen before it will bring me to the unlock method I selected. This is my first LG phone. Is this typical behavior for these devices?
Click to expand...
Click to collapse
I have the Verizon variant as well, they disabled most of the smart lock features that you are looking for. It works for me because I have it set to unlock when connected to my smart watch. But it is still aggravating they Verizon does this stuff.
Sent from my VS995 using XDA Labs
Thanks for the responses, guys! Looks like I've been able to get it working... to a point. I have Nova Launcher installed and have defined the double tap gesture to turn off the screen. Discovered that on my LG V20 with Nougat, this doesn't just turn off the screen. It locks it. If I turn off the screen using the power button, it works as it should.
This does not happen on my wife's LG V10 with Lollipop. On that device, the same software and gesture will turn off the screen, but it won't lock it.
In either case, one must still swipe to unlock the display, regardless of whether or not it's locked. Research indicates this is something Google implemented with version 5 of Android (until very recently, I was using 4.4).
So I've written to the developer of Nova Launcher to ask what, if anything, can be done. I'll post the results here when I have them.
TVThemeGuy said:
Thanks for the responses, guys! Looks like I've been able to get it working... to a point. I have Nova Launcher installed and have defined the double tap gesture to turn off the screen. Discovered that on my LG V20 with Nougat, this doesn't just turn off the screen. It locks it. If I turn off the screen using the power button, it works as it should.
This does not happen on my wife's LG V10 with Lollipop. On that device, the same software and gesture will turn off the screen, but it won't lock it.
In either case, one must still swipe to unlock the display, regardless of whether or not it's locked. Research indicates this is something Google implemented with version 5 of Android (until very recently, I was using 4.4).
So I've written to the developer of Nova Launcher to ask what, if anything, can be done. I'll post the results here when I have them.
Click to expand...
Click to collapse
Yes, I too grace to double tap to turn the screen on them swipe to unlock.
Sent from my LG-LS997 using XDA-Developers mobile app
I heard from the developer of Nova Launcher. Here's what he had to say:
...
Unfortunately this is a known issue in which there is a pop-up window within Nova that tells you about this and that there is a work around if you are rooted. Unfortunately there's no native work around if you're not rooted, however, you can go to the Google Play Store and purchase Screen Lock Pro (this app is not ours) and you can use it as a work around for this issue as well.
If you join the beta program, then follow these steps.
To get Screen Lock to appear in Nova Settings perform the following steps.
1) Have a device with a fingerprint scanner.
2) Set your security to use a PIN to unlock your device.
3) Set Double Tap gesture to Screen Lock.
4) Double Tap to turn off the device.
5) A popup window will appear asking you to choose one of two options.
6) Screen Lock should then show up within Nova Settings after that.
...
I opted to purchase Screen Lock Pro and configure Nova Launcher to launch the shortcut for that app when the screen is double-tapped.
All in all, this method works. There just one caveat: When you double tap and the shortcut is launched, your screen AND the second screen will both go blank for about 30 seconds (not that although there's no picture, the backlight remains on during this time). After that time, the second screen will come back. If you need to unlock your device prior to that, it will be necessary for you to press the power button twice. The first time locks the screen (evidently because Screen Lock Pro only darkens your screen for the first 30 seconds, and THEN locks it), the second time will turn the screen back on. Pressing once will display your second screen. There does not seem to be an adjustment to shorten this time interval.
Also, it's important to turn on Smart Lock and Fingerprint Sensor in the settings of Screen Lock Pro.
I've been using this as described and I can live with it.
All this being said, I'm going to request a feature enhancement from the developer of Screen Lock Pro to see if we can get that interval to be adjustable.
Oh, and I'm using my fingerprint for security, and I've found that unlocking the phone with my fingerprint means I don't have to swipe after unlocking. After several days, I've gotten used to this method and it works well for me, even away from home.
I hope this helps.