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.
How did you switch units from A to mA?

In my case, iStats seems to show mA when you hover over the graph (the menu bar icon always shows A). I was recently prompted to install an update, so maybe improvements were made.
 
FWIW - After getting Lilu+NVMeFix + SsdPmEnabler running, during those times of "0.00A", the iStats graphs show a very small mA draw on the 3.3V SSD line (less than <0.005A), instead of 0.00A.. this may be from an iStats update too.

View attachment 1707592
This seems more plausible to me than 0.00A necessarily being bogus (there may be cases where it is, my machine is but one data point). Mine shows 0.00A in times of extremely low (practically none, e.g. when all apps are closed) disk activity, but never shows this low under any disk activity more than a few tens of KB/s, and this behavior is the same whether I am on battery or mains for any length of time. I suspect it's more a data precision issue as your graph would appear to indicate. Unfortunately, even with the latest version of iStat Menus, my graph is stilll showing in A rather mA. No idea how to change that... so I have no way to confirm.
 
  • Like
Reactions: herb2k
The presentation in iStat Menus indeed seems changed a bit in latest version (?) but I have reservation on the conclusion of a precision issue.

I think the values on the dropdown menu are raw and instant values from SMC. Those values displayed on the graph are data points derived from some sort of averaging or interpolation algorithm. If so, extra precision is not meaningful. Hope someone with more insight in iStat Menus could comment.

_However_, if people follow my instructions in post #8111, and see very low or even 0.00A values when connected to _AC power_, then it's a very encouraging sign. There is some chemistry among the kexts + Big Sur that I haven't seen before.

