Related
Hi,
Every now and then, while my phone is in my pocket and I do receive a call, I pick it up to answer and the screen is totally unresponsive. I can't slide to answer or do anything at all. I tried to power it off and on again quickly, and then it seemed to get back to normal and I can answer the call. Most of the time this happened during incoming calls. Anybody noticed this behaviour as well?
I read in the HD2 Android forum that it was due to the light sensor. But I'm not sure.
Thanks,
-Gus
I'm experiencing the same issue...
Me too. anyone?
Same here. It happened on the Nexus one as well. Perhaps is a stock android issue.
I have created a bug report. Please help me by staring this report so that it gets Google's attention.
http://code.google.com/p/android/issues/detail?id=13853
Any update/fix on this issue yet? I'm having this problem on stock ICS, CM9 & AOKP as well.
I have this problem even without having the phone in my pocket, when I have it on the table and someone calls me, I have to wait for five seconds before answering, because before that the phone is irresponsive and it FC's, which rejects the call. It gets very annoying.
I've seen a lot of problems on the web about this. It might be the proximity/light sensor.
As a side note, have you cleaned the upper left corner of your screen (where the light sensor is located)? Or at least make sure nothing is actually over it (maybe a case or plastic, screen protector, etc).
Any update on code recently? Are you on stock ROMs or it happens on different custom ROMs/Kernels (good to test with several kernels instead)?
Some apps like AndroSensor or Phone Tester can give you insights about the proximity and light sensor. You might want to check it out and test this with a flashlight or something, and see if values change.
From the bug report, has someone actually tested comment 44 and 46?
Or tested this app DHD Proximity Sensor Recalibrator?
Some have even noticed missed connectors when phone was dissembled (this requires more effort).
Hi, I have an issue slightly different than the ones I've found from searching. I have an unrooted Nexus 5 on Tmobile. the proximity sensor SEEMS to work, it turns the phone off when I talk but it CONSTANTLY hanging up, muting, or putting calls on speaker. I didn't have this issue with my previous nexus 5 and since I've gotten the new one (new out of package, replacement for previous which was stolen) I've dropped maybe 40% of my calls on accident and maybe 10-15% of calls accidentally put on speaker/muted.
Frustrating when you're in a phone job interview and you keep hanging up on the interviewer. I tried using a friends bluetooth ear piece for awhile just to see what would happen and it just did the same thing except in my purse/pocket.
Is this maybe a sensitivty setting I can adjust or should I take it to nearby T-Mobile store to be serviced/replaced?
Diabolicbutterfly said:
Hi, I have an issue slightly different than the ones I've found from searching. I have an unrooted Nexus 5 on Tmobile. the proximity sensor SEEMS to work, it turns the phone off when I talk but it CONSTANTLY hanging up, muting, or putting calls on speaker. I didn't have this issue with my previous nexus 5 and since I've gotten the new one (new out of package, replacement for previous which was stolen) I've dropped maybe 40% of my calls on accident and maybe 10-15% of calls accidentally put on speaker/muted.
Frustrating when you're in a phone job interview and you keep hanging up on the interviewer. I tried using a friends bluetooth ear piece for awhile just to see what would happen and it just did the same thing except in my purse/pocket.
Is this maybe a sensitivty setting I can adjust or should I take it to nearby T-Mobile store to be serviced/replaced?
Click to expand...
Click to collapse
Do you happen to have a screen protector on?
There isn't any settings you can change unless you root. As the other poster said, the most common culprit is a screen protector that doesn't have a hole for the sensor or is misaligned.
aooga said:
There isn't any settings you can change unless you root. As the other poster said, the most common culprit is a screen protector that doesn't have a hole for the sensor or is misaligned.
Click to expand...
Click to collapse
No screen protector but rooting isn't an issue I've just been lazy and haven't done it yet.
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
What app are you using? This looks like a bug in an app, than in Android itself.
I had this problem even before installed any apps. In android l developer preview I didn't have sensors also, so after installed final version of lollipop the first thing I made was check sensors. On kitkat everything worked perfect.
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
i don't have light and proximity sensors too...
i did full wipe and flash stock OTA
hope they will fix it soon
Since upgrading to Lollipop my proximity and light sensor also stops working after a few minutes. It works again after a restart, but only for a few minutes.
I have flashed 4.4.4 again and the problem is not present there. After upgrading to 5.0 again the problem came back.
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
gamer.11 said:
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
Click to expand...
Click to collapse
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
m4nic4ndroid said:
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
Click to expand...
Click to collapse
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I haven't tried any other Lollipop ROMs, I thought about it and I might actually give it a go to see if the problem persists on other ROMs as well, but I would prefer to have stock Android running on my phone, so I'm really hoping for a fix from Google. I'm on few other threads about the same issue, so I know there's a lot of people with the same problem. I had this on the dev preview as well.
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Light Sensor & Proximity Sensor Error
m4nic4ndroid said:
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Click to expand...
Click to collapse
The Same Problem For Me As Well, My Light Sensor & Proximity Sensor Arent Working. I have downloaded the Final Image from Google Website for 5.0 hammerhead. But still the problem persists.
Nyk
After I got the Play services (with secure locations) update two days ago my light and proximity sensors are gone too. They will work for a while after reboot, but eventually they die.
All other sensors are working fine and only other updates have been to Skype, SwiftKey and TuneIn Radio.
Edit: I'm on stock OTA, no root and never unlocked the bootloader.
Sent from my Nexus 5 using Tapatalk
So uninstalling the play services update resolve the issue? I'm back to KitKat as without light sensor I find uncomfortable to use the phone. Will await the fix before moving to lollipop..
Sent from my Nexus 5 using XDA Free mobile app
"Clean install" using factory images? I did, no issues here.
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Did you reboot after disabling update?
Sent from my Nexus 5 using XDA Free mobile app
rawimage said:
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Uninstalling Play Services and Play Store update made no difference here. Problem still persists.
michalnied said:
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
Click to expand...
Click to collapse
Hi I have the same problems . Sensors are working after restarting my phone random time. Also you can read here
Uninstalling Play services didn't do it for me either. Sensors work for approximately 4-5 hours then they die.
Sent from my Nexus 5 using Tapatalk
Installed Play services update again after a few days and now my phone has been running fine for 50 hours with all sensors working 100%.
Sent from my Nexus 5 using Tapatalk
Hi all,
I've bought a brand new Mi Mix 2S device, and I'm having some issues with the proximity sensor. When accepting a phone call or listening a WhatsApp audio message the screen goes black. It won't light up again until the person calling terminates the call; with WhatsApp audio message it's still worse: I have to lock the screen and unlock it again in order to see something. I've tried to recalibrate it using the hardware test (*#*#*****#*# - I can't remeber the precise number atm), but in the proximity sensor menu the reading is 0 no matter of the sensor covering.
Is there any way I can solve this issue ? Is it a hardware problem ?
Thanks in advice
I have the exact same problem. It seems to happen frequently but not 100% of the time.
rainbow99 said:
I have the exact same problem. It seems to happen frequently but not 100% of the time.
Click to expand...
Click to collapse
I'm wondering if it could be related to the glass screen protector interfering with the ultrasonic proximity sensor...
Drogor said:
I'm wondering if it could be related to the glass screen protector interfering with the ultrasonic proximity sensor...
Click to expand...
Click to collapse
I think it is. Because mine started doing that when I dropped the phone once on the road. But as the other user said it doesn't do that 100% of the time
Sent from my Mi MIX 2S using Tapatalk
fopoku2k2 said:
I think it is. Because mine started doing that when I dropped the phone once on the road. But as the other user said it doesn't do that 100% of the time
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
My protector is not broken though... anyway where is the sensor positioned ?
Drogor said:
My protector is not broken though... anyway where is the sensor positioned ?
Click to expand...
Click to collapse
No idea
Sent from my Mi MIX 2S using Tapatalk
fopoku2k2 said:
No idea
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
The thing is mine does that 100% of the times... I fear it might be a hardware problem
Drogor said:
My protector is not broken though... anyway where is the sensor positioned ?
Click to expand...
Click to collapse
Here's a teardown of the Mix 2s and it shows the location of the sensor.
https://www.myfixguide.com/xiaomi-mi-mix-2s-teardown/
No problems with mine but I've only had it a couple days, I do have a glass screen protector coming and will see if that makes a difference once installed.
Thanks to everyone for your help. I've rebooted the phone several times and after the second reboot the calibration seemed to work. Now the sensor seems to work properly (at least at this very moment ).
Seems it was a software issue
How do you perform a proximity sensor harware test?
To the ppl having a problem:
Does your screen protection glass has holes for the sensors??
Thanks for information
Hello all,
My mix2s has this situation too, and does not have screen protection, if anyone finds a solutions please post here.
Thanks,
mine was working well until i flashed the new global beta. nownproximity sensor not working for me.
I tried nearly everything to fix the issue with my proximity sensor, which completely stopped working.
I have also created a poll on xiaomi.eu forum (https://xiaomi.eu/community/threads...nsor-work-as-in-non-ultrasonic-devices.46293/) in order to understand which was the normal functionality of the ultrasonic sensor. Indeed, I suspect that my sensor never worked as expected, as the screen often switched on during calls even if no notifications were received.
According to the hardware test, the sensor doed not work at all.
I tried to flash the persist.img partition but nothing as changed.
Instead, all the other sensors are working fine.
In order to understand if mine and yours is an hardware or software issue, could you please report if you are 100% sure that before flashing a custom rom the ultrasonic sensor worked properly?
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
esteras said:
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
Click to expand...
Click to collapse
As I wrote, my guess is that I also have an hardware issue. The sensor never worked properly and eventually stopped working. The fact that I also flashed a rom during that period is just a coincidence.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
esteras said:
I had exactly the same problem (sensor not working all the time or anormal behavior) and it was a hw fault. My solution was a warranty replacement. Now everything works fine.
Click to expand...
Click to collapse
One last question: how does the ultrasonic sensor work now? Just like non-ultrasonic sensors? The screen remains switched-off as expected during calls?
guildamx said:
As I wrote, my guess is that I also have an hardware issue. The sensor never worked properly and eventually stopped working. The fact that I also flashed a rom during that period is just a coincidence.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
One last question: how does the ultrasonic sensor work now? Just like non-ultrasonic sensors? The screen remains switched-off as expected during calls?
Click to expand...
Click to collapse
Now it works as the other phones that I had, very fast. Switch off when I put it near my ear and switch on again when I put it far away. There isn't any difference.
esteras said:
Now it works as the other phones that I had, very fast. Switch off when I put it near my ear and switch on again when I put it far away. There isn't any difference.
Click to expand...
Click to collapse
Thank you very much.
Since my sensor never worked that good, I suppose it was faulty from the beginning.
I use to have that problem too, but then I realized that could be a problem with the case I was using. I took it off and now I don't have any issue with the sensor
rodaven said:
I use to have that problem too, but then I realized that could be a problem with the case I was using. I took it off and now I don't have any issue with the sensor
Click to expand...
Click to collapse
Thank you but it is not my... case
I use the one provided in the box by Xiaomi and moreover the issue is there even if I remove the case.
Hi guys,
Noticed a very interesting thing today: suddenly a white light started to pulse next to the front cam every time I was tilting the phone. It was quick 3-4 pulses with strict intervals as if a sensor was working. It didn't pulse when phone was in a fixed position, only when tilting, in all apps.
A reboot fixed this, but I wonder if there is any sensor there that activated because of something? Never experienced this before!
Any thoughts what it can be? Thx.
Sounds like proximity sensor to me.
znel52 said:
Sounds like proximity sensor to me.
Click to expand...
Click to collapse
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
VirtualWaver said:
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
Click to expand...
Click to collapse
Im going to try this out myself next week and see what's going on. Mine ain't coming until Monday.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
blackhawk said:
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
Click to expand...
Click to collapse
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Limeybastard said:
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Click to expand...
Click to collapse
Even at full brightness because it's flashing, it's duty cycle is less than the surrounding pixels plus it will "flash" by darkening its pixels depending on screen color.
If it has specialized IR emitters I could see that happening maybe; if there's a design or manufacturing flaw.
Because it's flashing visible light it would be hard to use a cam to detect IR... which is how I normally check IR emitters.
While it was easily seen on the Note 10 i can't see it on the Note 20
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
blackhawk said:
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
Click to expand...
Click to collapse
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Nastrahl said:
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Click to expand...
Click to collapse
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
warriorvibhu said:
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
Click to expand...
Click to collapse
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
blackhawk said:
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
Click to expand...
Click to collapse
Trash apk ? Sorry i meant the built-in adaptive brightness.
---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------
blackhawk said:
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
Click to expand...
Click to collapse
I personally never heard about it. Thanks for the insight
Nastrahl said:
Trash apk ? Sorry i meant the built-in adaptive brightness"
I personally never heard about it. Thanks for the insight
Click to expand...
Click to collapse
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
blackhawk said:
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
Click to expand...
Click to collapse
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Nastrahl said:
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Click to expand...
Click to collapse
Thank you
I'll take a look at it. I'm running on dark mode but since it's Pie it's not native to all apps like Gmail which burns my eyes out.
*I'm playing with it. It will run on Pie. It takes some time to set up but definitely has potential.
Haven't been able to fairly gauge it's configured battery usage.