Talk:EMUI

EROFS - "Extendable" or "Enhanced"

I just added a link from this article to the EROFS article. But I noticed that whereas, here, we define the acronym as, "Extendable Read-Only File System", the EROFS article calls it "Enhanced Read-Only File System".

It is true that the cited article (ref 17, "EMUI 9.1 Official Now: What’s New, Supported Huawei devices list, and Download") does define the acronym as "Enhanced Read-Only File System" and that the two different 'decodes' for it are about as easily found as each other on the web - of the first four links found by a Bing search on "EROFS" which give an expansion, two define it as "Enhanced ...",

"Enhanced Read-Only File System - EROFS" at infradead.org/, and

"EROFS: A Compression-friendly Readonly File System for Resource-scarce Devices" at usenix.org

and two as "Extendable ..."

"EROFS Vs Squashfs – Whats The Difference? File Systems Comparison" at gigxp.com/, and

"Huawei brings its EROFS file system, GPU Turbo 3.0 to more phones" at gsmarena.com

However, since the second reference, above, is the paper describing the interface by its designers, I would say that they probably should have the final say about the name of their own work. In addition, the Linux code in Git hub which implements EROFS refers to it by the same name as it's inventors' paper.

I shall therefore change the name in this article to comply and add their paper as a reference. Hedles (talk) —Preceding undated comment added 12:25, 30 May 2020 (UTC)

GSMArena EMUI 14.2, is not HARMONYOS NEXT, and has AOSP 12 (Block the Russian editor, 188.65.244.223 for vandalism)

If I see more vandalism of this page, I will need to place anti-vandalism Wikipedia protocols on EMUI https://www.gsmarena.com/huawei_mate_x6-review-2781.php 84.9.236.94 (talk) 20:01, 11 January 2025 (UTC)

Remove the EMUI 14.2 (HarmonyOS NEXT) from Latest Release

This detail is incorrect and can be left as 14.2 or 15, or at best remove "Latest Release" from the infobox of EMUI 84.9.236.94 (talk) 08:08, 13 January 2025 (UTC)

 Not done: The page's protection level has changed since this request was placed. You should now be able to edit the page yourself. If you still seem to be unable to, please reopen the request with further details. Capybara Fan (talk) 16:39, 28 March 2025 (UTC)

Sorry, I was confused by the template below this. Was your comment supposed to be an edit request? If so, my reply still applies. If not, I apologize for the confusion. Capybara Fan (talk) 17:01, 28 March 2025 (UTC)

Request for Page Protection

Semi protection for EMUI 87.74.139.111 (talk) 09:07, 28 March 2025 (UTC)

Is this a request to have the page be semi-protected? The right venue for that would be WP:RPPI. I've also changed this section's title, because having a template there probably isn't good.

Capybara Fan (talk) 18:07, 28 March 2025 (UTC)

Unsourced OR: "OpenHarmony X.Y (L3-L5) Dual Frame / microkernel" in the version-history table

The parenthetical "OpenHarmony X.Y (L3-L5) [Dual Frame] [microkernel]" labels on the EMUI 12–15 rows are unsourced original research and should be removed or rewritten:

• No such classification exists. OpenHarmony's own documentation (OpenHarmony-Overview.md; the 3.0 Product Compatibility Specification) defines only three system types — mini/small/standard by RAM — and never uses "L3", "L4" or "L5". The six-tier "L0–L5" scheme traces to a May 2021 Weibo post relayed by IT之家 as a leak (博主爆料), not to any Huawei/OpenHarmony taxonomy.
• WP:CIRCULAR. A MediaWiki insource: search returns the string "L3-L5 Dual Frame" in exactly one article — this one. Every external site carrying the version-specific strings (HandWiki, Wikiwand, BetaWiki, Fandom) is a mirror of us. The strings were added on 2024-03-20 (rev. 1214651332) by an anonymous IP with a blank edit summary and no source.
• Factually off. "OpenHarmony 2.1.0" is not a real release (official line: 2.0 Canary → 2.2 → 3.0). The four version numbers are uncited and two contradict our own HarmonyOS version history table. "microkernel" is wrong for EMUI 12, whose HarmonyOS 2 phones ran a Linux+AOSP stack; a microkernel OS shipped only with HarmonyOS 5/NEXT (2024).

Per WP:BURDEN I'll remove the uncited tokens, keeping the sourced Android/AOSP base and the HarmonyOS pairing. Sources welcome if anyone has a Huawei/RS statement of these specific L-levels or version numbers. MintGekota (talk) 15:23, 4 July 2026 (UTC)

EMUI 12–15: "based on HarmonyOS" corrected to sourced "shares features with"

The software column described EMUI 12–15 as "Based on HarmonyOS X", but this is unsourced editorial synthesis. Reliable sources describe EMUI as an Android/AOSP-based overlay, and HarmonyOS as the same-cycle China-market sibling that EMUI shares features with — not a codebase it is built on. Notably the source already cited for EMUI 12 (Android Authority) says the UI is "inspired by Harmony OS 2.0", not "based on" it; GSMArena states "EMUI 13 contains Android 12" and lists "EMUI 13.1 (Europe) / HarmonyOS 3.1 (China)" as parallel builds; IT之家 describes EMUI 15 as "AOSP 12 with Harmony OS 4.3". I've corrected each cell to "Android Y (AOSP); shares features with HarmonyOS X" with citations. For the same reason, the new EMUI 16 row is labelled "Android 16 (AOSP)" with no HarmonyOS "based on" claim, since no source ties EMUI 16 to a HarmonyOS version. MintGekota (talk) 15:10, 14 July 2026 (UTC)