Related
Is anyone else having issues with AOD turning off even with slight darkness. For some reason my AOD keeps turning off even though there still some light in the room. It used to stay on when I wake up at 6am when there some sunlight but now it just turns off. I have to point the phone directly to the light sometimes to get it to turn on. Don't have any screen protector that is blocking the light sensor and seems to function correctly checking the debug mode (*#0*#). I have to reboot the phone to fix the issue but after a few days it goes back to being wonky.
yeah, i updated it via Samsung Galaxy App store, then did a data clear in the setting menu and now it works. But mine did the exact same thing.
clearing the data still causes me the problem.. Only fix for me is to reboot the phone =/
Do you have a screen protector?
Tidbits said:
Do you have a screen protector?
Click to expand...
Click to collapse
I have a screen protector but have all the cutouts that isn't blocking the proximity sensor. I've tested the sensor in debug mode and no issues at all.
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Tidbits said:
what was updated or installed recently that had this started happening with. It may be an app that introduced a bug. Did you try and see if there is a AOD update?
Click to expand...
Click to collapse
what screwed it up was the AOD update (go figures ).. I reverted back to the original before the update but somehow it's broken now. As mention it works like it should after a reboot but after a few days it becomes all wonky.
Greetings,
Does anyone have this issue? Phone wakes up when fingerprint reader is touched (with any finger) even when it's not set up? Is there any workaround?
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
katoda_ltd said:
Nope. In my case the phone just vibrates when touched with non-registered finger, but the screen remains dark.
Click to expand...
Click to collapse
That happens to me as well if I have a fingerprint set up.
But if there is absolutely no fingerprint is set up, the phone still wakes up whenever the scanner is touched.
To see if you have this issue, delete all your fingerprints from your f1, turn off the display and touch the fingerprint sensor and see what happens.
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
katoda_ltd said:
Yes, then it works like in your case, the phone wakes up.
As I'm using the fingerprint reader, it is not an issue for me. In your case, maybe just add a fingerprint hard to use, e.g. thumb, phone will vibrate when touched but at least will not wake up.
Click to expand...
Click to collapse
It's not a big issue. I was just wondering if it's only a problem with my specific unit.
If its a software issue probably get fixed with updates or maybe a different rom.
You never know if it's a bug or a feature
katoda_ltd said:
You never know if it's a bug or a feature
Click to expand...
Click to collapse
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Rowdyy Ronnie said:
If the FP lock gets triggered without having it activated/registered, it's a major bug and posses a huge security threat.
Click to expand...
Click to collapse
Do you also have this bug?
Windoors said:
Do you also have this bug?
Click to expand...
Click to collapse
Nope I don't have any such issue on miui beta 9.4.26
I would suggest you to do a factory reset if you continue to have this issue.
My phone came with oreo, it had this issue.
Now using 10.3.4 stable (prerooted) the issue persists.
Haven't tried lineageos.
This is a software feature from miui, my mi max used to also light up when no fingerprint is registered. It can be turned off somewhere in settings iirc.
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
srahman53171618 said:
If you don't have a finger print set up, then the finger print sensor acts a bit like the power button to wake the screen. I don't see why you would consider this to be a bug but I've seen this in a few other phones as well. Doesn't strike me as being a problem but maybe that's just me.
Click to expand...
Click to collapse
Well, if you accidentally touch it phone will wake up without you knowing. It can happen while its in your pocket.
Anyone using non-MIUI rom, do you also have this problem?
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 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.