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

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

Translated using Weblate (Portuguese (Brazil)) 

Currently translated at 9.3% (3 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 7d1a2f25

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

+3 −3
Original line number Diff line number Diff line
@@ -18,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**:

**Exemplo**:



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.
@@ -26,7 +26,7 @@ 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**:

**Exemplo**:



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.
@@ -46,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**:

**Exemplo**:



For instance, in a mobile device with a storage capacity of 64GB: