Develop Bugs

[TWEAK] Automatic Brightness levels!

Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I use the following settings:
Light sensor filter enabled.
Window length 10 seconds.
Reset threshold 400 lux.
Sample interval to 0.5s.
Light levels use custom checked.
Screen dim level, not sure what it is for but I have it on 1 instead of 20. ((edit: I found what it is for, it's the step size the filter takes? Or not? :s))
Edit other levels...
Number of levels: 18
0 1
10 1
117 17
225 33
272 49
320 65
480 80
640 96
960 112
1280 128
1940 144
2600 160
4200 175
5800 192
6900 207
8000 223
9120 239
10240 255
Allow light decrease checked.
Decrease hysteresis to 10%.
I hope people like my light settings, if you don't please tell me why

Reasons why some settings should be altered:
Reset threshold, should be able to set to 100 and 200 lux. At the moment if you walk into light it takes the filter some time to go up, so 100 or 200 lux would trigger a reset faster. Also the sensor starts at 225 lux so why 400 as a minimum in the first place?
Window length, as for the above, if you walk into light a smaller window length would help put brightness up much quicker in combination with a smaller reset threshold.
If the above two settings could be added in CMParts/ODParts that be great as the filter would be much more responsive to short period light changes. For example if you go from outside to inside or visa versa.
And maybe it would even be a better idea to remove the whole custom light levels and add a linear function to it to go with the filter (configurable) and just have 254 steps (1-255) over 10-10240?
Adding 254 steps yourself is ... A PAIN ><

English please
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.

shazan said:
guys i know there is a problem with the light sensor in desire and i have the same case with mine it this is all about it please let me know how to fix it please.
Click to expand...
Click to collapse
What ROM are you using? CyanogenMod and forks of it (OpenDesire, DeFrost etc) have a custom preferences menu where you can check out the light sensor values. That is when you leave the filter off and goto edit other levels. Hold your phone in line with a TL light and it should jump to 1280.
Do you see the top most number change when light changes?

Call me crazy, but I am ><
I put the whole table into the automatic backlight custom levels: http://www.linux-box.nl/~sjoer/1to255/1to255.php
And it works really well with light changes, it should work even better if reset threshold can be lower (200 or maybe 100) as it will respond to bright light <> no light much better.

how did you did that?
without typing lol

This is insane..... so much trouble for such a simple task. Automatic Brightness. On winMO i used g-lite wich was satisfacatory. A have the desire for a month now. I searched from a similar soft and i didn't find. But i'm not gooing to try this much trouble for something that should be easy. Thank you.

Im sorry but....HOW do I apply this ?

Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil

philje123 said:
Can this be applied to other roms?
I am using Pinky desire and would love to do this.
Phil
Click to expand...
Click to collapse
yes and for stock roms please

The screen minimum value is 10-255, so how can I set "1" to the first 2 levels?
I set 10, and I like the settings overall.

sfjuocekr said:
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
First off, "10 1" is redundant as you already cover that from 0 to 9. So 17 levels should be enough. Second, on the last line "10240 225" you probably meant "10240 255". Testing your settings with these modifications now. I find you have a lot of levels, probably can do with less to reduce flickering, but as I said, testing these first.

Can we use these settings in a Sense rom and if yes how?What file do we have to edit?

so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.

Can someone please make a post about how to use this (and especially on Sense Roms)? So far it only shows us "which sensor-level should be what brightness" but it doesn't provide any information on how to apply it.
I assume CM either has an app for this installed (if so, please tell us WHICH so we can use it too) or a shell-script in background (if so, tell us WHICH) adjusting the settings.

Could anyone post a how-to use these settings?
Edit: Nvm, it's under: Cyanogen Settings.
Btw under "Edit other levels" you should only change the boxes that's under "Lower"? You shouldn't touch "Screen" and "Button"?

Trying this out, and will see how it goes. Only have 5 levels on my current setup, so this should be a lot smoother

snudel said:
so useless guys.
setup max brightness and enjoy the brilliant screen.
it takes less battery than this tool to constantly check your ambient brightness.
Click to expand...
Click to collapse
Is that true?

any more improvements?
and how can i backup this setting?
i wont to input it again when i flash a new rom :-(

sfjuocekr said:
Issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2298
After toying around with the automatic brightness I'm now here to share my settings ...
I hope people like my light settings, if you don't please tell me why
Click to expand...
Click to collapse
Since the source code of Sense kernels is available now, would it be possible to write the tool for Sense ROMs too? You sure would do a lot of people a big favor

How to IMPROVE OG Pro PERFORMANCE & FUNCTIONALITY!

Hi everyone,
Now I know the OG pro has good ram and an amazing processor, and I'm not having any problems with lag or anything. This is more of a thread where I get to see what users have done to their OG pro and/or what apps you have downloaded to improve the phones performance and functionality.
Please post and modifications you have made, apps you use or have used, and how you improved the performance and functionality of the OG pro.
P.S. eventually sometime down the line someone might encounter some performance issues due to some random reason, so by getting this posted started now they will have a thread they can read through in order to improve their phones performance.
THANK YOU!:fingers-crossed:

Since I created the post I figured I would be the first to post a reply.
Currently under the battery setting I have Quad core control turned on in order to optimize my battery saving. This is one option you can turn off in order to IMPROVE PERFORMANCE.
AnTuTu CPU and MEMORY benchmark
Quad core control on Quad core control off
Total: 9786 Total: 10680
RAM: 3161 RAM: 3255
CPU Integer: 2577 CPU Integer: 3367
CPU float: 4048 CPU float: 4058
*I'm not that familiar with AnTuTu but as far as I know the difference in the scores is an increase of 9.1% which is a fairly good gain.
I also use the app named swapps which allows me to switch between apps much faster than having to hold the home button down to get the task menu and switch from there.
I hope this helps!

let's see.
cpu controller on
rooted
tibu to freeze/remove a ton of apps.
apex launcher
thermal throttling off
juice defender ultimate to handle battery & screen.

scott0 said:
let's see.
cpu controller on
rooted
tibu to freeze/remove a ton of apps.
apex launcher
thermal throttling off
juice defender ultimate to handle battery & screen.
Click to expand...
Click to collapse
how long is the battery lasting on average under these conditions ???

zohaer21 said:
how long is the battery lasting on average under these conditions ???
Click to expand...
Click to collapse
so long that i can't even guess. i'm quite stunned. i'm not running nay 3d games yet but i do a lot of reading on this so the screen is on, i also have the face recognition running, i can see when the screen tries to time out and the fr kicks in and keeps it lit.
the built-in auto screen dim never worked for me, i have jd brightness set to - 20% 45% 150% and it handles outdoors sunlight much better now also.
the phone last all day long with absolutely no worries at all, i would guess it could easily go 2 days with no worries but i've been plugging it in at night, i like to try to stay close to 100%.

scott0 said:
so long that i can't even guess. i'm quite stunned. i'm not running nay 3d games yet but i do a lot of reading on this so the screen is on, i also have the face recognition running, i can see when the screen tries to time out and the fr kicks in and keeps it lit.
the built-in auto screen dim never worked for me, i have jd brightness set to - 20% 45% 150% and it handles outdoors sunlight much better now also.
the phone last all day long with absolutely no worries at all, i would guess it could easily go 2 days with no worries but i've been plugging it in at night, i like to try to stay close to 100%.
Click to expand...
Click to collapse
I think you have to turn on auto brightness in the video app that's how I got mine to work
Edit. I made a video during the video play back I hit menu then settings then brightness then checked the auto box that turned on my auto bright
Sent from my LG-E980 using xda premium

nthknd said:
I think you have to turn on auto brightness in the video app that's how I got mine to work
Edit. I made a video during the video play back I hit menu then settings then brightness then checked the auto box that turned on my auto bright
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
i just tried this as well, it adjusts the screen brightness on the video but when i check the screen brightness in the drop down the auto box is not checked.
is your's checked in the drop down?

scott0 said:
i just tried this as well, it adjusts the screen brightness on the video but when i check the screen brightness in the drop down the auto box is not checked.
is your's checked in the drop down?
Click to expand...
Click to collapse
Mine isn't check there either but once you check it you'll see that your screen will dim when you adjust the level so check that box
Sent from my LG-E980 using xda premium

Kernel mods - are display gamma correction and refresh rate overclocking possible?

Got a V30 a few months ago - brilliant device but not that happy with the display - it has the very annoying "black crush" issue for me.
Short explanation (it's better you don't read - trust me it can be very annoying when you're aware of it):
The lower the screen brightness is set, dark grays and dark colours are shown completely black when they shouldn't - this is very annoying as the detail in darker areas of images completely disappears (it's bad for all content - pictures, videos, games). It can vary from device to device, even on the same models.
This is an issue at varying degrees on other OLEDs too such as Pixels', Samsung, OnePlus; but Apple and Huawei seem keep it mostly under control. Funny enough my old Galaxy S4 does not really have this issue.
Google and Samsung managed to partially fix it (completely for some users) with software updates, so this should be possible for us too especially as V30 has the exact same display as Pixel 2 XL which got some improvement via update if I remember correctly.
There are apps and tricks which claim to improve this but while they can help a bit they bring in other issues.
Looking for fixes I found this V30 kernel - "Savitar-OC-kernell" - a claimed feature was refresh rate OC (80Hz). The thread is closed, the links are dead, the dev didn't respond (PM'd months ago) and there is no video proof of it so I can't really be sure that it worked well or at all. But if true then it means there is at least a way to get very low level control of the display panel.
I have zero experience with kernel/ROM development but I can get technical so I did some (probably bad) research myself. Downloaded the kernel source from LG.
Found some interesting files here:
...\kernel\msm-4.4\drivers\video\fbdev\msm\lge\joan\
...\kernel\msm-4.4\arch\arm64\boot\dts\lge\
My guess is that V30's panel is "sw43402" (I think that's the driver IC model, same as 2 XL) - there are multiple files for it, with values for front/back porch, clk etc. which is what I suspect was modified for the refresh overclock.
Also found multiple entries/tables? for "gamma" and "blmap" (backlight map?) values which is what I hope can be used for a fix for the black crush.
My hope is that there is a way to tweak the gamma curves or some other form of display mapping. At 100% brightness my phone display is almost perfect, zero black crush. However as I set the brightness lower the black crush amount varies (it's not linear or exponential, it's "jumpy") which looks like there is some sort of mapping trying to compensate.
I'd love to hear your opinion especially if you have any experience with this stuff or if you can forward this to someone you know could answer. I would appreciate if you can tell whether you think this is possible and whether what I found is on the right track. Thanks for reading all this.

gamma correction
Click to expand...
Click to collapse
your best bet is via KCAL or KLAPSE in custom kernels
recommendation-based is to not go lower than 30 or 50% in brightness otherwise you'll lose details
refresh rate overclocking
Click to expand...
Click to collapse
not worth it, there's no true close hardware manipulation possible (like with Exynos kernel source) also OLED panels are sensitive (high brightness, burn-in, etc.) and (relatively?) short-lived already - why shortening life even more ?

Thanks for the reply.
KCAL seems to be a step in the right direction however I don't think I can find any kernel for V30 that has it. I'll look into KLAPSE but it seems that it won't help "out of the box" without some lower level modifications.
Refresh rate - sure it may not be very practical but I don't think it's that dangerous (One example being the overclocked Note 3 displays in the Oculus DK2 back in 2014). 80Hz may be too much (and may be ghosting) but even 67-72 should make a noticeable difference. And why not have it as an option - for science - or for people that plan to upgrade soon and want to go crazy with it.
zacharias.maladroit said:
there's no true close hardware manipulation possible
Click to expand...
Click to collapse
Can you please expand on this? What about the files I mentioned? An example snippet from
dsi-panel-sw43402-dsc-qhd-cmd-dv2_0.dtsi
Code:
[FONT="Courier New"]...
&mdss_mdp {
dsi_sw43402_dsc_qhd_cmd_dv2_0: qcom,mdss_dsi_sw43402_dsc_qhd_cmd_dv2_0 {
qcom,mdss-dsi-panel-name = "SW43402 cmd mode dsc dsi panel";
qcom,mdss-dsi-panel-type = "dsi_cmd_mode";
qcom,mdss-dsi-panel-framerate = <60>;
qcom,mdss-dsi-virtual-channel-id = <0>;
qcom,mdss-dsi-stream = <0>;
qcom,mdss-dsi-panel-width = <1440>;
qcom,mdss-dsi-panel-height = <2880>;
qcom,mdss-dsi-h-front-porch = <92>;
qcom,mdss-dsi-h-back-porch = <48>;
qcom,mdss-dsi-h-pulse-width = <32>;
qcom,mdss-dsi-h-sync-skew = <0>;
qcom,mdss-dsi-v-back-porch = <25>;
qcom,mdss-dsi-v-front-porch = <10>;
qcom,mdss-dsi-v-pulse-width = <1>;
...[/FONT]
I'd imagine something should happen if these are modified, or do you think nothing would happen? Some gamma and blmap tables are also further down in the file.
However there are multiple similar files in that folder which is a bit confusing to me. Any clue if there's public documentation on this or at least what to search for to understand it further?

cLick1338 said:
Got a V30 a few months ago - brilliant device but not that happy with the display - it has the very annoying "black crush" issue for me.
Short explanation (it's better you don't read - trust me it can be very annoying when you're aware of it):
The lower the screen brightness is set, dark grays and dark colours are shown completely black when they shouldn't - this is very annoying as the detail in darker areas of images completely disappears (it's bad for all content - pictures, videos, games). It can vary from device to device, even on the same models.
This is an issue at varying degrees on other OLEDs too such as Pixels', Samsung, OnePlus; but Apple and Huawei seem keep it mostly under control. Funny enough my old Galaxy S4 does not really have this issue.
Google and Samsung managed to partially fix it (completely for some users) with software updates, so this should be possible for us too especially as V30 has the exact same display as Pixel 2 XL which got some improvement via update if I remember correctly.
There are apps and tricks which claim to improve this but while they can help a bit they bring in other issues.
Looking for fixes I found this V30 kernel - "Savitar-OC-kernell" - a claimed feature was refresh rate OC (80Hz). The thread is closed, the links are dead, the dev didn't respond (PM'd months ago) and there is no video proof of it so I can't really be sure that it worked well or at all. But if true then it means there is at least a way to get very low level control of the display panel.
I have zero experience with kernel/ROM development but I can get technical so I did some (probably bad) research myself. Downloaded the kernel source from LG.
Found some interesting files here:
...\kernel\msm-4.4\drivers\video\fbdev\msm\lge\joan\
...\kernel\msm-4.4\arch\arm64\boot\dts\lge\
My guess is that V30's panel is "sw43402" (I think that's the driver IC model, same as 2 XL) - there are multiple files for it, with values for front/back porch, clk etc. which is what I suspect was modified for the refresh overclock.
Also found multiple entries/tables? for "gamma" and "blmap" (backlight map?) values which is what I hope can be used for a fix for the black crush.
My hope is that there is a way to tweak the gamma curves or some other form of display mapping. At 100% brightness my phone display is almost perfect, zero black crush. However as I set the brightness lower the black crush amount varies (it's not linear or exponential, it's "jumpy") which looks like there is some sort of mapping trying to compensate.
I'd love to hear your opinion especially if you have any experience with this stuff or if you can forward this to someone you know could answer. I would appreciate if you can tell whether you think this is possible and whether what I found is on the right track. Thanks for reading all this.
Click to expand...
Click to collapse
The savitar kernel dev is still active and made a new kernel, tachyon kernel that is, but he remove the 80hz because it doesnt work on real life test. All the kernel for v30 have kcal btw (there are only 2 kernel which is ceres (or lunar or orion or any other name that the dev like to named before) by @zacharias.maladroit and tachyon ( or some other name that i swear i cant remember) by @darkidz555
---------- Post added at 02:03 PM ---------- Previous post was at 01:59 PM ----------
cLick1338 said:
Thanks for the reply.
KCAL seems to be a step in the right direction however I don't think I can find any kernel for V30 that has it. I'll look into KLAPSE but it seems that it won't help "out of the box" without some lower level modifications.
Refresh rate - sure it may not be very practical but I don't think it's that dangerous (One example being the overclocked Note 3 displays in the Oculus DK2 back in 2014). 80Hz may be too much (and may be ghosting) but even 67-72 should make a noticeable difference. And why not have it as an option - for science - or for people that plan to upgrade soon and want to go crazy with it.
Can you please expand on this? What about the files I mentioned? An example snippet from
dsi-panel-sw43402-dsc-qhd-cmd-dv2_0.dtsi
Code:
[FONT="Courier New"]...
&mdss_mdp {
dsi_sw43402_dsc_qhd_cmd_dv2_0: qcom,mdss_dsi_sw43402_dsc_qhd_cmd_dv2_0 {
qcom,mdss-dsi-panel-name = "SW43402 cmd mode dsc dsi panel";
qcom,mdss-dsi-panel-type = "dsi_cmd_mode";
qcom,mdss-dsi-panel-framerate = <60>;
qcom,mdss-dsi-virtual-channel-id = <0>;
qcom,mdss-dsi-stream = <0>;
qcom,mdss-dsi-panel-width = <1440>;
qcom,mdss-dsi-panel-height = <2880>;
qcom,mdss-dsi-h-front-porch = <92>;
qcom,mdss-dsi-h-back-porch = <48>;
qcom,mdss-dsi-h-pulse-width = <32>;
qcom,mdss-dsi-h-sync-skew = <0>;
qcom,mdss-dsi-v-back-porch = <25>;
qcom,mdss-dsi-v-front-porch = <10>;
qcom,mdss-dsi-v-pulse-width = <1>;
...[/FONT]
I'd imagine something should happen if these are modified, or do you think nothing would happen? Some gamma and blmap tables are also further down in the file.
However there are multiple similar files in that folder which is a bit confusing to me. Any clue if there's public documentation on this or at least what to search for to understand it further?
Click to expand...
Click to collapse
Btw, @zacharias.maladroit motto for kernel development is stability and longevity so asking him for OC is not possible

Quick update, tried KCAL, only helps a little bit, but even on the most extreme settings it's barely effective.
KLAPSE has no means of improving it but I'm thinking something could be done by using the "brightness based scaling" and unlocking the "dimming" function to be able to actually brighten the image too. Currently it only goes from 20% to 100%, so it has to be able to go over 100% which I'm not sure is easy or possible.

Xiaomi Redmi Note 5 Automatic Brightness too low

Hi. Im using Xiaomi Redmi Note 5 with xiaomi.eu 9.9.3 and KangarooX r5.1 kernel installed and I am bothered by automatic brightness which doesn't work well. Brightness set by the phone is too low for me and I need to manually correct it but the worst thing is that after each screen blanking the phone sets the brightness again wrongly.
I asked a friend who have the same phone on the latest official software and the default kernel if it also occurs and he answered yes. Does someone know how to fix it?

its miui's stupidest bug ever and they dont even care to fix it. only solution if you are rooted, just install custoMIUIzer and choose higher minimum brightness value.

kos25k said:
its miui's stupidest bug ever and they dont even care to fix it. only solution if you are rooted, just install custoMIUIzer and choose higher minimum brightness value.
Click to expand...
Click to collapse
Thanks for the suggestion, it fixed the issue for me. What's interesting the algorithm is not to blame apparently - the light sensor is ****ed and dropping to single digit reading even in a relatively bright room if there's no direct lighting shining on it. Just a change of phone angle drops the reading from 400+ lux to single digits...

My note 5 brightness is terrible on automatic I have the note 7 too but the brightness is perfect on that phone.

kos25k said:
its miui's stupidest bug ever and they dont even care to fix it. only solution if you are rooted, just install custoMIUIzer and choose higher minimum brightness value.
Click to expand...
Click to collapse
Thanks i will try it. In miui11 they still didn't fixed that

brightness control

Hi i have been looking for a module for ed xposed which hopefully can control lowest brightness level. I am on Asop rom on the poco f3 and development is in early stages which means in darker areas the low brightness goes to low. It would be useful if there were a module which can set the lowest brightness to a certain value which the system cannot got lower than e.g 12% I hope this is understood and perhaps ther is already a module available for this but i cant find it.

sam00561 said:
Hi i have been looking for a module for ed xposed which hopefully can control lowest brightness level. I am on Asop rom on the poco f3 and development is in early stages which means in darker areas the low brightness goes to low. It would be useful if there were a module which can set the lowest brightness to a certain value which the system cannot got lower than e.g 12% I hope this is understood and perhaps ther is already a module available for this but i cant find it.
Click to expand...
Click to collapse
RootDim [root] - Apps on Google Play
Dim many rooted device's screens below factory settings.
play.google.com

loopypalm said:
RootDim [root] - Apps on Google Play
Dim many rooted device's screens below factory settings.
play.google.com
Click to expand...
Click to collapse
Thankyou so much its working perfectly just what i needed.

I spoke to soon left the phone overnight and in the morning brightness very minimal again. I guess it stopped working.