# Understanding Discrepancies in device storage utilization
## Introduction
In modern mobile devices, understanding and managing internal storage space is crucial for efficient device usage. However, users often encounter discrepancies in the reported size of internal storage between the device's system settings and file manager applications downloaded from app stores. This document aims to elucidate the reasons behind such inconsistencies and provide users with a clearer understanding of the issue.
@@ -20,7 +18,7 @@ Mobile devices allocate internal storage for various functions, including system
-**A/B Partitioning Devices**: Some newer Android devices utilize A/B partitioning, which involves having two separate system partitions, along with various other partitions, known as Slot A and Slot B. This setup allows seamless updates without interrupting the user experience. However, due to this nature, devices with A/B partitioning may allocate almost twice the amount of space compared to non A/B devices.
### Example:
**Example**:
Consider a mobile device with a total storage capacity of 64GB. The system partition may consume 10-15%, leaving the rest for user data. However, users may not see this breakdown, leading to discrepancies between reported sizes.
@@ -28,18 +26,15 @@ Consider a mobile device with a total storage capacity of 64GB. The system parti
Android devices employ flawed methods for calculating storage space utilization by system components, leading to discrepancies in reported storage sizes. These discrepancies may arise from the misattribution of storage space to system components, including erroneous categorization of user-generated files as system files.
#### Example:
**Example**:
Android's calculation of storage space consumed by system components exhibited inconsistencies. A test scenario was devised where a dummy 5GB file was created and pushed to the directory /data/media/0, a non-system directory representing internal storage. Despite the file's explicit location outside the system partition, the system storage breakdown erroneously attributed the increased storage utilization to the Android OS System, resulting in inflated system storage figures. This shows inherent flaws in Android's storage space calculation logic, where user-generated files outside the system directory are inaccurately categorized as system files, leading to misleading storage utilization metrics.
#### System storage info test results
##### Before Test
<imgsrc="/images/support-topics/incorrect-storage-info/Settings-Storage-Info-Before.png"alt="System storage info before test"width="200"height="400">
**System storage info test results**
##### After Test
<imgsrc="/images/support-topics/incorrect-storage-info/Settings-Storage-Info-After.png"alt="System storage info after 5gb file push test"width="200"height="400">
| Before Test (Clean Install) | After Test (5GB Dummy File) |
@@ -51,7 +46,7 @@ Conversely, in base 10 notation, storage units are named using metric prefixes s
Android's utilization of gigabytes (GB) as a unit of measurement contrasts with some File Manager apps that utilize use of gibibytes (GiB) for showing storage capacities. This discrepancy in measurement units contributes to confusion among users and may lead to an overestimation of the space occupied by the Android OS and other system files.
#### Example:
**Example**:
For instance, in a mobile device with a storage capacity of 64GB:
@@ -60,6 +55,11 @@ For instance, in a mobile device with a storage capacity of 64GB:
This discrepancy in advertised versus reported storage capacities may lead users to believe that the Android OS consumes a larger portion of storage space than it actually does.
| Android OS (Using Gigabytes) | Other File Managers (Using Gibibytes) |
-**Consider System Limitations**: Recognize that the total storage capacity reported in Settings may be higher than the usable storage space visible in file manager applications due to system partitioning, reserved space, and file system overhead.
