On the lock screen and ambient display, the display doesn't respect night mode. It is always in "day" mode. Once it unlocks, it fades to night mode. Has anyone else experienced this? Is there a fix to enable night mode on the lock screen/ambient display?
Bump. Has anybody else noticed this?
rriegner said:
Bump. Has anybody else noticed this?
Click to expand...
Click to collapse
From several reviews Ive seen the fingerprint sensor needs to flash at max brightness to work then the screen will go to whatever brightness you've selected
mpetruzz said:
From several reviews Ive seen the fingerprint sensor needs to flash at max brightness to work then the screen will go to whatever brightness you've selected
Click to expand...
Click to collapse
It's not the brightness that's the issue though, it's the fact that it's not tinted yellow for night mode.
The brightness flash is still unnecessary though. When registering a fingerprint, the rest of the display is dim, while the green circle is full brightness. There's no reason they can't do the same thing on the lock screen.
While verifying that fact though, I noticed that the fingerprint registration page disables night mode as well, so I guess it is a fingerprint thing after all. I still think it could be implemented better. I wonder if it's possible to counteract the tint from night mode on just the fingerprint sensor light.
I've found the same. A bit annoying. There should be an option in night maybe to disable fingerprint when night mode is on
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.
Hi,
since 2 months ago, i meet an issue which is kind of boring.
I have the ambiant display with the tap to wake mode ON and the fingerprint sensor activated.
At the begenning of my use, i have not met any issue : ambiant display was functional (i.e written informations on a black screen).
Now, when i wake up the screen with a double tap to wake gesture , informations are stile written but, this time, on a grey flickering/flashing screen (kind of stobe ligh effect). At the moment i touch the fingerprint sensor, it stops to be flashing grey and return to normal black.
Does someone have any idea of this issue? I am hesitating to proceed to a factory reset in order to see if it solves it.
Thanks in advance for your comments.
Does anyone else has a problem with ambient always on display not working? Most of the time it is there, but even if I turn off the Scheduler, sometimes off for hours, just the black screen. 10.3.10 MIUI
Yes, the same issue for me. Little annoying, but I hope it will be fixed in the next update. Maybe I will for now just turn off the always-on display.
You should read the description
Could you be more specific please?
"To reduce power consumption, items won't be displayed in the following situations:
1. When your device lies in dark for a long time.
2. When DND mode is on"
Haha, didn't saw that, but still, my room wasn't dark at all and it still went off. For now I have just disabled that option, and if that is only big bug I will be super happy.
Hi Guys,
I have the Ticwatch Pro 3 and it's great.
But I have a little problem. I love Always on Display (AOD) and in some situations I also like to set the display not to go into dimming mode via StayLit Wear with the "indefinitely" mode. This also worked great with my Huawei Watch 2, even when I put my arm down on the home screen, even if you can see the time normally. If I set the "indefinitely" mode with the StayLit Wear app on the Ticwatch Pro 3, it works that the Ticwatch Pro 3 always remains active, but only if, for example, I have the settings open or I am in the app selection and if an app is open even if I put my arm down. It also works on the home screen when I have my arm up all the time and look at the clock. But as soon as I'm on the homescreen and I turn my arm away or take it down, the watch always goes into dimming mode, despite the "indefinitely" mode of StayLit Wear.
That could actually only be due to the fact that Mobvoi has specified this in some system file for Wear OS, right?
Can I possibly edit the specific system file, or do something via ADB Shell so that I can set it so that the Ticwatch Pro 3 does not go into dimming mode as soon as I turn the arm away or take it down so that it is only time-controlled again is when the display goes into dimming mode and is not forced to dim when I turn my arm away or take it down?
Possibly for better understanding:
So it works with my Huawei Watch 2.
However, with the Huawei it is also the case that the change to the dimming mode does not happen automatically when I turn my arm away or take it down, but it is purely based on the set time of seconds until the display in the AOD is dimmed.
With the Ticwatch, however, this is set somewhere in such a way that the display not only goes into dimming mode based on the set seconds, but also presumably controlled by a sensor, from a certain angle regardless of the set seconds, immediately goes into dimming mode.
And I want to get rid of the sensor, that the dimming mode is forced and my question is whether someone knows where I can do that.
Thank you in advance for your feedback.