Keep your observations coming, and post raw data i.e. screenshots instead of your interpretation (unless you really know what you're doing).
 
Last edited:
  • Like
Reactions: macpro_mid2014
The presentation in iStat Menus indeed seems changed a bit in latest version (?) but I have reservation on the conclusion of a precision issue.

I think the values on the dropdown menu are raw and instant values from SMC. Those values displayed on the graph are data points derived from some sort of averaging or interpolation algorithm. If so, extra precision is not meaningful. Hope someone with more insight in iStat Menus could comment.

_However_, if people follow my instructions in post #8111, and see very low or even 0.00A values when connected to _AC power_, then it's a very encouraging sign. There is some chemistry among the kexts + Big Sur that I haven't seen before.

Keep your observations coming, and post raw data i.e. graphs instead of your interpretation (unless you really know what you're doing).
Good point - the screenshot I posted earlier today was captured on AC Power.
 
Hi BoPI,
  1. Without ssdpmEnabler, does Samsung 970 EVO Plus boot correctly?
  2. With ssdpmEnabler installed, is the panic error from Samsung 970 EVO plus same as that from Corsair 510 last week?


ssdpmEnabler, and NvmeFix (+Lilu) perform different functions. Also see my response to you in post #8052 in case you missed.

If you want to measure idle current, pls follow instructions in post #8111.



Yeah, I saw & read your post back then. But...it is only as accurate as the program's author. I'm not saying it's incorrect or correct. I just think the same silver package coming in two versions E12 and E12s doesn't make sense with how the semiconductor industry works..
Hi kvic,

Without SsdPmEnabler the Samsung 970 Evo Plus boots correctly, I'm just not happy with idle (0,42A) and temperature. So that why I bought Corsair 510 and using Evo Plus as external drive.

With ssdpmEnabler installed and Samsung 970 EVO plus my Mac had exactly the same panic error as with Corsair 510 last week. And also I couldn't reboot even with disabling ssdpmEnabler via Terminal, I used to reboot from external drive and delete SsdPmEnabler from /Library/Extensions manually.

To be 100% sure I did try twice.
 
Good point - the screenshot I posted earlier today was captured on AC Power.
Yeah.. I could tell. I think the screenshot of one hour session in post #8115 from @oryan_dunn was on AC power too. I think he also had NVMeFix additionally installed during that experimental hour.

I would put my money on that no 0.00A at idle was observed in both cases during those two hours. lol

Hi kvic,

Without SsdPmEnabler the Samsung 970 Evo Plus boots correctly, I'm just not happy with idle (0,42A) and temperature. So that why I bought Corsair 510 and using Evo Plus as external drive.

With ssdpmEnabler installed and Samsung 970 EVO plus my Mac had exactly the same panic error as with Corsair 510 last week. And also I couldn't reboot even with disabling ssdpmEnabler via Terminal, I used to reboot from external drive and delete SsdPmEnabler from /Library/Extensions manually.

To be 100% sure I did try twice.
Hi BoPI, I've created a ticket to better track this issue.

Ideally we would prefer a stock AppleSSD to troubleshoot. Samsung sticks are properly the least candidates for troubleshooting an issues that's already quite a myth. But I could understand AppleSSD won't be readily available in your case. In the meantime, I think your best strategy is to wait for some members to step forward and report more data points on 2014 13-inch MBP in combination with different brands of SSDs.

So your Samsung 970 EVO Plus failed to boot into Recovery Mode after KP. Did you verify later if the disk has data corruption? If so, it's another indication, the SSD and/or this specific MBP model are incompatible.
 
Yeah.. I could tell. I think the screenshot of one hour session in post #8115 from @oryan_dunn was on AC power too. I think he also had NVMeFix additionally installed during that experimental hour.

I would put my money on that no 0.00A at idle was observed in both cases during those two hours. lol


Hi BoPI, I've created a ticket to better track this issue.

Ideally we would prefer a stock AppleSSD to troubleshoot. Samsung sticks are properly the least candidates for troubleshooting an issues that's already quite a myth. But I could understand AppleSSD won't be readily available in your case. In the meantime, I think your best strategy is to wait for some members to step forward and report more data points on 2014 13-inch MBP in combination with different brands of SSDs.

So your Samsung 970 EVO Plus failed to boot into Recovery Mode after KP. Did you verify later if the disk has data corruption? If so, it's another indication, the SSD and/or this specific MBP model are incompatible.
Kvic,

I will try to install your SsdPmEnabler with my original Apple SSD in and test.

No data corruption. But couldn't reboot back, even with disabling your kext via Terminal. Rebooted from external drive and manually deleted SsdPmEnabler.kext from ../Library/Extensions folder, what helped to reboot Mac normally.
Please check what fault report I get straight after panic error and reboot back

panic(cpu 0 caller 0xffffff8017183d06): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x1b VID=0xffff DID=0xffff
. FW Revision=2B2QEXM7\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.60.1/Common/IONVMeController.cpp:5472
Backtrace (CPU 0), Frame : Return Address
0xffffffb09b2ab960 : 0xffffff8014ab9aed
0xffffffb09b2ab9b0 : 0xffffff8014bfc6e3
0xffffffb09b2ab9f0 : 0xffffff8014becd1a
0xffffffb09b2aba40 : 0xffffff8014a5ea2f
0xffffffb09b2aba60 : 0xffffff8014ab938d
0xffffffb09b2abb80 : 0xffffff8014ab9678
0xffffffb09b2abbf0 : 0xffffff80152be3ca
0xffffffb09b2abc60 : 0xffffff8017183d06
0xffffffb09b2abc80 : 0xffffff8017168427
0xffffffb09b2abde0 : 0xffffff801521c795
0xffffffb09b2abe50 : 0xffffff801521c696
0xffffffb09b2abe80 : 0xffffff8014afe6b5
0xffffffb09b2abef0 : 0xffffff8014aff5c4
0xffffffb09b2abfa0 : 0xffffff8014a5e13e

Kernel Extensions in backtrace:

com.apple.iokit.IONVMeFamily(2.1)[008D1169-B6FD-39ED-9033-C67AC409031C]@0xffffff8017161000->0xffffff801718afff


dependency: com.apple.driver.AppleEFINVRAM(2.1)[E4DF1D8B-0DA9-33A8-A7B6-17DCA1678FC0]@0xffffff8015e59000->0xffffff8015e62fff


dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9BA70327-883F-3E4F-960A-14203BB191FD]@0xffffff8016000000->0xffffff8016014fff


dependency: com.apple.iokit.IOPCIFamily(2.9)[D0F1BFB8-C28E-3E70-891B-73B783189394]@0xffffff801742c000->0xffffff8017453fff


dependency: com.apple.iokit.IOReportFamily(47)[3A404946-7B6B-371A-A7B5-96E25F6F449D]@0xffffff8017462000->0xffffff8017464fff


dependency: com.apple.iokit.IOStorageFamily(2.1)[AA8F8B9D-BA6E-3EBB-8195-4792042ADF71]@0xffffff801754c000->0xffffff801755dfff


Process name corresponding to current thread: kernel_task

Mac OS version:

20C69

Kernel version:


Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11

KernelCache slide: 0x0000000014800000


KernelCache base: 0xffffff8014a00000


Kernel slide: 0x0000000014810000


Kernel text base: 0xffffff8014a10000


__HIB text base: 0xffffff8014900000


System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)


