Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
My Networks settings data gets erased each time i upgrade using the patcher tool. Frustrating because it won't let me Export my settings prior.
Open your networking settings in System preferences make sure the the network you want to start when you login to your desktop is checked to automatically connect all others uncheck the box
 

Attachments

  • Screen Shot 2019-07-27 at 8.17.46 PM.png
    Screen Shot 2019-07-27 at 8.17.46 PM.png
    2.4 MB · Views: 193
  • Screen Shot 2019-07-27 at 8.18.41 PM.png
    Screen Shot 2019-07-27 at 8.18.41 PM.png
    2.4 MB · Views: 155
I really can't choose I am really liking macOS Catalina but Mojave has the things like DashBoard, Photo's and maps work that's why I am keeping macOS Mojave on my MacBook 5,2 and macOS Catalina on my iMac 9,1 the best of both worlds so to speak well at least unless something really change by the GM release of Catalina we are still in Beta so who knows what is going to change throughout the year but its nice to see it working when it looked like it might not be possible on our older Macs that is the fun of it :)

I haven't totally "ruled out" Catalina yet as my OS of choice as you pointed out it is still in beta. I also have to get used to 2 things: (1) separate system volume and data (2) since I use Terminal a lot, 'zsh' default shell as opposed to 'bash'. Thanks for the response.
 
  • Like
Reactions: TimothyR734
Open your networking settings in System preferences make sure the the network you want to start when you login to your desktop is checked to automatically connect all others uncheck the box
Lol why are you telling me this ?
 
Same question for @dosdude1, @ASentientBot, @pkouame and other contributors.
Mojave, 100%. I don't trust the Catalina graphics patches (that I made) enough to upgrade yet, if ever. They are more of a "proof of concept" than an actual usable fix. I do have a Catalina partition, but I barely touch it.

There aren't really any new features in Cat that I'd use, anyways. Just a couple slight UI improvements that I can live without. I'm actually curious if anyone on a pre-Metal card is using 10.15 on a daily basis? I sort of hope not... it's not a good experience at all.

I'm still playing around and learning, in the hope of someday creating a better solution, but it's a tough problem and way above my current skill level.
 
@TimothyR734 and @jackluke,

You two have been one of the most active contributors/testers of both Mojave and Catalina on unsupported threads. Do you have any preferences on which OS so far? Thanks.

HighSierra/Mojave fifty-fifty, nevertheless @ASentientBot has done an extraordinary work bringing back graphics acceleration in Catalina for non-metal machines.
 
I have, and it was working fine until I felt my mini needed a restart. However, I did try re-applying the patches and the same thing happened upon restart.

Edit: I think Nightshift got activated somehow even though it shows as off in the window. I disabled Flux and it seems to be somewhat working, although I had to point Time Machine at my disk again. I also see that you can't see what I see in my screenshot...

Grrr.
[doublepost=1564200901][/doublepost]Here, maybe this will show it.


NightShift is broken in the current UpdatePatcher for 10.14.6, it is not shown in the message center and does not work.
I patched again. This works very well here with 10.14.6 and MacMini3.1. MacPro3,1 and all Hackintosh's.
Try this:
patched_signed_Night_Shift_CoreBrightness.framework_10.14.6.zip
Overwrite in Mojave S / L / Private Frameworks /
 

Attachments

  • patched_signed_Night_Shift_CoreBrightness.framework_10.14.6.zip
    276 KB · Views: 204
NightShift is broken in the current UpdatePatcher for 10.14.6, it is not shown in the message center and does not work.
I patched again. This works very well here with 10.14.6 and MacMini3.1. MacPro3,1 and all Hackintosh's.
Try this:
patched_signed_Night_Shift_CoreBrightness.framework_10.14.6.zip
Overwrite in Mojave S / L / Private Frameworks /
Nightshift works for me. The toggle in NC does not appear, but it still works after installing the patch from Dosdude.
[doublepost=1564324019][/doublepost]
Mojave, 100%. I don't trust the Catalina graphics patches (that I made) enough to upgrade yet, if ever. They are more of a "proof of concept" than an actual usable fix. I do have a Catalina partition, but I barely touch it.

