Develop Bugs

[Q] Possibility for Future Screen Improvement?

Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.

uchihamonkey said:
Today is the very first time ever for me to root an android device and thank God it run perfectly.
Now i am using AIC kernel for V500 4.4.2 stock ROM. (http://forum.xda-developers.com/showthread.php?t=2741405)
Gamma correction in it really improved screen and picture quality. (plus 8000 antutu point increase bonus)
Before, i can barely see anything in Bloodborne trailer video. (http://www.youtube.com/watch?v=G203e1HhixY)
Since i cant post in development thread, i hope i can find answers to the followings:
Is it possible to further improve gamma in the future?
Even though currently gamma is improved, but the brightness level issue still persist. Is it hardware or software issue?
Is there any possibility for brightness level improvement in the near future (kernel) update?
All in all, i really like my G Pad and really hope for the possibility to receive screen improvement update in the near future.
Click to expand...
Click to collapse
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).

aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time

aicjofs said:
I heard a week or so ago through the grapevine of a version 20d coming out pretty soon. I have held off making any other changes to the AIC kernel until I see what LG did(no sense reinventing the wheel).
What brightness issue would you like changed? I know in general people think the Gpad screen is dark, but some of the AIC kernel users think the lowest brightness is too bright as well.
I think the screen is pretty bright at 100%, so for me it's a software issue. That's in 2 places, the kernel backlight driver, and the ROM brightness(think brightness slider).
Click to expand...
Click to collapse
It would be great if you could add row scheduler when you next update your kernel.
Thanks in advance rich ?
Sent from my LG-V500 using XDA Premium HD app

uchihamonkey said:
Tks for the reply and also thank you very much for the kernel, it really is helping a lot!
Rather than issue, i should have worded it as G Pad having a relatively low brightness level/dim display.
Compare to my nexus 7 1st gen, G Pad at 70% brightness level still not as bright as nexus at 30%.
Actually i dont really mind it, 70-80% G Pad brightness level is my sweet spot.
However, it would be great if the number is 30% rather than 70% (i am just feeling paranoid of having big number for a display setting).
I also realized that colours (might be) a bit off, especially red that looks orange-ish.
In general display seems lean toward yellow (yellowish-white).
Wonder if this is a common thing for all unit?
Hopefully it is just a matter of colours calibration that can be solved through software update not a hardware characteristic.
I tried Screen Adjuster and added more blue and red, but i just cant seems to find the proper setting to create a whiter white or redder red...
All in all, it is nice to hear version 20d may be coming soon.
Hopefully LG will address all these screen related things.
Also, really look forward to your another great work, especially when LG get it all wrong again this time
Click to expand...
Click to collapse
You can use Faux Clock or System Tuner to adjust the color temp and gamma.

meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?

vimesUK said:
Really...?
In that Kernel thread it states....
Add Faux Display interface (gamma control seems broken)
so does the Faux app control the gamma, even though aicjofs had noted that it seemed to be broken...?
Click to expand...
Click to collapse
It works for me?

meanoc said:
You can use Faux Clock or System Tuner to adjust the color temp and gamma.
Click to expand...
Click to collapse
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?

uchihamonkey said:
Pardon me but where can i find this Faux Clock and System Tuner?
Do you have any preferred setting for optimum screen (colour) performance?
Click to expand...
Click to collapse
You can find them here https://play.google.com/store/apps/details?id=com.teamkang.fauxclock and https://play.google.com/store/apps/details?id=ccc71.pmw.pro . Your best bet is to either use a calibration tool or just adjust it to your eyes.

Display Flicker on Custom ROMS

Hello everybody,
i have a strange bug. My display is flickering on most custom ROMS (CAF-Based and LOS). It's like the display is going on and off like 30 times in a second. Also on the lowest brightness the bottom 30% are complet black. On all OOS-based this problem is not present. So it's not a real hardware defect.
Someone has an idea what can cause this issue?

In case you did not know: The OnePlus3 uses some kind of PWM Pulse-width modulation to regulate its brightness. Test it for yourself: In a completely dark room move your hand very fast over your display. You will see a stutter effect at lower settings.
This is used in many tec devices and is known to be a more cheap implementation.
Back to your problem: Maybe your regulator for the pulse mod is broken?
Did you try a hard reset, meaning re-flashing all the core firmwares?

Hey.
Yes I read about this PWM. I also thought this could be the problem. Perhaps in the CAF Kernel the parameters are different? I've never looked in the source code for kernels. ?
And yes I have reset my phone with the full bricked version from the xda thread. Also tried different firmware versions (but only the nougat ones) with the CAF ROMs. Also tried all OOS versions (include marshmallow) and the problem never occurs there.
Is there perhaps a kernel manager where I can see (and change) some parameters related to the display driver? Only found some color calibrations in EX Kernel manager etc.

did you manage to solved this problem?

if on a custom rom, try disabling "Reduce Power Consumption" in live display settings. Might work, might not but you can try.

Antares9 said:
did you manage to solved this problem?
Click to expand...
Click to collapse
for me linage 15.1 and 14.1 are ok but others are not working.....

Increase minimum brightness

Hi,
can i set the minimum brightness in automatic mode to a higher value? Its to low for me and its f*ing annoying to adjust it manually a bit higher, everytime!
I got root and using latest xiaomi.eu rom.
Thanks
Spillunke

Spillunke said:
Hi,
can i set the minimum brightness in automatic mode to a higher value? Its to low for me and its f*ing annoying to adjust it manually a bit higher, everytime!
I got root and using latest xiaomi.eu rom.
Thanks
Spillunke
Click to expand...
Click to collapse
Please see also
https://forum.xda-developers.com/mi-max-3/how-to/automatic-brightness-fix-magisk-t3879427

Thanks for the link/hint.
It seems to work love it

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.

How To Guide HBM

The following command is how you can toggle HBM on our 6 Pro:
Code:
echo 1 > /sys/devices/platform/1c2c0000.drmdsim/1c2c0000.drmdsim.0/backlight/panel0-backlight/hbm_mode
Replace the one with a zero to disable!

HBM = high brightness mode?
Is it worth doing?

Cares said:
HBM = high brightness mode?
Is it worth doing?
Click to expand...
Click to collapse
I prefer doing it through @flar2 's HBM app set to automatic when using his custom ElementalX kernel. They've made that kernel for each of the previous Pixels (and some other phones) so I expect once the source code drops they'll do so for the P6P as well.
It definitely made a difference in direct sunlight.

Yeah I use Tasker to create QS toggle with that command

Is the command through adb? Or terminal?

rickysidhu_ said:
The following command is how you can toggle HBM on our 6 Pro:
Code:
echo 1 > /sys/devices/platform/1c2c0000.drmdsim/1c2c0000.drmdsim.0/backlight/panel0-backlight/hbm_mode
Replace the one with a zero to disable!
Click to expand...
Click to collapse
Any known downsides? I'm curious if there's no long term ill effects why it isn't just a default option. Any chance what's built in is 'what works for every panel' but HBM might cause an issue with a borderline panel that just barely squeaked through QA?

rickysidhu_ said:
The following command is how you can toggle HBM on our 6 Pro:
Code:
echo 1 > /sys/devices/platform/1c2c0000.drmdsim/1c2c0000.drmdsim.0/backlight/panel0-backlight/hbm_mode
Replace the one with a zero to disable!
Click to expand...
Click to collapse
I was playing around with this command a couple of days ago because I didn't feel that the maximum brightness was very good due to the Pixel 6 Pro using a Samsung s6e3hc3 display (cat /sys/class/backlight/panel0-backlight/device/panel_name), which is in fact the same display the Oppo Find X3 Pro uses & allegedly that goes upto 1300 nits.
I found that:
echo 1 >> /sys/class/backlight/panel0-backlight/hbm_mode
and
echo 2 >> /sys/class/backlight/panel0-backlight/hbm_mode
Both work to give the Pixel 6 Pro to achive a little more brightness (& they stay on after switching the screen off) - obviously setting HBM to "1" provides a little more brightness than "0", and "2" provides even more brightness than "1".
I used my ColourMunki Display to measure the brightness of the display multiple times & got the same results every time: these show that max brightness with HBM @ 0 is ~500 nits, HBM @ 1 is ~795 nits & HBM @ 2 provides 835 nits.
I'm hoping someone can replicate these numbers or verify with another, more accurate device & hopefully (when ElementalX is released) we will be able to toggle both HBM modes via the HBM widget

It also works on my Pixel 6 (non-pro), good to know, thanks!

I guess this is root-only?

Morgrain said:
I guess this is root-only?
Click to expand...
Click to collapse
Yeah, you'd get "permission denied" if you try to echo to that directory without su permissions

roirraW edor ehT said:
I prefer doing it through @flar2 's HBM app set to automatic when using his custom ElementalX kernel. They've made that kernel for each of the previous Pixels (and some other phones) so I expect once the source code drops they'll do so for the P6P as well.
It definitely made a difference in direct sunlight.
Click to expand...
Click to collapse
Yeah, in the past I've been doing it with tbalden's CleanSlate kernel, which comes with QS toggles. He even has a High Brightness mode & a High Brightness Boost mode, which goes even beyond what High Brightness gives you. But until (or if) he builds his kernel for this phone I'm using flar2's HBM mode app and just toggle it on if I need to.
The other day I went into the bright sun for the first time with this phone to test it's native HBM abilities (without flar2's app). It definitely appeared to turn on by itself (took about 3-5 seconds), which is different from my Pixel 4 XL, where the HBM mode was disabled and hidden by default. The screen was also plenty bright for me to see, so I think all this talk about it not having enough Nits or not being bright enough is a bit exaggerated.

