OpenHarmony 3.2 Beta5

Version Description

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

Enhanced basic capabilities for the standard system

The startup performance of the WebView component is optimized. Configuration management and input event support capabilities are enhanced. JSON files can be imported and loaded in modular mode.

The task pool and the TS2AOT-tool of the host version are provided. The dynamic library of the HAP package can be loaded without being compressed. The compiler runtime supports shared packages in the same application.

The dynamic shared library can be installed, updated, uninstalled, packed, and unpacked. For an application that is not configured with an entry icon, a default icon is displayed on the home screen. The runtime capability of the HAR shared package can be verified.

The local database is changed for widgets. Protection against frequent restart is provided for applications. The ServiceExtensionAbility component supports the asynchronous onConnected lifecycle.

Binding and authentication between local accounts and domain accounts are supported. A basic framework is provided for domain account management services. Direct creation of local users is forbidden.

The capabilities for controlling power indicators and lights are provided.

The HDI driver display layer supports horizontal mirroring and vertical mirroring.

Enhanced application development framework for the standard system

The process of compiling the shared package is added to the toolchain.

ArkUI supports obtaining of resources by resource name.

The component supports multi-level menus and group menus.

The process of compiling the HAR package is added.

The HAP compilation process is adapted so that .d.ets declaration files can be identified during HAP compilation.

Enhanced distributed capabilities for the standard system

BLE connection parameters can be configured, and the connection process is optimized.

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-Beta5 --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-Beta5 --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-Beta5 --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-Beta5 --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 Beta4.

SDK Updates

From this version on, only the public SDK is released. You can obtain the public SDK from the mirror or download it from DevEco Studio for your application development.

To use the full SDK that contains system APIs, you must download the full code, compile and build an SDK file, and switch to the full SDK on DevEco Studio. For details about how to compile the full SDK using the source code, see Full SDK Compilation Guide.

Feature Updates

Table 3 New and enhanced features

For details about the API changes, see API Differences.

For details about the API changes of each subsystem, see Changelogs.

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