• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help SD card as internal storage but message: ran out without using it!

coyote2

Newbie
Jan 4, 2019
48
26
I'm a confused Android noob.

My very first step was to add a 32 GB sd card as internal storage, which appeared to work:

Screenshot-20190112-133937.png


But then when I couldn't find the most-recent Apps I installed (as confirmed by the Play Store), I removed and re-added the Google Account I use with the store, and then noticed:

Screenshot-20190112-134942.png


Hence my confusion.

Aaargh. Any advice please?

Android 6.0.1
ZTE Z718TL
(Honestly I'm just using this weak phone to learn Android, I plan to then upgrade to a nicer phone.)
 
SD cards only recently could be used to expand system storage, but some manufacturers have disabled that. It's called adoptable storage, but it creates a different set of issues so it might not be able to be used that way on your phone.

If that's the case, then your apps must reside in the built-in memory of the phone. Worse is that that 8 GB the phone reports 2 GB is reserved for the system and the recovery partition among others so you'll only see maybe 5 GB or user storage.
 
  • Like
Reactions: Dannydet
Upvote 0
From my experience with a Lenovo phone that also runs Android 6, I found out that even when I added a 32gb SD card and successfully used it as internal storage, the phone still use the built-in memory to install apps. I can mount or unmount the sd card on the fly and the phone still works fine. Only some apps that use the SD card for storage would show a message saying that the SD card is missing.

So formatting a sd card as internal memory doesn't necessarily cure your apps memory shortage issue.
 
Upvote 0
Thank you both very much for your helpful replies!

I'm sorry I neglected to mention that this phone's manufacturer disabled that option too, I followed the instructions here
https://www.modaco.com/news/android...e-adoptable-storage-on-your-s7-s7-edge-r1632/
to use 'adb shell' to configure it as internal/adoptable storage. (Incidentally, for a raw noob that was too much challenge! Particularly because to get adb shell working I also needed to get Android Studio working and Windows drivers for the phone which itself challenged me.)

Perhaps I am simply assuming wrongly that once it runs out of internal memory if would automatically start using the adopted MicroSD card memory...

Question One:
Is what I need to do move the Apps from internal memory to the MicroSD card one at a time?
(I saw on Youtube how to do that)

  • "people successfully rooted your phone model using Kingroot. If you can root your phone, the famous app called "Links2sd" will help moving your apps to SD card."

As a noob who is using this as a temporary 'practice' phone I think rooting sounds an intimidating bridge too far for me.

I'm hoping that the move-one-at-a-time thing I asked about above will free up enough memory to install enough apps for me to configure/use them. Oh that reminds me please...

Question Two:
When I restore the backups I'm making to my Google account of this practice phone, to my future phone, will all the App config be preserved? If not, I'm using Android's default backup in Settings, would some other tool/method migrate more settings?

Thank you so much in advance!
 
Upvote 0
On rooting... All rooting is is gaining administrative privileges for your device. It allows you to access and write to the system partition. Because this is a security risk, many apps that require advanced security (like banking, finance, medical, etc.) may not work on a rooted device. Just saying.

By having root privileges, you can links2sd but I'm not sure if it works with any android phone after 5.0 since partitions are allocated differently. And BTW, moving apps to SD is not the same as adoptable storage. Links to SD really just formats a partition on your SD card in the same format as the internal storage and then creates symlinks that point to the SD where the app thinks they should normally reside. Adoptable storage extends the internal user partition to the SD card making it indistinguishable to the system.

Sounds great, right? Why not do that? Well, here's why. Micro SD cards are notoriously flaky when stressed under the load of continual read/writes from running apps directly from them. Because they are part of the user partition, when they fail (not if) they can take everything with them, even the files on internal memory. Plus, when used as adoptable storage, the card is encrypted and should never be removed from the phone ... ever .. unless you are going to perform a factory reset and format the card. SD cards are fine for storing anything that do not impact the system and you can backup like photos or media files.

Here's how Google backup/restore works. When you check that box to backup your apps and settings what you are really doing is backing up ONLY settings -- and this is important -- NO DATA. What does that mean? Well, if you ever have to restore your phone from the cloud, what restore will do is look at the list of apps the play store thinks you had on the device and reload them, in the latest version, from the play store. It will then attempt to overwrite the default settings with the ones it backed up from your phone. 98% of the time that's good enough, but if you have local data associated with the app, Google does NOT back that up, unless you tell it to specifically with Drive sync. So let's say you are playing a game that maintains your account in the cloud and one that saves game data locally. If you drop your phone in the pool and have to get a new one, when you restore, the games will load and the first game will be fine and you can pick up where you left off. The second game will most likely start you back at square one, but with the same credentials.

You are discovering the drawbacks of going cheap with Android. While it's certainly possible to use the device and many people do every day, you will never have the Android Flagship experience on a $200 phone.
 
Upvote 0
First, thank you very much lunatic59 for the priceless grounding I needed!

On rooting... All rooting is is gaining administrative privileges for your device. It allows you to access and write to the system partition.

Ah, that doesn't sound offputting...

Because this is a security risk, many apps that require advanced security (like banking, finance, medical, etc.) may not work on a rooted device. Just saying.

But this does, I want such apps to work.

By having root privileges, you can links2sd but I'm not sure if it works with any android phone after 5.0 since partitions are allocated differently. And BTW, moving apps to SD is not the same as adoptable storage. Links to SD really just formats a partition on your SD card in the same format as the internal storage and then creates symlinks that point to the SD where the app thinks they should normally reside. Adoptable storage extends the internal user partition to the SD card making it indistinguishable to the system.

That's what I expected, and exactly why I still don't understand why now that I HAVE MADE THE MICROSD CARD adoptable storage, I'm unable to install anymore apps even though the card is showing nearly empty.

Sounds great, right? Why not do that? Well, here's why. Micro SD cards are notoriously flaky when stressed under the load of continual read/writes from running apps directly from them. Because they are part of the user partition, when they fail (not if) they can take everything with them, even the files on internal memory. Plus, when used as adoptable storage, the card is encrypted and should never be removed from the phone ... ever .. unless you are going to perform a factory reset and format the card. SD cards are fine for storing anything that do not impact the system and you can backup like photos or media files.

I get it, but this is just temporary for practice so I figured the card would do well enough and survive long enough.

Here's how Google backup/restore works. When you check that box to backup your apps and settings what you are really doing is backing up ONLY settings -- and this is important -- NO DATA. What does that mean? Well, if you ever have to restore your phone from the cloud, what restore will do is look at the list of apps the play store thinks you had on the device and reload them, in the latest version, from the play store. It will then attempt to overwrite the default settings with the ones it backed up from your phone. 98% of the time that's good enough, but if you have local data associated with the app, Google does NOT back that up, unless you tell it to specifically with Drive sync.

Beautiful! I think I enabled Drive sync already, I'll make sure I do!

So let's say you are playing a game that maintains your account in the cloud and one that saves game data locally. If you drop your phone in the pool and have to get a new one, when you restore, the games will load and the first game will be fine and you can pick up where you left off. The second game will most likely start you back at square one, but with the same credentials.

You are discovering the drawbacks of going cheap with Android. While it's certainly possible to use the device and many people do every day, you will never have the Android Flagship experience on a $200 phone.

Got it. I'm just practicing on this phone because it was free. (Battery and speed are also unacceptable.)
 
Upvote 0
I still don't understand why now that I HAVE MADE THE MICROSD CARD adoptable storage, I'm unable to install anymore apps even though the card is showing nearly empty.
If you see your SD card listed as a separate location that the internal storage (not system) then it's not adoptable storage. On your 8 GB device I would guess originally you'd see the system at 1.7 GB and internal storage at 5.4GB .. or pretty close to that. When you pop in a 32 GB SD card, you will see that listed as either SD card or External storage depending how ZTE named them for this phone. And you'd see about 29 GB available (the old bit/byte rounding to confuse the heck out of people and make you think you're getting more than you do.)

