This happens because the patched files for the volume control patch are overwritten when updating the system. Just boot into your patched macOS USB drive, and re-run the post-install patch with volume control patch selected.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.12 Sierra Unsupported Macs Thread
- Thread starter redheeler
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Just wanted to reply on this post to say I had the same issue on my iMac Mid 2009, that app works perfectly to fix the brightness issues I was having. Was about to give up and restore the machine.
Thanks for posting that information about the app!
Could you please provide more specifics (link and/or website) of the exact application you are referring to ???
AFAIK this does not adjust the backlight it only draws a dark rectangle on the screen. For actual brightness control post 10.12.4 try http://bergdesign.com/brightness/
Better yet, let's ask https://www.tonymacx86.com/threads/...rol-using-applebacklightinjector-kext.218222/ this guy how we could get backlight support for our machines. We might not even need to load custom kexts, maybe it's just a matter of creating a special EDID string and a display override whatever the heck that means.
I can confirm that AUSEnabler is still up and running. Just updated my macPro 3,1 from .2 to .5 with no issues.
Actually, I finally just tried this and it did NOT work. Volume is still blasting at full volume so it's basically "binary" volume control now: 100% or off.
Any ideas?[EDIT] After applying the Volume Control patch ONLY a second time (instead of selecting the full i'Mac8,1 proposed packages) and then forcing a cache rebuild, I regained control over my volume control! #yay
Last edited:
I seem to have an issue with auto restart. I have tried the command sudo pmset autorestart 1 but it will not work. I check it by using pmset -g. And I haves pulled power too. I have tried it using terminal in the os and I booted to the USB and tried using that terminal. I have Yosemite and el capitain drives also setup and the command works fine and functions fine. Is there a problem with the patch? Or has the pmset commands changed? I don't know what else to check.
So, I can register with an Apple ID and use the App Store on a patched Sierra without issues?
After the 10.12.5 update, the backlit function on my 2008 MacBook Pro doesn't work anymore. Ironically, it works just fine on Windows , but when I turn the backlit on in windows, it can't be turned of in Mac OS anymore
, but when I turn the backlit on in windows, it can't be turned of in Mac OS anymoreAfter the 10.12.5 update, the backlit function on my 2008 MacBook Pro doesn't work anymore. Ironically, it works just fine on Windows
Keyboard backlight works on MacBookPro4,1.
its seems to be working fine on my 2007 iMac. With the latest beta. brightness control in Display Preferences hasn't worked since 10.12.4. But Night Shift is working fine after I changed the model year in CoreBrightness. But I have been using what I linked for brightness control. Maybe its different on different machines?
[doublepost=1496476913][/doublepost]
I guess the ambient light sensor patch from the post install does not fix this problem on any machine? I noticed dosdude1 mentioned that a few pages back but I never seen a reply to if it works or not.
In your first quote, pretty sure they're lamenting about the MacBook 13" 2009 (5,2) - brightness controls were broken by 10.12.5. The tonymacx86 thread looks interesting for a fix...someone would need to find the time to work on it.
Yes, the ambient light sensor patch does fix it on multiple machines (certainly on the MBP 4,1 - 2008). @G5-PowerLifter needs to re-apply the post-install patch for it to get his backlight working again on his MBP.
Wonder how much damage will be in the next version of macOS? Hope they don't change anything with SIP or the Kernel
Hope they don't change anything with SIP or the Kernel
@ac2334 - some people believe that the OS gets cluttered by upgrades (but, most of us do it this way) - there's really no reason I can think of for doing a clean install. (unless there's lots of Apps you'd like to uninstall)
@TMRJIJ - well, you KNOW there will be kernel changes (be odd to have a *NIX OS upgrade without them)....I think there could be changes to both the kernel as well as SIP to support continued development of APFS.
@TMRJIJ - well, you KNOW there will be kernel changes (be odd to have a *NIX OS upgrade without them)....I think there could be changes to both the kernel as well as SIP to support continued development of APFS.
I'am using all of my current macs the same install as the first one. A 10.3 with many times migrated from machine to machine and from PPC to 32bit Intel and later to 64 bit Intel. Everything works grate.
Not really. Sierra .5 is working just fine for me and "High" Sierra, feature-wise, feels more like a point update.
However defaulting to APFS is big. Anyone willing to share their experience with the APFS preview?
it'll be funny to see, if there could be an option to even upgrade my 2008 MacBook Pro to "High Sierra" (what a name..) to use that new apple file system. Apart from that, there wasn't much exciting stuff going on on today's keynote, No Mac mini an unffordable iMac Pro (which looks admittedly cool though) and the rest just iOS stuff. It appears to me, that apple is turning the iOS devices more and more into mac lookalikes. I'm sure in the not to distant future iOS and Mac OS will be the same.