Fact-checked by Grok 2 weeks ago

OpenHarmony


OpenHarmony is an open-source framework incubated and operated by the OpenAtom Foundation, intended for smart devices across all scenarios in a fully connected world. It employs a component-based, layered comprising , system service, framework, and application layers, supporting scalable deployment on hardware with memory from 128 KiB upward, including multi-kernel options like and . The project originated from code donations by to the OpenAtom Foundation in 2020, transitioning to open governance under the 2.0 license, with capabilities for distributed hardware collaboration via DSoftBus, consistent for multi-device development, and subsystems handling , , and drivers. By March 2025, compatibility evaluations confirmed over 1,000 products from 368 manufacturers, reflecting substantial adoption in China's and smart device ecosystems. This framework underpins efforts to foster an independent, interoperable OS alternative amid global constraints, prioritizing deterministic soft real-time performance and .

Origins and Governance

Inception and Huawei Code Donation

In response to U.S. Department of Commerce restrictions placing on the Entity List on May 16, 2019, which limited access to American technologies including and ecosystem components, intensified development of an independent operating system to ensure continuity in its device ecosystem. These export controls, aimed at concerns, prompted to pivot from reliance on foreign OS frameworks toward self-developed alternatives, with emerging as a distributed system designed for against disruptions. On September 10, 2020, during the Huawei Developer Conference (HDC 2020), Huawei announced the donation of its HarmonyOS open-source codebase to the OpenAtom Foundation, catalyzing the inception of the OpenHarmony project. The donated code encompassed the core framework and foundational capabilities for smart device operations, licensed under the Apache 2.0 terms to foster collaborative development. This transfer positioned OpenHarmony as an independent open-source initiative under OpenAtom's stewardship, distinct from Huawei's proprietary HarmonyOS implementations. The initial OpenHarmony codebase targeted distributed scenarios across (IoT) devices and multi-device collaborations, emphasizing seamless connectivity over single-device mobile paradigms like alternatives. This focus aligned with Huawei's strategic emphasis on full-scenario intelligence, enabling resource sharing among heterogeneous hardware without initial prioritization of smartphone-centric features.

Establishment under OpenAtom Foundation

The OpenAtom Foundation, established in June 2020 as a non-profit organization in dedicated to advancing global open-source initiatives, incubated OpenHarmony to oversee its evolution into a framework. Supported by China's Ministry of Industry and Information Technology and initiated by major domestic firms including , Alibaba, and , the foundation manages project contributions, governance, and compliance through a developer-centered model emphasizing co-construction, co-governance, and shared benefits. This setup aims to foster an ecosystem for intelligent devices while aligning with national technological priorities. OpenHarmony's organizational structure under OpenAtom promotes open collaboration by enabling global developer access to repositories and standards, yet governance exhibits strong Chinese institutional dominance, with executive positions often held by representatives from state-linked enterprises like . Empirical contributor data reveals a predominantly domestic base, with over 8,000 participants as of early 2025, the majority affiliated with Chinese entities and contributing millions of lines of code annually. Such concentration raises questions about the project's international independence, given the foundation's ties to state-directed open-source efforts that support broader strategic goals, including military applications. To mitigate perceptions of opacity in practices, OpenHarmony incorporated OpenChain conformance principles from its early stages, prioritizing license compliance and in development workflows. This commitment culminated in third-party certification to ISO/IEC 5230 in September 2024 via CESI, an OpenChain partner, validating systematic processes for management and countering risks associated with unverified contributions.

Organizational Structure and Contributors

OpenHarmony is incubated and operated under the governance of the OpenAtom Foundation, China's inaugural open-source foundation established in June 2020. The project's technical oversight is managed by a Technical Steering Committee (TSC), which directs development priorities, approves specifications, and coordinates community efforts. Complementing the TSC are domain-specific Technical Supporting Groups (TSGs), responsible for specialized areas such as compatibility, security, and ecosystem tools, ensuring modular decision-making while maintaining alignment with core objectives. Huawei serves as the primary contributor, having donated the initial codebase derived from in 2020, but the project incorporates inputs from a broader . As of December 2024, the OpenHarmony encompassed over 8,190 contributors and 63 member organizations, with cumulative contributions exceeding 110 million lines of . In early 2025, co-building units added more than 1.23 million lines of year-to-date, reflecting sustained but concentrated activity primarily from Chinese entities like and partners such as Honghu. Commit data from the project's repository indicates thousands of submissions since inception, though detailed breakdowns reveal limited non-Chinese participation, with international engagement emerging through collaborations like the Eclipse Foundation's Oniro project, which integrates OpenHarmony components under joint . This distribution raises empirical questions about the depth of global buy-in, as organizational members and commit origins skew heavily toward domestic participants despite outreach efforts. Code contributions undergo mandatory review processes on the platform, enforcing standards for quality, compatibility, and adherence to the Apache 2.0 license. policies emphasize open-source compliance, guided by advisors like Array for and OpenChain conformance to mitigate risks of infringement or hidden proprietary elements. mechanisms include systematic audits and testing protocols aligned with industry benchmarks, aimed at verifying code integrity and isolating potential vulnerabilities without relying on unverified assurances of backdoor absence. These measures support a framework of purported openness, though centralized influence from founding entities persists in steering committee composition and contribution volume.

Historical Development

Early Releases and Milestones (2020-2022)

OpenHarmony 1.0 was released on September 10, 2020, marking the project's initial open-source baseline with support for lightweight terminal devices featuring memory capacities from 128 KB to 128 MB. Built on the kernel, this version introduced foundational distributed capabilities, including a basic distributed soft bus (DSoftBus) enabling device discovery, connection, and data transmission for interconnection among hardware. Subsequent 2021 releases expanded kernel support and system profiles. OpenHarmony 1.1.0 LTS, issued on April 1, 2021, refined adaptations for resource-constrained embedded devices, enhancing scheduling, , and peripheral drivers while maintaining compatibility with the initial memory constraints. The OpenHarmony 2.0 Canary edition followed on June 1, 2021, introducing a standard system profile for devices with higher resource profiles (up to gigabytes of RAM), alongside iterative improvements for scenarios, such as better power efficiency and modular subsystem integration. Further 1.1.x LTS variants, including 1.1.1 on June 17, 1.1.2 on August 4, and 1.1.3 on September 30, focused on stability patches and refinements for distributed . In 2022, development emphasized performance optimizations and readiness. OpenHarmony 1.1.4 LTS, released February 11, 2022, incorporated elements of the Ark Compiler framework, including its JS runtime open-sourced the prior year, to enable for faster execution and reduced runtime overhead in distributed applications. Compatibility certification processes were formalized, with announcing OpenHarmony product assessments in March 2022 to verify interoperability for select hardware like sensors and wearables, ensuring adherence to subsystem standards such as DSoftBus and . These early certifications targeted resource-limited profiles, laying groundwork for verifiable expansion without quantified adoption metrics at the time.

Expansion and Version Iterations (2023-2024)

In 2023, OpenHarmony advanced toward greater and with the release of 4.0 on October 26, which introduced over 4,000 new application programming interfaces () and 200 hardware driver interfaces (HDIs) compared to 3.2, enabling expanded developer capabilities for distributed applications across devices. This iteration enhanced framework layers for cross-device data synchronization, including improvements to the distributed and event handling, while upgrading the subsystem to Skia 0310 for better rendering efficiency in multi-device scenarios. Beta releases earlier in the year, such as 4.0 Beta2 on August 3, tested these modular extensions, focusing on component enhancements and notification frameworks to support seamless data flow in and edge environments. The 4.0 series laid groundwork for -native features by integrating foundational support for on-device processing, though full framework expansions materialized in late 2023 betas like 4.1 Beta1 on December 31, which previewed -accessible UI components for tasks such as visual text input. These updates prioritized modularity through abstracted layers, allowing selective adoption of components for varying resource constraints, with measurable progress evidenced by the proliferation that addressed ecosystem demands for interoperable services amid external pressures from technology export restrictions. In 2024, version 4.1 released on March 30 further iterated on these foundations, delivering another set of over 4,000 to bolster application extensibility and distributed orchestration, including refined capabilities for task pooling and reverse in development workflows. Emphasis shifted to upstream compatibility for resource-intensive devices, with hierarchical configuration options introduced in the prior series enabling finer-grained integration of subsystems while maintaining for lighter profiles, thus enhancing modularity without monolithic dependencies. Subsequent patches, such as 4.1.1 on May 22, incorporated bug fixes and stability improvements, reflecting engineering efforts to sustain release velocity—quantified by the cumulative growth exceeding 8,000 across 4.x iterations—despite geopolitical constraints limiting proprietary access. enhancements in 4.1 specifically augmented components like text rendering with intelligent input methods, signaling a pivot to native primitives for cross-device and flow optimization.

Recent Advancements (2025)