Now, if you truly made the entire SD card adoptable storage, then you should only see a 1.7GB system and a 34GB internal partition.

I looks at the instructions and they were for the Samsung Galaxy S6/S7. Just because those instructions work for the S6 and S7 doesn't mean they will work for a ZTE phone. While they are common adb commands, it doesn't guarantee that the phone will even recognize the partition as part of the system.
 
Upvote 0
If you see your SD card listed as a separate location that the internal storage (not system) then it's not adoptable storage. On your 8 GB device I would guess originally you'd see the system at 1.7 GB and internal storage at 5.4GB .. or pretty close to that. When you pop in a 32 GB SD card, you will see that listed as either SD card or External storage depending how ZTE named them for this phone. And you'd see about 29 GB available (the old bit/byte rounding to confuse the heck out of people and make you think you're getting more than you do.)

Now, if you truly made the entire SD card adoptable storage, then you should only see a 1.7GB system and a 34GB internal partition.

I looks at the instructions and they were for the Samsung Galaxy S6/S7. Just because those instructions work for the S6 and S7 doesn't mean they will work for a ZTE phone. While they are common adb commands, it doesn't guarantee that the phone will even recognize the partition as part of the system.
Thank you again very much for your reply, lunatic59!!

The reason I asserted that my MicroSD is now adopted storage (and the reason I included the first picture in my original post), is that the process on that link I shared about doing it on the S7 I performed made the exact change seen in the two pictures in #6 on that link (which I'll paste here...sorry they're so huge...remember these 2 printscreens are from that link not from my phone)

