Add more info for Reasons

## Reasons for Discrepancies

Several factors contribute to the disparities in device storage size between Settings and file manager applications:

Several factors contribute to the disparities in internal storage size between Settings and file manager applications:

1. **System Partitioning**: Mobile devices allocate a portion of internal storage for system files, operating system components, and pre-installed applications. This portion, known as the system partition, is not accessible to users and is excluded from the available storage space reported in file manager applications.

### 1. System Partitioning

2. **Reserved Space**: Operating systems often reserve a certain amount of internal storage space for system updates, temporary files, cache, and other system-related tasks. This reserved space, while necessary for the smooth operation of the device, is not included in the available storage space visible to users in file managers.

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.

3. **File System Overhead**: File systems, such as FAT32, NTFS, and exFAT, impose overhead for file and directory structures, metadata, and journaling. This overhead consumes a small percentage of the total storage capacity but is not factored into the available storage space reported by 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.

4. **Flawed Calculation Methods**: Android's method of calculating storage space taken up by system components can be flawed, leading to inflated system storage utilization. Dummy user-generated files can also contribute to the misrepresentation of system storage utilization.

### 2. Reserved Space

5. **Unit of Measurement Discrepancy**: Android measures storage in gibibytes (GiB), while smartphone manufacturers advertise storage capacities in gigabytes (GB), leading to confusion and potential overestimation of the space occupied by the Android OS and other files.

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.

## Recommendations for Users

#### 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.

Understanding the reasons behind discrepancies in internal storage size display can help users make informed decisions about managing their device storage:

#### 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.

### 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

- **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.