Please just do a clean install at this point, or restore a STOCK, UNMODIFIED copy of CoreBrightness.framework, then apply the patch from the Patch Updater tool.
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.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Search this thread for iSight and Camera potential fixes. In my case (mbp 5,3) I swapped in some key HS (10.13.6) IOUSB related kexts to get my iSight camera working in both FaceTime and PhotoBooth. Note that the apple developer forums are also reporting camera related issues with dB4 ( = pB3 )
[doublepost=1532930147][/doublepost]
Or early this week. Hopefully the 2018 macbook pro performance snafu hasn't completely derailed the schedule.
most likely Tuesday for those on the developers seed Wednesday or Thursday for public beta seed
I used @dosdude1's cbpatch app to enable NS on HS. I have a different model (MacBookAir4,2) so it might not work for you. At least you can give it a try (backup your existing CoreBrightness.framework files first.
See this post for steps/instructions.
https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-164#post-26299434
Good luck.
DVD drive not working had nothing to do with Mojave, Night Shift, or CoreBrightness, and everything to do with the receipt stuck inside it.
Technician fix thy self.
Yeah I did that just now and reboot, no Night Shift is showing in Display preferences.
Do you have patch updater installed? It will put in the Night Shift patch automatically.
That was my mistake reported by Olivia88, there are NO issues with NEW dosdude1 Night Shift cbpatcher, there is been a mismatching between the old and new file.
To ONLY THOSE who used the Corebrightness patch on page 87:
Apply this Night Shift Mojave beta 4 pre-patched FILE: Download
edit:
To clarify, I want to point out, (since I've tried) that even using or re-patching twice my old page 87 patched file, the maximum errors you will get are only those regarding Prefpanes, if you stuck on Apple logo progress bar, for sure there is an invalid/incompatible Night Shift X code-signing in the new patching scheme with your machine. Unluckily bordered only to your (not only yours) machine.
Last edited:
Tuesday is Apple's financial results day, so I think it will be either Monday or Thursday
CMD-Space then type "patch . . . " will bring you also to all apps/items/docs you´d like to fire up. ;-)
Spotlight´s your friend!
Installed in my Mac Pro 3.1. GTX 680 and modified wifi/bluettoth module.
Works Superb. Even geekbench is higher.
Again, THANK YOU so much, dosdude1, and to each and every one who made it possible.
Works Superb. Even geekbench is higher.
Again, THANK YOU so much, dosdude1, and to each and every one who made it possible.
On my strictly personal opinion, in your case doing a fresh install or an in-place upgrade it's almost the same thing, it will refresh anyway the entire core main system files, I guess your issue was related mainly to a corrupted permissions onto the "User Home Folder", often adding a new Administrator user from System Preferences's "Users & Groups" resolves 50% of the issues.
edit:
Anyway in an earlier picture (page 154) of your machine it seems there is some insulating tape near your iSight cam, are you sure the webcam is not faulted? Maybe a little hit/shock? Just an impression.
Rarely even some drops of water or coffee (ex. on the tape covering the webcam) can break an hardware, I know well, cause only with a few drops of rain fallen into my MacBook keyboard, I had to replace the entire keyboard since the previous one gave me continuous random auto-typing letters.
Last edited:
So, if stuck on the Apple logo and progress bar after the update, is there a procedure to fix?
In that specific case I was referring ONLY at the POST Night-Shift-patch, the general causes of stuck on Apple Logo progress bar could be many: SIGABRT, Invalid GPU Kext, Invalid/missing Framework/Extensions signatures, invalid prelinkedkernel, corrupted disk permissions and so on.
edit:
If you are referring after upgrading the main system, then booting from the USB Mojave Patcher, avoiding reinstalling use the "Post Install" select your machine model, then select "Force cache rebuild".
This should fix stucking on Apple logo progress bar too.
If you are referring to Night Shift, yes you can revert since the dosdude1 cbpatcher makes a backup of your current CoreBrightness.framework into /Users/YourUsername/CoreBrightness-backup/
if you read earlier posts you could revert through single user mode Terminal commands.
Last edited:
@dosdude1 Could you make a continuity patch to include with your patcher as you did with your night shift patch?
Just noticed that if you hold CMD+Space for more than half a second it opens Siri.
Well there’s always something to discover even if someone has already discovered it.
I think we got 9 developer previews with HS. Even though they started the public beta early this year, I think we have at least 4 more to go before the GM cycle starts to ramp up. There's still a lot of bug chatter on the dev forums - the push to "metal-ize" all third party apps + accelerating the phase-out of 32 bit apps suggests they should take all the time that's necessary to regression test. No need to rush this at all. There's been enough bad press lately...
As far as I'm concerned they can release even 15 DP, I only hope that until (and after) the GM, they will stay in the dark about the OpenGL, telemetry plugin and legacy IOUSB.
Last edited:
Just curious - do a lot of you use Siri on your macs? I'm thinking of disabling it.
No, but I like the icon in the Finder bar, it's the only colored thing I have up there. Apart the fast user switching picture icon. Anyway I don't think Siri enabled takes so much RAM.
Last edited:
Ok. I'm just paranoid about anything that can potentially gather even more info than they already have
. Plus I think Siri is only really designed for modern "supported" macs. Moving "Hey Siri" to the T2 chip is a strong indication of that.What do you mean about staying in the "dark" about OpenGL?
No and will probably not any time soon. I'm scared of that lady..