Android-based startup management method

Abstract

The invention relates to an Android-based startup management method. The method comprises the following steps of: (101) finishing system initialization; (102) starting and transmitting system initialization finish broadcasting through mobile management service; (103) acquiring a receiver object list of the registered and received system initialization finish broadcasting for package management service through the mobile management service; (104) starting to transmit the system initialization finish broadcasting; (105) traversing the receiver object list and processing each object in the list according to pre-configuration or definition, if startup is allowed, starting corresponding application or progress, transmitting the broadcasting to an allowed object, and calling back an onReceive method, and if the startup is not allowed, jumping over the unallowed object; and (106) finishing the broadcasting through the system initialization. According to the method, the startup speed is effectively improved, and the system resources of mobile phones are saved.

Description

Technical field [0001] The invention relates to an Android operating system and its applications, and in particular to an Android-based boot management method. Background technique [0002] At present, after the Android system completes the system initialization, it will send out a system initialization completion broadcast (ACTION_BOOT_COMPLETE broadcast) to notify those applications that are interested in whether the boot is complete. Therefore, if an application wants to start its own service or do other things after booting, it only needs to do three steps: [0003] (1) Implement a static receiver (Receiver) in the application software code; [0004] (2) Register the Receiver as an object interested in ACTION_BOOT_COMPLETE broadcasting; [0005] (3) When the ACTION_BOOT_COMPLETE is sent to the Receiver, the application process will be created at this time, the onReceive() method in the Receiver will be called back, and any function can be implemented in this method. [0006] It ca...

AI Technical Summary

Problems solved by technology

[0008] Therefore, when the third-party software and the system software are scrambling to do the initialization work in the same period of time, we can easily see a phenomenon: after booting, the screen has entered the desktop, but the system is very stuck, click The application icon is unresponsive, and the desktop menu page is unresponsive... After all, the processor and memory resources of the mobile phone are limited. The more software is doing boot-up self-starting, the busier the system will be, and so on. After the application software is started, the resources of the system are almost exhausted, and there is such a law of linear growth, the more software that starts automatically after booting, the longer the boot time will be, and the more problems will occur.

In the process of system development, the author has seen some machines with problem feedback. There are hundreds of items of software on startup. Therefore, there is a high probability of ANR (Application not response) phenomenon during the startup process. The causes of ANR are usually divided into two types. Types: (1) The processor is busy, (2) The application program does not finish the work within the specified processor time), whether every third-party software must be started at boot time, why this option cannot be given to the user ? However, currently there is no such method in the Android system or this method is disclosed

Images