In May 2025, the OpenHarmony Developer Conference was held in , where the project announced the 5.1.0 Release with API version 18. This version introduced enhancements across multiple subsystems, including improved ArkUI components for text input, drag-and-drop animations, dialog boxes, and scrollable interfaces via new such as custom drop animations and text sharing capabilities. Additional updates encompassed for context encryption and window sizing, media improvements like spatial audio support and expanded video codec compatibility (, MPEG-4, ), distributed data management refinements in UDMF and RelationalStore for , and security features enabling group-based asset . Ecosystem expansion continued with certification milestones, as 41 new products from various manufacturers passed OpenHarmony compatibility evaluations in March 2025, increasing the cumulative total to 1,062 devices across 368 manufacturers. These certifications underscore adoption in diverse hardware, though direct open-source commit activity remains the verifiable metric of project momentum under the . The OpenHarmony Technology Conference in September 2025, convened in , marked the launch of the 6.0 Release version, emphasizing deep system-AI integration to enable features like streaming physical AB upgrades and enhanced large-model processing for instant application responses. This iteration supports broader terminal devices including smartphones, tablets, and computers, with advancements in ArkUI for rapid interface rendering and overall technological leaps aimed at industrial applications. A notable implementation occurred in space via the Dalian-1 Lianli mission, which validated the OpenHarmony (RTOS) in orbit during 2025. Over 1,000 hours of testing demonstrated improved subsystem response times and reliability for high-resolution tasks, confirming the RTOS's suitability for resource-constrained environments amid efforts to reduce foreign technology dependencies.

Technical Architecture and Features

Layered System Design

OpenHarmony features a four-layer architecture comprising the kernel layer at the base, followed by the system service layer, framework layer, and at the top. The kernel layer provides abstracted hardware access and core scheduling capabilities, while the system service layer delivers foundational services such as distributed data management and device connectivity. The framework layer offers and libraries for developers to build applications, and the top hosts user-facing software tailored to specific use cases. This bottom-up layered design inherently supports modularity by allowing selective inclusion of components, enabling lightweight implementations for devices with minimal resource footprints—such as embedded sensors requiring only basic and service subsets—while scaling to full-stack deployments for complex systems like smartphones or servers. Such configurability stems from the system's component-based construction, where subsystems can be assembled or omitted based on device constraints, fostering efficiency across heterogeneous hardware without redundant overhead. Compared to monolithic operating systems like , OpenHarmony's stratified modularity reduces by decoupling layers for independent customization and abstraction, permitting vendors to integrate alternative components without overhauling the entire stack. This causal structure promotes and adaptability, as evidenced by the ability to swap modular elements to match diverse deployment needs, thereby avoiding the entanglements common in tightly integrated ecosystems.

Kernel Abstraction and Multi-Kernel Support

OpenHarmony's kernel abstraction layer (KAL) facilitates a multi-kernel architecture by masking variances in underlying kernel implementations, thereby supplying the overlying system services with uniform access to core functionalities such as thread scheduling, memory management, and synchronization primitives. This design accommodates LiteOS kernels tailored for embedded devices with stringent resource constraints—LiteOS-M for microcontrollers handling kilobyte-scale memory via Memory Protection Units—and LiteOS-A for richer embedded platforms supporting Cortex-A architectures like Hi3516D V300 boards—alongside the Linux kernel for resource-abundant environments like servers. The abstraction promotes hardware portability by decoupling upper-layer components from kernel-specific details, enabling deployment across device classes from low-power sensors to nodes without wholesale code rewrites. LiteOS variants emphasize real-time responsiveness and energy efficiency, with minimal function sets excluding unnecessary overheads present in full-featured , which in turn offers expansive POSIX compliance and mature driver support for complex peripherals. This flexibility supports diverse chipsets, including ARM64 and x86, but necessitates kernel-tailored adaptations for foundations to bridge compatibility gaps. Empirical trade-offs arise in balancing portability against performance: the KAL's indirection layer can impose minor penalties in critical paths compared to direct calls, particularly under high-throughput scenarios favoring Linux's optimized monolithic structure, while prioritizes predictability at the cost of for massive workloads. Open-source availability of both s and the KAL enhances auditability, permitting of integrity and postures—unlike proprietary alternatives—though achieving seamless behavioral consistency across kernels requires rigorous testing of abstracted APIs.

Distributed Capabilities and Modularity

OpenHarmony's distributed capabilities rely on core primitives such as the Distributed Soft Bus (DSoftBus), an open-source communication framework that enables device discovery, connection management, networking, and data transmission across nearby devices. DSoftBus abstracts underlying transport protocols to provide unified for distributed , allowing devices to form ad-hoc networks and collaborate seamlessly without centralized intermediaries, thereby supporting causal coordination in multi-device ecosystems through event-driven discovery and linkages. Distributed data management complements DSoftBus by offering synchronization primitives, including Distributed Data Services (DDS), which enable cross-device storage and retrieval based on triplets of user ID, application ID, and device ID. This facilitates consistent data access and in distributed scenarios, such as shared states in swarms, where causal ordering is maintained via versioning and replication mechanisms to prevent inconsistencies during concurrent updates. Modularity in OpenHarmony is implemented via a component-based build system leveraging Generate Ninja (GN) for configuration and for compilation, permitting the assembly of tailored OS subsets from discrete like static libraries, dynamic libraries, or prebuilt binaries. Each is scoped to a single component, enabling selective inclusion to minimize footprint and eliminate unused code, which contrasts with monolithic OS designs by reducing resource overhead in resource-constrained distributed nodes. This modular approach extends to distributed features, where developers can configure only requisite soft bus or subsets for specific orchestration needs, optimizing for causal efficiency in scenarios like by avoiding bloat-induced delays in boot times or runtime overhead.

Security Mechanisms and Compatibility Standards

OpenHarmony employs a security subsystem featuring trusted execution environments () to isolate sensitive code and data execution, ensuring confidentiality and integrity against distributed threats such as unauthorized cross-device access. The Hardware Universal Key Store (HUKS) integrates TEE support for secure key lifecycle management, including generation, storage, and usage in isolated environments. This approach addresses risks inherent in distributed architectures by providing hardware-enforced isolation, distinct from less secure rich execution environments (REEs). Access controls are implemented via application sandboxes, permission frameworks, and token-based to prevent malicious or function misuse across interconnected devices. In distributed contexts, these mechanisms enforce process and , with permissions governing to shared resources like and databases, using user-device-application triplets for granular policy application. System services define custom permissions for sensitive , while sandboxing restricts traversal and inter-process interference, tailored to mitigate lateral movement risks in multi-device ecosystems. Device levels, classified from (basic) to SL5 (high assurance) per industry models, guide capability deployment based on threat profiles. Compatibility standards are verified through the X Test Suite (XTS) subsystem, which includes the Distributed Compatibility Test Suite (DCTS) for assessing cross-device interface stability and the Application Compatibility Test Suite (ACTS) for API conformance. These suites test ecosystem interoperability, ensuring adaptations align with OpenHarmony protocols derived from broader HarmonyOS verification frameworks, with execution via tools like xDevice for automated validation. Pass/fail outcomes from these tests empirically measure adherence to standards, supporting certification for devices and applications. The open-source nature of OpenHarmony facilitates third-party code reviews and security audits, allowing verification of mechanisms like secure boot and permission enforcement without proprietary barriers. This contrasts with closed systems, enabling community-driven improvements to distributed safeguards.

Ecosystem and Implementations

Software Distributions and Custom Adaptations

OpenHarmony's open-source framework enables extensive custom adaptations by third parties, allowing modifications to the , hardware drivers, and distributed capabilities to suit specialized use cases. This flexibility has led to distributions optimized for particular sectors, demonstrating the platform's viability beyond Huawei's ecosystem. In the IoT domain, Midea Group released its IoT operating system version 1.0 on October 14, 2021, as the first major third-party adaptation based on OpenHarmony. Built on OpenHarmony , it incorporates distributed soft bus for cross-device collaboration, enabling seamless integration of smart appliances from multiple manufacturers into unified ecosystems. Subsequent updates, such as compatibility certification for OpenHarmony 3.0 LTS in Midea's WB01 connection module, underscore ongoing stability enhancements for real-time appliance control and data sharing. For mobile applications, the PolyOS Mobile variant extends OpenHarmony's to support processors, providing developers with portable builds for experimental and commercial smartphones. Released in beta form as early as 2023, it includes precompiled images like polyos-mobile-3.2-beta2, emphasizing modularity for and distributed features without reliance on extensions. These adaptations highlight OpenHarmony's capacity for deep customization, with public repositories enabling community-driven refinements to core components for enhanced performance in niche architectures.

Hardware Platforms and Developer Kits

