CN107526637B - Application processing method and device, mobile terminal and storage medium - Google Patents
Application processing method and device, mobile terminal and storage medium Download PDFInfo
- Publication number
- CN107526637B CN107526637B CN201710648188.4A CN201710648188A CN107526637B CN 107526637 B CN107526637 B CN 107526637B CN 201710648188 A CN201710648188 A CN 201710648188A CN 107526637 B CN107526637 B CN 107526637B
- Authority
- CN
- China
- Prior art keywords
- cpu
- application
- application program
- blacklist
- occupancy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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/505—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 load
-
- 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/5044—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 hardware capabilities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to an application processing method, an application processing device, a mobile terminal and a storage medium. The method comprises the following steps: when monitoring that an application program is switched from a foreground to a background, acquiring an application identifier of the application program; judging whether the application identifier is recorded in a blacklist or not; and if the record exists, stopping running the application program, and recording the application identification of the application program occupying the condition that the probability of CPU abnormity is greater than the probability threshold value in the blacklist. The application processing method, the application processing device, the mobile terminal and the storage medium can effectively reduce the situation that the application running in the foreground is blocked due to the fact that resources are preempted.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an application processing method and apparatus, a mobile terminal, and a storage medium.
Background
With the rapid development of the internet, the smart mobile terminal has become the most common electronic device for many users, such as a smart phone, a tablet phone, and the like. A user may install various applications on the smart mobile terminal for use, and when the applications run in the background, some tasks consuming time or occupying a large amount of CPU (Central Processing Unit) sometimes need to be executed, and CPU resources are preempted, which results in the situation that the applications running in the foreground are stuck due to the preemption of the resources.
Disclosure of Invention
The embodiment of the application provides an application processing method and device, a mobile terminal and a storage medium, which can reduce the situation that an application running in the foreground is blocked due to the preemption of resources.
An application processing method, comprising:
when monitoring that the application program is switched from a foreground to a background, acquiring an application identifier of the application program;
judging whether the application identifier is recorded in a blacklist or not;
and if the record exists, stopping running the application program, and recording the application identification of the application program occupying the condition that the probability of CPU abnormity is greater than the probability threshold value in the blacklist.
In one embodiment, before the acquiring the application identifier of the application program when the application program is monitored to switch from the foreground to the background, the method further includes:
collecting the total occupancy rate of the CPU every other first preset time;
judging whether the CPU is in a busy state or not according to the total occupancy rate of the CPU;
if yes, acquiring the CPU occupancy rate of each running application program every second preset time;
and determining the application program with the CPU occupancy rate larger than the first preset value as the application program occupying the abnormal CPU.
In one embodiment, the determining whether the CPU is in a busy state according to the total occupancy of the CPU includes:
calculating the occupation level of the CPU according to the total occupation rate of the CPU;
accumulating the number of times of continuously maintaining at the occupancy level;
determining a busy degree corresponding to the occupancy level when the number of times reaches a count threshold corresponding to the occupancy level;
and when the busy degree is greater than a second preset value, judging that the CPU is in a busy state.
In one embodiment, after the determining that the application program with the CPU occupancy rate greater than the preset threshold is the application program with CPU exception, the method further includes:
screening the application programs occupying the abnormal CPU according to preset filtering conditions;
stopping running the screened application programs occupying the abnormal CPU, and recording the application identification of the application programs stopped to run;
acquiring recording data of preset times;
calculating the probability of the application program being stopped in the preset times according to the recorded data;
and adding the application identification of the application program with the probability of being stopped to be greater than the probability threshold value into the blacklist.
In one embodiment, the application identification of the application program which is updated or uninstalled in the blacklist is removed.
An application processing apparatus comprising:
the monitoring module is used for acquiring the application identifier of the application program when the application program is monitored to be switched from a foreground to a background;
the recording judgment module is used for judging whether the application identifier is recorded in the blacklist or not;
and the stopping module is used for stopping running the application program if the application identifier is recorded in the blacklist, and the application identifier of the application program with the probability of occupying the CPU abnormity, which is greater than the probability threshold value, is recorded in the blacklist.
In one embodiment, the apparatus further comprises:
the acquisition module is used for acquiring the total occupancy rate of the CPU every other first preset time;
the state judgment module is used for judging whether the CPU is in a busy state or not according to the total occupancy rate of the CPU;
the acquisition module is further used for acquiring the CPU occupancy rate of each running application program every second preset time if the CPU is in a busy state;
and the determining module is used for determining the application program with the CPU occupancy rate larger than the first preset value as the application program occupying the abnormal CPU.
In one embodiment, the state determining module includes:
the computing unit is used for computing the occupation level of the CPU according to the total occupation rate of the CPU;
the accumulation unit is used for accumulating the times of continuously maintaining the occupancy level;
a busy degree determining unit configured to determine a busy degree corresponding to the occupancy level when the number of times reaches a count threshold corresponding to the occupancy level;
and the state judgment unit is used for judging that the CPU is in a busy state when the busy degree is greater than a second preset value.
In one embodiment, the apparatus further comprises:
the screening module is used for screening the application programs occupying the abnormal CPU according to preset filtering conditions;
the stopping module is also used for stopping running the screened application programs occupying the abnormal CPU and recording the application identifiers of the application programs stopped to run;
and the adding module is used for acquiring recording data of preset times, calculating the probability of the application program stopping in the preset times according to the recording data, and adding the application identifier of the application program of which the probability of stopping is greater than the probability threshold value into a blacklist.
In one embodiment, the apparatus further comprises:
and the removing module is used for removing the application identification of the application program which is updated or uninstalled in the blacklist.
A mobile terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method as described above when executing the program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method as set forth above.
According to the application program processing method, the application program processing device, the mobile terminal and the storage medium, the application identification of the application program occupying the CPU anomaly probability greater than the probability threshold value is recorded in the blacklist, when the application program is monitored to be switched from the foreground to the background, the application identification of the application program is obtained, if the application identification is recorded in the blacklist, the application program is stopped running, the application program occupying the CPU anomaly and switched to the background can be stopped running in time, and the situation that the application program running in the foreground is blocked due to resource preemption is effectively reduced.
Drawings
FIG. 1 is a block diagram of a mobile terminal in one embodiment;
FIG. 2 is a flowchart illustrating a method of processing an application program according to one embodiment;
FIG. 3 is a schematic flow chart illustrating monitoring of CPU usage in one embodiment;
FIG. 4 is a schematic diagram of a process for determining whether the CPU is busy in one embodiment;
FIG. 5 is a schematic diagram of CPU occupancy level change in one embodiment;
FIG. 6 is a flowchart illustrating the process of screening applications occupying CPU exceptions to stop running in one embodiment;
FIG. 7 is a block diagram of an application processing device in one embodiment;
FIG. 8 is a block diagram of an application processing device in another embodiment;
FIG. 9 is a block diagram of a state determination module in one embodiment;
fig. 10 is a block diagram of a mobile terminal in another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad application.
It will be understood that, as used herein, the terms "first," "second," and the like may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, a first client may be referred to as a second client, and similarly, a second client may be referred to as a first client, without departing from the scope of the present application. Both the first client and the second client are clients, but they are not the same client.
Fig. 1 is a block diagram of a mobile terminal in one embodiment. As shown in fig. 1, the mobile terminal includes a processor, a non-volatile storage medium, an internal memory, a network interface, a display screen, and an input device, which are connected through a system bus. The non-volatile storage medium of the mobile terminal stores an operating system and computer-executable instructions, and the computer-executable instructions are executed by the processor to implement the application processing method provided in the embodiment of the application. The processor is used to provide computing and control capabilities to support the operation of the entire mobile terminal. The internal memory in the mobile terminal provides an environment for the execution of computer-readable instructions in the non-volatile storage medium. The network interface is used for network communication with the server. The display screen of the mobile terminal can be a liquid crystal display screen or an electronic ink display screen, and the input device can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the mobile terminal, or an external keyboard, a touch pad or a mouse. The mobile terminal can be a mobile phone, a tablet computer, a personal digital assistant or a wearable device. Those skilled in the art will appreciate that the architecture shown in fig. 1 is only a block diagram of a portion of the architecture associated with the subject application and does not constitute a limitation on the mobile terminal to which the subject application applies, and that a particular mobile terminal may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
As shown in fig. 2, in one embodiment, an application processing method is provided, which includes the following steps:
and step 210, when the application program is monitored to be switched from the foreground to the background, acquiring the application identifier of the application program.
The mobile terminal can monitor each running application program through the activity manager and monitor the state change of each running application program. And when the state change of the application program is detected, determining the type of the state change, and if the type of the state change is switched from the foreground to the background, acquiring the application identifier of the application program switched from the foreground to the background. The application identifier refers to information that can be used to uniquely identify the application, and may be, for example, a package name, a number, or the like of the application.
In one embodiment, the mobile terminal may obtain all running application lists at intervals, for example, every 5 seconds, through the RunningApp ProcessInfo class of the activity manager, and determine one by one whether the state of each running application in the application list is foreground running or background running. The current state of the application program can be compared with the previous state, and if the previous state of the application program is foreground operation and the current state is background operation, the application program can be determined to be switched from the foreground to the background. The mobile terminal can also monitor a home key (return key), and when the operating system receives a broadcast sent by clicking the home key, the operating system can determine that the application program running in the foreground is switched to the background.
In one embodiment, the mobile terminal may monitor the lifecycle of each activity, establish a global counter, count the calls of each activity to the onStart and onStop methods, add 1 to the global counter when an application calls onStart once, subtract 1 from the global counter when an application calls onStop once, indicate that the application is running in the foreground when the global counter of the application is greater than 0, indicate that the application is running in the background when the global counter of the application is equal to 0, and indicate that the application is switching from the foreground to the background when the global counter is changed from 1 to 0. In other embodiments, other ways may also be used to monitor the foreground and background switching of the application, and the method is not limited to the above-mentioned ways.
The mobile terminal reads the stored blacklist, application identifiers of the application programs occupying the CPU with the abnormal probability larger than the probability threshold value can be recorded in the blacklist, the mobile terminal can monitor the use condition of the CPU, and the CPU occupancy rate of each application program in operation is collected. Further, the CPU occupancy rate of each application program in background operation can be collected, whether the application program occupies the CPU abnormally is judged according to the CPU occupancy rate of the application program in the background operation, and when the CPU occupancy rate of the application program is larger than a first preset value, the application program can be judged to occupy the CPU abnormally. The mobile terminal can record application identifications of the application programs occupying the CPU abnormity during background operation each time, set the probability calculation base number as preset times, obtain recorded data of the preset times, record the application identifications of the application programs occupying the CPU abnormity during the background operation each time in the recorded data, calculate the probability of the application programs being recorded as occupying the CPU abnormity during the preset times according to the recorded data, and record the application identifications of the application programs with the probability larger than a probability threshold value into a blacklist. It should be understood that the preset times and the probability threshold may be set according to actual requirements, for example, the preset times are 8 times and 10 times, and the probability threshold is 70% and 75%, but not limited thereto, by setting the probability calculation base, the probability that the application is mistakenly considered to occupy the CPU anomaly may be reduced, and the accuracy of the blacklist may be improved.
At step 230, the application stops running.
When monitoring that the application program is switched from the foreground to the background, the mobile terminal can judge whether the application identifier of the application program exists in the blacklist, and if so, the mobile terminal can directly stop running the application program. Stopping running the application program may include closing or suspending the application program, wherein closing the application program refers to terminating (kill) the application program, suspending the application program refers to suspending the running of the application program, the suspended application program may be added to the wait queue, and when the CPU is idle, the running of the application program is resumed. According to the blacklist, the application program which is switched from the foreground to the background and possibly occupies CPU abnormity can be directly stopped, the CPU occupancy rate of the application program running in the background does not need to be collected at each time and then the application program stops running, the resource use of other application programs running in the foreground is guaranteed, and the blocking condition is reduced.
If the application identifier of the application program switched from the foreground to the background does not exist in the blacklist, the processing is not performed temporarily, so that the application program runs in the background, the CPU occupancy rate of the application program in the background running process is monitored, and when the CPU occupancy rate of the application program in the background running process is monitored, the application program stops running.
According to the application program processing method, the application identification of the application program with the probability of occupying the CPU anomaly larger than the probability threshold is recorded in the blacklist, when the application program is monitored to be switched from the foreground to the background, the application identification of the application program is obtained, if the application identification is recorded in the blacklist, the application program is stopped running, the application program which occupies the CPU anomaly and is switched to the background can be stopped running in time, and the situation that the application program running in the foreground is blocked due to the fact that resources are preempted is effectively reduced.
As shown in fig. 3, in an embodiment, before acquiring the application identifier of the application program when the application program is monitored to switch from the foreground to the background in step 210, the method further includes the following steps:
The mobile terminal can read the activity data of the CPU from a specific file every a first preset time, the specific file records the accumulated working time of the CPU from the start of the mobile terminal to the current moment, wherein the first preset time can be set according to actual requirements, such as 5 seconds, 7 seconds and the like, the first preset time is not too long or too short, the too long can cause inaccurate total occupancy rate of the CPU, and the too short can consume system resources. The specific file refers to a file in which activity data of the CPU is recorded, and in the file, the cumulative operating time of the CPU from the start of the mobile terminal to the current time, the cumulative time of each different process from the start of the mobile terminal to the use of the CPU at the current time, and the like are recorded.
In one embodiment, the mobile terminal may read, from the/proc/stat file under the/proc directory, the cumulative operating time of the CPU from the start of the mobile terminal to the current time every a first preset time, may record the cumulative operating time of the CPU read each time, and calculate a difference between the cumulative operating time of the CPU recorded this time and the cumulative operating time of the CPU recorded last time, to obtain the real operating time of the CPU in a first acquisition period, where the first acquisition period is the first preset time. The ratio of the real working time of the CPU in the first acquisition period to the first acquisition period can be determined, and the ratio is the total occupancy rate of the CPU.
And step 304, judging whether the CPU is in a busy state or not according to the total occupancy rate of the CPU, if so, executing step 306, and if not, executing step 302.
The mobile terminal can judge whether the CPU is in a busy state according to the collected total occupancy rate of the CPU, in one embodiment, a state value for judging the busy state can be set, when the total occupancy rate of the CPU is greater than the state value, the CPU can be judged to be in the busy state, for example, the set state value is 50%, and when the total occupancy rate of the CPU is greater than 50%, the CPU can be considered to be in the busy state currently.
And step 306, acquiring the CPU occupancy rate of each running application program every second preset time.
If the CPU is in a busy state, the mobile terminal may read CPU usage data of each running application program from a specific file every second preset time, where the second preset time may be set according to an actual requirement, and the second preset time may be a time period longer than the first preset time, for example, 1 minute, 40 seconds, and the like, and may reduce power consumption loss caused by frequently reading data of the CPU. Further, the mobile terminal may read, at every second preset time, the cumulative time that each process uses the CPU from the start of the mobile terminal to the current time from the/proc/stat file under the/proc directory, and the like, may determine the application identifier of each application program currently running, and read, in the/proc/stat file, the cumulative time that the associated process uses the CPU according to the determined application identifier. An application identifier may have one or more associated processes, and the cumulative time of use of the CPU by an application may be the sum of the cumulative time of use of the CPU by all processes associated with the application identifier for that application.
The mobile terminal can record the CPU using accumulated time of each running application program read each time, and can calculate the difference value between the recorded CPU using accumulated time and the last recorded CPU using accumulated time for each application program to obtain the real CPU using time of the corresponding application program in a second acquisition period, wherein the second acquisition period is second preset time, the ratio of the real CPU using time of the application program in the second acquisition period to the second acquisition period can be determined, and the ratio is the CPU occupancy rate of the corresponding application program.
And 308, determining the application program with the CPU occupancy rate larger than the first preset value as the application program with abnormal CPU occupancy rate.
The mobile terminal may compare the acquired CPU occupancy rate of each running application program with a first preset value, and if the CPU occupancy rate of an application program is greater than the first preset value, it may be determined that the application program occupies an application program with an abnormal CPU, where the first preset value may be set according to an actual requirement, for example, 40%, 45%, and the like.
In one embodiment, the mobile terminal may only collect the CPU occupancy rate of each application running in the background, thereby determining the application running in the background and occupying the CPU with an abnormal condition, and ensuring the fluency of the application running in the foreground.
In the embodiment, when the CPU is in a busy state, the CPU occupancy rates of the running application programs are collected, and the application program occupying the CPU with an abnormal CPU is determined, so that the system overhead caused by frequently collecting CPU data can be reduced, and the probability that the application program is mistakenly regarded as occupying the CPU with an abnormal CPU can be reduced.
As shown in fig. 4, in one embodiment, the step 304 of determining whether the CPU is in a busy state according to the total occupancy of the CPU includes the following steps:
and step 402, calculating the occupation level of the CPU according to the total occupation rate of the CPU.
The occupancy levels of the CPUs may be divided in advance, and each occupancy level may correspond to a different occupancy range, for example, the occupancy levels of 4 CPUs are divided, including L1, L2, L3 and L4, where the occupancy range corresponding to the L1 occupancy level is less than 20%, the occupancy range corresponding to the L2 occupancy level is 20% -40%, the occupancy range corresponding to the L3 occupancy level is 40% -60%, and the occupancy range corresponding to the L4 occupancy level is greater than 60%, but is not limited thereto. The mobile terminal collects the total occupancy rate of the CPU every other first preset time, can determine the occupancy rate range in which the collected total occupancy rate of the CPU falls, and obtains the occupancy level of the CPU corresponding to the falling occupancy rate range. For example, if the total occupancy rate of the collected CPUs is 18%, the occupancy level of the CPUs is L1, and if the total occupancy rate of the CPUs is 25%, the occupancy level of the CPUs is L2.
The number of times the occupancy level is continuously maintained is accumulated 404.
The mobile terminal may assign a level counter to each CPU occupancy level, and record the consecutive times that the CPU maintains at the corresponding occupancy level through the level counter, where the CPU maintains at a certain occupancy level means that the CPU is always at or above the occupancy level, for example, if the CPU occupancy level changes to L2 occupancy level, L3 occupancy level, or L2 occupancy level, the CPU may be considered to maintain at L2 occupancy level, and the consecutive times are 3.
In one embodiment, the mobile terminal collects the total occupancy rate of the CPU every first preset time, determines the occupancy level of the CPU, and may add 1 to level counters corresponding to the occupancy level and below, and zero-clear level counters of other occupancy levels. For example, if the current CPU occupancy level is L3, the level counters of L1, L2, and L3 are incremented by 1, and the level counter of L4 is cleared, and if the next CPU occupancy level is L2, the level counters of L1 and L2 are incremented by 1, and the level counters of L3 and L4 are cleared.
In one embodiment, the types of the occupancy levels may be divided, wherein the types may include an idle level and a busy level, for example, the L1 occupancy level is used as the idle level, and the L2, L3 and L4 occupancy levels are used as the busy levels, which respectively represent different busy levels. The mobile terminal collects the total occupancy rate of the CPU every other first preset time, calculates the occupancy level of the CPU, determines the corresponding type, adds 1 to the level counter corresponding to the occupancy level of the same type and below the occupancy level, and resets the level counters of other occupancy levels. For example, if the current CPU occupancy level is L1 and the CPU occupancy level belongs to the idle level, the level counter of L1 is incremented by 1, and the level counters of L2, L3, and L4 are cleared, and if the CPU occupancy level of the next time is L3 and the CPU occupancy level belongs to the busy level, the level counters of L3 and L2 that belong to the busy level are incremented by 1, and the level counters of L1 and L4 are cleared.
At step 406, when the number of times reaches a count threshold corresponding to the occupancy level, a busy level corresponding to the occupancy level is determined.
A corresponding count threshold may be set for each CPU occupancy level, and the count threshold may be used to determine whether the CPU of the mobile terminal is maintained in the operating state corresponding to the occupancy level. The mobile terminal accumulates the times of the CPU continuously maintaining at each occupation level through the level counter, and when the times of the CPU continuously maintaining at the occupation level reaches the counting threshold value corresponding to the occupation level, the mobile terminal can determine that the CPU is stable in the working state of the occupation level. For example, L1, L2, L3, and L4 are respectively set to have a corresponding count threshold value of c1, c2, c3, and c4, and when the number of times that the CPU continuously maintains the level of L1 reaches c1, the CPU is determined to be in the operating state of L1. Further, the count threshold corresponding to each occupancy level may decrease with the increase of the occupancy level, for example, the count thresholds corresponding to L1, L2, L3 and L4 are c1, c2, c3 and c4, where c1> c2> c3> c4, for example, c1 is 5 times, c2 is 4 times, c3 is 3 times, c4 is 2 times, etc., but not limited thereto. In one embodiment, if there are multiple occupation levels with the number of continuous maintenance times reaching the corresponding counting threshold, the occupation level with the highest level is selected as the stable working state of the CPU.
FIG. 5 is a diagram illustrating changes in CPU occupancy level, according to one embodiment. As shown in fig. 4, the mobile terminal collects the total occupancy rate of the CPU every 5 seconds, and determines the occupancy level of the corresponding CPU. If the first occupation level of the CPU is L1, adding 1 to the level counter of L1, and clearing the counters of other levels; if the second occupation level is L2, respectively adding 1 to the level counters of L1 and L2, and clearing the other level counters; if the third occupancy level is L3, respectively adding 1 to the level counters of L1, L2 and L3, and clearing the other level counters; if the fourth occupation level is L2, respectively adding 1 to the level counters of L1 and L2, and clearing the other level counters; the occupancy level of the fifth time is L4, and the level counters of L1, L2, L3, and L4 are incremented by 1, respectively. If the number of times that the CPU is continuously maintained at L2 reaches the corresponding count threshold 4, the CPU is considered to be stable in the operating state of L2.
And step 408, when the busy degree is greater than a second preset value, judging that the CPU is in a busy state.
Different CPU occupation levels can correspond to different busy degrees, the busy degree can be increased along with the increasing of the occupation levels, when the CPU is stabilized in a working state of a certain occupation level, the mobile terminal can determine a busy program corresponding to the occupation level, judge whether the busy degree is greater than a second preset value or not, and if the busy degree is greater than the second preset value, judge that the CPU is in the busy state. For example, the busy level of L1 may be set to less than 20%, the busy level of L2 may be set to 20% to 40%, the busy level of L3 may be set to 40% to 60%, and the busy level of L4 may be set to more than 60%, and when the busy program of the CPU is more than 20%, the CPU is considered to be in a busy state.
In an embodiment, the determination may also be directly made according to the type of the occupancy level at which the CPU is stable, and if the type of the occupancy level is a busy type, the CPU may be determined to be in a busy state, for example, the CPU may be determined to be in a busy state if the CPU is stable at any one of the occupancy levels L2, L3, and L4.
In this embodiment, the number of continuous maintenance times of the CPU at each occupancy level is accumulated, so as to determine a stable operating state of the CPU, determine whether the CPU is in a busy state by buffering and removing spikes, improve the accuracy of monitoring the state of the CPU, and avoid a state determination error caused by an occasional increase in the total occupancy rate of the CPU.
As shown in fig. 6, in an embodiment, after determining the application program with the CPU occupancy greater than the first preset value as the application program occupying CPU exception in step 308, the method further includes the following steps:
If the mobile terminal judges that the CPU is in a busy state, the CPU occupancy rates of all running application programs can be collected every second preset time, and the application programs with the CPU occupancy rates larger than the first preset value are determined as the application programs occupying abnormal CPUs. The mobile terminal may pre-establish a filtering condition to filter the monitored application programs occupying the CPU with abnormality, where the filtering condition may include an application program running in a foreground, a specific application list, an application program with a higher priority, and the like. The specific application list stores application identifiers of each protected application program, which may be application programs selected and set by the user, or may be set by the system according to actual requirements, and may include application programs such as music and instant messaging, for example.
And step 604, stopping running the screened application programs occupying the abnormal CPU, and recording the application identifiers of the application programs stopped to run.
After filtering the application program occupying abnormally according to the filtering condition, the mobile terminal can stop running the application program occupying abnormally and not meeting the filtering condition after being filtered, and record the application identification of the application program stopped running, the time of stopping running and other information.
In one embodiment, the mobile terminal may display the screened application program occupying the CPU with the abnormality on the interface, and the user determines whether to stop running the screened application program occupying the CPU with the abnormality, and stops running the selected application program according to a selection operation of the user.
And step 608, calculating the probability of stopping the operation of the application program in the preset times according to the recorded data.
The mobile terminal can take the preset times as a probability calculation base number to obtain the recorded data of the preset times, wherein the recorded data comprises application identifications of the application programs which are recorded each time and stop running and occupy the CPU abnormity, the probability of stopping running of each application program in the preset times can be calculated according to the recorded data, and the probability of stopping running of the application program in the preset times is obtained by dividing the times of stopping running of the application program in the preset times by the preset times. For example, if the application a is recorded to be stopped 2 times in 10 recorded data, the probability that the application a is stopped may be 20%.
And step 610, adding the application identifications of the application programs with the probability of being stopped to be greater than the probability threshold value into a blacklist.
The mobile terminal can add the application identifier of the application program with the probability of being stopped being greater than the probability threshold value into the blacklist, and if the probability of the application program being stopped being in the preset times is greater than the probability threshold value, it indicates that the application program often needs to occupy a large amount of CPU resources when running in the background, and the application program running in the foreground is seriously affected. The application program which often occupies a large amount of CPU resources when running in the background is added into the blacklist, so that the application program can be conveniently checked and killed in time when being switched from the foreground to the background.
In one embodiment, the probability that an application is stopped may be calculated in different ways. The mobile terminal can record the running condition of the application program every time, record the running time of the application program every time, and can add a corresponding stop tag when the application program is stopped running due to CPU occupation abnormity when the application program runs in the background. The mobile terminal can obtain operation record data of the application program for preset times, obtain the number of stop tags contained in the operation record data of the preset times, divide the number of the stop tags by the preset times, and then calculate the probability of the application program being stopped in the preset times of operation, and if the probability of being stopped is greater than the preset probability, then add the application identifier of the application program into a blacklist.
In this embodiment, the application programs occupying the CPU with abnormality can be screened according to the preset filtering condition, the application programs occupying the CPU with abnormality and not meeting the filtering condition after the screening are stopped, and the application programs with the probability of being stopped in the preset times being greater than the probability threshold value are added to the blacklist, so that the application programs can be conveniently checked and killed in time when being switched from the foreground to the background, and the situation that the application programs running in the foreground are jammed due to the preemption of resources can be effectively reduced.
In one embodiment, the application processing method further includes: and removing the application identification of the application program which is updated or uninstalled in the blacklist.
The mobile terminal can establish a corresponding blacklist removal mechanism, monitor the operations of installation, update or uninstallation and the like of the application program, judge whether the application identifier of the application program exists in the blacklist or not when the application program is monitored to be updated or uninstalled, and remove the application identifier from the blacklist if the application identifier exists in the blacklist. Further, the mobile terminal may create a receiving broadcast, monitor operations such as installation, update, or uninstallation of the application program through the receiving broadcast, obtain an operation type and an application identifier according to the receiving broadcast when the receiving broadcast is received, detect whether the application identifier is included in the blacklist if the operation type is update or uninstallation, and remove the application identifier from the blacklist if the operation type is included.
In one embodiment, if the number of times that the application program is stopped from running when the application program is switched from the foreground to the background reaches the threshold number of times, the application identifier of the application program can be removed from the blacklist, so that the accuracy and the timeliness of the blacklist are ensured.
In this embodiment, a blacklist removal mechanism is established to remove the application program whose blacklist is updated, uninstalled, etc., so as to ensure the accuracy and timeliness of the blacklist and reduce the probability of the application program being stopped by mistake.
As shown in fig. 7, in one embodiment, an application processing apparatus 700 is provided and includes a monitoring module 710, a recording determination module 720, and a stopping module 730.
The monitoring module 710 is configured to obtain an application identifier of the application program when the application program is monitored to be switched from the foreground to the background.
And the recording judgment module 720 is configured to judge whether the application identifier is recorded in the blacklist.
And a stopping module 730, configured to stop running the application program if the blacklist has the recorded application identifier, where the blacklist records the application identifier of the application program whose probability of occupying the CPU anomaly is greater than the probability threshold.
According to the application program processing device, the application identification of the application program with the probability of occupying the CPU abnormity larger than the probability threshold value is recorded in the blacklist, when the application program is monitored to be switched from the foreground to the background, the application identification of the application program is obtained, if the application identification is recorded in the blacklist, the application program is stopped running, the application program occupying the CPU abnormity can be stopped running and switched to the background in time, and the situation that the application program running in the foreground is blocked due to the fact that resources are preempted is effectively reduced.
As shown in fig. 8, in an embodiment, the application processing apparatus 700 includes a collecting module 740, a status determining module 750, and a determining module 760 in addition to the monitoring module 710, the recording determining module 720, and the stopping module 730.
The collecting module 740 is configured to collect the total occupancy rate of the CPU every first preset time.
And a state judgment module 750, configured to judge whether the CPU is in a busy state according to the total occupancy rate of the CPU.
The collecting module 740 is further configured to collect the CPU occupancy rates of the running applications every second preset time if the CPU is in a busy state.
The determining module 760 is configured to determine the application program with the CPU occupancy rate greater than the first preset value as the application program occupying the CPU exception.
In this embodiment, when the CPU is in a busy state, the CPU occupancy rates of the running application programs are collected to determine the application program occupying the CPU anomaly, so that the system overhead caused by frequently collecting CPU data can be reduced, and the probability that the application program is mistakenly considered to occupy the CPU anomaly can be reduced.
As shown in fig. 9, in one embodiment, the status determination module 750 includes a calculating unit 752, an accumulating unit 754, a busy level determining unit 756, and a status determination unit 758.
A calculating unit 752, configured to calculate an occupation level of the CPU according to the total occupation rate of the CPU.
An accumulation unit 754 for accumulating the number of times of continuously maintaining at the occupancy level.
A busy level determining unit 756 for determining a busy level corresponding to the occupancy level when the number of times reaches a count threshold corresponding to the occupancy level.
And a status determining unit 758, configured to determine that the CPU is in a busy status when the busy level is greater than the second preset value.
In the embodiment, the continuous maintaining times of the CPU at each occupation level are accumulated, so that the stable working state of the CPU is determined, whether the CPU is in a busy state is judged in a mode of buffering and removing peaks, the accuracy of monitoring the state of the CPU is improved, and the state judgment error caused by the fact that the total occupancy rate of the CPU is increased occasionally is avoided.
In one embodiment, the application processing apparatus 700 includes a filtering module and an adding module in addition to the monitoring module 710, the record determining module 720, the stopping module 730, the collecting module 740, the state determining module 750, and the determining module 760.
And the screening module is used for screening the application programs occupying the abnormal CPU according to the preset filtering conditions.
The stopping module 730 is further configured to stop running the screened application program occupying the CPU exception, and record the application identifier of the application program that is stopped to run.
And the adding module is used for acquiring the recorded data of the preset times, calculating the probability of the application program stopping in the preset times according to the recorded data, and adding the application identifier of the application program of which the probability of stopping is greater than the probability threshold value into the blacklist.
In this embodiment, the application programs occupying the CPU with abnormality can be screened according to the preset filtering condition, the application programs occupying the CPU with abnormality and not meeting the filtering condition after the screening are stopped, and the application programs with the probability of being stopped in the preset times being greater than the probability threshold value are added to the blacklist, so that the application programs can be conveniently checked and killed in time when being switched from the foreground to the background, and the situation that the application programs running in the foreground are jammed due to the preemption of resources can be effectively reduced.
In one embodiment, the application processing apparatus 700 further includes a removal module.
And the removing module is used for removing the application identification of the application program which is updated or uninstalled in the blacklist.
In this embodiment, a blacklist removal mechanism is established, and an application program that is updated and uninstalled by a blacklist is removed, so that accuracy and timeliness of the blacklist are ensured, and the probability that the application program is stopped by mistake is reduced.
The embodiment of the application also provides the mobile terminal. As shown in fig. 10, for convenience of illustration, only the portions related to the embodiments of the present application are shown, and specific technical details are not disclosed, please refer to the method portion of the embodiments of the present application. The mobile terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, a wearable device, and the like, taking the mobile terminal as the mobile phone as an example:
fig. 10 is a block diagram of a partial structure of a mobile phone related to a mobile terminal according to an embodiment of the present disclosure. Referring to fig. 10, the cellular phone includes: radio Frequency (RF) circuitry 1010, memory 1020, input unit 1030, display unit 1040, sensor 1050, audio circuitry 1060, WiFi module 1070, processor 1080, and power supply 1090. Those skilled in the art will appreciate that the handset configuration shown in fig. 10 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The RF circuit 1010 may be configured to receive and transmit signals during information transmission and reception or during a call, and may receive downlink information of a base station and then process the received downlink information to the processor 1080; the uplink data may also be transmitted to the base station. Typically, the RF circuit includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 1010 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM, General Packet Radio Service (GPRS), CDMA, Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.
The memory 1020 can be used for storing software programs and modules, and the processor 1080 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 1020. The memory 1020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function (such as an application program for a sound playing function, an application program for an image playing function, and the like), and the like; the data storage area may store data (such as audio data, an address book, etc.) created according to the use of the mobile phone, and the like. Further, the memory 1020 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 1030 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone 1000. Specifically, the input unit 1030 may include a touch panel 1032 and other input devices 1034. Touch panel 1032, which may also be referred to as a touch screen, may collect touch operations by a user (e.g., operations by a user on or near touch panel 1032 using a finger, a stylus, or any other suitable object or accessory) and drive the corresponding connection device according to a predetermined program. In one embodiment, touch panel 1032 may include two portions, 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, and sends the touch point coordinates to the processor 1080, and can receive and execute commands sent by the processor 1080. In addition, the touch panel 1032 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 1030 may include other input devices 1034 in addition to the touch panel 1032. In particular, other input devices 1034 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), and the like.
The display unit 1040 may be used to display information input by a user or information provided to the user and various menus of the cellular phone. The display unit 1040 may include a display panel 1042. In one embodiment, the Display panel 1042 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. In one embodiment, the touch panel 1032 can overlay the display panel 1042, and when the touch panel 1032 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 1080 to determine the type of the touch event, and then the processor 1080 provides a corresponding visual output on the display panel 1042 according to the type of the touch event. Although in fig. 10, the touch panel 1032 and the display panel 1042 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1032 and the display panel 1042 may be integrated to implement the input and output functions of the mobile phone.
The cell phone 1000 may also include at least one sensor 1050, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1042 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1042 and/or the backlight when the mobile phone is moved to the ear. The motion sensor can comprise an acceleration sensor, the acceleration sensor can detect the magnitude of acceleration in each direction, the magnitude and the direction of gravity can be detected when the mobile phone is static, and the motion sensor can be used for identifying the application of the gesture of the mobile phone (such as horizontal and vertical screen switching), the vibration identification related functions (such as pedometer and knocking) and the like; the mobile phone may be provided with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 1070, which provides wireless broadband internet access for the user.
The processor 1080 is a control center of the mobile phone, connects various parts of the whole mobile phone by using various interfaces and lines, and executes various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 1020 and calling data stored in the memory 1020, thereby integrally monitoring the mobile phone. In one embodiment, processor 1080 may include one or more processing units. In one embodiment, processor 1080 may integrate an application processor and a modem processor, wherein the application processor primarily handles operating systems, user interfaces, applications, and the like; the modem processor handles primarily wireless communications. It is to be appreciated that the modem processor described above may not be integrated into processor 1080.
The handset 1000 also includes a power supply 1090 (e.g., a battery) for powering the various components, and preferably, the power supply 1090 is logically coupled to the processor 1080 via a power management system that provides management of charging, discharging, and power consumption.
In one embodiment, the cell phone 1000 may also include a camera, a bluetooth module, and the like.
In the embodiment of the present application, the processor 1080 included in the mobile terminal implements the above-described application processing method when executing the computer program stored in the memory.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the above-described application processing method.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or the like.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (6)
1. An application processing method, comprising:
collecting the total occupancy rate of the CPU every other first preset time;
judging whether the CPU is in a busy state or not according to the total occupancy rate of the CPU;
if so, acquiring the CPU occupancy rate of each running application program every second preset time;
determining the application program with the CPU occupancy rate larger than a first preset value as the application program occupying the abnormal CPU;
screening the application programs occupying the abnormal CPU according to a preset filtering condition;
stopping running the screened application programs occupying the abnormal CPU, and recording the application identification of the application programs stopped to run;
acquiring recording data of preset times;
calculating the probability of stopping the operation of the application program in the preset times according to the recorded data;
adding the application identification of the application program with the probability of being stopped to be greater than the probability threshold value into a blacklist;
when monitoring that an application program is switched from a foreground to a background, acquiring an application identifier of the application program; the application identification refers to information which can be used for uniquely identifying an application program;
judging whether the application identifier is recorded in a blacklist or not;
if the record exists, stopping running the application program, and recording the application identifier of the application program of which the probability of occupying the CPU anomaly is greater than the probability threshold in the blacklist; if no record exists, temporarily not processing;
and removing the application identification of the application program which is updated or uninstalled in the blacklist.
2. The method of claim 1, wherein the determining whether the CPU is in a busy state according to the total occupancy of the CPU comprises:
calculating the occupation level of the CPU according to the total occupation rate of the CPU;
accumulating the number of times of continuously maintaining at the occupancy level;
determining a busy degree corresponding to the occupancy level when the number of times reaches a count threshold corresponding to the occupancy level;
and when the busy degree is greater than a second preset value, judging that the CPU is in a busy state.
3. An application processing apparatus, comprising:
the acquisition module is used for acquiring the total occupancy rate of the CPU every other first preset time;
the state judgment module is used for judging whether the CPU is in a busy state or not according to the total occupancy rate of the CPU;
the acquisition module is further used for acquiring the CPU occupancy rate of each running application program every second preset time if the CPU is in a busy state;
the determining module is used for determining the application program with the CPU occupancy rate larger than the first preset value as the application program occupying the abnormal CPU;
the screening module is used for screening the application programs occupying the abnormal CPU according to preset filtering conditions;
the stopping module is also used for stopping running the screened application programs occupying the abnormal CPU and recording the application identifications of the application programs stopped to run; the application identification refers to information which can be used for uniquely identifying an application program;
the adding module is used for acquiring recording data of preset times, calculating the probability of stopping the operation of the application program in the preset times according to the recording data, and adding the application identifier of the application program of which the probability of stopping the operation is greater than a probability threshold value into a blacklist;
the monitoring module is used for acquiring the application identifier of the application program when the application program is monitored to be switched from a foreground to a background;
the recording judgment module is used for judging whether the application identifier is recorded in the blacklist or not;
the stop module is used for stopping running the application program if the blacklist has the application identifier recorded therein, and the blacklist records the application identifier of the application program of which the probability of occupying the CPU anomaly is greater than the probability threshold; if no record exists, the record is not processed temporarily;
and the removing module is used for removing the application identification of the application program which is updated or uninstalled in the blacklist.
4. The apparatus of claim 3, wherein the status determining module comprises:
the computing unit is used for computing the occupation level of the CPU according to the total occupation rate of the CPU;
the accumulation unit is used for accumulating the times of continuously maintaining the occupancy level;
a busy degree determining unit configured to determine a busy degree corresponding to the occupancy level when the number of times reaches a count threshold corresponding to the occupancy level;
and the state judgment unit is used for judging that the CPU is in a busy state when the busy degree is greater than a second preset value.
5. A mobile terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor when executing the program implementing the method according to any of claims 1 to 2.
6. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1 to 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710648188.4A CN107526637B (en) | 2017-08-01 | 2017-08-01 | Application processing method and device, mobile terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710648188.4A CN107526637B (en) | 2017-08-01 | 2017-08-01 | Application processing method and device, mobile terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107526637A CN107526637A (en) | 2017-12-29 |
| CN107526637B true CN107526637B (en) | 2022-09-13 |
Family
ID=60680484
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710648188.4A Active CN107526637B (en) | 2017-08-01 | 2017-08-01 | Application processing method and device, mobile terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107526637B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111722919A (en) * | 2019-03-21 | 2020-09-29 | 北京小米移动软件有限公司 | Method and device for running background application program, storage medium and electronic equipment |
| CN110286961A (en) * | 2019-06-27 | 2019-09-27 | 深圳市网心科技有限公司 | Process based on physical host processor hangs up method and relevant device |
| CN111898117A (en) * | 2020-04-26 | 2020-11-06 | 广州视源电子科技股份有限公司 | Mutually exclusive application processing method, device, terminal and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101673216A (en) * | 2008-09-09 | 2010-03-17 | 联想(北京)有限公司 | Method and device for closing application program |
| CN102946486A (en) * | 2012-11-20 | 2013-02-27 | 惠州Tcl移动通信有限公司 | Background application automatic clearing method based on mobile phone and mobile phone |
| CN104239196A (en) * | 2014-09-17 | 2014-12-24 | 北京金山安全软件有限公司 | Method and device for detecting abnormal operation of application program and mobile terminal |
| CN105912370A (en) * | 2016-05-03 | 2016-08-31 | 广东欧珀移动通信有限公司 | Control method and apparatus for background application of mobile terminal and mobile terminal |
| CN106201683A (en) * | 2016-06-30 | 2016-12-07 | 宇龙计算机通信科技(深圳)有限公司 | A kind of manage the method for application, device and terminal |
| CN106325990A (en) * | 2016-08-19 | 2017-01-11 | 宇龙计算机通信科技(深圳)有限公司 | Control method of application program, control device and terminal |
| CN106909407A (en) * | 2015-12-23 | 2017-06-30 | 北京金山安全软件有限公司 | Background application program closing method and device and terminal |
| CN107045443A (en) * | 2017-04-14 | 2017-08-15 | 北京安云世纪科技有限公司 | background process control method, device and intelligent terminal |
-
2017
- 2017-08-01 CN CN201710648188.4A patent/CN107526637B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101673216A (en) * | 2008-09-09 | 2010-03-17 | 联想(北京)有限公司 | Method and device for closing application program |
| CN102946486A (en) * | 2012-11-20 | 2013-02-27 | 惠州Tcl移动通信有限公司 | Background application automatic clearing method based on mobile phone and mobile phone |
| CN104239196A (en) * | 2014-09-17 | 2014-12-24 | 北京金山安全软件有限公司 | Method and device for detecting abnormal operation of application program and mobile terminal |
| CN106909407A (en) * | 2015-12-23 | 2017-06-30 | 北京金山安全软件有限公司 | Background application program closing method and device and terminal |
| CN105912370A (en) * | 2016-05-03 | 2016-08-31 | 广东欧珀移动通信有限公司 | Control method and apparatus for background application of mobile terminal and mobile terminal |
| CN106201683A (en) * | 2016-06-30 | 2016-12-07 | 宇龙计算机通信科技(深圳)有限公司 | A kind of manage the method for application, device and terminal |
| CN106325990A (en) * | 2016-08-19 | 2017-01-11 | 宇龙计算机通信科技(深圳)有限公司 | Control method of application program, control device and terminal |
| CN107045443A (en) * | 2017-04-14 | 2017-08-15 | 北京安云世纪科技有限公司 | background process control method, device and intelligent terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107526637A (en) | 2017-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11099900B2 (en) | Memory reclamation method and apparatus | |
| CN107368400B (en) | CPU monitoring method and device, computer readable storage medium and mobile terminal | |
| CN107526640B (en) | Resource management method, resource management device, mobile terminal and computer-readable storage medium | |
| CN106293445B (en) | Method and device for acquiring application program use data and terminal equipment | |
| CN107391259B (en) | Resource processing method and device, computer readable storage medium and mobile terminal | |
| CN107526638B (en) | Application processing method and device, mobile terminal and storage medium | |
| AU2022200464B2 (en) | Method for reducing power consumption of terminal, and terminal | |
| CN103024205B (en) | Method, device and terminal for controlling power | |
| CN107577508B (en) | Application processing method and device, readable storage medium and mobile terminal | |
| CN108235308B (en) | Data reporting method and device, mobile terminal and computer readable medium | |
| CN107562539B (en) | Application program processing method and device, computer equipment and storage medium | |
| CN108334345B (en) | Application processing method and device, readable storage medium and mobile terminal | |
| CN108681498B (en) | CPU occupancy rate monitoring method and device and mobile terminal | |
| EP3506114B1 (en) | Memory processing method and device and storage medium | |
| CN107526637B (en) | Application processing method and device, mobile terminal and storage medium | |
| CN112703714A (en) | Application program processing method and device, computer equipment and computer readable storage medium | |
| CN105740715A (en) | Safety assessment method and terminal equipment | |
| JP7272694B2 (en) | Method and terminal for reducing power consumption of terminal | |
| CN108200546B (en) | Data reporting method and device, mobile terminal and computer readable medium | |
| CN106454953B (en) | Flow control method, device and terminal | |
| CN112612552A (en) | Application program resource loading method and device, electronic equipment and readable storage medium | |
| CN111966425A (en) | Process cleaning method and device, storage medium and mobile terminal | |
| CN107688498B (en) | Application program processing method and device, computer equipment and storage medium | |
| CN107526668B (en) | CPU monitoring method and device, computer equipment and computer readable storage medium | |
| CN107704316A (en) | Applied program processing method, device, mobile terminal and 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 | ||
| CB02 | Change of applicant information |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |