CN107844382B - Card screen detection method, mobile terminal and computer readable storage medium - Google Patents

Card screen detection method, mobile terminal and computer readable storage medium Download PDF

Info

Publication number
CN107844382B
CN107844382B CN201711055210.0A CN201711055210A CN107844382B CN 107844382 B CN107844382 B CN 107844382B CN 201711055210 A CN201711055210 A CN 201711055210A CN 107844382 B CN107844382 B CN 107844382B
Authority
CN
China
Prior art keywords
result information
mobile terminal
card screen
information
library
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
Application number
CN201711055210.0A
Other languages
Chinese (zh)
Other versions
CN107844382A (en
Inventor
周龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nubia Technology Co Ltd
Original Assignee
Nubia Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nubia Technology Co Ltd filed Critical Nubia Technology Co Ltd
Priority to CN201711055210.0A priority Critical patent/CN107844382B/en
Publication of CN107844382A publication Critical patent/CN107844382A/en
Application granted granted Critical
Publication of CN107844382B publication Critical patent/CN107844382B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0787Storage of error reports, e.g. persistent data storage, storage using memory protection
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079Root cause analysis, i.e. error or fault diagnosis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1417Boot up procedures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/142Reconfiguring to eliminate the error
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Computing Systems (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a card screen detection method, a mobile terminal and a computer readable storage medium, wherein the card screen detection method comprises the following steps: in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker; acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information; and when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file. According to the invention, the card screen fault information is output to the characteristic log file, so that developers can conveniently inquire the characteristic log file when detecting and positioning the card screen reason of the mobile terminal, thereby quickly and accurately positioning the card screen reason and greatly reducing the labor cost and the time cost.

Description

Card screen detection method, mobile terminal and computer readable storage medium
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a card screen detection method, a mobile terminal and a computer readable storage medium.
Background
With the development of mobile terminal technology, more and more Applications (APPs) are integrated in the mobile terminal, and at present, tens of thousands of applications are installed on the mobile terminal based on different scenes of the mobile terminal, and with more and more third-party applications and service software installed on the mobile terminal by a user, when people use the mobile terminal daily, certain key points in the starting and starting process of the mobile terminal are easily affected, so that the mobile terminal is blocked at certain key points, and a screen blocking phenomenon occurs.
At present, when the screen clamping phenomenon occurs on the mobile terminal, a user is required to manually force the mobile terminal to be restarted to enable the mobile terminal to recover to a normal state, user experience is poor, in addition, the reason for the screen clamping phenomenon occurring on the mobile terminal is various, the mobile terminal cannot be recovered to a normal state by restarting the mobile terminal, the mobile terminal needs to be returned to a manufacturer for maintenance, and more time is required for developers to detect and position the screen clamping reason for the mobile terminal. Therefore, how to quickly position the screen clamping reason and reduce the labor cost and the time cost are problems to be solved urgently at present.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a card screen detection method, a mobile terminal and a computer readable storage medium, and aims to solve the technical problems of how to quickly locate the reason for the card screen and reduce the labor cost and the time cost.
In order to achieve the above object, the present invention provides a card screen detection method, which is applied to a mobile terminal, and comprises the following steps:
in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information;
and when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file.
Optionally, after the step of matching the graphics library calling data with preset feature information to obtain matching result information, the card screen detection method further includes:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage partition through the linker.
Optionally, after the step of matching the graphics library calling data with preset feature information to obtain matching result information, the card screen detection method further includes:
when the matching result information is matching pass, storing the graph library calling data to a preset storage area;
and when the mobile terminal is detected to be in a screen-off standby state, removing redundancy of the graph library calling data in the preset storage area, and storing the graph library calling data after redundancy removal.
Optionally, after the step of matching the graphics library calling data with preset feature information to obtain matching result information, the card screen detection method further includes:
monitoring the calling data of the graphic library to acquire monitoring result information when the matching result information is that the matching is not passed;
and judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
Optionally, the step of determining whether the graph library is abnormal according to the monitoring result information includes:
judging whether the monitoring result information contains preset information or not;
if the monitoring result information contains preset information, judging that the graphic library is abnormal;
and if the monitoring result information does not contain preset information, judging that the graphic library is not abnormal.
Optionally, after the step of outputting the monitoring result information to the feature log file, the card screen detection method further includes:
reading a characteristic log file from a preset storage area at regular time, and judging whether the bit number of the characteristic log file is greater than or equal to a preset bit number;
and uploading the feature log file to a preset cloud for storage when the bit number of the feature log file is greater than or equal to a preset bit number.
In addition, to achieve the above object, the present invention also provides a mobile terminal, including: the card screen detection method comprises a memory, a processor and a card screen detection program which is stored on the memory and can run on the processor, wherein the steps of the card screen detection method are realized when the card screen detection program is executed by the processor.
The present invention further provides a computer-readable storage medium, wherein a card screen detection program is stored on the computer-readable storage medium, and when being executed by a processor, the card screen detection program implements the steps of the card screen detection method as described above.
The invention provides a card screen detection method, a mobile terminal and a computer readable storage medium, wherein the mobile terminal calls a graphic library required by a system startup process of the mobile terminal through a linker during the system startup process, acquires graphic library calling data generated when the linker calls the graphic library, matches the graphic library calling data with preset characteristic information to acquire matching result information, extracts current card screen fault information from the graphic library calling data when the matching result information is matching pass, and outputs the current card screen fault information to a characteristic log file, the scheme acquires the graphic library calling data generated when the linker calls the graphic library, matches the graphic library calling data with the preset characteristic information to acquire matching result information, and determines whether the card screen fault occurs in the mobile terminal based on the matching result information, then, when the mobile terminal has a card screen fault, the current fault information in the calling data of the graphic library is output to the characteristic log file, so that developers can conveniently inquire the characteristic log file when detecting and positioning the card screen reason of the mobile terminal, the card screen reason can be quickly and accurately positioned, and the labor cost and the time cost are greatly reduced.
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 level diagram of an operating system of the mobile terminal according to the present invention;
FIG. 3 is a schematic flow chart illustrating a card screen detection method according to a first embodiment of the present invention;
FIG. 4 is a flowchart illustrating a card screen detection method according to a second embodiment of the present invention;
fig. 5 is a flowchart illustrating a card screen detection method according to a third embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.
The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, 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 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing 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 call 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 related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a 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 graphic 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 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone 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 audio signals.
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 that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
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 (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 generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, 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 a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a 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 direction 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 sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. 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, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (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 external devices 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 external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the 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.
Referring to fig. 2, which is a schematic hierarchical diagram of an operating system stored in a storage program area, as shown in fig. 2, the operating system includes a Loader layer, a Kernel layer, a Native layer, a Framework layer (including a C + + Framework layer and a Java Framework layer), and an App layer, where an HAL layer (hardware abstraction layer) also exists between the Kernel layer and the Native layer, a JNI layer also exists between the C + + Framework layer and the Java Framework layer, and a SysCall layer also exists between the HAL layer and the Kernel layer.
The Loader layer comprises a Boot ROM (Boot service) and a Boot Loader (Boot initialization program), wherein the Boot ROM is mainly used for booting by pressing a Power (Boot) key for a long time when the mobile terminal is in a Power-off state, and a Boot chip starts to execute from a preset code solidified in the ROM. The Boot Loader is a Boot program before starting the operating system, and mainly has the functions of checking the RAM, initializing hardware parameters and the like.
The Kernel layer is mainly used for performing related work such as initialization process management, memory management, Display loading, Camera Driver (Camera Driver), Binder Driver (Binder Driver) and the like, and is used for creating Kernel daemon processes such as Kernel worker threads kworkder, soft interrupt threads ksofirqd and soft interrupt threads thermal.
The Native layer mainly comprises a daemon process of a user space hatched by init, a HAL layer, startup animation and the like. User daemon processes, User Daemons, such as ueven, logd, health, installd, adbd, and lmkd, can hatch out from the Init process (a User-level process started by a kernel); the init process also starts important services such as servicemanager and bootanim; the init process hatches a Zygote process, the Zygote process is the first Java process of the operating system, the Zygote process is the parent process of all the Java processes, and the Zygote process is hatched from the init process.
The Framework layer comprises a Zygote process, a System Server (System service) process and a Media Server (multimedia service) process, wherein the Zygote process is generated by an init process through analysis of an init.rc file and then fork, and mainly comprises loading Zygote init classes, registering Zygote Socket service end sockets, loading virtual machines, preloadClasses, preloadResouces and the like; the System Server process is derived from a Zygote process fork, the System Server is the first process of Zygote incubation, and the System Server is responsible for starting and managing the whole Java Framework and comprises services such as an ActivitiManager (application program component), a PowerManager (power supply management component) and a WindowManagerServer (window management component); the Media Server process, which is derived from the init process fork, is responsible for starting and managing the whole C + + frame, and includes services such as audio pointer (afofinger), Camera Service (Camera Service), and MediaPlayServer (multimedia Service).
The APP layer comprises APP processes, each APP process is generated by a Zygote process fork, the first APP process hatched by the Zygote process is a Launcher (desktop Launcher), desktop APPs seen by a user are created by the Zygote process, the App processes such as a Browser, a Phone and an Email are also created by the Zygote process, and each App runs on at least one process.
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 operating 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, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly 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 supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via 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 in detail herein.
Based on the above mobile terminal hardware structure, various embodiments of the mobile terminal of the present invention are provided.
Referring to fig. 1, in a first embodiment of the mobile terminal of the present invention, the mobile terminal includes: a memory, a processor, and a card screen detection program stored on the memory and executable on the processor, the card screen detection program when executed by the processor implementing the steps of:
in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information;
and when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage partition through the linker.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
when the matching result information is matching pass, storing the graph library calling data to a preset storage area;
and when the mobile terminal is detected to be in a screen-off standby state, removing redundancy of the graph library calling data in the preset storage area, and storing the graph library calling data after redundancy removal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
monitoring the calling data of the graphic library to acquire monitoring result information when the matching result information is that the matching is not passed;
and judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
judging whether the monitoring result information contains preset information or not;
if the monitoring result information contains preset information, judging that the graphic library is abnormal;
and if the monitoring result information does not contain preset information, judging that the graphic library is not abnormal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
reading a characteristic log file from a preset storage area at regular time, and judging whether the bit number of the characteristic log file is greater than or equal to a preset bit number;
and uploading the feature log file to a preset cloud for storage when the bit number of the feature log file is greater than or equal to a preset bit number.
The specific embodiment of the mobile terminal of the present invention is substantially the same as the specific embodiments of the card screen detection method described below, and is not described herein again.
Further, the present invention also provides a card screen detection method applied to the mobile terminal shown in fig. 1, referring to fig. 3, and fig. 3 is a flowchart illustrating a first embodiment of the card screen detection method according to the present invention.
In this embodiment, the card screen detection method includes:
step S101, in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
the card screen detection method is applied to the mobile terminal shown in fig. 1, and the mobile terminal comprises a smart phone, a tablet computer and the like. In an Android system, a required graphic library is called in the starting process of the system through a Linker, and the called graphic library is analyzed and resource is distributed. The method comprises the steps of combing the starting process of the Android system, standardizing the starting process of the Android system, and dividing the starting process of the system into five stages, namely a minimum system power-on and starting stage, a kernel layer power-on and starting stage, a Native layer starting stage, a framework layer starting stage and an application layer starting stage, wherein each starting stage is divided into an inherent part and a self-defined part of a Native system. After the starting process of the system is standardized, the processes are classified according to the process creation related to the execution of each stage flow after the standardization, in the starting process of the system, data related to hardware and resources are mainly loaded and initialized, and the processes related to the starting process of the system are divided into a core process and a non-core process according to the influence of the hardware and the resources on the system after the starting process is completed. The core process comprises a Camera driver, a Binder driver, a display driver and an all-in-one device driver (Wifi, Bluetooth, GPS, radio and NFC) of a Kernel layer; a daemon of the kernel; the method comprises the following steps of starting up animation of a Native layer, a ServiceManager process, an audioFlinger thread in a multimedia process, a media playing service thread, a Camera service thread and the like.
In the system startup process, a graphics library, namely a libskia library, needs to be loaded and called, and when the loaded and called graphics library is abnormal, the system startup process of the mobile terminal cannot be continuously executed, and a screen blocking phenomenon occurs. Because the loading and calling of the graphic library, the analysis of the graphic library and the resource allocation are realized through the linker, the method deploys the monitor at the Native framework layer, runs in the form of an independent process, and adjusts the starting sequence to ensure that the process is created and run when the system enters the Native framework layer in the starting process. In addition, the invention also establishes a daemon process on the Native layer for detecting whether the monitor operated on the Native layer is abnormal or not and recovering after the abnormality occurs, specifically, the daemon process actively initiates heartbeat communication with the process where the monitor is located at regular time to judge whether the monitor normally operates or not, the heartbeat communication mainly reads the state of the process where the monitor is located through the Native layer daemon process, judges whether the monitor normally operates or not according to the read state, when the daemon process reads that the state is in a blocking state, timing is carried out, when the state is read to be in the blocking state, the process where the monitor is located is forcibly closed, and the monitor is reestablished to ensure that the monitor is always in a normal working state.
When a user presses a Power key for a long time to start the mobile terminal, the mobile terminal performs a system starting process, and at the moment, the mobile terminal calls a graphic library required by the system starting process of the mobile terminal through a linker.
Step S102, obtaining graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to obtain matching result information;
the mobile terminal calls a graphic library required by a system startup starting process of the mobile terminal through a linker, obtains graphic library calling data generated when the linker calls the graphic library, and matches the graphic library calling data with preset feature information to obtain matching result information. The matching result information comprises a matching pass and a matching fail, the graphics library calling data comprises graphics library loading information, memory allocation information of the graphics library and the like, and further comprises virtual addresses and item numbers, symbol information, relocation information, init & finit funcs data, soinfo structure body data and the like related to the dynamic section information. The preset feature information includes a failure of loading the graphics library and a memory page missing of the graphics library, and it should be noted that the preset feature information may be set by a person skilled in the art based on an actual situation, which is not specifically limited in this embodiment.
And step S103, when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file.
And when the matching result information is that the matching is passed, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file, specifically, independently creating a thread by the mobile terminal to output the current card screen fault information to a debug process, and directionally outputting the current card screen fault information to the feature log file with debug authority processing by the debug process.
Optionally, in this embodiment, after step S102, the method further includes:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage partition through the linker.
It should be noted that the present invention provides a specific solution to the card screen failure based on the foregoing embodiments, and only this is described below.
When the matching result information is that the matching is passed, the mobile terminal unloads the graph library, and calls the graph library required by the system startup starting process of the mobile terminal in the preset storage partition through the linker, namely backups the graph library required by the system startup starting process of the mobile terminal in the preset storage partition, and can call the graph library backed up in the preset storage partition when the graph library is abnormal, so that the card screen fault is rapidly solved.
In the embodiment, in the system startup process, the invention calls the graphic library required by the system startup process of the mobile terminal through the linker, acquires the graphic library calling data generated when the linker calls the graphic library, matches the graphic library calling data with the preset characteristic information to acquire the matching result information, then extracts the current card screen fault information from the graphic library calling data when the matching result information is that the matching is passed, and outputs the current card screen fault information to the characteristic log file, the scheme calls the graphic library calling data generated when the linker calls the graphic library by acquiring the graphic library calling data and matches the graphic library calling data with the preset characteristic information to acquire the matching result information, determines whether the card screen fault occurs in the mobile terminal based on the matching result information, and then when the card screen fault occurs in the mobile terminal, the current fault information in the graph library calling data is output to the characteristic log file, so that a developer can conveniently inquire the characteristic log file when detecting and positioning the card screen reason of the mobile terminal, the card screen reason can be quickly and accurately positioned, and the labor cost and the time cost are greatly reduced.
Further, referring to fig. 4, a second embodiment of the card screen detection method of the present invention is proposed based on the above first embodiment, and the difference from the foregoing embodiment is that after step S102, the card screen detection method further includes:
step S104, storing the graph library calling data to a preset storage area when the matching result information is that the matching is passed;
and step S105, when the mobile terminal is detected to be in the screen-off standby state, removing redundancy of the graph library calling data in the preset storage area, and storing the graph library calling data after the redundancy is removed.
It should be noted that the present invention provides a specific way of data redundancy elimination based on the foregoing embodiments, and only this is described below, and other embodiments can be referred to.
And when the matching result information is that the matching is passed, the mobile terminal stores the graph library calling data to a preset storage area, and when detecting that the mobile terminal is in a screen-off standby state, removes redundancy of the graph library calling data in the preset storage area and stores the graph library calling data after removing the redundancy. For example, the generation time of the image library call data in the preset storage area is all from 10 to 11 points, 1000 pieces of data are stored in total, and a card screen fault occurs in the mobile terminal during the period from 10 to 11 points, and the card screen fault type is an abnormal graphic library, the 1000 pieces of stored data are subjected to redundancy removal, that is, the 1000 pieces of data are integrated into one piece of information including the card screen type, the recorded data quantity and the time point, and the type and the time point of the 1000 pieces of information are prevented from being respectively output and stored, so that the storage space is saved.
In specific implementation, the mobile terminal can also perform redundancy removing processing on the graph library calling data in the preset storage area within preset time, wherein the preset time is reasonable redundancy removing interval time determined through experiments, and in the interval time, data needing redundancy removing cannot be too much or too little, so that too long time is spent or redundancy removing is too frequent. The redundancy removing process is to integrate the monitoring result information collected in the preset time into an information output and storage, wherein the information comprises the reason type of the card screen, the time point of occurrence and the frequency of occurrence of various types.
In another specific implementation, the storage unit in the mobile terminal is divided into a plurality of storage sections, each storage section is used for storing different data, and the capacity of each storage section is constant, that is, the amount of data that can be stored is constant. Correspondingly, the capacity of the storage interval for storing the graph library calling data is also fixed, and when the graph library calling data is stored in the storage interval within the preset time, the stored data volume is continuously increased and possibly exceeds the capacity. Therefore, after the graph library calling data is subjected to redundancy removal processing and stored, whether the size of the stored data volume exceeds the size of the preset data volume is judged, and the size of the preset data volume is the capacity of the storage area for storing the graph library calling data. When the size of the stored data amount exceeds the preset data amount, it is described that the capacity of the storage interval is used up, data storage can no longer be performed, and the stored data needs to be deleted. And selecting information to be deleted from the stored graph library calling data, and deleting the information to be deleted. The selection principle can be based on the time sequence, and the earlier the time sequence is, the longer the time of the graph library calling data is, the less the referential significance is, so that the graph library calling data is selected as the information to be deleted for deletion.
In this embodiment, when the mobile terminal is in the screen-off standby state, the redundancy removal is performed on the image library call data stored and recorded, so that the data stored and recorded can be effectively reduced, the occupation of the disk space is reduced, and the utilization rate of the disk is improved.
Further, referring to fig. 5, a third embodiment of the card screen detection method of the present invention is proposed based on the first or second embodiment, and is different from the foregoing embodiments in that after step S102, the card screen detection method further includes:
step S106, when the matching result information is that the matching is not passed, monitoring the calling data of the graphic library to obtain monitoring result information;
and S107, judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
It should be noted that the present invention provides another card screen detection method based on the foregoing embodiment, and only this will be described below, and other embodiments can be referred to.
The mobile terminal monitors the graph library call data to obtain monitoring result information when the matching result information is not passed through, judges whether the graph library is abnormal or not according to the monitoring result information, and outputs the monitoring result information to a feature log file when the graph library is abnormal, wherein the graph library call data comprises virtual addresses and item numbers, symbol information, relocation information, init & limit funcs data and soinfo structure data related to dynamic section information.
Specifically, the mobile terminal calculates the size of the occupied memory of virtual addresses and item numbers, symbol information, relocation information, init & finit funcs data, soinfo structure data and the like related to dynamic section information in the graph library calling data, compares the size with the remaining memory of the current system, and judges whether the system memory is insufficient; judging whether the virtual address and the number of items related to the dynamic section information exceed the limit allowed by the system or not, and whether address errors or addressing abnormity exist in symbolic information and relocation data related to the dynamic section information or not; and judging whether the init and finit functions data have grammatical errors or not, and judging whether the soinfo structure data have exceptions of missing pages or not finding pages of the memories when the memories are allocated or not.
Optionally, in this embodiment, the step of determining whether the graphic library is abnormal according to the monitoring result information includes:
judging whether the monitoring result information contains preset information or not;
if the monitoring result information contains preset information, judging that the graphic library is abnormal;
and if the monitoring result information does not contain preset information, judging that the graphic library is not abnormal.
After the mobile terminal acquires the monitoring result information, whether the monitoring result information contains preset information or not is judged, if the monitoring result information contains the preset information, the fact that the called graphic library is abnormal can be judged, the fact that the card screen fault occurs in the mobile terminal is judged, if the monitoring result information does not contain the preset information, the fact that the called graphic library is not abnormal can be judged, and the fact that the card screen fault does not occur in the mobile terminal is judged. The preset information comprises that the system memory is insufficient, the virtual address and the number of items exceed a preset limit value, the symbolic information or the relocation data related to the dynamic section information has address errors or abnormal addressing, the init & limit functions data has syntax errors, and the soinfo structure data has a memory allocation, and the memory pages are missing or can not be found. When the monitoring result information at least comprises one or more of card screen fault information such as insufficient system memory, virtual address and item number exceeding a preset limit value, address error or addressing abnormity of symbolic information or relocation data related to the dynamic section information, syntax error of init & finit funcs data, and missing page or no memory page found when the distributed memory of the soinfo structure data exists, the called graphic library is abnormal, and the card screen fault of the mobile terminal can be judged.
In this embodiment, when the matching result information is that the matching fails, the method and the device perform positive abnormality judgment on the graphic library, so that the card screen fault caused by the abnormality of the graphic library cannot be detected, and the detection accuracy is improved.
Further, based on the first, second or third embodiment, a fourth embodiment of the card screen detection method of the present invention is provided, which is different from the foregoing embodiment in that the card screen detection method further includes:
reading a characteristic log file from a preset storage area at regular time, and judging whether the bit number of the characteristic log file is greater than or equal to a preset bit number;
and uploading the feature log file to a preset cloud for storage when the bit number of the feature log file is greater than or equal to a preset bit number.
It should be noted that the present invention proposes a specific storage manner of the feature log file based on the foregoing embodiment, and only this will be described below, and other embodiments can be referred to.
The mobile terminal reads the characteristic log file from the preset storage area at regular time, judges whether the bit number of the characteristic log file is larger than or equal to the preset bit number or not, uploads the characteristic log file in the preset storage area to the preset cloud for storage when the bit number of the characteristic log file is larger than or equal to the preset bit number, and deletes the successfully uploaded characteristic log file from the preset storage area.
In this embodiment, the method and the device can upload the feature log file to the cloud for storage when the feature log file exceeds a certain number of bits, so as to improve the utilization rate of the disk.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a card screen detection program is stored on the computer-readable storage medium, and when executed by a processor, the card screen detection program implements the following steps:
in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information;
and when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage partition through the linker.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
when the matching result information is matching pass, storing the graph library calling data to a preset storage area;
and when the mobile terminal is detected to be in a screen-off standby state, removing redundancy of the graph library calling data in the preset storage area, and storing the graph library calling data after redundancy removal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
monitoring the calling data of the graphic library to acquire monitoring result information when the matching result information is that the matching is not passed;
and judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
judging whether the monitoring result information contains preset information or not;
if the monitoring result information contains preset information, judging that the graphic library is abnormal;
and if the monitoring result information does not contain preset information, judging that the graphic library is not abnormal.
Further, the card screen detection program, when executed by the processor, further implements the steps of:
reading a characteristic log file from a preset storage area at regular time, and judging whether the bit number of the characteristic log file is greater than or equal to a preset bit number;
and uploading the feature log file to a preset cloud for storage when the bit number of the feature log file is greater than or equal to a preset bit number.
The specific embodiment of the computer-readable storage medium of the present invention is substantially the same as the specific embodiments of the card screen detection method described above, and details thereof are not repeated herein.
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 system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a computer storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (9)

1. A card screen detection method is applied to a mobile terminal, and is characterized by comprising the following steps:
in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information;
when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file;
monitoring the calling data of the graphic library to acquire monitoring result information when the matching result information is that the matching is not passed;
and judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
2. The card screen detection method of claim 1, wherein after the step of matching the graphics library call data with preset feature information to obtain matching result information, the card screen detection method further comprises:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage area through the linker.
3. The card screen detection method of claim 1, wherein after the step of matching the graphics library call data with preset feature information to obtain matching result information, the card screen detection method further comprises:
when the matching result information is matching pass, storing the graph library calling data to a preset storage area;
and when the mobile terminal is detected to be in a screen-off standby state, removing redundancy of the graph library calling data in the preset storage area, and storing the graph library calling data after redundancy removal.
4. The card screen detection method of claim 1, wherein the step of determining whether the graphic library is abnormal according to the monitoring result information comprises:
judging whether the monitoring result information contains preset information or not;
if the monitoring result information contains preset information, judging that the graphic library is abnormal;
and if the monitoring result information does not contain preset information, judging that the graphic library is not abnormal.
5. The card screen detection method according to any one of claims 1 to 4, wherein after the step of outputting the monitoring result information to a feature log file, the card screen detection method further comprises:
reading a characteristic log file from a preset storage area at regular time, and judging whether the bit number of the characteristic log file is greater than or equal to a preset bit number;
and uploading the feature log file to a preset cloud for storage when the bit number of the feature log file is greater than or equal to a preset bit number.
6. A mobile terminal, characterized in that the mobile terminal comprises: the card screen detection device comprises a memory, a processor and a card screen detection program which is stored on the memory and can run on the processor, wherein the card screen detection program realizes the following steps when being executed by the processor:
in the system starting process, calling a graphic library required by the system starting process of the mobile terminal through a linker;
acquiring graph library calling data generated when the linker calls the graph library, and matching the graph library calling data with preset characteristic information to acquire matching result information;
when the matching result information is matching pass, extracting current card screen fault information from the graph library calling data, and outputting the current card screen fault information to a feature log file;
monitoring the calling data of the graphic library to acquire monitoring result information when the matching result information is that the matching is not passed;
and judging whether the graphic library is abnormal or not according to the monitoring result information, and outputting the monitoring result information to a feature log file when the graphic library is abnormal.
7. The mobile terminal of claim 6, wherein the card screen detection program, when executed by the processor, performs the steps of:
when the matching result information is matching pass, unloading the graphic library;
and calling a graphic library required by the system startup process of the mobile terminal in a preset storage partition through the linker.
8. The mobile terminal according to claim 6, wherein the card screen detection program implements the steps of the card screen detection method according to any one of claims 3 to 5 when executed by the processor.
9. A computer-readable storage medium, characterized in that a card-screen detection program is stored thereon, which when executed by a processor implements the steps of the card-screen detection method according to any one of claims 1 to 5.
CN201711055210.0A 2017-10-31 2017-10-31 Card screen detection method, mobile terminal and computer readable storage medium Active CN107844382B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711055210.0A CN107844382B (en) 2017-10-31 2017-10-31 Card screen detection method, mobile terminal and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711055210.0A CN107844382B (en) 2017-10-31 2017-10-31 Card screen detection method, mobile terminal and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN107844382A CN107844382A (en) 2018-03-27
CN107844382B true CN107844382B (en) 2021-03-26

Family

ID=61681795

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711055210.0A Active CN107844382B (en) 2017-10-31 2017-10-31 Card screen detection method, mobile terminal and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN107844382B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112905367A (en) * 2019-11-19 2021-06-04 上海西门子医疗器械有限公司 Equipment exception handling method and device and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8516578B1 (en) * 2010-12-22 2013-08-20 Google Inc. Vertex array access bounds checking
CN105427366A (en) * 2015-11-11 2016-03-23 广州华多网络科技有限公司 Image rendering method and image rendering system
CN106528385A (en) * 2016-10-27 2017-03-22 北京小米移动软件有限公司 System fluency monitoring method and apparatus, and terminal
CN107066383A (en) * 2017-03-15 2017-08-18 武汉斗鱼网络科技有限公司 A kind of application program smoothness degree detection method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8516578B1 (en) * 2010-12-22 2013-08-20 Google Inc. Vertex array access bounds checking
CN105427366A (en) * 2015-11-11 2016-03-23 广州华多网络科技有限公司 Image rendering method and image rendering system
CN106528385A (en) * 2016-10-27 2017-03-22 北京小米移动软件有限公司 System fluency monitoring method and apparatus, and terminal
CN107066383A (en) * 2017-03-15 2017-08-18 武汉斗鱼网络科技有限公司 A kind of application program smoothness degree detection method and device

Also Published As

Publication number Publication date
CN107844382A (en) 2018-03-27

Similar Documents

Publication Publication Date Title
CN107276789B (en) Log uploading method and device and computer readable storage medium
CN107678876B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107807861B (en) Screen freezing solution method, mobile terminal and computer readable storage medium
CN108040159B (en) Restart positioning method based on hardware drive, mobile terminal and readable storage medium
CN107590057B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107704133B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107885635B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107704363B (en) Screen freezing monitoring method, mobile terminal and computer readable storage medium
CN107766222B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107908492B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107765922B (en) Card screen detection and solution method, mobile terminal and computer readable storage medium
CN107908491B (en) Card screen detection and solution method, mobile terminal and computer readable storage medium
CN108121613B (en) Memory page-based restart positioning method, mobile terminal and readable storage medium
CN107704132B (en) Method for detecting frozen screen of terminal, terminal and computer readable storage medium
CN107704332B (en) Screen freezing solution method, mobile terminal and computer readable storage medium
CN107908478B (en) Memory cleaning method, mobile terminal and computer readable storage medium
CN108052430B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN108012031B (en) Mobile terminal restart positioning method, mobile terminal and computer readable storage medium
CN107832191B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107861827B (en) Card screen detection method, mobile terminal and computer readable storage medium
CN107872367B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107818036B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107748633B (en) Solution for terminal screen freezing, terminal and computer readable storage medium
CN108089937B (en) Direct memory allocation-based restart positioning method, mobile terminal and storage medium
CN107861826B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium

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