CN109542744B - Method, device, storage medium and terminal for detecting abnormal starting problem of terminal - Google Patents

Abstract

The embodiment of the application discloses a method and a device for detecting abnormal starting-up problems of a terminal, a storage medium and the terminal. The method comprises the steps of detecting the start of an init process; acquiring state information of a starting-up animation process through a preset detection service; and when the boot failure is determined according to the state information, storing target information causing the boot failure fault in the boot process. By the technical scheme, the preset detection service can be started to detect the starting state after the starting process enters the android layer, and logs causing the problem of non-starting in the whole process are acquired and stored when the starting fails; the method can cover the complete stage of the starting-up process, avoid the problem of detection leakage, save target information causing starting-up failure, and be convenient for terminal developers to analyze the reason causing the problem of non-starting-up.

Description

Method, device, storage medium and terminal for detecting abnormal startup of terminal

technical field

The embodiments of the present application relate to smart device technologies, and in particular, to a method, an apparatus, a storage medium, and a terminal for detecting an abnormal startup of a terminal.

Background technique

As the degree of intelligence of the terminal increases, its application in people's daily life becomes more and more popular. However, due to the high intelligence of the terminal, the terminal usually fails to boot due to various reasons.

At present, the Android system (hereinafter referred to as Android) itself can monitor the boot failure caused by the service stuck in the boot process through the watchdog (or called watchdog) mechanism. For example, when a key service starts, start watchdog to monitor whether the service is stuck. However, the above watchdog mechanism cannot detect the mounting of services or partitions before the zygote process starts, and there is a problem of missing detection.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a method, device, storage medium, and terminal for detecting a problem of abnormal startup of a terminal, which can effectively optimize the solution for detecting a problem of a terminal not being turned on in the related art.

In a first aspect, an embodiment of the present application provides a method for detecting abnormal startup of a terminal, including:

It is detected that the init process is started;

Obtain the state information of the boot animation process through the preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file;

When the boot failure is determined according to the state information, the target information that causes the boot failure failure in the boot process is saved.

In a second aspect, an embodiment of the present application further provides a device for detecting an abnormal problem of starting a terminal, and the device includes:

The startup detection module is used to detect the startup of the init process;

an information acquisition module, configured to acquire state information of the boot animation process through a preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file;

The information storage module is configured to save the target information that causes the failure to boot in the boot process when it is determined according to the state information that the boot fails.

In a third aspect, the embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the method for detecting abnormal startup of a terminal as described in the embodiments of the present application.

In a fourth aspect, an embodiment of the present application provides a terminal, including a memory, a processor, and a computer program that is stored in the memory and can be run on the processor, and the processor executes the computer program to achieve the same implementation as the embodiment of the present application. The method for detecting abnormal startup of a terminal is described.

An embodiment of the present application provides a solution for detecting abnormal startup of a terminal. When the startup of an init process is detected, state information of a startup animation process is obtained through a preset detection service, wherein the program code corresponding to the preset detection service is in the init process. Executed when parsing the init.rc file; when it is determined that the boot fails according to the state information, the target information that causes the boot failure in the boot process is saved. Through the above technical solution, the preset detection service can be started to detect the boot state after the boot process enters the Android level, and when the boot fails, the logs that cause the failure to boot in the entire process can be obtained for storage; the entire stage of the boot process can be covered. , to avoid the problem of missed detection. In addition, saving the target information that causes the failure to boot can also facilitate the terminal developers to analyze the reasons for the failure to boot, and then optimize the boot process of the terminal.

Description of drawings

FIG. 1 is a flowchart of a method for detecting an abnormal problem of starting a terminal according to an embodiment of the present application;

FIG. 2 is a frame diagram of a startup process of a terminal based on an android system;

FIG. 3 is a flowchart of another method for detecting a problem of abnormal startup of a terminal provided by an embodiment of the present application;

FIG. 4 is a flowchart of another method for detecting abnormal startup of a terminal according to an embodiment of the present application;

FIG. 5 is a structural block diagram of an apparatus for detecting abnormal startup of a terminal according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present application;

FIG. 7 is a structural block diagram of a smart phone provided by an embodiment of the present application.

Detailed ways

The present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all the structures related to the present application.

Before discussing the exemplary embodiments in greater detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowchart depicts the steps as a sequential process, many of the steps may be performed in parallel, concurrently, or concurrently. Furthermore, the order of the steps can be rearranged. The process may be terminated when its operation is complete, but may also have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, subroutines, and the like.

FIG. 1 is a flowchart of a method for detecting a terminal startup abnormality problem provided by an embodiment of the present application. This embodiment can be applied to a scenario of monitoring a terminal startup failure. The method can be implemented by software and/or hardware, and can generally be integrated in the terminal. As shown in Figure 1, the method includes:

Step 110, it is detected that the init process is started.

It should be noted that the terminals in the embodiments of the present application may include mobile phones, tablet computers, notebook computers, computers, handheld game consoles, smart home appliances, and other devices that are installed with operating systems. The type of the operating system is not limited in the embodiments of the present application, and may include, for example, an Android (Android) operating system, a Windows (Windows) operating system, and an Apple (ios) operating system, and so on.

Take Android as an example to briefly describe the boot process of the terminal. The startup process of Android can be divided into two stages. The first stage is the startup of Linux, and the second stage is the startup of Android (which can be called the upper-level boot process). FIG. 2 is a frame diagram of a startup process of a terminal based on an android system. As shown in Figure 2, the booting process includes: 201, BootRom - when the boot button is pressed, the boot chip starts to execute from the preset code solidified in the ROM, and then loads the boot program to the RAM. 202. Bootloader, also known as bootloader, is a program that runs before the operating system runs. It is the first program to run. It is used to copy the operating system image file to RAM, and then jump to the entry of the image file. Executing the file can also be called entering bootloader mode. 203. Kernel - After loading the kernel into the memory, it first enters the kernel boot stage. At the end of the kernel boot stage, call start_kernel to enter the kernel boot stage, mainly to complete most of the initialization work of the kernel. Start_kernel will finally start the user space init process. 204. init process - when the kernel is initialized, the init process will be started. In Linux, all processes are directly or indirectly forked by the init process. The Init process is responsible for creating the most critical core daemon (daemon) processes in the system, including but not limited to zygote and service manager. Among them, zygote is the first dalvik virtual machine started by android, which is responsible for starting the Java process. The service manager is the basis of Binder communication. 205. Zygote process - this process is the parent process of all Java processes. For example, the zygote virtual machine starts the child process system_server, and defines a Socket to receive requests from the ActivityManagerService to start the application. 206. SystemServer process - When the SystemServer process is started, the ActivityManagerService will be initialized. At the same time, the service library of the local system will be loaded, createSystemContext() will be called to create the system context, ActivityThread will be created, various services will be enabled, and so on. 207. Home Activity - After ActivityManagerService is started, finishBooting() will be called to complete the boot process, and at the same time, a boot broadcast will be sent to enter the home interface and display the desktop.

In the embodiment of the present application, the terminal monitors the execution of the boot process, and when detecting an instruction to create and start the kernel thread init, determines that the init process is detected to be started. For example, the kernel initialization function start_kernel executes to the end and calls the rest_init function, and the rest_init function is mainly used to create and start the kernel thread init.

Step 120: Obtain status information of the boot animation process through a preset detection service.

It should be noted that the default detection service is used to perform loop detection on the boot process, obtain the attribute value of the boot animation service (the service carried on the boot animation process), and compare the attribute value with the attribute value representing the end of the boot animation. Comparison. If the property values of the two are the same, it is determined that the boot animation ends; otherwise, it is determined that the boot animation is in the playing state.

In addition, the program code corresponding to the preset detection service is executed when the init process parses the init.rc file. It can be understood that the init process will load some basic services and various services defined in the init.rc file when it is executed. The program code corresponding to the preset detection service is executed when the init process parses the init.rc file. For example, the program code corresponding to the preset detection service is loaded when the parsing operation of the init.rc file is performed, and may be executed before the first line function of parsing the init.rc file is performed. Among them, the init.rc file can contain the definition of the system core services, such as SurfaceFlinger, MediaServer, Logcatd, etc.; it can also include some services defined by the SOC manufacturer for the core functions of the SOC, such as the related services of a certain SOC of Qualcomm or MTK. It can also include services related to peripherals and differentiated functions used by the products of EM/ODM manufacturers. A single init*.rc is split, and its corresponding service can be defined in the etc/init directory of the corresponding partition based on the location of its binary file (such as /system, /vendor or /odm). It should be noted that each Each service corresponds to an rc file.

