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.
Sorry if I might have given old info, have deleted my post.
There is still a switch in Time Machine to switch it off/manually though and I assume you are saying it does not delete snapshots anymore.

Seeing the same. My workaround is to manually sleep the computers rather than let it fall asleep which so far appears to be a stable solution.
@houser, I finally was able to get 14.1 beta 3 installed on my iMac 15,1 using the 10-15-23 version of OCLP 1.1n.
However, the Time Machine "switch" you are seeing in your 14.1 b3 install is still "missing in action" and presumed to be a machine specific entity. Otherwise, I have not noticed any differences, compared with 14.0 (albeit, I haven't used it much).
 
@houser, I finally was able to get 14.1 beta 3 installed on my iMac 15,1 using the 10-15-23 version of OCLP 1.1n.
However, the Time Machine "switch" you are seeing in your 14.1 b3 install is still "missing in action" and presumed to be a machine specific entity. Otherwise, I have not noticed any differences, compared with 14.0 (albeit, I haven't used it much).
Well done. There are a number of things that have been improved, as always with point releases to a major release.
I just realised that you do not have a backup disk selected in the screenshot you gave in your post #2,356
The switch you are missing should show when you select a disk.
 
  • Like
Reactions: deeveedee
No offense, but that warning hasn't stopped anyone from using them. Let alone the security warnings in the nightly disclaimers (but that's OT).
You like to have the final word …
The first filter for installing experimental software is to be able read and do some research without asking very easy questions.
I can’t avoid beginners to do what they want, but I am not sure I am ready to answer infinite questions for an unsupported software.
 
Well I took a couple more runs at it.. Starting from Monterey, build/install OCLP to the EFI. Build a fresh Sonoma install from OCLP, right from the host Mac Pro. Wipe SSD and try to install. Gets stuck every time.

Sometime weird/different around Sonoma, as my Monterey clean installs always work great. I've probably tried six times now. I suppose I'll have to try again if we think OCLP 1.1 has substantial changes for my situation.
NVRAM reset. 🧐
 
  • Like
Reactions: deeveedee
Ah. Hadn't done that in a while. Will give it another go w/NVRAM reset when 1.1 is ready.

Still, don't you think it's weird that Monterey installs with zero issues and Sonoma cannot?
Not strange. Resetting NVRAM is not unusual with Open Core when changing versions of macOS. Welcome to the world of hackintosh.

EDIT: It still might not fix the installation, but those who have been using Open Core before OCLP was born are used to NVRAM resets.
 
Last edited:
  • Like
Reactions: hvds
@Sven; I think it is much more important to "cure" those crash on wake episodes than to understand why they happen, which is probably due to bad or incomplete programing on Apple's part. The pmset command <sudo pmset -b tcpkeepalive 0> is one of a set I found years ago, on a Japanese blog (all in Japanese of course, except for the command themself). I have used them all for years with no adverse affects. All shown below:


macOSの寝相について考えたこと -- `pmset` - ばかもりだし

電源まわりの設定, 前々から何となく気になっていて,なら何故すぐやらない,先日も触れましたが,マシンの新調きっかけで,この辺を整理しておこう,と思ったわけです. 勿論"あくまで自分レベル"で浅く😛 つか,スリープ,よくわかんない. 後で触れようかとは思っているのですが,いまいちスッと入ってこないんですよね. 思うに,"何処が分からないのか,が,分かっていない". そんな状態で,見切り発進です. % sw_vers ProductName: Mac OS X ProductVersion: 10.14.3 BuildVersion: 18D42
baqamore.hatenablog.com

pmset -g Shows the settings you have set now.
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
sudo rm /var/vm/sleepimage or sudo rm /private/var/vm/sleepimage
--Ignore any message saying there is no such file
Create a blanked zero-byte file so the OS cannot rewrite the file:

sudo touch /var/vm/sleepimage or sudo touch /private/var/vm/sleepimage

Make file immutable:
(sudo chflags nouchg ... to revert)
sudo chflags uchg /var/vm/sleepimage
or
sudo chflags uchg /private/var/vm/sleepimage
The sleep image file is actually in /private/var/vm/ but /var/vm/ is a symbolic link to that location.

sudo pmset -a proximitywake 0
sudo pmset -b tcpkeepalive 0
--This command may produce a warning saying some features may not work properly. This is fine, it simply disables Internet access during sleep. This is the same as disabling "PowerNap" Apple's badly implemented (demented?) attempt to have apps update themselves during sleep behind the users back.

sudo pmset -a standbydelaylow 86400
sudo pmset -a standbydelayhigh 86400
sudo pmset -a highstandbythreshold 0

If necessary;
sudo pmset restoredefaults
Hello,

If you want a simple solution to schedule your Mac, I write software with a GUI like the old MACOS.
My site to download: http://bmaillard.free.fr//programmer/ (the source is online)
I test it on Ventura and Sonoma.

Unknown.png


Enjoy
 
Last edited:
Hi to all. I am new to this forum. I want t ask about an issue that i have with my Mac and OCPL.
I installed the latest MacOS Sonoma in my iMac 27" Late 2009 10.1 and the blutooth does not working.
I use USB mouse and keyboard with no problem.
Before that i had install MacOS Ventura and blutooth was working just fine.
Is this a bug of OCPL 1.0.1 or is it something wrong with my Mac?
Thanks in advace for your time and help.
Welcome. Look at posts 2024, 2052 and 2057. I have a 2009 21.5" iMac 10.1 and also lost my bluetooth. Right now that iMac is in VA, while I'm in FL, so I haven't had the opportunity to try the hack explained in the above posts. Please pass on if it works. Cheers, Jim
 
  • Like
Reactions: jxid
I had the same experience with my MacBook Pro 5,2.
The KP log incorporated (as a "spoiler") into post #2284 on page 92 is identical to yours. The internal SSD is on SATA, while external SSD drive (Samsung Shield T7) is connected via a USB. Booting into either configuration caused an early hang irrespective of installation method, whether OTA or via USB installer.
No problem rebooting into Sonoma 14.1 beta1 after failure of the update.
I took one more step in testing, and attempted to boot via a USB thumb drive inserted into the USB hub I use to successfully login into MacBook Pro 5,2 after each system upgrade. The result was the same early KP. The USB hub test was prompted by the panic report, which nominally seems to center on the IOkit and USB interface(?), and the need to use the hub after each system update.
Hope a solution can be found. Latest OCLP 1.1n, from October 12, 2023 does not change the result.
Thank you to developers for their incredible work.
MBP5,2: it is able to install 14.1 betas now (verified that b2 USB installer boots well, but didn't try to install).
Developers were very active over the weekend, providing excellent updates to OCLP. OCLP 1.1.0n from today includes an update for USB1.1 which now allows usage of 14.1 betas. PatcherSupportPackage is now 1.4.1.
Applied the post-install patches of the new 1.1.0n to 14.0, no problems. KDK used is now the one belonging to 14.0.
Now doing OTA update of 14.0 to 14.1b3 on internal SSD (letting it run unattended).

MBP11,1: installed 14.0 on external SSD. Internal SSD for now remains on Monterey as this needs no root patches.

Thank you developers!


Edit: installation of b3 on MBP5,2 finished successfully. Root patching tbd later.
 
Last edited:
  • Like
Reactions: deeveedee and K two
Hello,

If you want a simple solution to schedule your Mac, I write software with a GUI like the old MACOS.
My site to download: http://bmaillard.free.fr//programmer/ (the source is online)
I test it on Ventura and Sonoma.

View attachment 2296174

Enjoy
Thanks @Bmld! I am grateful to you for having created and distributed this utility for free; I t’s very useful! It's sad to see that sometimes, apparently without any real reasonable reason, Apple intervenes to purge useful features or make changes that make the System no longer child-proof and simple people.
People like you, dear Bertrand, are precious in the world. With your precision, generosity and kindness you could also help perfect OCLP :)
Thanks again.
 
Last edited:
  • Like
Reactions: deeveedee
What about FaceTime, any issues there? Is there anything not functioning as intended on your machine?

I haven't found anything yet not working. FaceTime, Messages, Netflix in Safari, Photo Booth all working OK.
 
Hello,
How did you manage to display this ?
Thanks
 

Attachments

  • Screenshot 2023-10-15 at 23.21.41.png
    Screenshot 2023-10-15 at 23.21.41.png
    200.2 KB · Views: 85
Yes, very well, the T1 is now running for me again with 1.1.0n.

Now the only problem I have is that if the Macbook has been in standby for a longer period of time and I open it, it's as if it was switched off.

It just doesn't work for me anymore. Does anyone here know what this could be?

Macbook Pro 13,2
 
Yes, very well, the T1 is now running for me again with 1.1.0n.

Now the only problem I have is that if the Macbook has been in standby for a longer period of time and I open it, it's as if it was switched off.

It just doesn't work for me anymore. Does anyone here know what this could be?

Macbook Pro 13,2
#2363 has worked for me so far. Have not done #2364, but might be worth trying.
 
  • Like
Reactions: Mark Meretz
Hello everyone, newbie user here!

I have successfully installed Mac OS Sonoma 14.0 on a MacBook Air 13 Early 2015 (i7 2.2 Ghz, 8Gb of ram) with OCLP 1.0.1 and everything seems to work fine (except for the continuity camera, but I think it's a known bug).

Anyway, my question is about YouTube streaming above 1080p resolution with Safari (17).

I have already read something about the VP9 unsupported protocol, but I understand that with the latest release of Mac OS and Safari the problem was fixed (so it's possible to stream in 4k res for ex).

I have tried to enable in the experimental features "VP9 SW Decoder on Battery", "VP9 Encoder" and "WebRTC VP9 Codec", but I can only find the latest option. Enabling it changes nothing.
Can't find "VP9 SW Decoder on Battery", "VP9 Encoder" in the experimental menu.

So, there's really a way to enable 4k video streaming on YouTube (in reality I need only the 1440p resolution) also on our unsupported MacBook?

Or I'm missing something??

Thanks in advance!

P.s. Vimeo 4k 60fps videos works like a charm
 
  • Like
Reactions: olad
Hello everyone, newbie user here!

I have successfully installed Mac OS Sonoma 14.0 on a MacBook Air 13 Early 2015 (i7 2.2 Ghz, 8Gb of ram) with OCLP 1.0.1 and everything seems to work fine (except for the continuity camera, but I think it's a known bug).

Anyway, my question is about YouTube streaming above 1080p resolution with Safari (17).

I have already read something about the VP9 unsupported protocol, but I understand that with the latest release of Mac OS and Safari the problem was fixed (so it's possible to stream in 4k res for ex).

I have tried to enable in the experimental features "VP9 SW Decoder on Battery", "VP9 Encoder" and "WebRTC VP9 Codec", but I can only find the latest option. Enabling it changes nothing.
Can't find "VP9 SW Decoder on Battery", "VP9 Encoder" in the experimental menu.

So, there's really a way to enable 4k video streaming on YouTube (in reality I need only the 1440p resolution) also on our unsupported MacBook?

Or I'm missing something??

Thanks in advance!

P.s. Vimeo 4k 60fps videos works like a charm
As far as YouTube 4K, and Safari, it's worked for a few years with the latest releases of macOS and Safari. I wonder if something is wrong with your setup specifically. I can double check though, but the last time I played a 4K YT video in Safari, I remember it working without problems. Both on Monterey (officially supported), Ventura, and Sonoma (patched.)
 
  • Like
Reactions: Gianca90
As far as YouTube 4K, and Safari, it's worked for a few years with the latest releases of macOS and Safari. I wonder if something is wrong with your setup specifically. I can double check though, but the last time I played a 4K YT video in Safari, I remember it working without problems. Both on Monterey (officially supported), Ventura, and Sonoma (patched.)
Thanks, waiting for an update from you!

Additional information of my setup:

Open core settings: Moderate spoofing of MacBook Air 8.1 (to enable Universal control), the rest as default configuration but I have enabled again GateKeeper.

Using WIPR for ads blocking and NextDNS.

Nothing else....
 
@Gianca90 go to this video here:
in Safari. I'm using Safari 17.0 on Monterey, it will play in HD by default but press the full screen button and it should change to 4k. The only reason it might not is the GPU in that MacBook might not handle it well, I had trouble playing 4K video on a 13" late 2013 MBP with a supported OS, even after safari got support.
By the way, I did the test on an iMac 17,1 late 2015, 27" iMac, but I think it's fair test subject as it worked under open core installed versions as well as the native supported one.
 
  • Like
Reactions: deeveedee
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.