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.
Related
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
Every time I make a call, the screen dims and then blacks out in a matter of seconds. It's in an Otterbox Defender. I have tried every setting I could find and have it set to turn off display after 10 minutes but something is overriding that for this phone app.
I'm new to LG and the V30 but on my last device it detected proximity to the screen during calls so your cheek doesn't mistakenly hang up or something. I believe it uses the front side camera to detect your head there. Could that be what os going on?
Sent from my LG-H933 using Tapatalk
Mine does the same and I dont think it's to do with proximity sensor. When i make a call on speakerphone or Bluetooth with nothing near the phone, it still dims and blacks out
I agree it's likely not the proximity sensor in this case as I always have it on a desk and use it via bluetooth but thank you for that suggestion. But, in many cases, I need to enter in several series of #'s for conference lines and changing options but the screen blanks out way too fast. When I double tap it to open the screen, I sometimes accidentally hit a # and have to start over again...
diskwzrd said:
I agree it's likely not the proximity sensor in this case as I always have it on a desk and use it via bluetooth but thank you for that suggestion. But, in many cases, I need to enter in several series of #'s for conference lines and changing options but the screen blanks out way too fast. When I double tap it to open the screen, I sometimes accidentally hit a # and have to start over again...
Click to expand...
Click to collapse
Do you mean it turns pure black, or just dims? Mine dims if I'm on a call utilizing the speaker. Just touch the screen to brighten it up, then type your conference numbers.
Sent from my LG-H931 using XDA Labs
Mr CATFISH said:
Do you mean it turns pure black, or just dims? Mine dims if I'm on a call utilizing the speaker. Just touch the screen to brighten it up, then type your conference numbers.
Click to expand...
Click to collapse
I have the exact same problem with my V30. I use Bluetooth, either on a headset or in my car. After a few seconds, the screen dims, and then a few seconds later, it blacks out completely. When it dims, I can tap on it to wake it up, but the screen still responds to the tap, so if I happen to tap where the hangup button is (easy to do in a moving car), I end up hanging up on myself. Or, if I'm navigating through an automated attendant, when I tap the screen to wake it up, it invariably hits a button for a choice I didn't want, and I have to back out or start over. Very frustrating! If the screen goes completely black, then I just hit the power button to turn it back on, but once again, it'll dim out in a few seconds. I would LOVE to have a fix for this! I like this phone better than the past Samsung phones I've had, but the Samsungs don't do this.
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
captainentropy said:
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
Click to expand...
Click to collapse
I have the same problem on my V30+ since the oreo update. Before it was OK.
During call screen blacks out and then when I take my ear off screen it does not light up again.
I need to press the power button to have the screen displayed again during call. I wonder it this was not done on purpose in order to preserve battery
Nowever It's frustrating because I was not used to this.
Any ideas?
Thanks Anndy
Same frustration for me. I make regular use of speakerphone and it is very irritating.
Sent from my LG-H933 using Tapatalk
Anndy said:
I have the same problem on my V30+ since the oreo update. Before it was OK.
During call screen blacks out and then when I take my ear off screen it does not light up again.
I need to press the power button to have the screen displayed again during call. I wonder it this was not done on purpose in order to preserve battery
Nowever It's frustrating because I was not used to this.
Any ideas?
Thanks Anndy
Click to expand...
Click to collapse
No fixes yet that I'm aware of. The "solution" I use is to tap or double-tap on the very top of the screen where there are no buttons that will affect the call. But this is by no means an acceptable solution.
captainentropy said:
I want to add my frustration to this issue as well. I also have a V30 and this happens all the time. My mom has a G6 and says the same as well. It is simply unacceptable. If this is an LG-specific issue and it isn't fixed (or at least given an option to change the screen time-out) then this is a deal-breaker for another LG in the future. (same goes for the glass back as well, but that's another issue...)
Eagerly awaiting a fix or workaround....
Click to expand...
Click to collapse
I, too, want to add my frustration with this problem. In my case, the screen goes black immediately after touching the phone icon to connect a call. I talked to the T-Mobile people who said they never heard of this before. This has been an issue since 2012, so that was useless. This started happening with the last update. Hopefully if more people complain, a fix will happen.
Same here...
captainentropy said:
No fixes yet that I'm aware of. The "solution" I use is to tap or double-tap on the very top of the screen where there are no buttons that will affect the call. But this is by no means an acceptable solution.
Click to expand...
Click to collapse
I hope we can get a fix or an option to this soon. It really messes up calls when options are needed during the call.
I've had the exact same problem with my G6 ever since I purchased it (February 2018). It's really annoying and a problem when you are calling an automated voice system and it dims before you can make your selection and double tapping to wake can cause you to hit a wrong number selection (which happened the other day when I was refilling a prescription). Please fix this!
Happens on the V20 also with the latest update from Verizon. The only way around it is to tap in an area you think won't affect the call every few seconds. The number bar on the top seems to work. defintely need a fix for this. Really annoying
Mad Medik said:
I'm new to LG and the V30 but on my last device it detected proximity to the screen during calls so your cheek doesn't mistakenly hang up or something. I believe it uses the front side camera to detect your head there. Could that be what os going on?
Click to expand...
Click to collapse
Me too! The solution? NONE, NONE, and NONE.
I called T-Mobile today about this very problem after my frustration hit the roof. I complained it's impossible to hold business conference calls on my phone because the dialpad screen dims in exactly 5 seconds. I need it fully lit so I can mute/unmute at-will for clear-sounding and respectful meetings. Yet, as every smartphone user knows, computer screens are no match against sunlight. I inevitably fumble my way around the dialpad on a bright day.
I did every configuration possible to mitigate the problem: Screen Timeout (none), Auto Brightness (off), Brightness (100%), Battery Saver (off). Nothing stopped the dialpad from dimming like usual. However, to my own surprise, all other apps respected my settings during a call. So is the LG phone/dialpad app itself ignoring my system settings? Yes. Yes it is. My theory was soon confirmed....
T-Mobile offered to do a 3-way call with an LG representative. The conclusion? I was told flat out it's a "feature of all LG phones", it's the "default", and there is "no way to change it". SERIOUSLY, LG?!?!? Shame on you, LG!!!! I didn't say that to the LG rep, but, I did tell her I will be "forced stay away from future LG phones" if there really was no solution for this and every other phone LG makes. She offered her scripted apology to me several times but, alas, there was nothing she could do.
PS: This is so, so, so disappointing. They could have kept their default but provided a system option to enable the app's FLAG_KEEP_SCREEN_ON. They could have taken my customer compliant seriously. So, for anyone reading this, if you want to do any active use of the dialpad during a call, stay away from LG phones.
pbenedictxda said:
Me too! The solution? NONE, NONE, and NONE.
I called T-Mobile today about this very problem after my frustration hit the roof. I complained it's impossible to hold business conference calls on my phone because the dialpad screen dims in exactly 5 seconds. I need it fully lit so I can mute/unmute at-will for clear-sounding and respectful meetings. Yet, as every smartphone user knows, computer screens are no match against sunlight. I inevitably fumble my way around the dialpad on a bright day.
I did every configuration possible to mitigate the problem: Screen Timeout (none), Auto Brightness (off), Brightness (100%), Battery Saver (off). Nothing stopped the dialpad from dimming like usual. However, to my own surprise, all other apps respected my settings during a call. So is the LG phone/dialpad app itself ignoring my system settings? Yes. Yes it is. My theory was soon confirmed....
T-Mobile offered to do a 3-way call with an LG representative. The conclusion? I was told flat out it's a "feature of all LG phones", it's the "default", and there is "no way to change it". SERIOUSLY, LG?!?!? Shame on you, LG!!!! I didn't say that to the LG rep, but, I did tell her I will be "forced stay away from future LG phones" if there really was no solution for this and every other phone LG makes. She offered her scripted apology to me several times but, alas, there was nothing she could do.
PS: This is so, so, so disappointing. They could have kept their default but provided a system option to enable the app's FLAG_KEEP_SCREEN_ON. They could have taken my customer compliant seriously. So, for anyone reading this, if you want to do any active use of the dialpad during a call, stay away from LG phones.
Click to expand...
Click to collapse
Root, use Google dialer? Does it dim also? I have it installed, I'll check tomorrow morning.
Google dialer "Phone" app doesn't help...nope!
I gave a workaround in an identical thread somewhere else in this forum. Use Waze navigation app during phone calls. The screen won't dim. Drag the phone call thingy over to the Waze screen.
Found it:
ChazzMatt said:
When I have Waze navigation on, my screen doesn't dim. When I make a phone call, I go back to Waze map screen. I can drag the phone call thingy wherever I want. If I need to mute, unmute I just click that to go back to call dialer interface for a few seconds. Then I go back to Waze screen to keep display on.
Yes, it's a wonky workaround, but it works. When I use this while driving, I make sure my phone is plugged in for charging -- because the display will stay on for the entire duration of the phone call.
Click to expand...
Click to collapse
My LG G8X does the same thing, goes dim after a few seconds, then blacks out completely. In the day & age of "press 1 for this, press 2 for that" it really should allow for more time before the phone becomes disfunctionable...
New auto update on LG phone times out too fast
My LG phone auto updated to a 3 sec. screen blackout and can't be changed in any settings menu. The solution is to install the "Keep Screen On Free" app which completely solved the problem and lets you change the time out settings too.
Hello,
Long time lurker here and was hoping for some advice/ suggestions.
I have a Canadian S9 Plus (on Bell Mobility) and noticed the following issues/ annoyances:
1) When the phone is woken up (e.g. pressing the virtual home button, plugged into charger, new text message received, etc.), the screen would turn on, continuously look for fingerprints ("Wipe the fingerprint sensor and try again" message would keep flashing) and would not shut off until I press the power button to turn off the screen
2) The fingerprint sensor generally works (e.g. unlocks the phone, swipes to drop down notification window), HOWEVER it does not work to unlock the phone if the phone has been sleeping for more than a few minutes (nothing happens no matter which direction I swipe/ press the fingerprint sensor). When I try to unlock the phone, I will have to press the power button to wake up the phone then swipe the fingerprint sensor. This may be a standard feature, but after pressing the power button to wake up the screen I will always get a message that says "The fingerprint sensor may be dirty. Clean it and try again.". Again the fingerprint sensor otherwise works so cleanliness of the sensor isn't really an issue here.
Has this happened to anyone's phone? I tried clearing cache/ resetting app preferences/ factory resetting the phone multiple times but with no luck. I also called Samsung but the conversation didn't go anywhere.
Any other suggestions? Thanks in advance for your help!
Have not had that issue with mine.
Do you have the finger sensor gesture on?
chickenbb said:
Do you have the finger sensor gesture on?
Click to expand...
Click to collapse
Tried both finger gesture on and off - no difference with the same issues persisting :crying:
this is the exact issue im facing when i got my s9+, i also thought that it was a factory defect. but luckily recently it didnt came up again and i did nothing. but still continuing monitoring the issue as it is really so bothersome.
Sounds like a defect to me. I'd exchange it.
I have not had any issues. Have you tried re-scanning your fingers? I noticed that this finger print scanner is different from the one on my LG V20. It feels different, and seems to operate different. It's also a little smaller which makes me have to position my fingers different.
I also read the instructions wrong.. I was supposed to swipe my finger during the setup. I was pressing it down. Either way mine works great.
Same issue here, did you manage to solve it?
Mario_Nissan said:
Same issue here, did you manage to solve it?
Click to expand...
Click to collapse
Not at all - I ended up returning it. Any luck on your end?
Maybe try registering your finger/s with and without a case on. See what happens.
Same issue here. This is the one thing that really bugs me about this phone.
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 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.