Functionality "breaks" on power-on/boot on laptop w/ auto brightness

[ddiggles]

As I mentioned in issue #424 , the unison now works properly for me with auto-brightness enabled.

Upon powering on my laptop (from power off), I notice that Monitorian does not seem to work on boot - it doesn't grab the new brightness levels set by auto-brightness.

(I.e., lets say I shut down my computer at Monitorian was working, brightness level 40 of laptop display. I turn on my laptop the next day, and auto-brightness sets brightness to 55 as windows boots. Monitorian starts up (auto), but still reads the brightness values from last night's shut down [40], and is no longer automatically adjusting up and down - including unison with the external display.)

I can Monitorian to "re-hook" most of the time by toggling autobrightness off, then refreshing unison, then turning autobrightness back on.

[emoacht]

I reiterate that automatic brightness is device dependent and it is hard to even look into it and find a solution.

[ddiggles]

I reiterate that automatic brightness is device dependent and it is hard to even look into it.

Right, totally get it.

This sometimes happens on resume from sleep as well, however not all the time.

If I were to take a guess at the culprit, I think it's when the brightness level "changes behind Monitorian's back." I.e., if I power-on and auto-brightness sets a value that is different from Monitorian's "last value," (i.e. when I shut the computer down the night before) then it breaks it. Because internal auto-brightness always "goes first" when resuming / booting.

Is there any way for Monitorian to "get brightness value" for a specific monitor on boot/resume?

[emoacht]

It exactly depends on each system. I found that Surface Pro 8 does not return the actual brightness value when automatic brightness is on. There is no wonder it is the case in your system as well.

[ddiggles]

Gotcha. Well thank you for reading! Your app is great, very handy.