[GUIDE] OnePlus 7T Pro Neutral Display Calibration Settings - OnePlus 7T Pro (Regular & McLaren) Guides, News...

Similar to the thread for the OnePlus 7T I measured the OnePlus 7T Pro's display with my Spyder5. I'd like to share my settings so that you can have a neutral display colour. Keep in mind that every panel might be slightly different. So as always: YMMV.
Requirement:
- Custom kernel
- Kernel manager that can tweak KCAL
- In this case: OOS
Got to Settings > Display > Screen calibration
Select "Advanced" and "AMOLED Wide Gamut"
Set the slider (see the attached screenshot)
(Unfortunately there is no percentage or something similar to adjust it accurately.)
Go to your kernel manager app
Set the RGB to 253, 256, 253 (= lower blue and red to 253)
Done
Additional information:
- On my device I've noticed that it has less green no matter what you change in OOS' screen calibration.
- The profile is calibrated towards 6500K. Changing the preferred temperature might yield to slight color shifts but it will be better than not reducing the green tint at all.
- This profile is calibrated towards the 50% screen brightness. Changing the brightness may also slightly change the colours.
- In the end it would be enough for the average user to simply reduce the red and blue pixels to 253 and then set the preferred colour temperature.

Nice!!! Very useful.
Hope can make calibrate to 6504k(D65) setting.

ricky886 said:
Nice!!! Very useful.
Hope can make calibrate to 6504k(D65) setting.
Click to expand...
Click to collapse
Took me half an hour but here you go. Set it to 255, 256, 255 and the colour slider needs to be very far to the right.

Macusercom said:
Took me half an hour but here you go. Set it to 255, 256, 255 and the colour slider needs to be very far to the right.
Click to expand...
Click to collapse
Thank you so much!!!
And can you test d65 at 120cd/m?

ricky886 said:
Thank you so much!!!
And can you test d65 at 120cd/m?
Click to expand...
Click to collapse
There you go. This is the last time I'm uploading custom profiles, I hope that's okay with you. If you want further adjustments, I can recommend the Spyder5

Macusercom said:
There you go. This is the last time I'm uploading custom profiles, I hope that's okay with you. If you want further adjustments, I can recommend the Spyder5
Click to expand...
Click to collapse
Thanks for the setting:good:

What setting/ kernel/ app did you use make the RGB adjustment & 'color control' changes.
I cannot find it in OOS settings nor in Franco kernel manager.....

elmor0 said:
What setting/ kernel/ app did you use make the RGB adjustment & 'color control' changes.
I cannot find it in OOS settings nor in Franco kernel manager.....
Click to expand...
Click to collapse
I use EX Kernel Manager
EDIT: Here are my calibration settings in case someone wants to have sRGB with 6500K at 200 cd/m2. The calibration slider for warm/cold in OOS' settings is completely to the right.

@Macusercom Is the display calibration of the OnePlus 7T Pro the same as the OnePlus 7 Pro?

Is the "natural" display mode not accurate? Anandtech's review of the OP7 Pro (couldn't find one for the 7T Pro) mentioned that the natural mode was better than anything you could get from the advanced mode.
https://www.anandtech.com/show/14464/the-oneplus-7-pro-review/4

knpk13 said:
Is the "natural" display mode not accurate? Anandtech's review of the OP7 Pro (couldn't find one for the 7T Pro) mentioned that the natural mode was better than anything you could get from the advanced mode.
https://www.anandtech.com/show/14464/the-oneplus-7-pro-review/4
Click to expand...
Click to collapse
Ice Bear would use the natural color calibration...however, the display calibration changes to vivid when locking the screen and it stays that way until Ice Bear sets it to natural again. Ice Bear does not use the fingerprint sensor. Android 10 messed up the calibration profiles.