System shutdown begun: NO


Panic diags file available: YES (0x0)


Hibernation exit count: 0


System uptime in nanoseconds: 74761805518


Last Sleep: absolute base_tsc base_nano


Uptime : 0x000000116826b70b


Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000


Wake : 0x0000000000000000 0x0000000271be1bf1 0x0000000000000000


last started kext at 26532698902: >!AUpstreamUserClient 3.6.8 (addr 0xffffff7fb4f78000, size 12288)


loaded kexts:


com.ZLab.SsdPmEnabler 0.1.1


>!AUpstreamUserClient 3.6.8


>AudioAUUC 1.70


>!APlatformEnabler 2.7.0d0


>AGPM 119


>X86PlatformShim 1.0.0


@filesystems.autofs 3.0


@fileutil 20.036.15


>!AGraphicsDevicePolicy 6.2.2


@AGDCPluginDisplayMetrics 6.2.2


>pmtelemetry 1


>LuaHardwareAccess 1.0.16


|IOUserEthernet 1.0.1


>usb.!UUserHCI 1


|IO!BSerialManager 8.0.2f9


@Dont_Steal_Mac_OS_X 7.0.0


>!AHV 1


>!ADiskImages2 1


>!AHDAHardwareConfigDriver 283.15


>AGDCBacklightControl 6.2.2


>!ABacklight 180.3


>!AMCCSControl 1.14


>!A!IHD5000Graphics 16.0.1


>!A!ISlowAdaptiveClocking 4.0.0


>!AHDA 283.15


>eficheck 1


>ACPI_SMC_PlatformPlugin 1.0.0


>!A!IFramebufferAzul 16.0.1


>!AFIVRDriver 4.1.0


>!ASMCLMU 212


>!ACameraInterface 7.6.0


>!ALPC 3.1


>!AThunderboltIP 4.0.3


|IO!BUSBDFU 8.0.2f9


>!UTCKeyEventDriver 256


>!UTCButtons 256


>!UTCKeyboard 256


|SCSITaskUserClient 436.40.6


>!UCardReader 511.60.2


>!AFileSystemDriver 3.0.1


@filesystems.tmpfs 1


@filesystems.hfs.kext 556.60.1


@BootCache 40


@!AFSCompression.!AFSCompressionTypeZlib 1.0.0


@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1


@filesystems.apfs 1677.60.23


>AirPort.BrcmNIC 1400.1.1


@private.KextAudit 1.0


>!ASmartBatteryManager 161.0.0


>!ARTC 2.0


>!AACPIButtons 6.1


>!AHPET 1.8


>!ASMBIOS 2.1


>!AACPIEC 6.1


>!AAPIC 1.7


@!ASystemPolicy 2.0.0


@nke.applicationfirewall 310


|IOKitRegistryCompatibility 1


|EndpointSecurity 1


@kext.triggers 1.0


>!AGraphicsControl 6.2.2


|IOSerial!F 11


|IOAVB!F 900.12


>!ABacklightExpert 1.1.0


>!ASMBus!C 1.0.18d1


@!AGPUWrangler 6.2.2


|IOSlowAdaptiveClocking!F 1.0.0


>DspFuncLib 283.15


@kext.OSvKernDSPLib 529


|IONDRVSupport 585


>IOPlatformPluginLegacy 1.0.0


>X86PlatformPlugin 1.0.0


