Design method for android set top box production testing software

Abstract

The invention provides a design method for android set top box production testing software. The design method includes the concrete design steps that a production testing software entry is designed, first, the production testing software enters a recovery system in a mode of combination keys when being started, and if a user does not press any combination key in the starting process, the bootloader will read a start control information block BCB located in an MISC partition; when a start command is 'boot-recovery', the system will enter a Recovery mode, and the corresponding operation will be executed according to relevant commands through the Recovery service; when the start command is null and it is that no any command exist, the system will be normally started and finally enter the android system; data storage and a user interface are designed. Compared with the prior art, the design method for the android set top box production testing software improves interactivity and visual performance and is high in practicality and easy to popularize.

Description

technical field [0001] The invention relates to the technical field of communication information, in particular to a design method of production and testing software for an Android set-top box based on a recovery mode. Background technique [0002] Due to the complexity of the Android system, the main problem is the long startup time. A lot of time is spent on zygote preloading classes, initializing the stack and scanning the installation package. After several optimizations, the startup time is still about 30 seconds. Moreover, the set-top box for production testing is often the first run after the firmware is programmed, and its boot time is longer. At present, the production test of Android set-top boxes mostly adopts the method of triggering the production test application program through special operation or condition judgment after entering the Android system. This test method wastes a lot of time during the boot process, which directly affects the efficiency of produc...

AI Technical Summary

Problems solved by technology

[0002] Due to the complexity of the Android system, the long startup time is the main problem. A lot of time is spent on zygote preloading classes, initializing the stack and scanning the installation package. After several optimizations, the startup time is still about 30 seconds

Moreover, the set-top box for production testing is often the first run after the firmware is programmed, and its boot time is longer

At present, the production test of Android set-top boxes mostly adopts the method of entering the production test application through special operations or conditional judgments after entering the Android system. This test method wastes a lot of time during the boot process, which directly affects the efficiency of production testing.

Some manufacturers design a set of linux production test firmware to shorten the time to enter the production test software, but the set-top boxes that pass the production test need to burn the Android firmware once before leaving the factory, which increases the production process and reduces the production test efficiency in disguise.

Images