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.
Screen Shot 2018-10-24 at 7.03.46 PM.png
 
  • Like
Reactions: TimothyR734
[doublepost=1540388901][/doublepost]
I'm not supporting 32 bit apps (for the moment) Apple is deprecating heavily. I may reconsider that if we have an overwhelming need to.

It is working on macmini3.1 and macbookpro6.2, however any 32bit apps won't open. Now I am forced to go back to the original, since I have a few apps that are 32bit. Maybe you should do also the 32bit part. At the end of the day Apple will remove 32bit after Mojave, but why on earth would we impose to ourselves even stricter policies. For the life of Mojave 32bit is supported! By aggressively deprecating machines Apple is trying to force us all into an endless spending loop. If we give up on 32bit now, at the beginning of Mojave, we are accepting this game and I guarantee you, it won't end up well for any of us.
Exactly the same dark mode transparency in the side bar is present also in Windows 10 v1809 32bit. I have it running on a MacMini1.1 from 2006 and it works better than on both machines from above in Mojave. All this graphics mumbo jumbo is Apple's excuse to rip-off anyone stupid enough to believe those excuses.
 
They are stripped of their 32 bit images. Only the 64 bit images were patched. That accounts for the smaller size. The 32 bit images are useless in my opinion. Do you see any need to patch both?
Yes; installing this will break all 32 bit apps that use these frameworks!
Even Parts of the OS are still 32 bit even in mojave!

@dosdude1 DO NOT integrate this until he fixes it
 
Confirmed here, I just replaced the CoreUI with the stock one on-the-fly, without log-out or reboot, and the app opened again, so @pkouame the full framework patch is needed, and with full framework of course I mean only the unix exec (32 and 64 bit). I believe full CoreUI is suffice, but for safety use also the full Hitoolbox and Appkit binaries to update your patch.
and @Sveto
No problem. Time is the limiting factor for all of us, so fat binaries (32+64) will be delivered in a subsequent version. Not sure when, but it will be on the release schedule. Send me a list of your favorite 32 bit (free) apps so we can add to our test suite.
 
It is working on macmini3.1 and macbookpro6.2, however any 32bit apps won't open. Now I am forced to go back to the original, since I have a few apps that are 32bit. Maybe you should do also the 32bit part. At the end of the day Apple will remove 32bit after Mojave, but why on earth would we impose to ourselves even stricter policies. For the life of Mojave 32bit is supported! By aggressively deprecating machines Apple is trying to force us all into an endless spending loop. If we give up on 32bit now, at the beginning of Mojave, we are accepting this game and I guarantee you, it won't end up well for any of us.
Exactly the same dark mode transparency in the side bar is present also in Windows 10 v1809 32bit. I have it running on a MacMini1.1 from 2006 and it works better than on both machines from above in Mojave. All this graphics mumbo jumbo is Apple's excuse to rip-off anyone stupid enough to believe those excuses.
No problem. If you have a github account, add an issue for 32 bit support and I will add it to to the v1.1 milestone release.
 
DaniloGeekDude said: [URL='https://forums.macrumors.com/goto/post?id=26694439#post-26694439' said:
↑[/URL]
Thank you for prompt response. My MBAir4,2 is on 10.14 (18A391) so I will apply it and will let you know how it goes. I'm sure it will go great. Thanks again for your work and efforts.

"pkouame, post: 26694467, member: 1036080"]I just updated the hardware list and some notes. I will setup the wiki next week and start an FAQ.

Thanks for testing on Air - PM me, if you would like to join the team to watch the sausage being made in the private repo...Or simply post Issues with your results in the public one - it helps. Thanks again.

Your hybrid patch (if that is the right reference) worked great on my MBAir4,2 !!!
Applied both CoreUIHybrid and HIToolboxMenuBar. Love the transparent Dock and NotificationCenter.

Thank You @pkouame !
 
OMG!! Thanks Bro!!

With this Mod, my iMac Late 2009 become perfect right now!! :D

I was applied Hybrid with HIToolbar and CoreUI only.

Thanks a lot!!!



[doublepost=1540397018][/doublepost]
I had used this app (iMac Late 2009), but seems can't transfer photo with iPhone (iOS 12.0.1)?
it had worked when I had a iPhone 4s but never really used airdrop but maybe there might be a fix that needs to be found
[doublepost=1540439540][/doublepost]
I've seen those who posted that they have gotten their iMac brightness working. This is literally the only single issue I encountered after installing Mojave, everything else is working awesome. I have a dual monitor setup and can't adjust the brightness on the iMac screen. Looks like the iMac brightness is about halfway at most. Hope someone can help me out to find a solution.
sometime reapplying the backlight patch from the patch updater works or you can download the brightness slider from the App Store its free
 
All - Mojave Hybrid Mode v1.0 is released (for Mojave GM)

The screenshots should be self explanatory, but this is a "fix" for our broken Mojave Light Mode. Search back for my original posts on this. You will find it here with notes and instructions. Read them carefully.

Lots of good people collaborated on this. So a special shout out to these collaborators :
@testheit @arqueox @TimothyR734 @ASentientBot @0403979 @webg3 and others...


