Related
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
We have a fix
Please read this post (and Thanks Milaq for the fix!!) and follow the instructions.
[*]Also, can someone test custom auto brightness levels too please?
I have made a ClockWorkMod flashable version of the fix in this post. This should cover almost all ROMs, irrespective of how the device is named in build.prop (leo, htcleo, bravo, qsd8k).
Original Post:
UPDATE: Thanks to Looki75, we have a workaround using Tasker to have custom auto-brightness levels with the flashing LED libraries here. Please go through his post and give your feedback!
I am rewriting the whole post, based on what I realized/ learnt today
We currently two lights libraries for to our phone:
lights.htcleo.so - this file has working auto-brightness and flashing LED notifications - but custom auto-brightness settings do not work (more on this a bit later)
lights.qsd8k.s0 - this file has working auto-brightness and custom auto-brightness levels, but LED notifications do not flash
Custom auto-brightness settings
What is it?
This is a setting/ feature in CM7 ROMs, not sure if MIUI has it or not (Users, please confirm if you have custom auto-brightness settings in non-CM7 based ROMs)
In a pitch dark room, the screen's brightness chosen by auto-brightness setting may be higher than required. With custom auto-brightness, the level of brightness the phone uses for a specific amount of light can be configured - the biggest benefit being higher battery life. Please read this post by @Dorimanx for custom auto-brightness levels.
How do I know if I have it or not?
You do not have the lights library that is compatible with custom auto-brightness levels if:
Your LED Notifications work (Except HeirOS kernels)
If you have something similar to this in your logcat:
20:50:43.090 Error lights 180 ***: value=90 (Mode=1)
20:50:43.090 Error lights 180 ***: value=91 (Mode=1)
20:50:43.090 Error lights 180 ***: value=92 (Mode=1)
20:50:43.090 Error lights 180 ***: value=94 (Mode=1)
Click to expand...
Click to collapse
On the other hand, you have it if
Your LED does not flash
Your screen will dim for several seconds (5~10seconds) before timing out
You do not see the errors I had quoted above in your logcat
So what is the point of this thread?
I had tried several Kernel combinations (and libaudio.so, but that does not matter in this issue) while trying to figure out the No Sound/ BT Voice Command/ libaudio.so issues, and found out that even if I have lights.qsd8k.so, which enables custom auto-brightness levels, LED Notifications flash with HeirOS 1.7.5 Kernel - they flash in amber and green alternatively. This gave me a hope that
This is something to do with the kernel (I used Tytung's initrd.gz, so it is not from there...)
This could be fixed easily with all our kernels, because HeirOS has already done it!
So What Next?
Anyone using any of the HeirOS kernels see what library you have (/system/lib/hw), and please use the lights.qsd8k.so if it is not there, deleting lights.htcleo.so while at it (it is available in the Mirrors used by @Dorimanx), and confirm if you concur with my observations - please mention the kernel version and the name of the lights library in your feedback.
Once we have that confirmed, we can request HeirOS to let us know the secret ingredient (or someone intelligent enough to look through the source codes can find it and post the diff/ findings).
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!! I am sorry for not being clear earlier, a little bit of Rum cleared things up for me
Lets now restart this discussion!!!
It is people like you that are going to make our phone as if it came with android when we bought it! I know you are not the one doing the coding but with all your support, your don't give up attitude, and your connections you get the job done. Thank you for all your determination.
Sent from my HTC HD2 using XDA App
hopefully the next thread for collaboration work that will become one of it's kind in hd2 android history. thx for your dedication and all the testing that you do! thanks to all the devs making our hd2 improving everyday.
I have posted a request in HeirOS' kernel thread, meanwhile can those who use earlier versions (1.7.2 or so) confirm if they have working LED Notifications when you use a working auto-brightness configuration please?
If so, I think we can trawl the source code posted on the first post of HeirOS kernel thread...
ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals....
Click to expand...
Click to collapse
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.
Nixda99 said:
Had never problems with auto brightness and my last kernel with a non working LED notification is older than around a half year. But I tried only MDJ, Tytungs and Raf's kernel. Green and orange LED are working perfect with these.
What problems do you have with auto brightness? Not working or the false brightness for the actual light?
Only outdoor at sunshine the auto brightness sometimes didn't choose the maximum brightness, than I set manual to max.
Click to expand...
Click to collapse
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?
ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
Click to expand...
Click to collapse
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness
Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
eseregin said:
Yeah...
Typhoon included Led blinking, i always replace it with lights.qsd8k.so with auto-brightness, i dont care about Led blinking too much, more interesting good working auto-brightness
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
ph03n!x said:
The auto-brightness / LED notifications are from /system/lib/hw/lights.htcleo.so (or lights.qsd8k.so).
In our case if your ROM's chef chose to have a working LED Notification configuration, auto-brightness will not work - the display will have a fixed brightness irrespective of the surroundings, and will not dim before fading out.
If you choose working Auto Brightness, the screen will maintain ambient lighting, but when have a missed call or SMS or email or chat, the LED stays on and does not flash.
That said, what kernel are you using? And can you check your logcat right from system boot (using QtADB?) and let us know if you see any errors?
Click to expand...
Click to collapse
If I remember it correctly, the working LED Notification (i.e. No fading out feature) of lights.htcleo.so in my GB ROM is from Gpc.
Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
karapialis said:
Install led me know from the market and you will have both working fine.That is what i do in dorimanx rom which has auto brightness enabled by default.
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.
jan-willem3 said:
leds and auto brightness work perfectley if you use the lights file from iamgpc. So I dont see the problem. Secondly this problem is hard to catch I can remember that Letama and gauner1986 tried to solve this problem but at the end they gave up.
Click to expand...
Click to collapse
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...
ph03n!x said:
We currently have to choose between a working auto-brightness setting, or a working flashing LED notification in most configurations/ kernals.
I am saying "most" because in my quest to fix the No Sound/ BT Voice Command/ libaudio.so issues, I tested various kernels and configurations, and found that with HeirOS 1.7.5 kernel, I have a working auto-brightness WITH flashing LED notifications. The notifications actually flash amber and green.
So looks like this is something that we can fix easier than the close to 5 weeks spent on the No Sound bug
HeirOS, please share your thoughts/ inputs for the benefit of all of us!!
This is not a critical/ experience-affecting issue, but rather something that is now "broken" and can be fixed without much ado!!
My explanation / understanding of the LED Notification vs. Auto Brightness issue- correct me if required
Click to expand...
Click to collapse
Here is a well-known solution for auto-brightness + flashing LED:
karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Like I said earlier, while fixing it natively is a good-to-have solution, and not a deal breaker for almost all of us. But still having it fixed surely feels good, doesn't it?!!
karapialis said:
Install led me know from the market and you will have both working fine
Click to expand...
Click to collapse
Updated the first post
karapialis said:
Moreover I think that the developer of LedMeKnow app, which is free by the way, may point out to the developers what to change in order to have both auto brightness and led blinking working out of the box for hd2s
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
LED Me Know eats up battery while flashing notification. When its flashing LED, the battery drain is more than 100mAh. Though I haven't used the application in a long time, but I remember previously it used to do that...I wonder if its changed now..
I actually prefer a static LED with working auto brightness.
Its very obvious without staring at my phone whether I have a new text, missed call, or otherwise. I tend to miss the blinking since its 8 seconds apart.
(know it can be configured to 3 seconds, but still)
Sent from my HTC HD2 using Tapatalk
ph03n!x said:
Yes, manual brightness works in GPC's lights.htcleo.so, but auto-brightness does not.
I found the HeirOS has fixed this (though not documented) in 1.7.5 (not tested earlier versions)...
Click to expand...
Click to collapse
Auto brightness works fine here.
In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.
Vice versa
In HeirOS 1.8 kernel i have led working and i do notice that when its really dark the screen will get bright and when its super sunny it gets darker so i believe auto brightness + led works fine in his new test kernel btw i am on sense gb rom.
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
Auto brightness with flashing LED notification works perfectly in Tytung's rom and kernel.
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.
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
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