CN107908493B - Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium - Google Patents

Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium Download PDF

Info

Publication number
CN107908493B
CN107908493B CN201711055389.XA CN201711055389A CN107908493B CN 107908493 B CN107908493 B CN 107908493B CN 201711055389 A CN201711055389 A CN 201711055389A CN 107908493 B CN107908493 B CN 107908493B
Authority
CN
China
Prior art keywords
preset
thread
current process
created
threads
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
CN201711055389.XA
Other languages
Chinese (zh)
Other versions
CN107908493A (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 CN201711055389.XA priority Critical patent/CN107908493B/en
Publication of CN107908493A publication Critical patent/CN107908493A/en
Application granted granted Critical
Publication of CN107908493B publication Critical patent/CN107908493B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/0703—Error 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/0793—Remedial or corrective actions
    • 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/0703—Error 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/0706—Error 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/0736—Error 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/0742—Error 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5021—Priority

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

The invention discloses a method for monitoring and solving frozen screen, a mobile terminal and a computer readable storage medium, which directly acquire thread basic information of a preset thread participating in inter-process data communication from an inner core layer when the inter-process data communication is monitored, reduce intermediate logic call, quickly acquire the thread basic information, simultaneously determine that the current process does not have the creating condition of the preset thread based on the thread basic information and determine that the frozen screen occurs in the mobile terminal when the created preset threads in the current process are all in a blocking state, finally determine a frozen screen processing strategy according to the blocking duration of the created preset thread and process the created preset thread based on the frozen screen processing strategy, thereby quickly and timely solving the frozen screen problem, avoiding returning the mobile terminal to a manufacturer for maintenance, saving maintenance time and solving the problems when the frozen screen is monitored, the problem of screen freezing is solved automatically and timely, and maintenance time is saved.

Description

Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a frozen screen monitoring and solving method, a mobile terminal and a computer readable storage medium.
Background
With the development of mobile terminal technology, the hardware configuration of the mobile terminal is better and better, the functions that can be realized are more and more, and integrated APPs (applications) are more and more. At present, application programs based on different scenes of a mobile terminal are thousands of, and with the increasing quantity of third-party applications and service software installed on the mobile terminal by a user, people always encounter the problem of picture freezing when using the mobile terminal daily.
When the screen appears freezing in mobile terminal, the user restarts mobile terminal under the general condition to make it resume normal, and freeze the screen at every turn and all need the manual restart of user, user experience is not good, in addition, also can make it resume normal through restarting mobile terminal not necessarily, need return the mobile terminal to the producer maintenance, maintenance time is longer, consequently, how when monitoring freezing the screen, the screen is frozen to automatic and timely solution, it is the present problem of waiting to solve urgently to save maintenance time.
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 frozen screen monitoring and solving method, a mobile terminal and a computer readable storage medium, and aims to solve the technical problems of automatically and timely solving frozen screen and saving maintenance time when the frozen screen is monitored.
In order to achieve the above object, the present invention provides a method for monitoring and solving frozen screen, which comprises the following steps:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
Optionally, the step of determining whether the current process participating in the inter-process data communication has a condition for creating a preset thread according to the thread basic information includes:
determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information;
and judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread.
Optionally, judging whether the thread state value of each created preset thread of the current process is in a preset thread state value set;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Optionally, the step of determining whether all created preset threads of the current process are in a blocking state further includes:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Optionally, the determining a freeze-screen processing policy according to a duration interval in which a blocking duration of a created preset thread of the current process is located, and the processing the created preset thread based on the freeze-screen processing policy includes:
acquiring a first message queue of a first current process and a second message queue of a second current process for performing the inter-process data communication;
when the time interval in which the blocking time of the created preset thread of the current process is located is in the first time interval, removing the created preset thread with the longest blocking time from the first message queue and the second message queue;
and when the time intervals in which the blocking time of the created preset threads of the current process are located are both in a second time interval, removing the created preset threads with the longest blocking time from the first message queue and the second message queue respectively.
Optionally, after the step of determining whether all created preset threads of the current process are in a blocked state, the method for monitoring and solving frozen screen further includes:
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Optionally, after the step of outputting the stack call information and the thread interaction information to a feature log file, the freeze screen monitoring and solving 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: a memory, a processor, and a freeze screen monitoring and resolution program stored on the memory and executable on the processor, the freeze screen monitoring and resolution program when executed by the processor implementing the steps of:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
The present invention also provides a computer-readable storage medium having a freeze screen monitoring and resolution program stored thereon, the freeze screen monitoring and resolution program, when executed by a processor, implementing the steps of:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
The invention provides a method for monitoring and solving frozen screen, a mobile terminal and a computer readable storage medium, which can rapidly and timely solve the frozen screen problem by directly acquiring the thread basic information of a preset thread participating in the inter-process data communication from an inner core layer when the inter-process data communication is monitored, reducing intermediate logic call, rapidly acquiring the thread basic information, simultaneously judging whether the current process has the creating condition of the preset thread based on the thread basic information, performing blocking judgment on the created preset thread in the current process, then determining that the frozen screen occurs in the mobile terminal when the current process does not have the creating condition of the preset thread and the current states of the created preset thread are all in a blocking state, finally determining a frozen screen processing strategy according to the blocking duration of the created preset thread, and processing the created preset thread based on the frozen screen processing strategy, and the mobile terminal does not need to be returned to a manufacturer for maintenance, so that the maintenance time is saved, and the problems that when the screen is monitored, the screen is automatically and timely frozen and the maintenance time is saved are solved.
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 of a first embodiment of the freeze screen monitoring and resolution method of the present invention;
FIG. 4 is a schematic diagram illustrating a detailed flow of the step of determining whether all the created preset threads of the current process are in a blocking state shown in FIG. 3;
fig. 5 is a detailed flowchart illustrating the steps of determining a freeze-screen processing policy according to the time interval in which the blocking time of the created preset thread of the current process is located, and processing the created preset thread based on the freeze-screen processing policy in fig. 3;
FIG. 6 is a flow chart of a third embodiment of the freeze screen monitoring and resolution method 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 freeze screen monitoring and resolution program stored on the memory and executable on the processor, the freeze screen monitoring and resolution program when executed by the processor implementing the steps of:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information;
and judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
acquiring a first message queue of a first current process and a second message queue of a second current process for performing the inter-process data communication;
when the time interval in which the blocking time of the created preset thread of the current process is located is in the first time interval, removing the created preset thread with the longest blocking time from the first message queue and the second message queue;
and when the time intervals in which the blocking time of the created preset threads of the current process are located are both in a second time interval, removing the created preset threads with the longest blocking time from the first message queue and the second message queue respectively.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs 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 freeze screen monitoring and solving method described below, and will not be described herein again.
Further, the present invention also provides a method for monitoring and resolving frozen screen applied to the mobile terminal shown in fig. 1, referring to fig. 3, and fig. 3 is a schematic flow chart of a first embodiment of the method for monitoring and resolving frozen screen according to the present invention.
In this embodiment, the freeze screen monitoring and solving method includes:
step S101, when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
the method for monitoring and solving the frozen screen is applied to the mobile terminal shown in the figure 1, and the mobile terminal comprises a smart phone, a tablet computer and the like. Known by an operating system of the mobile terminal, data communication between different processes needs to be realized through a Binder driver of an operating system kernel space, the operating system is an Android system, and the Android system specifies that a SystemServer process can create 16 Binder threads at most for data communication between the processes; the SurfaceFlinger process can create 4 Binder threads at most for interprocess data communication; the program application process can create up to 8 Binder threads for interprocess data communication. And loading a Binder drive when the Binder thread is established and initialized, and then allocating a virtual address space to the Binder thread for receiving a transaction by adopting a memory mapping function. And each SystemServer process, the SurfaceFlinger process and the program application process only allow one Binder main thread to be created, and Binder sub-threads in the rest Binder thread pools are controlled and created by a Binder driver. The method comprises the steps that a system Server process, a SurfaceFlinger process and a Binder thread which can be created by a program application process are limited, when the creatable Binder threads are all in a blocking state, inter-process data communication cannot be carried out, so that the program application of an APP layer cannot carry out data communication with a system core process, and a frozen screen of a mobile terminal is caused.
Aiming at the problems, when monitoring the data communication between the processes, the mobile terminal reads the structure information of the preset thread participating in the data communication between the processes from a Kernel layer (Kernel layer), and acquires the thread basic information according to the structure information, wherein the preset thread is a Binder thread, the structure information comprises Binder _ thread structure information and Binder _ proc structure information, the Binder _ thread structure information comprises a process to which the Binder thread belongs, a thread PID, a transaction being processed by the Binder thread, an error code returned after failure of the Binder thread, and the like, the Binder _ proc structure information comprises a process for creating the Binder _ proc, a starting address of a mapped Kernel space, an address offset of the Kernel space and a user space, a created number of the Binder thread, a maximum created number of the Binder thread, and the like, and how many Binder threads are created according to the Binder _ thread structure information and the Binder _ proc structure information, Thread-based information such as the number of request threads that have been started, a default priority, whether a thread is waiting and whether a thread is processing a transaction.
Step S102, judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread according to the thread basic information;
after the mobile terminal acquires the thread basic information, whether the current process participating in the inter-process data communication has the creation condition of the preset thread is judged according to the thread basic information.
Specifically, the step S102 includes:
determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information;
and judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread.
The mobile terminal determines a current process participating in inter-process data communication after acquiring the thread basic information, and the created number and the maximum created number of the preset thread of the current process are obtained from the thread basic information, then judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of the preset thread, if not, judging that the current process does not have the creating condition of the preset thread, namely, the created number of the Binder thread of the current process and the maximum created number of the Binder thread are extracted from the thread basic information, and judges whether the created number of the Binder thread is less than the maximum created number of the Binder thread, if the created number of the Binder thread is less than the maximum created number of the Binder thread, it indicates that the current process can create the Binder thread, and if the created number of the Binder thread is equal to the maximum created number of the Binder thread, indicating that the current process can not create the Binder thread.
Step S103, when the current process participating in the inter-process data communication does not have the creating condition of the preset thread, namely the creating condition of the Binder thread, judging whether the created preset threads of the current process are all in a blocking state;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, the mobile terminal judges whether the created preset threads of the current process are all in a blocking state, namely judges whether the created Binder threads of the current process are all in the blocking state.
Specifically, referring to fig. 4, fig. 4 is a detailed flowchart of step S103 in fig. 3, where step S103 includes:
step S1031, determining whether the thread state value of each created preset thread of the current process is in a preset thread state value set;
step S1032, if the thread state value of each created preset thread of the current process is in a preset thread state value set, determining that the created preset threads of the current process are in a blocking state;
step S1033, if the uneven thread state value of each created preset thread of the current process is in the preset thread state value set, determining that the uneven created preset thread of the current process is in the blocking state.
The method comprises the steps that when a current process does not have a creation condition of a Binder thread, a thread state value of each created preset thread of the current process is obtained, whether the thread state value of each created preset thread is in a preset thread state value set or not is judged, if the thread state value of each created preset thread of the current process is in the preset thread state value set, the created preset threads of the current process can be judged to be in a blocking state, if the thread state value of each created preset thread of the current process is not uniform and is in the preset thread state value set, the created preset threads of the current process can be judged to be in the blocking state unevenly, and when the created preset threads of the current process are in the blocking state, screen freezing of the mobile terminal is shown. The thread state values include Blocked, Active, and Waiting Timeout, and the preset thread state value set includes Blocked, Waiting Timeout, and the like, that is, when the thread state values of each created preset thread of the current process are both Blocked or Waiting Timeout, it may be determined that all the created preset threads are in a blocking state. It should be noted that the preset thread state value set and the thread state value may be set by those skilled in the art according to practical situations, and the embodiment does not specifically limit this.
And step S104, when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
When the current process does not have the creating condition of the preset thread and the created preset threads of the current process are all in the blocking state, the mobile terminal determines a screen freezing processing strategy according to a time interval where the blocking time of the created preset threads of the current process is located, and processes the created preset threads based on the screen freezing processing strategy.
Specifically, referring to fig. 5, fig. 5 is a detailed flowchart of the step S104 in fig. 3, where the step S104 includes:
step S1041, acquiring a first message queue of a first current process and a second message queue of a second current process that perform the inter-process data communication;
step S1042, when the time length interval in which the blocking time length of the created preset thread of the current process is located is in the first time length interval, removing the created preset thread with the longest blocking time length from the first message queue and the second message queue;
step S1043, when the time length intervals in which the blocking time lengths of the created preset threads of the current process are located are both in the second time length interval, removing the created preset threads with the longest blocking time lengths from the first message queue and the second message queue, respectively.
The mobile terminal acquires a first message queue of a first current process and a second message queue of a second current process for inter-process data communication, and then removes the created preset thread with the longest blocking duration from the first message queue and the second message queue when the duration intervals of the blocking durations of the created preset threads of the current process are both in the first duration interval, namely removes the created preset threads with the longest blocking duration from the two message queues, and removes one created preset thread in total; when the time interval in which the blocking time of the created preset thread of the current process is located is in the second time interval, removing the created preset thread with the longest blocking time from the first message queue and the second message queue respectively, namely removing the created preset thread with the longest blocking time from the first message queue, simultaneously removing the created preset thread with the longest blocking time from the second message queue, and removing two created preset threads in total. In a specific implementation, when the time intervals in which the blocking durations of the created preset threads of the current process are located are all in the third time interval, the created preset thread with the longest blocking duration and the created preset line with the next longest blocking duration are removed from the first message queue, and the created preset thread with the longest blocking duration and the created preset line with the next longest blocking duration are removed from the second message queue, so that four created preset threads are removed in total. It should be noted that the first time interval may be 61 seconds to 120 seconds, the second time interval may be 121 seconds to 300 seconds, and the third time interval may be 301 seconds to 600 seconds, and besides, the first time interval, the second time interval, and the third time interval may also be set by those skilled in the art based on practical situations, which is not limited in this embodiment.
In specific implementation, after recording the blocking duration of each created preset thread, the mobile terminal judges whether the blocking duration of each created preset thread is greater than the preset blocking duration, if so, determines a freeze screen processing strategy according to a duration interval in which the blocking duration of each created preset thread is located, and processes the created preset threads based on the freeze screen processing strategy.
In this embodiment, when the inter-process data communication is monitored, the thread basic information of the preset thread participating in the inter-process data communication is directly acquired from the kernel layer, the intermediate logic call is reduced, the thread basic information is quickly acquired, meanwhile, whether the current process has the creation condition of the preset thread or not is judged based on the thread basic information, the created preset thread in the current process is subjected to blocking judgment, then, when the current process does not have the creation condition of the preset thread and the current states of the created preset thread are all in a blocking state, the frozen screen of the mobile terminal is determined, finally, the frozen screen processing strategy is determined according to the blocking duration of the created preset thread, and the created preset thread is processed based on the frozen screen processing strategy, so that the frozen screen problem is quickly and timely solved without returning the mobile terminal manufacturer for maintenance, the method saves maintenance time, and solves the problems of automatic and timely screen freezing and maintenance time saving when screen freezing is monitored.
Further, based on the mobile terminal shown in fig. 1 and the first embodiment described above, a second embodiment of the freeze screen monitoring and solving method of the present invention is proposed, which is different from the foregoing embodiment in that the step S103 further includes:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
It should be noted that, based on the foregoing embodiments, the present invention provides a specific way to determine whether a preset thread is in a blocking state.
When the current process does not have the condition of creating the preset thread, the mobile terminal judges whether the state return values acquired by each created preset thread of the current process based on the preset operation are all preset state return values, specifically, pings each created preset thread of the current process (Packet Internet Groper, Internet Packet searchers) to acquire the ping operation return value of each created preset thread of the current process and judge whether the ping operation return value of each created preset thread of the current process is the preset ping operation return value, if the ping operation return value of each created preset thread of the current process is all the preset ping operation return values, namely the state return values acquired by each created preset thread of the current process based on the preset operation are all the preset state return values, the created preset threads of the current process can be judged to be in the blocking state, if the ping operation return value of each created preset thread of the current process is not uniform to be the preset ping operation return value, that is, the state return value of each created preset thread of the current process, which is obtained based on the preset operation, is not uniform to be the preset state return value, it can be determined that the created preset thread of the current process is not uniformly in the blocking state. The ping operation return value, that is, the state return value, corresponds to the state of the created preset thread one by one, and the current state of the created preset thread can be determined according to the ping operation return value, that is, the state return value, and the states of the created preset thread include a busy state, an idle state, a suspended state, a blocked state, a timeout waiting state, and the like. The preset thread is a Binder thread.
In this embodiment, by performing ping operation on the created preset thread, the present invention can determine whether the current state of the created preset thread is in the blocking state based on the ping operation return value, and effectively improve the monitoring accuracy of the current state of the created preset thread.
Further, referring to fig. 6, based on the mobile terminal shown in fig. 1 and the first or second embodiment, a third embodiment of the freeze screen monitoring and resolving method of the present invention is proposed, which is different from the previous embodiment in that after the step S103, the freeze screen monitoring and resolving method further includes:
step S105, when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
It should be noted that the present invention proposes a specific output mode of the blocking information based on the foregoing embodiment, and only this will be described below, and other embodiments can be referred to.
The mobile terminal acquires the stack calling information, the thread interaction information and other blocking information of the current process when the created preset threads of the current process are all in a blocking state, and outputs the stack calling information, the thread interaction information and other blocking information to the feature log file.
Optionally, in this embodiment, after step S105, the 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, based on the foregoing embodiments, the present invention provides a specific uploading manner of the feature log file, 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 for processing the frozen screen can output the stack calling information and the thread interaction information to the feature log file when all the created preset threads of the current process are in the blocking state, and are convenient for reading the feature log file when the frozen screen occurs on the mobile terminal, so that the reason for the frozen screen is quickly located, and the labor cost and the time cost are greatly reduced.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a freeze-screen monitoring and resolving program is stored on the computer-readable storage medium, and when executed by a processor, the freeze-screen monitoring and resolving program implements the following steps:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information;
and judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
acquiring a first message queue of a first current process and a second message queue of a second current process for performing the inter-process data communication;
when the time interval in which the blocking time of the created preset thread of the current process is located is in the first time interval, removing the created preset thread with the longest blocking time from the first message queue and the second message queue;
and when the time intervals in which the blocking time of the created preset threads of the current process are located are both in a second time interval, removing the created preset threads with the longest blocking time from the first message queue and the second message queue respectively.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs the steps of:
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Further, the freeze screen monitoring and resolution program when executed by the processor further performs 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 embodiments of the above-mentioned freeze screen monitoring and solving method, and will not be described herein again.
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 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 (8)

1. A method for monitoring and solving frozen screens is characterized by comprising the following steps:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information, wherein the preset thread is a Binder thread;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information; the step of judging whether the current process participating in the inter-process data communication has the creation condition of the preset thread according to the thread basic information comprises the following steps: determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information; judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
2. The freeze screen monitoring and resolution method of claim 1, wherein the step of determining whether all of the created preset threads of the current process are in a blocked state comprises:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
3. The freeze screen monitoring and resolution method of claim 1, wherein the step of determining whether all of the created preset threads of the current process are in a blocked state further comprises:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
4. The freeze screen monitoring and resolution method according to claim 1, wherein the step of determining a freeze screen processing policy according to a duration interval in which a blocking duration of the created preset thread of the current process is located, and processing the created preset thread based on the freeze screen processing policy comprises:
acquiring a first message queue of a first current process and a second message queue of a second current process for performing the inter-process data communication;
when the time interval in which the blocking time of the created preset thread of the current process is located is in the first time interval, removing the created preset thread with the longest blocking time from the first message queue and the second message queue;
and when the time intervals in which the blocking time of the created preset threads of the current process are located are both in a second time interval, removing the created preset threads with the longest blocking time from the first message queue and the second message queue respectively.
5. The freeze screen monitoring and resolution method of any of claims 1-4, wherein after the step of determining whether all of the created preset threads of the current process are in a blocked state, the freeze screen monitoring and resolution method further comprises:
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
6. The freeze screen monitoring and resolution method of claim 5, wherein after the step of outputting the stack call information and the thread interaction information to a feature log file, the freeze screen monitoring and resolution 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.
7. A mobile terminal, characterized in that the mobile terminal comprises: a memory, a processor, and a freeze screen monitoring and resolution program stored on the memory and executable on the processor, the freeze screen monitoring and resolution program when executed by the processor implementing the steps of:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information, wherein the preset thread is a Binder thread;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information; the step of judging whether the current process participating in the inter-process data communication has the creation condition of the preset thread according to the thread basic information comprises the following steps: determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information; judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
8. A computer readable storage medium having a freeze screen monitoring and resolution program stored thereon, the freeze screen monitoring and resolution program when executed by a processor implementing the steps of:
when the interprocess data communication is monitored, reading structural body information of a preset thread participating in the interprocess data communication from a kernel layer, and acquiring thread basic information according to the structural body information, wherein the preset thread is a Binder thread;
judging whether the current process participating in the inter-process data communication has the creation condition of a preset thread or not according to the thread basic information; the step of judging whether the current process participating in the inter-process data communication has the creation condition of the preset thread according to the thread basic information comprises the following steps: determining a current process participating in the inter-process data communication, and acquiring the created number and the maximum created number of a preset thread of the current process from the thread basic information; judging whether the created number is smaller than the maximum created number, if so, judging that the current process has the creating condition of a preset thread, and if not, judging that the current process does not have the creating condition of the preset thread;
when the current process participating in the inter-process data communication does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are all in a blocking state;
when the created preset threads of the current process are all in a blocking state, determining a screen freezing processing strategy according to a time interval in which the blocking time of the created preset threads of the current process is located, and processing the created preset threads based on the screen freezing processing strategy.
CN201711055389.XA 2017-10-31 2017-10-31 Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium Active CN107908493B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711055389.XA CN107908493B (en) 2017-10-31 2017-10-31 Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711055389.XA CN107908493B (en) 2017-10-31 2017-10-31 Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN107908493A CN107908493A (en) 2018-04-13
CN107908493B true CN107908493B (en) 2021-05-21

Family

ID=61842381

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711055389.XA Active CN107908493B (en) 2017-10-31 2017-10-31 Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN107908493B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111061410B (en) 2018-10-16 2021-08-13 华为技术有限公司 Screen freezing processing method and terminal
CN113672454B (en) * 2021-07-30 2022-08-12 荣耀终端有限公司 Screen freezing monitoring method, electronic equipment and computer readable storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101599027A (en) * 2009-06-30 2009-12-09 中兴通讯股份有限公司 A kind of thread pool management method and system thereof
US9104860B2 (en) * 2012-05-29 2015-08-11 Appsense Limited Systems, methods and media for managing process image hijacks
CN107153583A (en) * 2017-05-24 2017-09-12 努比亚技术有限公司 A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7676675B2 (en) * 2003-06-06 2010-03-09 Microsoft Corporation Architecture for connecting a remote client to a local client desktop

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101599027A (en) * 2009-06-30 2009-12-09 中兴通讯股份有限公司 A kind of thread pool management method and system thereof
US9104860B2 (en) * 2012-05-29 2015-08-11 Appsense Limited Systems, methods and media for managing process image hijacks
CN107153583A (en) * 2017-05-24 2017-09-12 努比亚技术有限公司 A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于Android平台的移动终端设计与实现;舒俊;《中国优秀硕士学位论文全文数据库》;20140815;全文 *

Also Published As

Publication number Publication date
CN107908493A (en) 2018-04-13

Similar Documents

Publication Publication Date Title
CN107861817B (en) Thread blocking-based memory optimization method, mobile terminal and readable storage medium
CN107590057B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107678876B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107704363B (en) Screen freezing monitoring method, mobile terminal and computer readable storage medium
CN108052390B (en) Thread blocking-based memory cleaning method, mobile terminal and readable storage medium
CN107704133B (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
CN107967177B (en) Memory optimization method based on core process, mobile terminal and readable storage medium
US10474507B2 (en) Terminal application process management method and apparatus
CN108073458B (en) Memory recovery method, mobile terminal and computer-readable storage medium
CN110445924B (en) Network task execution method and terminal equipment
CN107908491B (en) Card screen detection and solution method, mobile terminal and computer readable storage medium
CN107885635B (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
CN107908492B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107908478B (en) Memory cleaning method, mobile terminal and computer readable storage medium
CN107766222B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107704332B (en) Screen freezing solution method, mobile terminal and computer readable storage medium
CN109362103A (en) A kind of data cache method and terminal device
CN107861826B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
US11418945B2 (en) Information processing method for RF device and mobile terminal
CN107818036B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107908493B (en) Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium
CN107832191B (en) Black screen detection method, mobile terminal and computer readable storage medium
CN107872367B (en) Black screen detection 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