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.
Related
Ok, I have a voice changer app that I want to use with the screen off. Ideally I'd start the app, turn on real-time processing, then turn the screen off. Currently, it only runs when the screen is on, as soon as I turn the screen off the app stops all voice processing. Screen needs to be off so the battery will last longer, and so the settings can't be changed accidentally (so touch has to be disabled as well).
I either need the app to keep running in the background, or have the screen turn off but not actually locked (I dunno the right term, but if the screen was off and didn't accept touch input, but the phone thought the screen was on...that'd be fine).
Closest I've found is to edit the AndroidManifest.xml file to set it persistent, then make it a system app. This will take me a while to figure out, and not even sure it'll work.
Is there some simple solution I'm overlooking? I've seen an app that turns off the screen with help from the proximity sensor...but I want the screen off whether it's in my pocket or lying on top of a table.
Edit: I tried some apps that use the proximity sensor to turn off the screen; as soon as the screen goes off, the voice changer app just stops. I have no idea what's triggering it (if the phone is actually entering a sleep state, or if the app is specifically watching for the screen to go off and suspends itself). Thought that might be a workaround, but nope.
With the S9+ powered up but the screen black: Press power button and I get the PIN screen as I have selected. In 3 seconds, the screen goes dark again. Can this be extended? The timeout is too short to read notifications before it goes black.
I am not referring to the screen timeout that is easily modified in settings.
Thanks (sorry if this is a dup - I did search)
Answer: 3 seconds is the built-in value
I had a chat session with Samsung and they confirmed that the built-in timeout is 3 seconds and can't be changed. That is the answer.
FYI: They have a very nice tool that allows them to take over your phone and you can watch them work.
Use Case
1. Phone is booted up, uses a pattern to unlock, allows notifications on the lock screen, has 30 second timeout (example)
2. Screen is black
3. Press Power button
4. You get the unlock screen and any notifications that exist - possibly many of them. This is allowed in the notification and lock screen settings
5. You start to read through the notifications to see if there are any that need attention and if not, you just put the phone down
6. In 3 seconds from the point when you get the lock screen and notifications, the screen goes black again unless you do something
The point is that you should be able to set a longer time (e.g., 15 seconds) for the screen to stay on before it goes black. That way you could review the notifications to see if you really want to log in and do something. This would not appear to be a security problem since the phone is still locked.
This is the way it is designed - working as designed per Samsung.
fyi
scott
There seems to be a work around. If you turn on face unlock, but don't point it at your face, it seems the lock screen will stay on and keep trying to find your face. Of course, you may not want to use face unlock.
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.
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
robjg63 said:
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
Click to expand...
Click to collapse
Hello!
Please write your problem to an official bugreport https://wiki.lineageos.org/bugreport-howto.html to let the LOS developers team about the encountered issue.
Thanks. Signed up to add the fault and found someone witha different device reporting the same bug around a week ago.
Added my confirmation of the problem with different hardware.
Fingers crossed someone may have a look at it when time allows.
Hello,
I'm experiencing a weird problem with my LG V30 H930 and I was wondering what could be the solution, if anyone has ever experienced that as well?
Yesterday I received a new LG V30 phone and that day I found something very disturbing. The "always on display" function does not work when it's too dark in the environment or when I cover the light sensor. This also results in:
- "double tap to wake" function does not work when it is too dark
- holding finger against the screen results in turning off display instead of entering options for changing wallpaper, adding widgets and settings. Additionally when I turn off the screen in this way, I need to press the button on the back of the phone twice, which is also a fingerprint reader and at the right time. If I do it too slowly, i.e. press the button once, wait a bit and then the second time, the screen will not turn on. I have to press it twice and relatively quickly
All of this does not happen when it is bright in the environment.
The phone's never been rooted, there is no custom firmware loaded on it, I've tried many times going back to factory settings.
Lovatnet said:
Hello,
I'm experiencing a weird problem with my LG V30 H930 and I was wondering what could be the solution, if anyone has ever experienced that as well?
Yesterday I received a new LG V30 phone and that day I found something very disturbing. The "always on display" function does not work when it's too dark in the environment or when I cover the light sensor. This also results in:
- "double tap to wake" function does not work when it is too dark
- holding finger against the screen results in turning off display instead of entering options for changing wallpaper, adding widgets and settings. Additionally when I turn off the screen in this way, I need to press the button on the back of the phone twice, which is also a fingerprint reader and at the right time. If I do it too slowly, i.e. press the button once, wait a bit and then the second time, the screen will not turn on. I have to press it twice and relatively quickly
All of this does not happen when it is bright in the environment.
The phone's never been rooted, there is no custom firmware loaded on it, I've tried many times going back to factory settings.
Click to expand...
Click to collapse
Why are you covering the light sensor if you want the AOD on?
You are basically replicating a flip case cover or flipping a phone over on the desk. Of course the AOD will turn off under those circumstances. There's nothing wrong with your phone.
With your display on, just quickly press your finger on the fingerprint sensor to display lock the phone and you will see AOD. Well you also have need the "power key instantly locks" option turned on. But I assume you have that on already.
Of course the AOD works in a dark environment. But in this instance, you are covering the light sensor -- which tells the phone you must have it in a flip cover case or flipped over. When you open the case or flip the phone back on, the AOD comes back on. In your fake way, you must be doing something wrong.
Stop covering the light sensor.
ChazzMatt said:
Why are you covering the light sensor if you want the AOD on?
You are replicating a flip case cover or flipping a phone over on the desk. Of course the AOD will turn off under those circumstances. There's nothing wrong with your phone.
Just quickly press your finger on the fingerprint sensor to display lock the phone and you will see AOD. Well you also have need the "power key instantly locks" option turned on. But I assume you have that on already.
Click to expand...
Click to collapse
I understand your logic, but it is a very weird feature then, not to be able to change wallpaper directly from the home screen, when it is dark in the room or not to be able to turn on the phone double-tapping the screen, which is turned off. Is it perfectly normal as well?
Lovatnet said:
I understand your logic, but it is a very weird feature then, not to be able to change wallpaper directly from the home screen, when it is dark in the room or not to be able to turn on the phone double-tapping the screen, which is turned off. Is it perfectly normal as well?
Click to expand...
Click to collapse
You can change wallpaper and double tap the screen, but go to AOD mode in a NORMAL way. I told you how. Just turn off the display with the fingerprint sensor. AOD. Double tap, display back on.
ChazzMatt said:
You can change wallpaper and double tap the screen, but go to AOD mode in a NORMAL way. I told you how. Just lock the display.
Click to expand...
Click to collapse
Thank you for your time!