1# OpenHarmony 5.0.1 Release 2 3 4## Version Description 5 6OpenHarmony 5.0.1 Release continuously improves the capabilities of the standard system, rolling out API 13 via quick iteration. Compared with 5.0.0 Release, OpenHarmony 5.0.1 Release has the following new or enhanced features: 7 8The C API capabilities are enriched, including but not limited to application queries of the application framework, ArkTS node customization, preferences data management, file management, AVSession integration, event notification, and toggle queries for Wi-Fi, Bluetooth, and location features, as well as cellular network-related capability and pasteboard management. Other improvements include camera enhancements with a wider range of shooting modes and optimizations to **Web** component functionalities. 9 10A more detailed description of the enhancements is as follows: 11 12 13### Application Framework 14 15- New ArkTS and C APIs are introduced for creating application child processes. 16 17- C APIs are added to obtain application information like the cache path, file encryption settings, and bundle name. 18 19- Adjustment of application-level font scaling is supported. 20 21 22### ArkUI 23 24- C API functionalities are enhanced for custom node attributes and ArkTS capabilities to access custom attributes of any target node. 25 26- The **Navigation** component now allows for customizable title bar positions and font styles for main titles and subtitle. The **NavDestination** component allows you to set the style of the bottom toolbar and control its visibility status. 27 28- Multiple components have been adapted for aging-friendly design, adjusting font sizes and component dimensions in line with system aging-friendly settings. Involved components include **Dialog**, **SeletTitleBar**, **SwipeRefresher**, **SplitLayout**, **ComposeTitleBar**, **ExceptionPrompt**, **TreeView**, **Filter**, **GridObjectSortComponent**, **ProgressButton**, **ToolBar**, and **TabTitleBar**. 29 30- The **RichEditor** component has been enhanced with features such as scrollbar visibility settings, image drag-and-drop support, and a more comprehensive set of shortcut keys. 31 32 33### Bundle Manager 34 35- New C APIs are added to query the MainElement information. 36 37- Third-party HAR now supports the retrieval of startup **want** parameters for launching the host application. 38 39 40### Distributed Data Management 41 42AC APIs are added to obtain, store, and delete preferences key-value data. 43 44 45### File Management 46 47- C APIs are now available for applications to obtain file names (including extensions) or the names of the last folder based on an URI. 48 49- Backup and restore are now supported for applications leveraging the application clone feature. 50 51 52### Graphics and Window Manager 53 54**Graphics** 55 56- C APIs are added to the Pixelmap module for manipulating the color space. 57 58- NativeImage now provides APIs to define the default read/write mode and preset sizes for geometric shapes. 59 60- When a UIAbility transitions to the background, animations with a set number of loops stops and invoke a complete callback, whereas those set to loop indefinitely continues regardless of whether the UIAbility is running in the foreground or background. 61 62**Window Manager** 63 64System applications can now proactively request focus. 65 66 67### Media 68 69**Audio** 70 71- C APIs are added to facilitate basic interaction with AVSession. 72 73- The error codes in the casting scenario are refined. 74 75- The device information attributes returned during casting are improved. 76 77**Camera** 78- General lens control features have been expanded to include lens cleanliness checks, tripod detection, and ring light compensation control. 79 80- Capabilities specific to foldable screen lenses have been introduced, allowing for the reporting of front and rear lens statuses based on the device's folding state and enabling automatic lens switching. 81 82- The feature of capturing HDR photos in HEIF format is introduced. 83 84- Cloud-based enhancements for shooting effects are integrated into the system. 85 86- The video segmentation feature is supported. After a video recording operating, a video is quickly generated for preview purposes, which is subsequently deleted once a high-quality video is processed and stored in Gallery, thereby optimizing preview performance. 87 88- The system now supports camera metadata detection, which supports detection and reporting of smiles, human faces, human eyes, cat eyes, and dog eyes. 89 90- The capability of outputting depth stream and photographic depth data is added. 91 92**Image** 93 94The picture type is added. The picture type allows the decoding of certain images with special information into multi-image objects. Multi-image object encoding and decoding and primary and secondary image management are supported. It applies to JPEG and HEIC images. 95 96 97### Common Event and Notification 98 99- C APIs are added to query the notification enabling status and subscribe to and unsubscribe from common events. 100 101- Applications can now start the system's semi-modal notification setting page. 102 103 104### Communications 105 106C APIs are introduced for checking the on/off status of Wi-Fi and Bluetooth. 107 108 109### Location 110 111C APIs are added to query the on/off status of geolocation, initiate and terminate location services, and report locations. 112 113 114### Telephony Service 115 116- C APIs are added to obtain the camping information of cellular networks, including the network registration status and access mode. 117 118- C APIs are added to obtain information about the default data SIM card. 119 120 121### Power Supply 122 123- The system can now obtain the current charging current, introducing the **nowCurrent** API for this purpose. 124 125- The airplane mode can be associated with temperature control. You can customize a temperature control policy to enable the device to enter the airplane mode. 126 127- The WorkSource proxy running lock can assist the resource scheduler in power consumption control. 128 129- Devices in a low-battery state can now automatically transition to a deeper sleep state (S4) after being woken up from a lighter sleep state (S3), facilitating extended standby periods. 130 131 132### Startup 133 134APIs are provided to query distributionOsApiName to obtain API version information. 135 136 137### ArkCompiler 138 139- ASON can parse strings and return collections.Map. 140 141- Template-based TaskPool APIs are optimized to refine return value structures, eliminating the need for explicit type conversion. 142 143 144### Multimodal Input 145 146- Key values are added to support custom common events for screen reading. 147 148- The system can now detect the consecutive pressing of the power button five times as a combined operation. 149 150- Event listening for the power and volume buttons is now supported. 151 152- APIs for querying and configuring infrared frequencies are now provided. 153 154 155### Resource Scheduler 156 157The VoIP continuous task type is introduced, allowing for audio and video call services even when the application is running in the background. 158 159 160### Pasteboard 161 162- C APIs are added to copy and paste multiple types of data and report cross-device data changes. 163 164- The system can now check whether the pasteboard contains data in a specific format. 165 166 167### Web 168 169- The capability to obtain the current scrolling offset of a web page is now available. 170 171- The WebResourceResponse object can check whether the response data is ready for the following data types: string, number, ArrayBuffer, and object. 172 173 174## Version Mapping 175 176**Table 1** Version mapping of software and tools 177 178| Software/Tool| Version| Remarks| 179| -------- | -------- | -------- | 180| OpenHarmony | 5.0.1 Release | NA | 181| Public SDK | Ohos_sdk_public 5.0.1.111 (API Version 13 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.| 182| (Optional) HUAWEI DevEco Studio| 5.0.1 Release | Recommended for developing OpenHarmony applications| 183| (Optional) HUAWEI DevEco Device Tool| 4.0 Release | Recommended for developing OpenHarmony smart devices| 184 185 186## Source Code Acquisition 187 188 189### Prerequisites 190 1911. Register your account with Gitee. 192 1932. Register an SSH public key for access to Gitee. 194 1953. Install the [git client](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) and [git-lfs](https://gitee.com/vcs-all-in-one/git-lfs?_from=gitee_search#downloading), and configure user information. 196 ``` 197 git config --global user.name "yourname" 198 git config --global user.email "your-email-address" 199 git config --global credential.helper store 200 ``` 201 2024. Run the following commands to install the **repo** tool: 203 ``` 204 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. 205 pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests 206 ``` 207 208 209### Acquiring Source Code Using the repo Tool 210 211**Method 1 (recommended)** 212 213Use the **repo** tool to download the source code over SSH. (You must have an SSH public key for access to Gitee.) 214 215- 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: 216 ``` 217 repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-5.0.1-Release --no-repo-verify 218 repo sync -c 219 repo forall -c 'git lfs pull' 220 ``` 221 222- Obtain the source code from the version tag, which is the same as that released with the version. 223 ``` 224 repo init -u git@gitee.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v5.0.1-Release --no-repo-verify 225 repo sync -c 226 repo forall -c 'git lfs pull' 227 ``` 228 229**Method 2** 230 231Use the **repo** tool to download the source code over HTTPS. 232 233- 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: 234 ``` 235 repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony-5.0.1-Release --no-repo-verify 236 repo sync -c 237 repo forall -c 'git lfs pull' 238 ``` 239 240- Obtain the source code from the version tag, which is the same as that released with the version. 241 ``` 242 repo init -u https://gitee.com/openharmony/manifest -b refs/tags/OpenHarmony-v5.0.1-Release --no-repo-verify 243 repo sync -c 244 repo forall -c 'git lfs pull' 245 ``` 246 247 248### Acquiring Source Code from Mirrors 249 250 251**Table 2** Mirrors for acquiring source code 252 253| Source Code | Version| Mirror | SHA-256 Checksum | Software Package Size| 254| --------------------------------------- | ------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | -------- | 255| Full code base (for mini, small, and standard systems) | 5.0.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/code-v5.0.1-Release.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/code-v5.0.1-Release.tar.gz.sha256) | 42.7 GB | 256| Hi3861 solution (binary) | 5.0.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_pegasus.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_pegasus.tar.gz.sha256) | 27.2 MB | 257| Hi3516 solution-LiteOS (binary)| 5.0.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_taurus_LiteOS.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_taurus_LiteOS.tar.gz.sha256) | 328.4 MB | 258| Hi3516 solution-Linux (binary) | 5.0.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_taurus_Linux.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/hispark_taurus_Linux.tar.gz.sha256) | 221.1 MB | 259| RK3568 standard system solution (binary) | 5.0.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/dayu200_standard_arm32.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/dayu200_standard_arm32.tar.gz.sha256) | 12.7 GB | 260| Public SDK package for the standard system (macOS) | 5.0.1.111 | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/ohos-sdk-mac-public.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/ohos-sdk-mac-public.tar.gz.sha256) | 1.3 GB | 261| Public SDK package for the standard system (macOS-M1) | 5.0.1.111 | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/L2-SDK-MAC-M1-PUBLIC.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/L2-SDK-MAC-M1-PUBLIC.tar.gz.sha256) | 1.2 GB | 262| Public SDK package for the standard system (Windows/Linux) | 5.0.1.111 | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/ohos-sdk-windows_linux-public.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/5.0.1-Release/ohos-sdk-windows_linux-public.tar.gz.sha256) | 2.5 GB | 263 264 265## Resolved Issues 266 267**Table 3** Resolved issues 268 269| Issue No.| Issue Description | 270| -------- | -------- | 271| I9S5ZN | There is a low probability that app freezing occurs in libunwind.z.so due to THREAD_BLOCK_6S in the com.ohos.settings process.| 272| I9S600 | There is a low probability that app freezing occurs in libark_jsruntime.so due to THREAD_BLOCK_6S in the com.ohos.settings process.| 273| IAB2U3<br>IAK2J2 | There is a low probability that a C++ crash occurs in libaudio_client.z.so of the OS_APAsyncRunne thread of the audio_server process.| 274| IAIRFB | There is a low probability that a C++ crash occurs in libweb_engine.so of the com.ohos.note thread of the com.ohos.note process.| 275| IAKLLD | There is a low probability that a C++ crash occurs in libaudio_policy_service.z.so of the SaInit2 thread of the audio_server process.| 276| IA56CU | There is a low probability that a C++ crash occurs in libweb_engine.so of the com.ohos.note thread of the com.ohos.note process.| 277| IA5AMJ | There is a low probability that app freezing occurs in libark_jsruntime.so due to THREAD_BLOCK_6S in the com.ohos.launcher process.| 278| IA5AIT | There is a low probability that system freezing occurs in render_service due to SERVICE_BLOCK.| 279| IA6RFX | There is a high probability that a C++ crash occurs in libbtservice.z.so of the OSaInit0 thread in the bluetooth_service process.| 280| IA8KGR | There is a low probability that a C++ crash occurs in libbluetooth_server.z.so of the OS_IPC_12_22172 thread of the bluetooth_service process.| 281| IAQC64 | Randomly open several applications and then open the Settings application. When you return to the home screen and repeatedly access the background interface, the Settings application may encounter a memory leakage of 32 KB for each operation.| 282| IASE04 | In the memory test of OpenHarmony on the RK3568 development board, the resident memory of the render_service process exceeds the baseline (31 MB).| 283 284## Known Issues 285 286**Table 4** Known issues 287 288| Issue No. | Issue Description | Impact| To Be Resolved By| 289| -------- | -------- | -------- | -------- | 290| I9SXZ8 | There is a low probability that app freezing occurs in libark_jsruntime.so due to THREAD_BLOCK_6S in the com.ohos.contacts process.| The application freezes when you open the Contacts application to query call records. This issue can be resolved by restarting the Contacts application.| December 15| 291| IA6RH6 | There is a high probability that app freezing occurs in libbtframework.z.so due to THREAD_BLOCK_6S in the com.ohos.settings process.| The Settings application might not respond. This issue can be resolved by restarting the Settings application.| December 15| 292| IASDWO | The sliding frame rate for accessing the Weibo home page through a browser is lower than the specification baseline.| Browsing experience is affected.| December 15| 293| IAZYOO | The RK3568 development board frequently encounters freezing issues during the WuKong comprehensive random pressure testing.| The SystemUI process fails to log main thread activities for a long period of time, and the absence of multi-modal event distributions on the lock screen side contributes to this problem. This issue can be resolved by pressing the power button. It has limited impact on users, and therefore no specific workaround is necessary.| December 15| 294| IANQF3 | There is a high probability that the system restarts during the WuKong pressure test.| This issue leads to the device restarting<br>and is currently not preventable.| December 15| 295| IB4L3E | There is a high probability that app freezing occurs in libcamera_framework.z.so due to LIFECYCLE_TIMEOUT in the com.ohos.camera process.| This issue is caused by the camera_host process. Restart the app to resolve the issue.| December 15| 296| IAP85P | There is a low probability that a process with a low startup priority is terminated preferentially, resulting in a system freeze.| This can lead to the application being shut down, but restarting the application can address the issue.| December 15| 297| I9SXZ8 | There is a low probability that app freezing occurs in libark_jsruntime.so due to THREAD_BLOCK_6S in the com.ohos.contacts process.| This issue occurs because the Contacts application is stuck in the **windowStage.loadContent()** API. Restarting the application can resolve the issue.| December 15| 298| IB36B2 | There is a low probability that a JS crash occurs in the com.ohos.mms process, and the problem stack is identified as close.| This issue may cause the Messaging application to exit unexpectedly. Restarting the application can resolve the issue.| December 15| 299