It's definitely not as bright as my op8 pro. I work outside so I always use flars hbm. I'm using it still but it's a little glitchy

Lughnasadh said:
The other day I went into the bright sun
Click to expand...
Click to collapse
Lughnasadh said:
The screen was also plenty bright for me to see, so I think all this talk about it not having enough Nits or not being bright enough is a bit exaggerated.
Click to expand...
Click to collapse
Can agree with this. Even with bright sunshine outside, I can still see everything without problem & sunglasses on (stock, no root, no forced HBM). That's the most extreme usecase I can think of, so that's fine on my end.

Ultimoose said:
Any known downsides? I'm curious if there's no long term ill effects why it isn't just a default option. Any chance what's built in is 'what works for every panel' but HBM might cause an issue with a borderline panel that just barely squeaked through QA?
Click to expand...
Click to collapse
There might be a possible downside of screen burn in for having HBM on for extended periods. Maybe poor battery life as well.
I don't think there's a default option because I think Android will enable it automatically when the device is under bright light. This command lets you use the mode in any lighting condition
If I'm incorrect with any of this information, anyone who knows more, feel free to let us know!

rickysidhu_ said:
There might be a possible downside of screen burn in for having HBM on for extended periods. Maybe poor battery life as well.
I don't think there's a default option because I think Android will enable it automatically when the device is under bright light. This command lets you use the mode in any lighting condition
If I'm incorrect with any of this information, anyone who knows more, feel free to let us know!
Click to expand...
Click to collapse
Thank you sir for the information, appreciate it!