OpenHarmony accommodates diverse hardware through development boards and kits optimized for system profiles including standard, small, and mini variants, enabling developers to test abstractions, distributed features, and hardware drivers. Official documentation lists support for 22 board models, with code repositories and daily builds available for each to streamline porting and prototyping. These platforms emphasize empirical validation of OS capabilities on real silicon, prioritizing chipsets with integrated , , GPU, and support for and multimedia workloads. Prominent examples feature SoCs from , such as the BearPi-HM Nano (Hi3861) for mini-system IoT development and Hispark_Phoenix (Hi3751V351) for standard-system multimedia processing. Rockchip-based kits like the HiHope HH-SCDAYU200 (RK3568) and Yangfan (RK3399) provide robust options for industrial control and video handling, reflecting heavy reliance on domestic Chinese semiconductor ecosystems. Broader vendor integration includes international offerings, such as NXP's i.MX8M Mini on the MILOS_Standard0 board for and ' STM32MP157A on BearPi-HM Micro for embedded applications. Espressif's ESP32U4WDH on the NiobeU4 kit supports wireless prototyping, signaling attempts at global developer outreach despite primary momentum from Asian suppliers like Amlogic, Bestechnic, and Telink. The 4B, a staple in hobbyist and educational hardware, achieved OpenHarmony compatibility certification in February 2024, permitting full OS deployment and driver integration on its BCM2711 SoC. This certification, part of the community's broader testing regime, confirms baseline hardware recognition, performance metrics, and conformance across vendors. In June 2024, the OpenHarmony ecosystem certified 47 additional products, encompassing development boards, kits, and chipsets, which underscores iterative growth in verified platforms while maintaining rigorous checks for stability and . These efforts ensure empirical feature parity, though adoption remains concentrated among Chinese vendors due to aligned supply chains and upstream contributions.

Specialized Applications (IoT, Space, Automotive)

OpenHarmony finds application in scenarios, particularly for resource-constrained smart home devices and appliances. Its mini-system variant supports operations on hardware with minimal memory, such as 128 KB, facilitating distributed capabilities across sensors, controllers, and actuators in environments like lighting systems, security cameras, and household appliances. This enables seamless device linkage and , where, for example, third-party distributions based on OpenHarmony allow smartphone control of appliances from brands like Midea, reducing in interconnected home networks. In space exploration, OpenHarmony serves as a real-time operating system (RTOS) for satellites operating under stringent temporal constraints. The Dalian-1 Lianli microsatellite, a 17-kg 12U CubeSat launched for high-resolution remote sensing, validated OpenHarmony RTOS on subsystems including the magnetometer, sun sensor, and attitude control in orbit as of June 2025. This deployment, running on domestic chips to mitigate foreign technology reliance, achieved command response times of two microseconds— a substantial improvement over prior configurations—enhancing real-time reliability and responsiveness in vacuum and radiation-challenged conditions. For automotive and transportation sectors, adaptations like SwanLinkOS leverage OpenHarmony's modular framework for vehicle-centric systems. Developed by Honghu Wanlian Technology (an iSoftStone subsidiary) and released in June 2022, SwanLinkOS integrates with OpenHarmony 3.1, supporting processors such as RK3399 and RK3568 for applications in intelligent in-vehicle terminals, road monitoring, and maritime supervision. These implementations provide customized distributions for dynamic and vehicle oversight, demonstrating improved operational efficiency in mobility-constrained settings through distributed soft bus mechanisms.

Oniro Project Integration

The Oniro Project, hosted by the , functions as a downstream distribution of OpenHarmony, extending its foundational layers with components optimized for global markets outside , particularly in automotive and applications. This integration emphasizes add-ons such as for cross-platform app usability, Eclipse Theia-based IDE for development, and the Servo web engine, enabling broader ecosystem compatibility while maintaining OpenHarmony's distributed OS core. Oniro's approach prioritizes tested partner features and release tools, facilitating adoption in Western regulatory environments that demand enhanced compliance and transparency, in contrast to OpenHarmony's primary orientation toward broad device interoperability. Through collaboration between the and OpenAtom Foundation, Oniro contributes upstream enhancements back to OpenHarmony where feasible, fostering hybrid open-source development for multi-kernel systems suitable for connected vehicles and . For instance, Oniro incorporates third-party services like Kanto for IoT management and Mosquitto for messaging, integrated into the build system to support real-time, flexible deployments in non-Chinese hardware ecosystems. This upstream/downstream dynamic has enabled joint efforts, such as license compliance workshops in November 2024, demonstrating potential for verifiable, auditable code flows that address global developer concerns over proprietary dependencies. Oniro's releases, including extensions for satellite and automotive integrations, highlight its role in bridging OpenHarmony's strengths with Western-focused modularity, though it diverges by mandating stricter open-source purity and market-specific adaptations to mitigate adoption barriers in regulated sectors. As of early 2025, this has supported collaborative forums, like the OpenHarmony Technical Forum presentations, underscoring Oniro's utility in expanding OpenHarmony's reach without altering its core distributed capabilities.

Relationship to HarmonyOS and OpenEuler

Overlaps and Divergences with HarmonyOS

OpenHarmony serves as the open-source upstream foundation for Huawei's proprietary operating system, sharing core architectural elements such as a distributed soft bus for device interconnection, a multi-kernel supporting and kernels, and a modular framework enabling seamless data and capability sharing across heterogeneous devices. These overlaps stem from Huawei's initial contributions to OpenHarmony, which were derived from technologies, ensuring that foundational distributed features like super virtual devices and capability access frameworks are common to both. In contrast, HarmonyOS diverges significantly as a downstream implementation by incorporating proprietary Huawei-specific modules, including closed-source engines (e.g., Celia assistant integrations), customized frameworks beyond the open ArkUI, and hardware-optimized drivers tailored for Huawei's processors and ecosystem services like Core, which are not available in OpenHarmony's fully open codebase exceeding 120 million lines. OpenHarmony permits unrestricted third-party modifications, such as alterations and driver additions, fostering independent forks, whereas HarmonyOS restricts such access to maintain Huawei's control over and optimizations. A key point of further divergence emerged with HarmonyOS NEXT (version 5.0, commercially launched in 2024), which eliminates Android Open Source Project () compatibility layers present in prior HarmonyOS versions, adopting a fully native stack built on 's core but enhanced with frameworks for and resource scheduling, thereby prioritizing Huawei's closed over OpenHarmony's general-purpose openness. This shift has enabled to power over 23 million devices by October 2025, primarily smartphones and tablets, while OpenHarmony's open nature supports non-Huawei adaptations without such extensions.

Integration with OpenEuler Ecosystem

OpenEuler, a Linux distribution primarily developed for server, cloud, and embedded environments, serves as a complementary platform to OpenHarmony in Huawei-led ecosystems, enabling interoperability through shared distributed technologies. The distributed soft bus (DSoftBus) from OpenHarmony has been integrated into openEuler Embedded, facilitating point-to-point device connections and authentication between openEuler-based embedded systems and OpenHarmony devices, which supports seamless data exchange in resource-constrained IoT scenarios. This integration leverages OpenHarmony's lightweight kernel abstractions alongside openEuler's Linux kernel (version 6.6 in the 25.03 release), allowing hybrid deployments where openEuler handles compute-intensive server tasks while OpenHarmony manages edge devices. In practical applications, components such as distributed —ported from OpenHarmony 3.2 into openEuler—enable synchronized handling across distributed nodes, enhancing reliability in cloud-edge architectures by propagating updates and security patches through common open-source repositories. For instance, the FangTian in openEuler 24.03 LTS SP2 unifies runtime environments, permitting OpenHarmony applications to execute alongside Linux-native ones on openEuler hosts, which reduces overhead in multi-device enterprises by standardizing for cross-OS . This synergy yields causal advantages, such as lower in flows from edge sensors to central , as evidenced by demonstrations of DSoftBus interconnecting openEuler with OpenHarmony endpoints for processing. Contributor communities for both projects overlap significantly under the OpenAtom Foundation, with providing core upstream contributions, though openEuler's governance invites broader participation from partners like Hoperun for extensions like human-machine interface (HMI) domains integrated with OpenHarmony frameworks. This reinforces ecosystem cohesion for enterprise users seeking vendor-diverse alternatives but maintains openness, as patches and modules are released via public repositories compatible with standard builds used in OpenHarmony's multi-kernel variants. Such alignments prioritize empirical over proprietary silos, though adoption remains concentrated in regions tolerant of Huawei's influence due to geopolitical factors.

Huawei's Role in Upstream Contributions

Huawei donated the foundational source code for OpenHarmony's L0 to L2 branches, derived from HarmonyOS and LiteOS, to the OpenAtom Open Source Foundation in September 2020, establishing the project's initial upstream codebase. This donation included core capabilities for smart devices, enabling the foundation to incubate and operate OpenHarmony as an open-source distributed operating system framework. As the primary initiator, has maintained a leading role in upstream development, actively contributing to OpenHarmony's evolution alongside the OpenAtom Foundation. By the end of 2024, the project had amassed over 1.5 million lines of code with contributions from more than 10,000 community participants, though 's ongoing inputs—verified through logs and foundation reports—constitute the bulk of core advancements and maintenance commits. The OpenAtom Foundation's policies facilitate external pull requests and code submissions, promoting broader participation while focuses on strategic enhancements to foster alternatives. This contribution model reflects Huawei's incentives to upstream innovations post-2020, verifiable via Gitee repository histories, where Huawei-affiliated developers dominate merged proposals, balanced by community review processes to integrate diverse inputs. Despite the predominance of internal commits, the project's Apache 2.0 licensing and contribution guidelines have enabled incremental external merges, accumulating inputs from over 9,200 developers by mid-2025.

Geopolitical Context and Controversies

Response to US Sanctions on Huawei

