harmony 鸿蒙OpenHarmony 4.0.2 Release

  • 2025-06-12
  • 浏览 (5)

OpenHarmony 4.0.2 Release

Version Overview

OpenHarmony 4.0.2 Release provides enhanced system security over OpenHarmony 4.0.1 Release by rectifying memory leak issues, certain known vulnerabilities in open-source components such as Linux kernel, and system stability issues.

Version Mapping

Table 1 Version mapping of software and tools

Software/Tool Version Remarks
OpenHarmony 4.0.2 Release NA
Public SDK Ohos_sdk_public 4.0.11.4 (API Version 10 Release) This toolkit is intended for application developers and does not contain system APIs that require system permissions. It is provided as standard in DevEco Studio.
(Optional) HUAWEI DevEco Studio 4.0 Release Recommended for developing OpenHarmony applications How to obtain:

SHA-256 checksum: 2c88cf43e1ef6ba722aac31eccc8ef92f07a9b72e43a9c1df127017828a22137

SHA-256 checksum: 25e491458eec50b4abddf5bed6aa85893801d70afbce02958f17bd904619405a

SHA-256 checksum: 284cb01f7b819e0da1d4fcacbbbbe8017ba220b5e3b9b1d5e4cc59ea30456acc
(Optional) HUAWEI DevEco Device Tool 4.0 Release Recommended for developing OpenHarmony smart devices
Click here.

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-4.0.2-Release --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-v4.0.2-Release --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-4.0.2-Release --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-v4.0.2-Release --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull'

Acquiring Source Code from Mirrors

Table 2 Mirrors for acquiring source code

Source Code Version Mirror SHA-256 Checksum Software Package Size
Full code base (for mini, small, and standard systems) 4.0.2Release Download Download 30.5 GB
Hi3861 solution (binary) 4.0.2Release Download Download 27.3 MB
Hi3516 solution-LiteOS (binary) 4.0.2Release Download Download 302.5 MB
Hi3516 solution-Linux (binary) 4.0.2Release Download Download 193.2 MB
RK3568 standard system solution (binary) 4.0.2Release Download Download 5.2 GB
Public SDK package for the standard system (macOS) 4.0.11.4 Download Download 2.0 GB
Public SDK package for the standard system (macOS-M1) 4.0.11.4 Download Download 800.7 MB
Public SDK package for the standard system (Windows/Linux) 4.0.11.4 Download Download 1.1 GB

What’s New

This version has the following updates to OpenHarmony 4.0.1 Release.

API Changes

N/A

Chip and Development Board Adaptation

For details about the adaptation status, see SIG_DevBoard.

Resolved Issues

Table 4 Resolved issues

