CN109976950B - Android system dynamic starting method, mobile terminal and computer readable storage medium - Google Patents
Android system dynamic starting method, mobile terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN109976950B CN109976950B CN201910242308.XA CN201910242308A CN109976950B CN 109976950 B CN109976950 B CN 109976950B CN 201910242308 A CN201910242308 A CN 201910242308A CN 109976950 B CN109976950 B CN 109976950B
- Authority
- CN
- China
- Prior art keywords
- hardware
- list file
- mobile terminal
- information
- detection list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000001514 detection method Methods 0.000 claims abstract description 95
- 238000012217 deletion Methods 0.000 claims abstract description 40
- 230000037430 deletion Effects 0.000 claims abstract description 40
- 230000008439 repair process Effects 0.000 claims description 13
- 230000005856 abnormality Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 description 16
- 230000008569 process Effects 0.000 description 15
- 230000006854 communication Effects 0.000 description 13
- 238000004891 communication Methods 0.000 description 12
- 230000009471 action Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000007689 inspection Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000001629 suppression Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
Abstract
The invention discloses a dynamic starting method of an Android system, a mobile terminal and a computer readable storage medium, wherein the method comprises the following steps: setting a hardware detection list file; setting a hardware deletion list file; starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list; if the hardware damage is detected, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into a hardware deletion list file; the mobile terminal is restarted. According to the invention, when the mobile terminal has hardware damage or hardware missing, the system can automatically detect and avoid the problem and complete the starting.
Description
Technical Field
The present invention relates to the field of mobile terminals, and in particular, to a method for dynamically starting an Android system, a mobile terminal, and a computer readable storage medium.
Background
Android is a Linux-based operating system with free and open source code. The method is mainly used for mobile equipment such as smart phones, tablet computers, smart car machine systems and the like.
The key flow of the startup of the Android device is as follows:
<1> bootloader loading bootstrap;
<2> linux Kernel boot (load various drivers);
<3> load the first process init at user level, which will load an init. Rc configuration file first;
<4> init. Rc configuration files are configured in a related manner, necessary folders and files are created, then some Android drivers are initialized, and then one of the most important tasks of the configuration files is to start a zygate (incubator) process, which is a parent process of an Android system and used for starting other service processes of the Android, so that the Android starting process is completed.
However, during the use process, some device of the machine is often damaged due to some irresistible external force or other reasons, and in addition, due to the diversity and diversification of clients, the Android equipment needs to be cut frequently and repeatedly, for example: removing the camera, removing a sensor, etc. If the intelligent vehicle system does not need a motor device and the like, the motor device is cut off, so that the device is missing.
The damage and the loss of the device can cause the Android system to be unable to start, thereby affecting the normal use of the terminal.
Disclosure of Invention
The invention mainly aims to provide a dynamic starting method of an Android system, a mobile terminal and a computer readable storage medium, and aims to provide a technical means capable of automatically detecting the damage or the loss of a device of the terminal and completing the normal starting of a system under the damage or the loss of the device.
In order to achieve the above purpose, the method for dynamically starting the Android system provided by the invention comprises the following steps:
setting a hardware detection list file;
setting a hardware deletion list file;
starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
if the hardware damage is detected, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into a hardware deletion list file;
the mobile terminal is restarted.
Further, the method starts the mobile terminal in the step, parses the hardware detection list file, and detects hardware disposed in the mobile terminal according to the hardware detection list, and then includes: if no hardware abnormality is detected, the mobile terminal is started according to the hardware specified in the hardware detection list file.
Further, the method includes, after restarting the mobile terminal in the step:
and sending a suggestion for overhauling damaged hardware to a user.
Further, the method comprises the steps of:
and after the repair of the damaged hardware is completed, removing the information of the hardware from the hardware missing list file, and simultaneously storing the information of the hardware in the hardware detection list file.
Further, the method starts the mobile terminal in the step, parses the hardware detection list file, and detects hardware disposed in the mobile terminal according to the hardware detection list, and then further includes:
if a hardware loss is detected, the information of the hardware is removed from the hardware detection list file.
To achieve the above object, the present invention also provides a mobile terminal comprising a memory, a processor and at least one application program stored in the memory and configured to be executed by the processor, the at least one application program being configured to perform the steps of:
setting a hardware detection list file;
setting a hardware deletion list file;
starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
if the hardware damage is detected, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into a hardware deletion list file;
the mobile terminal is restarted.
Further, the processor starts the mobile terminal in the executing step, parses the hardware detection list file, and executes after detecting hardware disposed in the mobile terminal according to the hardware detection list:
if no hardware abnormality is detected, the mobile terminal is started according to the hardware specified in the hardware detection list file.
Further, the processor further performs, after performing the step of restarting the mobile terminal:
after the repair of the damaged hardware is completed, removing the information of the hardware from the hardware missing list file, and simultaneously storing the information of the hardware in the hardware detection list file
Further, the processor starts the mobile terminal in the executing step, and parses the hard
The piece detection list file is arranged on the mobile terminal according to the hardware detection list detection
The hardware at the end also performs thereafter:
if a hardware loss is detected, the information of the hardware is removed from the hardware detection list file.
In addition, in order to achieve the above purpose, the invention further provides a computer readable storage medium, wherein the computer readable storage medium stores an Android system dynamic starting program, and the Android system dynamic starting program realizes the steps of any one of the Android system dynamic starting methods when executed by a processor.
According to the Android system dynamic starting method, the mobile terminal and the computer readable storage medium, by setting the hardware detection list file and the hardware deletion list file, when the system is started, whether hardware in the hardware detection list file is damaged or not is detected, if the hardware is damaged or not, the hardware information is removed from the hardware detection list file and enters the hardware deletion list file, and then the system is restarted, so that the normal starting of the system can be realized according to the new hardware detection list file, the problem that the system cannot be started normally when the hardware is damaged or lost is solved, the user experience is improved, and the degree of freedom of hardware cutting is enhanced.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention;
fig. 2 is a schematic diagram of a wireless communication system of the mobile terminal shown in fig. 1;
fig. 3 is a schematic flow chart of an implementation of the dynamic startup method of the Android system according to the first embodiment of the present invention;
fig. 4 is a schematic flow chart of an implementation of the dynamic startup method of the Android system according to the second embodiment of the present invention;
fig. 5 is a schematic flow chart of an implementation of the method for dynamically starting the Android system according to the third embodiment of the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present invention, and have no specific meaning per se. Thus, "module," "component," or "unit" may be used in combination.
The terminal may be implemented in various forms. For example, the terminals described in the present invention may include mobile terminals such as mobile phones, tablet computers, notebook computers, palm computers, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable MediaPlayer, PMP), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs, desktop computers, and the like.
The following description will be given taking a mobile terminal as an example, and those skilled in the art will understand that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for a moving purpose.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention, the mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will appreciate that the mobile terminal structure shown in fig. 1 is not limiting of the mobile terminal and that the mobile terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The following describes the components of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be used for receiving and transmitting signals during the information receiving or communication process, specifically, after receiving downlink information of the base station, processing the downlink information by the processor 110; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System ofMobile communication, global System for Mobile communications), GPRS (General Packet Radio Service ), CDMA2000 (Code Division Multiple Access, CDMA 2000), WCDMA (Wideband Code DivisionMultiple Access ), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, time Division synchronous code Division multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution, frequency Division Duplex Long term evolution), and TDD-LTE (Time Division Duplexing-Long Term Evolution, time Division Duplex Long term evolution), etc.
WiFi belongs to a short-distance wireless transmission technology, and a mobile terminal can help a user to send and receive e-mails, browse web pages, access streaming media and the like through the WiFi module 102, so that wireless broadband Internet access is provided for the user. Although fig. 1 shows a WiFi module 102, it is understood that it does not belong to the necessary constitution of a mobile terminal, and can be omitted entirely as required within a range that does not change the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the mobile terminal 100. The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive an audio or video signal. The a/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sound into audio data. The processed audio (voice) data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting the audio signal.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 1061 and/or the backlight when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; as for other sensors such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured in the mobile phone, the detailed description thereof will be omitted.
The display unit 106 is used to display information input by a user or information provided to the user. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile terminal. In particular, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1071 or thereabout by using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 110, and can receive and execute commands sent from the processor 110. Further, the touch panel 1071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 107 may include other input devices 1072 in addition to the touch panel 1071. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc., as specifically not limited herein.
Further, the touch panel 1071 may overlay the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or thereabout, the touch panel 1071 is transferred to the processor 110 to determine the type of touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of touch event. Although in fig. 1, the touch panel 1071 and the display panel 1061 are two independent components for implementing the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 may be integrated with the display panel 1061 to implement the input and output functions of the mobile terminal, which is not limited herein.
The interface unit 108 serves as an interface through which at least one external device can be connected with the mobile terminal 100. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.
Memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power source 111 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 111 may be logically connected to the processor 110 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the mobile terminal of the present invention is based will be described below.
Referring to fig. 2, fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present invention, where the communication network system is an LTE system of a general mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an e-UTRAN (EvolvedUMTS Terrestrial Radio Access Network ) 202, an epc (EvolvedPacket Core, evolved packet core) 203, and an IP service 204 of an operator that are sequentially connected in communication.
Specifically, the UE201 may be the terminal 100 described above, and will not be described herein.
The E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. The eNodeB2021 may be connected with other eNodeB2022 by a backhaul (e.g., an X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide access from the UE201 to the EPC 203.
EPC203 may include MME (mobility management entity) 2031, hss (Home Subscriber Server ) 2032, other MME2033, SGW (Serving gateway) 2034, pgw (PDN gateway) 2035 and PCRF (Policy and Charging Rules Function, policy and tariff function entity) 2036, etc. The MME2031 is a control node that handles signaling between the UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location registers (not shown) and to hold user specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034 and PGW2035 may provide IP address allocation and other functions for UE201, PCRF2036 is a policy and charging control policy decision point for traffic data flows and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem ), or other IP services, etc.
Although the LTE system is described above as an example, it should be understood by those skilled in the art that the present invention is not limited to LTE systems, but may be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above mobile terminal hardware structure and the communication network system, various embodiments of the method of the present invention are provided.
Example 1
The first embodiment of the invention provides a dynamic starting method of an Android system, as shown in fig. 3, comprising the following steps:
s11, setting a hardware detection list file and a hardware deletion list file;
specifically, a hardware check list file is configured and recorded as a device_check.list, and the hardware information configured in the hardware check list file represents that whether hardware is damaged or missing needs to be detected when the system is started.
And configuring a device deletion list file, namely a device_defect list, wherein the hardware information configured by the device deletion list file represents damaged or missing hardware of the mobile terminal, and the hardware listed in the device deletion list file does not need to be detected when the system is started.
S12, starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
s13, judging whether hardware damage is detected, if so, executing a step S14, otherwise, executing a step S16;
specifically, when Linux Kernel is started, devices_check_list is analyzed, and corresponding hardware is checked.
S14, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
if a certain device is damaged, the device information is stored in a device_defect.list file, for example, if a camera is damaged, the camera information is stored in the device_defect.list file, and the hardware inspection of the camera is not performed when the system is started.
S15, restarting the mobile terminal;
after the action of storing the damaged device information in the device_defect. List file is completed, the mobile terminal is automatically restarted.
S16, starting the mobile terminal according to the hardware specified in the hardware detection list file.
After the checking in step S13, all the damaged hardware has been removed from the hardware checking list file and listed in the hardware missing list file, i.e. the device_defect. List file, and at the restart in step S14, all the hardware in the detected hardware checking list file, i.e. the device_check. List file, is not damaged, so the system can complete the normal startup.
After the starting is finished, in order to enable a user to clearly know the damage condition of the hardware and remind the user to timely process the damaged hardware, a suggestion for overhauling the damaged hardware is sent to the user. The user can replace or repair the corresponding hardware of the mobile terminal, and after the repair of the damaged hardware is completed, the user removes the information of the hardware from the hardware missing list file, and meanwhile, the information of the hardware is stored in the hardware detection list file. I.e. when the camera is damaged as before, the mobile terminal has solved the problem of hardware damage after repairing or replacing the camera, and thus it is necessary to manually modify the hardware check list file, i.e. the devices_check.list file, delete the information of the corresponding device therefrom, and add the information of the device to the hardware check list file, i.e. the devices_check.list.
According to the Android system dynamic starting method, by setting the hardware detection list file and the hardware deletion list file, when the system is started, whether hardware in the hardware detection list file is damaged or not is detected, if yes, the hardware information is removed from the hardware detection list file to enter the hardware deletion list file, and then the system is restarted, so that normal starting of the system can be realized according to the new hardware detection list file, and the problem that the system cannot be started normally and needs to be overhauled when the hardware is damaged or lost is solved, user experience is improved, and the degree of freedom of hardware cutting is enhanced.
Example two
The second embodiment of the invention provides a dynamic starting method of an Android system, as shown in fig. 4, comprising the following steps:
s21, setting a hardware detection list file and a hardware deletion list file;
specifically, a hardware check list file is configured and recorded as a device_check.list, and the hardware information configured in the hardware check list file represents that whether hardware is damaged or missing needs to be detected when the system is started.
And configuring a device deletion list file, namely a device_defect list, wherein the hardware information configured by the device deletion list file represents damaged or missing hardware of the mobile terminal, and the hardware listed in the device deletion list file does not need to be detected when the system is started.
S22, starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
s23, judging whether hardware damage is detected, if so, executing a step S24, otherwise, executing a step S26;
specifically, when Linux Kernel is started, devices_check_list is analyzed, and corresponding hardware is checked.
S24, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
if a certain device is damaged, the device information is stored in a device_defect.list file, for example, if a camera is damaged, the camera information is stored in the device_defect.list file, and the hardware inspection of the camera is not performed when the system is started.
S25, restarting the mobile terminal;
after the action of storing the damaged device information in the device_defect. List file is completed, the mobile terminal is automatically restarted.
S26, starting the mobile terminal according to the hardware specified in the hardware detection list file;
through the checking in step S23, all the damaged hardware has been removed from the hardware checking list file and listed in the hardware missing list file, i.e. the device_defect. List file, and at the restart in step S24, all the hardware in the detected hardware checking list file, i.e. the device_check. List file, is not damaged, so the system can complete the normal startup.
S27, a suggestion of overhauling damaged hardware is sent to a user.
After the starting is finished, in order to enable a user to clearly know the damage condition of the hardware and remind the user to timely process the damaged hardware, a suggestion for overhauling the damaged hardware is sent to the user. The user can replace or repair the corresponding hardware of the mobile terminal, and after the repair of the damaged hardware is completed, the user removes the information of the hardware from the hardware missing list file, and meanwhile, the information of the hardware is stored in the hardware detection list file. I.e. when the camera is damaged as before, the mobile terminal has solved the problem of hardware damage after repairing or replacing the camera, and thus it is necessary to manually modify the hardware check list file, i.e. the devices_check.list file, delete the information of the corresponding device therefrom, and add the information of the device to the hardware check list file, i.e. the devices_check.list.
According to the Android system dynamic starting method, by setting the hardware detection list file and the hardware deletion list file, when the system is started, whether hardware in the hardware detection list file is damaged or not is detected, if the hardware is damaged or not, the hardware information is removed from the hardware detection list file to enter the hardware deletion list file, then the system is restarted, normal starting of the system can be achieved according to the new hardware detection list file, then the hardware damage condition is used for sending overhaul suggestions, and a user is helped to know the hardware damage condition and take repair measures properly; therefore, the problem that the system cannot be started normally and needs to be overhauled when the hardware is damaged or lost is solved, the user experience is improved, and the degree of freedom of hardware cutting is enhanced.
Example III
A third embodiment of the present invention provides a method for dynamically starting an Android system, as shown in FIG. 5, including the following steps:
s31, setting a hardware detection list file and a hardware deletion list file;
specifically, a hardware check list file is configured and recorded as a device_check.list, and the hardware information configured in the hardware check list file represents that whether hardware is damaged or missing needs to be detected when the system is started.
And configuring a device deletion list file, namely a device_defect list, wherein the hardware information configured by the device deletion list file represents damaged or missing hardware of the mobile terminal, and the hardware listed in the device deletion list file does not need to be detected when the system is started.
S32, starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
s33, judging whether hardware damage is detected, if so, executing a step S34, otherwise, executing a step S38;
specifically, when Linux Kernel is started, devices_check_list is analyzed, and corresponding hardware is checked.
S34, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
if a certain device is damaged, the device information is stored in a device_defect.list file, for example, if a camera is damaged, the camera information is stored in the device_defect.list file, and the hardware inspection of the camera is not performed when the system is started.
S35, judging whether hardware loss is detected, if so, executing a step S36, otherwise, executing a step S38;
s36, removing the information of the hardware from the hardware detection list file;
if a device is missing, the device information is stored in the device_defect. List file, for example, if the camera is missing, the user may cut the camera, so that the hardware cannot be found, the camera information is removed from the hardware detection list file, and the system is started without checking the hardware of the camera.
S37, restarting the mobile terminal;
after the action of storing the damaged device information in the device_defect. List file is completed, the mobile terminal is automatically restarted.
S38, starting the mobile terminal according to the hardware specified in the hardware detection list file;
after the checking in step S33, all the damaged hardware has been removed from the hardware checking list file and listed in the hardware missing list file, i.e. the device_defect. List file, and at the restart in step S37, all the hardware in the detected hardware checking list file, i.e. the device_check. List file, is not damaged, so the system can complete the normal startup.
After the starting is finished, in order to enable a user to clearly know the damage condition of the hardware and remind the user to timely process the damaged hardware, a suggestion for overhauling the damaged hardware is sent to the user. The user can replace or repair the corresponding hardware of the mobile terminal, and after the repair of the damaged hardware is completed, the user removes the information of the hardware from the hardware missing list file, and meanwhile, the information of the hardware is stored in the hardware detection list file. I.e. when the camera is damaged as before, the mobile terminal has solved the problem of hardware damage after repairing or replacing the camera, and thus it is necessary to manually modify the hardware check list file, i.e. the devices_check.list file, delete the information of the corresponding device therefrom, and add the information of the device to the hardware check list file, i.e. the devices_check.list.
According to the Android system dynamic starting method, by setting the hardware detection list file and the hardware deletion list file, when the system is started, whether hardware in the hardware detection list file is damaged or not is detected, if the hardware is damaged or not, the hardware information is removed from the hardware detection list file to enter the hardware deletion list file, and then the system is restarted, so that the normal starting of the system can be realized according to the new hardware detection list file, the problem that the system cannot be started normally and needs to be overhauled when the hardware is damaged or lost is solved, user experience is improved, and the degree of freedom of hardware cutting is enhanced.
Example IV
A fourth embodiment of the present invention provides a mobile terminal, as shown in fig. 1, comprising a memory 109, a processor 110 and at least one application stored in said memory 109 and configured to be executed by said processor 110, said at least one application being configured to perform the steps of:
s11, setting a hardware detection list file and a hardware deletion list file;
specifically, a hardware check list file is configured and recorded as a device_check.list, and the hardware information configured in the hardware check list file represents that whether hardware is damaged or missing needs to be detected when the system is started.
And configuring a device deletion list file, namely a device_defect list, wherein the hardware information configured by the device deletion list file represents damaged or missing hardware of the mobile terminal, and the hardware listed in the device deletion list file does not need to be detected when the system is started.
S12, starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
s13, judging whether hardware damage is detected, if so, executing a step S14, otherwise, executing a step S16;
specifically, when Linux Kernel is started, devices_check_list is analyzed, and corresponding hardware is checked.
S14, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
if a certain device is damaged, the device information is stored in a device_defect.list file, for example, if a camera is damaged, the camera information is stored in the device_defect.list file, and the hardware inspection of the camera is not performed when the system is started.
S15, restarting the mobile terminal;
after the action of storing the damaged device information in the device_defect. List file is completed, the mobile terminal is automatically restarted.
S16, starting the mobile terminal according to the hardware specified in the hardware detection list file.
After the checking in step S13, all the damaged hardware has been removed from the hardware checking list file and listed in the hardware missing list file, i.e. the device_defect. List file, and at the restart in step S14, all the hardware in the detected hardware checking list file, i.e. the device_check. List file, is not damaged, so the system can complete the normal startup.
After the starting is finished, in order to enable a user to clearly know the damage condition of the hardware and remind the user to timely process the damaged hardware, a suggestion for overhauling the damaged hardware is sent to the user. The user can replace or repair the corresponding hardware of the mobile terminal, and after the repair of the damaged hardware is completed, the user removes the information of the hardware from the hardware missing list file, and meanwhile, the information of the hardware is stored in the hardware detection list file. I.e. when the camera is damaged as before, the mobile terminal has solved the problem of hardware damage after repairing or replacing the camera, and thus it is necessary to manually modify the hardware check list file, i.e. the devices_check.list file, delete the information of the corresponding device therefrom, and add the information of the device to the hardware check list file, i.e. the devices_check.list.
Optionally, the following step is further performed after step S13: judging whether the hardware is detected to be missing or not, and if the hardware is detected to be missing, removing the information of the hardware from the hardware detection list file.
According to the mobile terminal provided by the embodiment, the processor of the mobile terminal is used for executing the Android system dynamic starting method, by setting the hardware detection list file and the hardware deletion list file, when the system is started, whether hardware in the hardware detection list file is damaged or not is detected, if the hardware is damaged, the hardware information is removed from the hardware detection list file to enter the hardware deletion list file, and then the system is restarted, so that the normal starting of the system can be realized according to the new hardware detection list file, the problem that the system cannot be started normally and needs to be overhauled when the hardware is damaged or lost is solved, the user experience is improved, and the degree of freedom of hardware cutting is enhanced.
Example five
The fifth embodiment of the present invention provides a computer readable storage medium, where a dynamic Android system starting program is stored, and the steps of the dynamic Android system starting method described in any one of the first embodiment, the second embodiment, and the third embodiment are implemented when the dynamic Android system starting program is executed by a processor.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (8)
1. The Android system dynamic starting method is characterized by comprising the following steps of:
setting a hardware detection list file, wherein the hardware information configured in the hardware detection list file represents whether hardware is damaged or missing or not when the Android system is started;
setting a hardware missing list file, wherein hardware information configured by the equipment missing list file represents damaged or missing hardware of the mobile terminal, and hardware listed in the equipment missing list file does not need to be detected when an Android system is started;
starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
if the hardware damage or the hardware deletion is detected, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
the mobile terminal is restarted.
2. The method for dynamically starting an Android system according to claim 1, wherein after starting a mobile terminal in the step, parsing the hardware detection list file and detecting hardware disposed in the mobile terminal according to the hardware detection list comprises:
if no hardware abnormality is detected, the mobile terminal is started according to the hardware specified in the hardware detection list file.
3. The Android system dynamic boot method according to claim 1, wherein after restarting the mobile terminal, the method comprises:
and sending a suggestion for overhauling damaged hardware to a user.
4. The Android system dynamic startup method according to claim 3, wherein the method further comprises the steps of:
and after the repair of the damaged hardware is completed, removing the information of the hardware from the hardware missing list file, and simultaneously storing the information of the hardware in the hardware detection list file.
5. A mobile terminal comprising a memory, a processor and at least one application stored in the memory and configured to be executed by the processor, characterized in that the at least one application is configured to perform the steps of:
setting a hardware detection list file, wherein the hardware information configured in the hardware detection list file represents whether hardware is damaged or missing or not when the Android system is started;
setting a hardware missing list file, wherein hardware information configured by the equipment missing list file represents damaged or missing hardware of the mobile terminal, and hardware listed in the equipment missing list file does not need to be detected when an Android system is started;
starting the mobile terminal, analyzing the hardware detection list file, and detecting hardware arranged on the mobile terminal according to the hardware detection list;
if the hardware damage or the hardware deletion is detected, removing the information of the hardware from the hardware detection list file, and simultaneously storing the information of the hardware into the hardware deletion list file;
the mobile terminal is restarted.
6. The mobile terminal of claim 5, wherein the processor, after executing the steps to activate the mobile terminal, parse the hardware detection list file, and detect hardware disposed at the mobile terminal according to the hardware detection list, executes:
if no hardware abnormality is detected, the mobile terminal is started according to the hardware specified in the hardware detection list file.
7. The mobile terminal of claim 5, wherein the processor further performs, after performing the step of restarting the mobile terminal:
and after the repair of the damaged hardware is completed, removing the information of the hardware from the hardware missing list file, and simultaneously storing the information of the hardware in the hardware detection list file.
8. A computer readable storage medium, wherein an Android system dynamic start program is stored on the computer readable storage medium, and when the Android system dynamic start program is executed by a processor, the steps of the Android system dynamic start method according to any one of claims 1 to 4 are implemented.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910242308.XA CN109976950B (en) | 2019-03-28 | 2019-03-28 | Android system dynamic starting method, mobile terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910242308.XA CN109976950B (en) | 2019-03-28 | 2019-03-28 | Android system dynamic starting method, mobile terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109976950A CN109976950A (en) | 2019-07-05 |
| CN109976950B true CN109976950B (en) | 2024-01-09 |
Family
ID=67081179
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910242308.XA Active CN109976950B (en) | 2019-03-28 | 2019-03-28 | Android system dynamic starting method, mobile terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109976950B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6230285B1 (en) * | 1998-09-08 | 2001-05-08 | Symantec Corporation | Boot failure recovery |
| JP2009176232A (en) * | 2008-01-28 | 2009-08-06 | Fujitsu Ltd | Starting device, starting method, and starting program |
| CN105760264A (en) * | 2016-02-04 | 2016-07-13 | 浪潮电子信息产业股份有限公司 | Method and device for detecting faulty hardware equipment of server |
| CN108108198A (en) * | 2017-12-15 | 2018-06-01 | 联想(北京)有限公司 | For the method and system of computer system |
-
2019
- 2019-03-28 CN CN201910242308.XA patent/CN109976950B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6230285B1 (en) * | 1998-09-08 | 2001-05-08 | Symantec Corporation | Boot failure recovery |
| JP2009176232A (en) * | 2008-01-28 | 2009-08-06 | Fujitsu Ltd | Starting device, starting method, and starting program |
| CN105760264A (en) * | 2016-02-04 | 2016-07-13 | 浪潮电子信息产业股份有限公司 | Method and device for detecting faulty hardware equipment of server |
| CN108108198A (en) * | 2017-12-15 | 2018-06-01 | 联想(北京)有限公司 | For the method and system of computer system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109976950A (en) | 2019-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109587747B (en) | SIM card switching control method, terminal and computer storage medium | |
| CN109195143B (en) | Network access method, mobile terminal and readable storage medium | |
| CN109766119B (en) | Recovery partition upgrade method, terminal and computer readable storage medium | |
| CN107329865B (en) | Method for opening adb function of debugging bridge, mobile terminal and computer readable medium | |
| CN109040441B (en) | Application body-separating display method, mobile terminal and computer readable storage medium | |
| CN109901980B (en) | Serial port log capturing circuit, method, terminal and computer readable storage medium | |
| CN109144705B (en) | Application management method, mobile terminal and computer readable storage medium | |
| CN107862217B (en) | Position information acquisition method, mobile terminal and computer storage medium | |
| CN107172605B (en) | Emergency call method, mobile terminal and computer readable storage medium | |
| CN109002547B (en) | Log file storage method, mobile terminal and computer readable storage medium | |
| CN108121681B (en) | Hot plug implementation method, terminal and storage medium | |
| CN112597115A (en) | Container mirror image compression method and device, terminal equipment and medium | |
| CN109151216B (en) | Application starting method, mobile terminal, server and computer readable storage medium | |
| CN109522276B (en) | Application icon management method, terminal and computer-readable storage medium | |
| CN108629863B (en) | Method for automatically signing in application program, mobile terminal and readable storage medium | |
| CN113067734B (en) | Electronic price tag upgrading method, electronic price tag system, electronic terminal and storage medium | |
| CN110413330B (en) | Face unlocking initialization method, equipment and computer readable storage medium | |
| CN110209434B (en) | Memory management method and device and computer readable storage medium | |
| CN110099173B (en) | Touch experience mode switching method, terminal and storage medium | |
| CN112395106A (en) | Process management method, mobile terminal, and computer-readable storage medium | |
| CN110187934B (en) | Application control method, terminal and computer readable storage medium | |
| CN108845821B (en) | Application program updating method, terminal and computer readable storage medium | |
| CN108900696B (en) | Data processing method, terminal and computer readable storage medium | |
| CN109062688B (en) | Memory allocation method, server and mobile terminal | |
| CN108650404B (en) | Port starting circuit, device and mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |