[Beta release] NativeDisplayBrightness 0.0.5 testing [updated]

alexramone said:

Please, HIGH SIERRA support!!! Thanks!

Click to expand...

Its already working with HS. I am using since GM.

Works well on LG 23MP68VQ-P. Thank you!

Dear God, Bensge, this tool is phantastic work! I was honestly baffled to watch the brightness adjust flawlessly across all my 3 monitors, all of them pesky screens different models and vendors — connected through either HDMI to Display Port or DVI to Display Port adapters. One of them is an 8 year old ASUS and... it just worked.

alexramone said:

Please, HIGH SIERRA support!!! Thanks!

Click to expand...

It works just fine with High Sierra, regardless if running APFS or HFS. A common issue when updating using the App Store is that your login-items may have been reset. Make sure FunctionFlip & NativeDisplayBrightness are running on start-up and you are golden.

Awesome tool, is there any chance volume control support could be added?

Tested on High Sierra (17B48). Amazing work! Got this working with original corded apple keyboard and Dell U2715H.
Thank you

AUTOMATIC SERVICE RESTART AFTER REBOOTING
I succeeded at working around the service autostart issue (where you had to kill NativeDisplayBrightness in activity monitor and restart it in order to work after booting) with writing a simple .command file:

Step 1: Writing the .command file
In a text editor write this code:
and save it somewhere with the .command extension (suggested example: "/Applications/BrightnessFix.command")

Step 2: Edit permissions
to execute the .command file, open the terminal and enter the following command:

Step 3: Make it auto-run every time you start your computer
To do this open Settings>Users & Groups>select your account and click on "Login Items".
To add your fix click on the plus and open it. Make sure to enable it by check-marking it.

Step 4: Changing sudo permissions (WARNING: Follow this guide very closely! Any edits of the /etc/sudoers file without using the visudo command method might result in corrupting admin permissions - you will be unable to execute files that require that kind of permission)

To make this fix work the file needs to execute automatically (without admin needing to enter their password in the terminal).
Change sudo permissions by opening the terminal and executing the following commands:

and enter your password
click "a" so that "-- INSERT --" appears at the bottom of the window. Now you are in edit mode.

Using the arrow keys navigate to:
and change it to match:

Press "ESC" to exit editing mode ("-- INSTERT --" should disappear).
To complete this process type ":wq" and press ENTER.

To see if it worked try restarting the terminal and type in a command with sudo, for example:
(this should open the Safari app)
If the terminal doesn't ask for a password it worked.

Hope this helped

This app does nothing for my Display.
Overlay shows on F1/F2 keypress, but no brightness is actually changed.

DDC/CI controls are enabled in the settings of my monitor (Acer V223HQ) and they works under Windows just fine.

I have an Intel HD 4000 graphics, if it matters.

kikiwora said:

This app does nothing for my Display.
Overlay shows on F1/F2 keypress, but no brightness is actually changed.

DDC/CI controls are enabled in the settings of my monitor (Acer V223HQ) and they works under Windows just fine.

I have an Intel HD 4000 graphics, if it matters.

Click to expand...

This only fixes the bug where the app doesn't properly fuction after restarting and has nothing to do with the app itself or monitor compatibility. For example this app works with my dell u2515h but I had to re-enable it every time I turned my hackintosh on. This fix does this automatically.

urby4444 said:

This only fixes the bug where the app doesn't properly fuction after restarting and has nothing to do with the app itself or monitor compatibility. For example this app works with my dell u2515h but I had to re-enable it every time I turned my hackintosh on. This fix does this automatically.

Click to expand...

No no no, I was talking about application itself, not about your Automatic Restart Service, sorry for a ambiguity. My fault