Ultimoose said:
Any known downsides? I'm curious if there's no long term ill effects why it isn't just a default option. Any chance what's built in is 'what works for every panel' but HBM might cause an issue with a borderline panel that just barely squeaked through QA?
Click to expand...
Click to collapse
I used automatic HBM through @flar2 's ElementalX kernel and app on my Pixel 1 for several years - I never experienced any issues. It definitely made the screen brighter in direct sunlight than the Pixel 1 did by itself without the kernel and app.

DanielF50 said:
I was playing around with this command a couple of days ago because I didn't feel that the maximum brightness was very good due to the Pixel 6 Pro using a Samsung s6e3hc3 display (cat /sys/class/backlight/panel0-backlight/device/panel_name), which is in fact the same display the Oppo Find X3 Pro uses & allegedly that goes upto 1300 nits.
I used my ColourMunki Display to measure the brightness of the display multiple times & got the same results every time: these show that max brightness with HBM @ 0 is ~500 nits, HBM @ 1 is ~795 nits & HBM @ 2 provides 835 nits.
Click to expand...
Click to collapse
Following up on this, I tested some HDR10+ videos on YouTube & if you run cat /sys/class/backlight/panel0-backlight/hbm_mode, when these are playing, you get a result of HBM: "1" so the kernel is obviously able to use this feature on a stock device, and maybe even utilises this when in extreme lighting conditions.

I've update High Brightness Mode to support Pixel 6/6Pro (version 5.03).
High Brightness Mode - Apps on Google Play
See your screen in bright sunshine. High brightness mode for your phone
play.google.com

flar2 said:
I've update High Brightness Mode to support Pixel 6/6Pro (version 5.03).
Click to expand...
Click to collapse
Thank you!!

flar2 said:
I've update High Brightness Mode to support Pixel 6/6Pro (version 5.03).
High Brightness Mode - Apps on Google Play
See your screen in bright sunshine. High brightness mode for your phone
play.google.com
Click to expand...
Click to collapse
Does it support the "2" mode described above by @DanielF50 ?
forum.xda-developers.com/t/hbm.4356189/post-85878625