There aren't really any new features in Cat that I'd use, anyways. Just a couple slight UI improvements that I can live without. I'm actually curious if anyone on a pre-Metal card is using 10.15 on a daily basis? I sort of hope not... it's not a good experience at all.

I'm still playing around and learning, in the hope of someday creating a better solution, but it's a tough problem and way above my current skill level.
You're right - on non-metal hardware, Catalina doesn't run as well as Mojave. I have it installed on a separate partition, but rarely boot in to it. Mojave is far more stable.
 
HighSierra/Mojave fifty-fifty, nevertheless @ASentientBot has done an extraordinary work bringing back graphics acceleration in Catalina for non-metal machines.

There is absolutely no doubt about it. Since I hardly ever use Photos and Maps, Catalina is technically more than enough for my use. While High Sierra/Mojave are still current there is just no need for it. I just hope that somebody knowledgeable still pays attention to Catalina developments later on as there is a very slim chance that at some point update Apple will quietly reintroduce the OpenGL support.
 
Does anyone know how to re-enable screen brightness control?

> iMac 9,1
> updated from 10.14.5 to .6
> post install patcher run after update
> patchupdater installed remaining updates upon first login
> several restarts and SMC resets performed
> all patches re-installed
> still same behavior: brightness control overlay reacts but without a corresponding screen brightness change
> screen brightness is stuck at lowest brightness level

Thanks in advance!
 
see if the works replace this in /System/Library/PrivateFramworks -Versions A folder also there is a free app called the brightness slider in the App Store make sure you have the display brightness in system preference set all the way just use the brightness slider to adjust the brightness this what I use on my iMac 9,1
 

Attachments

  • CoreBrightness.zip
    260.5 KB · Views: 153
  • Screen Shot 2019-07-28 at 8.23.53 AM.png
    Screen Shot 2019-07-28 at 8.23.53 AM.png
    3 MB · Views: 184
Mojave, 100%. I don't trust the Catalina graphics patches (that I made) enough to upgrade yet, if ever. They are more of a "proof of concept" than an actual usable fix. I do have a Catalina partition, but I barely touch it.

There aren't really any new features in Cat that I'd use, anyways. Just a couple slight UI improvements that I can live without. I'm actually curious if anyone on a pre-Metal card is using 10.15 on a daily basis? I sort of hope not... it's not a good experience at all.

I'm still playing around and learning, in the hope of someday creating a better solution, but it's a tough problem and way above my current skill level.
I think your patches are awesome seems very stable on my mid 2009 iMac I have been using it as my daily driver no issues except Photo's, Maps and Drift screensaver but that is a good trade off so don't cut yourself short :)
 
Last edited:
Hello,

If I want to keep macOS Extended (Journaled) partition in order to install Mojave, I won't be able to have updates via Software Update.

But can I update manually my system via the traditional combo updates?
Can I also be able to install manually the security updates?

Thanks in advance,

Frenchieisverige
 
  • Like
Reactions: TimothyR734
Hi,
no problem you can keep HFS+, but you have to create with every new update a new macOS Mojave Patcher stick, downloading the new version via tool and install it, and do the Post Install procedure.
Don't forget the Force Cache Rebuild!
Thats all.
Update function: Nope
Combo update: Nope
For APFS only.
Security Updates I put on auto, working here.
The manually option should work, but I never tried this out.
 
Last edited:
Does anyone know how to re-enable screen brightness control?

> iMac 9,1
> updated from 10.14.5 to .6
> post install patcher run after update
> patchupdater installed remaining updates upon first login
> several restarts and SMC resets performed
> all patches re-installed
> still same behavior: brightness control overlay reacts but without a corresponding screen brightness change
> screen brightness is stuck at lowest brightness level

Thanks in advance!