|IOAccelerator!F2 439.52


@!AGraphicsDeviceControl 6.2.2


@plugin.IOgPTPPlugin 900.11


|IOEthernetAVB!C 1.1.0


>!ASMBusPCI 1.0.14d1


>!AHDA!C 283.15


|IOHDA!F 283.15


|IOAudio!F 300.6.1


@vecLib.kext 1.2.0


|IOGraphics!F 585


>IOPlatformPlugin!F 6.0.0d8


>!AThunderboltEDMSink 5.0.3


>!AThunderboltDPOutAdapter 8.1.4


|Broadcom!BHost!CUSBTransport 8.0.2f9


|IO!BHost!CUSBTransport 8.0.2f9


|IO!BHost!CTransport 8.0.2f9


>usb.!UHub 1.2


>!UMultitouch 264


>usb.IOUSBHostHIDDevice 1.2


>usb.cdc 5.0.0


>usb.networking 5.0.0


>usb.!UHostCompositeDevice 1.2


>!AThunderboltDPInAdapter 8.1.4


>!AThunderboltDPAdapter!F 8.1.4


>!AThunderboltPCIDownAdapter 4.1.1


>!ABSDKextStarter 3


|IOSurface 289.3


@filesystems.hfs.encodings.kext 1


>!AXsanScheme 3


|IONVMe!F 2.1.0


>!AThunderboltNHI 7.2.8


|IOThunderbolt!F 9.3.2


|IO80211!F 1200.12.2b1


|IOSkywalk!F 1


>mDNSOffloadUserClient 1.0.1b8


>corecapture 1.0.4


>!A!ILpssGspi 3.0.60


>usb.!UHostPacketFilter 1.0


|IOUSB!F 900.4.2


>usb.!UXHCIPCI 1.2


>usb.!UXHCI 1.2


>!AEFINVRAM 2.1


>!AEFIRuntime 2.1


|IOSMBus!F 1.1


|IOHID!F 2.0.0


$!AImage4 3.0.0


|IOTimeSync!F 900.11


|IONetworking!F 3.4


>DiskImages 493.0.0


|IO!B!F 8.0.2f9


|IOReport!F 47


|IO!BPacketLogger 8.0.2f9


$quarantine 4


$sandbox 300.0


@kext.!AMatch 1.0.0d1


|CoreAnalytics!F 1


>!ASSE 1.0


>!AKeyStore 2


>!UTDM 511.60.2


|IOUSBMass!SDriver 184.40.6


|IOSCSIBlockCommandsDevice 436.40.6


|IO!S!F 2.1


|IOSCSIArchitectureModel!F 436.40.6


>!AMobileFileIntegrity 1.0.5


@kext.CoreTrust 1


>!AFDEKeyStore 28.30


>!AEffaceable!S 1.0


>!ACredentialManager 1.0


>KernelRelayHost 1


|IOUSBHost!F 1.2


>!UHostMergeProperties 1.2


>usb.!UCommon 1.0


>!ABusPower!C 1.0


>!ASEPManager 1.0.1


>IOSlaveProcessor 1


>!AACPIPlatform 6.1


>!ASMC 3.1.9


|IOPCI!F 2.9


|IOACPI!F 1.4


>watchdog 1


@kec.pthread 1


@kec.corecrypto 11.1


@kec.Libm 1
 
Last edited:
Yeah.. I could tell. I think the screenshot of one hour session in post #8115 from @oryan_dunn was on AC power too. I think he also had NVMeFix additionally installed during that experimental hour.

I would put my money on that no 0.00A at idle was observed in both cases during those two hours. lol
My screenshot was definitely on battery, and I've never installed nvmefix, only your SsdPmEnabler.

As for iStats, it seems the 0.00A readings are either bogus (and should be 0.01A or higher) or a result of precision issues (current is actually less than 0.01A), either in iStats or in hardware. I highly doubt the system is completely powering down the SSD while the system is running. Precision issues somewhere seem to be the most likely cause. Are there any other programs other than iStats to get this info? Any built in command line tools to directly query the power sensors?