Ice Bear said:
Ice Bear would use the natural color calibration...however, the display calibration changes to vivid when locking the screen and it stays that way until Ice Bear sets it to natural again. Ice Bear does not use the fingerprint sensor. Android 10 messed up the calibration profiles.
Click to expand...
Click to collapse
Hm, a known bug (maybe it needs to be that way for the FP sensor to work) is that the lockscreen always stays at the default vivid calibration, until you unlock the screen, at which point it changes to the one you selected. Ice Bear is saying that it doesn't change back to natural when Ice Bear unlocks the screen? I'm using a 7T Pro. I tried the calibration profiles but I decided to stick to natural.
Another long known OOS bug, idk why they're not fixing it, is that the screen is blacked out after first boot although it's active and receives inputs, you have to turn it off and on again to get it to work.

Ice Bear said:
@Macusercom Is the display calibration of the OnePlus 7T Pro the same as the OnePlus 7 Pro?
Click to expand...
Click to collapse
I'm not sure as I don't have a OnePlus 7 Pro, unfortunately
knpk13 said:
Is the "natural" display mode not accurate? Anandtech's review of the OP7 Pro (couldn't find one for the 7T Pro) mentioned that the natural mode was better than anything you could get from the advanced mode.
https://www.anandtech.com/show/14464/the-oneplus-7-pro-review/4
Click to expand...
Click to collapse
I'd have to check again. I've used advanced for K-lapse but as it broke the fp sensor, I left it as-is. But despite the natural mode being neutral, it probably uses another whitepoint. I prefer 6500K but that ultimately comes down to personal preference.

Macusercom said:
Similar to the thread for the OnePlus 7T I measured the OnePlus 7T Pro's display with my Spyder5......
Click to expand...
Click to collapse
May I ask how did you use Spider 5 on android. I have a rooted Oneplus 7T and a Spyder5.