It should be noted that the boot animation process, also known as the boot animation process, is a process for displaying the boot animation on the touch screen. The boot animation process is started by executing the surfaceflinger::startBootAnim() function, where the configuration in bootanimation is disabled, indicating that the process depends on the display service of the system, and the bootanimation process can only be started when the display-related services are started, that is After the surfaceFlinger service is up, it will pull up the bootanimation service to display the boot animation. Since bootanimation inherits the Thread class, when the run() of the parent class is called, readyToRun() will be called before the thread runs to perform the set initialization work. For example, call the member function createSurface of the SurfaceComposerClient object mSession by executing readyToRun() to obtain a SurfaceControl object control, and then call the member function getSurface of control to obtain a Surface object s. Both control and s can communicate with SurgaceFlinger through binder. In addition, OPENEGL and EGL are initialized to define an EGL display and describe an EGL framebuffer configuration parameter, and to describe an EGL drawing surface and an EGL drawing context. In addition, the animation files are sequentially read for display on the touch screen.

It should be noted that the status information is used to indicate whether the boot animation process is completed, that is, whether the boot animation is played, including a first attribute value representing the end of the boot animation and a second attribute value representing the playback of the boot animation.

Exemplarily, after it is detected that the init process is started, it is determined whether the init process executes and parses the init.rc file, and if so, the program code corresponding to the preset detection service is loaded and executed, and the loop detection is performed based on the program code to periodically Detect the status information of the boot animation process.

Step 130: When it is determined according to the state information that the boot fails, save the target information that causes the boot failure in the boot process.

It should be noted that, based on the display time of the boot animation in the boot process of the terminal, the threshold time of the boot animation process during execution can be determined, which is recorded as the preset time threshold. For example, the preset time threshold is set to be slightly longer than the display time of the boot animation under normal circumstances. If the execution time of the boot animation process exceeds the preset time threshold, it means that the boot process is stuck in the boot animation display stage, the boot animation process is always in the state of executing the boot animation service, and it is determined that the boot fails. Assuming that before the execution time of the boot animation process exceeds the preset time threshold, the property value of the detected boot animation service becomes the property value representing the end of the boot animation, then it is determined that the boot animation process ends, and the conclusion that the boot is successful can be drawn. After the startup is successful, the exit statement of the program code corresponding to the preset detection service can be executed to exit the program.

Exemplarily, when it is determined based on the status information that the boot fails, the log file recording the boot exception information in the entire boot process is printed, and recorded as the boot exception log, that is, the boot exception log includes the entire boot process that caused the terminal to boot. Failed target information. The startup exception log is stored in the set storage space of the terminal, so that the startup exception log can be returned to the server of the terminal manufacturer. Optionally, the boot exception log is stored in a reserved partition of the terminal, where the reserved partition is a customized partition of the terminal manufacturer to store some key logs or other information that is not expected to be cleared. The reserved partition has the characteristic that the read and write frequency is lower than the set threshold. The set threshold can be the default lower read and write frequency of the system, which can avoid the occurrence of partition damage caused by frequent read and write. The reserved partition also has the feature that it will not be erased when the machine is flashed, and can securely save the log file that records the abnormal information of the boot.

In the technical solutions of the embodiments of the present application, when the startup of the init process is detected, the state information of the boot animation process is obtained through a preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file ; When it is determined that the startup fails according to the state information, the target information that causes the startup failure in the startup process is saved. Through the above technical solution, the preset detection service can be started after the boot process enters the Android layer to detect the boot state, and when the boot fails, the logs that cause the problem of not booting in the entire process can be obtained for storage, and the logs can be returned to the terminal. Manufacturer; it can cover the complete stage of the boot process to avoid the problem of missed detection. In addition, saving the target information that causes the boot failure can also facilitate the terminal developers to analyze the reasons for the non-boot problem, and then optimize the terminal boot process.

