OpenHarmony 3.2 Beta3

Version Description

OpenHarmony 3.2 Beta3 provides the following enhancements over OpenHarmony 3.2 Beta2:

Enhanced basic capabilities for the standard system

The pan-sensor subsystem adds vibrator priority management.

The multimodal input subsystem adds mouse pointer style and speed setting, configuration of sequential ability startup, and ScreenHop; and enhances mouse event reporting.

The Misc services subsystem adds the following basic features: pasteboard, upload and download, screen lock, and input method framework.

The kernel subsystem adds the following basic capabilities: memory level notification to Ability Manager Service (AMS), reclaim priority management for resident system services, and reclaim priority management based on different Extension ability states.

In the Design For X (DFX) subsystem, the faultloggerd component supports print in the hybrid JS and native stacks; the hilog component provides domain trustlist management and log statistics; the hisysevent and hiappeventssh components provide enhanced event capabilities; the hidumper component provides more detailed memory classification information.

The parameterized data driver capability is added to the unit test framework. APIs related to fling and complex gestures (such as two-finger pinch) are added to the UI test framework. The xdevice component adds device-level DFX log collection upon task execution.

The multi-language runtime subsystem adds the following capabilities: ES2021 in strict mode, modularization, runtime debugging and tuning enhancement, and bytecode hot reload.

User identity authentication is added to the IAM account subsystem. The permission service supports precise positioning and fuzzy positioning, and other capabilities are enhanced. The privacy management service is provided.

The multimedia subsystem adds native APIs for audio decoding, audio encoding, video decoding, and video encoding; audio and video synchronization; playback start time optimization; video hardware encoding and decoding based on the HDI codec interface; distributed audio, volume, and device status management; device listening and projection; preview, photographing, and video recording using distributed cameras.

Enhanced application development framework for the standard system

The common event and notification subsystem provides DLP adaptation. Subsystems can send notifications.

The webview component supports copy and paste. Basic audio/video playback and HTTPS bidirectional authentication are supported.

Permission verification, startup rules, and quick repair are added for the ability framework, and widgets can be flexibly separated and combined.

The following capabilities are enhanced: ArkUI component, resource and media query, DFX, and toolchain. The memory and performance are optimized.

The DeviceProfile subsystem supports adaptation to the automatic synchronization policy of the distributed database and supplements the type of information that can be collected.

For the bundle management framework, Extension abilities are added for the thumbnail and preview. Certain features become tailorable. Foolproof and quick repair are added. Specific capabilities of preset applications can be managed. Applications can be installed without decompressing HAP files.

For the system ability management subsystem (SAMGR), system services can be loaded across devices. The restart and recovery mechanism is provided for the foundation process. Distributed component management supports multi-user, cross-device invoking. Singleton ability continuation is supported.

Enhanced distributed capabilities for the standard system

The distributed database supports cross-device and cross-application sharing. The relational database (RDB) supports remote query, database encryption, and app twin. The KVDB supports backup and restore, condition-based synchronization, and centralized system data synchronization when the device goes online.

Version Mapping

Table 1 Version mapping of software and tools

Source Code Acquisition

Prerequisites

1. Register your account with Gitee.

2. Register an SSH public key for access to Gitee.

3. Install the git client and git-lfs, and configure user information.

   git config --global user.name "yourname"
   git config --global user.email "your-email-address"
   git config --global credential.helper store
   

4. Run the following commands to install the repo tool:

   curl -s https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 > /usr/local/bin/repo  # If you do not have the permission, download the tool to another directory and configure it as an environment variable by running the chmod a+x /usr/local/bin/repo command.
   pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests
   

Acquiring Source Code Using the repo Tool

Method 1 (recommended)

Use the repo tool to download the source code over SSH. (You must have an SSH public key for access to Gitee.)

• Obtain the source code from the version branch. You can obtain the latest source code of the version branch, which includes the code that has been incorporated into the branch up until the time you run the following commands:

  repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.2-Beta3 --no-repo-verify
  repo sync -c
  repo forall -c 'git lfs pull'
  

• Obtain the source code from the version tag, which is the same as that released with the version.

  repo init -u git@gitee.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v3.2-Beta3 --no-repo-verify
  repo sync -c
  repo forall -c 'git lfs pull'
  

Method 2

Use the repo tool to download the source code over HTTPS.

• Obtain the source code from the version branch. You can obtain the latest source code of the version branch, which includes the code that has been incorporated into the branch up until the time you run the following commands:

  repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony-3.2-Beta3 --no-repo-verify
  repo sync -c
  repo forall -c 'git lfs pull'
  

• Obtain the source code from the version tag, which is the same as that released with the version.

  repo init -u https://gitee.com/openharmony/manifest -b refs/tags/OpenHarmony-v3.2-Beta3 --no-repo-verify
  repo sync -c
  repo forall -c 'git lfs pull'
  

Acquiring Source Code from Mirrors

Table 2 Mirrors for acquiring source code

Updates

This version has the following updates to OpenHarmony 3.2 Beta2.

Feature Updates

Table 3 New and enhanced features

For details about the API changes, see the following:

API Differences

Chip and Development Board Adaptation

For details about the adaptation status, see SIG_DevBoard.

Samples

Table 4 New samples

For more information, visit Samples.

Resolved Issues

Table 5 Resolved issues

Known Issues

Table 6 Known issues