2013 Retina Macbook Pro, says 'Mac Model does not support standby'

[STCTbone]

I'm pretty sure my model of MBP can and does hibernate... any idea what might be causing this?

Could this have something to do with the fact that FileVault is currently encrypting my Mac's SSD?

[tomrittervg]

In a terminal, run sysctl hw.model - what is the output?

(The relevant code is

yontma-mac/You'll Never Take Me Alive!/LaptopSettingsController.m

Line 35 in 37e3814

+(Boolean) canStandby

and https://support.apple.com/en-us/HT202124 is the authority from Apple)

[STCTbone]

Thanks for the quick reply! Output is:

hw.model: MacBookPro10,1 which according to the source above should be ok right?

[tomrittervg]

No, I'm afraid that corresponds to MacBook Pro "Core i7" 2.7 15" Retina 2012 and the 15" Retina did not support hibernate until "Early 2013 and later".

[tomrittervg]

Oh wait. 10,1 corresponds to both BOTH MacBook Pro "Core i7" 2.7 15" Retina 2012 and MacBook Pro "Core i7" 2.4 15" Early 2013. Well that's not helpful. Hm... not sure what to do about this! I'll have to look into it, but it is definitely a bug...

[STCTbone]

Potential issue: for Major Version 10 macs, you're identifying eligible macs by majorVersion == 10 && isRetina. isRetina is set to [[NSScreen mainScreen] backingScaleFactor] == 2.0f; however I'm using a non-retina ultrawide as my main display right now, so isRetina == false for me. I'm not very familiar with Objective C, but perhaps set isRetina to true if the scaling factor of any connected display == 2.0f?

[tomrittervg]

Yes, that would also cause this issue (and is #14). If you're comfortable building from source, you can edit the function to always return true (although as I mentioned it's possible your Mac doesn't support hibernate if you aren't sure about the model.)

Otherwise I may be able to fix this in January, but I've since moved laptops and I'm not actually set up with an Apple Account here I don't think so this project might have turned abandonware...

[STCTbone]

Ahh missed #14 thanks. I'll try rebuilding it myself. Thanks again for the help, and putting the app together!