The addition of Technologies to the on May 16, 2019, by the Department of Commerce's imposed licensing requirements for exports, reexports, and transfers of items subject to the , severely limiting 's access to U.S.-origin semiconductors, software, and technologies integral to mobile operating systems like with . This restriction, expanded in subsequent rules including the addition of 46 non-U.S. affiliates on August 19, 2019, and further affiliates in 2020, directly catalyzed 's pivot from reliance on , as new devices could no longer receive services updates or certifications. In response, Huawei initiated the OpenHarmony project under the OpenAtom Foundation, donating its core source code (including kernel foundations) in phases during 2020, with the first OpenHarmony 1.0 release occurring on September 10, 2020. This open-source framework was designed to enable distributed device interoperability without dependence on restricted U.S. technologies, attracting contributions from over seven initial partners including and state-linked entities, as part of China's broader "" strategy emphasizing domestic technological self-sufficiency. The project's structure, managed by OpenAtom—a non-profit coordinating efforts—facilitated rapid ecosystem building, with version 2.0 released on June 1, 2021, supporting and applications. Proponents within , including and officials, portray OpenHarmony as a triumph of indigenous innovation that circumvents U.S. export controls, enabling and partners to deploy sanction-resilient software stacks and reducing vulnerability to future restrictions. Conversely, analyses from observers highlight it as a reactive measure driven by enforced , with OpenAtom's role in aggregating contributions from firms like Alibaba and reflecting coordinated state influence rather than purely market-led open-source evolution, potentially aimed at sustaining 's market position amid ongoing [Entity List](/page/Entity List) expansions. By 2024, this initiative had expanded to over 41 new commercial products monthly, underscoring its role in fostering alternatives to foreign-dominated OS landscapes.

Security Risks and Espionage Allegations

Concerns regarding risks in OpenHarmony primarily stem from its under the OpenAtom Foundation, a Chinese-led open-source entity closely aligned with and perceived as advancing the 's (CCP) strategic goals for technological self-reliance. U.S. lawmakers, including members of the Select Committee on the Chinese Communist Party, have highlighted potential risks, arguing that OpenHarmony's codebase, initially contributed by Huawei, could serve as a vector for state-sponsored or disruption, particularly in sectors like energy grids and ports where it has seen adoption. These allegations draw on broader geopolitical tensions, with critics pointing to OpenAtom's role in PRC national strategy as enabling undue CCP influence over open-source projects, potentially embedding hidden mechanisms for or control that evade detection in distributed systems. In June 2025, the Select Committee urged the to disclose details of any collaborations with OpenAtom and HarmonyOS-related efforts, emphasizing the need for an independent, third-party security audit of OpenHarmony's full codebase to verify the absence of backdoors or vulnerabilities exploitable by foreign actors. No such comprehensive public audit has confirmed intentional backdoors to date, though identified vulnerabilities, such as CVE-2024-37030 allowing via use-after-free errors in pre-installed apps, underscore ongoing risks amenable to patching in open-source environments. Counterarguments emphasize OpenHarmony's open-source transparency, which facilitates global and contrasts with proprietary systems where scrutiny is limited; proponents note the absence of verified incidents tied to the project, attributing concerns to unsubstantiated fears rather than of malice. However, causal risks persist for adopters in sensitive domains, as mandatory with national laws could compel contributors or maintainers affiliated with state entities to insert or overlook subversive elements, a dynamic not fully mitigated by code openness alone. U.S. officials have advocated coordinated international restrictions on derivatives like OpenHarmony to such threats, framing adoption as a potential gateway for CCP-enabled spying or .

Intellectual Property Disputes and Open-Source Compliance

OpenHarmony, developed under the 2.0, adheres to (OSI) standards for code sharing and modification, enabling contributions from over 70 organizations as of 2023. However, its intellectual property provenance has faced scrutiny due to Huawei's dominant role in upstream contributions, which account for substantial portions of the despite by the OpenAtom Foundation. Critics, including U.S. congressional inquiries, have raised questions about potential undisclosed derivations from or components, citing Huawei's historical reliance on Open Source Project () adaptations prior to U.S. sanctions in 2019. These concerns stem from empirical analysis of early implementations, which revealed Android-compatible elements despite claims of a microkernel architecture based on . No verified lawsuits or license violations have been documented for OpenHarmony itself, distinguishing it from broader IP disputes in hardware patents. Nonetheless, the project's heavy dependence on code—estimated to form the core of its distributed OS framework—prompts debates on "cleanliness," with independent audits lacking transparency beyond self-reported compliance. Proponents argue this reflects legitimate innovation in response to export controls, leveraging open-source principles to build a domestic without lock-in. Detractors, however, view it through a lens of causal realism, positing that rapid development amid sanctions increases risks of unattributed , potentially violating upstream licenses like those in or . In response, initiatives like the Eclipse Oniro project have emerged as downstream forks, emphasizing rigorous IP toolchains to detect violations and ensure vendor neutrality. Oniro's compliance mechanisms, including early-stage IP scanning and legal reviews, address perceived risks in OpenHarmony's Huawei-centric contributions, facilitating community-driven alternatives without direct reliance on potentially tainted provenance. This approach underscores a viewpoint prioritizing verifiable independence over normalized acceptance of state-affiliated open-source efforts, amid calls for forked repositories to mitigate influence from entities like Huawei or OpenAtom. Such forks highlight tensions between open-source collaboration and empirical safeguards against IP opacity.

Global Adoption Barriers and Criticisms

OpenHarmony's global adoption faces significant hurdles stemming from its close association with , which has been stigmatized in Western markets due to U.S. sanctions imposed since 2019 over concerns. These restrictions have severed Huawei's access to key global supply chains and technologies, fostering distrust among Western enterprises and governments wary of potential backdoors or data vulnerabilities linked to Chinese state influence. As a result, uptake remains negligible in and , where alternatives like dominate IoT and sectors, while OpenHarmony thrives primarily in China's domestic market, powering over 100 million devices in IoT applications as of August 2025. Critics highlight the immaturity of OpenHarmony's compared to Android's established maturity, with fewer native applications—approximately 20,000 as of January 2025—and a narrower set that discourages developers from or building for the platform. This lag creates a chicken-and-egg problem: limited apps deter device adoption, while sparse device deployment reduces incentives for app development, contrasting sharply with Android's vast library exceeding 30,000 APIs and billions of installations. executives have acknowledged this immaturity, urging consumers and partners to tolerate early shortcomings, yet third-party developers cite insufficient incentives and gaps as persistent barriers to broader engagement. Outreach initiatives, such as the OpenHarmony Technical Conference held in , , on September 3, 2025, and the Developer Conference in on May 24, 2025, aim to bridge these gaps by partnering with entities like the Foundation's Oniro project to promote accessibility and compliance in Western contexts. These events featured workshops on expansion and open-source integration, yet attendance and follow-through have yielded mixed results, with participation skewed toward Asian and select stakeholders rather than achieving widespread global developer buy-in. Analysts note that while such efforts signal intent to decouple from Huawei's extensions, entrenched market dynamics and geopolitical skepticism continue to limit penetration beyond China-centric alliances.

Impact and Reception

Achievements in Diversifying OS Landscapes

OpenHarmony has facilitated the development of non-Android operating system stacks for () devices, enabling Chinese manufacturers to deploy alternatives to Google-dominated ecosystems. By 2025, it achieved certification as China's national operating system for , supporting applications in connected appliances, wearables, and industrial equipment, thereby reducing reliance on U.S.-controlled technologies. In June 2024 alone, 47 new products qualified for OpenHarmony testing, demonstrating growing ecosystem momentum with mandatory use of version 4.1 or higher for certifications starting January 1, 2025. Its distributed architecture introduces innovations for , where devices collaborate seamlessly across scenarios, outperforming traditional systems in latency-sensitive tasks. Ground and on-orbit tests of OpenHarmony real-time OS on the Dalian-1 Lianli satellite validated task switching times averaging ≤2 μs, with stable operation across three subsystems, supporting efficient in resource-constrained environments. In intelligent implementations, the system achieved communication ≤50 ms and data loss rates as low as 0.03%, enabling edge interactions without dependency on centralized cloud architectures. Through modular, layered designs including DSoftBus for device connectivity and distributed data management, OpenHarmony contributes to open-source alternatives under the OpenAtom Foundation, allowing customization for diverse hardware without proprietary lock-in. This fosters broader OS diversification, as evidenced by distributions like KaihongOS for full-scenario deployments, promoting indigenous stacks that mitigate foreign tech vulnerabilities in .

Technical Limitations and Performance Critiques