frankzappatistas said:
May I ask how did you use Spider 5 on android. I have a rooted Oneplus 7T and a Spyder5.
Click to expand...
Click to collapse
Generate a fully white image (#FFFFFF) and display it on your device. Use DispCal on a Mac or PC and check "Interactive Calibration". Place the Spyder on the computer's display until it is done.
You may now put the Spyder in your Android device and see the RGB balance as well as brightness

Macusercom said:
Generate a fully white image (#FFFFFF) and display it on your device. Use DispCal on a Mac or PC and check "Interactive Calibration". Place the Spyder on the computer's display until it is done.
You may now put the Spyder in your Android device and see the RGB balance as well as brightness
Click to expand...
Click to collapse
This is some awesome next level creativity. Thanks I will try it myself.

Related

[Q] Jeff Sharkey's AMOLED "night mode"

Has anyone attempted to/willing to try to implement this on the Captivate?
jsharkey.org/blog/2010/07/01/android-surfaceflinger-tricks-for-fun-and-profit/
This is really interesting. I'm into astronomy and it would be awesome to not have the phone blind me everytime I turn it on during an observing session to use it for google sky and the atomic clock.
Apparently no dev types are interested enough to tell us that they are not interested.
asrrin29 said:
This is really interesting. I'm into astronomy and it would be awesome to not have the phone blind me everytime I turn it on during an observing session to use it for google sky and the atomic clock.
Click to expand...
Click to collapse
No doubt.
This thing is blinding even on the lowest brightness setting.
Yes, the brightness is pretty ridiculous. Is this because of the AMOLED screen? Can't set brightness below "blinding" due to no backlight?
I have heard that the leaked I897UCJH2 rom has a lower mininal brightness; which might help with the blinding brightness at night, and also helps bettery a bit.
Not sure if you guys are interested in leaked ROMs but I'm sure if Samsung does not release it that a cook will make a custom rom from it.
looks awesome
Bump.
I think this would be extremely useful.
/agree to post above me
asrrin29 said:
This is really interesting. I'm into astronomy and it would be awesome to not have the phone blind me everytime I turn it on during an observing session to use it for google sky and the atomic clock.
Click to expand...
Click to collapse
Me too. I'm jealous of the iphone star map program. The authors were smart enough to make it all black and red. You can tell none of the google authors star gaze in their spare time with all that color.
k2snowboards88 said:
Me too. I'm jealous of the iphone star map program. The authors were smart enough to make it all black and red. You can tell none of the google authors star gaze in their spare time with all that color.
Click to expand...
Click to collapse
on Google sky map theres a night mode option when you press the menu key.
I seem to recal hearing that at a certain point when the voltage is too low the screen will still work, but you see glitches/artifacts.
So im assuming this is why the min brightness is set where it is.
Berserk87 said:
I seem to recal hearing that at a certain point when the voltage is too low the screen will still work, but you see glitches/artifacts.
So im assuming this is why the min brightness is set where it is.
Click to expand...
Click to collapse
There is that very low brightness that occurs when you have less than 10% battery life. I wish they would make that brightness user selectable.
Even if the screen cannot be physically set below a certain level of brightness, it would be trivial to have the OS do the equivalent of putting a partially-transparent black rectangle over the screen. Sure, color fidelity would suffer, but it would be a welcome option anyway--I have seriously considered wearing sunglasses in bed.
Tinyboss said:
Even if the screen cannot be physically set below a certain level of brightness, it would be trivial to have the OS do the equivalent of putting a partially-transparent black rectangle over the screen. Sure, color fidelity would suffer, but it would be a welcome option anyway--I have seriously considered wearing sunglasses in bed.
Click to expand...
Click to collapse
wow, i think your right.
instead of trying to set the brighness lower just put a transparent gray object that sites on top of all the windows.
It would have the same effect and save tons of battery.
You can!
k2snowboards88 said:
There is that very low brightness that occurs when you have less than 10% battery life. I wish they would make that brightness user selectable.
Click to expand...
Click to collapse
Search for a widget called Curvefish Brightness Level in the market. Set it to 0% brightness, which appears to be the same as the low battery life brightness.
k2snowboards88 said:
Me too. I'm jealous of the iphone star map program. The authors were smart enough to make it all black and red. You can tell none of the google authors star gaze in their spare time with all that color.
Click to expand...
Click to collapse
the google sky map version I have turns black and red in night mode

[Q] lower brightness

Hello,
are there any solution on lower brightness in jp6 like voodoo 4 on 2.1?
The screen is too much bright at night!
Anybody knows this comes with one of the next releases of voodoo5?
g ehmi
Come one, am i the only one who love's this great setting in voodoo4?
Supercurio said already it's planned. Don't know when.
Till then Rayban can help
hacksome said:
Supercurio said already it's planned. Don't know when.
Till then Rayban can help
Click to expand...
Click to collapse
damn I'm just a oacley.
anyone know a other tool who makes same effect?
HOPE SUPERCURIO BRINGS IT ON FROYO!
Take a look at Exzended Controlls, with the widget for brightnes i am able to set it to 2% which is 'dark' enough for me
Sent from my GT-I9000 using XDA App
Tanis64 said:
Take a look at Exzended Controlls, with the widget for brightnes i am able to set it to 2% which is 'dark' enough for me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Im using extended widgets too, mine goes as low as 1% but i think thats still the systems native low brightness Voodoo goes even lower...
Just slide your finger along the notification bar.
app called "brightness level"
set to 0%
Interested in this as well.
I think we are actually looking for something lower than 0%
It is probably the amoled screen vs backlit one, the way they operate. 20% on lcd is much lower than 0% on amoled.
Maybe there is some kind of overlay that can act as Rayban? Like ie when you do Titanium backup, you can see the rest of the application being much darker than the notification that pops up. Probably some overlay being used.
Maybe some of you asking yourself why, but try using it in complete darkness for awhile and you'll see what I mean.
Billus said:
Just slide your finger along the notification bar.
Click to expand...
Click to collapse
Nice one even if it set it only min to 12% nice "hidden" function
encho said:
Maybe some of you asking yourself why, but try using it in complete darkness for awhile and you'll see what I mean.
Click to expand...
Click to collapse
Thats what i mean like a torch in the night.
I had tested all brightness apps in market but no one goes lower.
Thanks for help.
Mybe a dev or supercurio can help to explain
Yes, the lowest stock level is already quite bright, too bright of course for night use in bed.
You'll also notice that the colors & contrast looks quite dull on the lowest stock brightness settings, with a color deviation in the red shadow colors.
With the revamped Voodoo color which will be released step by step during the next weeks, you'll be able to go so "dark" (if chosen) that you'll be almost not able to see it in the dark even when on
All that, preserving color accuracy and color temperature (which goes more red when you lower the brightness on stock)
yaocheng said:
app called "brightness level"
set to 0%
Click to expand...
Click to collapse
does this app go lower than "Dimmer - Night mode" ?
Dimmer shows it goes from 30 (lowest stock) to 10...
moved this is not a Dev topic
supercurio said:
Yes, the lowest stock level is already quite bright, too bright of course for night use in bed.
You'll also notice that the colors & contrast looks quite dull on the lowest stock brightness settings, with a color deviation in the red shadow colors.
With the revamped Voodoo color which will be released step by step during the next weeks, you'll be able to go so "dark" (if chosen) that you'll be almost not able to see it in the dark even when on
All that, preserving color accuracy and color temperature (which goes more red when you lower the brightness on stock)
Click to expand...
Click to collapse
Thank you i'm happy to read this!!!
supercurio said:
With the revamped Voodoo color which will be released step by step during the next weeks, you'll be able to go so "dark" (if chosen) that you'll be almost not able to see it in the dark even when on
All that, preserving color accuracy and color temperature (which goes more red when you lower the brightness on stock)
Click to expand...
Click to collapse
Can't wait, thanks for the info.
Sent from my GT-I9000 using XDA App

how to reduce galaxy note screen brightness without filter?

050820121030:
I have use the search button to see how i can lower screen brightness on galaxy note.
i found everywhere mentioning screen filter, it is not i don't like screen filter, but when i take screenshot it will be tinted gray.
so i decide to go to a more elegant way like what atrix 4g user did.
http://forum.xda-developers.com/showthread.php?t=1245332
i tried with my note, i cant find sys/bus/i2c/drivers/lm3532, i decided to check folder with the nearest name, but i can't find it.
so i decided to download linux, mind you i have no idea how to use linux.
i downloaded samsung ics opensource update 4, inside i can't find leds-lm3532.c,leds-lm3532.h,board-mot-lights.c.
so futhur dig found leds-lm3530c, the file structure is different with leds-lm3532.c, but i think it works the same.
any good suggestion from experts?
edit1 050820121203:
I decided to check what AdjBrightness do.
it is modifying the following files
/sys/class/leds/lcd-backlight/brightness
/sys/class/leds/amber/blink
/sys/class/leds/amber/brightness
/sys/class/leds/green/blink
/sys/class/leds/green/brightness
all return errors in note.
further investigation leads to Rootdim:
/sys/class/leds/leds-sec/trigger
/sys/class/leds/leds-sec/brightness
/sys/class/leds/leds-sec/mmc1::/trigger
/sys/class/leds/leds-sec/mmc1::/brightness
/sys/class/leds/leds-sec/mmc2::/trigger
/sys/class/leds/leds-sec/mmc2::/brightness
here all the triggers return error.
next thing i check /sys/class/
i see backlight/panel in it.
i also see lcd, leds and lightsensor.
have no idea, keep digging.
100820120935:
Found s6*aa*.c files inside driver folder.
There will be some info about 5.3inch screen.
Deeper search found that it only suplort 24 stages of brightness
From 0,1 to 30 is 0
Conclusion minimum brightness for galaxy note is 1(more than 30)
Keep digging.
100820121808:
s3cfb_s6e39a0.c contain brightness level from 1 to 24.
100820121815:
AMS529HA01 is samsung 5.3 inch galaxy note panel
s3cfb_s6e8aa0 -- the one we are using.
the following files also related to the above file.
s3cfb_s6e39a0
s3cfb_s6e63m0
s6d6aa1
s6dr171
s6e8aa1
smart_dimming
midas-lcd
setup-fb-s5p
the whole thing means samsung have tried other lcd before hd super amoled 5.3 inch?
keep digging for the brightness
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
1609120512:
https://sites.google.com/site/androidnothize/no-dock/input-device-and-backlight
this shows you minimum brightness level is 30
http://forum.xda-developers.com/showthread.php?t=1709686
search for min_bl
http://forum.xda-developers.com/showthread.php?t=1154278&page=617
curve?
http://forum.xda-developers.com/showthread.php?t=1576355&page=222
N.E.A.K
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
d210 said:
So, what's the verdict? Are we stuck with "too bright in the dark" screens on our Note's?
Click to expand...
Click to collapse
For that purpose a screen filter works just fine for me.
Frankly it's not doing it for me, it looks like I'm looking through a grey plastic bag.
Andrew0811 said:
150820121820:
End of research, the brightness for amoled devices only have 24 levels.
lower than that you will need to adjust contrast for better battery consumption.
if you use filter it wont decrease battery consumption, and it will affect your screenshot images clarity.
Click to expand...
Click to collapse
So what is conclusion bro?
We can't use brightness below the SYSTEM-MINIMUM?
I also want more battery by reducing brightness to below 10.
AND yes you did well.
Good research.

[APP]OLED Saver (flicker free backlight dimming, no PWM)

This app is a life saver for anyone who suffers from "invisible" screen flickering caused by PWM backlight control. Most AMOLED displays control lower than 100% display brightness by PWM. This method is extremely easy to implement, but can cause eye strain and headaches for sensitive people. DC dimming is rare as it is hard to implement without sacrificing color accuracy. This is where OLED Saver comes in handy.
How to use:
- turn off system adaptive brightness
- install the app, allow permissions it requests and enable the service
- set minimum screen brightness to 255 if you want to have the safest value (guaranteed to have zero flickering). After further testing, values as low as 96 seems to be still safe - but test it with your phone to be sure.
- minimise the ongoing notification to hide it from lockscreen
- turn on automatic brightness change from the notification ("A")
- remove OLED Saver from battery optimizations
In some rare cases you will need to suspend the service from notification (while taking screenshots for example, app installer might need it disabled too).
If you have Tasker and root access, you can toggle the service to force 100% brightness automatically. I'm using 100% while viewing videos/pictures and taking photos.
Start service
Code:
am startservice org.js.oledsaver/.MainService
Stop service (this will remove also notification)
Code:
am stopservice org.js.oledsaver/.MainService
So far I haven't found any negative point while using this app, just wish it was included in the AOSP code so we could still use adaptive brightness. Anyway, give it a try and share your experience.
I used to have some trouble watching text on this display under certain light conditions.
I don't know if it is just a placebo effect, but since I've installed this app, I don't feel any discomfort anymore.
I also can't see any difference in picture quality.
pecholino said:
I used to have some trouble watching text on this display under certain light conditions.
I don't know if it is just a placebo effect, but since I've installed this app, I don't feel any discomfort anymore.
I also can't see any difference in picture quality.
Click to expand...
Click to collapse
You can easily check if it's working with another phone's camera. People have different sensitivity to PWM flickering, from none to watering eyes. You are probably somewhere in between. Without the app, I had a slight feeling like something was pulling my eyes. As soon as I enabled the app, this sensation has been gone. My wife doesn't see/feel any difference, but I left it enabled for her anyway, just to be on the safe side.
Thanks a lot for introducing this app. It works.
However I encountered a problem. With this OLED Saver activated and using GCAM to take photos, it boosts the brightness to maximum. Then I went elsewhere like home screen or other app, the auto brightness seemed not working and kept the max. brightness.
Then I tried locking the screen and unlocking, the brightness went up or down randomly, or it worked in some particular patterns I don't know. Anyway, it can't keep the brightness I set previously.
Does anyone has any idea to remedy this? Thanks a lot.
CLS_phone said:
Thanks a lot for introducing this app. It works.
However I encountered a problem. With this OLED Saver activated and using GCAM to take photos, it boosts the brightness to maximum. Then I went elsewhere like home screen or other app, the auto brightness seemed not working and kept the max. brightness.
Then I tried locking the screen and unlocking, the brightness went up or down randomly, or it worked in some particular patterns I don't know. Anyway, it can't keep the brightness I set previously.
Does anyone has any idea to remedy this? Thanks a lot.
Click to expand...
Click to collapse
Which GCAM app do you use? I'll try it. In stock camera it doesn't behave this way.
Btw. I tried to contact the developer if he could add global intents so we could control OLED Saver with Tasker and without root, this should help in preventing this kind of behavior. No response so far though. If you are rooted you could use method mentioned in the first post.
Also I'm in touch with Velis Auto Brightness developer - this app offers much more features (customizable automatic brightness levels, apps exclusion and more) and has similar feature for OLED displays, but sadly it doesn't work on status/nav bar as of now. If he manages to use the same method as OLED Saver, we could switch to VAB app.
The GCAM version is 7.0.009.259843690.
Phone model is M1906F9SH (64G global version) with OE ROM.
Thank you.
CLS_phone said:
The GCAM version is 7.0.009.259843690.
Phone model is M1906F9SH (64G global version) with OE ROM.
Thank you.
Click to expand...
Click to collapse
Could you send me the link to the particular GCAM apk pls? Different authors might give slightly different results.
I'm not allowed to post link here, yet.
Please search this file name: PMGC_7.0.009_FinalBuild_V14.apk
It's what I've saved and installed.
CLS_phone said:
I'm not allowed to post link here, yet.
Please search this file name: PMGC_7.0.009_FinalBuild_V14.apk
It's what I've saved and installed.
Click to expand...
Click to collapse
Hm, I can't replicate this. I've installed GCAM, enabled max brightness for pictures (but it does nothing, as system brightness is at max already and real dimming is done with OLED Saver, which is not being controlled by GCAM). Moving to/from GCAM doesn't change anything. If I manually suspend OLED Saver from notification, GCAM shows max brightness correctly. On resume it returns to the expected behavior and dimmer display.
Yeah, sometimes I got what you described. Sometimes it rushes to very very bright, but sometimes it can be very dim...
I'll try reset it again and see how it goes. Thanks for your time.
CLS_phone said:
Yeah, sometimes I got what you described. Sometimes it rushes to very very bright, but sometimes it can be very dim...
I'll try reset it again and see how it goes. Thanks for your time.
Click to expand...
Click to collapse
I think that I saw OLED Saver "crash" once while using the phone - brightness suddenly went to max and was controlled by system. Since I removed this app from battery optimizations, it seems to be stable. Though this does not explain rapid bright/dim changes.
This looks very useful but what is it doing exactly? Is it running the screen at max brightness at all time and using some kind of overlay to dim the screen? Isn't that bad for battery life?
Sent from my G6 using Tapatalk
barth2 said:
This looks very useful but what is it doing exactly? Is it running the screen at max brightness at all time and using some kind of overlay to dim the screen? Isn't that bad for battery life?
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
Yes, as you said, running HW brightness at max and putting a translucent overlay over the screen. It's basically SW implementation of DC dimming. It has a small artifacts with very low brightness, especially on grey colors, but otherwise no issues. Impact on battery should be negligible (OLED displays work different than LCD). Here is a nice article with links to more information at the end https://blog.elcomsoft.com/2019/11/...e-11-pro-and-pro-max-google-pixel-4-and-4-xl/
_mysiak_ said:
Yes, as you said, running HW brightness at max and putting a translucent overlay over the screen. It's basically SW implementation of DC dimming. It has a small artifacts with very low brightness, especially on grey colors, but otherwise no issues. Impact on battery should be negligible (OLED displays work different than LCD). Here is a nice article with links to more information at the end https://blog.elcomsoft.com/2019/11/...e-11-pro-and-pro-max-google-pixel-4-and-4-xl/
Click to expand...
Click to collapse
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
barth2 said:
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
I̶ ̶u̶s̶e̶d̶ ̶o̶n̶l̶y̶ ̶c̶a̶m̶e̶r̶a̶ ̶o̶f̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶p̶h̶o̶n̶e̶ ̶a̶n̶d̶ ̶i̶t̶ ̶s̶e̶e̶m̶s̶ ̶t̶h̶a̶t̶ ̶f̶l̶i̶c̶k̶e̶r̶ ̶s̶t̶o̶p̶s̶ ̶t̶o̶ ̶b̶e̶ ̶v̶i̶s̶i̶b̶l̶e̶ ̶a̶t̶ ̶a̶b̶o̶u̶t̶ ̶l̶e̶v̶e̶l̶ ̶2̶2̶0̶ ̶f̶r̶o̶m̶ ̶2̶5̶5̶,̶ ̶b̶u̶t̶ ̶a̶s̶ ̶f̶a̶r̶ ̶a̶s̶ ̶I̶ ̶k̶n̶o̶w̶,̶ ̶p̶r̶e̶t̶t̶y̶ ̶m̶u̶c̶h̶ ̶a̶l̶l̶ ̶S̶a̶m̶s̶u̶n̶g̶ ̶A̶M̶O̶L̶E̶D̶ ̶d̶i̶s̶p̶l̶a̶y̶s̶ ̶u̶s̶e̶ ̶P̶W̶M̶ ̶a̶t̶ ̶a̶n̶y̶ ̶l̶e̶v̶e̶l̶ ̶b̶e̶l̶o̶w̶ ̶1̶0̶0̶%̶,̶ ̶s̶o̶ ̶i̶t̶'̶s̶ ̶s̶a̶f̶e̶ ̶t̶o̶ ̶a̶s̶s̶u̶m̶e̶ ̶t̶h̶a̶t̶ ̶M̶i̶ ̶A̶3̶ ̶i̶s̶ ̶n̶o̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶t̶.̶
Edit: actually PWM seems to kick in at 80% brightness and below.
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
CLS_phone said:
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
Click to expand...
Click to collapse
Yes, I noticed that "slow flickering/artifacts" as well. I believe it's the side effect of DC dimming method and probably one of the reasons why it's not so widely used. From what I read, Samsung AMOLED panels are designed to be used with PWM dimming, so we probably can't avoid it with very low brightness. If it's too disturbing, I just move the OLED Saver brightness slider a bit higher (it stops completely at roughly 40% brightness). Using pitch black themes in apps helps too. Not a perfect solution but definitely better than PWM
Btw. it's the same for any app using translucent overlays, I tried a couple of them and at similar brightness, all behave the same.
barth2 said:
Has anyone used a high speed cam to determine at which brightness level the a3 flickers, or is it all level below 100%
Sent from my G6 using Tapatalk
Click to expand...
Click to collapse
It seems to be at 80% and below. 81-82% and above should be safe.
CLS_phone said:
Hi _mysiak_,
I changed to some other version of GCAM (without the max brightness view finder) and then this OLED Saver App is working fine afterwards. Thank you.
Then I found, when in very dim setting, occasionally, the white color (now it's actually gray) seems not stable. It could be fluctuating from neutral gray to warmer. Not intrusive, though. Do you see that?
Click to expand...
Click to collapse
Try to change the "basic physical brightness" to value 96, artifacts don't disappear completely, but I don't notice them so often.
Level 96 in OLED Saver corresponds to HW brightness level 82%, which seems to be still free of PWM.
Thanks for the tip.
It's really works. Thanks for the tip ???

Question did asus pull back ww_31.1010.0411.132 firmware?

I downloaded 31.1010.0411.132 firmware from official website on which includes October security patch.
but now the firmware is not showing anymore on list.
did asus pull back that firmware?
I just received it OTA.
DerSteppo said:
I just received it OTA.
Click to expand...
Click to collapse
Me too, seems to work just fine.
The latest firmware is 138 and can be downloaded from ASUS site.
Zenfone 8|Phones|ASUS Global
A new compact powerful choice: Flagship 5G processor · 120Hz AMOLED display · 4000mAh battery · Pro-grade dual rear and front camera · IP68 water resistant
www.asus.com
Since I've opted in for A13 beta, I just got 33.0210.0210.100 a few minutes ago.
This is my first device running Android 13, so I don't have too much personal experience about it, but so far so good!
5tormChild said:
Since I've opted in for A13 beta, I just got 33.0210.0210.100 a few minutes ago.
This is my first device running Android 13, so I don't have too much personal experience about it, but so far so good!
Click to expand...
Click to collapse
I tried to sign up since I received the recent update, but servers where down since. I will try again later.
5tormChild said:
Since I've opted in for A13 beta, I just got 33.0210.0210.100 a few minutes ago.
This is my first device running Android 13, so I don't have too much personal experience about it, but so far so good!
Click to expand...
Click to collapse
How long do you wait? from you sign up to become beta tester until you get android 13 beta ota update?
damarwardoyo said:
How long do you wait? from you sign up to become beta tester until you get android 13 beta ota update?
Click to expand...
Click to collapse
I've applied a few months ago, so I got a notification about a week before that A13 beta will be available soon, so I can upgrade my ZF8 to it.
Everything's fine, but I found a few bugs and/or issues:
- no matter what the brightness setting is, when the phone's screen awakes (with a double tap in my case), for a fraction of a second it's on full brightness, but then goes back to the set value,
- I had an issue with the touchscreen one time, but after a lock-unlock everything went back to normal,
- I had a custom system mode setting, which is now completely missing, only the 4 factory defaults are present (High performance, Dynamic, Durable and Ultra durable); I was able to set lower CPU / RAM speeds, but now these settings are gone,
- there's a power menu besides the settings gear when I pull down the notification bar, which is unnecessary IMO, it's right where the settings was.
Other than that I find it more usable than the A12, and the battery life seems to be a bit better in my case.
5tormChild said:
I've applied a few months ago, so I got a notification about a week before that A13 beta will be available soon, so I can upgrade my ZF8 to it.
Everything's fine, but I found a few bugs and/or issues:
- no matter what the brightness setting is, when the phone's screen awakes (with a double tap in my case), for a fraction of a second it's on full brightness, but then goes back to the set value,
- I had an issue with the touchscreen one time, but after a lock-unlock everything went back to normal,
- I had a custom system mode setting, which is now completely missing, only the 4 factory defaults are present (High performance, Dynamic, Durable and Ultra durable); I was able to set lower CPU / RAM speeds, but now these settings are gone,
- there's a power menu besides the settings gear when I pull down the notification bar, which is unnecessary IMO, it's right where the settings was.
Other than that I find it more usable than the A12, and the battery life seems to be a bit better in my case.
Click to expand...
Click to collapse
What about Monet? Is it integrated?
ibolito said:
What about Monet? Is it integrated?
Click to expand...
Click to collapse
I'm using a plain black background because of the AMOLED screen (it consumes less power this way), but I'll check it for you.
Does it have a separate menu item in Settings? I haven't found anything related in Display.
Google’s dynamic color engine, codenamed monet, grabs a single source color from the user’s wallpaper and generates 5 tonal palettes that are each comprised of 13 tonal colors of various luminances. These 65 colors make up the R.color attributes that apps can use to dynamically adjust their themes.
Click to expand...
Click to collapse
5tormChild said:
I'm using a plain black background because of the AMOLED screen (it consumes less power this way), but I'll check it for you.
Does it have a separate menu item in Settings? I haven't found anything related in Display.
Click to expand...
Click to collapse
5tormChild said:
I'm using a plain black background because of the AMOLED screen (it consumes less power this way), but I'll check it for you.
Does it have a separate menu item in Settings? I haven't found anything related in Display.
Click to expand...
Click to collapse
Monet is Android's theme engine that changes the color of the UI to match the wallpaper, if nothing changes when you apply a new wallpaper then sadly it might be not implemented with this update too.

Categories

Resources