Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App doesn't read brightness after waking up #1398

Open
3 tasks done
fidwj01 opened this issue Jul 1, 2023 · 1 comment
Open
3 tasks done

App doesn't read brightness after waking up #1398

fidwj01 opened this issue Jul 1, 2023 · 1 comment
Labels
Type: Bug Issue is a bug (e.g. Crash, …)

Comments

@fidwj01
Copy link

fidwj01 commented Jul 1, 2023

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

When the screen wakes up from being off, changing the brightness from the MacBook keyboard won't update the app which causes "sync brightness" to not work. I've tried every options under "Upon startup or wake", nothing worked.

Restarting the app can fix the issue.

Screenshot 2023-06-30 at 7 39 18 PM

Steps to reproduce

  1. Enable "Sync brightness changes from Built-in and Apple displays"
  2. Put the computer to sleep or wait until the display is off
  3. Wake up the computer
  4. Change brightness from the Touch Bar/built-in keyboard
  5. The change in brightness won't be detected by the app unless you restart the app

Expected behavior

It should behave the same after the computer wakes up from sleep/display off.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 13.4 Ventura
- Mac model: MacBook Pro 15 2017
- MonitorControl version: 4.1.0 Build 7034
- Monitor(s): Built-in screen and LG HDR WQHD
- Apple Silicon/M1 (yes or no): no
@Volodymyr-13
Copy link

Volodymyr-13 commented Jul 24, 2023

Same here, also Volume reset too. When I change volume using keys - it sets to 0 in real, but still showing like it set.

And during this, changing volume do nothing - it always stays 0 in real value.
Restart of the app bring volume to normal value.

Screenshot 1

@waydabber waydabber added the Type: Bug Issue is a bug (e.g. Crash, …) label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue is a bug (e.g. Crash, …)
Projects
None yet
Development

No branches or pull requests

3 participants