Brightness Control

0 views

Skip to first unread message

Meinard Hartmann

unread,

Aug 3, 2024, 4:30:01 PM8/3/24

to plenivalfai

If i install whole KDE(1st option ), everything works fine, but with 3rd, Many were missing like network and other. Somehow i managed to sort everything except above two. In settings, there is no option to control brightness. Any idea which package should i install from the whole Plasma Package for brightness and hotkey.

You need to install the powerdevil package.
In terminal just do:
sudo pacman -S powerdevil
Just restart and you should be good to go. (This will enable and start the Power Management service on startup)
You can adjust the brightess when clicking on the Battery Icon or through your Laptop hotkeys.
Further Brightness adjustment settings are in System Settings > Hardware > Power Management

Screen brightness might be tricky to control. On some machines physical hardware switches are missing and software solutions may not work well. However, it is generally possible to find a functional method for a given hardware

My setup is a Mac mini M1 connected to a 27" Led Cinema Display via USB-C adapter for mini displayport. Working perfectly with MacOs Big Sur since always. But when I upgrade to Monterey, the monitor's brightness come locked at 50%, and brightness commands disappeared in System Preferences. Brightness keys on Apple Keyboard don't work either (f1, f2, f14, f15) I've tried apps like MonitorControl, but they only serve to decrease brightness ... the maximum brightness in these applications starts from 50% that the monitor is stuck. Anyone else having this problem? What can I do?

Afterwards, I disconnected the Cinema Display and connected it back into the Mac Mini M1 setup. Bam 100% brightness. The brightness level was maintained from where I had it prior to unplugging from Macbook Pro.

Same problem this was a bug / omission in the build of macOS Monterey. Apple please restore this service. I have a brand new Mac-mini and I would like to use my Apple LED Cinema Display 27 in. properly see image below.

I haven't tried the lunar.fyi yet which has been suggested by some people here, but it might be an option. As I said in another thread above, I solved my problem with the MonitorControl app. Details in: -24-cinema-display-brightness-control-monterey.2319531/ in the solution indicated by the user "flyabb". It worked perfectly for me (Mac mini M1 + 27" Led Cinema Display via USB-C adapter for mini displayport).

No, here for me everything ok using MonitorControl, custom max DDC, etc, very simple, there was no reduction in colors. But for those who are still looking for a solution, I think it's worth testing the MonitorControl app and the lunar.fyi and see which works best with your display. Thankfully there are options to use our veteran monitors ;)

Hi, I have the exact same setup and while the MonitorControl app allowed me to control my brightness again, the maximum brightness was at most around 50% of what the LED Cinema Display is capable of. I solved this by connecting the monitor to my old 2013 MBA and manually set the brightness to maximum by holding down ctrl and the adjusting the brightness with the F1/F2 keys. It seems that the Cinema Display "remembers" its brightness settings, when I reconnected it to the M1 Mac mini I was back to full brightness. This still doesn't ultimately solve the brightness control issue, but at least I can see what I'm working on now. Hope this helps, cheers.

I just got a Mac Studio and connected my trusty LED Cinema Display. I guess I didn't notice the lack of brightness controls in Monterey until now. It's unacceptable Apple would drop something as simple as a brightness control. The Cinema Display is my secondary monitor, and I can accept the current brightness. If I need to change it I'll try the third-party utilities.

What sort of an adapter did you use to connect your LED Cinema Display to your Mac Studio? My Mac Studio is a few weeks away from delivery, and I'd like to be able to use my LED Cinema Display/24" with it.

Displays control panel took a moment to adapt to the addition of a new external monitor but the brightness was good (and had been good when previously connected to a 2014 iMac). Following a restart however, the brightness has stuck at around 50%. Displays control panel offers no Brightness control. I have installed Lunar, Monitor Control and Brightness Slider, with no luck whatsoever.

Each of those additional controls (recommended here and on MacRumors by users experiencing similar problems) shows Cinema Display Brightness at 100%. Monitor Control and Brightness Slider do enable further dimming (to -50%) but Lunar has no effect whatsoever. Changing brightness via the F1 and F2 keys works as normal on the new Studio Display but shows a lock under the Cinema Display on-screen brightness display.

I'm having an issue with my Samsung N210 laptop that has the GMA3150 graphics controller (Atom N450 CPU). The problem is that after downloading recent Intel graphics drivers I can no longer change my screen brightness. This problem has been reported long ago elsewhere, at least in the sammynetbook.com forums. Following their advice, I uninstalled the driver and went back as far as version 8.14.10.1972 (the 64-bit version of the driver). The next driver available from Intel's site no longer allows me to change screen brightness, nor does anything newer.