FIG. 3 is a flowchart of another method for detecting a problem of abnormal startup of a terminal provided by an embodiment of the present application. As shown in FIG. 3 , the method includes:

Step 301, it is detected that the init process is started.

Step 302: Periodically acquire attribute information of the boot animation service through a preset detection service.

It should be noted that the attribute information is a character representing whether the start-up animation is finished or not. The terminal can determine whether the start-up animation has ended by detecting the attribute information of the start-up animation service.

Exemplarily, the preset detection service acquires attribute information of the boot animation service according to a set period. The period value may be a system default value, and the calculation amount of the terminal and the timeliness of detection need to be comprehensively considered when setting the period value. Assuming that the period value is set too small, it will result in a large amount of calculation of the terminal and occupy too much computing resources of the terminal. If the period value is set too large, the end of the boot animation cannot be detected in time.

Step 303: Obtain the execution time of the boot animation process.

Exemplarily, to record the execution time of the boot animation process, the method may be that, when the boot animation process starts to be executed, the time recording module is triggered to work to perform time recording. It should be noted that the time recording module may be a hardware component such as a timer or a crystal oscillator, and may also be implemented by software.

The terminal periodically obtains the execution time of the boot animation process through the preset detection service, wherein the period value of the detection period may be a system default value.

Step 304 , determine whether the execution time is less than the preset time threshold, if yes, go to step 305 , otherwise go to step 308 .

Exemplarily, the terminal obtains the execution time of the boot animation process from the time recording module, and compares the execution time with a preset time threshold.

Step 305 , determine whether the attribute information is an attribute value representing the end of the boot animation, if so, go to step 306 , otherwise go to step 307 .

Step 306 , determine that the boot animation process is in an ending state, and determine that the boot is successful.

Exemplarily, when the execution time of the boot animation process is less than the preset time threshold, if it is detected that the property information of the boot animation service becomes a value representing the end of the boot animation, it is determined that the boot animation process is in an end state. Furthermore, if it is detected that the boot animation process is in an ending state, it can be determined that the start is successful.

Step 307: Determine that the boot animation process is in the state of executing the boot animation service.

Exemplarily, if the attribute information of the boot animation service is a value representing that the boot animation is being played, it can be determined that the boot animation process is in the state of executing the boot animation service.

In the current cycle, it is determined that the boot animation process is in the state of executing the boot animation service, the preset detection service waits for the set time to come in the next cycle, returns to step 303 to obtain the execution time of the boot animation process, and then executes steps 304 and 305 in sequence , cyclically execute the above steps until the execution time exceeds the preset time threshold, or until it is detected that the boot animation process is in the end state before the execution time exceeds the preset time threshold.

Step 308: If the boot animation process is always in the state of executing the boot animation service, it is determined that the boot fails.

Exemplarily, if before the execution time exceeds the preset time threshold, the boot animation process is always in the state of executing the boot animation service, and when the execution time exceeds the preset time threshold, the end event of the boot animation is still not detected, then Make sure the boot failed.

Step 309 , when it is determined based on the state information that the startup fails, acquire a startup exception log corresponding to the startup process.

The boot exception log includes target information that causes the terminal to fail to boot in the entire boot process. The target information includes key information about failures such as all services stuck during the entire boot process, or the services do not end or the partition is not mounted successfully.

Exemplarily, when the startup fails, the startup exception logs of each failure stage in the startup process are obtained.

Step 310: Store the boot exception log in a reserved partition.

Store the boot exception log in the reserved partition, and report the boot exception log to the terminal R&D personnel at an appropriate time, which can avoid the loss of the log file that records the key information of the boot exception due to flashing or restarting the terminal. It provides a basis for R&D personnel to analyze the reasons for abnormal startup, and furthermore, it also provides a basis for optimizing the startup process.

The technical solutions of the embodiments of the present application detect the execution status of the boot animation process before the execution time of the preset detection service exceeds the preset time threshold, and determine whether the boot is successful according to the execution status of the boot animation process; if the boot fails, then Print the key information corresponding to each error stage of the entire boot process as the boot exception log, and store the boot exception log securely in the reserved partition, so that it can cover the entire stage of the upper-layer boot process, not limited to a single module or service. , to avoid the situation of missed detection; in addition, it can also avoid the loss of the log file that records the key information of abnormal startup caused by flashing or restarting the terminal.

