OpenHarmony 3.0.5 LTS

Version Description

OpenHarmony 3.0.5 LTS is a maintenance version of OpenHarmony 3.0 LTS. This version has rectified certain issues detected in OpenHarmony 3.0.3 LTS and provides the following capability updates.

Enhanced capabilities for the small system

The DFX subsystem supports native crash information collection and device restart fault locating. The communication subsystem supports basic STA capabilities.

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.)

repo init -u git@gitee.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v3.0.5-LTS --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.

repo init -u https://gitee.com/openharmony/manifest.git -b refs/tags/OpenHarmony-v3.0.5-LTS --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

Feature Updates

Table 3 New and enhanced features

API Updates

This version does not involve API updates.

Chip and Development Board Adaptation

For details about the adaptation status, see SIG_DevBoard.

Resolved Issues

Table 4 Resolved issues

Fixed Security Vulnerabilities

The following vulnerabilities are reported by the project teams. For details about the affected versions and patches released to fix the vulnerabilities, see Security Vulnerability Disclosure.

Table 5 Fixed security vulnerabilities