OpenHarmony 3.2 Beta4

Version Description

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

Enhanced basic capabilities for the standard system

The program access control subsystem supports forward-edge Control Flow Integrity (CFI) and provides enhanced API exception handling.

The kernel subsystem provides enhanced HyperHold memory expansion and F2FS device performance optimization.

The multimodal input subsystem allows applications to enable or disable keys on the keyboard and supports multi-hotspot related to input devices.

The graphics subsystem supports graphics data transmission based on shared memory, YUV graphics layers, GPU compositing on RenderService, and rotation and dynamic resolution of the virtual screen.

The update subsystem supports A/B hot updates, and A/B partition device updates for flashd and SD/OTG.

The globalization subsystem supports on-demand subscription of device management events, overlay differentiation of system resources, and cross-OS resource management.

The Misc services subsystem supports file upload in PUT mode, download task configuration, input method framework optimization and enhancement, and printing service framework.

The DFX subsystem supports collection of power consumption data, system event data, and perf data.

ArkTS APIs support error code reporting, which delivers higher exception handling efficiency.

Enhanced application development framework for the standard system

Dynamic library isolation is supported, and applications to be disposed can be interrupted during runtime management.

Window property setting and ArkTS widget interaction are supported. The <XComponent> provides the container component capability.

Application dependencies can be configured. The list of installed and uninstalled applications can be added, deleted, and queried. The list of applications that are forbidden to run can be added, deleted, and queried.

Enhanced distributed capabilities for the standard system

The distributed hardware supports the request and import of credential parameters of the same account.

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

Acquiring Source Code from Mirrors

Table 2 Mirrors for acquiring source code

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
   

What's New

This version has the following updates to OpenHarmony 3.2 Beta3.

Feature Updates

Table 3 New and enhanced features

Chip and Development Board Adaptation

For details about the adaptation status, see SIG_DevBoard.

Samples

The following samples written in ArkTS are added.

Table 4 New samples

For more information, visit Samples.

Resolved Issues

Table 5 Resolved issues

Known Issues

Table 6 Known issues