Just got the Verizon V30 and I do have AOD on. When I put the phone to sleep with power or knock off I have trouble waking it up. It appears the screen goes off totally when I flip it over or put it in my pocket. Whe I pull it out of the pocket it will not wake up with power button or knock on taps for a good 20 seconds or more.
I cannot find a setting to stop the screen for totally going off when I pocket the phone. I can confirm that I do NOT have the smart lock feature enabled. I’m just using a PIN code unlock, no facial or voice recognition. I really like the phone but I can’t have this happening every time I take it out of my pocket or turn it over on the couch.
Any ideas?
Thanks for reading.
Rob
BubbaRob1978 said:
Just got the Verizon V30 and I do have AOD on. When I put the phone to sleep with power or knock off I have trouble waking it up. It appears the screen goes off totally when I flip it over or put it in my pocket. Whe I pull it out of the pocket it will not wake up with power button or knock on taps for a good 20 seconds or more.
I cannot find a setting to stop the screen for totally going off when I pocket the phone. I can confirm that I do NOT have the smart lock feature enabled. I’m just using a PIN code unlock, no facial or voice recognition. I really like the phone but I can’t have this happening every time I take it out of my pocket or turn it over on the couch.
Any ideas?
Thanks for reading.
Rob
Click to expand...
Click to collapse
Do you have any screen protector on the phone? Any battery saver apps or settings? In my experience the AOD is suppose to go off when turned over or put in a pocket. I haven't seen a way to change that. Mine might take a couple seconds to awaken, but never 20 seconds.
BubbaRob1978 said:
Just got the Verizon V30 and I do have AOD on. When I put the phone to sleep with power or knock off I have trouble waking it up. It appears the screen goes off totally when I flip it over or put it in my pocket. Whe I pull it out of the pocket it will not wake up with power button or knock on taps for a good 20 seconds or more.
I cannot find a setting to stop the screen for totally going off when I pocket the phone. I can confirm that I do NOT have the smart lock feature enabled. I’m just using a PIN code unlock, no facial or voice recognition. I really like the phone but I can’t have this happening every time I take it out of my pocket or turn it over on the couch.
Any ideas?
Thanks for reading.
Rob
Click to expand...
Click to collapse
Were you able to find a fix for this issue? This started to happen with mine
BubbaRob1978 said:
Just got the Verizon V30 and I do have AOD on. When I put the phone to sleep with power or knock off I have trouble waking it up. It appears the screen goes off totally when I flip it over or put it in my pocket. Whe I pull it out of the pocket it will not wake up with power button or knock on taps for a good 20 seconds or more.
I cannot find a setting to stop the screen for totally going off when I pocket the phone. I can confirm that I do NOT have the smart lock feature enabled. I’m just using a PIN code unlock, no facial or voice recognition. I really like the phone but I can’t have this happening every time I take it out of my pocket or turn it over on the couch.
Any ideas?
Thanks for reading.
Rob
Click to expand...
Click to collapse
I just began having this issue. Do you still have the device?
It never worked correctly so I got rid of it. My coworker still uses his and has no issues. Sorry I can't help more.
Rob
I try it by my V30 and had no problems. It is eventually just a random bug?
Nemeziz 56th said:
I try it by my V30 and had no problems. It is eventually just a random bug?
Click to expand...
Click to collapse
I have my since December from last year and only now it started to behave like that.. I don't know if it is a software issue or hardware issue of some kind. I've tested the sensors and they appear to be fine.. I will try to do a backup of my data and perform a hard reset to see if it helps, but I'm not counting on it...
I don't use AOD. Just try it to reproduce the problem. Maybe my V30 get the same problems after long term use of it.
The only problem i get random with screen is, that after a restart the colors get crazy there are not normal after enabling Comfort View all get back normally but it is a other story.
Nemeziz 56th said:
I don't use AOD. Just try it to reproduce the problem. Maybe my V30 get the same problems after long term use of it.
The only problem i get random with screen is, that after a restart the colors get crazy there are not normal after enabling Comfort View all get back normally but it is a other story.
Click to expand...
Click to collapse
I did some tests (issue of being a former Senior QA Engineer). I've tried disabling the AOD and the same thing happened. What I just did is disabling the Knock-On feature.
I need to test it more thoroughly but the issue didn't happen after that.. YET. I need to go somewhere, with the phone in my pockets for a longer period (even though by now I should've seen the issue again) just to be sure and even trying to enable the Knock-On back again.. But let's see..
As for the colors, I really can't say much because I've never used the comfort view feature (I usually just dim down the brightness at night and that's all).
Yeah test it i will it do too. I enabling the AOD and say you next day when i get some problems.
I testing AOD since yesterday and dont get any problem until now.
Hello, I had the same problem, the proximity sensor fails, although the tests say otherwise, download an application from play store, fix sensor, solved!
---------- Post added at 02:49 AM ---------- Previous post was at 02:47 AM ----------
https://play.google.com/store/apps/details?id=es.dmoral.proximitysensorfixer
Nemeziz 56th said:
I testing AOD since yesterday and dont get any problem until now.
Click to expand...
Click to collapse
I still need to try the Comfor Color to see if it happens here. Is only that I always forget to try.
With mine the AOD worked well since day one. I did some things that seemed to have fixed somehow...
I've removed the device from the case I was using (a simple thin one). gave it a good cleaning, forced the power button for a while because I was feeling it was getting stucked. It seemed to keep showing issues HOWEVER, after I disabled the Knock-On feature, left it off for a while it stopped to have issues. I enabled it again and now it is working perfectly... I don't know if it was a coincidence or a sum of all factors.. but now it seems to be working...
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
Markbarr said:
Hello, I had the same problem, the proximity sensor fails, although the tests say otherwise, download an application from play store, fix sensor, solved!
---------- Post added at 02:49 AM ---------- Previous post was at 02:47 AM ----------
https://play.google.com/store/apps/details?id=es.dmoral.proximitysensorfixer
Click to expand...
Click to collapse
Take a look at my previous message (i replied to Nemeziz) I did some things and it's working so far...
By the way, what is this app you were talking about?
caio_oz said:
I still need to try the Comfor Color to see if it happens here. Is only that I always forget to try.
With mine the AOD worked well since day one. I did some things that seemed to have fixed somehow...
I've removed the device from the case I was using (a simple thin one). gave it a good cleaning, forced the power button for a while because I was feeling it was getting stucked. It seemed to keep showing issues HOWEVER, after I disabled the Knock-On feature, left it off for a while it stopped to have issues. I enabled it again and now it is working perfectly... I don't know if it was a coincidence or a sum of all factors.. but now it seems to be working...
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
Take a look at my previous message (i replied to Nemeziz) I did some things and it's working so far...
By the way, what is this app you were talking about?
Click to expand...
Click to collapse
Sorry for my English, I do not use the Knock-On function, below is the application link for the proximity sensor
Related
I have this one problem that happens intermittently:
Sometimes, upon turning the screen on, the face unlock turns on, but the camera doesn't, so all that's shown is a black screen.
Has anyone else experienced this?
I tried out the face unlock for a day and yes this happened to me a lot. When it worked it is pretty handy but I would say 1 out 3 times ff camera did not turn on.
Sent from my EVO using xda premium
It happened to me once so far. Ive been using it(and just playing with it) for two days now.
Happened to me quite a few already but only when I was in low light situations. Other than that, when I'm outside or during the day indoors, it works perfectly!
kevinsturf said:
Happened to me quite a few already but only when I was in low light situations. Other than that, when I'm outside or during the day indoors, it works perfectly!
Click to expand...
Click to collapse
This happens to me outdoors, in good light, as well.
I hope HTC rolls out a fix soon.
No problems here worked eveytime since pre-order launch day
Sent from my Evo Lte using XDA
I think once out of the 30+ times I've used it so far (I have mine set to stay unlocked for 5 minutes) the camera didn't come on in time for the face unlock timeout.
It's still happening to me, maybe about 10-15% of the time.
Me too- I'd say 10 - 15% is about right. It works enough that I've left it on though.
---------- Post added at 12:02 PM ---------- Previous post was at 11:58 AM ----------
kevinsturf said:
Happened to me quite a few already but only when I was in low light situations. Other than that, when I'm outside or during the day indoors, it works perfectly!
Click to expand...
Click to collapse
In low light it's different- it actually specifies that lighting is the problem; I can't remember the actual wording. Like I said, it still works enough for me to keep using it.
-still like most of us geeks, it will bother me until I fix it.
it happened to me when i was custom rom
No Issues here.....has always turned on....
I wonder though.....for those having the issue......(and don't flame for this question) but did you make sure you were not covering the front camera? its in the upper right side of the screen and I could see possibly covering the cam with a stray finger......
just a thought to check.....though unlikely.
slayer69 said:
I wonder though.....for those having the issue......(and don't flame for this question) but did you make sure you were not covering the front camera? its in the upper right side of the screen and I could see possibly covering the cam with a stray finger......
Click to expand...
Click to collapse
I hear ya- I'm an I.T. tech, and people go nuts when I say "are you sure it's turned on?" -but for the record, the camera is not blocked when it happens.
What I found out is that the timing of the two knocks is less important, what is more important is to keep the finger on the screen after the second knock. After the second knock just keep it on the screen until you see the LED lights up, and you'll see how more efficient it will become.
Im tapping on every other device since I have my LG!
Sent from my Nexus 7 using Tapatalk 4
i go knock knock knock, it almost always helps.
Noam23 said:
What I found out is that the timing of the two knocks is less important, what is more important is to keep the finger on the screen after the second knock. After the second knock just keep it on the screen until you see the LED lights up, and you'll see how more efficient it will become.
Click to expand...
Click to collapse
Excellent information; exactly what I was looking for. Thanks!
Yeah works good so far!
Gesendet von meinem LG-D802 mit Tapatalk 4
I noticed most of the time when Knock On fails for me is because the phone isn't on a solid flat surface for example while I'm holding it in my hand or while it's on my bed.
This makes me think the accelermeter is used for this feature. So if you have too much "suspension", it won't trigger.
Just my thoughts!
Edit: I just tested with incredibly light touches and it still worked so perhaps it isn't accelerometer enabled. =S
amankapoor4 said:
i go knock knock knock, it almost always helps.
Click to expand...
Click to collapse
yeah, i hear if you say "knock knock" out loud as you do it, it works EVERY time.
Sent from my LG G2 using Tapatalk Pro
Great tip
Exactly what i was looking for although still a bit slow compared with what i had with my Nexus 4 and the touch control app. But at least I just do Knock knock once.
That really does work everytime.
Nice tip. I have been playing around with suggestions that I have seen elsewhere but yours seems to be the most consistent (I've done it 25+ times now in a row with your technique). I've even tried changing the rate at which I do the knocks (fast versus slow) and have also tapped on different parts of the screen. It seems like the key is leaving your finger on the screen on the second knock.
Previously some things that I read to increase the success rate were (each with mixed results):
- Always tap on the top of the phone (where the notification bar would be)
- Always tap three times instead of two
- Tap once and then pause slightly and then tap twice
On a side note, does anyone know how this feature works exactly? Is it simply the digitizer detecting the taps on the screen or is there something else going on?
I tried tapping on the back of the phone. This didn't work so the at least use the touchscreen for the knock knock feature.
Sent from my LG-D802 using xda app-developers app
LoL
Sent from my LG-D801 using xda app-developers app
kamiel said:
I tried tapping on the back of the phone. This didn't work so the at least use the touchscreen for the knock knock feature.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Ya, after doing some more testing, it must be the touchscreen. The reason I thought it may have been something else is I have gotten it to work by tapping in the top right corner of the phone (presumably not on the screen) but that's probably b/c the bezel is so small. I haven't been able to get it to work along the bottom of the phone (over the LG logo).
amankapoor4 said:
i go knock knock knock, it almost always helps.
Click to expand...
Click to collapse
This! Works 99.9% of the time for me
---------- Post added at 11:51 AM ---------- Previous post was at 11:47 AM ----------
Fraxon said:
Im tapping on every other device since I have my LG!
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This as well!!!
I hate it bc that's how I was when the first iPhone came out...made me want to pinch to zoom my laptop screen. Now I find myself tapping the iphone or laptop to unlock but get mad when they don't lol
Knock On feature to turn screen on doesn't work if proximity sensor is covered (try to cover it and tap the screen - it will stay off). Also phone needs a short while to detect the sensor is not covered anymore. So if you pull out your phone out of a pocket and immediately try to turn screen on it simply won't work at first try. Second usually does the job. I've never really had a problem with unlocking the phone while it's on the table or something, when the sensor isn't (or wasn't two seconds ago) covered by anything.
So the reason of our problem is slow response from proximity sensor, it's super fast to detect the sensor is covered, but a lot slower to detect it's uncovered. (You can test it during the phone call - you'll see what I mean).
The solution is just wait a second after you pull out your phone from pocket or after you holding it the way it covers or is near the proximity sensor. I don't think guys triple knocking or keeping your finger on the screen is really helpful. ?
Maybe it can be fixed somehow by our devs, make the proximity sensor reacts quicker.
xegi said:
Knock On feature to turn screen on doesn't work if proximity sensor is covered (try to cover it and tap the screen - it will stay off). Also phone needs a short while to detect the sensor is not covered anymore. So if you pull out your phone out of a pocket and immediately try to turn screen on it simply won't work at first try. Second usually does the job. I've never really had a problem with unlocking the phone while it's on the table or something, when the sensor isn't (or wasn't two seconds ago) covered by anything.
So the reason of our problem is slow response from proximity sensor, it's super fast to detect the sensor is covered, but a lot slower to detect it's uncovered. (You can test it during the phone call - you'll see what I mean).
The solution is just wait a second after you pull out your phone from pocket or after you holding it the way it covers or is near the proximity sensor. I don't think guys triple knocking or keeping your finger on the screen is really helpful. ?
Maybe it can be fixed somehow by our devs, make the proximity sensor reacts quicker.
Click to expand...
Click to collapse
Probably does that so it won't come on by "knocking" in your pocket. Not a big deal for me at all. And the OP's method is working 100% of the time fur me. No need for 3 knocks any more.
I'd like to confirm what don't others have said and say that the most common mistake is tapping too fast.
Correct that the knock on only uses the sensor to avoid turning the screen on in your pocket.
However, if the touch screen constantly listens for these knocks while it is turned off, shouldn't that consume at least a considerable amount of battery?
Sent from my LG-D802 using XDA Premium 4 mobile app
Noam23 said:
What I found out is that the timing of the two knocks is less important, what is more important is to keep the finger on the screen after the second knock. After the second knock just keep it on the screen until you see the LED lights up, and you'll see how more efficient it will become.
Click to expand...
Click to collapse
this is an excellent tip, thanks! I went from knock knock knock knock, to knock knock and hold and its worked every time for me..
Exellent tip thanks!
Works 100% of the time now! :good::victory::laugh:
This tip however, does not apply to turn off the device. Two quick taps (and release) takes care of that always!
Cheers!
noob question
Noam23 said:
What I found out is that the timing of the two knocks is less important, what is more important is to keep the finger on the screen after the second knock. After the second knock just keep it on the screen until you see the LED lights up, and you'll see how more efficient it will become.
Click to expand...
Click to collapse
sorry for this really really dumbass question but when u say "After the second knock just keep it on the screen until you see the LED lights up"
i infer 1 knock (tap and lift finger) and then 2nd one is not actually a knock (tap and lift finger) but just tap and keep ur finger there itself
or
is it 2 knocks and then (after second lift of finger) jst touch the screen again
good i really feel like dumbest dumb on this planet asking this question but please do reply
i dont yet have g2 but planning on buying it so i cant confirm myself what u meant
And it is..... auto brightness!
Not sure why, but after going to 4.4.2 my battery life sucks. Nothing helps. I have greenify, AppOps, disable service, and my phone sleeps like a baby. I then turned auto brightness off and my phone battery is back to normal. I can actually go a full day without having to run for a charger now. My screen on time went from 3 hours to 4 hours. My Android OS and And Kernel(OS) went down a lot too.
To fix the issue with brightness, I downloaded Lux AutoBrightness. But only use the "Adjust On Wake" option. It will only adjust brightness once, when you turn the screen on, rather than constantly accessing the ambient light sensor.
Note that I have a GPE HTC One. Folks on Sense may have varying results.
zerogun said:
And it is..... auto brightness!
Not sure why, but after going to 4.4.2 my battery life sucks. Nothing helps. I have greenify, AppOps, disable service, and my phone sleeps like a baby. I then turned auto brightness off and my phone battery is back to normal. I can actually go a full day without having to run for a charger now. My screen on time went from 3 hours to 4 hours. My Android OS and And Kernel(OS) went down a lot too.
To fix the issue with brightness, I downloaded Lux AutoBrightness. But only use the "Adjust On Wake" option. It will only adjust brightness once, when you turn the screen on, rather than constantly accessing the ambient light sensor.
Note that I have a GPE HTC One. Folks on Sense may have varying results.
Click to expand...
Click to collapse
I feel the same way and it is pissing me off. It sucks so bad that I got another phone. I'll give this a try and report back in a few days.
thanks
citionecent said:
I feel the same way and it is pissing me off. It sucks so bad that I got another phone. I'll give this a try and report back in a few days.
thanks
Click to expand...
Click to collapse
any updates on sense 6.6
ditto
I made the mistake of actually checking and accepting the update from AT&T recently, and hate it. Absolutely hate it. I want my scrolling gallery on the lock screen back, and the battery life is absolutely horrid, burns it up at least twice as fast. Just posting here to affirm to anyone looking - DO NOT UPDATE.
Now to find a way to step back down, or change the rom entirely...
No such thing
abs0lut3z33r0 said:
any updates on sense 6.6
Click to expand...
Click to collapse
---------- Post added at 03:48 PM ---------- Previous post was at 03:45 PM ----------
Folks who have taken the ota have reported this,I would run latest ruu and see if that fixes it.
ghent96 said:
I made the mistake of actually checking and accepting the update from AT&T recently, and hate it. Absolutely hate it. I want my scrolling gallery on the lock screen back, and the battery life is absolutely horrid, burns it up at least twice as fast. Just posting here to affirm to anyone looking - DO NOT UPDATE.
Now to find a way to step back down, or change the rom entirely...
Click to expand...
Click to collapse
My phone's always-on display will turn off. I can't bring it out of it's 'slumber' anyway other than plugging it in. It instantly pops out of sleep and works fine. I'll lock it and while I can see the always-on display the fingerprint reader will unlock it with no problems. This just started in the past hour for me. I've tried resetting the phone and the issue still pops up, and quickly at that.
Are you using a case or screen protector? Could be something interfering with the ambient light or proximity sensor causing the phone to think it's in your pocket at all times?
Edit:
Actually just tested this. Covered the top sensors and the always on display turned off and fingerprint sensor no longer worked just like you described
Sent from my LG-H850 using XDA-Developers mobile app
duckysempai said:
Are you using a case or screen protector? Could be something interfering with the ambient light or proximity sensor causing the phone to think it's in your pocket at all times?
Edit:
Actually just tested this. Covered the top sensors and the always on display turned off and fingerprint sensor no longer worked just like you described
Sent from my LG-H850 using XDA-Developers mobile app
Click to expand...
Click to collapse
You may be right about that. I'm using a lifeproof case and I had just opened it up to clean off the inside (I had shown someone the phone earlier and dog hair found its way to the inside of the case). Funny thing is I turned it completely off and let it sit for a time, as opposed to the restart I did earlier, and it's working alright now. Maybe I just needed to reset it's calibration by resetting it?
Anyone know how to disable this weird dependence on the light sensor? I just don't understand why it would ever disable itself because it's dark.
somethinlike said:
My phone's always-on display will turn off. I can't bring it out of it's 'slumber' anyway other than plugging it in. It instantly pops out of sleep and works fine. I'll lock it and while I can see the always-on display the fingerprint reader will unlock it with no problems. This just started in the past hour for me. I've tried resetting the phone and the issue still pops up, and quickly at that.
Click to expand...
Click to collapse
I read this is a feature of the phone. The always on will turn off in your pocket or in a darkened room. Nice idea since you do not need to be using the juice then. You can test this in a dimmly lit room by cupping your hands over the display to block the light.
marcmarshall said:
I read this is a feature of the phone. The always on will turn off in your pocket or in a darkened room. Nice idea since you do not need to be using the juice then. You can test this in a dimmly lit room by cupping your hands over the display to block the light.
Click to expand...
Click to collapse
Sure, but it won't turn on even when I press the back button. Pretty obnoxious when I'm sitting in a blacked out room and I have to hold it up to the computer screen to activate it.
Yeah, I'm sorry I didn't read the thread carefully. That sucks. I'm in a dark room now watching video. The display turned off, I heard a notification, when I picked up the phone it came on. I do not like that that the led notifications stop. I'm not sure what happens to sound notifications when the always on goes off. I prefer to set the phone silent until a certain time in the AM and then use a sound profile to get notifications and a low volume.
somethinlike said:
Sure, but it won't turn on even when I press the back button. Pretty obnoxious when I'm sitting in a blacked out room and I have to hold it up to the computer screen to activate it.
Click to expand...
Click to collapse
I would return it for another or send it in on warranty.
marcmarshall said:
I would return it for another or send it in on warranty.
Click to expand...
Click to collapse
I'm thinking it was the Lifeproof case I have on it. It all worked fine for a week then when I tested the case for waterproof it failed (the phone wasn't in it). I sent for another one and it seems to be working alright now. Maybe it had something to do with the inside of my case getting wet? I don't know.
Great! Enjoy your phone g why are we still calling these things phone?). I like the G5. Now that we have torur I am hoping their for some nice tweaks.
I've had this happen too and it made my life proof case useless because I couldn't use my phone with it on it I still have the issue once in a while but not nearly as often anymore
Sent from my LGLS992 using XDA-Developers mobile app
I'm pretty sure my S7e had the option to turn the screen completely off when in a pocket or face down, even when AOD was turned on. I can't find any way to do that on the S9. Even on auto brightness it stays on, very dimly. On manual brightness, it stays on at whatever brightness you've set. What's the point of having AOD use even a little bit of battery if you can't see the display at all?
Anyone found a way to shut AOD off in these circumstances?
Try Blocking Touches in the Display Options.
Goofytek said:
Try Blocking Touches in the Display Options.
Click to expand...
Click to collapse
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Is this just a rant? Cause it seems like you've answered your own question.
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
I've been trying to solve this as well. It seems some models have different wording in the block touches option. My tmobile device says something like prevent touches while in a dark place, pocket. I've been told the wording for that option on other models is more like disable screen in dark places, pockets. I hope it gets changed in an update.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
vintagerock said:
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
Click to expand...
Click to collapse
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Nope. If I put it face down on a table or desk in a completely dark room, I can see the light from the screen reflecting off the surface. (My case lifts the screen slightly off the table.) And if I take it out of my pocket, I can see the AOD is very dim immediately after coming out, and then brightens after a split second.
afh3 said:
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
Click to expand...
Click to collapse
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I think I see where at least some of the misunderstanding is now.
What you describe is expected behavior in the dark/low-light scenario.
Note that the AOD turns off (if you've enabled "Block accidental touches" in the display settings) only if the >proximity< sensor detects that the phone is, well, in proximity to something - such as when it is face-down or in a pocket.
If not in proximity to something, what can be expected is that the illumination sensor will simply adjust the AOD brightness (if in the automatic mode) in response to the ambient light it detects - bright in bright light, and dim in low or no light. Just as you've described your experience.
Again, if your "Block accidental touches" feature is on, and the AOD isn't turning off when it is in proximity to an object (in a pocket, face-down, etc.) you may have a defect.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
chickenbb said:
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
Click to expand...
Click to collapse
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
afh3 said:
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
Click to expand...
Click to collapse
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
vintagerock said:
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
Click to expand...
Click to collapse
Verizon branded S9+ [ARBG] here.
afh3 said:
Verizon branded S9+ [ARBG] here.
Click to expand...
Click to collapse
Hmm interesting.
I meant to say att branded is what I have.
vintagerock said:
Hmm interesting.
I meant to say att branded is what I have.
Click to expand...
Click to collapse
You could always factory-reset the device and see if the functionality returns.
With an SD card and a SmartSwitch backup, it's not that painful to reset the phone and get it back to (more or less) the configuration you have right now.
After a reset, I'd probably test it >before< restoring the SmartSwitch backup - just to confirm that it isn't some app that is breaking the AOD turn-off deal.
Best of luck with this.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
vintagerock said:
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
Click to expand...
Click to collapse
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
chickenbb said:
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
Click to expand...
Click to collapse
Yeah I stopped bxaactions and it instantly fixed the AOD problem. What actions do you have your button mapped to?