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).Nightlies are for people who are able to find how to install them...
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).Nightlies are for people who are able to find how to install them...
@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.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.
Well done. There are a number of things that have been improved, as always with point releases to a major release.@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).
You like to have the final word …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).
NVRAM reset. 🧐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.
Ah. Hadn't done that in a while. Will give it another go w/NVRAM reset when 1.1 is ready.NVRAM reset. 🧐
Not strange. Resetting NVRAM is not unusual with Open Core when changing versions of macOS. Welcome to the world of hackintosh.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?
Hello,@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
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, JimHi 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.
MBP5,2: it is able to install 14.1 betas now (verified that b2 USB installer boots well, but didn't try to install).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.
Check the nightly site again, latest version dated 9:11 am Oct. 16. New support packages etc.T1 support now fully working with tonight's OCLP 1.1.0n on my MacBook Pro 13,2 running Sonoma 14.1 beta 3.
View attachment 2296246View attachment 2296247
What about FaceTime, any issues there? Is there anything not functioning as intended on your machine?T1 support now fully working with tonight's OCLP 1.1.0n on my MacBook Pro 13,2 running Sonoma 14.1 beta 3.
View attachment 2296246View attachment 2296247
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.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
What about FaceTime, any issues there? Is there anything not functioning as intended on your machine?
About This HackHello,
How did you manage to display this ?
Thanks
#2363 has worked for me so far. Have not done #2364, but might be worth trying.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
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.)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
Thanks, waiting for an update from you!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.)