Constraints

You need to fully understand the following constraints on the hardware, system, and applications when you deploy and use the video stream cloud phone.

• Software and hardware constraints
  • The video stream engine server runs in the Kbox container, and the OS is Android 11.0.0.
  • The video stream engine client is 64-bit and must run on 64-bit mobile phones running HarmonyOS or Android 7 or later.
  • The video encoding function of the video stream engine server depends on a third-party video encoding module. The module can be either a software or hardware implementation, for example, the NETINT Quadra T2A video encoding card. If the constant bit rate mode is used for encoding, the image may be blurry for a short time when the image changes rapidly. This is because the bit rate requirement in this scenario is too high. You can increase the bit rate to alleviate the problem.
  • The video decoding function of the video stream engine client depends on the hardware video decoding capability of the mobile phone.
  • The hardware-related performance and specifications described in this document need to be tested on specified hardware.
• Use constraints
  • This project delivers the binary library of the video stream engine to third parties and promises the quality, performance, and security of the engine. Third parties integrate the video stream engine based on their service scenarios and define product specifications and performance. In addition, third parties are responsible for scenario definition, service development, network design, system security, and service O&M.
  • The unique one-click cleanup function of Huawei phones will not stop the active processes with data transmission in the background, because the video stream engine client needs to maintain heartbeat data to ensure continuous network connection with the video stream engine server. Therefore, on Huawei phones, the video stream engine client will not be stopped during one-click cleanup.
  • The host OS is not within the delivery scope of this solution. Therefore, security hardening measures related to the OS need to be implemented by you or the independent software vendor (ISV). This document does not provide related descriptions.
  • In this document, the root permission is used by default to call scripts. The scripts are for reference only, and no commercial commitment is made. To minimize OS security risks, it is recommended that you or the ISV implement defense measures in commercial deployment scenarios, such as file access control and minimum authorization.
  • When performing operations based on this document, configure appropriate permissions on the uploaded files and directories. You are advised not to configure the write permission for other user groups.
  • To ensure the stable running and optimal performance of the video stream cloud phone, ensure that the bound GPU nodes and CPU cores are within the same chip when starting the cloud phone.
• Others
  • The compatibility between applications and Android emulators, such as third-party login, advertisement, payment, customer feedback, extended games, and emulator detection, depends on the compatibility capability of the cloud phone image.
  • If you enable the dynamic frame rate adjustment function, set the ro.hardware.downfps environment variable to 12 or 24 to avoid unknown exceptions caused by insufficient frame rates.
  • When hardware configuration scheme 1 is used, if you enable the composition bypass function, the screen may rotate when you enter or exit a game or bring up the text input field. Evaluate the impact to determine whether to enable this function.
  • The video stream engine relies on the secure and reliable communication mechanism provided by a third party for session authentication and data transmission/encryption.
  • Commercial binary files comply with the minimum permission principle of Android. The file owner and owner group must be root.
  • When a video stream cloud phone runs for a long time, it occupies a large amount of cache on the host. Run the following command to periodically clear the cache:

    1	echo 3 > /proc/sys/vm/drop_caches

    

    Clearing the cache will temporarily affect the system performance. Therefore, you need to control the clearing period and granularity.

    • Clear the page cache.

      1	echo 1 > /proc/sys/vm/drop_caches

    • Clear kernel slab objects (including inode and dentry).

      1	echo 2 > /proc/sys/vm/drop_caches

    • Clear both the page cache and kernel slab objects.

      1	echo 3 > /proc/sys/vm/drop_caches