Jump to content
  • Here's how to configure adoptable storage on your S7 / S7 Edge


    PaulOBrien

    If you've been following the launch of the Samsung Galaxy S7 / S7 Edge, you may have read that adoptable storage, a Marshmallow feature that lets you use the microSD card just like internal storage, is missing. The S7s do include a feature where you can move apps to SD card, but it's not quite the same. The good news? You can enable the feature using ADB and it seems to work great, including in hybrid ('mixed') mode.

    In order to set adoptable storage up, you will need a computer with working 'adb' and, of course, a microSD card in your phone, the faster the better (I personally use a 128GB EVO+ in my own device. Here's the process!

    1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.

    2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.

    3. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.

    4. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).

    56c732ac96934_EmberLibraryMediator.png.a

    5. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179:160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179:160 mixed 50'. Easy right?

    6. This process will take a while, but when it's done, the Settings -> Additional Settings -> Storage view on your device should show the new Internal Storage. Note that, for some reason, the total space isn't reported correctly as you can see in this image, however everything seems to work OK. When you install apps, they will generally install automatically to the storage with the most space available, although you can manually move things around if you want to, perhaps for performance reasons (the real Internal storage will likely always be a bit faster).

    Screenshot_20160310-102957.png.89b152a2e Screenshot_20160310-103431.png.3e620ba5f

    7. If you want to see another view of how you are doing for space, you can use a third party tool such as FreeSpace or FreeSpace Plus.

    Screenshot_2016-02-19-12-42-43.png.6e319

    And that's it! Let us know how you get on, and enjoy your new, expanded S7!

     

     

    Edited by PaulOBrien



    User Feedback

    Recommended Comments



    Alex h, I got that same error and then I figured out that I put a space after the colon in "sm partition disk:179,32 private" and there shouldn't be one.  Just in case this helps uhh, 9 months later or helps someone else who found their way here to find a solution.

    Share this comment


    Link to comment
    Share on other sites

    Hi Paul, I have a Galaxy A7 (2015) Android version 6.0.1. I got to here but it didn't format at all,

    I:\Software\Samsung\fastboot>adb shell
    [email protected]:/ $ sm list-disks
    disk:179,64
    [email protected]:/ $ sm partition disk:179,64 private
    [email protected]:/ $

    Here is some additional info,

    1|[email protected]:/ $ sm list-volumes
    private mounted null
    public:179,65 mounted 03F7-C530
    emulated mounted null
    privatemode unmounted null
    [email protected]:/ $

    Here is another command that I tried,

    1|[email protected]:/ $ sm list-disks adoptable
    [email protected]:/ $

    Edited by Tim Lim
    Appended info.

    Share this comment


    Link to comment
    Share on other sites



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Social

  • Topics

  • Posts

    • Selling a pixel 3a black. Unlocked and boxed   Has a tiny ding right on the front bottom but with the screen protector on can't even tell.   Comes with case.   £200 delivered
    • can you please tell me how you signed the zip file because with zipsigner it doesnt work 😕 says footer error in recovery Greetings
    • Hello. I've been using this smartphone since 2016, I went through the official upgrade to Android 5.1.1 and then to 6.0.1. Long story short I'm now with TWRP 3.2.3-0 and Lineage 14.1 (Android 7.1.2). I found some interesting bugs: one is that if you have low battery, about to self power off, and you switch on the torch, it stays on even after the phones is powered off, and you can't turn it off whatsoever, except plugging in the charger and switch on the phone again I guess, but I didn't try it. The matter is that if you let the torch on to let the battery discharge completely, and the light goes off, when you charge it again and switch on the phone you can't switch on the torch anymore, even tho the system claims is on, it doesn't beam any light from the flash led. The only way to "reset" this status is to open the phone, removing the back cover, unscrew 3 screws that hold a tiny bar and manually disconnect the battery (most rightside connector) and then reconnect it. Not even holding the power button helps. Another bug is that if you turn on the phone, and then, without putting it on stand-by, check with some kind of cpu monitoring app the cpu cores activity, the less powerful cores of the A53 are awake and running. If you put the phone in stand by and then re-awake it up, they are always on sleep or "disconnected" or similar status. Even tho it seems that this doesn't affect performance, so it seems that they doesn't show correct running status but still works. Last but the most important: the phone THROTTLES at room temperature!!! If you try a cpu intensive app, the cores throttles at 800 MHz or less, and if it heats more it goes down even to 200 MHz stuttering everything! I don't know if it gots bad thermal spread design or is it a thermal sensor bug, since in system monitor apps it shows temperature above 49~50 in idle while room temp is 20 to 23 °C and over 67-68 while running full calculations! Can anybody confirm or else suggest me some solutions to these issues? Thanks.
    • It worked well on my liquid a1 (running custom rogers rom). Should work on any acer based 2.2 roms I think. But I cant guarantee 😉 use at own risk.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.