Release Notes

Kunpeng BoostKit

26.0.RC1

Kbox cloud phone container

7.3.0_11

DTS2024031108664

Minor

The music playback process remains after KuGou is terminated in the multi-window screen.

The process termination API is not invoked when the app is being terminated in the multi-window screen. It is suspected that the app bypasses process termination through some detection.

The process cannot be terminated in the multi-window screen, but can be terminated in the notification panel or app info screen.

Terminate the app in the notification panel or forcibly stop the app in the app info screen.

The issue is being located.

DTS2023051802653

Minor

After the BIOS is upgraded to 6.56 and the server is restarted, the encoding card chip intermittently fails to be detected.

Following a server reboot, the encoding card chip occasionally fails to be detected. This low-probability issue can be resolved by a subsequent reboot, but it impacts normal customer operations.

If the T432 encoding card is used, cloud phone density is affected when this problem occurs.

1. Use the iBMC to set the server fan modules to the high-performance mode.
2. Occasional identification failure: The fault can be rectified by a cold reboot.
3. Damaged connector pins: Contact the manufacturer for a card replacement.

1. The T432 encoding card is outside Huawei's sales scope. We will add a restriction notice regarding the missing T432 chip and include workaround instructions in the official documentation to alert customers.
2. This issue will remain open while we track the manufacturer's final root cause investigation.

DTS2023051004239

Minor

When using XPlayer for hardware video decoding, the system occasionally falls back to its own software decoding. This prevents stable utilization of Kbox's hardware decoding capabilities, indicating a compatibility issue between Kbox and XPlayer.

NETINT destruction or initialization occasionally responds slowly. As a result, XPlayer detects that the hardware decoding capability is insufficient, and software decoding is used instead.

Low-probability container fallback from hardware to software decoding; no impact on actual video playback.

XPlayer enforces strict response time limits on hardware decoding interfaces. Since falling back to software decoding does not disrupt video playback, no immediate workaround is required.

Continue joint investigation with NETINT to locate and resolve the slow response issue.

DTS2023022301216

Notice

When installing and opening the game on Kbox Basic Cloud Phone, attempting to log in with an account that has no registered characters triggers a "Device Data Anomaly" error, preventing the creation of a new character.

The exact root cause is still under investigation. Two potential angles are currently being explored:

1. Incomplete device emulation: Kbox device emulation is not yet fully optimized and may lack specific data required by the game. This will need to be evaluated in future Kbox evolution strategies.
2. The game may have detected that Kbox is a virtual environment rather than a physical device, thereby triggering its anti-cheat mechanism.

Mitigation measures are available, and the impact is small. Sky: Children of the Light is not currently on the official compatibility list; the primary testing objective was to verify ETC2 texture support, which has been successfully validated. Furthermore, logging in with an existing character account works as expected.

Logging in with an existing character account works as expected.

This issue will remain open. A final decision on whether to close it will be evaluated after a thorough baseline assessment of device emulation capabilities.

DTS202105190IPKB9P1300

Condition: The CTS test suite is used in the CI daily build scenario.

Symptom: Test cases in some modules of the test suite failed to pass corresponding tests in a container. After another container was used, the test cases passed the corresponding tests.

Root cause: In this trouble ticket, the failed test case in 296 CtsUiAutomationTestCases is not a baseline test case but an additional test case. The test case will be further analyzed in the CTS special work.

The failed test case in 26 CtsAssistTestCases is caused by the test case itself, whose Google bug ID is 30859355. This issue may be eligible for an exemption.

Two failed test cases in 69 CtsGraphicsTestCases are related to Vulkan enablement. After the two test cases that do not support the extended properties and image format are masked according to the last CCB decision, this module can pass the test.

From July 2 to September 3, CI CTS daily build was performed for 28 times, among which CtsWidgetTestCases failed for 4 times, CtsJvmtiRunTest993HostTestCases and CtsAtraceHostTestCases each failed once, and CtsAccessibilityTestCases did not fail. The general failure rate is low. Increasing the number of retries can improve the pass rate of the preceding modules.

Impact: The issues in this trouble ticket occurred occasionally. The module with the highest failure rate failed four times in 28 times of CI daily build, and other modules failed once or did not fail. This affected the CTS pass rate in the CI environment.

Minor

Workaround: Increase the number of retries for failed test cases.

Blue zone issue 15

Condition: The video stream cloud phone is used to test Cocos.

Symptom: When playing a game in landscape mode, touch and hold the notification bar and click the home button on the server side. As a result, the notification bar is forcibly pulled out.

Root cause: This requires that the drop-down notification bar be masked. However, this is not implemented in the complex operation scenario described in the symptom part. As a result, the drop-down notification bar can still be displayed. The masking solution in this scenario is still under discussion and is not modified before this release.

Impact: The trigger condition is highly specific and rare. Generally, a user is unlikely to press and hold the notification bar with the left hand while simultaneously pressing and holding the home button with the right hand. In addition, this problem strictly occurs during landscape-to-portrait orientation switches. Even if the notification bar appears, it does not disrupt normal functionality. Therefore, the practical impact is negligible.

Blue zone

No workaround required; rarely triggered under normal usage conditions.

DTS202107210KJTJ7P1400

Condition: Video streaming cloud phone testing with Cocos during CI daily builds.

After running Cocos test cases in the CI video streaming daily build, the server-side cloud phone main interface displays screen artifacts.

Root Cause Analysis: CI log analysis indicates that while Cocos test cases are running, an out-of-bounds memory access occurred within Mesa's gallium_dri.so, leading to a Mesa crash. The call stack points to the eglSwapBuffersWithDamageKHR interface in the Mesa library. The visible symptom is screen artifacts. Initial findings suggest the issue is related to the third-party Mesa driver component, and further deep-dive analysis is required to pin down the exact root cause.

Impact:

1. There is a low probability that this problem occurs. This problem occurred twice on the video stream daily build server (on July 20 and September 4, with a gap of more than one month). In subsequent 6,000 dedicated tests, this problem did not recur.
2. Only the cloud phone that runs the test case is affected. Other cloud phones started on the server are not affected.

Minor

Restart the cloud phone.

DTS2021090912581

Condition: Upgrade the server firmware (BIOS 177, CPLD 5.14, and iBMC 3.01.12.23).

Symptom: The server (model 5220) uses a new motherboard to upgrade BIOS 177, CPLD 5.14, and iBMC 3.01.12.23, but the upgrade fails, and the server hangs. Currently, no official new versions are available for the new motherboard.

root cause: Model 5220 has two versions corresponding to the old and new motherboards. The link to the BIOS version matching the old motherboard at the Support website is invalid. In this test, the new motherboard is used. According to the Kunpeng computing hardware developers of the 5220 motherboard, the BIOS version matching the new 5220 motherboard has not been released. If the latest BIOS version on the Support website is used, the upgrade fails. To solve this problem, the BIOS team needs to release the BIOS version matching the new motherboard to the Support website.

Impact: If a customer uses the new motherboard, the customer cannot obtain the matching BIOS version from the Support website.

Minor

None