mac-pixel-clock-patch-V2
mac-pixel-clock-patch-V2 copied to clipboard
Update CoreDisplay-patcher.command
Proposal to add MacOS 10.14.4 support. It worked for me (MacBook Air 2015 i5 8Gb early 2015 with LG 25UM57 21:9 display, connected with Thunderbolt to HDMI cable). Just used the version 5 of the patch, no issue detected for now. Copy/Paste still works.
Patch v5 not working for MBP 13" 2018. Any ideas?
Not for now, I'll investigate. Do you run OSX 10.14.4? What kind of display enhancement do you expect from this patch? Can you post the terminal outputs you obtain when executing the patch?
Hi. Yes I run 10.14.4 and when try to patch I got this:
SIP looks to be disabled, all good!
(otool) Detected unpatched CoreDisplay on OS X 10.14.4 (18E227). SIP looks to be disabled, all good! Patching CoreDisplay with patch version 5 Re-signing /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: replacing existing signature update_dyld_shared_cache: warning: x86_64h skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-1.dat update_dyld_shared_cache: warning: x86_64h skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-2.dat update_dyld_shared_cache: warning: x86_64h skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-3.dat update_dyld_shared_cache: warning: i386 skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-1.dat update_dyld_shared_cache: warning: i386 skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-2.dat update_dyld_shared_cache: warning: i386 skipping because of bad install name /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/Resources/fcl-fc-3.dat update_dyld_shared_cache: i386 incorporating 629 OS dylibs, tracking 457 others, building closures for 247 executables update_dyld_shared_cache: warning: x86_64h rejected from cached dylibs: /System/Library/PrivateFrameworks/CreateML.framework/Versions/A/CreateML (("Could not find dependency '/System/Library/PrivateFrameworks/TuriCore.framework/Versions/A/TuriCore'")) update_dyld_shared_cache: warning: x86_64h rejected from cached dylibs: /usr/lib/swift/libswiftCreateML.dylib (("Could not find dependency '/System/Library/PrivateFrameworks/TuriCore.framework/Versions/A/TuriCore'")) update_dyld_shared_cache: x86_64h incorporating 1382 OS dylibs, tracking 1004 others, building closures for 2136 executables Closing...
On 13 May 2019, at 11:22, YJaff [email protected] wrote:
Not for now, I'll investigate. Do you run OSX 10.14.4? What kind of display enhancement do you expect from this patch? Can you post the terminal outputs you obtain when executing the patch?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Floris497/mac-pixel-clock-patch-V2/pull/304#issuecomment-491724195, or mute the thread https://github.com/notifications/unsubscribe-auth/ADDYEWD5FXTQXRWNDB4BL4DPVEQMPANCNFSM4HLRNRLA.
Yeah, not working for me either on 10.14.4. 2016 MacBook Pro and I used v5. I looks like it runs fine but then I'm still locked at 30Hz and the display is choppy.
Not working on 10.14.5. Patch says: SIP looks to be disabled, all good!
Unknown version of CoreDisplay found. ---- BEGINNING MD5 HASH SUMS ---- version: 10.14.5 build:18F132
otool CoreDisplay: 814fe7a8695f6583d821b5665f6df71a
otool CoreDisplay.bak: 714a9e14ccc64b0cf4bef2f083087d8e CoreDisplay: 9581c3d50658882e79325bcf5f510245 CoreDisplay.bak: d5a2f0272a1197325a65429f06136b04
---- ENDING MD5 HASH SUMS ------- Might reroll back to 10.14.2, depending on time.