OpenHarmony 3.2 Beta2

Version Description

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

Enhanced basic capabilities for the standard system

Added the multi-hotspot distribution mechanism for the window.

Added the restart recovery mechanism for power management.

Added the stylus pressure and tilt in events, and added key input support for multimodal input.

Added the preset application pre-authorization mechanism and fingerprint enrolling/authentication/identification framework to the security domain.

Added selfie mirroring in recording mode, audio control and audio effect control, infrared device input, audio USB insertion/removal identification, and event reporting to the driver.

Enhanced application framework capabilities for the standard system

The ability allows addition of static and dynamic widgets, startup of abilities that are not locally installed, SA-initiated ability startup and access, singleton ability continuation, sandbox application opening during running management, and no display of system application abilities in the latest mission list.

Bundle management provides NDK interfaces for obtaining the bundle name and certificate fingerprint information of the current bundle, querying the pack information of a specified application, and aging and uninstalling atomic services.

Application development samples for the standard system

Added samples such as Gobang, QR code generation and parsing, widget usage, multimedia, short video, and facial recognition, helping developers quickly use basic capabilities of OpenHarmony.

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-Beta2 --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-Beta2 --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-Beta2 --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-Beta2 --no-repo-verify
  repo sync -c
  repo forall -c 'git lfs pull'
  

Acquiring Source Code from Mirrors

Table 2 Mirrors for acquiring source code

What's New

This version has the following updates to OpenHarmony 3.2 Beta1.

SDK Updates

From this version onwards, both the Public SDK and Full SDK are provided. The Public SDK is provided as standard in DevEco Studio.

If an application developed using the SDK of an earlier version calls system APIs, you must manually switch to the Full SDK by following the instructions provided in Guide to Switching to Full SDK after the version upgrade. This operation ensures successful build of your application project.

Feature Updates

Table 3 New and enhanced features

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