1# OpenHarmony 4.0 Beta2 2 3## Version Description 4 5The standard system capabilities of OpenHarmony 4.0 are continuously improved. ArkUI further enhances the capabilities of basic components. The application framework supports ArkTS widget updates triggered by agents. The bundle manager subsystem supports data sharing across atomic services, as well as enterprise application installation. The DSoftBus subsystem supports session-level transmission capability negotiation. The Unified Data Management Framework (UDMF) supports temporary authorization for files in distributed directories in cross-device dragging scenarios. The file management subsystem supports device-cloud synchronization of public image files. The multimedia subsystem further enhances the audio, media playback, and audio/video codec capabilities. The graphics rendering library is upgraded to Skia 0310. The window component capability is enhanced. The common event and notification subsystem supports batch notification deletion. The security subsystem supports Digital Signature Algorithm (DSA). ArkCompiler Runtime supports JSContext and dynamic profile guided optimization (PGO). DFX provides a unified collection framework for easier application debugging. 6 7## Feature Description 8 9 10### Application Framework 11 12- The content of an ArkTS widget can be updated through a data agent. 13 14- Static configuration and static graph display are provided for ArkTS widgets. 15 16 17### ArkUI 18 19- **\<XComponent>** supports texture rendering. Popup positions can be customized, and popups can be closed layer by layer by pressing the **Esc** key. The **\<ListItem>** component supports the swipe-to-delete gesture, which means that users can long swipe left to delete an element. ArkTS/JS widgets support callbacks triggered upon the completion of rendering. The **\<Image>** and **\<Text>** components support obscuring. The **\<ContextMenu>** component supports segment-based display. 20 21- The animation effect is enhanced, including the layout attribute, background image size and position, and show/hide attribute (implicit animation). **scrollToIndex** can be used to set animation effects for lists. Fuzzy animations are provided for tabs, and display/disappearance animations are provided for popups. Custom animations are also supported. 22 23- Named routes are supported so that page-specific switching animations can be set. The lite ArkUI framework supports global data objects and data sharing between pages within an application. 24 25- Global APIs support the stage model multiton scenario. 26 27 28### Bundle Management 29 30- APIs are provided to set and query the application distribution type and attachment information. 31 32- Applications that can open a file are identified through the file name extension, implementing the mapping between a file name extension and an application. 33 34- Enterprise applications can be installed. To install an application whose certificate type is **enterprise**, you must request the **ohos.permission.INSTALL_ENTERPRISE_BUNDLE** permission. 35 36 37### Distributed Data Management 38 39- The UDMF supports temporary authorization for files in distributed directories in cross-device dragging scenarios. 40 41- RDB store NDK interfaces are provided. These interfaces are used for transaction addition, deletion, modification, and query, data encryption, hierarchical data protection, and backup and restore. 42 43- The system can automatically select a Bluetooth or Wi-Fi P2P channel for synchronization of key-value and distributed data objects based on the data volume. 44 45 46### DSoftBus 47 48- Management of soft bus link information is supported. 49 50- Cross-device transmission capability negotiation is provided at the session level. 51 52 53### Distributed Hardware 54 55- The audio recording latency in distributed scenarios is optimized. 56 57- The distributed file system supports mutual file access over Bluetooth P2P connections. 58 59- A listener can be provided to listen for device name changes. 60 61 62### File Management 63 64- Public image files can be synchronized between the device and cloud (on the prerequisite that the cloud service is enabled for the login account of the device). Images on the cloud can be selected through the picker. 65 66- Applications can customize the directories to be backed up. 67 68- Public images can be managed by category. Users can classify user images through albums in Gallery. 69 70- Applications can listen for the addition, modification, and deletion of files in the sandbox. 71 72- Applications can share files in the sandbox across devices. 73 74 75### Graphics & Window 76 77**Graphics** 78 79- APIs are provided to pick the color of a selected region in an image. Applications can use the APIs to select a region in an image and obtain its dominant color and average color value. 80 81- APIs are provided to set the offset of the rotation center on the z-axis anchor point so that the rendered anchor point can be modified during rotation. 82 83- The rendering library on which the graphics subsystem depends is upgraded to Skia 0310. 84 85**Window** 86 87- The way for obtaining the parameter values of the display module is optimized. Now actual parameter values are directly obtained from the hardware instead of the software. 88 89- The window component capability is enhanced. The window supports window attributes, child windows, modal windows, window effects, window decoration, screen-on/screen-off, screenshot, and screen recording in component mode. 90 91 92### Multimedia 93 94**Audio** 95 96- The sound effect framework is supported. Device vendors can configure sound effect policies and load custom sound effects. Applications can query, switch, or disable the sound effect mode. 97 98- Intra-system recording is supported. Audio data played in the system can be filtered and recorded based on the audio scene attribute. 99 100- The display name of the audio output device can be obtained from the playback object information. 101 102**Media Playback** 103 104Audio effect parameters can be configured. 105 106**Audio/Video Codecs** 107 108- Native APIs can be used to query the audio and video codecs of the system. 109 110- Native APIs can be used to encapsulate audio and video data, that is, to store encoded media data in files in a certain format. 111 112- Native APIs can be used to decapsulate audio and video data, that is, to extract media frame data from bit stream data. 113 114 115### Common Event and Notification 116 117- Notifications can be deleted in batches. 118 119- The emitter supports unsubscription of condition-specific callbacks. 120 121 122### Basic Communications 123 124- The Wi-Fi module supports background scanning. 125 126- The Wi-Fi module supports random MAC addresses in STA mode. 127 128 129### Network and Communication 130 131- A TCP socket can be used for communication with the server. 132 133- Data transfer to a remote server is supported. 134 135- HTTPS certificate management adaptation is supported. 136 137- The NIC proxy is supported. 138 139 140### System Service Management 141 142- System services can be started as required, for example, called by external systems or triggered by events. System services can be automatically stopped when the device is idle. 143 144- The system service configuration format is optimized by using the JSON format instead of the XML format. 145 146 147### Power Supply 148 149- New APIs are provided to enable the system to enter the sleep state immediately. 150 151- Events and behavior can be customized based on the hibernation source. 152 153- Wakeup events can be customized based on the wakeup source. 154 155 156### Multimodal Input 157 158- Original events of keyboard input devices are mapped to the intent event of normalized interaction, so that you do not need to pay attention to whether the input behavior comes from the touch or keyboard during application development. 159 160- Users can customize the touchpad based on their use habits. 161 - Both the press and touch actions can be used to map a click on the left mouse button. 162 - Both of the following actions can be used to map a right-click on the mouse: touching the left or lower right corner, and pressing or touching the left or lower right corner with two fingers. 163 - 10 speed levels are supported. 164 - Both of the following actions can be used to map a scroll with mouse: content moving in the same direction as your finger moves, and content moving in the reverse direction as your finger moves. 165 166 167### Theme Framework 168 169- The lock screen management service supports lock screen event callbacks, static/dynamic wallpaper, and service status query when the screen is locked. 170 171- The wallpaper management service allows users to customize and reset wallpapers, and lock/unlock the screen. 172 173 174### Upload and Download 175 176Users can query upload and download tasks, synchronize and query task status, persistently store task records, and rectify exceptions. 177 178 179### Security 180 181**Crypto Framework** 182 183- DSA is supported. 184 185- APIs are provided to parse DSA, Elliptic Curve Cryptography (ECC), and Rivest Shamir Adleman (RSA) keys and obtain key parameters. 186 187- APIs are provided to obtain the algorithm type used to generate random numbers. 188 189- APIs are provided to randomly generate, convert, encrypt, and decrypt SM4 keys. 190 191- The Hash-based Message Authentication Code (HMAC) and hash capabilities are provided for SM3 keys. 192 193- APIs are provided to randomly generate, convert, sign, verify, encrypt, and decrypt SM2 keys. 194 195**Key Management** 196 197- HUKS key encryption is supported. 198 199- The service identity field of the key can be added to the Key Attestation public key certificate. 200 201- Standard HDIs are provided. 202 203**Mutual Authentication Between Devices** 204 205Pseudonyms can be generated and identified in the following scenarios: 206 207- Mutual authentication on multiple devices that use the same account to log in 208 209- Mutual authentication on two devices that are connected in P2P mode using different accounts 210 211 212### Ability Access Control 213 214- The display of the permission management menu is optimized. The permission groups of media assets and files are split, and the authorization granularity of corresponding permissions is more refined. 215 216- Compatibility with SELinux in the Treble architecture is supported. 217 218 219### Account 220 221- Third-party applications can use the account authorization capability. 222 223- Management on domain account plugins is provided to support domain account management and authentication. 224 225 226### WebView 227 228- The web camera capability and HTML5 tag capabilities such as bindContextMenu, Select, and date input are supplemented. 229 230- Multiple rendering processes can be split. 231 232- Basic text and image dragging capabilities are provided. 233 234- WebRTC video conferencing (excluding camera sharing) is supported. 235 236- Independent SELinux labels are provided for rendering processes to enhance basic security. 237 238 239### ArkCompiler 240 241- ArkCompiler Runtime supports JSContext and dynamic PGO, which collects type and function hotspot information at runtime and generates AP files. The NAPI library can be dynamically imported and loaded. 242 243- In type compilation mode of ArkCompiler, the front-end compilation toolchain is switched to es2abc. 244 245- New APIs are provided for the NAPI buffer, object, arraybuffer, and object types. 246 247- The task pool supports task interruption and cancellation, task group definition, task status and scheduling information dotting, and identification and recovery of tasks that wait for a long time. 248 249- Different versions can be built for system users and user **root**. The user version supports Wukong and XTS. 250 251- The compiler toolchain supports debugging of the previewer. 252 253 254### DFX 255 256- A unified collection framework is provided for application debugging. 257 258- Unified trace collection is provided. 259 260- Native HiTraceMeter APIs are provided. 261 262- The performance radar provides tool classes for service modules (subsystems) to transfer performance tracing point records and settlement performance data in service processes. 263 264 265### Kernel 266 267Code execution permission control is enhanced as follows: 268 269- Secure memory is supported. 270 271- Scenario-specific code execution permission control policies are provided. 272 273- Full lifecycle management is provided for code execution permission control. 274 275- Executable files can be parsed to obtain code segment information. 276 277- Integrity protection is provided for code pages. 278 279 280### Driver 281 282- The extended device driver framework provides the following capabilities: 283 - Based on the DriverExtensionAbility, the extended device driver framework builds lifecycle management capabilities, including developing, deploying, installing, updating, uninstalling, and running extended driver packages in the application state. 284 - USB device extension driver packages that are developed by third-party device vendors and do not comply with standard protocols can be installed on OpenHarmony devices. After such a USB device is inserted, the system can identify it and matches an extension driver package. 285 - Third-party applications can query and bind to a USB device extension driver package through the extended device management framework. 286 287- The camera driver provides the following capabilities: 288 - Identifying USB camera hot swap events during startup check and after startup. 289 - Preview, photographing, and video recording of USB cameras, and query and configuration of the camera format and resolution. 290 291- The codec driver provides hardware decoding acceleration for JPEG images, including obtaining hardware decoding information, initializing and deinitializing instances, decoding JPEG images, and applying for and releasing a buffer. 292 293- The sensor driver provides driving for temperature and humidity sensors. It supports the query of temperature and humidity components of small-system devices, component enabling/disabling, and data query. 294 295 296## Version Mapping 297 298**Table 1** Version mapping of software and tools 299 300| Software/Tool| Version| Remarks| 301| -------- | -------- | -------- | 302| OpenHarmony | 4.0 Beta2 | NA | 303| Public SDK | Ohos_sdk_public 4.0.9.6 (API Version 10 Beta2) | 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.| 304| (Optional) HUAWEI DevEco Studio| 4.0 Beta2 | Recommended for developing OpenHarmony applications How to obtain:<br><br>SHA-256 checksum: ae9b228fb1f79e99441e10bdcf347ebfc42266be8b170bbce3c9764ba32d82a4<br><br>SHA-256 checksum: 5c9afc5b1262868b58376155f1e8576d33c1ade8b01091edc4d7d397cd34026c<br><br>SHA-256 checksum: ea6c98cafd5036e4a6fd46b0b1cde3a306953b1eef423d5940f1af7c632205d6 | 305| (Optional) HUAWEI DevEco Device Tool| 4.0 Beta1 | Recommended for developing OpenHarmony smart devices How to obtain:<br>[Click here to go to the download page](https://device.harmonyos.com/cn/develop/ide#download).| 306 307 308## Source Code Acquisition 309 310 311### **Prerequisites** 312 3131. Register your account with Gitee. 314 3152. Register an SSH public key for access to Gitee. 316 3173. 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. 318 319 ``` 320 git config --global user.name "yourname" 321 git config --global user.email "your-email-address" 322 git config --global credential.helper store 323 ``` 324 3254. Run the following commands to install the **repo** tool: 326 327 ``` 328 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. 329 pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests 330 ``` 331 332 333### Acquiring Source Code Using the repo Tool 334 335**Method 1 (recommended)** 336 337Use the **repo** tool to download the source code over SSH. (You must have an SSH public key for access to Gitee.) 338 339- 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: 340 ``` 341 repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-4.0-Beta2 --no-repo-verify 342 repo sync -c 343 repo forall -c 'git lfs pull' 344 ``` 345 346- Obtain the source code from the version tag, which is the same as that released with the version. 347 ``` 348 repo init -u git@gitee.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v4.0-Beta2 --no-repo-verify 349 repo sync -c 350 repo forall -c 'git lfs pull' 351 ``` 352 353**Method 2** 354 355Use the **repo** tool to download the source code over HTTPS. 356 357- 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: 358 ``` 359 repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony-4.0-Beta2 --no-repo-verify 360 repo sync -c 361 repo forall -c 'git lfs pull' 362 ``` 363 364- Obtain the source code from the version tag, which is the same as that released with the version. 365 ``` 366 repo init -u https://gitee.com/openharmony/manifest -b refs/tags/OpenHarmony-v4.0-Beta2 --no-repo-verify 367 repo sync -c 368 repo forall -c 'git lfs pull' 369 ``` 370 371 372### Acquiring Source Code from Mirrors 373 374**Table 2** Mirrors for acquiring source code 375 376| Source Code | Version| **Site** | **SHA-256 Checksum** | Software Package Size| 377| --------------------------------------- | ------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | -------- | 378| Full code base (for mini, small, and standard systems) | 4.0 Beta2 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/code-v4.0-Beta2.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/code-v4.0-Beta2.tar.gz.sha256)| 27.7 GB | 379| Hi3861 solution (binary) | 4.0 Beta2 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_pegasus.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_pegasus.tar.gz.sha256)| 27.5 MB | 380| Hi3516 solution-LiteOS (binary)| 4.0 Beta2 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_taurus_LiteOS.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_taurus_LiteOS.tar.gz.sha256)| 300.9 MB | 381| Hi3516 solution-Linux (binary) | 4.0 Beta2 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_taurus_Linux.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/hispark_taurus_Linux.tar.gz.sha256)| 192.4 MB | 382| RK3568 standard system solution (binary) | 4.0 Beta2 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/dayu200_standard_arm32.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/dayu200_standard_arm32.tar.gz.sha256)| 5.2 GB | 383| Public SDK package for the standard system (macOS) | 4.0.9.6 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/ohos-sdk-mac-public.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/ohos-sdk-mac-public.tar.gz.sha256)| 832.3 MB | 384| Public SDK package for the standard system (macOS-M1) | 4.0.9.6 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/L2-SDK-MAC-M1-PUBLIC.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/L2-SDK-MAC-M1-PUBLIC.tar.gz.sha256)| 788.4 MB | 385| Public SDK package for the standard system (Windows\Linux) | 4.0.9.6 | [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/ohos-sdk-windows_linux-public.tar.gz)| [Download](https://repo.huaweicloud.com/openharmony/os/4.0-Beta2/ohos-sdk-windows_linux-public.tar.gz.sha256)| 2.0 GB | 386 387 388## What's New 389 390This version has the following updates to OpenHarmony 4.0 Beta1. 391 392### API 393 394For details about the API changes over OpenHarmony 4.0 Beta1, see [API Differences](https://gitee.com/openharmony/docs/blob/OpenHarmony-4.0-Beta2/en/release-notes/api-diff/v4.0-beta2/Readme-EN.md). A few API changes may affect applications developed using API version 9 or earlier. For details about the change impact and adaptation guide, see [Changelogs](https://gitee.com/openharmony/docs/blob/OpenHarmony-4.0-Beta2/en/release-notes/changelogs/v4.0-beta2/Readme-EN.md). 395 396 397### Feature Updates 398 399[Version Description](#version-description) 400 401### Chip and Development Board Adaptation 402 403For details about the adaptation status, see [SIG_DevBoard](https://gitee.com/openharmony/community/blob/master/sig/sig_devboard/sig_devboard.md). 404 405 406### Samples 407 408**Table 3** New samples 409 410| Subsystem| Name| Introduction| Programming Language| 411| -------- | -------- | -------- | -------- | 412| Connectivity| [Upload and Download](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/BasicFeature/Connectivity/UploadAndDownLoad)| This sample uses the **\@ohos.request** APIs to create and query upload and download tasks. In this sample, an HTTP File Server (HFS) functions as the server.| ArkTS | 413| File management| [Application Access Data Backup and Restore](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/BasicFeature/FileManagement/FileBackupExtension)<br>(Full SDK)| The BackupExtensionAbility enables an application to access the backup and restore framework.<br>**BackupExtensionAbility** is a derived class of **ExtensionAbility** in the stage model. You can modify the configuration file to customize the backup and restore framework behavior, including whether to allow backup and restore and specifying the files to be backed up.<br>This sample provides an application for the backup process to generate and display data.| ArkTS | 414| Common event and notification| [Custom Badge](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/BasicFeature/Notification/CustomNotificationBadge)| This sample shows how to use the **\@ohos.notificationManager** APIs to set a badge on the home screen and send and obtain notifications.| ArkTS | 415| Common event and notification| [Custom Notification Push](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/BasicFeature/Notification/CustomNotificationPush)<br>(Full SDK)| This sample shows how to use the **\@ohos.notificationManager** APIs to listen for callbacks to determine whether to send notifications. It implements notification filtering callback management.| ArkTS | 416| NDK | [Native Xcomponent](https://gitee.com/openharmony/applications_app_samples/tree/master/code/BasicFeature/Native/NdkXComponent)<br>(Native SDK)| This sample shows how to use the native XComponent interface to obtain a **NativeWindow** instance, obtain the layout/event information, register an event callback, and draw shapes on the page through OpenGL/EGL. In this sample application, you can click the button to draw a pentagon and click the XComponent area to change the pentagon color.| Native C++ | 417| Application Model| [Data Agent Widget - Database Update](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/SystemFeature/ApplicationModels/PersistentProxyForm)<br>(Full SDK)| This sample shows a data agent widget. It uses the **\@ohos.application.DataShareExtensionAbility**, **\@ohos.data.dataShare**, and **\@ohos.data.dataSharePredicates** APIs to implement widget content updates along with RDB changes after widget subscription information is modified.| ArkTS | 418| Application Model| [Data Agent Widget - Push Application Update](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/SystemFeature/ApplicationModels/ProcessProxyForm)<br>(Full SDK)| This sample shows how to use the data agent widget in the push application form. It uses the **\@ohos.data.dataShare** APIs to modify subscription conditions of the data agent widget and publish the widget data.| ArkTS | 419| Application Model| [Edit Application](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/SystemFeature/ApplicationModels/Receiver)| This sample implements simple sharing, including sharing cancellation and completion, based on the UIExtension. In the sample application, you can touch **Return Share** to return to the calling application; you can also touch **Stay Edit App** to stay in the current application.| ArkTS | 420| Application Model| [Initiating Application Sharing](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/SystemFeature/ApplicationModels/Share)<br>(Full SDK)| This sample implements the initiation of sharing through the **Share** button. It provides two application icons: share demo and share edit. You can touch one of them to initiate sharing and redirect to the corresponding application.| ArkTS | 421| Application Model| [Text Application](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-4.0-Beta2/code/SystemFeature/ApplicationModels/Template)<br>(Full SDK)| This sample implements simple sharing, including sharing cancellation and completion, based on the UIExtension. In the sample application, you can touch **Return Share** to return to the calling application; you can also touch **Stay Share Text** to stay in the current application.| ArkTS | 422 423For more information, visit [Samples](https://gitee.com/openharmony/applications_app_samples). 424 425 426## Resolved Issues 427 428**Table 4** Resolved issues 429 430| Issue No.| Description| 431| -------- | -------- | 432| I6U4ZT | The first photo in Gallery cannot be opened when the power supply is disconnected immediately after the photo is taken.| 433| I79752 | There is a medium probability that the .ohos.smartperf thread of the com.ohos.smartperf process causes a C++ crash in libark_jsruntime.so.| 434| I79P3K | There is a low probability that the onDestroy stack encounters a JS crash in the com.ohos.callui process.| 435| I79TCB | There is a low probability that the VizCompositorTh thread of the com.ohos.note process causes a C++ crash in libweb_engine.soTh.| 436| I78CBC | Memory leakage occurs in libace.z.so when a user touches an image folder in Gallery to browse images in grid form and then exits repeatedly.| 437| I78CH7 | Memory leakage occurs in libace.z.so when applications are repeatedly added to or removed from the dock bar.| 438 439 440## Known Issues 441 442**Table 5** Known issues 443 444| Issue No.| Description| Impact| To Be Resolved By| 445| -------- | -------- | -------- | -------- | 446| I78C9W | Memory leakage occurs in libace.z.so when a user touches an image in Gallery to maximize it and then exits repeatedly.| This operation scenario is uncommon, and the leak issue disappears after the application is restarted. The impact is controllable.| 2023-08-30| 447| I7BF3M | During the long-term running test, the launcher process occasionally encounters app freezing because STRINGID:APPLICATION_BLOCK_INPUT is stuck in libeventhandler.z.so.| This issue does not cause the system to restart. The impact is controllable.| 2023-08-30| 448| I7M51R | There is a low probability that a C++ crash occurs in the render_service thread of the com.ohos.systemui process.| The render_service thread will restart automatically. The impact is controllable.| 2023-08-30| 449| I7NWF3 | Due to compatibility issues, the session fails to be enabled for a Wi-Fi P2P connection between a device running 3.2.x and a device running 4.0.x. | This issue does not occur when both devices run 4.0.x. The impact is controllable. | 2023-08-30 | 450| I7BOAO | Multiple GLES3 test cases of the third-party repository fail to be executed. | The third-party vendor is carrying out adaptation. | 2023-08-30 | 451