Enabling the NETINT Card
This section describes how to enable the NETINT card. If the NETINT card does not need to be enabled, skip this section.
If the hardware H.264 video encoding of the NETINT card is enabled, the encoding delay and bandwidth consumption can be reduced.
- Upgrade the firmware version to 318X2013.
If the firmware has been upgraded, go to the next step. If not, perform the following operations:
- Run the nvme list command after nvme-cli is installed on the server.
# apt install nvme-cli # nvme list
You can view the firmware version of the NETINT card on the right.
- If the firmware version is not 318X2013, upload the T4XX_V3.1.8_release.zip package to the server, decompress the package, and run the t4xx_auto_upgrade.sh script in the package. After the script is executed, restart the server.
- Run the nvme list command after nvme-cli is installed on the server.
- Enable the NETINT card for H.264 hardware encoding.
Check the value of ro.vmi.demo.video.encode.format in the vendor/default.prop file in the InstructionPhoneAndroidRServer.tar.gz package. The value 1 indicates that H.264 hardware encoding is used.
To enable OpenH.264, change the value of ro.vmi.demo.video.encode.format in vendor/default.prop to 0.
- Query whether H.264 hardware encoding takes effect.After starting and connecting to the instruction stream cloud phone server and playing a video, run the following commands in the Docker container. H.264 video encoding information is displayed.
# docker exec -it kbox_${kbox_id} sh # logcat | grep Netint
You can check whether H.264 hardware encoding takes effect only after step 5 in Starting an Instruction Stream Cloud Phone is complete.