Issue No. Description
IA7RFU [OpenHarmony 4.0.11.3] A C++ crash occurs on libhdf_host.z.so due to an error of the IPC_0_583 thread of the composer_host process. This issue occurs 263 times.
IA50TF [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_vdi_impl.z.so due to an error of the IPC_0_600 thread of the composer_host process. This issue occurs 98 times.
IA4VWD [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_service_1.0.z.so due to an error of the IPC_0_651 thread of the composer_host process. This issue occurs 99 times.
IA4VOG [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_service_1.0.z.so due to an error of the IPC_0_611 thread of the composer_host process. This issue occurs 1207 times.
I9UD63 [OpenHarmony 4.0.11.1] App freezing occurs on getTimeDetailByCallTime of the com.ohos.contacts process. This issue occurs 11 times.
I9D96I [OpenHarmony 4.0.10.18] The input method is not automatically displayed when a user touches the search box.
I9BN09 [OpenHarmony 4.0.10.18] App freezing occurs due to THREAD_BLOCK_6S in the com.ohos.photos process. This issue occurs 10 times.
I97K8F [OpenHarmony 4.0.10.16] The LiteOS DSoftBus process cannot be started.
IA8XY1 [OpenHarmony 4.0.11.4] A JS crash occurs on isFolderMoveIn of the com.ohos.note process. This issue occurs once.
IA8ORN [OpenHarmony 4.0.11.4] A C++ crash occurs on libipc_core.z.so due to an error of the IPC_0_625 thread of the softbus_server process. This issue occurs 17 times.
IA8HPZ [OpenHarmony 4.0.11.3] The WLAN status cannot be synchronized on the Settings screen after WLAN is enabled and disabled on the Settings screen.
IA56NT [OpenHarmony 4.0.11.2] A JS crash occurs on unregisterObserver of the com.ohos.settings process. This issue occurs once.
IA52Z3 [OpenHarmony 4.0.11.2] A C++ crash occurs on libclang_rt.ubsan_minimal.so due to an error of the IPC_0_623 thread of the composer_host process. This issue occurs 5 times.
IA52VP [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_stub_1.0.z.so due to an error of the IPC_0_610 thread of the composer_host process. This issue occurs 22 times.
IA52OZ [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_vdi_impl.z.so due to an error of the OS_IPC_1_635 thread of the composer_host process. This issue occurs twice.
IA52FF [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_vendor.z.so due to an error of the IPC_1_613 thread of the composer_host process. This issue occurs once.
IA5292 [OpenHarmony 4.0.11.2] A C++ crash occurs on libhdf_ipc_adapter.z.so due to an error of the IPC_0_628 thread of the composer_host process. This issue occurs 45 times.
IA521D [OpenHarmony 4.0.11.2] A C++ crash occurs on libhilog.so due to an error of the IPC_1_588 thread of the composer_host process. This issue occurs 13 times.
IA51QG [OpenHarmony 4.0.11.2] A C++ crash occurs on libipc_single.z.so due to an error of the IPC_1_592 thread of the composer_host process. This issue occurs 3 times.
IA51KP [OpenHarmony 4.0.11.2] A C++ crash occurs on libnative_rdb.z.so due to an error of the os.settingsdata thread of the com.ohos.settingsdata process.
IA51AZ [OpenHarmony 4.0.11.2] A C++ crash occurs on libdisplay_composer_vdi_impl.z.so due to an error of the OS_IPC_1_626 thread of the composer_host process. This issue occurs 11 times.
IA513N [OpenHarmony 4.0.11.2] A C++ crash occurs on libnative_appdatafwk.z.so due to an error of the os.settingsdata thread of the com.ohos.settingsdata process. This issue occurs 18 times.
I9UF1I [OpenHarmony 4.0.11.1] A C++ crash occurs on libhdifd_parcelable.z.so due to an error of the IPC_1_625 thread of the composer_host process.
I9UESA [OpenHarmony 4.0.11.1] A C++ crash occurs on libdlp_permission_sdk.z.so due to an error of the ffrtwk/CPU-2-0 thread of the foundation process. This issue occurs once.
I9TPH7 [OpenHarmony 4.0.11.1] A JS crash occurs on updateActionBar of the com.ohos.photos process. This issue occurs once.
I9TNOU [OpenHarmony 4.0.11.1] The inForm parameter of the hap-sign-tool.jar tool is case insensitive.
I9PITC [OpenHarmony 4.0.10.18] When the indentation of the text in a memo is adjusted, saved, and the application is closed, the text appears without indentation upon reopening.
I9K8ZD [OpenHarmony 4.0.10.18] A C++ crash occurs on libdevicemanagerserviceimpl.z.so due to an error of the TimerRunning thread of the device_manager process. This issue occurs once.
I96SJG [OpenHarmony 4.0.10.17] A JS crash occurs on unregisterObserver of the com.ohos.settings process. This issue occurs once.
I920DA [OpenHarmony 4.0.10.16] A JS crash occurs on AirplaneVM of the com.ohos.systemui process. This issue occurs once.

Fixed Security Vulnerabilities

Table 4 Fixed security vulnerabilities

Issue No. Description
IA9LC2 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36939
I9PJJN [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26733
I9QZR5 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-27004
I9QZC7 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52467
I9QZB8 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26903
I9QZ9J [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-27399
I9QW5Y [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-51794
I9QW30 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2017-14058
I9Q65G [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-51793
I9Q1NE [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26862
I9Q1MT [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52462
I9OGPC [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-24863
I9OEZF [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-46887
I9NQVB [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26601
I9JE1E [Vulnerability] [OpenHarmony 4.0 Release] CVE-2022-2078
I9JDLS [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-4001
I9H4QZ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-0450
I9FXHF [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52160
I9COE3 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52498
I9BU69 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-25739
I952TO [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-24858
I950WP [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-24857
IA7RSP [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47469
IA7RR1 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52835
IA7RQS [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52879
IA7RQM [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52868
IA7RQC [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52739
IA7ROX [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52869
IA7AZ7 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35896
IA7AVQ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52781
IA7AUA [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52832
IA7A6Q [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36017
IA7A60 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35822
IA74VS [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52881
IA74RP [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36883
IA49BH [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-39375
I9UNOT [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-4906
I9QZQO [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-27038
I9QZQB [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26801
I9QZCJ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26923
I9PJK7 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26735
I9PJJT [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26805
IA4BSA [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36899
IA47RY [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36904
I9TCEQ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26934
I9TCE6 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47479
I9TCBI [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47506
I9TCAM [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47485
I9TC9P [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47483
I9TC7F [Vulnerability] [OpenHarmony 4.0 Release] CVE-2021-47474
I9OU4P [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26885
I9OU4C [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26883
I9OU42 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26884
I9OU3J [Vulnerability] [OpenHarmony 4.0 Release] CVE-2022-48655
I9O3RW [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-31578
I9JNCO [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52436
I9H4LS [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-6597
IA7RS0 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36929
IA7RRT [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36941
IA7RPQ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35984
IA7RPD [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52730
IA7ROQ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36008
IA7RO9 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35997
IA7BIZ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36901
IA7B91 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36903
IA7B81 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35904
IA7B1I [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-27414
IA7B0N [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35955
IA7AY5 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35969
IA7AXC [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35962
IA7AV3 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-35789
IA7AT2 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36940
IA7A45 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52803
IA7A3F [Vulnerability] [OpenHarmony 4.0 Release] CVE-2023-52791
IA74SA [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36938
IA74RC [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36905
IA74QZ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-36902
IA6W5Z [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-48514
I9RKKZ [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-31755
I9QZSH [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26852
I9QZS8 [Vulnerability] [OpenHarmony 4.0 Release] CVE-2024-26901

Known Issues

Table 5 Known issues

Issue No. Description Impact To Be Resolved By
/ / / /

你可能感兴趣的鸿蒙文章

harmony 鸿蒙OpenHarmony 1.0 (2020-09-10) (EOL)

harmony 鸿蒙OpenHarmony 1.1.0 LTS (2021-04-01) (EOL)

harmony 鸿蒙OpenHarmony 1.1.1 LTS (2021-06-22) (EOL)

harmony 鸿蒙OpenHarmony 2.0 Canary (2021-06-01)

harmony 鸿蒙OpenHarmony v1.1.3 LTS (EOL)

harmony 鸿蒙OpenHarmony 1.1.4 LTS (EOL)

harmony 鸿蒙OpenHarmony v1.1.2 LTS (EOL)

harmony 鸿蒙OpenHarmony 1.1.5 LTS (EOL)

harmony 鸿蒙OpenHarmony v2.2 Beta2

harmony 鸿蒙OpenHarmony 3.0 LTS

0  赞
  • 所属分类： 后端技术
  • 本文标签：
  • 版权声明： 原创文章如转载，请注明本文链接: https://m.seaxiang.com/blog/7VUPc8
热门推荐
标签云
Linux Java Spring Spring Boot docker 大数据 前端 生活 maven golang 软件 spring cloud fintech mac vscode 其他 区块链 以太坊 V神 开发者 技术 股票 git greenplum 分布式事务 chrome mysql flink kafka 设计模式 原理 鸿蒙 seo
最新文章
本文目录