Hi @nitramwin
I had the same problem with iMac8,1 but I solved it in my message #15477 page 620.
I followed message #11156 from @dosdude1 but it did not work.
I had the idea to replace only one file on the 3 of the archive bkltpatch10.14.2.zip
Only replace the file "DisplayServices.framework" contained in /S/L/PrivateFrameworks (and repaired the permissions)

Code:
sudo chmod -R 755 /Volumes/NameOfYourMojaveDisk/System/Library/PrivateFrameworks/DisplayServices.framework
sudo chown -R 0:0 /Volumes/NameOfYourMojaveDisk/System/Library/PrivateFrameworks/DisplayServices.framework
sudo kextcache -system-caches
sudo kextcache -system-prelinked-kernel

It works with .3 .4 .5 and .6

Try to run install.sh content in the attached archive with your iMac9,1
 

Attachments

  • bkltpatch10.14.6_ONLY_FOR_iMac8,1.zip
    82.2 KB · Views: 181
Last edited:
see if the works replace this in /System/Library/PrivateFramworks -Versions A folder also there is a free app called the brightness slider in the App Store make sure you have the display brightness in system preference set all the way just use the brightness slider to adjust the brightness this what I use on my iMac 9,1
Really hate that App. Although I have to use it. It´s the only one that can "manage" brightness in a Macbook Pro late 2011 dedicated GPU disabled. But really doesn´t control the brightness. Many items apppears with maximum bright. The trackpad cursor, for example. And the emergent windows.
 
Last edited:
NightShift is broken in the current UpdatePatcher for 10.14.6, it is not shown in the message center and does not work.
I patched again. This works very well here with 10.14.6 and MacMini3.1. MacPro3,1 and all Hackintosh's.
Try this:
patched_signed_Night_Shift_CoreBrightness.framework_10.14.6.zip
Overwrite in Mojave S / L / Private Frameworks /

I never had night shift enabled. That said, f.lux was working perfectly before that random event happened after a restart. After another restart, it went back to working just fine again.

I have no idea what happened.
 
Hi,
no problem you can keep HFS+, but you have to create with every new update a new macOS Mojave Patcher stick, downloading the new version via tool and install it, and do the Post Install procedure.
Don't forget the Force Cache Rebuild!
Thats all.
Update function: Nope
Combo update: Nope
For APFS only.
Security Updates I put on auto, working here.
The manually option should work, but I never tried this out.

Hmm... that is not really convenient. I was hoping to keep the recovery boot partition in case of emergency.
I guess I'll do like others using APFS with the custom booting patch.

Thanks anyway.
 
  • Like
Reactions: TimothyR734
sudo nvram boot-args= will turn off verbose mode to check to see if you need to install the recovery fix while booting hold command R
Used this command: 'sudo nvram boot-args=' but still see verbose output while starting..
Also, while using CMD+R on boot I get 'NO' sign. Does it means I don't have recovery partition? Does your script add it permanently or should it be done with every update?
Thanks
 
Used this command: 'sudo nvram boot-args=' but still see verbose output while starting..
Also, while using CMD+R on boot I get 'NO' sign. Does it means I don't have recovery partition? Does your script add it permanently or should it be done with every update?
Thanks
Its jackluke's script and yes each time you do a macOS update the script needs to be applied and its normal to have some verbose message if you have used the APFS Rom Patcher or applied the APFS patch
 
Your recovery partition will be updated to 14.6, you won't loose it.
Hmm...
That is not what is written on dosdude's website. I have a cMP 3,1 from 2008 which does not support APFS natively. Thus, I'll need to use his boot patch. The downside of this patch is that it removes the possibility to boot on recovery partition.
Am I missing something?
 
Hmm...
That is not what is written on dosdude's website. I have a cMP 3,1 from 2008 which does not support APFS natively. Thus, I'll need to use his boot patch. The downside of this patch is that it removes the possibility to boot on recovery partition.
Am I missing something?
Is your hdd/ssd formatted APFS if so try running this script in terminal to fix recovery mode
 

Attachments

  • apfsrecoveryfix.command.zip
    1.2 KB · Views: 167
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.