Edit:
Here is a screenshot from this morning. I had ran it down to dead last night before plugging it in. This hour is on battery, with no kext loaded. For most of this hour, I was using RDP and had Safari open, but not really surfing the web with it. But as soon as I started really using Safari, it bumped up to that plateau you see. I saw this same behavior yesterday without SsdPmEnabler enabled. It would sit at 0.00A, I'd be getting great battery drain while using it (say 6% per hour or so). But once it gets in this state, battery drain increases, and I don't see it pop back to that 0.00A. level.

1609950930091.png
 
Last edited:
@oryan_dunn Looks something interesting. What's the lowest value in the above graph? Could you check multiple places along the flat line at the bottom, and perhaps do a screenshot with the tooltip pop-up?

EDIT:

Thanks for the updated screenshot below.

So looking at the graph above basically between ~10:37 and ~11:20, iStat Menu shows your SSD almost consumes no power. One thing you could check is counting the disk activities such as bytes written/read etc during such a period. If there is non-trivial amount, you perhaps will be convinced the power consumption can't be zero. You can also fire up BlackMagic (like I did months ago) and run for a few minutes and check the SSD 3.3V current readings during the benchmark.
 
Last edited:
@oryan_dunn Looks something interesting. What's the lowest value in the above graph? Could you check multiple places along the flat line at the bottom, and perhaps do a screenshot with the tooltip pop-up?
The flat line is 0A. And in the screenshot below, I've gone back to only using RDP, but the power never did go back to 0.00A like after I first booted the computer this morning. This is with no kext loaded.
1609953537932.png


Edit: perhaps it's related, I just realized by looking at the chart, the fan turned on around 11:20am, and hasn't turned off since, sitting around 1300rpm.
 
Last edited:
Good evening,

I own a Late 2013 MacBook Pro Retina.
Just to let you know, I finally made the switch from my 512Gb original Apple SSD to a 1Tb NVMe SSD.

I used the small Gigabase adapter with a Western Digital Black SN750. My operating system is MacOS Big Sur 11.1.

Everything works like a charm :)

I just have to install what's needed to lower the sleep power consumption and I'll be done.
 
I highly doubt the system is completely powering down the SSD while the system is running. Precision issues somewhere seem to be the most likely cause. Are there any other programs other than iStats to get this info? Any built in command line tools to directly query the power sensors?

SmartMonTools or other SMART tools should provide more exact reads from the actual device. I guess that’s is what istats is reading as well.
 
The flat line is 0A. And in the screenshot below, I've gone back to only using RDP, but the power never did go back to 0.00A like after I first booted the computer this morning. This is with no kext loaded.
View attachment 1707985

Edit: perhaps it's related, I just realized by looking at the chart, the fan turned on around 11:20am, and hasn't turned off since, sitting around 1300rpm.

I recall you had the same machine as me... That's the behavior I've noticed on my 2015 13" MBP - the SSD 3.3V line reads 0.0V from a cold start, until the fan turns on. Then it starts to fluctuate as one would expect.

I looked through a boardview schematic of the laptop - the 3.3V current sense circuit is shared with the fan control, which is why I suspect this happens on our model.
 
I recall you had the same machine as me... That's the behavior I've noticed on my 2015 13" MBP - the SSD 3.3V line reads 0.0V from a cold start, until the fan turns on. Then it starts to fluctuate as one would expect.

I looked through a boardview schematic of the laptop - the 3.3V current sense circuit is shared with the fan control, which is why I suspect this happens on our model.
My sisters laptop is an early 2015 13" MacBook Pro. I'll keep an eye on this behavior when I reinstall SsdPmEnabler. I don't recall seeing this same behavior when I had that installed before, but I hadn't paid close attention.

Here are a couple screenshots that show this, top SSD 3.3V, and bottom is the fan rpm:
1609969314575.png

1609969345504.png

The fan graph y axis is terrible, at 2:54:12, the fan kicked on, and remained on (the flat line before is 0rpm, the flat line after is 1290-1310rpm, despite it looking flat).

Edit: Right now, it was reading 0.00A and 0rpm on the fan, I kicked off a disk speed test, and was getting normal numbers, but it still showed 0.00A and 0rpm. About 10s into the test, the fan kicked on, and the SSD powered showed 1A or so.

