I have seen that the space occupied by 'System' is different for different storage sizes of the same device.
My Samsung Galaxy S22 Ultra shows space occupied by system as over 50 GB. Mine is the 512 GB variant (Snapdragon). While I don't remember how much it was out of the box, but it has been somewhere in that region throughout.
But the space occupied by S22U 256 GB variant is much lower, at around 30 GB for the same region.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone explain why this is different?
In this context, Samsung's OneUI is probably the most bloated version of Android. Even though there is some explanation (about 7% conversion loss) as to why System on Samsung devices shows a very high use of storage space (it apparently includes the 7% conversion loss), it still doesn't explain why the System size is substantially different between different storage variants of the same device.
References:
Not True- 60 GB OS Occupy on the Samsung Galaxy S23 Ultra
You may already know about 60 GB OS Occupy on the Samsung Galaxy S23 Ultra from popular News Sites. But that is not accurately correct. The claim that
www.androidinfotech.com
One UI 5.1 bloatware does NOT take up 60GB storage on the Galaxy S23 series
It turns out One UI 5.1 bloatware does not take up 60GB system storage on the Galaxy S23 phones. Here's an explanation.
www.androidauthority.com
download the ROM from samfw or samloader, extract it and see what is inside. I bet even when converted into raw partition images the system is around 4 GB only. therefore what you mean with System is actually userdata or something different.
aIecxs said:
download the ROM from samfw or samloader, extract it and see what is inside. I bet even when converted into raw partition images the system is around 4 GB only. therefore what you mean with System is actually userdata or something different.
Click to expand...
Click to collapse
User files, app data, etc. are shown separately.
check the output of df what is the total size of system partition. check space occupied on userdata partition.
Code:
df -h /
df -h /data
aIecxs said:
check the output of df what is the total size of system partition. check space occupied on userdata partition.
Code:
df -h /
df -h /data
Click to expand...
Click to collapse
My device isn't rooted. Not sure if these terminal commands would work.
Doing a bit of math, here are the numbers:
The 7% computational difference means:
For 512 GB variant, about 36 GB is included in the System classification, which means the OS itself is only about 14 GB, which is along expected lines.
For 256 GB variant, 7% is about 18 GB, so if Storage Analysis shows System as occupying about 32 GB, this will confirm the OS itself is only about 14 GB, which is same as above. Someone with a 256 GB variant would be able to confirm this.
Likewise, the 128 GB variant should show System as occupying 23 GB and 1 TB variant should show System as occupying 86 GB.
Hopefully people with these storage variants can confirm this.
Samsung should ideally provide more details (breakdown) on what makes up the space shown against System as OS Files and Others.
the df cmd doesn't need root. you could easily figured out from any terminal emulator.
I checked this ROM and the super partition is 12G only.
https://samfw.com/firmware/SM-S908U/TMB/S908USQU2CWAI
Doing a bit of math, here are the numbers:
12G - 9.3G = 2.6G reserved
the system partition is only 6.1G (haven't checked f2fs file system, it's less). so obviously what you see as System is actually stored on userdata partition. I assume the ROM is the same for all variants of storage 128/256/512G, so the system partition is therefore also the same size.
Code:
[email protected]:/mnt/c/Android/Backup/SM-S908U/AP_S908USQU2CWAI_S908USQU2CWAI_MQB61793398_REV00_user_low_ship_MULTI_CERT_meta_OS13/super$ ls -lh
total 9.3G
-rwxrwxrwx 1 ubuntu ubuntu 21M Feb 13 21:21 odm.img
-rwxrwxrwx 1 ubuntu ubuntu 1.1G Feb 13 21:21 product.img
-rwxrwxrwx 1 ubuntu ubuntu 6.1G Feb 13 21:13 system.img
-rwxrwxrwx 1 ubuntu ubuntu 236M Feb 13 21:21 system_ext.img
-rwxrwxrwx 1 ubuntu ubuntu 1.8G Feb 13 21:18 vendor.img
-rwxrwxrwx 1 ubuntu ubuntu 53M Feb 13 20:58 vendor_dlkm.img
btw the 7 % "loss" isn't about occupied space at all, it's simply the "difference" between GB <=> GiB (but it's the same size only different unit)
1000^3 (GB) Gigabyte != 1024^3 (GiB) Gibibyte
https://www.wikipedia.org/wiki/Gigabyte
In other words your phone comes with 512 GB = 476.8 GiB storage. and that marketing naming is same for each and every storage we buy, be it pendrive, MicroSD card or HDD disk drive, not a Samsung thing...
aIecxs said:
I assume the ROM is the same for all variants of storage 128/256/512G, so the system partition is therefore also the same size.
Click to expand...
Click to collapse
That's true. This question arose because the built-in storage analyzer shows different values for different storage variants of the same device (same region).
aIecxs said:
btw the 7 % "loss" isn't about occupied space at all, it's simply the "difference" between GB <=> GiB (but it's the same size only different unit)
Click to expand...
Click to collapse
Yes, it's just a question of units.
The value shown against System is basically the unaccounted difference, which is a mathematical computation of the total storage size minus the sum of all other allocations (classifications).
Okay, think I got it. I had to read whole thread including links again twice...
so what they claim is basically
- Samsung is mixing up different units GB - GiB
- System is not even sum of existing files, but
- System is just calculated by subtracting all the non-system files (rest)
or in other words, the storage app is lying. whoever has coded this.
still I think 20 G is too much compared to 6 G system partition, maybe that is dalvik ART cache of extracted system apks (and their respective apps data) counted all together.
someone with rooted device should count all system files on userdata partition to clarify. the tool already comes with toybox du
@TheMystic Find attached the partition table of the S22U taken from the PIT file. All partitions except /userdata are summarized as "Android OS". The /userdata starts at block 3.574.272 and ends with the last free adress block. With a block size of 4K /userdata starts at 14.640.218.112 byte (13,6GiB, which is the occupied storage by Android OS)
TheMystic said:
References:
Not True- 60 GB OS Occupy on the Samsung Galaxy S23 Ultra
You may already know about 60 GB OS Occupy on the Samsung Galaxy S23 Ultra from popular News Sites. But that is not accurately correct. The claim that
www.androidinfotech.com
One UI 5.1 bloatware does NOT take up 60GB storage on the Galaxy S23 series
It turns out One UI 5.1 bloatware does not take up 60GB system storage on the Galaxy S23 phones. Here's an explanation.
www.androidauthority.com
Click to expand...
Click to collapse
Taken from 2nd URL:
You always lose about 7% of storage marketed by manufacturers due to conversion losses.
Samsung and some other OEMs choose to hide lost space under the system storage.
Click to expand...
Click to collapse
That's not correct. You can't loose storage due to conversion. If someone runs 1 mile and another one 1,609 km then nobody runs more than the other. Loss of storage would mean 512GB are converted into 476,84GiB and then turned into 476,86GB. That would be indeed a real loss but it's incorrect.
There's also no lost space. The first 256 and the last 34 blocks (512 byte) are reserved for the GPT. Then your bootloader begins at block 256 and the last partition has to end at (last block - 34). Only the single partitions have a rest of unused space at the end. But that's a few kb and quite normal.
The most informations inside the 1st link are nonsense...
Starting with this
1,073,741,824
Click to expand...
Click to collapse
Sorry, that's not a number when using more than one comma.
In binary, 1GB equals 1,073,741,824 bytes, approximately 238.4GB in decimal units for a 256 GB
Click to expand...
Click to collapse
Awesome!! The official binary unit for GB is GiB. Then 256GB are 238,4GiB (<= and this is the binary and not the decimal unit!!).
From the mentioned arstechnica.com page:
Several users report the phone uses around 60GB for the system partition right out of the box.
Click to expand...
Click to collapse
From that point I refused to read any further.
How can a partition on a physical storage become bigger without changing the size of any other partition?
Or how does the stored data on a partition effects the entire amount of the available storage? When I create a 10GB partition on a 100GB physical storage I've a second one of 90GB. No matter what I stored on the 10GB the other is still 90GB. So, the size of /system is always the same!
Back to the 1st link:
The amount of storage space used by the Android system on the Galaxy S23 series is about 20 GB, not 60 GB, as previously reported. This is still a lot of storage, but not as much as reported in the system settings. The additional storage is mainly due to pre-installed apps, including core Google system apps replicated by Samsung. However, it is possible to uninstall most third-party pre-installed apps.
Click to expand...
Click to collapse
I love this guy! Pre-installed apps are called system apps (mostly) because their APK is saved on a system partition. Since those partitions are r/o we can't uninstall them. But if we could, it won't turn any byte on your device into an usuable for you. It's still a system partition mounted r/o and already summarized as Android OS in your storage overview.
Next thing is that neither system apps nor any bloatware (however, who should say an app is bloatware? Should Android decide it on its own "Oh yeah, this app is definitely bloatware! Categorize it as "System" storage, please") could occupy storage as "System". On /data partition it's determinated that the paths ~/app, ~/data and ~/user_de are the OS' app directories. All entries are summarized as "Apps" and that's it.
Additionally, available storage space and updates to the Android operating system can also impact the size of the Android OS on the Galaxy S23 Ultra.
Click to expand...
Click to collapse
No, they can't. If they are stored on your device, then it will be on /cache. Since Samsung is still using A-only partitioning scheme an OTA-update requires to be installed from recovery. But you can't access /data from your stock recovery and it wouldn't make any sense to store the update on it.
alecxs said:
maybe that is dalvik ART cache of extracted system apks
Click to expand...
Click to collapse
Those files are max. 1GB. Only system apps without any updates need /data/dalvik-cache/. The updated ones store their APKs and the odexed Java code in /data/app. Furthermore the libraries and some other storage occupying stuff from the APKs are not part of the dalvik-cache.
WoKoschekk said:
You can't loose storage due to conversion.
Click to expand...
Click to collapse
That's true. The issue is they have used GB and GiB inconsistently.
Also, what is reported under 'System' is just a balancing figure, i.e. total storage minus sum of all other classifications.
The storage used by 'System' does vary for different storage variants of the same device model, but that difference is due to unit conversion. And where the system file manager isn't able to classify a particular file properly, it tends to include them under 'System', which causes more variation. I wonder why they even have a dedicated classification called 'Other files'.
Ideally, they should have a breakdown for 'System' to show the storage occupied by the OS (which should be identical for all storage variants of the same device model), and space occupied by System Files/ Data.
Anything else should go under 'Other files' and the Storage Analyser should list these files by size/ location. There is plenty of scope for improvement in how this tool displays information.
TheMystic said:
And where the system file manager isn't able to classify a particular file properly, it tends to include them under 'System', which causes more variation
Click to expand...
Click to collapse
No, there are fixed rules for classification that are stated in the AOSP.
TheMystic said:
Ideally, they should have a breakdown for 'System' to show the storage occupied by the OS
Click to expand...
Click to collapse
See attached file, infos are taken from the firmware.
TheMystic said:
The storage used by 'System' does vary for different storage variants of the same device model, but that difference is due to unit conversion.
Click to expand...
Click to collapse
There is no marketing issue or sth similar and there is no conversion issue. If you have 40GB in System then there is 40GB occupied by OS and system related files. No matter if GB or GiB. Occupied is occupied.
Edit: The attached pit file is valid for every model
WoKoschekk said:
No, there are fixed rules for classification that are stated in the AOSP.
Click to expand...
Click to collapse
Then Samsung doesn't seem to be following it properly.
WoKoschekk said:
See attached file, infos are taken from the firmware.
Click to expand...
Click to collapse
So the OS itself is 13.63 GB?
WoKoschekk said:
There is no marketing issue or sth similar and there is no conversion issue. If you have 40GB in System then there is 40GB occupied by OS and system related files. No matter if GB or GiB. Occupied is occupied.
Click to expand...
Click to collapse
Check this out:
[SOLVED] Difference in System Storage in March update
The allocation of storage between System and 'Other files' has changed after the Mar'23 update. Before the update, System was occupying 50.40 GB data. It was always this number for almost a year now (since the phone launched). But after the...
forum.xda-developers.com
TheMystic said:
Check this out:
Click to expand...
Click to collapse
I checked this out. But where do I find the proof for loss of storage due to conversion? Where is the proof for different occupied storage by system on all the different variants? All I can see is a single statement refering to this thread:
TheMystic said:
Also, the value of System will be different for devices with different storage sizes, even if it they are identical in all other aspects and are running on the same build of the OS.
Click to expand...
Click to collapse
TheMystic said:
So the OS itself is 13.63 GB?
Click to expand...
Click to collapse
Yes
WoKoschekk said:
where do I find the proof for loss of storage due to conversion?
Click to expand...
Click to collapse
There is no loss as such, but just that the space occupied by 'System' as shown by the built-in tool is a lot more than the actual space used by the OS and System Files.
WoKoschekk said:
Where is the proof for different occupied storage by system on all the different variants?
Click to expand...
Click to collapse
I don't have proof to show you now. You may find it on the internet. But it is a fact. The space occupied by 'System' as shown by the built-in tool is indeed significantly different for different storage variants of the exact same device. The reasons have been mentioned in the OP and the comments section.
TheMystic said:
There is no loss as such, but just that the space occupied by 'System' as shown by the built-in tool is a lot more than the actual space used by the OS and System Files.
Click to expand...
Click to collapse
How do you know that?
TheMystic said:
But it is a fact.
Click to expand...
Click to collapse
Because you can find it online...? Mmh... A detailed listing of those files would be helpful. But only a comparison of devices that are running since weeks/months says nothing.
WoKoschekk said:
How do you know that?
Click to expand...
Click to collapse
I have the details for my device (see attachments). As you would see, space occupied by 'System' has remained constant at 50.4 GB over the last 1 year of several updates. As you said, the OS is only about 14 GB. Which means the rest is basically difference in units used.
I have confirmed the different values reported between different storage variants of the exact same device. I don't have screenshots to show you now, but this is indeed true. The explanation for the difference is provided in comment #5.
WoKoschekk said:
A detailed listing of those files would be helpful.
Click to expand...
Click to collapse
The built-in tool doesn't provide a breakup for this value. But as mentioned in comment #5, the excess is mostly due to conversion of units.
WoKoschekk said:
If you have 40GB in System then there is 40GB occupied by OS and system related files. No matter if GB or GiB. Occupied is occupied.
Click to expand...
Click to collapse
Nope. That's why I wrote I had to read it twice
Related
I have a problem after a failed OTA update to Lollipop. I now have a large amount of storage missing. See the attached screenshots below. Basically my Moto G thinks:
Internal storage = 5.52 GB
Apps usage = 2.85 GB
Other misc usage = 0.20 GB
Available space = 0.63 GB
That means there is 1.8 GB missing!
I read a suggestion in another thread on a different device that I should use the DiskUsage app to get a better readout on where the data is stored. I attached that screenshot as well. It picks up a massive 1.9 GB for "System Data". That seems too large to my untrained eye. And this sort of disparity was not there before the failed OTA update. This seems to be on the regular storage (/sdcard0/ or /emulated/0/) and not in the true system root (/). Please help me figure out how to clean this up. I can't identify any culprits in the folders /sdcard0/Android/, /sdcard0/.mmsyscache/, /sdcard0/.temp or any other such place.
Any idea what this is
try to redo ota update and make sure to be succefull
ahmedteling said:
try to redo ota update and make sure to be succefull
Click to expand...
Click to collapse
That is not easy! I have a bootloader-unlocked and rooted XT1045. To complete OTA update I need to either flash stock firmware or upgrade to custom Lollipop ROM. Neither of which I have time to sort out now...
This reasonable coming from files in the root folders. That calculator do not process in those folders like /data /recovery /system...
If you have root it will be easy install Clean Master and let root access it will scan and clean your device. Very helpful.
Otherwise, only wipe internally OR looking for those locations as /data (all folders inside) /recovery (all folders)
So that your choice
Summary
Flashed Successfully: http://download.cyanogenmod.org/?device=falcon
Failed Due to Insufficient System Partition Size: http://forum.xda-developers.com/android/software/tk-gapps-t3116347 , the stock one
Please help to resize the system partition, I have 16GB Model, userdata or simply /data has size 12.7G which is not in use and free. Please help me to take some storage sapce from /data and to reallocate it to /system
I will be veryyyyyyy grateful.
http://screencast.com/t/oQqjFfYL
http://screencast.com/t/D5kVQOQl
I have already done this kind of thing in GooGle Nexus 3 Which is a Samsung Device and Uses PIT Partition Layout with Odin. I couldn't find any helpul resources for Moto G.
Bla Bla Bla Bla
I am facing an issue of smaller /System partition. While today's newer devices often come with 1.5GB (or more) of storage in the system partition, Moto G 1st Gen is more than a year old have 1GB or less of system storage available.
This, coupled with the fact that Google's applications have doubled in size in the past 18 months, means that your device may not be able to accommodate our larger GApps packages.
I want to answer some asumption
1) I am seriously not interested in link2sd or whatever.
2) I am doing this for learning purpose as well as obviously to ease my experience with this cell
3) Any help is much appreciated. Thank You in Advance.
Hello, I have this phone (8gb) since August and never noticed how much storage I have until now because it started notifying me storage was full. Well, it says total space is 4,53gb and without /system 3,60. So my question is, where is the 4gb of storage that I don't see? I was hoping it was occupied by /system but it is not. We're talking about a half of the storage and it's unbelievable that I cannot use at least 5 of the 8 I've payed for.
Any help would be very appreciated!
4.53 gb is your /data partition(user apps and data are stored here), other space is used in /system partition where all system files are located.
Is there a way to resize the partitions?
isavoro said:
Is there a way to resize the partitions?
Click to expand...
Click to collapse
it was possible to resize partitions in many phones and there are also apps available on playstore for it. but you should reset it to default before flashing any rom. :/
And do you think reducing /system may be a problem?
isavoro said:
And do you think reducing /system may be a problem?
Click to expand...
Click to collapse
when I was using stock, my system partition was filled by 1.5gb from 2.19gb. there is still some space there but you shouldn't reduce it because it will get filled over time with app updates. and there will be problem with ota updates if you resize it.
Ok, I have two Devices a t959 and a t959v. I have brought them both up to android 4.x.x with the appropriate files for the device. Somehow the T959 repartitioned the amount of system RAM from 500Mb to 1.5Gb while the t959v is still at 500mb. On the t959 I flashed to stock, using the Samsung Vibrant Root tools. (T959UVJFD)
then the update.zip recovery from 03.11.2102. then to cm-7.2.0-vibrantmtd and then to Xperia Vibrantmtd 4.2.2. I didn't notice the repartition until I ran out of space installing the same apps that were on the t959 and then compared the two phones under settings/apps. the t959v says 410Mb used and 117Mb free. the t959 says 373mb used and a whopping 1.1Gb free.
I looked at the log for the Xperia update and came across this: "Creating file system with parameters: Size: 1589624832 This would indicate that the partitioning happened during that update.
My upgrade path on the t959v was Oneclick Stock restore, then bhundven-blastoff-v2.5. then CM 11-20140908-UNOFFICIAL-galaxys4gmtd.
I didn't see anything similar during the update in the t959v.
So my dumb question is: Is there a way to have a similar memory partition on the t959v?
It seems to be that having the larger system partition goes a long way to making the phone really useable since after about 9 apps the normal system partition fills up. Is there a downside to having the larger system partition?
thewizardofahhs said:
Ok, I have two Devices a t959 and a t959v. I have brought them both up to android 4.x.x with the appropriate files for the device. Somehow the T959 repartitioned the amount of system RAM from 500Mb to 1.5Gb while the t959v is still at 500mb. On the t959 I flashed to stock, using the Samsung Vibrant Root tools. (T959UVJFD)
then the update.zip recovery from 03.11.2102. then to cm-7.2.0-vibrantmtd and then to Xperia Vibrantmtd 4.2.2. I didn't notice the repartition until I ran out of space installing the same apps that were on the t959 and then compared the two phones under settings/apps. the t959v says 410Mb used and 117Mb free. the t959 says 373mb used and a whopping 1.1Gb free.
I looked at the log for the Xperia update and came across this: "Creating file system with parameters: Size: 1589624832 This would indicate that the partitioning happened during that update.
My upgrade path on the t959v was Oneclick Stock restore, then bhundven-blastoff-v2.5. then CM 11-20140908-UNOFFICIAL-galaxys4gmtd.
I didn't see anything similar during the update in the t959v.
So my dumb question is: Is there a way to have a similar memory partition on the t959v?
It seems to be that having the larger system partition goes a long way to making the phone really useable since after about 9 apps the normal system partition fills up. Is there a downside to having the larger system partition?
Click to expand...
Click to collapse
First off, welcome to the forums!
By "system RAM", I'm assuming that you mean data storage for apps. There are typically three main partition to worry about: the system partition which contains all the preinstalled apps and the OS (Android), the data partition which stores all user installed apps and data, and the sdcard partition (optional) which stores music, videos, pictures etc. The RAM is used by the phone as a place to hold the data that is currently being used.
The TL,DR version is this: The T959 has 16gb of storage, the T959V has only 1GB. Read on for more info...
One of the key differences (to the end user) of the T959 and the T959V is that the T959 has an internal SD card while the T959V does not. So for the T959, there is 16GB of space, some of which is used for the data, some for the system, and the rest for the sdcard partition. On the other hand, the T959V just has a larger oneNand partition than the T959. On the T959, it stores the recovery, boot, and efs partitions (which are not really important for the end user, just that they work ) So on the T959V, it has a larger one (about 1GB) that stores the data and system partition in addition to the recovery, boot, etc partitions. The sdcard partition is used when you insert a microSD card into the phone. On the T959, when you insert an microSD card it is used as yet another partition that the T959V doesn't have.
Note that this is a bit of a simplification.
It is possible to have more space on the data partition to install apps, but then you have to move the data partition to the microSD card. This is slower but definitely possible.
Hope this helps.
This X3 new device with android 10, have Super partition and eat 2x system storage. Anyone can explain this function? is save for deleted? Is custom rom also read this super partition?
because i'm new with this case, and my old poco f1 did't have super partition
I didn't fully understand it either, but it's like having a nested partition table, so you have this 8gb physical partition (super) and inside you will have 3 logical partitions (system,product,vendor) that are free to be resized if needed.
DP FH said:
I didn't fully understand it either, but it's like having a nested partition table, so you have this 8gb physical partition (super) and inside you will have 3 logical partitions (system,product,vendor) that are free to be resized if needed.
Click to expand...
Click to collapse
Hello!. can the 3 logical partitions (from super) be resized to make them smaller? im using crdroid (a11), oss, latest twrp and super is already rw-able.
Everything is possible, good luck figuring out how