FIG. 4 is a flowchart of another method for detecting a problem of abnormal startup of a terminal provided by an embodiment of the present application. As shown in FIG. 4 , the method includes:

Step 401, it is detected that the init process is started.

Step 402: Periodically acquire attribute information of the boot animation service through a preset detection service.

Step 403: Obtain the execution time of the boot animation process.

Step 404 , determine whether the execution time is less than the preset time threshold, if yes, go to step 405 , otherwise go to step 408 .

Step 405 , determine whether the attribute information is an attribute value representing the end of the boot animation, if so, go to step 406 , otherwise go to step 407 .

Step 406 , determining that the boot animation process is in an ending state, and determining that the boot is successful.

Step 407: Determine that the boot animation process is in the state of executing the boot animation service.

It should be noted that, in the current cycle, it is determined that the boot animation process is in the state of executing the boot animation service, and the preset detection service waits for the set time to arrive in the next cycle, and returns to step 403 to obtain the execution time of the boot animation process, and then executes in sequence. Steps 404 and 405 , execute the above steps cyclically until the execution time exceeds the preset time threshold, or until it is detected that the boot animation process is in the end state before the execution time exceeds the preset time threshold.

Step 408: If the boot animation process is always in the state of executing the boot animation service, it is determined that the boot fails.

Step 409: When it is determined based on the state information that the startup fails, acquire a startup exception log corresponding to the startup process.

Step 410: Store the boot exception log in a reserved partition.

Step 411: When it is detected that a preset condition is met, acquire the target information and output it in the form of a log file.

It should be noted that the preset conditions include but are not limited to detecting an information acquisition request of a preset diagnostic tool, and normal booting after detecting a booting abnormality. Among them, the normal startup includes the normal startup after the system automatically restarts after the startup is abnormal; in addition, the normal startup also includes the normal startup after the flashing machine, etc.

Exemplarily, when an information acquisition request sent by a preset diagnostic tool is detected, the log file is read from the reserved partition and sent to the preset diagnostic tool. The preset diagnostic tool may be a program for diagnosing problems such as the terminal not being powered on, the terminal being crashed, or the terminal being stuck when powered on.

Optionally, after saving the target information that causes the boot failure failure in the boot process, the target data in the data partition (also referred to as the data partition) is cleared, and the terminal is controlled to restart. If the boot process of the terminal is stuck in the boot animation stage, there may be files or folders that cause abnormal playback of the boot animation. You can clear such files or folders in the data to enable the terminal to boot successfully. For example, characteristic information (including file name or suffix name, etc.) of the file or folder that causes the terminal boot process to be stuck in the boot animation can be determined by analyzing historical fault data. After it is detected that the startup fails, the files or folders conforming to the above characteristic information are deleted from the data partition, and then the terminal is controlled to restart to check whether the problem of the failure of the terminal startup has been overcome. If the terminal is successfully powered on, the above-mentioned target information stored in the boot process that caused the failure to boot will be output to the setting server in the form of a log file, so that the R&D personnel of the terminal manufacturer can obtain the key information corresponding to each terminal failure to boot. It can be understood that there may be many ways for the terminal to send the log to the setting server, which is not specifically limited in this embodiment of the present application. For example, logs can be uploaded to the terminal manufacturer's setting server through WiFi. For another example, the method may also be through a short message or a mobile data method.

In addition, the terminal can be successfully powered on by flashing, and the boot exception log with target information is stored in the reserved partition in advance, and the data in the reserved partition will not be lost due to the flashing operation.

The technical solutions of the embodiments of the present application, after the terminal fails to boot up, try to repair the cause of the terminal boot failure by clearing the target data in the data partition, and detect whether the terminal can be successfully booted. The log file (also known as the boot exception log) is output to the setting server so that the terminal manufacturer can obtain the log file, thereby providing a data basis for the R&D personnel to determine the cause of the abnormal boot of the terminal, and further, it can be effectively optimized. boot process.