Screenshot_20160310-102957.png.89b152a2e46a01fbf4a0e11cbf0148ad.png

Screenshot_20160310-103431.png.3e620ba5fdfb230a8a5d23701bf88f79.png



(i.e, from the card being listed under Portable Storage, to no Portable Storage being listed, so now my card too is listed not as Portable Storage anymore).

But that's really all I know to look for, so when you say "If you see your SD card listed as a separate location that the internal storage (not system)", I'm sorry but I don't know where else to look....Where do I look please to see the things your helpful post points out I should look for, please?
 
Upvote 0
p.s. I just looked at a ton of apps (in Settings|Apps) including every one that said it used more than 1 MB of storage. At least 2/3 didn't even have a "Change Storage" button...but for every one of those I clicked it and of the 2 options offered, "Phone" and "SanDisk SD card", every one already had "SanDisk SD card" selected.

So...while I'm still extremely curious to take a look at wherever I can find (?) the info lunatic59's last post was pointing me to, after that I guess I'll be buying a nice phone...just sooner than I planned.
 
Upvote 0
What those linked images are showing are how SD card went from roughly 30 GB up to 60 GB after adopting the storage. The problem with that is the idea the SD card is actually your micro SD card. It's the internal storage mounted at /sdcard.

When Android was first developed over a decade ago, there was very little internal memory so expansion was done with removable storage in the form of an SD card. Since Android is based on the Linux kernel, it requires a mount point for all storage and it was hard coded into the os to mount external storage as '/sdcard'. At the time all installed apps would use /sdcard as the default location. As Android devices improved over time and began to have larger internal memory, external storage became optional, but apps still looked for /sdcard, so it was changed to create a mount point on the internal partition and make external storage mount someplace else. Android devices (phones or tablets) today may not even have an SD card slot, but apps still need to use the /sdcard path to install and save data. That's why you have one and it's NOT the real SD card.

If you can see a mount point called "SanDisk SD card" then you definitely haven't adopted the card. And, just because the card no longer shows under storage, doesn't mean it's being used. It just isn't recognized by the OS.
 
Upvote 0
Thank you very much for your reply!

You say "If you can see a mount point", and I'm unsure: does "SD card" appearing on the pictures I'm posting mean we see a mount point...or is there some other screen (or App) on which I would need to see if it is a mount point? (Sorry I'm such a noob, I'm just trying to learn and thank you for your help!)
 
Upvote 0
You stated that the images poster were from the tutorial and not from your phone. Just because the screens you see look similar doesn't mean that the process was successful. Here's what you need to see on your end ... Before: Under device storage, besides the "internal storage" you need to see "SD Card" listed under both internal and portable storage. After: you should no longer see portable storage, but more importantly, you should see that the amount of space listed under Internal SD Card has grown by the approximate size of your physical SD card. If you don't see that, then all you've done is made your SD card unrecognizable to the phone.
 
Upvote 0
(Unfortunately I didn't [even know how to] create a 'before' screenshot on my phone, but) the 'after' screenshot on my phone is the very first image in this thread's initial post. (And the word "internal" is no where on it, but no problem since...)

I do notice that the capacity of the SD card has remained the same (the actual capacity of my card), while on the before/after examples on the instructions(1) that I posted (now that I finally focus my attention on what you've patiently and repeatedly explained I should look at) I do see that on the 'after' photo the displayed capacity of the SD card on the S7 has roughly doubled (it's presumably true capacity, wow!).

(1) which I naively and ignorantly went ahead thinking would/did would work on my different phone model.

I'm touched that you so generously spent the time to help me, lunatic59. It's a great comfort to know that androidforums is here.
 
  • Like
Reactions: lunatic59
Upvote 0
Here's one of the things that bugs me about phone manufacturers ... they mess with the settings menus. Not to add or take away features, but simply to change the way things are displayed. Apparently Samsung splits the internal and external sd card partitions when displaying storage, but ZTE (like LG, my phone manufacturer) lumps them together under Device. At least LG labels it as internal and external.

meminternal.png


So in your case, if the SD card was adoptable and you added it correctly you'd see your "Phone" storage increase by the size of the SD card. Since ZTE only displays the SD Card under storage when it detects a card in your phone, then I am going to say it wasn't adopted, or else you wouldn't see an SD card at all.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones