Closed joeyjbeckman closed 4 years ago
Which version are you on? Does this occur if you change the saved filter or only when the filter is on custom?
Version 3.0, when it is released, has a lot of backend changes to profiles and it's likely that this bug does not exist on it (not because I specifically fixed it, but because of how many changes there were).
I am on version 2.10.1. And yes it also occurs if I change the saved filter.
Turning the filter on and then off has no effect, but changing to a different filter and then back to my filter corrects the temperature. Any idea when version 3.0 will be released?
Basically once @raatmarien has the chance to look them over and make sure they are changes he wants to release.
@joeyjbeckman If you want to try this earlier to confirm whether the bug is fixed, you can get a debug version here (it's built from aa9c553, if you'd prefer to build yourself).
The debug build will install alongside the version from fdroid/gplay.
I tried the debug version, but unfortunately it seems like the bug has not been fixed.
Turning the filter on and then off has no effect, but changing to a different filter and then back to my filter corrects the temperature.
Does it correct the temperature the next time Red Moon turns on using the timer, or only when you do it manually?
Can you reproduce this issue for intensity and dim level, or only color? If so, can you reproduce it for 2 or 3 settings at once, or just one at a time?
If you could share a specific order of steps to take in order to trigger the bug, that would be helpful, too.
Closing because I don't have enough info to reproduce this and I don't 100% understand the behavior. If you (or anyone) can still reproduce this on the latest version of Red Moon, please open a new bug report :heart:
Using Red Moon on Marshmallow, I have saved a custom filter with a temperature ~2800K, but at sunset when it automatically turns on, it reddens the screen to ~800K.