Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8909f7f6 authored by Florian Bausch's avatar Florian Bausch Committed by Weblate
Browse files

Translated using Weblate (Portuguese (Brazil)) 

Currently translated at 43.7% (14 of 32 strings)

Translation: /e/ support center/Pages/Support_Topics/Explain_Incorrect_Fresh_Install_Size_Of_Internal_Storage
Translate-URL: https://i18n.e.foundation/projects/e-support-center/pagessupport_topicsexplain_incorrect_fresh_install_size_of_internal_storage/pt_BR/
parent 10198846

htdocs/_i18n/pt_BR/pages/support_topics/explain_incorrect_fresh_install_size_of_internal_storage.md

+4 −4
Original line number Diff line number Diff line
@@ -22,7 +22,7 @@ Mobile devices allocate internal storage for various functions, including system 


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.



### 2. Flawed Calculation Methods

### 2. Métodos de cálculo falhos



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.
@@ -30,13 +30,13 @@ Android devices employ flawed methods for calculating storage space utilization 


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

**Resultados do teste de informações de armazenamento do sistema**



| Before Test (Clean Install) | After Test (5GB Dummy File) |

| ----------------------- | ------------------------------- |

| ![Android OS (Using GB)](/images/support-topics/incorrect-storage-info/Settings-Storage-Info-Before.png) | ![Other File Managers (Using GiB)](/images/support-topics/incorrect-storage-info/Settings-Storage-Info-After.png) |



### 3. Unit of Measurement Discrepancy

### 3. Discrepância nas unidades de medida



A capacidade de armazenamento costuma ser medida usando diferentes sistemas de contagem. A maioria dos dispositivos e sistemas, como o Windows e o Linux, utiliza um método chamado notação binária (base 2). Nesse sistema, 1 GB é calculado como 1.024 × 1.024 × 1.024 bytes. No entanto, para simplificar e evitar confusão, alguns aplicativos ou utilitários podem exibir o espaço de armazenamento usando um sistema diferente, chamado notação decimal (base 10). Na base 10, 1 GB equivale a 1.000 × 1.000 × 1.000 bytes.
@@ -60,7 +60,7 @@ Essa discrepância entre as capacidades de armazenamento anunciadas e as relatad 
| ![Android OS (Using GB)](/images/support-topics/incorrect-storage-info/File_Manager_GB_1.png) | ![Other File Managers (Using GiB)](/images/support-topics/incorrect-storage-info/File_Manager_GiB_1.png) |

| ![Android OS (Using GB)](/images/support-topics/incorrect-storage-info/File_Manager_GB_2_Files.png) | ![Other File Managers (Using GiB)](/images/support-topics/incorrect-storage-info/File_Manager_GiB_2.png) |



## Recommendations for Users

## Recomendações para os usuários



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