Coming from a OP5 with a separate fingerprint sensor (rather than under display), I'm used to being able to unlock the phone just by placing a finger on the sensor - even when the display is off.
On the 10T, the sensor only seems to work with the display is on, so I need to jiggle the phone a bit too wake it and then present my finger.
I found a setting 'fast unlock' which reads like the sensor is always active however I can't see any difference and pressing when the screen is off does nothing.
Anyone seen this / know how to get it working?
(For context, this is mostly an issue when I leave the phone on the desk and want to check something without moving the phone. If I pick it up then it wakes up and sensor works as expected)
Related
I just installed AOKP Unofficial 4.2.2 from this thread.
If I simply make a call, the proximity sensor functions as expected and near perfectly (I think there's slightly too much lag between removing the phone from one's ear and the screen coming back on... but not unbearable). With the keypad shown, I've found the behavior to be quite unpredictable. On my first call with the new ROM, I called my company voicemail and between inputting my password and cradling the phone, I could hear a bunch of key presses occurring. It ended up disconnecting the call. This is quite reproducible for me.
I'd like to know if this is a reproducible issue, intended function, and/or bug (which I will report if others can verify).
Method:
- Dial a number
- Set phone on table
- Put hand in viscinity of top of the phone
- Observe screen turning off and on as you move your hand over the sensor and then away
- Pull up keypad
- Repeat hand test and observe that the screen is not predictable
In trying this several ways, there's either a lag in detecting proximity, or it's just flaky. I actually find it really hard to reproduce consistently. Sometimes it actually will turn off (I can see peripherally that if I put it to my ear), however if cradling (with phone still well within what I could call "proximity" to my face/ear), it will dial numbers. In putting my hand in various positions over the phone, sometimes it turns off, sometimes not. With the keypad hidden, it turns off reliably 100% of the time.
The biggest difference I can reproduce is that if you put a single finger over the full width of the top of the phone (over the HTC logo -- the sensor is just to the left of the logo), it will reliably turn off the screen without the number pad, but not with it. I get that the sensor probably needs to account that one's fingers will be pushing on the screen to enter numbers, but something directly over the sensor (simulating an ear pressed to it) should turn it off even with the number pad shown, I would think.
Thanks for any suggestions of if you'd like any further information.
----------
ETA: S-off, unlocked bootloader, AOKP: aokp_jewel_unofficial_Mar-12-13, baseband 1.12.11.1210, Android 4.2.2.
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!
I have a Mi A3 and think it's great, but there is one issue I'm facing.. the fingerprint sensor is always active and when the phone is in my pocket and touches my leg, it wakes the screen after X failed attempts.
Multiple times I've pulled out my phone to find my leg has been typing numbers into the emergency dialler..
Is there any way (prefer no root - but so be it if needed..) to use the proximity sensor to kill the FP sensor? That way when it's covered in my pocket the FP sensor would be disabled and stop waking the phone all the time.
And before anyone says just put in your pocket with the screen out.. well that's just asking to get it smashed ?
Try disabling "show fingeprint icon when screen is off" feature.
Tried that one already. Unfortunately the sensor is still alive so if something touches it the phone attempts to unlock.
After a couple of attempts it seems to turn on and show buttons for emergency dialler / pin unlock.
Not sure if this would be usable on A3, but you could try this approach:
https://android.stackexchange.com/questions/153948/completely-disable-the-fingerprint-sensor
Edit: just tried it on my A1. I can disable the FP sensor with:
Code:
echo soc:fpc1020 > /sys/bus/platform/drivers/fpc1020/unbind
BUT, can't get it back yet (only with reboot): this should be the correct command, but it doesn't do anything
Code:
echo soc:fpc1020 > /sys/bus/platform/drivers/fpc1020/bind
Custom ROMs have something like pocket mode that detects and prevents it don't they? I wish something like that would be available for stock as well. Wouldn't mind root.
I have the same problems with scanner acting in a pocket. Looks like I have to disable scanner for now. This can be done by removing recorded fingerprints from settings.
As a workaround for emergency dialing, you can use WaveUp app and set it to lock with proximity sensor. It probably won't prevent fingerprint readings, but at least the display will turn off in your pocket. Works best with root, I'm using it on Mi A1. "Turn display on when removing from pocket" feature is highly addictive. I use HW power button mainly for taking screenshots now..
Edit: Tasker with states "proximity sensor and orientation - phone upside down" and task "display - turn off" can do the same if you want to keep it simple.
Edit 2: Nicer Tasker profile, turns screen off only when the screen is locked (prevents accidental locks while using the phone):
Profile 1 - state "proximity sensor" + state variable value "%SCREEN_LOCKED ~ true", task "display - turn off"
Profile 2 - event "display unlocked", task "variable set, %SCREEN_LOCKED to false"
Profile 3 - event "display off", task "variable set, %SCREEN_LOCKED to true"
Turn display on&off with power button and you are good to go.
Thanks will give the commands a go when I get chance and see if it works on the A3.
put you phone opposite side .... screen upwards in pocket.
hi this feature works on my device when i turn off the proximity sensor the fingerprint icon does not show up on the screen
I have this problem too with Android 11.
I wanted to try the method with fpc1020 driver. The driver is here, but what is weird, that in /sys/bus/platform/devices is not such device attached :/
The easily way to do this is root the phone. After this you can disable all useless features
wetito said:
The easily way to do this is root the phone. After this you can disable all useless features
Click to expand...
Click to collapse
I have rooted phone but you probably doesn't understand the problem.
I don't want to completely disable fingerprint, I just want the FP to be disabled by proximity sensor, because it's bul*** to have enabled FP in pocket...
Benik3 said:
I have rooted phone but you probably doesn't understand the problem.
I don't want to completely disable fingerprint, I just want the FP to be disabled by proximity sensor, because it's bul*** to have enabled FP in pocket...
Click to expand...
Click to collapse
There"s a quick setting to add by developer settings that disable all sensors. Have you tryed? Maybe it work
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.
I don't know anything about how under-screen fp readers work, but... Is there no way to use it when the screen is off?
On previous phones I always used the fingerprint sensor to turn on and unlock with one touch, but this N20 5G seems to only fp-unlock when A) The screen is on, and B) The "fingerprint goes here" icon is visible.
The screen will usually turn on when I pick up the phone ("Somatic Gesture"); the fingerprint icon then appears for a few seconds, then goes away. That seems to be the only window for unlocking without clicking the power button.
Am I missing a trick?
I use double tap to wake and it works great. The sensor stays lit up for about 7 full seconds before going black. YMMV
Good point, double-tap to wake was disabled by default!
Still two more taps than I'd prefer to get to the fingerprint unlock, but I guess that's more a reflection of how incredibly lazy I've become than a problem with the phone.
Florp said:
I don't know anything about how under-screen fp readers work, but... Is there no way to use it when the screen is off?
On previous phones I always used the fingerprint sensor to turn on and unlock with one touch, but this N20 5G seems to only fp-unlock when A) The screen is on, and B) The "fingerprint goes here" icon is visible.
The screen will usually turn on when I pick up the phone ("Somatic Gesture"); the fingerprint icon then appears for a few seconds, then goes away. That seems to be the only window for unlocking without clicking the power button.
Am I missing a trick?
Click to expand...
Click to collapse
It works for me