Ok, so here's something fun. I'm not sure if it's just touchwiz or all ROMs do this. If you look at your disk space, you're going to notice that a large portion is used, however it's being reported incorrectly. Let's say you're using 2.5Gb on your internal SD card. That 2.5Gb is being reported twice, so rather than having 8Gb free, any disk space report will show 5.5Gb free. Here's how you can see this.
For rooted users in ADB (or terminal):
Code:
cd /
busybox du -sh *
##You'll see that /data is fairly large
##Also, note the size of /sdcard
cd /data
du -sh *
You'll see /data/media is being reported as the same size as your SDCard. That's because /data/media is your internal SD Card. So basically any report will incorrectly report disk availability. If anyone has an AOSP ROM that they can test this on it would be appreciated.
I thought that on sd cards didn't show true to the advertized card size do to the calculations of bits by the manufacturer.
Related
I've encountered problems trying to access the external SD card on my rooted Samsung Galaxy S3.
There are entries in /mnt/ for both internal and external storage, namely the following mount points:
/mnt/sdcard/ - internal
/mnt/extSdCard/ - external
The former is mounted onto the filesystem as /sdcard/. Ideally I'd like to mount the external card instead. Based on information elsewhere on the site, I checked the /etc/void.fstab file with the intention of making changes. However I didn't find what I was expecting. Here's the relevant part of the file:
Code:
{
supported_exfat = yes
}
dev_mount sdcard /mnt/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
Based on this config I would have expected the external SD card to be mounted as /sdcard/. But clearly it isn't, and I don't understand why.
For the time being I am using Directory Bind to access external storage via /sdcard/external_sd/ but it would be easier to simply mount external storage as /sdcard/.
Anyone have any suggestions?
Hi,
I have a Nexus One running the latest CM7, and a 32G sdcard with 3G partitioned for sdext2. I use Link2SD to link or move apps to the ext partition. My current free storage info:
/data (on device storage) - 107M
/data/sdext2 - 2G
/cache/download - 107M
/mnt/sdcard - 22G
Everything works as expected until I try to install an app larger than the available internal storage (a number of Humble Bundle apks are quite large). The install fails on the phone, and using adb to install gives me this error:
Code:
[email protected] /A/A/s/platform-tools [1]>
./adb install -e ~/Downloads/SwordAndSworcery-android-1.0.16hb_1380585044.apk
failed to copy '/Users/am/Downloads/SwordAndSworcery-android-1.0.16hb_1380585044.apk' to '/data/local/tmp/SwordAndSworcery-android-1.0.16hb_1380585044.apk': No space left on device
rm: can't remove '/data/local/tmp/SwordAndSworcery-android-1.0.16hb_1380585044.apk': No such file or directory
As I understand it, Link2SD is only links/moves an app after it has been successfully installed.
Is there a way to install this "directly" to the sdext2 partition, or perhaps link the /data/local/tmp to the sdcard?
Thanks,
Todd
I wanted to have the fast SD Card, just to make the overall performance of my phone just a little better, and since my phone model (LG Optimus F7 everything has to be linked to SD card because the "external sd card" is a partition of the built in internal giving 1.27 gig of space - On a current gen phone! Jellybean!)
So I have a SanDisk Ultra 32 gig chip - active chip - partioned into 2 partitions - 1 Fat 32 and 1 ext4
The new card is a Micro Center Circle(10) HC 32 gig chip - partitioned into 2 partitions - 1 fat 32, and 1 ext 4
I have a multi-card reader for my laptop, when I try my main chip the fat32 partition can only have the files copied off, and the ext4 partition won't mount. So I can't just copy the files because any files on second mount are inaccessable. (I just thought while typing this I could makesure partition 1 is bigger than 2, use built in file manager copy all of partition 2 onto 1 on sd card, copy onto computer).
Anyway, I'll try that, but I was wondering if I transfered as much material, then made a back up of my rom, factory reset, re-installed backed up rom but with other sd card in, wouldn't the rom put the files on the sd card where they were? It won't know I switched?
Running Ubuntu Linux -
Errors I get from Terminal, etc below
Code:
####ERROR######
Error mounting /dev/sdb2 at /media/xieon/71937e1e-588a-4e44-a435-9c6485d066c3: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb2" "/media/xieon/71937e1e-588a-4e44-a435-9c6485d066c3"' exited with non-zero exit status 32: mount: block device /dev/sdb2 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdb2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
#####ERROR#####
I have a cheapo DragonTouch Y88X. I'm not looking for a custom ROM or anything - its for the kids and honestly it does everything they need, with one exception: Disney Movies Anywhere can't download videos to the external SD card.
As near as I can tell, this is an application problem - hardwired looking for /mnt/sdcard instead of using the Google API to find where the SD card is mounted, and DragonTouch was brain dead and mounted part of the internal storage to /mnt/sdcard (the actual SD card gets mounted to /mnt/extsd).
OK, so I'm not going to get Disney to change the app (and there's no setting to change where it downloads to other than "Save To/Play From SD Card"), so I started poking around how to change the mount points. I'm reasonably familiar with linux, sys admin duties and the like. But the format and options on the fstab file are a bit unfamiliar to me... All I really want to do is make the external SD card be mounted at /mnt/sdcard (and maybe mount the internal partition to something useful - maybe app cache space or something?)
I managed to get root and installed ES File Explorer, and the fstab file (/fstab.sun8i to be specific) has the following lines that I think are relevant...:
Code:
...
/devices/virtual/block/nandk auto vfat defaults wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host auto vfat defaults wait,check,noemulatedsd,voldmanagedsd=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
...
I don't know quite enough about either fstab or Android/DragonTouch's variant of it to know why both sdcard and extsd have two entries each... Or exactly how to swap them. I could try to change the voldmanaged=[name] entry on each - would that be safe?
Is what I'm trying to do crazy, or should this work?
Thanks
Hi everyone!
I have successfully expanded the internal storage of the phone with an sd card using the "sm partition DISK mixed" command in adb:
Code:
mido:/ $ sm list-disks
disk:179,96
mido:/ $ sm partition disk:179,96 mixed 50
mido:/ $ sm list-volumes
private:179,99 mounted 0e05b528-c814-4078-b7ef-1a0f95260531
private mounted null
public:179,97 mounted F227-1806
emulated mounted null
emulated:179,99 unmounted null
My phone is Xiaomi Redmi Note 4x MIUI Global 11.0.2 (android 7.0). Sd card used: Kingston 8GB MicroSDHC class 4.
I successfully used this mode for a while (transferred many applications to sd) until I saw that class 4 memory cards are really very slow and bought a new class 10 memory card: Smartbuy microSDHC 64gb class 10.
And here, unfortunately, it was not possible to expand the internal memory. Here is the adb shell log:
Code:
mido:/ $ sm list-disks
disk:179,64
mido:/ $ sm partition disk:179,64 mixed 75
mido:/ $ sm list-volumes
private:179,67 unmountable null
private mounted null
public:179,65 mounted C1B0-1F00
emulated mounted null
We see that private volume is not set, unlike the code at the beginning. Moving applications to the sd card does not work (the "change storage" button disappeared in the interface)
I tried to
Code:
mido:/ $ sm format private:179,67
mido:/ $ sm mount private:179,67
Error: java.lang.IllegalStateException: command '328 volume mount private:179,67 0 -1' failed with '400 328 Command failed'
The set-force-adoptable setting also failed, but the error code changed:
Code:
1|mido:/ $ sm set-force-adoptable true
mido:/ $ sm mount private:179,67
Error: java.lang.IllegalStateException: command '336 volume mount private:179,67 0 -1' failed with '400 336 Command failed'
1|mido:/ $
Setting "set-force-adoptable" before "sm partition" didn't help also.
How can it be that this procedure worked with one memory card, but did not work with another? What criteria can I use to buy a new memory card to be sure everything will work out? Is there still a way to fix something with this memory card?
Thank you very much in advance for your help!
As long as you don't undo Adoptable Storage on 1st SD-card ( means reformat it as Portable Memory ) you can't use the 2nd SD-card as Adoptable Storage
jwoegerbauer said:
As long as you don't undo Adoptable Storage on 1st SD-card ( means reformat it as Portable Memory ) you can't use the 2nd SD-card as Adoptable Storage
Click to expand...
Click to collapse
I forgot to write about it, I did it after old SD through “Settings” -> “Storage” -> “xxx SD card” -> ”ERASE & FORMAT. Didn't help
As I can see you didn't get it.
BTW: What you've done was the absolutely wrong way.
jwoegerbauer said:
As I can see you didn't get it.
BTW: What you've done was the absolutely wrong way.
Click to expand...
Click to collapse
How can I undo Adoptable Storage on 1st SD-card?
I tried to "sm partition disk:xxxxx public" on 1st card.
Also I tried to use instruction from one forum thread :
To go back from adoptable to portable storage open Settings/Storage/Phone storage/hit 3 dots od the right top corner/migrate data, bit be sure you don't have more data on SD that's your internal storage of the phone. That's all, then you can format your sd as a portable storage.
Click to expand...
Click to collapse
My Xiaomi has no 3 dots on the right top corner so I thought " Erase & Format " does the same.
IDK how to reverse the adopted storage to portable storage by means of sm thus the linkage gets removed: never have tried it. May be sm unmount command does the job.
BTW: Erase & Format applied to adopted storage simply wipes all data there and freshly formats it.
jwoegerbauer said:
IDK how to reverse the adopted storage to portable storage by means of sm thus the linkage gets removed: never have tried it. May be sm unmount command does the job.
BTW: Erase & Format applied to adopted storage simply wipes all data there and freshly formats it.
Click to expand...
Click to collapse
I tried to "sm unmount", no changes. I tried to use a third memory card, but it's the same with it. The first memory card can still be set as adoptable. It seems that the phone remembre 1st card and does not want to work with others.
August9299 said:
The first memory card can still be set as adoptable. It seems that the phone remembre 1st card and does not want to work with others.
Click to expand...
Click to collapse
That's what I told you.