View attachment 797799 View attachment 797800

Many more screenshots and details are available in the repo.

This is still an active project, so updates and support for upcoming Mojave updates will be coming soon. Open an Issue if you have a problem.

More documentation and a cleaner "scripted" installation will be available when time permits. Other ways of distributing are being explored.

NOTE: For the moment it is assumed that you know what you're doing and are fairly comfortable with the Terminal command line. If you are not, proceed with caution and ask for help: there are plenty of us who tested this to help.

Nothing here will brick your machine if you follow guidelines and make some quick backups (again - read instructions carefully) Ultimately, it always pays to know how to do things manually...

Do not use if you have upgraded to a beta - while it may be compatible it is highly unrecommended as each beta needs to be analyzed, patched and released. Going forward I plan on only supporting official Mojave updates, the in-between betas are too hard to track...


Enjoy (from the team)

Pardon my ignorance, but I just installed the hybrid patch on my MBP 5,5 after being confused due to the fact I was trying to patch the frameworks not in the current versions folder, but I eventually figured it out and I am currently running the "hybrid" mode. Anyways, it seems just the same as others have created in short scripts to turn on the reduce transparency for the menu bar but not the dock. Didn't the project start off as a half dark half light mode? I am probably very wrong about this, but I don't understand why editing the framework is necessary when you could just use something like @jackluke's script. Thank you so much for all the help you provide for this community, and I apologize in advance for demeaning your very hard work.
 
  • Like
Reactions: olad
Pardon my ignorance, but I just installed the hybrid patch on my MBP 5,5 after being confused due to the fact I was trying to patch the frameworks not in the current versions folder, but I eventually figured it out and I am currently running the "hybrid" mode. Anyways, it seems just the same as others have created in short scripts to turn on the reduce transparency for the menu bar but not the dock. Didn't the project start off as a half dark half light mode? I am probably very wrong about this, but I don't understand why editing the framework is necessary when you could just use something like @jackluke's script. Thank you so much for all the help you provide for this community, and I apologize in advance for demeaning your very hard work.
With the patch it brings transparency in other places that weren't there my menubar was semi transparent but now its solid which is fine with me but I love it it may not be pleasing to all but its much better than it was
 
Pardon my ignorance, but I just installed the hybrid patch on my MBP 5,5 after being confused due to the fact I was trying to patch the frameworks not in the current versions folder, but I eventually figured it out and I am currently running the "hybrid" mode. Anyways, it seems just the same as others have created in short scripts to turn on the reduce transparency for the menu bar but not the dock. Didn't the project start off as a half dark half light mode? I am probably very wrong about this, but I don't understand why editing the framework is necessary when you could just use something like @jackluke's script. Thank you so much for all the help you provide for this community, and I apologize in advance for demeaning your very hard work.
Please read the docs carefully and possibly study the screenshots in the github repo.

Hybrid effectively restores "vibrancy" to Light Mode as intended by Apple with a few shortcomings that are still in development (like the menubar and a few other UI elements) The "project" has gone much further than the original experiments a few months ago (which essentially explored replacing the "broken" light mode vibrancy with the dark version - which was never really optimal and fraught with even more confusing glitches). I don't know of any other "solution" here that has addressed this. Point one out for me.

Flat mode zaps transparency across the board while retaining Dock, Notification panel and other pleasant transparency features, so without the side effects of a hard core Preferences>Accessibility setting of reduce transparency (OFF system wide) and High Contrast. The latter is obviously a less invasive solution and scripted by many others here. The former is a patch and forget approach with some bonuses.

There are many approaches to all of this. You choose what suits you better.
 
Hi DaniloGeekDude,

You installed the Mojave 10.14.1 beta 5 on your MacBookPro,5,3 without a problem.

MY MACBOOK PROFILE:
macOS Mojave
Version 10.14 (18A391)
MacBook Pro (15-inch, Early 2011)
Processor 2.2 GHz Intel Core i7
Memory 16 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 512 MB


I'm having trouble installing any of the beta's on top of 10.14 (18A391) it does not finish the install.
The progress bar only shows only half way, and never moves after that. I only have the Public beta to install.

Do you have a procedure or steps I can follow for my situation with a Pubic beta install?

Thanks...

I apologize for not responding to this right away.

A couple of things.
  1. You probably need the developers seed to install or update to the 10.1.4.1 beta. Never tried Public, so that will be my guess. You can search this thread for the Developer's Access Utility to sign up your MBP5,3.
  2. Second, which have been verified in this thread, you have to have the SMC version 1.48fs. Some folks in here had problems upgrading due to SMC version. Mine worked since my MBP5,3 is on that version. See my post below.
macOS 10.14 Mojave on Unsupported Macs Thread

Good luck.
 
  • Like
