Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe

[The_Moves]

Benefit to 4k?

Will I guess i'll find out. Just booted off Xubuntu live and use nvme-cli to change the desired format to 4k. Reinstalling Mojave now. Also this time, i'm going to do HFS+ encrypted versus APFS encrypted as evidently HFS+ has better performance. Only nice thing about APFS is the Copy on Write which would help with space utilization.

EDIT: Just realized my Mojave install reverted to APFS even though I formatted as HFS+... Maybe i'll be doing High Sierra after-all...

 

[jackqueenking]

Thanks for all the valuable information in this thread, it helped me a lot!

I've upgraded my MacBook Pro (Retina, 15-inch, Mid 2014) with a 1TB HP EX920, using the Sintech adapter. After disabling standby everything works fine.

Disk speed (Blackmagic tool):
1200 MB/s read, 1450 MB/s write

Power consumption with Mail,Safari,Terminal,PHPStorm started, but idle. Medium display brightness, no background jobs (spotlight indexing...) running:
Apple 512GB: 80% after 2:30
HP 1TB EX920: 65% after 2:30

Power consumption when sleeping, after 1/2/3 days:
Apple 512GB: 98% / 96% / 94%
HP 1TB EX920: 94% / 85% / 77%
(checked once per day)

Nice results. I am experience similar things on the 13 inch 2014 model. I am getting a total of about 5-5.5 hours of usage with brightness set to 50%. I have not tested the sleeping power consumption.

How many charge cycles does your battery have? It seems like our OEM drives are extremely low powered in comparison to any NVME drive tested here, even the sabrent... still lasts longer than a windows machine though lol

 

[MacXperte]

Hi @macgeek01 I was a little too fast to claim success. I started eventually getting the random reboots and double-startups. I put back the original Apple SSD and installed OS X 10.14.4. Now I have MacBookPro11,1 151.0.0.0.0 which is latest rom. In fact I have more problems now than ever before!

Here is my pmset now:

System-wide power settings:
Currently in use:
 standbydelaylow      10800
 standby              0
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             1
 gpuswitch            2
 networkoversleep     0
 disksleep            10
 standbydelayhigh     86400
 sleep                1 (sleep prevented by coreaudiod)
 autopoweroffdelay    28800
 hibernatemode        25
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 highstandbythreshold 50
 acwake               0
 lidwake              1

I tried to fix restart issues with this command

sudo nvram enable-legacy-orom-behavior=1

That did not help at all. What do I do now? All sleep and hibernation issues are worse than ever. Do I have to flash the MBP to MacBookPro12,1 182.0.0.0.0 ??

### UPDATE ##
I reversed the nvram command with
sudo nvram enable-legacy-orom-behavior=1
Still it was crashing and restart every time on sleep. So I set back pmset to defaults. (also hibernatemode =3) At least I have no more restart after sleep. Still wondering what is correct values.

With the settings you posted above, your issues were to be expected. hibernate mode 25 means hibernating on every sleep. But with your MacBook Pro 13" (Mid 2014), an NVMe drive and unpatched firmware, restoring a session from an hibernate file is not supported, so on every sleep it had to reboot.

To completely avoid hibernating, three values have to be set to 0 like this:

sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0

There are still discussions about it, and even Page 1 had a wrong command until now. For final clarification let me cite from the pmset man page:

SAFE SLEEP ARGUMENTS

hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets written is also dependent on the values of standby and autopoweroff

For example, on desktops that support standby a hibernation image will be written after the specified standbydelay time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.​

I'll put the correct code on Page 1 right now.

 

[Italia321]

I have Macbook Pro late 2014 with Adata 8200Pro with bootrom 151.0.0.0.0
My setting is and I have no problemi with that.
sudo pmset -a standby 0 is enough for me
The power consumption after sleeping 10 hour is 9%

 

[MacXperte]

I read a report on another thread of a 2015 iMac with 3rd party NVME SSD that received the firmware update.

Maybe 2015 and newer models will get the updates. Not sure if this was true for the firmware update released before the most current one?

