On my old Droid X, custom roms left the option there to set your own thresholds to ambient light as well as custom brightness levels. This was necessary, due to its weird reporting of ambient light to begin with.
On CM9 on the X, that would be under Display in the system settings. With CM10 on the S III, there's no such option. On Samsung's stock rom as well as on CM I find that auto brightness sets the screen too dim. Can those levels be adjusted? Thanks!
it is in cm 11 nighties not cm 10 tho
Slim has the ability to adjust this as well though their default auto setup seems to work well for me.
Related
I saw a thread in the EVO section that said people were using Tasker to create brightness levels with the ambient sensor.
Has anyone seen a rom yet that used the sensor and allows you to create your own brightness levels at certain light percentages?
Ive tweaked it a tad in the extended controls widget but would definitely like to set my own like I did back in CM D1 days
Hi
I recently upgrade my SAGA from CM 7.1 to 7.2, it seems CM team did a great work, less defect, smooth animation and so on. If the Auto Brightness can be as good as which on 7.1, it will be a perfect Rom.
Basically, I use the default setting, except enabled "Allow light decrease" on both version, I found on 7.1, if you move phone from a bright place to a darker place, the screen will get darker gradually, even just from one level to another, it doesn't make you feel flicker. However, on 7.2, it just change the backlight from one level to anther without any transition. I even tried the latest night version built on July 29, same reaction.
Does anyone have the same problem and know why?
Thanks.
The current rom im running that has the problem is cleanrom ultralight, I have had it before on cleanrom and i think some builds of stock roms, dont think CM10 ever gave me this problem.
When I run lux auto brightness and set the slider to a subzero setting, when I run most apps (but not all) the screen goes totally black. One example is setcpu, and it also happens when I launch lux settings. One example where it works fine is nova launcher. If I press the screen on top where the status bar is, and "grab" the status bar, screen reappears until I let status bar go, where screen goes black again.
Basically on most apps using lux in subzero setting causes screen to be totally black but still clickable. Any ideas?
Screen filter app doesnt cause this problem, but lux serves my needs better.
Sent from my SCH-I535 using xda premium
Hey sfetaz,
This is the first I've heard of this issue. It sounds like transparency is being lost somehow. I'd take this issue up with the Cleanrom devs, chances are they changed something they shouldn't have.
Hi,
I have the same issue as described by sfetaz. If I set the brightness to sub-zero (-1 is sufficent), the screen goes to minimum sub-zero brightness (-90) after a few moments in most apps. Sometimes it looks like this happens only if screen content doesn't change for a while. This does not happen if brightness is set to 1 or higher.
I use Lux Lite on a Motorola RAZR HD (XT925) running CyanogenMod 10.2. The issue exists since CyanogenMod 10.2 nightly build 2013-10-19. On 2013-10-18 everything is OK for me.
BBQLog (changelog.bbqdroid.org) shows some display related changes in CyanogenMod on 2013-10-18 and 2013-10-19.
I know 10/20 there was an update for the display. I ran it on PACman with no issues, and I am now on the 10/25 Vanir. No issues with either. I did notice this morning that when I load the default values, that I only load the 2 setting gs I have set, 0 and 2000 or 20000 can't remember off hand. I have my 0 set for -40 and it dims the screen correctly.
This post was made by Vanlandi.
On my RAZR HD (XT925), the problem persisted upto CM-10.2 Snapshot-M1 (2013-11-02).
After flashing CM-10.2 Nightly 2013-11-06, overlays (sub-zero, night/astronomer) mode are functional again.
It had something to do with the overlay. Normal brightness adjustments (>=1) worked as expected. Going to sub-zero or enabling Night/Astronomer Mode, screen content got barely visible after some seconds. When I enabled alternative overlay, the screen went totaly black (sub-zero) or red (night mode). (havn't tried astronomer mode with alternative overlay)
For me, this issue is resolved on the current CM Nightlys for XT925.
Not sure if this is a Nexus5 or Android issue ...
Not sure if this is because I'm moving from an AMOLED to a IPS LCD ...
but I find the Auto-Brightness less of a function and more of a roller coaster ride.
- At home, in a well lit environment, the phone defaults to max brightness, which doesn't seem correct.
- In a dark room, upon wake of the phone, it correctly selects a lower brightness, yet will randomly ping up to max brightness, then settle back down.
The screen on the Nexus5 is absolutely gorgeous, but it just can't seem to select and lock onto the proper brightness level with respect to ambient light.
Is anyone else experiencing auto-brightness wonky-ness? Are there any potential fixes?
Everyone AFAIK suffers from it on nexus 5.
I have a horrible feeling it's a hardware fault, as none of the other Google devices on kitkat have this issue.
yeah the auto brightness seems to be too aggressive, but i'm sure custom roms will have the ability to tweak the auto brightness settings. i think even gravity box has some tweaks for the brightness
If you download Android Sensor Box, you can check the Light sensors. I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings. I'm not sure if it's a rom issue or hardware issue, but my cousin also has a N5 and his worked fine. I tried flashing a new rom and mine still acted up fresh after boot (1st app installed after fresh flash was Android Sensor Box to test).
As a rule I don't use auto brightness. Just get something like lux or install exposed and enable a mod to let you adjust it by sliding your finger across the notification n shade. Easier and faster.
Sent from my Nexus 5 using Tapatalk
I find that autobrightness will auto-turn on, even when i don't want it to.
There is something funky about it, I can either make the phone too dark (using lux) or too bright (using default settings)
I'm still not happy.
Tried Lux, tried adjusting the brightness tables via Gravity Box, used Twilight (to dim at night), no matter what, N5 just wants to be at full brightness all the time!
I had my Nexus 5 in the cinema the other day. The phone was sat in the cup holder by the chair for the most part of an hour when I quickly replied to a text. On turning the screen on it was on full brightness and what's worst is it took around 10 seconds for it to go down. There is definitely something not quite right with it.
Aria807 said:
Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Hi, I have been experiencing this as well, so I attempted to fix this at ROM level. The solution requires Xposed framework, so it works only on rooted devices (related discussion).
Has anyone else had issues with their Adaptive Brightness not working. Toggling the setting has no effect on my display. For such an expensive phone I expect things like this to work.
Yes, it doesn't work that great for me either. I mean I can see it adjusts the brightness "somewhat". But it appears it is not nearly as dramatic as on my Galaxy S7 which would pretty much perfectly adjust the brightness.
I agree that a phone this expensive should do it correctly out of the box. Google please listen.
This is the intended function as I understood it, so I googled it and here confirms. This is not intended to operate the same as auto brightness many other phones use.
In Android L, Google's introduced a new feature called Adaptive Brightness that combines manual and auto brightness. You can manually adjust the brightness level to a state you like. Once it's set, your screen will adjust based on ambient light so it stays at the same brightness relative to the light around you. This way you can set the screen to your preferences without sticking to an absolute level.
Click to expand...
Click to collapse
Been this way a long time. Would this be your first Nexus/Pixel phone?
Source
The problem I have is that every time the phone is rebooted, adaptive brightness is set back to Off, even though it was On when the phone was restarted. Running NDE63V and not rooted.