Reactions: olad
It is working on macmini3.1 and macbookpro6.2, however any 32bit apps won't open. Now I am forced to go back to the original, since I have a few apps that are 32bit. Maybe you should do also the 32bit part. At the end of the day Apple will remove 32bit after Mojave, but why on earth would we impose to ourselves even stricter policies. For the life of Mojave 32bit is supported! By aggressively deprecating machines Apple is trying to force us all into an endless spending loop. If we give up on 32bit now, at the beginning of Mojave, we are accepting this game and I guarantee you, it won't end up well for any of us.
Exactly the same dark mode transparency in the side bar is present also in Windows 10 v1809 32bit. I have it running on a MacMini1.1 from 2006 and it works better than on both machines from above in Mojave. All this graphics mumbo jumbo is Apple's excuse to rip-off anyone stupid enough to believe those excuses.
I have a pre-release v1.1 with Universal "fat" binaries that work.
Tested locally against a few 32 bit apps with success.
If you can identify some of your choice 32 bit apps - we will add that to the test suite before release.
Again, I prefer to follow and track issues, bugs, enhancement requests in my public github repo. If you can.
 
I have a pre-release v1.1 with Universal "fat" binaries that work.
Tested locally against a few 32 bit apps with success.
If you can identify some of your choice 32 bit apps - we will add that to the test suite before release.
Again, I prefer to follow and track issues, bugs, enhancement requests in my public github repo. If you can.

If you use the "fat" frameworks binaries, then it will work for any 32 and 64 bit apps, there is no much to test, just patch double as you did for the previous "thin" frameworks.
[doublepost=1540453907][/doublepost]
and @Sveto
No problem. Time is the limiting factor for all of us, so fat binaries (32+64) will be delivered in a subsequent version. Not sure when, but it will be on the release schedule. Send me a list of your favorite 32 bit (free) apps so we can add to our test suite.
 
  • Like
Reactions: olad
If you use the "fat" frameworks binaries, then it will work for any 32 and 64 bit apps, there is no much to test, just patch double as you did for the previous "thin" frameworks.
[doublepost=1540453907][/doublepost]
I do.
Since some of these fixes patch DATA sections, the 32 bit and 64 bit patches are different (e.g. CoreUI) - the actual hex pattern is different. If it's a code section (e.g. AppKit) the addresses and offsets are different.
All patches are sourced from the original "fat" frameworks - divided - patched than lipo'ed back together and finally ad-hoc signed. Hence my desire to test exhaustively...Supporting fat binaries is double the work.
 
I do.
Since some of these fixes patch DATA sections, the 32 bit and 64 bit patches are different (e.g. CoreUI) - the actual hex pattern is different. If it's a code section (e.g. AppKit) the addresses and offsets are different.
All patches are sourced from the original "fat" frameworks - divided - patched than lipo'ed back together and finally ad-hoc signed. Hence my desire to test exhaustively...Supporting fat binaries is double the work.

I really don't check the "app bit platform" in general, I just use random 32 bit apps, so I'd say your previous "64 bit patch" for me covers more than 50% of the apps, I've tested only CoreUI, moreover I've verified that this framework binary is replaceable on-the-fly even through Finder, while I don't think the same goes for HIToolBox and Appkit, these last two are more important and tricky frameworks in MacOS, so agree with you, they need a bit more attention.
 
What KEXTS does the LegacyUSBInjector replace? I mean to ask, if I wanted to patch without it, what KEXTS would I need. I think @ASentientBot said something about IOUSB KEXTS but I'm not sure which ones.
 
@0403979 it's not that hard to find out:
- on "macOS Mojave Patcher" right click -> show package content -> Contents -> Resources
- on "macOS Post Install" right click -> show package content -> Contents -> Resources

inside that folder you find everything you need to know. all simple bash scripts :)

also for all the people who claim that they want to know what the patcher does, it's all there ;)
 
Last edited:
  • Like
Reactions: pkouame
@0403979 it's not that hard to find out:
- on "macOS Mojave Patcher" right click -> show package content -> Contents -> Resources
- on "macOS Post Install" right click -> show package content -> Contents -> Resources

inside that folder you find everything you need to know. all simple bash scripts :)
That doesn't tell me what the equivalent to the LegacyUSBInjector is. I know it was made to make patching easier but I want to patch without it. So I need to know what it's replacing.
 
the legacyUSB patch doesn't replace a system kext, I think somewhere in the thread it is explained (from parrotgeek) what the "LegacyUSBInjector.kext" does.

EDIT: the kext contains a single Info.plist
I mean that it does the job of replacing a few other KEXTS so either you can use it or replace those KEXTs. I want to know what those KEXTS are.
 
@dosdude1 is there anyway to repair trackpad problem for mojave on macbook 5,2 mid 2009 ? there is no any right click :(

Probably you already know, but there are two workarounds to perform a right-click:

1. holding "ctrl" key press trackpad main button
2. using a cheap usb pc mouse with two physical buttons

However I'd attempt something different from Terminal:

defaults write .GlobalPreferences com.apple.trackpad.enableSecondaryClick YES

then reboot.

Another attempt very similar, open Trackpad prefpane and on "secondary click" section set to "Click in bottom right corner", then from Terminal:

defaults -currentHost write -g com.apple.trackpad.enableSecondaryClick -bool YES

reboot and see if clicking bottom corner of the trackpad perform a right-click.
 
  • Like
Reactions: olad
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.