MonitorControl: Not working after sleep mode
Before opening the issue, have you…?
- Searched for existing issues
- Looked through the wiki
- Updated MonitorControl to the latest version (if applicable)
Describe the bug
Hi there,
it’s perfect and works totally fine with the new Huawei MateView. The only issue I have once in a while: Sometimes after my MacBook was in sleep the app is not working / responding. Both, the function keys for brightness and sliders do not work anymore. After closing and opening the app again, everything works fine.
Anyone knows why this issue can occur?
Cheers Dennis
Steps to reproduce
Occurs randomly
Expected behavior
This bug occurs randomly. Most of the time it works like magic.
Anything else?
No response
Environment Information (please complete the following information)
- macOS version: 11.5.2
- Mac model: M1, MacBook Pro
- MonitorControl version: 3.0.0 RC1
- Monitor(s): Huawei MateView, 28
- Apple Silicon/M1 (yes or no): yes
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 28 (15 by maintainers)
Here is an unsigned test build that should fix this issue if somebody would like to try it out. This requires you to click ‘Open Anyway’ in Preferences/Security. The source of this build is here - if you don’t trust in unsigned builds and want to build it yourself. Thank you!
Ok, I was able to reproduce the issue reliably and was able to debug it. The issue is that there are some instances when the display configuration changes with regards to the service port that the app uses to communicate with the display on Apple Silicon but macOS does not send a reconfiguration event so the app is trying to communicate using an outdated service port. This seems to happens whenever during sleep the display looses power or enters a deep sleep so the link between the mac and the display is severed, but the display cable remains attached during sleep.
I’ll change the sobering logic (this happens after sleep) so the app always does a display reconfiguration no matter what.
Unfortunately I have a lot to do in my job, so I can’t complete the “bug hunting”. But open the lid and close it again seems (in the couple few days) to eliminate the problem. So it don’t need to restart the app, to fix the problem. Very interesting! But I will answer all of your questions. hopefully this weekend!