FIG. 5 is a structural block diagram of an apparatus for detecting abnormal startup of a terminal according to an embodiment of the present application. The apparatus can be implemented by software and/or hardware, and is generally integrated in a terminal, and can monitor upper layers by executing a method for detecting abnormal startup of a terminal. The complete stage of the boot process. As shown in Figure 5, the device includes:

The startup detection module 510 is used to detect the startup of the init process;

The information obtaining module 520 is configured to obtain state information of the boot animation process through a preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file;

The information storage module 530 is configured to save the target information that causes the failure to boot in the boot process when it is determined that the boot fails according to the state information.

An embodiment of the present application provides an apparatus for detecting abnormal startup of a terminal. When it is detected that an init process is started, state information of a startup animation process is obtained through a preset detection service, wherein the program code corresponding to the preset detection service is in the init process. Executed when parsing the init.rc file; when it is determined that the boot fails according to the state information, the target information that causes the boot failure in the boot process is saved. Through the above technical solution, the preset detection service can be started after the boot process enters the Android layer to detect the boot state, and when the boot fails, the logs that cause the problem of not booting in the entire process can be obtained for storage, and the logs can be returned to the terminal. Manufacturer; it can cover the entire stage of the boot process to avoid the problem of missed detection. In addition, saving the target information that causes the boot failure can also facilitate the terminal developers to analyze the reasons for the non-boot problem, and then optimize the terminal boot process.

Optionally, the information acquisition module 520 is specifically used for:

The attribute information of the boot animation service is periodically acquired through the preset detection service, and the state information of the boot animation process is determined according to the attribute information.

Optionally, the step of determining the state information of the boot animation process according to the attribute information in the information acquisition module 520 specifically includes:

Get the execution time of the boot animation process;

When the execution time is less than the preset time threshold, determine whether the attribute information is an attribute value representing the end of the boot animation;

If so, determine that the boot animation process is in the end state;

Otherwise, it is determined that the boot animation process is in the state of executing the boot animation service.

Optionally, also include:

The booting judgment module is configured to, after judging whether the attribute information is an attribute value representing the end of the booting animation, if it is detected that the booting animation process is in the end state before the execution time exceeds the preset time threshold, then Make sure the boot is successful;

If the startup animation process is always in the state of executing the startup animation service before the execution time exceeds the preset time threshold, it is determined that the startup fails.

Optionally, the information storage module 530 is specifically used for:

When it is determined based on the state information that the startup fails, a startup exception log corresponding to the startup process is obtained, wherein the startup exception log includes target information that causes the terminal to fail to boot in the entire startup process;

The boot exception log is stored in a reserved partition, wherein the read and write frequency of the reserved partition is lower than a set threshold, and the reserved partition will not be erased during flashing.

Optionally, also include:

The file output module is configured to obtain the target information and output it in the form of a log file when it is detected that a preset condition is met after saving the target information that caused the failure to boot during the boot process.

Optionally, the file output module is specifically used to:

Clear the target data in the data partition, and control the terminal to restart;

If the terminal is successfully powered on after restarting, the target information is output to the setting server in the form of a log file.

Embodiments of the present application further provide a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute a method for detecting an abnormal startup of a terminal when the computer-executable instructions are executed by a computer processor, and the method includes:

It is detected that the init process is started;

Obtain the state information of the boot animation process through the preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file;

When the boot failure is determined according to the state information, the target information that causes the boot failure failure in the boot process is saved.

storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; non-volatile memory, such as flash memory, magnetic media (eg hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a second, different computer system connected to the first computer system through a network such as the Internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (eg, in different computer systems connected by a network). The storage medium may store program instructions (eg, embodied as a computer program) executable by one or more processors.

Of course, a storage medium containing computer-executable instructions provided by the embodiments of the present application, the computer-executable instructions of the computer-executable instructions are not limited to the above-mentioned operations of detecting abnormal terminal startup problems, and can also execute the operations provided by any embodiment of the present application. Relevant operations in the method for detecting abnormal startup of a terminal.

The embodiment of the present application provides a terminal, the terminal has an operating system, and the device for detecting an abnormal startup of the terminal provided by the embodiment of the present application can be integrated into the terminal. FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present application. As shown in FIG. 6 , the terminal includes a memory 610 and a processor 620 . The memory 610 is used to store computer programs and the like; the processor 620 reads and executes the computer programs stored in the memory 610 . The processor 620 implements the following steps when executing the computer program: detecting that the init process is started; obtaining state information of the boot animation process through a preset detection service, wherein the program code corresponding to the preset detection service parses init in the init process .rc file; when it is determined that the boot fails according to the state information, the target information that causes the boot failure in the boot process is saved.

The memories and processors listed in the above examples are all parts of the terminal, and the terminal may also include other components. Taking a smart phone as an example, the possible structure of the above-mentioned terminal will be described. FIG. 7 is a structural block diagram of a smart phone provided by an embodiment of the present application. As shown in FIG. 7, the smart phone may include: a memory 701, a central processing unit (Central Processing Unit, CPU) 702 (also known as a processor, hereinafter referred to as CPU), a peripheral interface 703, an RF (Radio Frequency, radio frequency) circuit 705, Audio circuitry 706, speakers 711, touch screen 712, power management chip 708, input/output (I/O) subsystem 709, other input/control devices 710, and external ports 704 through one or more communication buses or signal lines 707 to communicate.

It should be understood that the illustrated smartphone 700 is merely an example of a terminal, and that the smartphone 700 may have more or fewer components than those shown, two or more components may be combined, or Different component configurations are possible. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The following will describe in detail the smart phone integrated with the device for detecting abnormal startup of the terminal provided in this embodiment.

Memory 701, which can be accessed by CPU 702, peripheral interface 703, etc., said memory 701 can include high-speed random access memory, and can also include non-volatile memory, such as one or more disk storage devices, flash memory devices , or other volatile solid-state storage devices. The memory includes a reserved partition customized by the terminal manufacturer. The read and write frequency of the reserved partition is lower than the set threshold, and the reserved partition will not be erased when the device is flashed. A computer program is stored in the memory 701, and log files and the like may also be stored.

A peripheral interface 703 that can connect the input and output peripherals of the device to the CPU 702 and the memory 701 .

I/O subsystem 709 , which can connect input and output peripherals on the device, such as touch screen 712 and other input/control devices 710 , to peripherals interface 703 . The I/O subsystem 709 may include a display controller 7091 and one or more input controllers 7092 for controlling other input/control devices 710 . Wherein, one or more input controllers 7092 receive electrical signals from or send electrical signals to other input/control devices 710, which may include physical buttons (push buttons, rocker buttons, etc. ), dial pad, slide switch, joystick, click wheel. Notably, the input controller 7092 can be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

The touch screen 712, which is an input interface and an output interface between the user terminal and the user, displays visual output to the user, and the visual output may include graphics, text, icons, videos, and the like.

Display controller 7091 in I/O subsystem 709 receives electrical signals from touch screen 712 or sends electrical signals to touch screen 712 . The touch screen 712 detects the contact on the touch screen, and the display controller 7091 converts the detected contact into interaction with the user interface object displayed on the touch screen 712, that is, to realize human-computer interaction, and the user interface object displayed on the touch screen 712 can be run. Icons for games, icons for connecting to the corresponding network, etc. It is worth noting that the device may also include a light mouse, which is a touch-sensitive surface that does not display visual output, or an extension of the touch-sensitive surface formed by a touch screen.

The RF circuit 705 is mainly used to establish the communication between the mobile phone and the wireless network (ie, the network side), and realize the data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving text messages, e-mails, etc. Specifically, the RF circuit 705 receives and transmits RF signals, also known as electromagnetic signals, the RF circuit 705 converts electrical signals into electromagnetic signals or converts electromagnetic signals into electrical signals, and communicates with communication networks and other devices through the electromagnetic signals to communicate. RF circuitry 705 may include known circuitry for performing these functions including, but not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODECs ( COder-DECoder, codec) chip set, subscriber identity module (Subscriber Identity Module, SIM) and so on.

The audio circuit 706 is mainly used for receiving audio data from the peripheral interface 703 , converting the audio data into an electrical signal, and sending the electrical signal to the speaker 711 .

The speaker 711 is used to restore the voice signal received by the mobile phone from the wireless network through the RF circuit 705 to sound and play the sound to the user.

The power management chip 708 is used for power supply and power management for the hardware connected to the CPU 702, the I/O subsystem and the peripheral interface.

The terminal provided by the embodiment of the present application can start the preset detection service to detect the boot state after the boot process enters the Android level, and when the boot fails, obtain the logs that cause the problem of not booting in the entire process for storage, and can return the logs to It can be transmitted to the terminal manufacturer; it can cover the entire stage of the boot process to avoid the problem of missed detection. In addition, saving the target information that causes the boot failure can also facilitate the terminal developers to analyze the reasons for the failure to boot, and then optimize the terminal boot process. .

The apparatus, storage medium and terminal for detecting abnormal terminal startup problems provided in the above embodiments can execute the method for detecting abnormal terminal startup problems provided by any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the foregoing embodiments, reference may be made to the method for detecting an abnormal problem of terminal startup provided by any embodiment of the present application.

Note that the above are only preferred embodiments of the present application and applied technical principles. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present application. The scope is determined by the scope of the appended claims.

Claims (9)

1. a method for detecting abnormal problem of terminal startup, it is characterized in that, comprising: It is detected that the init process is started; Obtain the state information of the boot animation process through the preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file; When it is determined according to the state information that the boot fails, the target information that causes the failure to boot in the boot process is saved; When it is determined that the startup fails according to the state information, the target information that causes the startup failure in the startup process is saved, including: When it is determined based on the state information that the startup fails, a startup exception log corresponding to the startup process is obtained, wherein the startup exception log includes target information that causes the terminal to fail to boot in the entire startup process; The boot exception log is stored in a reserved partition, wherein the read and write frequency of the reserved partition is lower than a set threshold, and the reserved partition will not be erased during flashing. 2. The method according to claim 1, wherein obtaining the state information of the boot animation process through a preset detection service, comprising: The attribute information of the boot animation service is periodically acquired through the preset detection service, and the state information of the boot animation process is determined according to the attribute information. 3. The method according to claim 2, wherein determining the state information of the boot animation process according to the attribute information, comprising: Get the execution time of the boot animation process; When the execution time is less than a preset time threshold, determine whether the attribute information is an attribute value representing the end of the boot animation; If so, determine that the boot animation process is in the end state; Otherwise, it is determined that the boot animation process is in the state of executing the boot animation service. 4. The method according to claim 3, wherein after judging whether the attribute information is an attribute value representing the end of the boot animation, the method further comprises: If it is detected that the boot animation process is in an ending state before the execution time exceeds the preset time threshold, it is determined that the boot is successful; If the startup animation process is always in the state of executing the startup animation service before the execution time exceeds the preset time threshold, it is determined that the startup fails. 5. The method according to claim 1, characterized in that, after saving the target information causing the failure to boot in the boot process, the method further comprises: When it is detected that the preset condition is met, the target information is acquired and output in the form of a log file. 6. The method according to claim 5, wherein when detecting that a preset condition is met, acquiring the target information and outputting it in the form of a log file, comprising: Clear the target data in the data partition and control the terminal to restart; If the terminal is successfully powered on after restarting, the target information is output to the setting server in the form of a log file. 7. A device for detecting abnormality of terminal startup, characterized in that it comprises: The startup detection module is used to detect the startup of the init process; an information acquisition module, configured to acquire state information of the boot animation process through a preset detection service, wherein the program code corresponding to the preset detection service is executed when the init process parses the init.rc file; an information storage module, configured to save the target information that caused the failure to boot in the boot process when it is determined according to the state information that the boot fails; The information storage module is specifically used for: When it is determined based on the state information that the startup fails, a startup exception log corresponding to the startup process is obtained, wherein the startup exception log includes target information that causes the terminal to fail to boot in the entire startup process; The boot exception log is stored in a reserved partition, wherein the read and write frequency of the reserved partition is lower than a set threshold, and the reserved partition will not be erased during flashing. 8 . A computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the method for detecting an abnormal problem of starting a terminal as claimed in any one of claims 1 to 6 is implemented. 9. A terminal, characterized in that, comprising a memory, a processor and a computer program stored on the memory and running on the processor, and when the processor executes the computer program, any one of claims 1-6 is realized. The above-mentioned method for detecting the abnormal problem of terminal startup.

Images