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.
Related
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.
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).
Hi all!
I have noticed that in most lollipop based ROMs I've tried backlight dims based on screen content. When the image on screen is dark enough the screen brightness drops slightly (or rather jumps down). It's not that noticeable while brightness in settings is set relatively high, but on lower settings it's extremely annoying. It's even more annoying when the jump occurs while scrolling through a webpage! ('cause it happens there too!)
The easiest way to reproduce the problem would be to open the Settings app (preferably using default theme) and slowly sliding notification drawer down. Sliding it back up won't always bring back the brighter.... well... brightness, however a quick slide down and up from status bar should. Sometimes closing the notification area slowly would result in brightness jumping back up. Just give it a try and see...
Another easy way to experience this issue is to set a dark (or even not that dark) wallpaper (happens with this one for example), clean up that homescreen and open and close Chrome (from launcher's dock) repeatedly.
It happens in (doesn't matter if installed in internal memory or internal mass storage):
BlissPop, CyanideL, CM12.1 nightlies, EuphoriaOS, EOS, DirtyUnicorns
It doesn't happen in:
CM11, CM11s, CM12s, (and surprisingly) AOSPA-L and XenonHD
Why is that happening? How can the issue be fixed? It makes every great ROM unusable for me (and therefore I'm basically stuck on CM11s). Don't get me wrong, both AOSPA-L and XenonHD, are great but they are missing a thing or two )
It's a power saving feature. It's called CABC. You can disable it with certain kernel tweaking apps. I have ak kernel with synapse, and there's an option to disable. I always keep it enabled.
Wow, man! That like... saved my One from KitKat forever... Thank you sooooo much! But... where do you know that from?
Is anybody else facing this problem?
Here is the link - https://imgur.com/gallery/nuchOmQ
Have you got the brightness set to automatic? I've seen that behaviour when I have it set but not when I don't.
Alan
alan sh said:
Have you got the brightness set to automatic? I've seen that behaviour when I have it set but not when I don't.
Alan
Click to expand...
Click to collapse
It's not set on automatic
Noticed this when I first got the phone. It went away after a couple of system updates.
I guess it's about the refresh rate, i switched it to 60Hz and the flickering problem went away.
I noticed something similar on the latest open beta even though all the auto adjustment toggles have been switched off.
I fixed mine I guess. Flashed android 10 oos on both slots and used evira kernel. Dunno which one fixed it but so far no flickering or no changing of screen tone/colors.
It's the switch in refresh rate i think, I've been having it on Oxygen 10, don't think I've noticed it on Oxygen 11 beta
Perhaps yeah. but on OB1/a11 it's more noticeable for me so I switched back to the lastest OOS stable(a10) on both slots and running a custom kernel. No issues till now running 90hz.
I just put on the stable 21 and still getting it from time to time. Feels like it's more noticeable yellow tinge than before.