That's an interesting thought!

Maybe the reason firmware updates don't work from NVMe drives is the same why waking from hibernation doesn't either? (The drive not being available in a certain power state.)
Leads to some follow-up questions. Maybe some of you could try:

• Someone with older firmware: can you successfully update firmware when booted from an external (USB) drive? Without having to switch the NVMe drive back to a stock drive, is what I mean.
  (I know for sure that the update will be proposed again if the firmware is less than current, even if the system on the external drive itself is up-to-date.)
• Someone with a patched EFI (allowing hibernation with 2013/2014 MacBook): does firmware update work normally?
  (Don't know if someone wants to try that, because if it works the patch might be gone …)

Unfortunately all firmwares are up-to-date here, so I can't test myself …

 

[jackqueenking]

With the settings you posted above, your issues were to be expected. hibernate mode 25 means hibernating on every sleep. But with your MacBook Pro 13" (Mid 2014), an NVMe drive and unpatched firmware, restoring a session from an hibernate file is not supported, so on every sleep it had to reboot.

To completely avoid hibernating, three values have to be set to 0 like this:

sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0

There are still discussions about it, and even Page 1 had a wrong command until now. For final clarification let me cite from the pmset man page:

SAFE SLEEP ARGUMENTS

hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets written is also dependent on the values of standby and autopoweroff

For example, on desktops that support standby a hibernation image will be written after the specified standbydelay time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.​

I'll put the correct code on Page 1 right now.

His value for standby was also set to 0, that means on every sleep he would go directly into hibernate mode 25. If the value was set to 1 he would have to wait standbydelayhigh or standbydelaylow minutes during regular sleep before going into hibernate mode 25. Unless that's not how standby works? I had the same issue of restarting during sleep because I was testing the 151 bootrom but then I reset to default values and it worked.

 

[MacXperte]

I have Macbook Pro late 2014 with Adata 8200Pro with bootrom 151.0.0.0.0
My setting is and I have no problemi with that.
sudo pmset -a standby 0 is enough for me
The power consumption after sleeping 10 hour is 9%

With these settings everything will be fine - until:

• Your MacBook sleeps more than 8 hours on ac power. After 8 hours (autopoweroffdelay=28800 seconds) autopoweroff=1 will hibernate your MacBook and you will have to reboot. autopoweroff 0 will prevent that.
• Or your MacBook loses all power while sleeping (ac or battery) e.g. for the battery being completely drained, or an SMC reset. On next power-up your MacBook will try to use the hibernatefile that was created for such emergencies because of hibernatemode=3, but can't, and will have to reboot.

In the latter case it doesn't make a lot of difference, but still: hibernatemode 0 will make for a somewhat more elegant recovery (probably without the "double reboot" some are reporting), and it will save the time and resources to create a useless hibernatefile every time your MacBook goes to sleep.

 

[jackqueenking]

The biggest mistake people are making in this thread is assuming standby=0 disables hibernation that's why they have been reporting that its working fine with mode 3.

 

[MacXperte]

I successfully used a Transcend PCIe SSD 220S 1TB (TS1TMTE220S) with Sintech Adapter in a MacBook Pro Retina 13" (Mid 2014, MacBookPro11,1).

I updated the firmware before I started, booting from an external SSD with a plain High Sierra system on it. Although Security Update 2019-002 was installed on that external SSD before, App Store proposed it again (presumably because of the firmware not being up-to-date).

I bought both the long and the short black Sintech adapters and tried them both. Both came with black tape already protecting the backside of the connector and just worked, but I noticed some minor differences:

• The long version has a connector, that will allow you to easily insert the m.2 SSD in a 45° angle, producing more pressure on the pins when you bring it down and fix it in the final position. (Post #3950 has a nice picture of that.)
  The short version has a slide-in connector, similar to the one on the motherboard.
• Because of the different type of connector, the short version is also slightly thinner. In the A1502 housing that made the difference between the bottom case closing easily or not.

The performance (4x PCIe lanes with both adapters) was quite good for a Mid 2014 MacBook. Blackmagic reported 1360/1520 MB/s, and ADM 59 MB/s random 4k read!


The Transcend 220S SSDs have a nominal speed of 3500/2800 MB/s, DRAM and SLC cache, and TLCs. At currently 150€ / 180$ it's a good deal I think. Would be curious to see some tests by @gilles_polysoft and inclusion in the table. If there are more positive reports, we might add it to the whitelist of compatible SSDs.

 

[gilles_polysoft]

The Transcend 220S SSDs have a nominal speed of 3500/2800 MB/s, DRAM and SLC cache, and TLCs. At currently 150€ / 180$ it's a good deal I think. Would be curious to see some tests by @gilles_polysoft and inclusion in the table. If there are more positive reports, we might add it to the whitelist of compatible SSDs.

Hi,
Thanks for the suggestion, yes the Transcend 220s has a good perf/price ratio. I'll test one soon and will include it in the tables.
I already have a transcend 110s to test, and will get and also add the 220s.

 

[djangoreinhardt442]

After viewing this forum and performing the upgrade I thought I would share my experience.

Macbook air 6,1

Bootrom 110.0.0

High sierra

Sintech long adapter https://smile.amazon.co.uk/gp/product/B01CWWAENG/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

Crucial CT500P1SSD8 P1 500 GB https://smile.amazon.co.uk/gp/product/B07J2WBKXF/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1

Having seen the use of kapton tape on previous posts I thought it was worth showing that this adapter comes with the pins already taped over.

All seems to work as expected for Mac OS with the same hibernation caveats as described by others.

The issue that seems different to any other previous post is with installing Windows via Boot Camp.

The process works fine up to booting from the install disk and selecting the drive for install but after this the screen goes blank.

This happens for all versions of Windows I have attempted 7,8 and 10.

On the stock drive with the same boot ROM and OS version process works fine and I also tried Winclone to restore the Windows partition to the new drive but when I boot into Windows the same blank screen occurs.
View attachment 831688 View attachment 831689

IF your SSD is formatted as APFS (and NOT as NTFS or HFS+, you won't be able to make Windows work.
If you search the interwebz, there is a workaround described somewhere, but I do believe it is a bit complicated. You should be able to google it (or, I am sure someone on this thread has already mentioned the workaround - if at all possible - last time I read something on the subject, there were lots of problems).

 

[tsugaru]

IF your SSD is formatted as APFS (and NOT as NTFS or HFS+, you won't be able to make Windows work.
If you search the interwebz, there is a workaround described somewhere, but I do believe it is a bit complicated. You should be able to google it (or, I am sure someone on this thread has already mentioned the workaround - if at all possible - last time I read something on the subject, there were lots of problems).

You can get it working, but you won't be able to do it properly with the Apple polish per se.
The actual control panel doesn't work in Windows, and for me the Boot Camp assistant did nothing for me.
How I got it working on my system (rMBP 2015 13")

Open Boot Camp Assistant. Download the Windows Support software. Once downloaded, stick it on a USB drive or some other accessible storage medium.
Open Disk Utility. Create a new partition for Windows on your SSD. In my case, I shrunk my APFS from 500 to 300, and gave the rest to Windows. Format the Windows partition to FAT32 and name it something easy, like BOOTCAMP or whatever.
Create a Windows USB installer as you would, using Rufus or Microsoft's own utility. I'm sure you could use Netbootin or whatever other method. Whatever works for you.
Once that's done, reboot your Mac, and hold down Option. Select EFI boot or whatever corresponds to your created Windows USB installer.
Install Windows. You'll have to select your BOOTCAMP or named FAT32 partition and click format, as Win10 requires NTFS as a filesystem.
Once Windows is installed, connect your USB disk with the Windows Support software. Run the setup.exe in there and install your drivers and such. Once done, run Apple Software Update, as there's a couple of essential driver updates (WiFi.)
Reboot again. Run Windows update and such.

Windows as a whole should be working fine. However, you probably want to use the Boot Camp control panel for some stuff. You won't be able to select your startup disk from it, but you'll be able to change some trackpad behaviours (tap to click is a big one.)

Open command prompt as administrator. So click start, type in command or cmd, and when command prompt comes up, right click on it and select Run as administrator.
In the window, type the following:

runas /trustlevel:0x20000 AppleControlPanel.exe

Set your options, and then hope Apple actually updates Boot Camp again sometime to properly work.

To switch between macOS and Windows, you'll have to use the Option key at startup, or set it in System Preferences on your Mac.

Hope that helps.

 

[djangoreinhardt442]

No, that's not how "standby" works. According to the pmset man page standby 1 has no effect on what happens when the Mac goes to sleep, but only on what happens after sleeping on battery for the stanbydelay(s) duration.
[doublepost=1555098231][/doublepost]I successfully used a Transcend PCIe SSD 220S 1TB (TS1TMTE220S) with Sintech Adapter in a MacBook Pro Retina 13" (Mid 2014, MacBookPro11,1).

I updated the firmware before I started, booting from an external SSD with a plain High Sierra system on it. Although Security Update 2019-002 was installed on that external SSD before, App Store proposed it again (presumably because of the firmware not being up-to-date).

I bought both the long and the short black Sintech adapters and tried them both. Both came with black tape already protecting the backside of the connector and just worked, but I noticed some minor differences:

• The long version has a connector, that will allow you to easily insert the m.2 SSD in a 45° angle, producing more pressure on the pins when you bring it down and fix it in the final position. (Post #3950 has a nice picture of that.)
  The short version has a slide-in connector, similar to the one on the motherboard.
• Because of the different type of connector, the short version is also slightly thinner. In the A1502 housing that made the difference between the bottom case closing easily or not.

The performance (4x PCIe lanes with both adapters) was quite good for a Mid 2014 MacBook. Blackmagic reported 1360/1520 MB/s, and ADM 59 MB/s random 4k read!
View attachment 831826

The Transcend 220S SSDs have a nominal speed of 3500/2800 MB/s, DRAM and SLC cache, and TLCs. At currently 150€ / 180$ it's a good deal I think. Would be curious to see some tests by @gilles_polysoft and inclusion in the table. If there are more positive reports, we might add it to the whitelist of compatible SSDs.

Those are some great bench numbers in ADM
For comparison, i will enclose my experience with Apple OEM 1TB in a 2015 rMBP 13 inch, early 2015 below.
Also, I thought the 2014 MBP had a 2x PCIE connection, and not a 4x lane PCIE connection.

Anyway you slice it, great numbers, which makes sense, SMI controller 2262EN

Taken from The Tech Report:

"Transcend's MTE 220S SSD escapes SATA shackles

by Tony Thomas — 6:45 PM on January 22, 2019


Transcend isn't a name that comes up too often when discussing consumer internal storage, but the company boasts a wide array of solid-state products. The lineup has just expanded to include a range-topping NVMe drive. The MTE 220S is an M.2 stick powered by 3D NAND that pushes bits over a four lane-wide PCIe link to achieve sequential read speeds of 3500 MB/s and sequential write speeds of 2800 MB/s. If I had to hazard a guess, I'd say it's likely 64-layer 3D TLC from either Micron or SanDisk, with a rebranded Silicon Motion controller like the SM2262EN along for the ride."

 

[The_Moves]

What info/evidence do I need to post for my MyDigitalSSD BPX Pro 80mm 960GB?

I’ve got it installed, latest firmware (had updated to 14.4 prior to installing it), no modified bootrom or mattcard. U fortunately I already have copied my 300GB worth of data over twice now as I changed from APFS to HFS. I purchased it assuming it was similar to the Sabrent Rocket.

I’m also using a Sintech long adapter which I can also confirm has tape/some material over pins which makes kapton tape un-needed. Unfortunately the Sintech long does bend when securing it with the screw.

 

[shaderman]

Hi all. I see a lot of advanced guys here who understand very deeply.
My problem is not very standard and no one can solve it

I have problems with power supply of ssd drive samsung 970 EVO (not plus)
disk not visible in system. But if you perform certain actions from becomes visible
1. power computer ON and wait loading
2. enter sleep mode
3. exit sleep sleep mode
4. reboot system disk visible and work perfect (install OS, working)

BUT if computer power OFF and again power ON, disk again not visible

 

[djangoreinhardt442]

Hi all. I see a lot of advanced guys here who understand very deeply.
My problem is not very standard and no one can solve it

I have problems with power supply of ssd drive samsung 970 EVO (not plus)
disk not visible in system. But if you perform certain actions from becomes visible
1. power computer ON and wait loading
2. enter sleep mode
3. exit sleep sleep mode
4. reboot system disk visible and work perfect (install OS, working)

BUT if computer power OFF and again power ON, disk again not visible

You should to specify what model, year, size of MPB you have.
You should also specify which adapter you used.

It sounds like you have a sleep/hybernation issue

ADD ON:
Please read post 3954 by @MacXperte AND go to page 1 for correct code, as suggested by that user

#3954
↑
Hi @macgeek01 I was a little too fast to claim success. I started eventually getting the random reboots and double-startups. I put back the original Apple SSD and installed OS X 10.14.4. Now I have MacBookPro11,1 151.0.0.0.0which is latest rom. In fact I have more problems now than ever before!

Here is my pmset now:
Code:
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 1
gpuswitch 2
networkoversleep 0
disksleep 10
standbydelayhigh 86400
sleep 1 (sleep prevented by coreaudiod)
autopoweroffdelay 28800
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 10
highstandbythreshold 50
acwake 0
lidwake 1

I tried to fix restart issues with this command
Code:
sudo nvram enable-legacy-orom-behavior=1
That did not help at all. What do I do now? All sleep and hibernation issues are worse than ever. Do I have to flash the MBP to MacBookPro12,1 182.0.0.0.0 ??

### UPDATE ##
I reversed the nvram command with
sudo nvram enable-legacy-orom-behavior=1
Still it was crashing and restart every time on sleep. So I set back pmset to defaults. (also hibernatemode =3) At least I have no more restart after sleep. Still wondering what is correct values.
Click to expand...
With the settings you posted above, your issues were to be expected. hibernate mode 25 means hibernating on every sleep. But with your MacBook Pro 13" (Mid 2014), an NVMe drive and unpatched firmware, restoring a session from an hibernate file is not supported, so on every sleep it had to reboot.

To completely avoid hibernating, three values have to be set to 0 like this:
Code:
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
There are still discussions about it, and even Page 1 had a wrong command until now. For final clarification let me cite from the pmset man page:

SAFE SLEEP ARGUMENTS
hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets written is also dependent on the values of standby and autopoweroff

For example, on desktops that support standby a hibernation image will be written after the specified standbydelay time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.

I'll put the correct code on Page 1 right now.

 

[djangoreinhardt442]

No, that's not how "standby" works. According to the pmset man page standby 1 has no effect on what happens when the Mac goes to sleep, but only on what happens after sleeping on battery for the stanbydelay(s) duration.
[doublepost=1555098231][/doublepost]I successfully used a Transcend PCIe SSD 220S 1TB (TS1TMTE220S) with Sintech Adapter in a MacBook Pro Retina 13" (Mid 2014, MacBookPro11,1).

I updated the firmware before I started, booting from an external SSD with a plain High Sierra system on it. Although Security Update 2019-002 was installed on that external SSD before, App Store proposed it again (presumably because of the firmware not being up-to-date).

I bought both the long and the short black Sintech adapters and tried them both. Both came with black tape already protecting the backside of the connector and just worked, but I noticed some minor differences:

• The long version has a connector, that will allow you to easily insert the m.2 SSD in a 45° angle, producing more pressure on the pins when you bring it down and fix it in the final position. (Post #3950 has a nice picture of that.)
  The short version has a slide-in connector, similar to the one on the motherboard.
• Because of the different type of connector, the short version is also slightly thinner. In the A1502 housing that made the difference between the bottom case closing easily or not.

The performance (4x PCIe lanes with both adapters) was quite good for a Mid 2014 MacBook. Blackmagic reported 1360/1520 MB/s, and ADM 59 MB/s random 4k read!
View attachment 831826

The Transcend 220S SSDs have a nominal speed of 3500/2800 MB/s, DRAM and SLC cache, and TLCs. At currently 150€ / 180$ it's a good deal I think. Would be curious to see some tests by @gilles_polysoft and inclusion in the table. If there are more positive reports, we might add it to the whitelist of compatible SSDs.

I wanted to compare the benchmarks MacXperte posted:

The Transcend 220S uses the newer Silicon Motion controller SN2262EN
vs
The HP EX 920 uses the older SN2262 controller.

There is a difference the link bandwidth here (MacBook Pro 2014 vs MacBook Pro 2015 15 inch)
Nonetheless, very similar results (you can ignore the high(er) sequential reads and writes due to bandwidth limitation)

 

[axx0]

Nice results. I am experience similar things on the 13 inch 2014 model. I am getting a total of about 5-5.5 hours of usage with brightness set to 50%. I have not tested the sleeping power consumption.

How many charge cycles does your battery have? It seems like our OEM drives are extremely low powered in comparison to any NVME drive tested here, even the sabrent... still lasts longer than a windows machine though lol

"Charge cycle count: 296, Battery condition: Normal"

I'm a bit disappointed that the SSD upgrade costs so much additional battery power. I had a look on the tables posted here (thanks for this great work @gilles_polysoft) and wasn't expecting this.
(Apple SSD: 0.4W / 1.0W idle/avg. power consumption, HP EX920: 0.6W / 1.2W idle/avg)

 

[jackqueenking]

"Charge cycle count: 296, Battery condition: Normal"

I'm a bit disappointed that the SSD upgrade costs so much additional battery power. I had a look on the tables posted here (thanks for this great work @gilles_polysoft) and wasn't expecting this.
(Apple SSD: 0.4W / 1.0W idle/avg. power consumption, HP EX920: 0.6W / 1.2W idle/avg)

Yeah I have the same results with my Intel 760p, the wattages on the table are all within margin of error. The SX8200 averages 1.2 as well and the intel is listed at 1.3 but I doubt that 0.1 Watt difference will make for any improvements since usage patterns play a heavy role. I also don't think the Apple SSDs listed there correspond to the AHCI drives present in the 2013/2014 models. The ones listed are NVME I believe based on the speeds from 2015 and 2016 and I have a strong feeling that 2013/2014 drives use even less power than those ones which probably explains why even the lowest powered NVME cost this much additional battery consumption.
[doublepost=1555172552][/doublepost]

No, that's not how "standby" works. According to the pmset man page standby 1 has no effect on what happens when the Mac goes to sleep, but only on what happens after sleeping on battery for the stanbydelay(s) duration.
[

Yes that's what I meant. So visually speaking you'd have the following:
Standby = 1 would lead to the following states
Active --> Sleep --> Hibernate 0/3/25 (where the transition between sleep and hibernate is governed by standbydelay(s) time)

Standby = 0
Active --> Hibernate 0/3/25
Essentially the mac goes directly to hibernate

 

[djangoreinhardt442]

Yeah I have the same results with my Intel 760p, the wattages on the table are all within margin of error. The SX8200 averages 1.2 as well and the intel is listed at 1.3 but I doubt that 0.1 Watt difference will make for any improvements since usage patterns play a heavy role. I also don't think the Apple SSDs listed there correspond to the AHCI drives present in the 2013/2014 models. The ones listed are NVME I believe based on the speeds from 2015 and 2016 and I have a strong feeling that 2013/2014 drives use even less power than those ones which probably explains why even the lowest powered NVME cost this much additional battery consumption.

[doublepost=1555172552][/doublepost]
Yes that's what I meant. So visually speaking you'd have the following:
Standby = 1 would lead to the following states
Active --> Sleep --> Hibernate 0/3/25 (where the transition between sleep and hibernate is governed by standbydelay(s) time)

Standby = 0
Active --> Hibernate 0/3/25
Essentially the mac goes directly to hibernate

On the subject of Power Consumption

***Well, you are paying a price for extra performance:****
Apple AHCI SSD - idle consumption - 0.4W/write consumption - 3.4W/read consumption - 3.1W/AVG -1.0 W
Apple NVME SSD - idle consumption - 0.3W/write consumption - 5.0W/read consumption - 3.1W/AVG -1.1 W
HP EX920 idle consumption - 0.6W/write consumption - 4.4W/read consumption - 3.5W/AVG -1.2 W
ADATA SX8200 . idle consumption - 0.6W/write consumption - 3.9W/read consumption - 3.7W/AVG -1.2 W

If you want to conserve energy, then buy an older SSUAX or SSBUX type SSD (both should be AHCI-correct me if I am wrong please) off Ebay - they are plenty to be found and install it in your MBP

If you want to improve performance (whatever that means to you), then stick in a newer NVME controller (Apple makes a "Polaris" NVME SSD which is quite pricey - you can find one on Ebay too) -Either an Apple one (double the price or more than double the price of current non-Apple NVME SSDs) or one made by ANY of the compatible manufacturers listed on page 1.

I do not think it possible to have a controller consuming less power AND having a higher performance.

Gilles' numbers seem to support that notion which is why he has a power efficiency and performance by price chart

 

[jackqueenking]

On the subject of Power Consumption

***Well, you are paying a price for extra performance:****
Apple AHCI SSD - idle consumption - 0.4W/write consumption - 3.4W/read consumption - 3.1W/AVG -1.0 W
Apple NVME SSD - idle consumption - 0.3W/write consumption - 5.0W/read consumption - 3.1W/AVG -1.1 W
HP EX920 idle consumption - 0.6W/write consumption - 4.4W/read consumption - 3.5W/AVG -1.2 W
ADATA SX8200 . idle consumption - 0.6W/write consumption - 3.9W/read consumption - 3.7W/AVG -1.2 W

If you want to conserve energy, then buy an older SSUAX or SSBUX type SSD (both should be AHCI-correct me if I am wrong please) off Ebay - they are plenty to be found and install it in your MBP

If you want to improve performance (whatever that means to you), then stick in a newer NVME controller (Apple makes a "Polaris" NVME SSD which is quite pricey - you can find one on Ebay too) -Either an Apple one (double the price or more than double the price of current non-Apple NVME SSDs) or one made by ANY of the compatible manufacturers listed on page 1.

I do not think it possible to have a controller consuming less power AND having a higher performance.

Gilles' numbers seem to support that notion which is why he has a power efficiency and performance by price chart

Absolutely, I was just saying that even a small increase in power consumption can cause such a large difference in battery life. The AHCI SSD you mentioned i think is from 2015 since it has PCIe 3.0 x4 which is different from the PCIe 2.0 x4 in the 2014 models hence it lead me to think that maybe the 2014 drives had lower power consumption than what was listed in his table.

 

[shaderman]

You should to specify what model, year, size of MPB you have.
You should also specify which adapter you used.

It sounds like you have a sleep/hybernation issue

ADD ON:
Please read post 3954 by @MacXperte AND go to page 1 for correct code, as suggested by that user

#3954
↑
Hi @macgeek01 I was a little too fast to claim success. I started eventually getting the random reboots and double-startups. I put back the original Apple SSD and installed OS X 10.14.4. Now I have MacBookPro11,1 151.0.0.0.0which is latest rom. In fact I have more problems now than ever before!

Here is my pmset now:
Code:
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 1
gpuswitch 2
networkoversleep 0
disksleep 10
standbydelayhigh 86400
sleep 1 (sleep prevented by coreaudiod)
autopoweroffdelay 28800
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 10
highstandbythreshold 50
acwake 0
lidwake 1

I tried to fix restart issues with this command
Code:
sudo nvram enable-legacy-orom-behavior=1
That did not help at all. What do I do now? All sleep and hibernation issues are worse than ever. Do I have to flash the MBP to MacBookPro12,1 182.0.0.0.0 ??

### UPDATE ##
I reversed the nvram command with
sudo nvram enable-legacy-orom-behavior=1
Still it was crashing and restart every time on sleep. So I set back pmset to defaults. (also hibernatemode =3) At least I have no more restart after sleep. Still wondering what is correct values.
Click to expand...
With the settings you posted above, your issues were to be expected. hibernate mode 25 means hibernating on every sleep. But with your MacBook Pro 13" (Mid 2014), an NVMe drive and unpatched firmware, restoring a session from an hibernate file is not supported, so on every sleep it had to reboot.

To completely avoid hibernating, three values have to be set to 0 like this:
Code:
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
There are still discussions about it, and even Page 1 had a wrong command until now. For final clarification let me cite from the pmset man page:

SAFE SLEEP ARGUMENTS
hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets written is also dependent on the values of standby and autopoweroff

For example, on desktops that support standby a hibernation image will be written after the specified standbydelay time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.

I'll put the correct code on Page 1 right now.

Thank you for paying attention to my question.
Sorry to write here, but again I saw a lot here of advanced guys where who understand very deeply.

My computer
iMac 2017 21 (18,2)
Boot ROM: 170.0.0.0.0
SMC : 2.40f0
OS 10.13.6 or 10.14.4

adapter
https://aliexpress.com/item/M-key-M...108.1000016.1.684b492emWq0C1&isOrigTitle=true


pmset now

Currently in use:
standby 1
Sleep On Power Button 1
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
autorestart 0
networkoversleep 0
disksleep 0
sleep 1 (sleep prevented by sharingd, coreaudiod)
autopoweroffdelay 28800
hibernatemode 0
autopoweroff 1
ttyskeepawake 1
displaysleep 10
tcpkeepalive 1
standbydelay 10800


this command I already tried
sudo nvram enable-legacy-orom-behavior=1

 

[The_Moves]

Do we know if our MacBooks with NVME drives can use the L1.2 power state for true low power? Reading some drives don’t have the feature, others may get it via a firmware update. Maybe we can assume most drives made today have it?

 

[The_Moves]

Here is the smartctl information with power states from my MyDigitalSSD BPX Pro 80mm 960GB, also note I forced it to 4096 sector size.

Code snippet:

root@xubuntu:~# smartctl -a /dev/nvme0
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.18.0-15-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       BPXP
Serial Number:                      297707930FDE07070918
Firmware Version:                   ECFM12.2
PCI Vendor/Subsystem ID:            0x1987
IEEE OUI Identifier:                0x6479a7
Total NVM Capacity:                 960,197,124,096 [960 GB]
Unallocated NVM Capacity:           0
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          960,197,124,096 [960 GB]
Namespace 1 Formatted LBA Size:     4096
Local Time is:                      Fri Apr 12 02:08:34 2019 UTC
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0007):   Security Format Frmw_DL
Optional NVM Commands (0x0054):     DS_Mngmt Sav/Sel_Feat *Other*
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     70 Celsius
Critical Comp. Temp. Threshold:     90 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +    10.73W       -        -    0  0  0  0        0       0
 1 +     7.69W       -        -    1  1  1  1        0       0
 2 +     6.18W       -        -    2  2  2  2        0       0
 3 -   0.0490W       -        -    3  3  3  3     2000    2000
 4 -   0.0018W       -        -    4  4  4  4    25000   25000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 -     512       0         2
 1 +    4096       0         1

 

[selamet]

There were two versions of the black sintech adapter
Now I can confirm thaï every sintech adapters use the same wirings and work perfectly.

I have ordered black short adaptor from amazon. I have a concern about receiving old non-proper wiring version of the black short adaptor (due to old not sold stocks). Is there a way to check either the adaptor is the new corrected wiring or not ?