1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
Related
Is it just me or does the auto-brightness seem to only stay at a certain brightness and never change? On my previous phone, usually when I had auto-brightness enabled, whenever I walked into a dark room, my brightness would lower right away but on this phone, no matter where I go, the brightness seems to always be the same with auto-brightness on. The brightness does not change, even when I walk out with the sun out..
Can anybody confirm this please, I'm thinking of exchanging this unit as it might be defective...
Sent from my LG-P999
Might be your phone. In my moderately-lit office, I can definitely see the screen brightness change when I focus a flashlight on the sensor and then take it away. It's not a huge difference, but definitely observable.
Do you use a case? Is the case blocking the light sensor?
I do not use a case. I have also tried blocking the sensor with my fingers and the brightness just seems to always stay the same... also when I use the power control widget to change brightness and set it to auto-brightness it immediately jumps to that same particular brightness level that I've been stating
Sent from my LG-P999
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
abowmedia said:
I was noticing this as well. It seems to just go to medium brightness and stay there all day. I never notice any changing.
Click to expand...
Click to collapse
That's exactly what I'm experiencing, glad to know I'm not the only one..
Sent from my LG-P999
The change is definitely less noticeable on this phone than my Nexus One, but is there.
I just got the G2x and it does the same for me. It's range of brightness seems to be 20-30% and that's it. I had this problem with stock gingerbread, so I tried rooting and installing CM7, but same problem. So I got it set to manual 10/40/100 on my power control.
My friend said his original droid did this for quite a while until a software update came along a few months later. Maybe we just have to wait till there's a software update to fix it?
Yes, it's borked, always has been.
Mine is broken too. Same happens to me.
Sent from my LG-P999 using XDA Premium App
Same here. It has never worked, as far as I can remember. Depending on where the setting happens to be left at, my battery runs out in just a few hours, or I cannot use it in the car.
Aside: I switched to an original Droid from an iPhone 3G, then onto a G2X. My next phone is going to be an iPhone -- and I'm not coming back to Android until Google figures things out. Android is nice, but I hate being out of date after a couple of months, and having to install unsupported, hacky, half-broken user-built ROMs to stay current with the state-of-the-art functionality.
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
My light sensor appears to work. It does have a fair amout of hysterisis in it otherwise it would drive you nuts.
Sounds like you're either not shining your torch at the actual sensor or yours really doesnt work. It's about an inch to the left of the front camera in case it's the former. It should poll every 4 seconds when on 'auto' brightness, and change the screen accordingly. I find that it works, but it doesnt really change the screen brightness to the best level for viewing. I'm sure there's an app to deal with this although I usually just set it manually. It's easy enough to do.
Oyeve said:
I have been playing with my TF for a little over a month. I updated to 3.1 so I don't know it this is an issue. My problem is the ambient light sensor. It doesnt seem to work. No matter what brightness i have or if it's on auto or not I have never seen my screen get dimmer or brighter in any situation. I put a flashlight right on the sensor and I see nothing change onscreen. Anyone else have this going on?
Click to expand...
Click to collapse
It's perfectly possible the sensor is sensitive to IR or some other wavelength in daylight that's not emitted by your flashlight. The sensor definitely works just fine for me.
I never notice the screen changing brightness (it's designed to gradually change according to the different light exposure so human eyes don't notice it changed, but in reality it did change). When I'm in a car however, if there's trees near by and it blocks the sun every so often, I can clearly see the brightness suddenly shooting up and dropping down. I don't think it works with lamps though (turning on my lights didn't make the display brighter), only light from the sun.
It works quite well now that I'm updated to 3.1. It went through various stages of not working or just messing up back on the 3.0 updates. Now it reacts, increases and decreases and the screen is bright enough.
Mine seems broken too. Strange, because this would be the first thing wrong with me Transformer and it doesn't even seem like a common problem.
This and the browser typing lag alone are making me think of selling it.
Okay, mine is definitely broken.
I just tried it by going out in the balcony and then going in the bathroom and shutting the door - nothing happens.
Seriously Asus, what were you doing when you designed and built this thing? My Tranformer is otherwise perfect - no light bleed, no creaks, no pubes under the screen, no issue at all. Except the light sensor... it seems maybe the perfect Transformer doesn't exist.
mine works
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
On my TF, it takes about a minute for the brightness to change when I move from a dark room to the great outdoors.
Give it a little time for the software loop to kick in
Is this any way to calibrate this sensor? It's works horrible!
Shawn_230 said:
Okay, some progress.
Shinning my HD2's bright dual LED's right onto the sensor actually makes the sensor work.
But still, this thing is apparently not calibrated well because going from outside to a totally dark room didn't change the brightness - it doesn't matter if putting two LEDs right onto the sensor makes it work, that's not why it's there.
Click to expand...
Click to collapse
Do you have a screen protector?
Not to go off topic but I only had keyboard lag when I was using the Asus keyboard Shawn, have you tried the default Android keyboard?
There is an app in the market called androsensor that will tellyou the values for many sensors including the light sensor.
Mine is measured in lux and ranges from 0 to 400 indoors it does not update quickly mine updates every few seconds.
Sent from my Transformer TF101
vladdt said:
Is this any way to calibrate this sensor? It's works horrible!
Click to expand...
Click to collapse
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
It seems to work for me except that it doesn't adjust the levels properly. I can be in a somewhat bright room and the brightness is still at its lowest level, making it difficult to read. However, in broad daylight, the brightness shoots up.
I might try Lux as suggested previously.
lrissman said:
There is a paid program i use and love called lux
Well worth the price imo. It essentially lets you manually adjust the screen brightness for the various light levels over time, remembers these and will automatically put the screen at those levels next time. It alo has some logic too but i cant talk to that.
Sent from my Transformer TF101
Click to expand...
Click to collapse
+1 for Lux - great app
Sent from my Transformer TF101 using Tapatalkr
Hi all, just looking for a suggestion as to what could be causing my issue.
long story short, got phone yesterday afternoon gmt, by time I got chance to play with it was around 9pm, anyway I took a quick video with 960fps, good results but bit grainy, probably due to sun beginning to set.
No problem, says it needs good lighting, I'll try it indoors later, so fast forward a couple hours and I got good lighting indoors, photos and video coming out nice and clear, but whenever I try slow mo I get an effect as if my light is on a strobe setting.
Not sure if it's faulty or just really crappy in artificial light, I suppose I can find out soon enough, but wondered what you guys thought
What kind of light do you have? Certain lights such as flourescent actually "blink" 50-60 times a second depends on what hz the electricity in your country is. It's kinda a given that those blinks will be easily distinguished when you slow down time 32 times. All artificial lights flicker but some can be used in high framerate videos while others can't. Even the sun flickers but there is currently no camera able to record in a framerate high enough to see it. When they film in high framerates in a studio setting they actually sync the flickering with the camera so all frames it records are when the light is on.
I think some types of LED lights don't flicker (but be careful, some do) so you can try with them if you have.
Incandescent lamps won't flicker for sure, you can try using them.
kot5nik said:
I think some types of LED lights don't flicker (but be careful, some do) so you can try with them if you have.
Incandescent lamps won't flicker for sure, you can try using them.
Click to expand...
Click to collapse
Ok cool, its definately the lights in the house, just tried it with curtains open n lights off, no strobe.
So i guess im limited to doing slow mo in sunlight or need to buy new light bulbs lol
I have led lightbulbs upstairs, all downstairs ones are old school filament type bulbs, due to hours i work i best get looking for some flicker free lights
Hey guys
Do you experience also light sensor issues like wrong brightness in certain environments and the sensor is to slow in adjustment?
Yeah i do, mostly in the camera App. It always gets really dark for no reason.
Yeah, i've noticed this in low-light areas, the brightness goes back and forth a lot but mostly stays lower than expected
Light sensor in xperias is adaptive. If you think that your mobile got brightness wrong in a certain environment just correct it by using brightness slider. After couple of days and adjustments it will get every light situation right.
I find this approach to work better then with other brands even though it takes som time to get it just right
Thanks for all the answers. I can also confirm that the expected brightness is lower and after some days off correction the results are getting better.
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.