Also, at some point, I'll pop the original SSD back in and watch the behavior under as close test conditions that I can. Before swapping it out, I briefly watched it, and I don't recall seeing any behavior like this.
 
Last edited:
  • Like
Reactions: herb2k
Thank you for the advice kvic! I just ordered some Kapton tape and will try it out when it comes in on Thursday. Do you have any advice on where to exactly put the kapton tape on the adapter?
You really should look into actual kernel panic logs inside Console.app before jumping to the conclusion that the installation of 3rd party SSDs is the culprit.

For area to apply Kapton tape, look at post #1 as a starting point. And exercise common sense from high school science class. Personally I don't think it hurts if you apply a bit more than you need.

Kvic,

I will try to install your SsdPmEnabler with my original Apple SSD in and test.

No data corruption. But couldn't reboot back, even with disabling your kext via Terminal. Rebooted from external drive and manually deleted SsdPmEnabler.kext from ../Library/Extensions folder, what helped to reboot Mac normally.
Please check what fault report I get straight after panic error and reboot back
The kernel panic is in the NVMe driver which isn't good news.

If you show AppleSSD is fine, then the machine (2014 13-inch) should be safe to assume okay. Next step will be borrowing a SSD listed in this table and see if it works or at the same time other models from 2013 to 2015 could report success (or failure) stories with these sticks:
  • Corsair MP510
  • Samsung 970 EVO Plus
  • Silicon Power A80
Looks like it'll take some time. To manage your expectation, there isn't much I could do in the kext at the moment.
 
  • Like
Reactions: BoPl
Device: Mid-2014 MacBook Pro 15" Retina (MacBookPro11,3)
OS: 10.13.6
Boot ROM Version: 429.0.0.0.0
SSD: Western Digital 1TB WD Blue SN550 WDS100T2B0C-00PXH0


I installed the Lilu+NVMeFix on High Sierra, after first installing and testing SsdPmEnabler. The power consumption seems unchanged as compared to using just SsdPmEnabler. At idle, the lowest that the power consumption will go to is 0.18A. I'm wondering if the Lilu+NVMeFix is not working as expected in High Sierra. Does anyone have a similar or different experience?

Also, the overnight power loss during sleep on a brand new battery is 5%, which no notifications to the stock sleep/hibernation settings.



Screen Shot 2021-01-07 at 9.33.03 AM.png
 
@manu3569 Thanks for posting your result.

What's your SN550's idle current without any kexts?

High Sierra might not have the best NVMe driver. If you're adventurous, try to port the driver from a newer macOS version. You may try your luck asking how-to in MacPro hackintosh threads.

I can't speak for High Sierra. I could share my brief experience with Nvme + Catalina + SN550 + 2015 13-inch MBP. So our SN550 idles at 0.26A without any kexts. With NvmeFix, we see 0.03A drop regardless of the existence of ssdpmEnabler.

Now the weird thing that I still don't understand is that this 0.03A drop is consistently observed right after every reboot. And then after some use (perhaps a few days with multiple sleep/wakeup but no reboot), this 0.03A drop will mysteriously disappear. Since it doesn't hurt, we still have NvmeFix installed. Perhaps that would make you less bother with it working or not.

With stock sleep/hibernation, 5% battery drain overnight is very good I would say.
 
With stock sleep/hibernation, 5% battery drain overnight is very good I would say.
That's something else I was testing. On my system, overnight (12hrs), battery dropped 20%.

I looked at what pmset showed, and it seems the default for Big Sur (and perhaps others, not sure), is 24hrs before hibernate kicks in when battery is above 50%, and 3hrs when battery is lower than 50%. Even then, the hibernate mode does not power down the RAM. Is this common for default settings on a MacBook? It just seems very strange it'd be 24hrs before hibernate kicked in. I know you can change it, just still quite odd for a default, as it would likely drain half the battery or more before actually going to hibernate.
 
Just adding another data point:

Mac Model: Late 2013, 15" MacBook Pro (MacBookPro11,3)
SSD: 2TB Sabrent Rocket Pro
Idle Current:
Default - 0.17A​
ssdpmEnabler - 0.05A​
ssdpmEnabler + Lilu/NVMeFix - 0.01A​
 
  • Like
