Hi,
My Sony tablet S 16GB does, according to settings -> storage, has this much memory:
Internal storage (USB storage) - Total space 8.92 GB
Internal storage - Total space 3.94 GB
it makes total of 12.86 GB
If I take in count trick with not multiplying Bytes with 1024 but with 1000, I come to 16 GB = 14.9 real GB (which tablet should show).
So, minimum of capacity tablet should report is 14.9 GB (which I think is a chip trick that shouldn't be used) but it shows 12.86 GB which is significantly less.
Where is the rest of the memory?
Where's the rest 3,14 GB (or at least 2.04 GB)?
You have to consider that there are some hidden mountpoints for the system. Maybe the following output of the df command clarifies something:
Filesystem Size Used Free Blksize
/dev 370M 64K 370M 4096
/configs 1M 44K 1M 2048
/mnt/asec 370M 0K 370M 4096
/mnt/obb 370M 0K 370M 4096
/system 377M 256M 121M 4096
/datapp 377M 122M 255M 4096
/data 3G 723M 3G 4096
/cache 503M 8M 495M 4096
/log 15M 13M 2M 4096
/mnt/sdcard 8G 2G 6G 4096
There is /mnt/secure/asec as well but I couldn't determine the size because I don't have root access.
When you use 8.92 GiB for 8G and 3.94 GiB for 3G, you're getting close to the 16 GB. (15551 MiB)
thank you
I see it's (probably) 16GB (ISO Giga, not computer Giga) but they locked a lot of it for system use.
Next thing I could find out is that it has dual core processor but one core is only for system update?
sony still should of gave us 16GB regardless how much goes towards the rom.
ross231 said:
sony still should of gave us 16GB regardless how much goes towards the rom.
Click to expand...
Click to collapse
Maybe. In general, the storage number always relates to the amount of actual physical storage is included in the device. User-accessible storage is a whole different deal and liable to change.
Even my iPhone, a claimed 16GB has only 13.6 (ISO) Gig of storage available, a big drop as well. Every system since OSes and applications started taking up non-trivial amounts of storage has reported the physical storage, not the user-available.
Being a naturally curious guy I decided to figure out why my KHDX with 64GB, but using a Safestrap ROM slot, is "running out of space".
Generally when that happens, I use "DiskUsage", an app in PlayStore by "Ivan Volosyuk", which I'd been using when my phone was an OG Droid, and this app was updated for KitKat and everything. I'm sure everybody had used it at some time. If you haven't... You should.
https://play.google.com/store/apps/details?id=com.google.android.diskusage
It's a storage visualizer, much like SequoiaView or WinDirStat on PC.
Any way, generally, when DiskUsage is on a phone, I should see
App Storage
Storage Card
/storage/sdcard0 (and perhaps sdcard1 as well)
[Root Required]
(That's the way my Droid Bionic is setup, running stock-based ROM and a Cyanogen Mod 10.2 in slot 1)
However, when the same app is on the HDX, running inside ROM slot 1... I get...
Storage Card
[Root Required]
No app storage, eh?
Also, the normally accurate progress bar where it reads all the directories and sizes? Jumped all over creation, counted up to like 312% and such crazy things. But eventually it told me that TOTAL storage I have on the 'storage card' is 6192MB with ZERO free space detected (eh?)
using "Root required" option lets you browse the directories with root permissions and yielded a bunch of interesting stuff under storage
/storage/emulated
/storage/emulated/0
/storage/emualted/0/Android/obb
/storage/emulated/legacy
/storage/emulated/legacy/Android/obb
None of these "emulated" stuff exists on my phone. (Droid Bionic has ROM, 8 GB "internal" SD, and I have a 32GB microSD in there too).
So, after all that blah blah blah... The question...
Can someone explain or link to article that explains how the storage is counted in the HDX?
How can there be no app stroage?
What is that "emulated" and "emulated/legacy"? (I 'll research that myself too)
And perhaps related to Hashcode's Safestrap HDX... Where is the rest of my 64GB?
You should issue a "df" command in a terminal (adb shell from pc, or from pc with JuiceSSH for example. Here is my output on a slot rom on my 16G kindle. You can see that i have 3G left on 11G for sdcard.
What is probably happening is your virtual /data partition (slot) which store downloaded apps runs out of space (i think your limited with safestrap when creating the slot, i did choose 2G for me).
Now most games should install theire game data on sdcard, else i guess you should be able to use some move to sd options in applications settings or with an app.
Filesystem Size Used Free Blksize
/dev 871M 48K 870M 4096
/dev 871M 48K 870M 4096
/mnt/secure 871M 0K 871M 4096
/mnt/secure 871M 0K 871M 4096
/mnt/asec 871M 0K 871M 4096
/mnt/asec 871M 0K 871M 4096
/mnt/obb 871M 0K 871M 4096
/mnt/obb 871M 0K 871M 4096
/datamedia 11G 8G 3G 4096
/ss 11G 8G 3G 4096
/system 1G 1009M 74M 4096
/system/fonts 79M 79M 0K 1048576
/cache 295M 9M 286M 4096
/data 2G 905M 1G 4096
/persist 31M 4M 27M 4096
/firmware 63M 18M 45M 16384
/persistbackup 31M 4M 27M 4096
/mnt/shell/emulated 11G 8G 3G 4096
/storage/emulated/legacy 11G 8G 3G 4096
/storage/emulated 871M 0K 871M 4096
/storage/emulated/0 11G 8G 3G 4096
/storage/emulated/0/Android/obb 11G 8G 3G 4096
/storage/emulated/legacy 11G 8G 3G 4096
/storage/emulated/legacy/Android/obb 11G 8G 3G 4096
Sent from my KFTHWI using xda app-developers app
i just got a Star/Ulefone n9002 mediatek based clone of a Samsung Galaxy Note 3. the phone is pretty nice... i'm liking it. specs on it are pretty good, but i am having an issue with the internal SD card. when i ordered it, it was suppose to come with an 8gb internal SD card. i got it, took it out of the box and checked, and the system specs said that it had a 16GB internal card. originally, i thought, "Bonus!!" but the more i thought about it, the more i realized that this is probably bogus or an issue with whatever rom is flashed on it. checking needrom.com there are 2 rom images out there for it and they both list the original specs for an 8gb internal card. when i started loading things on it, i suddenly started to get strange errors about running out of space. it didn't make much sense. anyway, i rooted it with mtk droid tools, installed the custom CWM, and what not, and started poking under the hood. fdisk is giving me errors and parted refuses to even work on it. (maybe i am running the wrong commands, but attached are outputs).
anyway, i already know there is an issue with the ROM cause MTK Droid tools reports that it has an mt6582 cpu even though the software on the phone reports and mt6589. all of the roms say it should be an mt6582 also. not a big deal in my opinion.
my question is this... is there anyway to non-destructively fix the partition table? i have read alot about editing the EBR files to change partition sizes, but there has got to be a better way. also, i'd like to truely verify the size of the built in storage without opening up the phone and reading the numbers off of the internal SD card.
should i just get the latest ROM off of needrom.com and flash it? i don't know if this would fix the partition table either.
here are the outputs:
fdisk output:
1|[email protected]_wet_v116_jb5:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 951232.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Command (m for help): v
v
Partition 2 does not end on cylinder boundary
Partition 2: sector 0 greater than maximum 16
Partition 3 does not end on cylinder boundary
Partition 3: sector 0 greater than maximum 16
Partition 4 does not end on cylinder boundary
Partition 4: sector 0 greater than maximum 16
Partition 5: sector 0 greater than maximum 16
Partition 6: sector 0 greater than maximum 16
Logical partition 5 not entirely in partition 1
Total allocated sectors 4290439170 greater than the maximum 15219712
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes
1 heads, 16 sectors/track, 951232 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1153 2432 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2433 3712 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5313 6080 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8129 97728 716800 83 Linux
/dev/block/mmcblk0p6 376001 64 2144476159+ 83 Linux
Command (m for help):
Click to expand...
Click to collapse
gdisk output:
[email protected]_wet_v116_jb5:/system/xbin # gdisk
gdisk
GPT fdisk (gdisk) version 0.8.4
Type device filename, or press to exit: /dev/block/mmcblk0
/dev/block/mmcblk0
EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55
Error reading logical partitions! List may be truncated!
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if
you don't want to convert your MBR partitions to GPT format!
***************************************************************
Command (? for help): v
v
No problems found. 13732797 free sectors (6.5 GiB) available in 4
segments, the largest of which is 13656031 (6.5 GiB) in size.
Click to expand...
Click to collapse
parted output:
1|[email protected]_wet_v116_jb5:/system/xbin # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) check
check
check
Error: Can't have a partition outside the disk!
(parted) print devices
print devices
print devices
Error: Can't have a partition outside the disk!
(parted) print all
print all
print all
Error: Can't have a partition outside the disk!
(parted)
Click to expand...
Click to collapse
/proc/mounts:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 rw,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
/proc/partitons
major minor #blocks name
7 0 1254 loop0
7 1 11451 loop1
253 0 524288 zram0
179 0 7609856 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 716800 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2097152 mmcblk0p7
179 8 4601856 mmcblk0p8
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 31166976 mmcblk1
179 97 31162880 mmcblk1p1
Click to expand...
Click to collapse
progress...
i take it by the deafening number of replys, no one has any idea whats up with my issue or any idea how to fix it. so i have been digging deeper myself and think i have come up with some solutions.
first of all, i was just planing on flashing one of the roms off of the NeedRom.com website, but i read a couple of posts on chinaphonearena.com and one in some german forum that listed a phone with my same baseband and ROM build, and when they flashed the new rom, it screwed up their touch screen. something about having an incompatible touch screen driver. i don't know if the person flashing the rom chose the correct rom, or incorrect rom, but it made me skidish to attempt this as a fix.
so i checked in on modifying the EBR files, which people have been doing on these mediatek phones for a while. i thought maybe one of mine was screwed up. i extracted the EBR1 and EBR2 file from my fine with MTKDroidTools and i pulled the files out of the rom update. i also took the scatter file generated by MTKDroidTools and the scatter file from the rom update. i compared them line for line. the EBR files are totally identical! as was the scatter file. address of where the partitions start and stop inside the phone are 100% the same. so flashing a new rom wouldn't have fixed the problem anyway.
i started googling around at the error that parted gives me: "Error: Can't have a partition outside the disk!" this is discussed elsewhere, but mostly on actual machines, not phones. there are some postings here on XDA, but none that address my specific issue. anyway, the ways it always suggests to fix it is to figure out which partition is oversized, used the sfdisk utility to dump the partiton table, fix it, and re-write the partition table to disk. simple enough, if you know what your partition table should look like.
back to fdisk, i reprint out a copy
1|[email protected]_wet_v116_jb5:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 951232.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Command (m for help): v
v
Partition 2 does not end on cylinder boundary
Partition 2: sector 0 greater than maximum 16
Partition 3 does not end on cylinder boundary
Partition 3: sector 0 greater than maximum 16
Partition 4 does not end on cylinder boundary
Partition 4: sector 0 greater than maximum 16
Partition 5: sector 0 greater than maximum 16
Partition 6: sector 0 greater than maximum 16
Logical partition 5 not entirely in partition 1
Total allocated sectors 4290439170 greater than the maximum 15219712
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes
1 heads, 16 sectors/track, 951232 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
/dev/block/mmcblk0p2 1153 2432 10240 83 Linux
/dev/block/mmcblk0p3 2433 3712 10240 83 Linux
/dev/block/mmcblk0p4 5313 6080 6144 83 Linux
/dev/block/mmcblk0p5 8129 97728 716800 83 Linux
/dev/block/mmcblk0p6 376001 64 2144476159+ 83 Linux
Click to expand...
Click to collapse
this does indeed tell me that the internal flash memory is about 8gb (Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes) but it is not obvious to me which partition is screwed up.
anyway, i'd love for someone that has an mtk6582 based phone with 8gb of internal storage to provide me with a dump of their partition table, then i could just restore it over mine, and it should fix the issue!... the command is simple...
adb shell
su
sfdisk -d /dev/sdc > PT.txt
Click to expand...
Click to collapse
from what i see (i may be wrong here) but these phones run with something like 2 partition tables... there is the one that is physically connected to the first 512 bytes of the SD card. then they have the EBR's which map out all of the EMMC partitons. so there is just one big partition seen from the outside, but through software, we can map that big partition in to smaller ones by knowing start and end addresses inside that big partition. i tell you, it is confusing.
i'm sure if i use the spflash_tool and format my phone and re-install a rom, it would fix the problem, but i am nervous about doing that because so many people have had issues putting rom's on this phone. they report that even when going back to their original backup the touch screen issues persist.
anyone have any comments? any ideas? any mbr backup they could share with me?
I believe you read my thread in chinese forum, I have one here too, because my touch is not working well since the rom upgrade.
Anyway, I'm almost sure you have like me a STAR Ulefone N9002 MTK6582 (1.3GHz) with 8Gb total memory.
AnTuTu 17500 values are 6582, 13000 are 6589T.
The original ROM have 1Gb RAM, 2Gb Internal Memory, and 8Mpx camera.
The ROM you have, and the MARCH Rom Update of Needrom, make the fake values, and the ram and internal memory are not correct. The camera is updated to 13Mpx too.
If you want, here you could read the procedure to edit the MBR by yourself.
Or you could flash the JAN rom of needrom.
I'm not sure about what cause my touch to get screwed, I guess I will never know, but I will keep flashing my phones...
At the moment, I'm waiting for a new touch for replace.
Cheers and good luck.
PMoto.
I'm running a SlimKat ROM on Sony Xperia Z Ultra. Officially the device has 16GB storage installed, but only 11.79GB are available to the user. I know that all the rest is reserved for the OS needs. May be the official Sony ROM really needs 3.5GB of space to function properly, but since SlimKat is a very compact ROM, I'm sure it doesn't need so much storage (am I right?).
So is there any way to make more storage available for the user needs and less for the OS? May be there are some ways to repartition the device memory.
When I tried to google the question, I learned that there are some tricks to make the device treat the external SD card as internal storage, but that's not what I'm looking for now
I believe the NAND (internal SSD) capacity is reported using the the binary system (base 2 i believe), so 16GB won't actually be 16GB, same as your 1TB HDD won't give you the full 1TB, because 1000GB isn't 1000GB, like 1MB isn't 1000KB, but 1024KB as an example. It's math. I have no idea how a typical SSD's capacity is counted though, but you can't "recover" those 3.5GB and have all 16GB to yourself. A part of the 3.5GB simply doesn't exist.
LordManhattan said:
I believe the NAND (internal SSD) capacity is reported using the the binary system (base 2 i believe), so 16GB won't actually be 16GB, same as your 1TB HDD won't give you the full 1TB, because 1000GB isn't 1000GB, like 1MB isn't 1000KB, but 1024KB as an example. It's math.
Click to expand...
Click to collapse
Yes, I know, but 16GB would be 14.9 "real" GB, not 11.79
netimen said:
Yes, I know, but 16GB would be 14.9 "real" GB, not 11.79
Click to expand...
Click to collapse
the storage isn't empty you know ...there is allot of files stored there other than your personal files
SÜPERUSER said:
the storage isn't empty you know ...there is allot of files stored there other than your personal files
Click to expand...
Click to collapse
Yes, I understand that. But does the system really need 3GB to store it's files? SlimKat is very compact, my /system partition is 500MB currently
netimen said:
Yes, I understand that. But does the system really need 3GB to store it's files? SlimKat is very compact, my /system partition is 500MB currently
Click to expand...
Click to collapse
if I select everything excluding /sbin, /sdcard and /storage I get 9.34GB
if i select everything excluding /sbin, /sdcard, /storage and /data I get 3.71GB
I am on slimkat rom with pimped kernel
netimen said:
Yes, I know, but 16GB would be 14.9 "real" GB, not 11.79
Click to expand...
Click to collapse
Sure, but the flashed size isn't the installed size. The ROM can be 200MB when downloaded, but it can easily be 1GB when installed. It's compressed like crazy. The stock ROM is even larger at what? 800MB? Installed, that'll be 2.5-3GB, easily. I backed up my GPe ROM (NAND) last week. It's around 3GB with all my apps, and I have (only) around 20 apps installed.
Just let this go now before you do some damage to your device.
Here is the mounted partitions in carbon only 2.2 GB for system, but there is 1.6 free. At the most I would think you could get back would be only a little over ~1 GB. not worth the risk I feel
Code:
[email protected]:~/dev/carbon> adb shell
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 904.7M 132.0K 904.5M 4096
/sys/fs/cgroup 904.7M 12.0K 904.6M 4096
/mnt/asec 904.7M 0.0K 904.7M 4096
/mnt/obb 904.7M 0.0K 904.7M 4096
/mnt/fuse 904.7M 0.0K 904.7M 4096
/tmp 904.7M 0.0K 904.7M 4096
/system 2.2G 657.6M 1.6G 4096
/cache 196.7M 5.8M 191.0M 4096
/data 11.8G 5.3G 6.5G 4096
/mnt/idd 7.5M 1.0M 6.5M 1024
/lta-label 15.7M 4.8M 10.9M 4096
/mnt/shell/emulated 11.8G 5.3G 6.5G 4096
/mnt/media_rw/sdcard1: Permission denied
/storage/sdcard1 29.5G 22.6G 6.9G 32768
1|[email protected]:/ $
I've cleaned caches, restarted phone, removed secure folder, moved all apps to SD card, ran app booster, and still, system data stays the same, at 25GB. Screenshot from DiskUsage shows the used space - internal memory is mislabeled as storage card. Screenshots from device care show other apps at 55G which can't be true - when I open that I see only small apps there.
output from `df -h`:
Code:
star2lte:/data/enc_user $ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 2.7G 1.6M 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
/dev/block/dm-0 4.1G 4.0G 119M 98% /
/dev/block/dm-1 622M 616M 5.8M 100% /odm
/dev/block/dm-2 618M 559M 58M 91% /vendor
tmpfs 2.7G 0 2.7G 0% /mnt/sde
/dev/block/sda23 45M 12K 45M 1% /omr
/dev/block/sda21 583M 12M 571M 3% /cache
/dev/block/sda3 16M 2.8M 13M 19% /efs
/dev/block/sdd1 1.8M 556K 1.3M 29% /cpefs
/dev/block/dm-3 53G 47G 4.9G 91% /data
/data/knox/secure_fs/enc_user 53G 47G 4.9G 91% /data/enc_user
/data/knox/secure_fs/enc_media 53G 47G 4.9G 91% /data/knox/secure_fs/enc_media
/data/knox/secure_fs/enc_media 53G 48G 4.9G 91% /mnt/shell/enc_emulated
/data/media 53G 48G 4.9G 91% /storage/emulated
/mnt/media_rw/6112-71F4 60G 49G 11G 83% /storage/6112-71F4
How can I clean up system data?
Android 10, stock, non-root.
Same problem here, 64 GB storage, around 20 GB for user data. How many space I free up less space I have. I don't want do a hard reset and reconfigure all authentication and bank apps.
Device Xiaomi Mi 9, Android 10, no root.