Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

acousticbiker

macrumors 6502a
Original poster
Jun 28, 2008
835
144
I just upgraded from a 2020 Intel MBA to an M1 MBA. I had been using MonitorControl with the Intel MBA but with the change to an M1 MBA, that app no longer recognizes my Philips 329P9H (which the developer is aware of). I've tried:

  • Control Center: the Display brightness slider is grayed out and can't be toggled
  • System Prefs > Displays: I don't see a brightness slider
  • Monitor's on screen menu: Brightness is grayed out and can't be toggled
 
  • Like
Reactions: Sanpete

Gnattu

macrumors 6502a
Sep 18, 2020
935
1,198
MonitorControl is using macOS private framework, the OSD.framework, and because it is closed, we cannot re-compile it to an ARM version by ourselves. The fix is not possible before someone extract the universal binary of that private framework from Big Sur.
 

bill-p

macrumors 68030
Jul 23, 2011
2,747
1,249
Github tracking for this issue:

You can follow that thread to see if/when the issue is resolved. From what I'm seeing, it may be a bug in the OS itself. And as Gnattu said, we don't have control over internal Apple frameworks, so at this point, we can only wait for them to do something about it. This may be some minor revisions later. 11.1 beta doesn't seem to resolve this, either.
 

Gnattu

macrumors 6502a
Sep 18, 2020
935
1,198
Github tracking for this issue:

You can follow that thread to see if/when the issue is resolved. From what I'm seeing, it may be a bug in the OS itself. And as Gnattu said, we don't have control over internal Apple frameworks, so at this point, we can only wait for them to do something about it. This may be some minor revisions later. 11.1 beta doesn't seem to resolve this, either.
This is not a "bug", this is a "feature". Because the use private frameworks is prohibited by Apple and they will offer no help for you to use those frameworks.
It works before because the developers of MonitorControl extract the binary of that framework 3 years ago using some undocumented method, and integrates that into the project. Obviously, that binary was made for Intel, not AS. To make it work for AS, we need to extract it from Big Sur again.
 

acousticbiker

macrumors 6502a
Original poster
Jun 28, 2008
835
144
Thanks, everyone, the details are over my head technically but I’m subscribed to that issue on GitHub to keep tabs.

Assuming a fix for MonitorControl is not imminent, anyone have tips for how I can control brightness in the meantime?
 

bill-p

macrumors 68030
Jul 23, 2011
2,747
1,249
Well, it goes without saying... but I think you may have to use the controls on the monitor itself to achieve that in the mean time.
 

acousticbiker

macrumors 6502a
Original poster
Jun 28, 2008
835
144
Well, it goes without saying... but I think you may have to use the controls on the monitor itself to achieve that in the mean time.
As I mentioned in my original post, the controls on the monitor are also grayed out (just for brightness, I can toggle the others).

System Pref > Display > Brightness doesn't work ?
Also, as mentioned in my original post, there is no brightness toggle when I go to System Prefs > Displays

And another weird twist is that when I use the native MBA display, I can only change between the maximum and one notch below maximum brightness using the F1 and F2 keys - strange because the brightness in the Control Center (and Display prefs) is closer to the middle, which is where I prefer. The other function keys work and I can control brightness from Control Center and System Prefs > Displays in this case. This weirdness persists even after a reboot.
 
Last edited:

bill-p

macrumors 68030
Jul 23, 2011
2,747
1,249
As I mentioned in my original post, the controls on the monitor are also grayed out (just for brightness, I can toggle the others).

Oh, you mean the OSK of the monitor itself is grayed out? That's very odd. Have you tried a different port?
 

acousticbiker

macrumors 6502a
Original poster
Jun 28, 2008
835
144
Oh, you mean the OSK of the monitor itself is grayed out? That's very odd. Have you tried a different port?
I'm connecting via USB C and don't have an HDMI or Display Port cable to try those other ports on my monitor.
 

Six0Four

macrumors 6502a
Mar 27, 2020
772
685
As I mentioned in my original post, the controls on the monitor are also grayed out (just for brightness, I can toggle the others).


Also, as mentioned in my original post, there is no brightness toggle when I go to System Prefs > Displays

And another weird twist is that when I use the native MBA display, I can only change between the maximum and one notch below maximum brightness using the F1 and F2 keys - strange because the brightness in the Control Center (and Display prefs) is closer to the middle, which is where I prefer. The other function keys work and I can control brightness from Control Center and System Prefs > Displays in this case. This weirdness persists even after a reboot.

Damn. If Apple doesnt fix it maybe you will have to buy a magic keyboard with the brightness keys.
 

acousticbiker

macrumors 6502a
Original poster
Jun 28, 2008
835
144
I just spoke with an Apple Tech Support Senior Advisor and he said, independent of whether you're using an Intel or M1 Mac, brightness must be controlled on the monitor itself, that it has never been possible to do so in Display Preferences. Does that sound right? I no longer have my Intel Mac to test that.
 

bill-p

macrumors 68030
Jul 23, 2011
2,747
1,249
Well, he's wrong. Apple's displays have no on-monitor control. For instance, I still have the Thunderbolt Display, and it has to be controlled within MacOS itself. That also goes for speaker volume as well.

I don't have your specific monitor, but I can confirm at least that some monitors work like this.

As a last resort, get yourself a USB-C > HDMI adapter and see if that allows you to adjust brightness via the monitor?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.