Now, screen brightness on the N210 netbook is controlled by pressing Fn + Up and Fn + Down. It also requires a program from Samsung called "Easy Display Manager". Trying to adjust screen brightness using the latest Intel driver bring up a graphic produced by Easy Display Manager (EDM from now), but the brightness bars in said graphic don't move, nor does screen brightness change.

The problem is not just with Samsung's EDM program. There is a brightness slider in Windows 7 Power Options, and that also doesn't work after installing a driver later than .1972. With .1972 the Windows screen brightness slider works again, just like Samsung's EDM.

What is causing all of this and is there any way to use drivers less than a year old while still being able to control screen brightness via hotkeys? It's an important feature of any laptop. It just HAS TO WORK, don't you think?

The workaround suggested above won't help on my Samsung N150 Endi netbook running now under Windows 10 (which otherwise perfoms way better than Win7!) either. COULD INTEL PLEASE DO SOMETHING ABOUT THIS FLAWED GMA 3150 DRIVER AT LAST??? This really is shameful, considering that this bug has been reported for 4 years now.

I have fixed this issue on my Samsung N150 netbook about 20 minutes ago. Let me give you the particulars and then BOTH a link to the page I got this info from AND the steps I took to get it working in Windows 10. DTG: 15 August 2015 - 10:48 CDT (U.S.A.) (GMT-6)

This driver is the one Windows Update is pushing onto my netbook in Windows 10. Like all the other complaints above, it won't let you change the brightness of the backlight, so you drain your battery faster when not plugged in.

I cannot confirm which part of ANY of this is what worked, but I know that I did all instructions directly using regedt32.exe (I'm an experienced IT professional, by the way) and my Brightness controls now FULLY WORK after a restart.

This does work, indeed, thanks a lot! To speed up the procedure, however, I suggest to copy and paste these lines (which are also listed (w/o comments) in the link you mentioned) into a .reg file to be created using the new Windows 10 "Editor"--and then double-click on it, of course , before rebooting the system.

Now that it's morning, I've had some time to go through line-by-line those added registry keys. I can confirm that I can still control the brightness after removing all the "added" entries above. You only need to change the number value for the FeatureTestControl values to make it work.

Because I have read that sometimes the FFFF value might prevent the screen from even turning on after recovering from Standby ( -8/samsung-n150-plus-i-cant-control-bright/701.html Samsung n150 Plus, I can't control bright), I have changed the values to FFFE and I still have brightness control. I tested my Sleep mode just now and with the FFFE value in all positions, it does in fact come up properly after Sleep. I have Hibernate mode disabled for personal reasons. I don't much care for hibernate. Windows 10 boots up fast enough on its own for me to not care. I am running a Crucial MX100 250 GB SSD drive, after all.

I think I'm fully set with Windows 10 now. Everything works, all hot-keys work, all programs work properly (even the Samsung ones off the website). I'm pretty happy with Windows 10. It breaking my SLI on my desktop, however....that's another story. >.

Glad I could help you out. I'm trying to spread the word on how to fix this so people can upgrade to Windows 10 without having to worry about their battery life. Lord knows we can't trust Intel or Samsung to fix their driver packages when they're this old. I've already sent an e-mail to Samsung about this resolution, but I doubt I'll ever receive a reply or that they'll do anything.

You can even do like apastron said and make a registry batch file to do this. Make these three changes and then reboot your computer. You should have brightness control back if you have the Samsung Easy Display Manager software installed. You can get that app from Samsung's website for the N150 ( -N150-JA03US -N150-JA03US).

EDIT: Ok, so the Brightness keys work just fine, but something that still doesn't work are the Brightness sliders in Windows itself. Because of this, the brightness doesn't auto-change when you unplug the power supply and move to battery power and vice versa. I'll continue working on this issue until I have a solution.

So I'm still testing different values and registry settings, because even using FFFE, the Windows sliders still don't work. Yes, the FN keys change the brightness just fine. But I want to get the Windows sliders working so that when I plug/unplug the power cable, the brightness will automatically change to fit the change in power profile. To do this, I'll have to really study the entire registry log for that chip in Windows 7 so I can replicate it to Windows 10. I'll keep this thread updated with any progress I make.