Jump to content

Trying to enable Night Shift on unsupported macs


nandor690
 Share

27 posts in this topic

Recommended Posts

I know for the older Mac pros you can. But I don't know if that's what I need. I was hoping maybe a kext and some plist editing would get it.

To monitor CPU frequency, for example, I use fakesmc and the fakesmc senor kext in my real iMac. Cause there is no other way iv found to monitor that and a few other things.

Plus, I had to modify the macOS install image to get around platform support and a few other things so there has to be some kind of way.

It's funny how my real iMac has almost turned into a hackintosh lol

 

Sent from my iPhone 7 Plus 256GB

Link to comment
Share on other sites

May try to boot your old Mac with Clover? And try to simulate a supported SMBios natively then check whether Night Shift is working for you.

BTW it's time for the good old Macs to retire LOL

I almost did until I read about why macOS wasent supported. I upgraded the CPU to a X7900 extreme 4 years ago and that worked great until OS X Yosemite. Then it didn't support Sierra because X7900 doesn't support sse4.1 instructions. So I upgraded it again to a T9300 and a 802.11ac/BT 4.0 combo card and it actually runs macOS 10.12.4 really good. It's by no means a work horse but it does work great for doing lighter stuff while I do my main work on the hackintosh

Link to comment
Share on other sites

May try to boot your old Mac with Clover? And try to simulate a supported SMBios natively then check whether Night Shift is working for you.

BTW it's time for the good old Macs to retire LOL

So using Clover did work. Its installed on my hard drive on the 2007 iMac. which now thinks that it is a late 2012 iMac. That is the first year that supports Metal, which apparently is what macOS wants to see for night shift to work. 

There are a few draw backs. 

2 out of the 3 USB ports don't work. if I plug in Mighty Mouse it lights up but doesn't work

I'm using the BCM943602CS combo card, it sees the 802.11ac but does NOT see bluetooth

​The isight camera doesn't work 

 

Any suggestions?

  • Like 1
Link to comment
Share on other sites

So using Clover did work. Its installed on my hard drive on the 2007 iMac. which now thinks that it is a late 2012 iMac. That is the first year that supports Metal, which apparently is what macOS wants to see for night shift to work. 

There are a few draw backs. 

2 out of the 3 USB ports don't work. if I plug in Mighty Mouse it lights up but doesn't work

I'm using the BCM943602CS combo card, it sees the 802.11ac but does NOT see bluetooth

​The isight camera doesn't work 

 

Any suggestions?

This could be related to USB. Try to increase the limitations. Google may help.

Bluetooth issues could be relevant to firmware, take a look at https://github.com/RehabMan/OS-X-BrcmPatchRAM

Link to comment
Share on other sites

Very nice!!! That is some great info right there. It would be a whole lot better to be able to modify the frameworks instead of having to use clover and the modified ssdt I had to make for the usb, bluetooth and camera. If this works, I won't need any of that and will be able to boot my iMac regularly 

  • Like 1
Link to comment
Share on other sites

Maybe we could use a Clover patch to fix the absence of Night Shift on unsupported Hackintosh

I am using MacbookPro 8,1 SMBIOS and I think there should be a way to transform that framework patch into a clover hot patch no?

Link to comment
Share on other sites

Maybe we could use a Clover patch to fix the absence of Night Shift on unsupported Hackintosh

I am using MacbookPro 8,1 SMBIOS and I think there should be a way to transform that framework patch into a clover hot patch no?

That's exactly what you do. I'm using a clover and smbios on my 2007 iMac to make it think it's a late 2013 iMac. And night shift works.

Just look for the MacBooks that support metal and use that year

Link to comment
Share on other sites

That's exactly what you do. I'm using a clover and smbios on my 2007 iMac to make it think it's a late 2013 iMac. And night shift works.

Just look for the MacBooks that support metal and use that year

Well you can do that if you dont care about power management.. remember you need a proper SMBIOS adequate to your CPU... i wonder if there is a clover kext patch to fix this on unsupported SMBIOS ...
Link to comment
Share on other sites

Well you can do that if you dont care about power management.. remember you need a proper SMBIOS adequate to your CPU... i wonder if there is a clover kext patch to fix this on unsupported SMBIOS ...

For sure, I see what you are saying but running the same exact test on 7,1 (native) and then using a 13,1 smbios has no change on each test. Well within margin of error. So I don't think it effects it that much as far as power management. 

 

Could try spoofing the Graphics card to think it is a card that supports Metal. 

or if someone could figure this out Supported Mac models for Night Shift in Sierra 10.12.4 Iv tried but each time, Display Preference crash every time I click on it in System Preferences. so I just use smbios for now

Link to comment
Share on other sites

Fantomas recently advised me that f.lux app does the same as Night Shift and can be run on all systems. Most likely to be easier and less risky than messing around with SMBIOS on a real Mac...

 

I've tried to enable Night Shift on my C2D which normally runs with MBP7,1 SMBIOS and the feature was only available with Ivy Bridge profiles or later.

iv known about that. I want night shift tho

Link to comment
Share on other sites

Nope. It could be impossible to implement patching framework by Clover. Just one reason - we don't know when the target framework has been loaded.

Patching kernelcache is very different. Because the RAM for kernelcache must be released by boot.efi and at that time Clover will patch the RAM for kernelcache.

Actually Clover will do nothing (have no ability to do) when boot.efi loads, or we can say after that.

Anyway. Clover can't patch framework, at least right now.

Maybe you should rethink your continued onslaught to 'appear' knowledgable, rather than continue to spew utter tosh like "that RAM needs to be released by boot.efi before a boot loader can patch it...... "

 

Too many people thinking and not doing has become the 'norm'

  • Like 2
Link to comment
Share on other sites

Maybe you should rethink your continued onslaught to 'appear' knowledgable, rather than continue to spew utter tosh like "that RAM needs to be released by boot.efi before a boot loader can patch it...... "

 

Too many people thinking and not doing has become the 'norm'

I have been messing with hackintoshes since 2010 and in those 7 years I have found that there is a way to do anything, or make anything work. 

Link to comment
Share on other sites

we don't know when the target framework has been loaded.

True, they are loaded after kernel entry (kexts are always loaded to RAM pre-entry). There might be a way to patch the kernel code that loads the frameworks with an interception call (save context, do stuff, restore context and return) and grab the required addresses from stack/register (whereever they are saved), though I'm not sure how one would approach that.

 

Patching kernelcache is very different. Because the RAM for kernelcache must be released by boot.efi and at that time Clover will patch the RAM for kernelcache.

No clue what you are trying to say... UEFI offers no kind of memory protection (segmentation is off, paging is optional, but virtual mode will only be invoked after the booter exits BootServices, though still it's the XNU kernel that virtualizes later, because booter-side it makes little sense). You can access all memory at all times (might be MM memory is protected, though I guess that is platform-specific - it is not 'indexed' at least).

 

Actually Clover will do nothing (have no ability to do) when boot.efi loads, or we can say after that.

Check AptioFix, Clover (well, AptioFix in that case) does stuff even on kernel entry, throughout boot.efi execution

 

Too many people thinking and not doing has become the 'norm'

Seriously...

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...