Database Users

[Q]Cannot adjust brightness in apps

Hi everyone,
I have a Nook Color running CM7.1 off sd card. It was working nicely for 3 months, however, there's something weird happened to me today.
Normally, I use the app "Brightness Level" to change the screen brightness and it worked fine. But it doesn't work anymore. What's worse, apps like the Kindle and the Nook reader, which have the ability to change the brightness, can't change the brightness anymore. The only way that I can change the brightness is go to setting-display-brightness.
But I notice if I use brightness level to change the brightness, it will take effect after waking up the screen the next time.
I have reflash the rom and also tried to fix the permission using rom manager, but no luck.
I will appreciate any help that you guys offer.
Thanks
Richard

[Q] some strange adaptive brightness randomly

helllo
Even if I am using manual brightness set to max - when browsing for example XDA forums which has alot of white - I notice if i drop down the statusbar to check notifications - then go back into xda the screen dims down a notch. (Going from alot of black to alot of white)
This is with all auto-options set to disabled and at max brightness.
This also occured in omega rom, also MF8 base.
And sometimes after a while, it can go back to max brightness randomly. I feel its some sort of adaptive brightness thingy that is misbehaving - even though everything is set to manual.
I tried MGA but its the same thing - . -
and it happens randomly. then after a little while the brightness can go up to max again.......

There's an option in the display settings which is badly named but which turns off this behavior. I think it's named adaptative display or auto tone or something like that. It's the 2nd from the bottom.
Sent from my GT-I9505 using xda app-developers app

fstorm said:
There's an option in the display settings which is badly named but which turns off this behavior. I think it's named adaptative display or auto tone or something like that. It's the 2nd from the bottom.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I already have everything like this turned off

Same problem here. Couldn't find any 3rd party app to address this. Tried almost all brightness related titles in the play store. Hope someone will come out with some dolution for this. It's sooooo annoying!
Sent from my GT-I9500 using Tapatalk HD

+1

Same probleme here....
That made now 2 weeks that I search a solution. All the options of auto-luminosity are disabled, luminosity set to the maximum manually, auto-tons disabled and eco mode off but despite everything, in a dark part, my screen dimmed. It is very disturbing because it dimmed then return in full luminosity etc.... It is a problem but beyond that, I noted that at the time when the automatic adjustment of luminosity occurs, the processor also loses in frequency. It still reaches a maximum at 1.458 ghz or worse at 1.2 ghz.. I tested several Roms: Stock rooted, Google edition 4.3, V8.0 Omega, the result is the same one. I tested several Kernels: Faux123, KT-SGS4 and Adam Kernel. I tried to block the processor at 1.89 GHZ (min + max) at a session of games but at the end of a few seconds, automatic reduction of the luminosity and decreased processor. I think it is not a hardware problem because much of users of Galaxy S4 have this worries.
I become insane with that! And my wife also
Is it possible that a developer integrates a corrective in next a Rom or perhaps make a tweak?
Sent from my GT-I9505 using xda app-developers app

