I've looked at past threads, but found no resolution to this.
I'm running voodoo colour with deep black settings and everything looks great, except right before the screen times out it will dim to its lowest setting and force the amoled panel to turn a sickly yellow/green hue.
I would like to disable the dim aspect and just let the screen time out by shutting off completely. Is there anyway to do this? I'm running the latest version of Pixel Rom with Air Kernel 4.2. I don't have auto-brightness enabled.
i am having the same issu i dont have to yellow tint in low light
but still i whould like to disable the dim it is disturbing my daily use of the device
i too dont see any point for this time out before the screen turns of
and i cant understand why when plying a game i need to touch the screen every 25 sec to get rid of the dim
thanks
I remember seeing something about auto-brightness light sensor tweaking back when I was using NV rom last year but I don't know if that would apply or not.
Does anyone know if the custom apps on the market avoid this?
edit: Tried Tasker for a full screen-off solution, and a bunch of other apps. Wasn't able to get the results I wanted :I
I have a Samsung Captivate and I am running a kernel with voodoo color support with this same issue.
The first post of this thread shows a possible solution - http://forum.xda-developers.com/showthread.php?t=1002090
I flashed the pixel os android 10 in my redmi note 7 and now i am facing screen lock issue my phone does not accept any screen lock that i am trying to apply on it plzz help me
Related
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).
I'm not sure what it is with this phone's auto brightness but comparing it to my old nexus 5 I can see that this phones screen is always darker. I know autob its working because I sometimes see it change automatically but its just always set to be way too dark. I
f anyone else has this problem or know how to fix it without having to manually adjust the brightness that would help a ton.
Also if you changed your lux levels please post those.
On and also I do have the official screen protector on if that matters.
genardas said:
I'm not sure what it is with this phone's auto brightness but comparing it to my old nexus 5 I can see that this phones screen is always darker. I know autob its working because I sometimes see it change automatically but its just always set to be way too dark. I
f anyone else has this problem or know how to fix it without having to manually adjust the brightness that would help a ton.
Also if you changed your lux levels please post those.
On and also I do have the official screen protector on if that matters.
Click to expand...
Click to collapse
Yes, it is a little dark, you can go to settings/display & light and hit the little gear icon, hit adjust and set up the screen brightness you like depending on the ambient light.
i am facing that some time while scrolling brightness increases for some millisecond and come to normal. i found that is twitter, some huge page in browser page.
can any one tell what could be the issue hardware or just a software bug which can be fixed with other rom installation.
I noticed my AOD has a slight shade of magenta which is making it harder to see. Anyone else have this issue? Or is it just the norm? It's odd it'll show as plain white if I enable double tap to view but once I set it to always on it turns pinkish. Just the pixels that are on. (Not the background)
I've tried safe mood, fac reset, downgrading to 8.1 , going back to 9 , rooting , then clean flash 9 and it's still pink. It's a very odd behavior since it's only link only when I enable it via "always on" I'll notice it flashes pretty rapidly. I've tried to adb adn set custom brightness via that way all it does is fix the flicker but not the hue.
Any suggestions would be greatly appreciated.
Note: The following post was posted on Samsung Members: I thought I'd post it on here to raise awareness: and to get help.
Recently brought a Samsung Galaxy A51 for a family member, and upon setting the fingerprint and activating the blue light filter: I realised everytime I'm on the lock screen, there's no blue light filter! Upon unlocking, the filter is applied to the rest of the phone. I read on the Samsung forum when someone asked why, that it's like that due to the fingerprint. So why can't the rest of the screen, apart from the fingerprint area, have blue light filter?! Am I expected to burn my eyes whilst trying to look at the time in the middle of the night?! I'm sure with Amoled panels, that each pixel can be controlled, so why hasn't this been applied? Samsung needs to step up their software game as a simple error like this gives a terrible experience. Not the first time something like this occured on a Samsung device.*Furthermore, I tried a third party blue light filter: Twilight which worked fine with the fingerprint. Rather use the in built one as it's lots better.
I'd appreciate any help, thanks!
You can set a Bixby routine to lower the brightness and turn on blue light filter at certain time.
I really like the lockscreen with full brightness, to enjoy the beautiful images of the dynamic wallpapers.
ramping said:
You can set a Bixby routine to lower the brightness and turn on blue light filter at certain time.
I really like the lockscreen with full brightness, to enjoy the beautiful images of the dynamic wallpapers.
Click to expand...
Click to collapse
Thanks for the suggestion. I still think samsung should e automatically implement something to make the lock-screen, eye-frienly at night time. As the screen is really nice, but it hurts your eyes at night. They really,
really need to fix the software as there are a few issues: one of which is that it's buggy.