Hi peoples
Does anybody know of a way of reducing the backlight brightness below the stock settings?
I've tried various screen filters, such haxor Screen Filter, but these apps are rubbish IMO. All they do is apply a grey transparency filter over the screen, they don't actually reduce the backlight brightness The result is a trick, the screen looks darker but it's really only because the white pixels are made grey. The problem with this approach is that it messes up the contrast and colors, and gives a washed out look.
I like to sometimes use my N10 in a pitch black room, which needs a very dark screen. My old Galaxy Tab 8.9 was good for this, because the backlight was able to go much darker than the N10. The thing is, I know the N10 hardware is capable of having a darker backlight because if you don't touch the tablet for a few minutes, the screen first goes dim before it turns off.
I would like to be able to manually activate the very dim screen setting, or better still, have a lower brightness range available in the brightness settings.
RootDim
mag13 said:
RootDim
Click to expand...
Click to collapse
Thanks - works a charm!
Hey guys
Was just wondering if setting the display mode to Basic will use less battery than if you set it to Adapt display.
Colours are more vibrant and brighter on Adapt display.
My S6 have an option to change the screen mode from adaptive to basic mode, is there an option in 6p too?
there's an sRGB switch in the developer's setting that turns off the saturation and displays more accurate colors, if that's what you mean
Yes! That's it, thank you so much.
Recently I found out that whenever the brightness is set to minimum value (or low enough to a specific value), the screenshot that I take will become greyish.
Is it possible that Amazon integrated a grey overlay into the brightness setting? My hypothesis is that when the critical point is reached, instead of lowering the actual brightness, Fire OS draws a grey overlay on the screen.
Hey guys,
so far I’m really happy with my new 6T. But I’ve found one bug which I’d like to see fixed.
I like to use either the sRGB or the DCI-P3 color profile as the standard color profile is just too saturated and contrasty for my liking. And at night, I’d like to use the display night mode, to reduce blue light. Unfortunately, if the screen is off and I wake up the phone, (doesn’t matter if it’s via face unlock or screen unlock) the screen changes itself to Standard color profile and you can slowly see the night mode take effect – but on top of the standard color profile which is, as mentioned above, not my cup of tea. It happens with both sRGB and DCI-P3 profiles and night mode enabled.
Only if you then turn night mode off again, you can literally see the colors jump back to your original set profile. Which obviously cannot and should not be the intended way night mode works, as night mode also reduces contrast and saturation. This can be seen if you have set the color profile to Standard in the first place and then turn on night mode, which basically shifts the colors to sRGB. Curiously enough, if you then lock the phone and wake it up, everything is as it should be and as I'd like it to be when sRGB is the set profile, meaning the color profile stays sRGB like and night mode is in effect.
I’m running completely stock Oxygen OS 9.0.5., no root, didn’t unlock bootloader or anything.
Does anyone else experience this behavior? Any help or suggestions are greatly appreciated!
Thanks!
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
rriegner said:
I've been trying to find an answer to this issue since I got the phone. It is appalling that both ambient display and the lock screen are not affected by night mode. It is completely counteractive to how night mode should work.
And I have no idea why they disable color profiles when in night mode. In the settings menu, once you enable night mode, the screen calibration option is greyed out. But it is clearly not a technical limitation because enabling sRGB and then night mode produces the proper effect of a night-shifted sRGB color space. Waking the phone at night turns night mode off on the lock screen, and puts it in standard profile, then shifts to night-shifted standard profile after unlocking. I hate it.
If you come across an answer, please post it back here so others (and I) can find it.
Also, small technical note: night mode does not affect saturation or contrast or color space, only color temperature. sRGB is an entirely different color space with different saturation and gamma curves.
Click to expand...
Click to collapse
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
ef_x said:
Thanks for your reply. Glad I'm at least not the only one noticing this issue.
As to your last statement, I would've thought so too. But this does not seem to be the case here. If you set the color profile to standard and then turn on night mode, the color space gets changed to sRGB, at least from what I can see. It looks completely different than the falsely activated night shifted standard profile, and looks exactly like the night mode in top of the sRGB mode, so less saturation and contrast (gamma). I don't know if this is intentional but makes it all the more confusing, because it retains the combination of sRGB + night mode even after locking and unlocking.
Click to expand...
Click to collapse
Wow, you are exactly right. I never thought to try that method, but I agree with your assessment. In standard calibration, night mode also toggles sRGB on and off. This is not affected by lock.
In both sRGB and DCI-P3, toggling night mode does not change calibration, but waking from lock leaves it stuck in standard calibration until you toggle night mode again.
And in all scenarios, the lock screen is never in night mode. Also, the add fingerprint page disables night mode and sticks you back into standard calibration with night mode, no matter which calibration you had selected. So the add fingerprint page acts exactly like the lock screen. This leads me to believe that the fingerprint sensor needs a very specific color of light to operate. But that doesn't excuse the fact that calibration keeps switching and getting stuck. I would think they can override that though.
I just made a post about this on reddit. Maybe up vote it to help increase visibility as this is the first mention I've seen about this issue other than this reddit post.
https://www.reddit.com/r/oneplus/comments/9wkkgj/_/
The whole night mode issues and ambient display going max brightness are super frustrating. This is my first non Nexus/pixel since the oneplus 1, and these small issues are making me question if leaving for a less stable manufacturer was a good idea
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
rriegner said:
After doing some more testing, I've determined this whole ordeal is tied to the fingerprint sensor. Deleting all my fingerprints (disabling it entirely) has resolved all the issues of switching calibrations an night mode toggling. Everything works as it should, except ambient display never is night mode. But the lock screen is in night mode.
I'm personally ok with this for now. Face unlock is very quick, and smart lock keeps my phone unlocked at home at night. Hopefully this gets fixed for real in a future update.
Click to expand...
Click to collapse
Exactly what i discover. Night mode not works when fingerprint senor is active which means on screen lock and app lock.Don't know weather they do it intentionally(to work fp sensor fine) on not but this is seriously irritating and painful to eyes.