OpenHarmony's multi-kernel architecture, which supports subsystems such as and through a Kernel Abstraction Layer (KAL), enables adaptation to varied device resource constraints but introduces engineering complexity and risks of ecosystem fragmentation. This design, intended to abstract kernel differences for unification, complicates consistent driver development and maturity, lagging behind 's extensive, battle-tested hardware support accumulated over decades of global contributions. Performance critiques highlight trade-offs inherent in OpenHarmony's microkernel-based components, particularly in the HongMeng underpinning advanced implementations, where mechanisms and message-passing yield overheads—benchmarks indicate up to 2x slower execution in select workloads relative to Linux's monolithic structure. In distributed environments leveraging the DSoftBus for device interconnection, these costs can amplify in or high-throughput scenarios, contrasting with centralized OS optimizations that minimize such penalties. Slower global developer adoption is evidenced by limited empirical metrics: as of late 2023, OpenHarmony had generated only 8 peer-reviewed research papers, dwarfed by over 7,000 for , signaling gaps in tooling and community scrutiny. The platform's count in version 4.0 stood at roughly 10,435—less than a third of Android API level 28's 30,000+—constraining application sophistication and third-party library integration, exacerbated by immature static analysis frameworks for the ArkTS language and absent app publishing infrastructure akin to mature ecosystems. These factors contribute to a bare-bones experience, with ongoing needs for instrumentation and compliance tools to bridge shortfalls.

Broader Industry and Economic Implications

OpenHarmony's emergence has propelled China's digital self-reliance initiatives, enabling the country to diminish reliance on foreign operating systems such as for and smart devices, thereby reshaping domestic supply chains toward greater autonomy. By late 2024, the OpenHarmony community encompassed over 8,100 members and saw contributions from more than 70 organizations, positioning it as the fastest-growing open-source operating system for smart devices and supporting over 20,000 native applications. This development aligns with national strategies to fortify technological independence amid export controls, potentially stabilizing China's sector—projected to contribute to global connected devices reaching 18.8 billion by end-2024—while insulating local industries from disruptions in Western-dominated ecosystems. In terms of competitive dynamics, OpenHarmony introduces pressures on Android's hegemony, particularly in , where derivative systems like captured 17% by Q3 2024, fostering diversification and spurring innovation through open-source collaboration. Advocates contend this rivalry enhances global options for developers and erodes monopolistic control, with Huawei's related OS investments forecasted to create at least 3 million jobs in China's sector. Conversely, the pursuit of sovereignty risks entrenching bifurcated , as Chinese standards diverge from international norms, elevating barriers and development expenses for cross-border supply chains; this fragmentation, accelerated by self-reliance policies, divides the global landscape and may undermine for multinational participants. Economically, while OpenHarmony drives market penetration and domestic R&D—Huawei allocated over 20% of annual sales to research for three consecutive years through 2024—the trade-offs include amplified security overheads from nascent, parallel infrastructures and potential inefficiencies in duplicated global efforts. Critics, drawing from analyses of China's broader autonomy push, warn that such isolation could inflate costs and expose ecosystems to unmitigated risks, contrasting with benefits like localized job growth and reduced foreign dependency vulnerabilities. Empirical data on adoption remains nascent, but the system's emphasis on third-party ecosystem building underscores challenges in achieving seamless scale without compromising unified standards.

