Just thought I'd report an observation.
To Nandroid backup my CRemix rom (3.8GB), it took:
to Internal storage: 2 minutes
to SD Card storage: 6 minutes
Haven't clocked the restore process yet...
-Mike
Yeah, I've noticed that too. Even with high class cards, it takes considerably longer than internal storage, which is normal. If I need a quick backup to test something out, i use internal storage, otherwise it's SD.
Related
I just installed the latest version of CM6 and I think the nandroid backup or something took up a huge chunk of my internal storage (maybe), but i went from about 80MB of internal storage to 15MB, then moved all my apps to my sd card and now i still only have 25MB, with 645MB on my sd card
i dont think this is normal, right?
can someone suggest ways of how to free up some internal storage space? idk what is safe to mess with and what isn't
Were ROM did you flash over? An older version of CM6 or something else? Did you remember to wipe both the cache and dalvik? If you made a nandroid backup it should go to the SD card, not internal storage. It isn't normal for the mem to be that low. I'm not sure what you should do, but I'd recommend reflashing and make sure you do all the wipes.
I've been on the nexus kick for a few years now and getting a note 3 when it's released, but I had a question regarding storage and roms that I was hoping someone would be able to clear up for me....
On the nexus line there is a virtual sd card and anything you save to that takes up part of the 16gb storage, but when I wipe and install a new rom the virtual sd card portion of the phone remains untouched, so I still have my music, navigon maps, ringtones, etc. On older phones I had, I had something like 8gb internal and a physical sd card and wipes would clear the full 8gb but leave the sd card intact. With a phone like the note 3 with 32gb of storage and physical sd slot, will wiping and rom changes take out the entirety of the 32gb internal storage, meaning I shouldn't use it for music, videos, or pictures, but only use it for programs? 32gb is a hell of a lot of storage for only apps, especially coming from a 16gb nexus which was 16 total between "sd" and internal storage.
On Note 2, "internal" SD card is not touched when flashing custom ROMs, unless you choose to wipe SD card in recovery. I see no reason why Note 3 would be different.
Okay that sounds good. I wasn't aware if phones with physical sd card slots would have a virtual internal sd card from their phone memory since the last time I had a phone with a physical sd card the virtual internal sd card wasn't a thing.
Hey all,
Forgive me if this question has been asked before (Google did not help me find an answer) but I'm looking for the "best practice" method of upgrading my MicroSD card once it's already been mapped to internal storage using Marshmallow's "Flex Storage" capability.
I bought a 32GB Moto X Pure Edition and promptly installed my fastest MicroSD card (a 32GB PNY U3 Turbo card) and set it to function as internal storage after the Marshmallow update.
Since then, I bought a 64GB U3 card so that I'd have ample space for music and video. What I'm trying to figure out is the process to:
1) Take a snapshot of my internal storage (i.e. copy to an external HDD)
2) Remove the "old" microSD without any detrimental affect to installed applications
3) Mount the "new" larger microSD as internal storage
4) Copy everything back to the new internal storage
Is there a documented process for doing this, or some sort of migration tool I can use to upgrade the microSD capacity?
Good question
Bumpage. Has anyone seen anything on the nets describing the storage upgrade process for Flex Storage?
Probably not possible unless you flash a new ROM over the old. My understanding is that the sd card, once made to be part of the phone storage, is that it is 128bit encrypted in EXT4 format.
bw03 said:
Probably not possible unless you flash a new ROM over the old. My understanding is that the sd card, once made to be part of the phone storage, is that it is 128bit encrypted in EXT4 format.
Click to expand...
Click to collapse
The thing is I currently have more internal storage free space available than actual data stored on my SD, so ideally there should be a way to migrate my data back to true internal storage, eject the SD, and replace with a bigger card?
Even if I have to do it manually, I want to make sure I don't screw with installed apps.
Sent from my XT1575 using Tapatalk
Might be a stupid question but have you tried taking out the card and seeing what happens?
I think the moral here is to start with the largest capacity card you think you'll need. 64GB cards are dirt cheap these days. Unless you need your entire mp3 collection on your phone, I doubt there is a real need for anything bigger.
I mentioned this in another thread, but probably more appropriate here. There is a way to partition the card for both internal and external storage. Portion of it is used for apps/data while the rest for pics/music and is visible when not in the phone.
The question is, can you create a twrp image of the system & internal storage with one sd card. Replace it with a different one, repartition it (in recovery), then restore your data?
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
Hello,
There might be a solution.
(Please notice I translate the android names from French, so there might be some variations)
In the settings/storage, click on the interal memory line.
In the settings -the 3 dots top right-, you might be able to transfer data from SD to internal memory.
Then, you can format back you sd card, remove and replace it, and voila, that should work.
My 2 cents,
Decided to start using this yesterday, was a sort of on the whim decision.
I have a 32 gig S7 and a 64 gig sd card, it is an expensive samsung SDHC EVO UHS card. (they cheaper now but was expensive when I purchased).
So previously I had internal memory which was the phone's internal storage, obviously this is not the full 32 gig as a chunk is partitioned off for OS usage.
SD card as portable storage formatted using exFAT
I noticed first when I installed superman rom I couldnt make /data F2FS, tkkg explained it is because alot of the scripts used to install the likes of magisk etc. do not support F2FS so my internal is ext4, but I managed to make the cache filesystem F2FS at least.
Likewise yesterday I discovered using the portable sdcard as F2FS is also not supported, the rom wont auto mount it and a notification appears saying its corrupted. Since I had already wiped the SD to change filesystem I decided to try adoptable storage, I enabled using the adb method and using the mixed mode so not the full sdcard is adoptable storage, in my case I chose a 50/50 split bearing in mind nandroid backups are huge, to do one single backup I need 12 gig free on the portable sdcard storage.
Interestingly I discovered the partition used for the adoptable storage is F2FS , it gets mounted under /mnt/expand/{some long random id}, I dont know the exact criteria for how parts of data get moved there but 1.8gig was utilised from the off.
Knowing its F2FS which is more resilient than exFAT, I have already moved titanium backups to the adoptable storage away from the portable sdcard storage and I plan to also move media to it as well that is currently on the portable storage.
My free space that is available for internal use is now moved from 13.6gig free out of max 25 gig to 36gig free out of a max 55gig.
I have one warning tho, I have already raised this on github to the TWRP dev's, from what I can see TWRP is not adoptable storage aware. The F2FS partition is not auto mounted in TWRP and I cannot even find a way to manually mount it (in the GUI), since some stuff from /data will get moved there it means when a nandroid backup is done parts of /data may be excluded that are sitting on the adoptable storage. Not a big deal if you doing a backup to test something, and then if you restore, its done close to when the backup is taken, but if the restore is done a long time after the backup the adoptable storage been out of sync might be an issue.
I welcome further thoughts from people.
update TWRP devs say it is supported but might be an issue with mixed mode which I will provide them more info on later.
attaching speed test
first sdcard is exfat second is f2fs Adoptable
I'm really confused what you are trying to show? Are you claiming that your sd card somehow becomes faster as adoptable storage?
I dont know if it is actually faster but it does benchmark faster probably due to using F2FS instead of exFAT.
The main reason I am preferring F2FS as it has more resilience than exFAT whilst still been fast.
Ok a little update, after my failed aatempt to upgrade to a 128 gig card, I restored the nandroid backup which I made before I first inserted the 128gig card.
Now the adopted storage is not been mounted by android, I wont be doing anything about this now as I have another 128 gig card arriving tommorow at which point I will need to setup mixed storage on that anyway, but it seems if you try to make another adoptable storage on new card, even if you have a nandroid backup, the previous adoptable storage is not preserved, suggesting the settings for it are not configurdd in a location that is included in nandroid backups.
I am not aware of a process that allows an already created adoptable storage partition to get remounted, I assume I would need to wipe the sd card again and rerun the commands to set it up which is not very user friendly.
It was running perfectly fine until I tried to make a new storage on my 128gig card, but is flawed if you are swapping out sd cards.
ok some clarification on the bench figures.
The red scard is the portable sdcard storage.
The yellow sdcard is actually the phone internal memory.
Internal memory is the adoptable storage.
So the F2FS isnt miles faster which makes sense as F2FS is supposed to be very close to exFAT in performance, faster than ext4 but not so much exFAT, however it has exFAT levels of performance with better data integrity mechanisms (exFAT has no safety mechanisms).
I found this out in two ways.
The internal memory test failed when I accidently left the bench folder read only in the adoptable storage.
I also added a custom location test of /sdcard which matched the yellow sdcard scores.
The question now is that is the slower write performance of a evo+ card going to be noticeable versus the internal storage speeds. So far indications seem no, also that by default my camera was writing to the sdcard anyway and has always worked fine.
It seems what goes on the mnt/expand or on /sdcard when device storage is specified is automatically decided by an algorithm.
Those who are want to use adoptable storage and have concerns over write speeds, there is pretty fast sdcards out there like the samsung pro which has 90mB writesm, but I think that card can only go up to 64gig in size.
Hello.
I have a Moto G4 and it has SD card formatted as internal and so some of the apps and data is physically on the SD card. The total system+apps+data storage is approximately 15GB and the internal memory of the phone is less than 15GB, hence I have the SD card formatted as internal.
I am currently running LineageOS 14.1 on the device. My questions is that if I backup the ROM and all its apps and data in TWRP recovery and later restore it on the same device but with SD card not formatted as internal, would this work? where would the apps+data which exceed phone's internal memory be saved?
Thanks
Regards