1# OpenHarmony 4.1 Release 2 3 4## Version Description 5 6With the release of OpenHarmony 4.1 Release, the development suite is upgraded to API Version 11 Release. Compared with OpenHarmony Release 4.0, OpenHarmony 4.1 Release comes with more than 4000 new APIs to enrich your application development capabilities. Open application development capabilities are presented as kits, delivering a clearer logic and scenario-specific perspectives. ArkUI component openness and animation capabilities are further enhanced. Web capabilities are continuously supplemented. Distributed capabilities improve networking stability and connection security. The multimedia subsystem supports richer encoding capabilities and more refined playback control capabilities. You are welcome to use this version and provide valuable suggestions. 7 8You can read this document to learn more about key feature and capability updates provided by this version. 9 10### SDK 11 12The open capabilities provided by the SDK are presented by kit. You can search for and use the capabilities by kit. These scenario-specific capabilities offer a clearer programming logic. 13 14In addition, the development guide and API reference are reconstructed by kit for better understanding and easier use. 15 16 17### ArkUI 18 19- The **\<NodeContainer>** component is provided to enhance custom drawing. 20 21- The text and container components are enhanced as follows: 22 - The **\<TextInput>** and **\<Text>** components support character-based truncation. 23 - The **\<TextInput>** and **\<TextArea>** components support obtaining of the caret position. 24 - Intelligent word segmentation is supported. The logic for inserting the caret based on the word segmentation result is added, and a new word segmentation algorithm is used. 25 - The **\<ImageSpan>** component supports custom long-press menu events as well as component indentation and alignment. 26 - Through **ScrollToIndex**, the **\<List>** component can specify the target list item to scroll to in the list item group. 27 28- The components have the AI access capabilities enhanced as follows: 29 - The **\<TextInput>** component and related text components support visual input. 30 - The **\<Text>**, **\<RichEditor>**, and related text components support text entity recognition. 31 32- Status management is enhanced as follows: 33 - The undefined, null, and union types are supported. 34 - The **\<ListItem>** component can update methods in the **ForEach** and **LazyForEach** attributes. 35 - The **@LocalStorageLink** and **@LocalStorageProp** decorators are not updated when they are not activated. 36 37- The chip component is added. The following components have their style, interaction, and animation enhanced: **\<TextInput>**, **\<TextArea>**, **\<List>**, **\<Grid>**, **\<Search>**, **\<CheckBox>**, **\<Slider>**, **\<Image>**, **\<Menu>**, and semi-modal pop-up are enhanced. 38 39- The customization capability of the pop-up components and navigation components is enhanced as follows: 40 - The rounded corners, shadows, and popup arrows of pop-up menus can be customized. 41 - The **isShow** parameter is added in the **bindContextMenu** method. 42 - The navigation bar in the **\<Navigation>** component can be hidden. 43 - The **\<Navigation>** component provides the function of obtaining detailed information about each page of the route stack and destroying or displaying pages based on the page information. 44 45- New style objects and component style attribute methods are provided to support style reuse and dynamic switching. 46 - The universal attribute style supports **Style** objects. 47 - Component-specific attribute styles support objects derived from **Style**. 48 - The polymorphic style is switched to the **Style** object. 49 50 51### Application Framework 52 53- When an application exits normally, the **temp** directory is cleared to improve security and reduce system storage space consumption. 54 55- Enhanced ExtensionAbility management capabilities: Background management and unified timeout are provided for ServiceExtensionAbilities. 56 57- Enhanced ArkTS widget capabilities: Transparent widgets, data proxy refresh, single-color mode, and lock-screen widgets are added. 58 59 60### Bundle Management 61 62- The system-level HSP supports OTA upgrades. 63 64- A guide is provided to optimize the size of the modular development package. 65 66 67### DSoftBus 68 69- The QoS interface capability is constructed for DSoftBus transmission to better manage bottom-layer link resources and provide route selection decisions, improving distributed service experience. 70 71- The subsystem specifications are continuously enhanced. The connection reliability confirmation capability is added to route selection, and connection parameters can be dynamically set based on resource conditions. 72 73- The DFX mechanism is enhanced. For example, the subsystem supports service process dotting, upper-layer distributed service statistics, and service alarms for network monitoring events. 74 75- The IPC provides APIs for querying reference counts and timestamps, and the maintenance and debugging capabilities are enhanced. 76 77 78### Distributed Data Management 79 80- Standard data definitions and descriptors of the Unified Data Management Framework (UDMF), query of standard data types, data access authorization and management, and application-defined data types are supported. 81 82- Cross-device synchronization is not allowed for data without security levels. 83 84- The preferences data supports modification, query, and persistence of data streams in Uint8Array format. 85 86- An RDB can be created in the subdirectory of the specified application sandbox path. 87 88 89### Graphics and Window Manager 90 91**Graphics** 92 93- The system supports variable frame rates and provides APIs for service access. 94 95- HDR Vivid videos can be rendered and displayed. 96 97- The graphics NDK capability is enhanced. The **OnFrameAvailableListener** callback is provided for native Image APIs. Primary colors can be set for the native window. The OpenGL ES extension APIs are supported, and the drawing capabilities are further enhanced. 98 99- You can specify a window not to be recorded during screen recording. A privacy window can be recorded as a pure black image. 100 101- The system resolution can be adjusted. 102 103- APIs are provided to adjust the system frame rate based on the animation and adjust the application frame rate. 104 105- The animation capability is enhanced. The cut-out and rounded screen are supported, and navigation transition animation supports element sharing. 106 107- The graphics rendering pipeline supports the Vulkan backend. 108 109- The graphics subsystem provides drawing APIs. 110 111- The native window APIs support the metadata setting to adapt to the transmission of dynamic metadata with frames in HDR video scenarios. 112 113**Window Manager** 114 115- Interactive status notifications are provided for the window stage. 116 117- Global search of the window type is supported. 118 119 120### Multimedia 121 122**Audio/Video** 123 124- Calling applications are allowed to access media sessions. 125 126- The color of the AVCastPicker component can be customized, and the component status can be listened. 127 128- Historical albums and playlists of applications can be displayed on the media controller. 129 130- The system supports concurrent playback of multiple audio streams with low latency and dynamic adjustment of the callback frequency and data volume. 131 132- Low-latency audio recording is supported. 133 134- Low-power audio playback is available for music and audiobook applications. 135 136- Audio-haptic is provided to support precise synchronous playback of audio and haptic streams. 137 138- AMR/MKV demuxing and AMR decoding are supported. 139 140- Media information about audio and video files can be obtained. 141 142- The video framework is optimized to reduce resource usage. The AVBuffer is used to support full-process data processing and zero copy. 143 144- Digital Rights Management (DRM) is supported. DRM plug-in management, device certificate request and processing, media key request and processing, and DRM program decryption are supported. 145 146**Image** 147 148- Decoding of .ico images is supported. 149 150- Color setting and CSS parsing of .svg images are supported. 151 152- Color Space Conversion (CSC) between sRGB and P3 during decoding is supported. 153 154**Media Library** 155 156- Object-based read and write interfaces are available for media data. 157 158- Multiple access modes, such as fast, balanced, and high-quality, are provided. 159 160### Camera 161 162- The camera NDK APIs are provided for applications to perform secondary processing on camera data. 163 164- The **CameraPicker** class is provided so that third-party applications can wake up or integrate the photographing and video recording capabilities of the camera. 165 166- The basic camera control capabilities, including smooth zoom and flashlight, are enhanced. 167 168- Camera performance is enhanced for smoother switching between the front and rear cameras and between taking photos and recording videos. 169 170 171### Common Event and Notification 172 173- System applications are allowed to send live view notifications. 174 175- Emitter supports subscription by string type. The serializable data type is supported for data to be transferred in events. The number of subscribers can be obtained. 176 177- Applications can receive only custom common events released by themselves. 178 179 180### Utils 181 182- Worker threads can be created in the HAR or HSP. 183 184- The task pool can send messages to the host thread during execution. 185 186 187### Connectivity 188 189- NFC provides Host-based Card Emulation (HCE). 190 191- NFC supports the configuration of the default payment application. 192 193- APIs are provided to check whether the currently connected Wi-Fi hotspot is a mobile phone hotspot. 194 195- APIs are provided to add the STA device connected to a Wi-Fi hotspot to the blocklist. 196 197 198### Location 199 200- APIs are provided for geocoding, reverse geocoding, and geocoding service status query. 201 202 203### Power Supply 204 205- The code structure of **DisplayPowerManager** is adjusted. The brightness management module is changed to an independent module. 206 207- An animation with the updatable battery level is displayed during the charging of a device in the powered-off state. 208 209 210### Security 211 212- Certificate management: The CA certificate path is opened. 213 214- Certificate framework: Certificate chain verification, revocation check, and certificate chain construction are supported. 215 216- The crypto framework supports the PBKDF2 algorithm, optional AAD parameters for symmetric keys, variable-length key HMAC, DH/25519 algorithm, Brainpool curve, SM2 key parsing and parameter processing, and curve name-based key generation. 217 218### Access Control 219 220**Permission Management** 221 222- A permission dialog box can be displayed on a UIExtensionAbility page. 223 224- Screen lock status records are added to permission usage records. 225 226- The option of allowing permissions can be displayed when an application is in use. 227 228### ArkCompiler 229 230- The dynamic import capability supports variables as parameters. 231 232- Runtime APIs are provided for instrumentation and replacement of class methods. 233 234- The number sign (#) can be used to declare private members of a class. 235 236- Cross-thread serialization is provided for the **Sendable** class. 237 238- The TSC is upgraded from 4.2.3 to 4.9.5. 239 240- The incremental compilation speed is enhanced for ArkTS applications. 241 242- The obfuscation function is enhanced. File names and folder names can be obfuscated. Comments in declaration files can be deleted. Exportable object names and their attribute names can be obfuscated. 243 244- libc: Security hardening interfaces such as **dlopen** and **dlclose** are added, and multi-thread reentrant is supported. The performance of some frequently used C APIs is optimized. The following lib interfaces are added to the DK: random number arc4random*, stack-related backtrace, shared memory shm_open, and shell mode matching wordexp. The header files **execinfo.h**, **queue.h**, and **cdefs.h** are supported. 245 246- C++ debugging: The debugging speed in scenarios such as application startup and .so loading is optimized. Standalone LLDB debugging is supported. 247 248 249### Resource Manager 250 251- Resource indexes can be added through the shortcut menu in the **module.json** file. 252 253- The **resfile** directory can be packaged and compiled. 254 255- The resource ID can be obtained based on the resource name. 256 257 258### USB 259 260- The USB device management capability is supplemented. The USB service can be enabled or disabled for all devices or a given device, or by device type. In addition, the disabling policy can be persistent in restart and hot swap scenarios. 261 262- The USB service authentication mode is optimized by adding access control permissions and refining the permissions of system services and system applications to call the USB service. 263 264- The vulnerabilities of the bulk transfer and control transfer interfaces are fixed. Interfaces for E2E transfer are available, and the performance meets the requirements. 265 266 267### Multimodal Input 268 269- Users can double-touch the power button to start an ability. 270 271- The mouse cursor can be customized. 272 273- The setting of the mouse cursor style in the multimodal input scenario is optimized. 274 275- APIs are provided for processing key press events by priority. 276 277- The mouse cursor size and color can be set, and the animation cursor style is supported. 278 279 280### Pan-Sensor 281 282- Sensor data precision can be reported so that the system can detect the sensor precision of different devices for better application adaptation. 283 284- C APIs are added for sensors and vibrators. 285 286- The custom vibration format is extended. The **curve** field is added to describe the complex continuous vibration effect. 287 288 289### Device Management 290 291APIs related to \@ohos.deviceInfo.d.ts are provided for small-system devices. 292 293 294### Test Framework 295 296**Automated Test Framework arkXtest** 297 298- Simulation of UI operations, such as scrolling the mouse wheel and double-clicking the left or right mouse button, is supported. 299 300- Using shell commands to simulate UI operations, such as click, scroll, double-click, and text input, is supported. 301 302- The efficiency of searching for component information in the UI test framework is improved. 303 304- The information about the text size and color is added in the dump information. 305 306- The asynchronous listening capability is added to listen for system dialog box events and obtain text information. 307 308**Test Scheduling Framework xDevice** 309 310- The capability of automatically retesting failed items during a single test is provided. The number of retest times can be configured, and only one test report is generated. 311 312- The test report is optimized by unifying the test report header information for mini-system, small-system, and standard-system devices. 313 314- A remote download address can be configured when the test resources are unavailable on the local host. 315 316**Stability Test Tool WuKong** 317 318- The capability of configuring pages and ability pages is added. Page shielding can be configured during the test to speed up test. 319 320- The single-scenario pressure test capability is provided. Operation events can be cyclically injected to a component, and the number of cycles can be configured. 321 322**Performance Development Tool SmartPerf Host** 323 324- Collection, analysis, and display of HiLog and HiSysEvent are supported. 325 326- The hiperf event count can be analyzed and displayed. 327 328- Trace capture can be dynamically paused and debugged. 329 330- The thread wakeup relationship tree can be quickly traced. 331 332**Performance Test Tool SmartPerf Device** 333 334- The capability of capturing memory and CPU data is optimized. 335 336- Commands are provided for starting or stopping collection. 337 338- The capability of periodically obtaining screenshots, resolutions, and refresh rates is provided. 339 340 341### DFX 342 343- Collection of CPU, GPU, memory, I/O, network, and trace data is supported. 344 345- The fault type data is open. 346 347- HiDebug supports resource information collection during application running. 348 349- HiProfiler supports in-depth tuning of the CPU, GPS, audio, display, and GPU for power-intensive applications, time consumption analysis in animation scenarios (start, exit, screen switch, transition, and sliding), and lightweight ftrace data collection. 350 351- HiProfiler and HiDumper work together to collect the extended memory information of the memory process. 352 353- HiTrace supports lightweight, long-term data collection. 354 355- HiPerf supports symbol parsing and stack aggregation. 356 357 358### Upload/Download 359 360- Foreground tasks and background tasks can share the number of tasks. 361 362- The status and progress of background tasks can be monitored. 363 364- Task priorities are supported. Foreground or background tasks can be executed based on their respective priorities. 365 366- The system-level proxy is automatically used. 367 368 369### Input Method Framework 370 371- The input method experience is optimized when the WebView gains focus. 372 373- The input method experience is optimized when the focus switches between windows. 374 375- The input method in security mode is supported. 376 377- The input method can be switched by pressing the logo key and the **Space** bar. 378 379- The **inputMethodList** module is provided. 380 381 382### Time and Time Zone 383 384- The NTP server address can be configured through system parameters. A maximum of five NTP server addresses can be configured. 385 386- The switch of automatic time and time zone synchronization can be configured through system parameters. 387 388 389### Globalization 390 391- The preferred language of an application can be set and obtained. 392 393- The text time and phone number formats can be recognized. 394 395- Quick date calculation is supported. 396 397### AI 398 399MindSpore Lite provides C APIs for on-device machine learning. 400 401 402### Update 403 404- Differential multi-thread update is supported. 405 406- A retry mechanism is added for hardware faults during an update to improve update reliability. 407 408- The language parameters in normal mode can be synchronized to the updater used in the update. 409 410 411### Web 412 413- The web-based accessibility node query and reporting capabilities are added. 414 415- APIs are provided for reporting page redirection events. 416 417- Application and network proxy, and application certificate management are supported. 418 419- Rendering at the same layer is supported. (This enhancement is available only for certain components such as **\<XComponent>** and **\<button>**). 420 421- The component supports the execution of JS scripts injected in advance after DOM building is complete. 422 423- C APIs **registerJavaScriptProxy** and **runJavaScript** are available. 424 425- Resource interception supports the ArrayBuffer data type. 426 427 428## Version Mapping 429 430**Table 1** Version mapping of software and tools 431 432| Software/Tool | Version | Remarks | 433| -------- | -------- | -------- | 434| OpenHarmony | 4.1 Release | NA | 435| Public SDK | Ohos_sdk_public 4.1.7.5 (API Version 11 Release) | This toolkit is intended for application developers and does not contain system APIs that require system permissions. | 436| (Optional) HUAWEI DevEco Studio | 4.1 Release | Recommended for developing OpenHarmony applications How to obtain:<br><br>SHA-256 checksum: c46be4f3cfde27af1806cfc9860d9c366e66a20e31e15180cf3a90ab05464650<br><br>SHA-256 checksum: 15d6136959b715e4bb2160c41d405b889820ea26ceadbb416509a43e59ed7f09<br><br>SHA-256 checksum: ac04ca7c2344ec8f27531d5a59261ff037deed2c5a3d42ef88e6f90f4ed45484 | 437| (Optional) HUAWEI DevEco Device Tool | 4.0 Release | Recommended for developing OpenHarmony smart devices<br>[Click here](https://device.harmonyos.com/cn/develop/ide#download). | 438 439 440## Source Code Acquisition 441 442 443### **Prerequisites** 444 4451. Register your account with Gitee. 446 4472. Register an SSH public key for access to Gitee. 448 4493. 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. 450 ``` 451 git config --global user.name "yourname" 452 git config --global user.email "your-email-address" 453 git config --global credential.helper store 454 ``` 455 4564. Run the following commands to install the **repo** tool: 457 ``` 458 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. 459 pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests 460 ``` 461 462 463### Acquiring Source Code Using the repo Tool 464 465**Method 1 (recommended)** 466 467Use the **repo** tool to download the source code over SSH. (You must have an SSH public key for access to Gitee.) 468 469- 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: 470 ``` 471 repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-4.1-Release --no-repo-verify 472 repo sync -c 473 repo forall -c 'git lfs pull' 474 ``` 475 476- Obtain the source code from the version tag, which is the same as that released with the version. 477 ``` 478 repo init -u git@gitee.com:openharmony/manifest.git -b refs/tags/OpenHarmony-v4.1-Release --no-repo-verify 479 repo sync -c 480 repo forall -c 'git lfs pull' 481 ``` 482 483**Method 2** 484 485Use the **repo** tool to download the source code over HTTPS. 486 487- 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: 488 ``` 489 repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony-4.1-Release --no-repo-verify 490 repo sync -c 491 repo forall -c 'git lfs pull' 492 ``` 493 494- Obtain the source code from the version tag, which is the same as that released with the version. 495 ``` 496 repo init -u https://gitee.com/openharmony/manifest -b refs/tags/OpenHarmony-v4.1-Release --no-repo-verify 497 repo sync -c 498 repo forall -c 'git lfs pull' 499 ``` 500 501 502### Acquiring Source Code from Mirrors 503 504 505**Table 2** Mirrors for acquiring source code 506 507| Source Code | Version | Mirror | SHA-256 Checksum | Software Package Size | 508| --------------------------------------- | ------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | -------- | 509| Full code base (for mini, small, and standard systems) | 4.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/code-v4.1-Release.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/code-v4.1-Release.tar.gz.sha256) | 31.6 GB | 510| Hi3861 solution (binary) | 4.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_pegasus.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_pegasus.tar.gz.sha256) | 29.2 MB | 511| Hi3516 solution-LiteOS (binary) | 4.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_taurus_LiteOS.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_taurus_LiteOS.tar.gz.sha256) | 318.7 MB | 512| Hi3516 solution-Linux (binary) | 4.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_taurus_Linux.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/hispark_taurus_Linux.tar.gz.sha256) | 215.8 MB | 513| RK3568 standard system solution (binary) | 4.1 Release | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/dayu200_standard_arm32.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/dayu200_standard_arm32.tar.gz.sha256) | 8.4 GB | 514| Public SDK package for the standard system (macOS) | 4.1.7.5 | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/ohos-sdk-mac-public-signed.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/ohos-sdk-mac-public-signed.tar.gz.sha256) | 1.1 GB | 515| Public SDK package for the standard system (macOS-M1) | 4.1.7.5 | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/L2-SDK-MAC-M1-PUBLIC-signed.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/L2-SDK-MAC-M1-PUBLIC-signed.tar.gz.sha256) | 1.1 GB | 516| Public SDK package for the standard system (Windows\Linux) | 4.1.7.5 | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/ohos-sdk-windows_linux-public.tar.gz) | [Download](https://repo.huaweicloud.com/openharmony/os/4.1-Release/ohos-sdk-windows_linux-public.tar.gz.sha256) | 2.2 GB | 517 518 519## Update Description 520 521This version has the following updates to OpenHarmony 4.1 Beta1. 522 523### API Updates 524 525- For details about the API changes over OpenHarmony 4.1 Beta1, see [API Differences](http://gitee.com/openharmony/docs/blob/OpenHarmony-4.1-Release/en/release-notes/api-diff/v4.1-Release-vs-v4.1-beta1/Readme-EN.md). 526- For details about the API changes over OpenHarmony 4.0 Release, see [API Differences](http://gitee.com/openharmony/docs/blob/OpenHarmony-4.1-Release/en/release-notes/api-diff/v4.1-Release-vs-v4.0-Release/Readme-EN.md). 527 528A few API changes over OpenHarmony 4.1 Beta1 may cause your application projects to be incompatible. For details about these changes, see [Changelogs](http://gitee.com/openharmony/docs/blob/OpenHarmony-4.1-Release/en/release-notes/changelogs/v4.1-Release/Readme-EN.md). 529 530### Chip and Development Board Adaptation 531 532For details about the adaptation status, see [SIG_DevBoard](https://gitee.com/openharmony/community/blob/master/sig/sig_devboard/sig_devboard.md). 533 534 535### Samples 536 537For more information, visit [Samples](https://gitee.com/openharmony/applications_app_samples). 538 539 540## Resolved Issues 541 542**Table 4** Resolved issues 543 544| Issue No. | Description | 545| -------- | -------- | 546| I8PEOF | A system freeze may occur due to LIFECYCLE_TIMEOUT of the com.ohos.mms process. As such, a white screen is displayed. | 547| I8QET3 | A C++ crash may occur in libbluetooth_server.z.so of the OS_IPC_10_25363 thread of the bluetooth_servi process. As such, the Bluetooth service is abnormal. | 548| I8QH9S | A C++ crash may occur in libnative_appdatafwk.z.so of the os.settingsdata thread of the com.ohos.settingsdata process. As such, the background data management process stops. | 549| I8QNI7 | A system freeze may occur due to SERVICE_BLOCK of the foundation process. | 550| I8QSZ1 | An app freeze occurs in libsamgr_proxy.z.so of the com.ohos.systemui process, due to THREAD_BLOCK_6S. | 551| Vulnerabilities (such as I7TYTF) in 43 open-source components | 43 open-source component vulnerabilities, such as protection_fault in the errseq_set function of the kernel | 552| I78THF | The maligpu version in the RK3568 kernel patch is too old (11.29), and a large number of CVE vulnerabilities are not fixed. | 553| I83D6I | If Bluetooth is repeatedly enabled and disabled in Settings, there is a possibility that an app freeze occurs. | 554| I827LU | Memory leakage occurs when Bluetooth is repeatedly enabled and disabled in Settings. A memory leak of 15 MB occurs within one hour. | 555| I82V2W | Memory leakage occurs when Bluetooth is repeatedly enabled and disabled in Settings. The memory usage of Settings increases to 180 MB within one hour. | 556 557 558 559## Known Issues 560 561**Table 5** Known issues 562 563| Issue No. | Description | Impact | To Be Resolved By | 564| -------- | -------- | -------- | -------- | 565| I8WP8M | Create a large folder by moving an application icon on the home screen to overlap with another application icon, and then move an application icon out of the folder. Repeat this operation. Five minutes later, a total of about 25 MB memory is leaked on the launcher, that is, a 673.68 KB memory leak for each operation. | The system freezes when the memory leak reaches a certain amount.<br>Workaround: Close background applications or restart the device. | April 30 | 566| I98AV0 | Repeatedly turn on and then turn off the location information switch. When this operation lasts for 5 minutes, a total of about 14 MB memory is leaked on the distributeddata process, that is, a 95.57 KB memory leak for each operation. | The system freezes when the memory leak reaches a certain amount.<br>Workaround: Exit the current page. | April 30 | 567| I9A9NO | Repeatedly touch the upper right corner of the SMS application to create an SMS message and then touch **Back**. When this operation lasts for 5 minutes, a total of about 50 MB memory is leaked, that is, a 341.33 KB memory leak for each operation. | The system freezes when the memory leak reaches a certain amount.<br>Workaround: Exit the application. | April 30 | 568| I8QLRO | There is a low probability that a C++ crash occurs in libbtstack.z.so of the stack thread of the bluetooth_servi process. | The Bluetooth service automatically recovers, and users are unaware of the exception. | April 30 | 569| I8TLYJ | There is a low probability that a C++ crash occurs in libbtstack.z.so of the SaInit1 thread of the bluetooth_servi process. | The Bluetooth service automatically recovers, and users are unaware of the exception. | April 30 | 570| I8TM99 | There is a low probability that a C++ crash occurs in libbtframework.z.so of the softbus_server thread of the softbus_server process. | The DSoftBus service automatically recovers, and users are unaware of the exception. | April 30 | 571| I8VFJS | There is a low probability that a JS crash occurs in ObservedPropertyAbstractPU of the com.ohos.settings process. | There is a low probability that the Settings application crashes. Users can exit the application to reclaim the memory. | April 30 | 572| I98NGO | There is a low probability that an app freeze occurs in the com.ohos.settings process because THREAD_BLOCK_6S is stuck in the libbtframework.z.so stack. | There is a low probability that the Settings application crashes. Users can exit the application to reclaim the memory. | April 30 | 573| I90A2N | There is a possibility that an app freeze occurs in the com.ohos.systemui process because THREAD_BLOCK_6S is stuck in the libeventhandler.z.so stack. | There is no response when users touches or swipes on the phone. This issue can be resolved when users access the control panel or notification center again. | May 30 | 574| I963UO | There is a possibility that a C++ crash occurs in libEGL.so of the RSRenderThread thread in the com.ohos.systemui process. | The screen automatically locks. The issue does not persist after users unlock the screen. | May 30 | 575| I9A089 | There is a moderate probability that a system freeze occurs in the foundation process due to SERVICE_BLOCK. | After the system freezes for 5 seconds, a 1-second startup animation is played, and the screen is locked. The issue does not persist after users unlock the screen. | April 15 | 576| I9AYM2 | There is a low possibility that an app freeze occurs in the com.ohos.note process because THREAD_BLOCK_6S is stuck in the libweb_engine.so stack. | The Notes application freezes. The issue does not persist after the application is restarted. | May 30 | 577| I9CGOZ | There is a high probability that an app freeze occurs in the com.ohos.camera process because THREAD_BLOCK_6S is stuck in the libcamera_framework.z.so stack. | The Camera application does not respond. The issue does not persist after the application is restarted. | April 30 | 578| I9AEO0 | There is a low probability that an app freeze occurs in the com.ohos.settings process due to APP_INPUT_BLOCK. | The Settings application does not respond. The issue does not persist after the application is restarted. | April 30 | 579| I8QH9S | There is a low probability that a C++ crash occurs in libnative_appdatafwk.z.so of the os.settingsdata thread of the com.ohos.settingsdata process. | The settingsdata service breaks down. It automatically starts when users access the data again. This has no impact on users. | April 15 | 580| I963TL | There is a low probability that a C++ crash occurs in libark_jsruntime.so of the com.ohos.mms thread of the com.ohos.mms process. | The SMS application does not respond or automatically exits. The issue does not persist after the application is restarted. | April 30 | 581| I9635I | There is a low probability that the device automatically restarts. | The impact is controllable. No workaround is required. | April 30 | 582| I96JJ7 | There is a low probability that a C++ crash occurs in libace_compatible.z.so of the com.ohos.note thread of the com.ohos.note process. | The Notes application may crash. The issue does not persist after the application is restarted. | April 30 | 583| I993H9 | There is a possibility that an app freeze occurs in the com.ohos.smartperf process because THREAD_BLOCK_6S is stuck in the libglobal_resmgr.z.so stack. | When users use the SmartPerf application to view real-time performance data of other applications, the application freezes.<br>Workaround: The system automatically clears the application process. The issue does not persist after the application is restarted. | April 30 | 584| I97U6G | There is a low possibility that an app freeze occurs in the com.ohos.certmanager process because THREAD_BLOCK_6S is stuck in the librender_service_client.z.so stack. | The system automatically exits the certificate management application when it is frozen. The impact is controllable. | April 30 | 585| I98KIG | There is a low probability that an app freeze occurs in the com.ohos.camera process because THREAD_BLOCK_6S is stuck in the libcamera_framework.z.so stack. | The Camera application freezes. The issue does not persist after users exit the application, clear the memory, and open the application again. | April 15 | 586| I98NFR | There is a low probability that a C++ crash occurs in libwm.z.so of the ohos.smartperf thread of the com.ohos.smartperf process. | There is a low probability that the application exits. The issue does not persist after the application is restarted. | April 30 | 587| I98AWP | 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. | The Notes application may crash. The issue does not persist after the application is restarted. | April 30 | 588| I96ZWB | The peer device cannot be found after device networking. | When using the distributed audio service, OpenHarmony 4.0 and 4.1 devices cannot be compatible or interoperate with each other. The impact is controllable. | May 30 | 589| I96CJL | The networking between mini-system devices fails. | The impact is controllable, and no workaround is available. | May 30 | 590