References

  1. [1]
    OpenHarmony Project
    A unified OS for flexible deployment​​ OpenHarmony enables hardware resources to be scaled with its component-based and small-scale designs. It can be deployed ...
  2. [2]
    OpenHarmony Project - docs - Gitee
    A unified OS for flexible deployment​​ OpenHarmony enables hardware resources to be scaled with its component-based and small-scale designs. It can be deployed ...
  3. [3]
    OpenHarmony Community: In March 2025, 41 new products have ...
    Mar 31, 2025 · In March, 41 new products passed the compatibility evaluation, and a total of 1,062 products from 368 manufacturers have passed the ...Missing: adoption | Show results with:adoption
  4. [4]
    Huawei's Harmony aims to end China's reliance on Windows, Android
    Jun 27, 2024 · Huawei no longer controls OpenHarmony, having gifted its source code to a non-profit called the OpenAtom Foundation in 2020 and 2021 ...
  5. [5]
    U.S. Restrictions on Huawei Technologies: National Security ...
    Jan 5, 2022 · From May 2019 through August 2020, DOC amended its rules, tightening restrictions on exports to Huawei, and extending the TGL several times. In ...
  6. [6]
    HarmonyOS now has 100 million lines of code - Huawei Central
    Mar 22, 2023 · At HDC 2020, Huawei launched open-source HarmonyOS as OpenHarmony and donated the entire code to OpenAtom Foundation. OpenAtom Foundation is ...Missing: inception | Show results with:inception
  7. [7]
    Huawei Announces OpenHarmony Project With A BSD-Licensed ...
    Sep 11, 2020 · Huawei Announces OpenHarmony Project With A BSD-Licensed HarmonyOS Source Code Release ; September 10, 2020, Initial OpenHarmony release with ...Missing: donation | Show results with:donation
  8. [8]
    Open Source @ Huawei
    Huawei started using open source code 20 years ago. Over time, the company ... Donated device OS OpenHarmony to OpenAtom Foundation. Open sourcing of AI ...
  9. [9]
    Chinese tech companies supported open-source project ... - ijiwei
    The OpenHarmony Foundation accepted the code related to the primary function of the smart device operating system donated by Huawei in September 2020 ...Missing: inception | Show results with:inception
  10. [10]
    OpenHarmony Educational Resource Package launched by ...
    Jun 7, 2021 · Last September, Huawei announced at the HDC 2020 conference that it would donate OpenHarmony to the OpenAtom Foundation. OpenHarmony is the ...
  11. [11]
    关于我们 - 开放原子开源基金会
    开放原子开源基金会是致力于推动全球开源事业发展的非营利机构，于2020 年6 月在北京成立。基金会秉持“共建、共治、共享”的核心理念，定位为以开发者为中心的开源项目 ...Missing: website | Show results with:website
  12. [12]
    Open-Source Technology and PRC National Strategy: Part I
    May 10, 2024 · The OpenAtom Foundation supports open-source technology in areas such as RISC-V architecture and Electronic Design Automation. · OpenHarmony, an ...
  13. [13]
    Governance Structure - openEuler
    Chairperson. Xiong Wei. Huawei Technologies Co., Ltd. ; Executive Director. Hu Zhengce. Huawei Technologies Co., Ltd. ; Executive Secretary. Liu Yanfei. OpenAtom ...
  14. [14]
    Open-Source Technology and PRC National Strategy: Part II
    May 24, 2024 · The CCP's decisions to deepen its involvement in the OpenAtom Foundation and support the development of OpenHarmony and other open-source based ...
  15. [15]
    FOSDEM 2021 - OpenChain upfront: OpenHarmony was born this way
    Having prioritized compliance, governance and transparency, OpenChain was the natural backdrop for it. Rather than embracing open source only to exploit it, ...
  16. [16]
    OpenHarmony Announces Third-Party Certification to ISO/IEC 5230 ...
    Sep 17, 2024 · OpenHarmony has adopted ISO/IEC 5230 via third-party certification provided by CESI, an official partner of the OpenChain Project.
  17. [17]
    300 Years: Huawei's Open Source Strategy - Interconnected
    Sep 24, 2020 · In the case of Huawei though, OpenHarmony is a young project, and OpenAtom is an even younger foundation. The lazy and obvious conclusion ...
  18. [18]
    The State of OpenHarmony Ecosystem: Initiatives, Toolchains, and ...
    Feb 8, 2024 · To support the technical success of OpenHarmony, the TSC has further set up various domain-specific Technical Supporting Groups (TSG). At the ...
  19. [19]
    gudehe/compatibility - Gitee
    OpenHarmony Program Compatibility Working group 1.0. The OpenHarmony Compatibility Team is responsible for defining and monitoring the Product Compatibility ...
  20. [20]
    Huawei donated HarmonyOS core structure to OpenAtom Foundation
    Jun 7, 2021 · Huawei has donated the HarmonyOS core structure package and all the basic capabilities related to code to the firm.Missing: inception | Show results with:inception
  21. [21]
    OpenHarmony Community: In December 2024, 83 new products ...
    Jan 3, 2025 · Among them, Huawei Device Co., Ltd., Shenzhen Kaihong Digital Industry Development Co., Ltd., and Hunan Kaihong Zhigu Digital Industry ...Missing: adoption | Show results with:adoption
  22. [22]
    OpenHarmony Community: Since the beginning of this year, the co ...
    Mar 12, 2025 · As of February, the co-construction units have contributed more than 1.23 million lines of code to OpenHarmony this year. As of February ...Missing: statistics | Show results with:statistics
  23. [23]
    [PDF] Software Engineering for OpenHarmony: A Research Roadmap - arXiv
    Nov 21, 2023 · tags, 1,400 forks, 57 stars, 7,833 commits, and 627 contributors. ... Similarly, Huawei has released EMUI to feature a more personalized user ...Missing: statistics | Show results with:statistics
  24. [24]
    Eclipse Oniro for OpenHarmony | projects.eclipse.org
    The Project was established through a first-of-its-kind agreement between two major global open-source foundations - The Eclipse Foundation and The OpenAtom ...Missing: structure | Show results with:structure
  25. [25]
    Eclipse and OpenAtom: Pioneering Open Source Innovation
    Jan 30, 2024 · The goal of the Oniro Project is to elevate the OpenHarmony platform by developing a suite of Western market-focused modifications and add-ons, ...
  26. [26]
    OpenHarmony, an operating sytem with OpenChain in mind
    Having prioritized compliance, governance and transparency, OpenChain was the natural backdrop for it. Rather than embracing open source only to exploit it, ...
  27. [27]
    OpenHarmony Security Test Guide - docs - Gitee
    With reference to industry standards and best practices, this document provides specifications for security tests of the OpenHarmony project.
  28. [28]
    [PDF] June 4, 2025 Dear Mr. Milinkovich
    Jun 4, 2025 · We write to express our concern regarding HarmonyOS, OpenHarmony, and the Eclipse. Foundation's collaboration with the OpenAtom Foundation ...Missing: structure | Show results with:structure
  29. [29]
    OpenHarmony Release Notes - docs - Gitee
    OpenHarmony v1.1.2 LTS (2021-08-04) · OpenHarmony 1.1.1 LTS (2021-06-22) · OpenHarmony 1.1.0 LTS (2021-04-01) · OpenHarmony 1.0 (2020-09-10). Logo en © Gitee.
  30. [30]
    Softbus-Communication Subsystem-Basic System Capability ...
    Apr 13, 2021 · Provides high-speed, secure communication between devices. This module implements unified distributed communication capability management ...
  31. [31]
    OpenHarmony 2.0 Canary (2021-06-01) - docs - Gitee
    OpenHarmony 2.0 Canary (2021-06-01). Version Description. On the basis of OpenHarmony 1.1.0, OpenHarmony 2.0 adds the version for the standard system, ...
  32. [32]
    LiteOS kernel for embedded devices with rich resources - GitHub
    The OpenHarmony LiteOS Cortex-A is a new-generation kernel developed based on the Huawei LiteOS kernel. Huawei LiteOS is a lightweight operating system (OS) ...Missing: 2021 | Show results with:2021
  33. [33]
    Ark Compiler JS runtime became open source in Huawei HarmonyOS
    Sep 7, 2021 · Ark JS runtime officially became open source in Huawei OpenHarmony OS. It's the first Ark compiler to use direct compilations of programming to machine codes ...
  34. [34]
    Huawei certified OpenHarmony products to grow device ecosystem
    Mar 16, 2022 · As per the latest information, Huawei has officially released OpenHarmony products certification that has passed compatibility assessment.Missing: 2020-2022 | Show results with:2020-2022
  35. [35]
    OpenHarmony 4.0 Release
    Scenario-specific code execution permission control policies are provided. ... Integrity protection is provided for code pages. Driver. The extended device ...Missing: review | Show results with:review
  36. [36]
    OpenHarmony 4.0 release version launched with API 10
    Oct 28, 2023 · OpenHarmony 4.0 Release version launched with over 4000 ArkTS APIs to enrich application development capabilities and 200 HDI interfaces.
  37. [37]
    harmony 鸿蒙OpenHarmony 4.0 Beta2 - seaxiang
    Oct 30, 2023 · The third-party vendor is carrying out adaptation. 2023-08-30. 你可能感兴趣的鸿蒙文章. harmony 鸿蒙OpenHarmony 1.0 (2020-09-10) (EOL) · harmony ...
  38. [38]
    http://docs.openharmony.cn/pages/v4.1/en/release-notes/OpenHarmony-v4.1-beta1.md
  39. [39]
    OpenHarmony v4.1 Release (2024-03-30)
    OpenHarmony 4.1 Release comes with more than 4000 new APIs to enrich your application development capabilities.
  40. [40]
    harmony 鸿蒙OpenHarmony Release Notes - seaxiang
    Oct 28, 2022 · OpenHarmony 4.x Releases · OpenHarmony v4.1.2 Release (2024-12-26) · OpenHarmony v4.1.1 Release (2024-05-22) · OpenHarmony v4.1 Release (2024-03-30).<|separator|>
  41. [41]
    The OpenHarmony Developer Conference 2025 will be officially ...
    May 6, 2025 · The open source HarmonyOS Developer Conference 2025 will be officially announced on May 24, and the 5.1 Release version will be released.Missing: advancements | Show results with:advancements
  42. [42]
    OpenHarmony 5.1.0 Release - docs - Gitee
    API version 18 is officially released in OpenHarmony 5.1.0 Release. Compared with the preceding OpenHarmony 5.0.3 Release featuring API version 15, this version ...
  43. [43]
    OpenHarmony Technology Conference 2025 Successfully Held - 36氪
    Sep 27, 2025 · On September 27, the OpenHarmony Technology Conference 2025 was successfully held at the Changsha International Convention Center.
  44. [44]
    OpenHarmony 6.0 Release Version Officially Launched - Voila!News
    Sep 27, 2025 · This version is capable of supporting terminal devices such as smartphones, tablets, and computers. Additionally, the conference plans to ...
  45. [45]
    On-Orbit Validation of the OpenHarmony Real-Time Operating ...
    Apr 14, 2025 · OpenHarmony is an open-source project incubated and operated by the OpenAtom Open Source Foundation. ... A block diagram of the OpenHarmony ...<|separator|>
  46. [46]
    Spurred by US sanctions, China adapts Huawei's HarmonyOS for ...
    Jun 21, 2025 · “The Lianli satellite mission showed that using the OpenHarmony real-time operating system significantly improved the satellite's response ...
  47. [47]
    Why OpenHarmony is not classified as Linux-based despite having ...
    Jul 7, 2024 · OpenHarmony is not classified as a Linux system because its primary kernel is LiteOS, not the Linux kernel.
  48. [48]
    LiteOS-A Overview - OpenHarmony/docs
    The LiteOS-A kernel is ideal for the small system, which supports memory of megabytes and Memory Management Unit (MMU) isolation. Equivalent kernels include ...Missing: 2021 | Show results with:2021
  49. [49]
    Kernel - OpenHarmony/docs
    The OpenHarmony LiteOS kernel provides basic functions, such as process and thread scheduling, memory management, inter-process communication (IPC) mechanism, ...
  50. [50]
    OpenHarmony - BetaWiki
    OpenHarmony is an open-source distributed operating system project with technical origins partially derived from Huawei's LiteOS. Initially developed by Huawei ...Missing: history | Show results with:history
  51. [51]
    Kernel Overview - OpenHarmony/docs
    The LiteOS-M kernel has simple code structure, including the minimum function set, kernel abstraction layer (KAL), optional components, and project directory.
  52. [52]
    OpenHarmony/docs - Gitee
    Kernel subsystem: OpenHarmony uses a multi-kernel design (Linux or LiteOS) ... The kernel abstraction layer (KAL) hides differences in kernel ...
  53. [53]
    openharmony/communication_dsoftbus: 暂无描述 - GitHub
    DSoftBus implements unified distributed communications between near-field devices and provides APIs for device discovery, connections, networking, and data ...Missing: 1.0 | Show results with:1.0
  54. [54]
    DSoftBus - Embedded SIG - openEuler
    Jul 21, 2022 · DSoftBus is an open source device communication base of the OpenHarmony community. It powers devices with distributed collaboration capabilities.
  55. [55]
    OpenHarmony/distributeddatamgr_datamgr - Gitee
    Distributed Data Service (DDS) provides the capability to store data in the databases of different devices. DDS isolates data based on a triplet of the account, ...
  56. [56]
    Building a Module - OpenHarmony开源项目
    It can be a dynamic library, static library, configuration file, or prebuilt module. A module must belong to a component and can belong to only one component.Configuration Rules · C/C++ Template Example · Prebuilt Template Example
  57. [57]
    Compilation and Building Guide - OpenHarmony/docs
    OpenHarmony is designed with a layered architecture, which consists of the kernel layer, system service layer, framework layer, and application layer from ...
  58. [58]
    openharmony/kernel_liteos_m: LiteOS kernel for devices ... - GitHub
    OpenHarmony LiteOS-M is a lightweight operating system kernel designed for the Internet of Things (IoT) field. It features small footprint, low power ...Missing: 2021 | Show results with:2021
  59. [59]
    LiteOS-M Overview - kernel - OpenHarmony/docs
    The OpenHarmony LiteOS-M kernel is a lightweight operating system (OS) kernel designed for the IoT field. It features small size, low power consumption, and ...
  60. [60]
    Basic Concepts of HUKS - OpenHarmony开源项目
    The TEE provides a secure execution environment for trusted applications (TAs) to ensure end-to-end security by features, such as isolated execution ...
  61. [61]
    GitHub - openharmony/security_itrustee_ree_lite: TEE agent service
    The itrustee_ree_lite module provides a set of rich execution environment (REE) API components for interacting with iTrustee-developed TEEOS, ...
  62. [62]
    Access Control Overview - OpenHarmony开源项目
    To prevent improper or malicious use of data or functions, the system provides a variety of access control mechanisms, including the application sandbox, ...
  63. [63]
    openharmony/security_permission: Application permission ... - GitHub
    In OpenHarmony, apps and system services run in independent sandboxes. Both processes and data are isolated from each other to protect the security of app ...
  64. [64]
    GitHub - openharmony/distributeddatamgr_datamgr: Distributed ...
    Distributed Data Service (DDS) provides the capability to store data in the databases of different devices. DDS isolates data based on a triplet of the ...
  65. [65]
    Security Overview - OpenHarmony/docs - Gitee
    Security Overview. The OpenHarmony security subsystem provides security capabilities that make your applications and devices more secure and help you manage ...
  66. [66]
    Device security level management | 设备安全等级管理模块 - GitHub
    The security capabilities of OpenHarmony devices are classified into five levels from SL1 to SL5, based on the industry standard security classification model ...Missing: mechanisms | Show results with:mechanisms
  67. [67]
    openharmony/xts_dcts: Distributed compatibility test suite - GitHub
    The X test suite (XTS) subsystem contains a set of OpenHarmony certification test suites, including the currently supported distributed compatibility test ...Xts · Usage Guidelines · Test Case Development...
  68. [68]
    OpenHarmony/xts_tools - Gitee
    Introduction. The X test suite (XTS) subsystem contains a set of OpenHarmony certification test suites, including the currently supported application ...Introduction · System Types · Usage Guidelines · Test Case Development...
  69. [69]
    Compatibility Test Services - Open Harmony technical site
    Compatibility test services ensure devices and applications comply with OpenHarmony standards, using tools like XTS Suite, and provide practical insights.Missing: 2020-2022 | Show results with:2020-2022
  70. [70]
    xDevice User Guide - OpenHarmony开源项目
    To ensure compatibility of the OpenHarmony ecosystem, OpenHarmony provides the compatibility test service. For related products, API tests are required for ...Overview · Implementation Principles · Test Commands
  71. [71]
    security - OpenHarmony/docs - Gitee
    Overview. This section provides samples about how to use existing security mechanisms to improve system security features, including secure boot, application ...
  72. [72]
    Differences and commonalities between HarmonyOS and ...
    Apr 17, 2025 · OpenHarmony aims to build a neutral and open distributed operating system ecosystem to promote the prosperity and development of the Internet of ...
  73. [73]
    First third party IoT operating system launched based on ...
    Oct 15, 2021 · Midea IoT operating system 1.0 shares the latest cross device features powered by distributed capability framework in the OpenHarmony project.
  74. [74]
    Midea unveils IoT operating system backed by Huawei
    Oct 21, 2021 · The IoT operating system would help link smart home appliances made not only by Midea but also by other manufacturers, providing an all-new ...
  75. [75]
    First OpenHarmony 3.0 LTS version compatibility test certification ...
    Midea connection module WB01 equipped with Media's IoT operating system has passed the OpenHarmony 3.0 LTS compatibility certification test.
  76. [76]
    PolyOS | PolyOS
    OpenHarmony. PolyOS Mobile extends an OpenHarmony reference porting implementation to RISC-V hardware manufacturers and developers. Portability.Missing: PolyPS | Show results with:PolyPS
  77. [77]
    PolyOS Files
    openharmony-spacemit-musepaper.zip, 548.0 MiB, 2024-Nov-07 09:15 ; polyos-mobile-3.2-beta2.img.tar.xz, 220.6 MiB, 2023-Aug-31 08:00 ; polyos-mobile-3.2-beta2.img.Missing: PolyPS | Show results with:PolyPS
  78. [78]
    en/device-dev/dev-board-on-the-master.md · OpenHarmony/docs - Gitee
    ### Supported Development Boards, Hardware Platforms, Chipsets, and Developer Kits for OpenHarmony
  79. [79]
    Raspberry Pi 4B development board obtains OpenHarmony ...
    Feb 8, 2024 · In the latest edition, the Raspberry Pi 4B development board gained the OpenHarmony compatibility certificate. Eventually, the device platform ...Missing: developer HiSilicon
  80. [80]
    47 new products qualified for OpenHarmony compatibility test in ...
    Jul 15, 2024 · The device list includes development boards, development kits, tablets, routers, cameras, smartphones, tablets, watches, robots, and more.<|separator|>
  81. [81]
    Analysis of OpenHarmony's Contribution to the Digital ...
    Dec 23, 2024 · 2.1.2 Development History of OpenHarmony. Since Huawei donated the basic capabilities of HarmonyOS to the OpenAtom Foundation in September 2020, ...<|separator|>
  82. [82]
    China tests home-grown OS in space to reduce foreign dependence
    Jun 21, 2025 · Yu's team implemented the OpenHarmony RTOS on three critical subsystems of the Lianli satellite: the magnetometer, sun sensor, and attitude ...
  83. [83]
    China successfully tests home-grown OS in space to reduce foreign ...
    Jun 21, 2025 · After launching into the orbit, the Dalian-1 Lianli CubeSat spent over 1,000 hours testing satellite subsystems powered by OpenHarmony real-time ...
  84. [84]
    iSoftStone, Together with Its Subsidiary SWANLINK, Successfully ...
    Feb 4, 2024 · This solution is based on the OpenHarmony intelligent in-vehicle terminal, vehicle supervision system, and third-party dynamic monitoring ...
  85. [85]
    SwanLink Released the First SwanLinkOS Transportation Software ...
    SwanLinkOS transportation software adapts to OpenHarmony 3.1 Release version, and supports domestic Rockchip RK3399, RK3568 and other mainstream chips. It ...Missing: automotive | Show results with:automotive
  86. [86]
    Eclipse Oniro for OpenHarmony | projects.eclipse.org
    Eclipse Oniro for OpenHarmony is built upon the foundational layers of OpenHarmony, an open-source project incubated and operated by the OpenAtom Foundation.
  87. [87]
    OpenHarmony Downstream / Upstream relationship - Oniro Project
    For Eclipse Oniro, a downstream OpenHarmony distribution, the primary focus is to ensure well integrated and tested features from and for partners. The ...
  88. [88]
    Oniro Project
    React Native extends the usability of existing applications and ecosystems on top of OpenHarmony, enabling seamless integration across platforms. Eclipse Kanto ...
  89. [89]
    eclipse-oniro4openharmony/third_party_kanto: Kanto integration for ...
    This project outlines the process for integrating third-party services, specifically Kanto and Mosquitto, into the Oniro-OpenHarmony build system.<|separator|>
  90. [90]
    Collaborative Approaches to License Compliance OpenHarmony ...
    Nov 17, 2024 · It is a project of the OpenAtom Foundation, which is a non ... Collaborative Approaches to License Compliance OpenHarmony and Eclipse Oniro ...
  91. [91]
    Oniro Projects
    Eclipse Oniro For OpenHarmony. Built on OpenHarmony, Oniro extends its core with global-ready components like React Native and the Servo web engine, among ...<|separator|>
  92. [92]
    Oniro at the Open Harmony Technical Forum
    Apr 8, 2025 · But that's where the collaboration between the Eclipse Foundation and Open Atom Open Source Foundation comes in. Oniro, built on OpenHarmony, is ...
  93. [93]
    Understanding What HarmonyOS Adds to OpenHarmony
    Jun 28, 2025 · Huawei open-sourced the foundational capabilities of HarmonyOS and donated them to the OpenAtom Open Source Foundation, officially establishing ...
  94. [94]
    HarmonyOS, HarmonyOS Next, OpenHarmony and Oniro Explained
    Oct 13, 2024 · In this article we provide an overview of the ecosystem around this new operating system and provide some background on the different initiatives.Missing: adoption | Show results with:adoption
  95. [95]
    How much of the inherited HarmonyOS technologies is ... - Reddit
    Aug 17, 2025 · HarmonyOS is ~90% open at the app stack level vs. Android's ~60%, making it the more developer-friendly choice for open ecosystems. HarmonyOS is ...Missing: differences overlaps
  96. [96]
    A first look at app security on HarmonyOS NEXT - Promon
    May 20, 2025 · We did an initial technical analysis to determine if it is feasible and useful to protect Harmony OS NEXT apps.
  97. [97]
    https://www.youtube.com/watch?v=bT1zhi26Ang
  98. [98]
    Key Features - openEuler Docs
    The distributed soft bus system (DSoftBus) of openEuler Embedded integrates the DSoftBus and point-to-point authentication module of OpenHarmony, implementing ...<|separator|>
  99. [99]
    Distributed Data Management - OpenEuler Docs
    Distributed data management is ported from the upstream OpenHarmony 3.2 Release. It consists of the following components. Component, openEuler Software Package ...
  100. [100]
    FangTian for Wayland and OpenHarmony Applications | Docs
    The FangTian window engine integrates multiple application ecosystems, allowing Linux and OpenHarmony applications to run on openEuler simultaneously.
  101. [101]
    Expanding the Ecosystem Through Distributed Soft Bus
    DSoftBus is an open source communication base for distributed devices developed by the OpenHarmony community. It enables unified distributed communication ...Missing: 1.0 | Show results with:1.0
  102. [102]
    openEuler Monthly Bulletin – September
    Sep 30, 2024 · This framework has been extended to include an HMI domain through the integration of OpenHarmony. Hoperun, in collaboration with the ...
  103. [103]
    OpenHarmony - Wikipedia
    History. The first version of OpenHarmony was launched by the OpenAtom Foundation on September 10, 2020, after receiving a donation of the open-source code ...
  104. [104]
    Openness, Collaboration, and Shared Success - About Huawei
    By the end of 2024, the OpenHarmony community has attracted more than 8,100 individual contributors, over 70 organization contributors, and more than 390 ...Missing: statistics | Show results with:statistics
  105. [105]
    Huawei Launches Tiangong Initiative to Invest USD141 Million in ...
    Sep 22, 2025 · OpenHarmony has attracted more than 9,200 contributors and has launched over 1,300 software and hardware products spanning sectors such as ...
  106. [106]
    https://gitee.com/openharmony
  107. [107]
    OpenHarmony: OpenHarmony是由开放原子开源基金会（OpenAtom Foundation）孵化及运营的开源项目，目标是面向全场景、全连接、全智能时代，搭建一个智能终端设备操作系统的框架和平台，促进万物互联产业的繁荣发展。
    ### Summary of OpenHarmony (https://gitee.com/openharmony)
  108. [108]
    Huawei Launches “Tiangong Plan,” Pledging About $140 Million to ...
    Sep 22, 2025 · Huawei launches a $140M “Tiangong Plan” to boost AI-native apps and agents for HarmonyOS; HarmonyOS 5 has surpassed 17M devices.
  109. [109]
    [PDF] Huawei Entity List Frequently Asked Questions (FAQs)
    Dec 3, 2020 · BIS added Huawei Technologies Co., Ltd. (Huawei) and many of its non-U.S. affiliates to the. Entity List effective May 16, 2019 on the basis ...
  110. [110]
    Addition of Entities to the Entity List - Federal Register
    May 21, 2019 · Huawei will be listed on the Entity List under the destination of China. This final rule also adds to the Entity List sixty-eight non-U.S. ...
  111. [111]
    https://torrestradeadvisory.com/huawei-entity-list-guide/
  112. [112]
    Huawei Entity List Guide - Torres Trade Advisory
    Effective August 19, 2019, BIS added an additional 46 non-U.S. Huawei affiliates to the Entity List, claiming that these entities also posed a significant risk ...
  113. [113]
    Huawei HarmonyOS breaks tech blockade imposed by US sanctions
    Nov 4, 2024 · In May 2019, the U.S. Department of Commerce added Huawei to the Entity List, barring it from doing business with U.S. firms including Google, ...
  114. [114]
    House Select Committee Calls on Non-Profit to Answer for Its ...
    Jun 5, 2025 · A letter to the Eclipse Foundation raising serious concerns regarding the non-profit's support of HarmonyOS, OpenHarmony, and collaborations with the OpenAtom ...Missing: incubation | Show results with:incubation
  115. [115]
    CVE-2024-37030 Detail - NVD
    Description. in OpenHarmony v4.0.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps through use after free.Missing: backdoors audit findings
  116. [116]
    Huawei launches first laptops using home-grown HarmonyOS
    There is no public evidence that Chinese consumer tech has ever been used to spy for the Chinese government. None. Meanwhile, the USA has been caught running ...<|separator|>
  117. [117]
    Block Huawei's HarmonyOS together with US allies, lawmakers urge
    May 16, 2025 · WASHINGTON -- Huawei Technologies' HarmonyOS operating system could be used by China for espionage, and the U.S. government should work with ...Missing: OpenHarmony | Show results with:OpenHarmony
  118. [118]
    https://arstechnica.com/gadgets/2021/02/harmonyos-hands-on-huaweis-android-killer-is-just-android/
  119. [119]
    Huawei's HarmonyOS: “Fake it till you make it” meets OS development
    Feb 2, 2021 · The OpenHarmony repo uses Huawei's LiteOS IoT microkernel, and the apps in the repo are not Android apps. The HarmonyOS 2.0 emulator, because it ...Missing: derivation allegations
  120. [120]
    https://newsroom.eclipse.org/eclipse-newsletter/2024/january/oniro-versatile-vendor-neutral-operating-system-platform-smart
  121. [121]
    Oniro: A Versatile, Vendor Neutral Operating System Platform for ...
    Jan 29, 2024 · The Oniro IP toolchain serves as a vital mechanism for reducing risks associated with software development. This includes a rigorous ...Missing: fork | Show results with:fork
  122. [122]
    https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1602
  123. [123]
    [oniro] Request for resources for discussing security issues/potential ...
    Jul 28, 2022 · Summary. The Oniro Core team and Compliance Toolchain team need ways to discuss security issues and potential IP violations.Missing: concerns | Show results with:concerns
  124. [124]
    Stumped in the West, Huawei Targets Emerging Markets - EE Times
    Huawei is setting its sights on other markets. A recent announcement positions the company to take advantage of a continent where smartphones only account for ...Missing: stigma | Show results with:stigma
  125. [125]
    HarmonyOS (1 Billion+) and OpenHarmony (100 million+) are on an ...
    Aug 20, 2025 · OMH (Open Mobile Hub) Linux Foundation Europe Project: HarmonyOS (1 Billion+) and OpenHarmony (100 million+) are on an estimated 1.1 billion ...Open source HarmonyOS, OpenHarmony goes global! Cooperating ...Why I don't believe in HarmonyOS NEXT global success? : r/HuaweiMore results from www.reddit.com
  126. [126]
    HarmonyOS Next applications has reached 20,000 and 10 billion ...
    Jan 13, 2025 · The goal for 2025 is to develop 100000 applications, thus strengthening the Huawei + OpenHarmony ecosystem.
  127. [127]
    Comparison of HarmonyOS vs. Android and iOS - Netizen
    Jun 2, 2025 · HarmonyOS Next's independence from Android makes it a distinct platform, but its app ecosystem is less mature than Android's Play Store or iOS' ...
  128. [128]
    Software Engineering for OpenHarmony: A Research Roadmap
    We present to the mobile software engineering community a research roadmap for encouraging our fellow researchers to contribute promising approaches to ...
  129. [129]
    Forging a Global, Secure, and Compliant Ecosystem for Smart Devices
    Sep 12, 2025 · The OpenHarmony Technical Conference in Florence on September 3, 2025, served as a pivotal gathering, showcasing a vibrant and rapidly ...
  130. [130]
    Can open source secure Europe's digital infrastructure?
    Aug 25, 2025 · Another example is OpenHarmony, the open source core of Huawei's HarmonyOS. After US sanctions cut Huawei's access to key components, China ...
  131. [131]
    Practical Experience Sharing on OpenHarmony 5.0.0 Release ...
    This article shares practical testing experiences with OpenHarmony 5.0.0 and outlines the compatibility testing process, along with useful tips and precautions.Missing: suite | Show results with:suite
  132. [132]
    On-Orbit Validation of the OpenHarmony Real-Time Operating ...
    Aug 8, 2025 · Main technical parameters and scientific objectives of the Dalian-1 Lianli satellite mission. 3D, 3-dimensional; HAN, hydroxylamine nitrate. …
  133. [133]
    [PDF] Design and Performance Optimization of an Intelligent Cockpit ...
    This study designs and implements an intelligent cockpit system based on OpenHarmony. By constructing a three-layer distributed architecture and mathematical ...Missing: benchmarks | Show results with:benchmarks
  134. [134]
    [PDF] Interim Report 2025
    Aug 25, 2025 · As a leading distribution product based on OpenHarmony – the first full-scenario open-source operating system – KaihongOS is specifically ...
  135. [135]
    [PDF] Microkernel Goes General: Performance and Compatibility in the ...
    Jul 10, 2024 · Flexibilized: Prioritize performance by providing structural supports for flexible ... of tradeoffs between isolation and performance according to.
  136. [136]
    "Deep Blue Insight" is the most unique new security ecology in 2024
    Feb 8, 2025 · The implementation of new defense mechanisms and the rise of new attack technologies will profoundly change the landscape of digital security.Missing: integration | Show results with:integration
  137. [137]
    The Most Groundbreaking New Security Ecosystem of 2024
    Feb 8, 2025 · Compared to the Linux kernel, it achieves a notable enhancement in security, albeit with a slight performance trade-off. However, it is ...
  138. [138]
    Number of connected IoT devices growing 13% to 18.8 billion globally
    Sep 3, 2024 · IoT Analytics expects this to grow 13% to 18.8 billion by the end of 2024. This forecast is lower than in 2023 due to continued cautious enterprise spending.
  139. [139]
    Open Source Oniro App Store is a game changer
    Feb 11, 2025 · Gathering from a recent developer tutorial video in Chinese, OpenHarmony is compatible with HarmonyOS Next projects and vice versa, so you don't ...
  140. [140]
    HarmonyOS: Huawei's OS venture, challenges, and potential global ...
    Apr 18, 2024 · Huawei's investment in HarmonyOS is expected to significantly boost China's tech industry, potentially creating at least 3 million jobs.Missing: implications | Show results with:implications
  141. [141]
    How China's self-sufficiency drive is dividing the global tech ...
    May 8, 2025 · China is rapidly advancing its technological self-sufficiency in semiconductors and biotechnology, a trend accelerated by escalating trade tensions with the US.
  142. [142]
    [PDF] 2024 Annual Report - Huawei
    Mar 26, 2025 · OpenHarmony and openEuler. By the end of. 2024, the OpenHarmony community has attracted more than 8,100 individual contributors, over. 70 ...