StorageInfo: Include screenshots for test

Mobile devices employ a sophisticated partitioning scheme to allocate internal storage for various system functions and user data. The system partition, a segregated segment of storage, is exclusively reserved for system files, operating system components, and pre-installed applications. This partition remains inaccessible to users and is shielded from direct manipulation or access through file manager applications.

#### Example:

Consider a mobile device with a total internal storage capacity of 64GB. Out of this capacity, the system partition may consume approximately 10-15% of the total storage, leaving the remaining space available for user data and applications. However, users may not have visibility into the exact allocation of space within the system partition, leading to discrepancies between reported storage sizes in Settings and file managers.

### 2. Reserved Space

Operating systems allocate a portion of internal storage space for essential system functions, including system updates, temporary files, cache data, and system logs. This reserved space acts as a buffer to facilitate seamless operation and ensure system stability under varying usage scenarios. However, this reserved space is not explicitly accounted for in the available storage space visible to users in file manager applications.

#### Example:

When a mobile device receives a system update, the operating system may temporarily utilize additional storage space to download and install the update files. This temporary storage consumption may not be reflected in the available storage space reported by file manager applications, leading to discrepancies in storage size display.

### 3. File System Overhead

File systems impose overhead for managing file and directory structures, storing metadata, and implementing journaling mechanisms to ensure data integrity. These overhead costs, while relatively minor, contribute to the utilization of storage space and may vary depending on the file system format used by the device.

#### Example:

In a file system such as FAT32 or NTFS, each file occupies a minimum allocation unit size, leading to potential wastage of storage space for small files. Additionally, metadata associated with each file, including file attributes and timestamps, consumes additional storage space. While these overhead costs are inherent to file system operations, they are not factored into the available storage space reported by file manager applications.

### 4. Flawed Calculation Methods

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:

Android's calculation of storage space consumed by system components exhibited inconsistencies. By creating a dummy 4GB file in a non-system directory, the system storage breakdown erroneously attributed the increased storage utilization to the Android OS, leading to inflated system storage figures.

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

<img src="/images/support-topics/incorrect-storage-info/Settings-Storage-Info-Before.png" alt="System storage info before test" width="200" height="400">

##### After Test

<img src="/images/support-topics/incorrect-storage-info/Settings-Storage-Info-After.png" alt="System storage info after 5gb file push test" width="200" height="400">

### 5. Unit of Measurement Discrepancy

Android's utilization of gibibytes (GiB) as a unit of measurement contrasts with smartphone manufacturers' use of gigabytes (GB) for advertising 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:

A mobile device advertised as having 64GB of storage capacity by the manufacturer may appear as approximately 59.6GB in the device settings due to the conversion from gibibytes to gigabytes. 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.

## Recommendations for Users