Anyone else notice lift to wake sometimes doesn't work? Sometimes it's fine, other times there's a few second delay, other times I can shake the phone after picking it up and nothing then it finally comes on. Googling shows intermittent reports over the last year or two of similar symptoms on the 2 and 2 XL.
Also, double tap sometimes does nothing. Tapping again usually works. Sometimes it works fine several times in a row, then fails again.
Lastly, I have fingerprint lock enabled. If lift to wake works, and double tap gets me to the lock screen sometimes I can swipe up and get the home screen. Other times it forces me to use my fingerprint.
Quite a bit of flakiness in this whole area. Things appear to be working fine once I'm in, but getting there is quite inconsistent.
I did contact support, tried various things they suggested including booting into safe mode, but didn't fix it. They're supposed to get back to me...
samnada said:
Also, double tap sometimes does nothing. Tapping again usually works. Sometimes it works fine several times in a row, then fails again.
Click to expand...
Click to collapse
Definitely noticed this on my 3XL. It's like it doze's a little too hard or something. Usually doesn't react properly after long periods of inactivity. Same with FP on my P3. But sometimes the FP is fine, like you say it's flaky and inconsistent. Maybe something that will be tuned a little better in an update or with a custom kernel in the not to distant future....
Chronzy said:
Definitely noticed this on my 3XL. It's like it doze's a little too hard or something. Usually doesn't react properly after long periods of inactivity. Same with FP on my P3. But sometimes the FP is fine, like you say it's flaky and inconsistent. Maybe something that will be tuned a little better in an update or with a custom kernel in the not to distant future....
Click to expand...
Click to collapse
Couple of things.
I ended up disabling FP and then setting it up again and since then the FP detection has been much more consistent. Maybe sometimes the process for the initial FP scan isn't very good and that might cause the security scans after that to be inconsistent. Just a guess. Anyway, resetting it might help.
Also, the comment I made about sometimes I can just swipe on the lock screen and not have to use FP was due to having "Smart Lock" enabled. It's a bit confusing (at least to me) in the Settings screens. Under Security > Advanced > Trusted Agents > Smart Lock can be turned off. I did that and now it always requires my FP.
One more thing. The swipe on the FP scanner to bring down the notification panel is very flaky for me. Works only about 50% of the time at most. Also went over that with support. Waiting for them to get back to me on that one as well.
samnada said:
Couple of things.
I ended up disabling FP and then setting it up again and since then the FP detection has been much more consistent. Maybe sometimes the process for the initial FP scan isn't very good and that might cause the security scans after that to be inconsistent. Just a guess. Anyway, resetting it might help.
Also, the comment I made about sometimes I can just swipe on the lock screen and not have to use FP was due to having "Smart Lock" enabled. It's a bit confusing (at least to me) in the Settings screens. Under Security > Advanced > Trusted Agents > Smart Lock can be turned off. I did that and now it always requires my FP.
One more thing. The swipe on the FP scanner to bring down the notification panel is very flaky for me. Works only about 50% of the time at most. Also went over that with support. Waiting for them to get back to me on that one as well.
Click to expand...
Click to collapse
Most of the stuff you experienced is standard operation for phone's with Double tap to wake, lift to wake, etc. Those features just kinda go to sleep after a while. And yes, smart lock keeps you logged in during certain situations that you specify. Welcome to Team Pixel!
Don't use a lot of those features, but some OT thoughts..
I think there is some FP lag if you have lift-to-check enabled because it's 'lifting-to-check' while i'm hitting the FP. I disabled lift to check and i'll see if the FP's a little snappier.
Always helps to redo the FP after you change a case too- I usually do 2x on each index finger.
PuffDaddy_d said:
Most of the stuff you experienced is standard operation for phone's with Double tap to wake, lift to wake, etc. Those features just kinda go to sleep after a while. And yes, smart lock keeps you logged in during certain situations that you specify. Welcome to Team Pixel!
Click to expand...
Click to collapse
Every phone I've had has quirks. It is a bit disappointing a useful feature like lift to wake, especially with no notification LED, has been flaky for so long it's now accepted behavior. I tried a location smart lock feature on my previous Samsung and quickly abandoned it as unreliable as well. What seems odd and a bit confusing is the Smart Lock on/off switch is in a totally different place than where you set up the specific settings, some of which get added by default. Really like the phone, just a bit of acclimation.
Do you have your battery saver on? I found that after I turned off my battery saver it worked
oneeyeddie said:
Do you have your battery saver on? I found that after I turned off my battery saver it worked
Click to expand...
Click to collapse
I had battery saver on. I've turned it off for now to see if that helps and how much extra battery gets used. Thanks for the suggestion.
Update: That didn't take long. Lift to wake is still flaky. Works sometimes, other times not.
I've noticed the same. I use smart lock with a Garmin watch. On my Nexus 6 it always worked, and if I didn't have my watch on, when I swiped the screen it would ask for a PIN. Now, I lift or double tap and sometimes it will then let my swipe the screen, but most often I have to hit the power key. This is not an improvement.
Can't believe no one has figured this out. It has to do with the lock to sleep delay. By default it is set to 5 seconds. So, madly tapping won't work. Go into settings and change the timing. Be amazed.
Related
Is "double tap to wake screen" available for Z2? This post [*1] says it's included in 4.4. My Z2 is with 4.4.2, but I can't find the setting to turn it on.
*1: fonearena.com/blog/97620/hands-on-with-sonys-android-4-4-ui-on-a-xperia-z2-double-tap-to-wake-gestures-and-more.html
khumash said:
Is "double tap to wake screen" available for Z2? This post [*1] says it's included in 4.4. My Z2 is with 4.4.2, but I can't find the setting to turn it on.
*1: fonearena.com/blog/97620/hands-on-with-sonys-android-4-4-ui-on-a-xperia-z2-double-tap-to-wake-gestures-and-more.html
Click to expand...
Click to collapse
Settings -> Display -> Tap to wake up
khumash said:
Is "double tap to wake screen" available for Z2? This post [*1] says it's included in 4.4. My Z2 is with 4.4.2, but I can't find the setting to turn it on.
*1: fonearena.com/blog/97620/hands-on-with-sonys-android-4-4-ui-on-a-xperia-z2-double-tap-to-wake-gestures-and-more.html
Click to expand...
Click to collapse
i find the double tap so frustrating ! i would say 9 times out of ten i cant get the screen to wake using this ! and it don't seem to matter where on the screen i tap or how hard , it just isn't very responsive. i use the button on the side now !
strommy1966 said:
i find the double tap so frustrating ! i would say 9 times out of ten i cant get the screen to wake using this ! and it don't seem to matter where on the screen i tap or how hard , it just isn't very responsive. i use the button on the side now !
Click to expand...
Click to collapse
Same here. Hopefully there will be a customized rom that can configure that double tap sensitivity level. The current range is too narrow, you can't tap too fast or too slow. So I usually just keep tapping 3-5 times until the screen unlocks. I use the button more often too.
Hmm that's weird. It almost always works the first time for me. I don't even tap hard. Do you tap fast enough?
Probably not fast enough. If I hold the phone with just one hand, usually my thumb is not fast enough.
It does not matter how fast or hard you tap the screen. It almost never works here. Can anyone confirm if this can be fixed with a hard reset?
I've just toyed around with this tap to wake and I've noticed some things about how it works.
You have to tap in the same place (you can't tap in corner and then then the other corner) and the distance seems to have only half an finger width margin of erorr, you have to use a small area to tap, so you cant tap with your whole thumb for example, it works best with just a finger tip. It doesn't matter how hard you tap but timing is important and it's roughly the same speed as a typical double click on a mouse (the faster the double tap the better).
Using this method to wake the phone is pretty redundant I think, I prefer to use the power button.
Anyway hope this helps.
Personally I've had no problems with double tap to wake. You just have to remember to tap in exactly the same place, and at a moderate rate. If you tap too fast, it doesn't pick it up.
I do love the feature though. I use it to wake my phone up probably 80% of the time, especially when it's sitting flat on a desk. So much more convenient than hitting the power button.
i tap with my index finger in fairly rapid succession normally in the middle of the screen .. but as i have said before i find it works far less than it should ! if the phone is laying down on a hard surface it will work more often , but if i hold in one hand and tap with the other, it seems to fail .
double tapping
Read most of these replies and i had the same issue regardless if i tap in the same spot, speed etc.
Anyways even though i dont wear gloves, i had this option ticked which affected the sensitivity of the screen. Once i unticked this option, the double tapping works 100% regardless of where on the screen i tap etc. you just need to tap consecutively close not seconds apart and mine never fails.
Hope this helps....
I noticed that also, but the circle that appears when you are close to the screen drives me nuts, so I turned it off. Instead I tap 3 times. That seems to do the trick.
Hi guys! I ran into the same problem , and I hope my post will help someone. You 've probably noticed that a double tap works in virtually 100 % of cases, if the phone is lying on a flat surface and does not move. So the trick is to keep your phone in a stationary while you're tapping . If you have small hands ( like I have ) , I recommend to keep the phone so that the lower left corner of the phone rested in the palm of your hand, and so the phone will not move. Pressing force and velocity values are not actually important. Sorry for my English and I hope somebody will find this information useful
double tap
Quasar83 said:
It does not matter how fast or hard you tap the screen. It almost never works here. Can anyone confirm if this can be fixed with a hard reset?
Click to expand...
Click to collapse
After a week of using it, i had the same problems as you guys.
Now, it's wotking just fine, everytime.
You should get used to how to tap. Not very fast, slowly is better .:good:
It's wotking fine. Don't blaim de phone, it's you to blame
After much reading, it seems that the only known way to toggle Knock On/Off on the Verizon LG G3 is to root.
Because of my work situation and Good For Enterprise, I am unable to root. This has bugged the heck out of me.
I really wish to toggle Knock On/Off as when I'm cleaning the screen, fumbling the phone, etc it likes to wake up. From time to time I would get a stock LG Screen pop up that asked me to toggle this feature. I never did, as I didn't know how to replicate it.
Fast forward to last night. Note: so far I have only gotten this to work with a soft cotton shirt, but was able to replicate it numerous times. I pulled the phone out of my pocket. OCD & tempered glass don't mix. I starting cleaning my screen with my shirt. I had three fingers inside my shirt and start swiping up and down fairly fast with the screen off. Any other time, the screen would wake up, and I would have to manually turn it off to finish cleaning. However, the LG screen popped up asking to turn on/off Knock On. I left it alone, and tried this numerous times with success. I actually got a bit brazen and turned it off. I can tell you it indeed disables knock on as well as knocking off with the status bar (I use Nova). I can verify it works with the screen on as well, so it must have to do with swiping on the status bar.
I tried again this morning with a sweater and have yet to replicate it. If I figure anything more out, I will update this post, but props to Verizon for hiding stock features from us.
Erik
Mine doesn't turn on when I clean it... You must be doing it wrong
Chilidog said:
Mine doesn't turn on when I clean it... You must be doing it wrong
Click to expand...
Click to collapse
Mine turns on every time I wipe it - be it with my T-shirt or actually cleaning it using the wipe and spray I use for my glasses. So it appears the OP isn't doing it wrong. But I'm sure he values you contribution to the topic.
Chilidog said:
Mine doesn't turn on when I clean it... You must be doing it wrong
Click to expand...
Click to collapse
I wasn't aware there was a defined right and wrong way to use a piece of cloth to clean a smartphone screen. Is there any way you could post up a video on YouTube to share? Come to think of it, maybe the feature was always there, VZW just figured everyone was cleaning their screen the right way and wouldn't see it.
THANKS!!!!!
http://youtu.be/Tvh_l10fmzY
Cleaning it the wrong way brings up this screen-
Sent from my VS985 4G using XDA Free mobile app
do you have a knock code set? When I had knock code set and I would clean the screen it would come on and I would get failed attempts to unlock. With Knock code turned off the screen says off while cleaning it
gramenz said:
After much reading, it seems that the only known way to toggle Knock On/Off on the Verizon LG G3 is to root.
Because of my work situation and Good For Enterprise, I am unable to root. This has bugged the heck out of me.
I really wish to toggle Knock On/Off as when I'm cleaning the screen, fumbling the phone, etc it likes to wake up. From time to time I would get a stock LG Screen pop up that asked me to toggle this feature. I never did, as I didn't know how to replicate it.
Fast forward to last night. Note: so far I have only gotten this to work with a soft cotton shirt, but was able to replicate it numerous times. I pulled the phone out of my pocket. OCD & tempered glass don't mix. I starting cleaning my screen with my shirt. I had three fingers inside my shirt and start swiping up and down fairly fast with the screen off. Any other time, the screen would wake up, and I would have to manually turn it off to finish cleaning. However, the LG screen popped up asking to turn on/off Knock On. I left it alone, and tried this numerous times with success. I actually got a bit brazen and turned it off. I can tell you it indeed disables knock on as well as knocking off with the status bar (I use Nova). I can verify it works with the screen on as well, so it must have to do with swiping on the status bar.
I tried again this morning with a sweater and have yet to replicate it. If I figure anything more out, I will update this post, but props to Verizon for hiding stock features from us.
Erik
Click to expand...
Click to collapse
If you're not too attached to the stock LG launcher, then I've heard changing your launcher does this. Can't vouche for it as I haven't tried it, but this is what I've read. Might be worth a try if it bugs you that much and you can't root!
supposedly with the new Google Now launcher the knock on and off don't work.
That may be an option for the OP.
I think with Nova launcher you can toggle the knock on and off but I am not sure about that, just what I have read here.
both launchers install without root.
R-
labcoat22 said:
supposedly with the new Google Now launcher the knock on and off don't work.
That may be an option for the OP.
I think with Nova launcher you can toggle the knock on and off but I am not sure about that, just what I have read here.
both launchers install without root.
R-
Click to expand...
Click to collapse
I use the Google Now Launcher and knock code still turns my phone on without problem. I can still knock off but only on the notification bar.
Also, no issues with it turning on when wiping the screen.
One thing that has happened though is sometimes I pull it out of my pocket and end up touching the screen in a way before I enter my knock code that makes it think I put in the wrong code.
That is good to know. I have read of some folks the knock to un-lock stop working after installing a third party launchers
R-
LaTropa64 said:
I use the Google Now Launcher and knock code still turns my phone on without problem. I can still knock off but only on the notification bar.
Also, no issues with it turning on when wiping the screen.
One thing that has happened though is sometimes I pull it out of my pocket and end up touching the screen in a way before I enter my knock code that makes it think I put in the wrong code.
Click to expand...
Click to collapse
Action launcher has an option for knock off an works great! Knock on as well as knock code works without issues too.
I use nova launcher prime and have mapped the double tap gesture to greenify hibernate and lock. This allows me to use nova but still enjoy double tap to turn off the screen
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.
The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
turbosrrgood said:
The fingerprint scanner is actually very good if you set it up right, and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
Or lift to check turned on rather than AOD.
turbosrrgood said:
...and will always be displayed with always on display... No tap required. Problem solved
Click to expand...
Click to collapse
This is not my experience at all. Sometimes I get a fingerprint sensor icon. Other times my phone is unlocked via Smart Lock and I get an Unlock icon in place of the fingerprint sensor. Other times I get a Lock icon indicating Smart Lock is expired. Other times I get no icon there at all.
If the fingerprint sensor is there and I'm on the dimmed screen, sometimes it'll just light up and deny, and other times it won't even acknowledge that I've put my finger on the sensor.
If the Unlock icon is there, it requires a tap to unlock (no holding!). So that means I have to actually look at the screen and discern which icon is there to know whether I need to tap or hold.
And Lift to Check Phone would be even more problematic for me, since I'm trying to avoid accidental screen interactions and this would only cause more.
On all my other Pixel phones I just touch the back fingerprint sensor and the phone is on. I don't have to think about a dozen different possible states the phone could be in every time I want to turn it on.
Have you tried to recalibrate it via the Pixel tool thing Google has?
Google Pixel - Update and Software Repair
gavingt said:
The simple user experience of unlocking the device on is so bad on Pixel 6. There's just no winning option.
Smart Lock randomly kicks in, so I can't be sure that a single tap of the screen will turn on the phone.
The fingerprint sensor sucks, and requires a tap on the screen just to bring it up. And sometimes I don't even get the option to use my fingerprint.
I don't even like the single-tap gesture to begin with. It means I'm accidentally turning my screen on all the time just when carrying the phone. It almost started a call with my deadbeat father, who I haven't talked to in 20 years
I could go with no screen lock but then I'm locked out of several key features (like viewing my account passwords). Also, pressing the Power button at all on a phone this big is cumbersome, since I then have to reposition my entire hand to go from pressing it to then interacting with the screen.
I'm already rooted because I absolutely needed the Back button to be on the right side. Now I'm hoping modders can fix the unlocking experience because it's the next big issue in my mind.
Click to expand...
Click to collapse
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
If you changed the Animation Scale in Developer Settings then the AOD fingerprint icon can disappear.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
gavingt said:
I never used to use Smart Lock, but on this phone it means I don't have to deal with the inconsistent fingerprint sensor as often.
Click to expand...
Click to collapse
Try setting up the fingerprint scanner again, slightly moving your finger with ever press during set up to get every angle and view of the print. It's been pretty much perfect for me. I suppose Google could have helped instruct people to do that better in the process.
turbosrrgood said:
It sounds like smartlock working as intended (which I find useless, and poor security). It will give you an unlock icon instead of the fingerprint. Maybe you simply don't want smart unlock, which is more useful for password only. This seems like more of a matter of figuring out what features you want to use.
Click to expand...
Click to collapse
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
turbosrrgood said:
I did see it happen a couple of times in your stream. I don't recall seeing that on mine, but I haven't been looking for it. The only other thing I can suggest is make sure you have the latest updates and/or factory reset.
Edit - I tried to replicate your stream, and the sensor showed in all 30 attempts for me. For whatever it's worth, so might be something specific to your device, maybe settings or software issue
Click to expand...
Click to collapse
It could be a bug related to my specific settings:
Rooted device, still on the October update
Lock after screen timeout: 30 minutes
Power button locks instantly: Off
gavingt said:
I just restarted my phone, and then repeatedly unlocked and locked it (sometimes by fingerprint, sometimes by tapping). By the end of the video, the fingerprint sensor icon disappeared completely and wouldn't come back until after another restart:
Streamable Video
Watch this video on Streamable.
streamable.com
This is just one example of the inconsistencies. I haven't changed the animation settings either.
Click to expand...
Click to collapse
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
kramer987 said:
what are you going on about lol. this is the kind of nonsense that is so irritating. you had 100% success rate unlocking your phone. what's the problem. looks to me like it works. so what's the big deal. and then you have the gall to complain that the sensor icon disappeared after you repeatedly locked and unlocked your phone? yea. try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
gavingt said:
I'm already rooted because I absolutely needed the Back button to be on the right side.
Click to expand...
Click to collapse
You know gesture navigation is a thing now right? Back buttons are so "last decade".
sic0048 said:
You know gesture navigation is a thing now right? Back buttons are so "last decade".
Click to expand...
Click to collapse
Yes, I know and I hate it. It's extra motion that tires out my hand and I often trigger the gestures when I don't mean to.
gavingt said:
Sure, ignore my multiple posts on the subject. It's not nonsense. I have no idea why you're trying to minimize this, and why you feel the need to be so combative.
Click to expand...
Click to collapse
i will just apologize and go on with my day. good luck with the phone.
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it. And you can't see it in the video, but the sensor doesn't even light up the first time I touch it. This is clearly a software bug.
gavingt said:
I went ahead and updated to the November firmware, and wiped my data as well. Now my phone won't show the fingerprint sensor while unlocking under any circumstances. I also found an interesting bug wherein I'm still able to turn my screen on by tapping it repeatedly even with "Tap to check phone" disabled:
screen-20211102-164842[1]
Watch "screen-20211102-164842[1]" on Streamable.
streamable.com
EDIT: And, of course, as I was typing this the fingerprint sensor just magically came back. And it still doesn't work unless I tap the dimmed screen to wake it first. Watch as it straight up ignores my finger the first time:
screen-20211102-171057[1]
Watch "screen-20211102-171057[1]" on Streamable.
streamable.com
I can recreate this 100% of the time by just setting my phone down for a second and picking it back up, then trying to unlock it.
Click to expand...
Click to collapse
but at least we know you like dunkin donuts, dominos pizza, and your mom forgets stuff
kramer987 said:
try starting your car repeatedly. see what happens with the engine.
Click to expand...
Click to collapse
Guess you don't know anything about cars. You can start and stop a fuel injected car until the battery dies, and nothing will happen to the engine or fuel system. (Yes, the battery will die if you keep starting the car and tuning it off right away) Just as proof of this, most modern cars shut off the engine when you come to a stop, and restart when you let off the brake. If you're in stop and go traffic, the engine will shut off and turn on repeatedly in a short amount of time nd distance.
Now with classic cars and motorcycles, you my flood the carb with repeated starts. Not a big deal, and not any kind of damage.
The only "damage" in repeatedly starting a car would be normal wear and tear on the starter. They do have a finite lifespan. But again, not damage, just use.
I've been documenting my struggles with my lock screen in another thread. But I just had a major breakthrough and didn't want this to get buried.
To recap, my lockscreen has been a buggy mess from day one. The fingerprint sensor barely works, the fingerprint icon randomly disappears, and the gray border that's supposed to appear around the fingerprint icon simply doesn't show up. The lockscreen doesn't light up when I pick up the phone either (it stays dimmed). Also, wallpapers don't show up on the lock screen, and the big ugly clock sometimes disappears or moves itself to the top-left.
I've tried just about everything to fix this. As a last-ditch effort, I added a new user profile only to find that the lockscreen works perfectly well for this new profile (but still not for my main one).
Here's my main profile with the unusable lockscreen:
broken lockscreen of main profile
Watch "broken lockscreen of main profile" on Streamable.
streamable.com
And here's what it looks like when using the other profile:
working lockscreen on new profile
Watch "working lockscreen on new profile" on Streamable.
streamable.com
So there's clearly some obscure bug that most people aren't experiencing here. I'd love to just figure it out so I can move on.
When I didn't have the "always on display" turned on, the phone was very consistant about turning on properly when I picked it up. I ran it this way for 3-4 days without any issues.
After reading some articles on the P6, I realized that it has an AOD and that it was turned off. So I turned the AOD on while leaving all the other settings set the same. At first, the finger print icon wouldn't appear consistantly, but that is because I had adjusted the animation scale settings in the Developer settings. Changing that back to stock fixed the issue with the finger print icon not showing up.
That beings said, I have experienced the same "unresponsive" screen many times over the last couple of days that I have had the AOD turned on. The screen stays dimmed (or even turned off if I pull the phone out of my pocket) and the finger print reader is inactive (even though the icon is displayed). The screen is suppose to turn on when I lift the phone up, but it doesn't always do it. When this happens, I have to either manually turn the screen on using the power button, or double tap the screen to wake it. This is clearly a bug in the system somewhere. I probably need to report it to Google, but hopefully it is fixed soon.
After spending way too long on this, I've determined that the bug occurs consistently with these specific settings (although it may also occur for similar ones):
Lock after screen timeout: 30 minutes (or anything high enough to prevent it from locking between tests)
Power button instantly locks: disabled
Lift to check phone: disabled
Tap to check phone: disabled
Always show time and info: enabled
Replication steps:
1) Enter the above settings
2) Press the Power button to go to the lockscreen
3) Set your phone down for a couple seconds
4) Pick your phone back up and try to use the fingerprint sensor
Result: The fingerprint sensor won't work the first time.
I think all the other issues I had were actually stemming from this one issue.