Reactions: kvic
@kvic - Thanks for your response and insight about potential driver related current differences.

What's your SN550's idle current without any kexts?

With all 3 kexts removed, the lowest I see the current go is 0.31A.

Screen Shot 2021-01-07 at 4.22.23 PM.png


And when loading the SsdPmEnabler.kext again, the current drops back down to 0.18A.

Screen Shot 2021-01-07 at 4.24.39 PM.png





@dannytang - What macOS version are you running?

Mac Model: Late 2013, 15" MacBook Pro (MacBookPro11,3)
SSD: 2TB Sabrent Rocket Pro
Idle Current:
Default - 0.17AssdpmEnabler - 0.05AssdpmEnabler + Lilu/NVMeFix - 0.01A
 
  • Like
Reactions: kvic
That's something else I was testing. On my system, overnight (12hrs), battery dropped 20%.

I looked at what pmset showed, and it seems the default for Big Sur (and perhaps others, not sure), is 24hrs before hibernate kicks in when battery is above 50%, and 3hrs when battery is lower than 50%. Even then, the hibernate mode does not power down the RAM. Is this common for default settings on a MacBook? It just seems very strange it'd be 24hrs before hibernate kicked in. I know you can change it, just still quite odd for a default, as it would likely drain half the battery or more before actually going to hibernate.

Yes, perfectly normal. Sometimes turning off Bluetooth helps, as well as disconnecting any peripherals.

I set the standbydelay settings on my machine to 30 mins and 60 minutes to help prevent the overnight drain.
 
is there a guide to installing a new ssd with big sur? i see a lot of posts about bootrom and nvmefix and im not sure what it all means, sorry

I have a macbook air 2015, and am looking to upgrade the ssd to a 500gb kingston a2000. my bootrom version is 425.0.0.0.0, is that a good thing?
i know i have to backup my data through something that isnt time machine, but then how am i supposed to access the data after installing ssd?
 
Last edited:
@manu3569

thanks again for the follow-up. Those graphs are very pleasing to look at and IMO their jigsaw shapes are representative of normal systems.

@dannytang

thanks for posting your result. Concise yet detailed.

So you shucked a Sabrent Rocket Pro. What do you end up re-purposing the enclosure? I might be completely off track.

I've added both results to the table in the User Guide.

That's something else I was testing. On my system, overnight (12hrs), battery dropped 20%.

I looked at what pmset showed, and it seems the default for Big Sur (and perhaps others, not sure), is 24hrs before hibernate kicks in when battery is above 50%, and 3hrs when battery is lower than 50%. Even then, the hibernate mode does not power down the RAM. Is this common for default settings on a MacBook? It just seems very strange it'd be 24hrs before hibernate kicked in. I know you can change it, just still quite odd for a default, as it would likely drain half the battery or more before actually going to hibernate.

On our 2015 13-inch MBP + SN550 1TB, I measured 2% per hour battery drop during sleep under stock sleep/hibernation settings. You got 1.7% per hour. That's even better, and expected as herb2k said.

I believe Apple's choice of the defaults is to minimize wear & tear on NAND chips (less durable & expensive but replaceable in older systems) and again NAND chips (more durable & cheaper but soldered to logicboard in newer systems). In both cases, NAND chips lasting longer serve Apple's interest, and perhaps people who strongly believe in Apple's way.

Apple won't tolerate 2% per hour drain during sleep. I think their proprietary SSDs in these older machines are capable of power-off and this facilitates the whole system entering very low power consumption during sleep. I believe that's not the case when 3rd party SSDs are installed.

Battery drain during sleep is easiest to fix by entering hibernation earlier. Idle power consumption is harder to improve. Here comes ssdpmEnabler in an attempt to address this aspect, with further savings from NvmeFix/Lilu in some circumstances. OTOH, high power consumption during active/read/write has no way to workaround for end users.

Hopefully people know how to prioritise when picking a new SSD for these older machines.
 
  • Wow
  • Like
Reactions: porg and herb2k
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.