I installed the patched CoreBrightness on my MBP 8,2 external drive and I haven't any issue with Safari, while the NightShift works OK.Installing the 19H2 patched CoreBrightness.framework breaks Safari on my iMac. While the NightShift is working nicely with the Framework installed I cannot use the Safari to browse any longerThis is a really nice one.
Waiting for installer with everybody))) And downloading update on Mac mini 2012 via spoofing Mac model - 11,15 GbNice...🤔...but most people here don't have a dev account so your link won't work for them, we need a download link for all...
Sucatalog shows no new beta (just) yet, last time it was posted a day later.
So the catalog still does not show the new Install Assistant.pkgWaiting for installer with everybody)))
Here's the page, search for InstallAssistant.pkgSo the catalog still does not show the new Install Assistant.pkg
Not in the coming days, more like 2 weeks to go if not a bit more.In a way, this is a strong indication that the work on version 11.0 has already been completed and that we should see the long-awaited launch of Big Sur happening in the coming days.
Whoever is in the beta program, it is good to leave, as the Big Sur 11.0 installer will not appear if you continue in the beta, you will go to the 11.0.1 beta.
disagree with you, I believe we will see him later this week. There's no reason to launch an 11.0.1 beta if you don't release 11.0 GMNot in the coming days, more like 2 weeks to go if not a bit more.
You can disagree with me all you want, thing is, 11.0 will be for the to be released new macs with likely references to unreleased macs, now...Apple don't want people to know that just yet.disagree with you, I believe we will see him later this week. There's no reason to launch an 11.0.1 if you don't release 11.0
You can disagree with me all you want, thing is, 11.0 will be for the to be released new macs with likely references to unreleased macs, now...Apple don't want people to know that just yet.
Apple also always releases GM candidates first at least a week before, we haven't seen a GM just yet.
There's also the letter g in the last beta, should be a or something to be close to release.
And, there will be an event, there hasn't been a date released yet by Apple just yet, some say it will be the 17th. of November.
I will eat my shoes if Apple releases macOS 11 this week.
Just a few more weeks, they'll be behind you before you know it.You're right, but she did this quite recently with iOS, first releasing the 14.1 and 14.2 beta.
We will not lose faith.
It got lost on release dates, including betas versions this year.
We have already launched every day of the week. There is no longer a pattern.
This could be related to an AppleSilicon release most likely in production with an internal GM of macOS labelled 11.0.disagree with you, I believe we will see him later this week. There's no reason to launch an 11.0.1 beta if you don't release 11.0 GM
Yes, thank you - now I see that when opening a file, the disassembler offers the option AArch64 instead of intel. I‘ll look closer but need to understand the ARM RISC instructions better first.I made some searching and noticed that Disassembler can understand till ARMv7 and ARM64 (that is ARMv8) while any recent iOS hardware device and Apple Silicon Mac should use ARMv8.4-A .
So with BigSur seems apple (after Catalina) double sized almost all of their system core binaries exec to include both AArch64 and x86_64 coding, I guess more than rewrite many core binaries, they simply used those from their iOS that were already ARM64 , just to say, even the System Update packing is similar to iOS .Yes, thank you - now I see that when opening a file, the disassembler offers the option AArch64 instead of intel. I‘ll look closer but need to understand the ARM RISC instructions better first.
Wasn‘t there mention earlier in this thread that some functionality dropped from BS in intel implementation, does exist for ARM?
The move from Mojave to drop X86 unity binaries was precisely for this reason.So with BigSur seems apple (after Catalina) double sized almost all of their system core binaries exec to include both AArch64 and x86_64 coding, I guess more than rewrite many core binaries, they simply used those from their iOS that were already ARM64 , just to say, even the System Update packing is similar to iOS .