I think i know what's causing the issue.
When I got my phone I noticed the same thing. Apparently its a function of the software deep in the system(at least that's how I understand it). There is no easy way to turn it off. Basically it throttles the screen brightness depending on the average amount of white displayed. The more white the more the brightness is throttled. Not sure if it's to prevent the screen from overheating or to save battery or for both. It's kind of like how the screen can ramp up to a higher brightness when in auto than when in manual. I think it's a thermal issue, but not sure.

2ndammendment said:
I think i know what's causing the issue.
When I got my phone I noticed the same thing. Apparently its a function of the software deep in the system(at least that's how I understand it). There is no easy way to turn it off. Basically it throttles the screen brightness depending on the average amount of white displayed. The more white the more the brightness is throttled. Not sure if it's to prevent the screen from overheating or to save battery or for both. It's kind of like how the screen can ramp up to a higher brightness when in auto than when in manual. I think it's a thermal issue, but not sure.
Click to expand...
Click to collapse
i also think its thermal/power saving related.
a kernel tweak should fix it.

aliendna99 said:
i also think its thermal/power saving related.
a kernel tweak should fix it.
Click to expand...
Click to collapse
I don't know of any kernels which address this "issue". Even if you could fix it with a kernel, I'm not sure you would want to

[Obsolete] Yoga Tab 3 Plus no more Flickering/CABC [ROOT]

Update
Lenovo fixed the issue in the latest update with my initial method which was switching off the CABC in the backlight controller which gives us a brightness boost. So obviously it is not dangerous.
Old Message:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
Instructions:
Use a build.prop editor form the Playstore
Edit the variable "ro.qualcomm.cabl=2" and set it to 0. CAUTION this modifies the system partition. If you want to receive OTAs in the future you will have to flash the system partition with an original image or backup.
Reboot
Technical details:
There are three places where CABC can be switched off:
In the build.prop
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c -> could be dangerous because it increases brightness and the voltages in the backlight controller

matshias said:
So having achieved root, I was looking into the easiest of the issues. Some call it flickering. The "feature" is called CABC and is supposed to save battery. But obviously this comes at a cost of the display constantly adapting the brightness to the content which can cause flickering depending on what you have on the screen.
With root this can be switched off. Alternatively a new kernel could solve this without root. In both cases an unlocked bootloader is still required.
I attached an Automate flow which disables CABC and guess what we get a brightness bump of about 20%. Now the maximum brightness of the display is even a bit brighter than my old Yoga Tab 2 and should be on par with the 3 pro
Make sure that Automate runs on system startup and has root enabled.
Technical details:
There are two places where CABC can be switched off:
In the device tree blob in the boot image/kernel. Specifically the DSI switch on commands in the LCD panel description contain the enabling of CABC
In the LCD backlight driver /sys/devices/soc.0/78b6000.i2c/i2c-2/2-002c
It turns out that if you disable the latter CABC is off even without modifying the former. Of course this requires ROOT to change. This could also be done in the kernel, but would need either a recompile or modifying the init.rd
Click to expand...
Click to collapse
Thanks Now only audio sync issues left for me and tablet will be perfect.

Have you compared the battery performance with and without CABC disabled?

Ashili said:
Have you compared the battery performance with and without CABC disabled?
Click to expand...
Click to collapse
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.

matshias said:
No, these battery life tests take a long time, which I don't have Time is better spent looking into the other issues. It shouldn't be too much of a difference.
Click to expand...
Click to collapse
Yap, I think so. The battery life is long enough. Thank you.

I would think as long as you manually adjust brightness to match your content, you'd get similar results.

I modified the thread to use a less invasive method. I am having issues with my tablet. I am not sure it was caused by this mod but just to be safe I recommend everyone not to use it any longer.

what kind of problem?

chuwq1038 said:
what kind of problem?
Click to expand...
Click to collapse
Everything works (also the display) but the battery drains and the back of the tablet gets warm even when the tablet is switched off. Could be completely unrelated to the mod, but who knows.

With latest official update I have a battery drain issue too. 15% down overnight...

Le Max 2 Black Crush Survey

I would be grateful if people could post their results in this topic after following the instructions.
Okay i posted about this before in the small eui topic but i don't think anyone saw it and it's a general issue that affects everyone so i want to bring it to people's attention.
This phone seems to give a lot of black crush. I have used the stock EUI fw and the small eui CFW and both have it. Black crush is where dark regions of images just turn to solid black so that you cannot see anything below a certain darkness - as you can imagine this is a large issue.
Instructions for the test:
Go here: www.lagom.nl/lcd-test/black.php
You should be able to see all of the squares, 1 - 255
However for me, at highest, retina burning brightness, I can only see down to 7 or so and at a comfortable brightness, only 11 or 12. At lowest brightness I can only see as low as 25 or 20!
Report back how far you can see (at different phone brightness levels including minimum) and also please list what firmware you are using. I wonder if this is an EUI issue or a hardware issue.
Click to expand...
Click to collapse
This is with the screen set to Natural like it should be (the other LE ECO, Vivid etc modes are way over saturated and you actually get colour crush), and even in the other modes it is just like this too.
Because there are these colour modes, i think there must be a way to fix this somehow in eui based fw?
It seems like LE ECO is doing something to mess up the black level and crush all the blacks to make the screen look all contrasty deliberately.
(on a side note, the small eui cfw referred to a change: "Disabled LeEco gamma curve (oversaturation in the daylight)" although i'm not sure exactly the technicalities of it, it didn't seem to help with this issue as on both smalleui and stock x829 it is the same).
One thing i did notice was that on the stock 829 FW, when you first turn the phone on, it DOESN'T have the issue. However when the phone first sleeps it then changes back to the colour mode with the black crush issue (so if it times out to standby or you press the power button etc then you get the problem back).
To me, that seems like the phone is only starting the code the runs the black crush on the first lock screen / standby opportunity.
It wonder if KCAL support could be added to the EUI based CFW? Or if Le Eco's own colour controls (whatever they used to do the colour mode settings) could be user configured. Maybe it is these colour controls that are causing the issue in the first place?
I would be grateful if people could test this and also bring it to the attention of cfw developers (especially eui based).
Thanks

Auto brightness training

I often have to be very persistent in training the phone for brightness in the auto mode. Especially in the evening, when the brightness slider is to the left of the middle. I set the desired brightness, but it is not fixed. You have to do it 10 times or more, and after a minute the brightness again lives its own life. Has anyone come across this on customs ROMs? Everything was great on stock.

Bookworm Yevgen said:
I often have to be very persistent in training the phone for brightness in the auto mode. Especially in the evening, when the brightness slider is to the left of the middle. I set the desired brightness, but it is not fixed. You have to do it 10 times or more, and after a minute the brightness again lives its own life. Has anyone come across this on customs ROMs? Everything was great on stock.
Click to expand...
Click to collapse
Turn off auto brightness Its Simple
(I dont understood your issue propperly...)

ai.Sanaul said:
Turn off auto brightness Its Simple
(I dont understood your issue propperly...)
Click to expand...
Click to collapse
Maybe you don't know auto-brightness can be trained due to users preferences. At least it works on stock.
Or don't you use auto-brightness at all?
I am accustomed to auto-brightness at any time of a day and I like to use it. I don't want to change it mannualy after each changes of circumstances.
However on the custom ROM the process isn't so easy. I just have doubts if it will be successful at all.

Bookworm Yevgen said:
Maybe you don't know auto-brightness can be trained due to users preferences. At least it works on stock.
Or don't you use auto-brightness at all?
I am accustomed to auto-brightness at any time of a day and I like to use it. I don't want to change it mannualy after each changes of circumstances.
However on the custom ROM the process isn't so easy. I just have doubts if it will be successful at all.
Click to expand...
Click to collapse
i,m on Samsung J2 Pro 2018(i use most) with Super Amoled screen and my phone dosent supports auto brightness but i've seen in Redmi 9 Power (second phone i have) that it works according to light around you and cant be trained at all... i think you been talking about another concept, sorry... Tell me about it more if you can so i can learen about it.

ai.Sanaul said:
i,m on Samsung J2 Pro 2018(i use most) with Super Amoled screen and my phone dosent supports auto brightness but i've seen in Redmi 9 Power (second phone i have) that it works according to light around you and cant be trained at all... i think you been talking about another concept, sorry... Tell me about it more if you can so i can learen about it.
Click to expand...
Click to collapse
There is nothing special to say more here. Just in the auto-brightness mode, the user sets the slider to the desired level at any time. This is repeated a certain number of times and after that the phone remembers the new settings and, depending on this, the new auto-brightness algorithm works. The learning process for brightness is endless. You can adjust it anytime to your preference. In any case, it worked fine on stock and the phone memorized new settings very quickly.

Bookworm Yevgen said:
There is nothing special to say more here. Just in the auto-brightness mode, the user sets the slider to the desired level at any time. This is repeated a certain number of times and after that the phone remembers the new settings and, depending on this, the new auto-brightness algorithm works. The learning process for brightness is endless. You can adjust it anytime to your preference. In any case, it worked fine on stock and the phone memorized new settings very quickly.
Click to expand...
Click to collapse
oh! its a cool thing. Thanks

I tried A11, A12, A13 ROMs, and after that I'm on A10 stock again. I think that's the best way for me to keep my nerve sells. Now the autobrigness doesn't even need additional training.