CN107844342B - Control method and device for keeping application program alive, storage medium and mobile terminal - Google Patents
Control method and device for keeping application program alive, storage medium and mobile terminal Download PDFInfo
- Publication number
- CN107844342B CN107844342B CN201711168305.3A CN201711168305A CN107844342B CN 107844342 B CN107844342 B CN 107844342B CN 201711168305 A CN201711168305 A CN 201711168305A CN 107844342 B CN107844342 B CN 107844342B
- Authority
- CN
- China
- Prior art keywords
- application program
- foreground service
- application
- foreground
- setting
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44594—Unloading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/32—Means for saving power
- G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
- G06F1/3234—Power saving characterised by the action undertaken
- G06F1/329—Power saving characterised by the action undertaken by task scheduling
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The embodiment of the application discloses a control method and a control device for keeping application program alive, a storage medium and a mobile terminal, wherein the method comprises the following steps: acquiring application information of an application program requesting to set foreground service; judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy; and if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service. According to the technical scheme, the keep-alive operation of the management and control application program can be reasonable, the rogue application program is prevented from being kept alive through setting of the foreground service, running resources and electric quantity of the mobile terminal are wasted, and the running smoothness of the mobile terminal is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of application management and control, in particular to a method and a device for managing and controlling keep-alive of an application program, a storage medium and a mobile terminal.
Background
The types and the realizable functions of the application programs in the mobile terminals such as the mobile phone are more and more, convenience is provided for the life and work of people, and people can make and receive calls, listen to music, watch videos, play games and the like by using the mobile phone. But some rogue applications can run all the time in order to keep themselves running, and self-start or keep running state through some keep-alive modes. In the related art, the control method for keeping the application program alive has the defect and needs to be improved.
Disclosure of Invention
The embodiment of the application provides a control method and device for keeping alive of an application program, a storage medium and a mobile terminal, and the keeping alive of the application program can be reasonably controlled.
In a first aspect, an embodiment of the present application provides a method for managing and controlling application keep-alive, including:
acquiring application information of an application program requesting to set foreground service;
judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy;
and if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service.
In a second aspect, an embodiment of the present application provides an application keep-alive management and control device, including:
the application information acquisition module is used for acquiring the application information of the application program requesting to set the foreground service;
a foreground service setting judgment module, configured to judge whether the application program can set a foreground service based on the application information according to a preset foreground service setting policy;
and the foreground service setting prohibition module is used for prohibiting the application program from setting foreground service if the application program cannot set the foreground service so as to prohibit the application program from starting by setting the foreground service.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for managing application keep-alive as provided in the first aspect.
In a fourth aspect, an embodiment of the present application provides a mobile terminal, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing, implements the application keep-alive management and control method as provided in the first aspect.
According to the embodiment of the application, the application information of the application requesting to set the foreground service is acquired, the application information is set according to the preset foreground service setting strategy, whether the application can set the foreground service is judged, if the judgment result is not, the application is prohibited from setting the foreground service, so that the application is prevented from being kept alive through setting the foreground service, the keep-alive operation of the application can be reasonably controlled, the situation that the mobile terminal wastes the running resources and the electric quantity due to the fact that some rogue applications keep-alive is avoided, and the running smoothness of the mobile terminal is also improved.
Drawings
Fig. 1 is a flowchart of a method for managing and controlling application keep-alive according to an embodiment of the present application;
FIG. 2 is a flowchart of another method for managing application keep-alive according to an embodiment of the present disclosure;
FIG. 3 is a flowchart of another method for managing application keep-alive according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a management and control device for keeping alive an application program according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of another mobile terminal according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, specific embodiments of the present application will be described in detail with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some but not all of the relevant portions of the present application are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Fig. 1 is a flowchart of a method for managing application keep-alive according to an embodiment of the present application, where the method of the present embodiment may be performed by an application keep-alive management device, which may be implemented by hardware and/or software, and the device may be disposed inside a mobile terminal as a part of the mobile terminal. The mobile terminal in the implementation of the application comprises a mobile phone, a tablet computer or a notebook computer and other devices.
As shown in fig. 1, the method for managing and controlling keep-alive of an application program provided in this embodiment includes the following steps:
service is an un-visualized background running logic, which is used to provide background running services for applications, and may be referred to as services, such as background music playing services. service runs almost always in the background, and it has been a tedious task to do silently. However, the system priority of the service is still relatively low, and when the system has a memory shortage condition, the service running in the background may be recovered. If it is expected that a Service can always keep a running state and cannot be recycled due to insufficient system memory, the use of foreground Service can be considered, the system can consider that the Service is visible to a user, and will not kill the Service when the memory is insufficient or the foreground Service and the common Service corresponding to the Service are the most different in that the Service always has a running icon displayed in a status bar of the system, and more detailed information can be seen after the status bar is pulled down, which is very similar to the effect of notification. The mode of setting the foreground service keep-alive application program can be utilized by some rogue application programs, after a certain service of the application program is set as the foreground service through setting the notification, the user actively clears the notification to make the user unable to perceive, but the system cannot clear the notification because of the foreground service, so that the process of the application program is kept resident, and the keep-alive of the application program is realized. The keep-alive of the application program may be that the application program is started by setting a foreground service after being closed, or that a certain service is set as the foreground service in the running process of the application program and is kept to run in a resident mode, which is not limited in the embodiment of the present application.
The technical scheme provided by the embodiment can be applied to the application scene that the application program keeps alive by setting the foreground service. When detecting that the event of the application program requesting to set the foreground service is triggered, acquiring the application information of the application program requesting to set the foreground service.
Wherein the detecting that the event requesting the setting of the foreground service is triggered may include: detecting that an event calling a set function for setting a foreground service is triggered, the set function may be a startForeground function.
The application information may include application attribute information and/or application setting information and/or application running information of the application, and the like. The application attribute information may include: user Identifier (UID), application package name, Process Identifier (PID), and the like. The application setting information may include: whether the application is set as a member in a white list or not, whether a self-starting switch of the application is set to be started or not, whether the application is set as a common application of a user or not, and the like. The application execution information may include: the application may be running condition information such as the use frequency, running priority, or application type of the application, or feedback information of a user during the running process of the application, or whether the application has a corresponding foreground interface during the running process and/or the number of times of setting foreground service during the running process, etc. The feedback information of the user may comprise that the user manually closes the application.
And 102, judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy, if so, executing a step 103, and otherwise, executing a step 104.
And judging whether the application program can set foreground service or not based on the application attribute information and/or the application setting information and/or the application running information according to a preset foreground service setting strategy. If the judgment result indicates that the application program can set the foreground service, the operation of setting the foreground service for the application program can be controlled to be executed, if the judgment result indicates that the application program can not set the foreground service, the operation of setting the foreground service for the application program is forbidden, and if the judgment result indicates that the application program can not set the foreground service, the operation of setting the foreground service for the application program is forbidden.
And 103, prohibiting the application program from setting a foreground service so as to prohibit the application program from keeping alive through setting the foreground service.
The implementation manner of prohibiting the application from setting the foreground service may be to prohibit the setting function from being called to set the foreground service, or prohibit the execution of the operation of eliminating the notification, so that the user knows that such an application has set the foreground service, and can select whether to close the application by the user. After the application program is determined to be a rogue application according to the step 102, the application is prohibited from setting the foreground service, so that the application program is prohibited from being kept alive by setting the foreground service.
And step 104, controlling and executing the operation of setting the foreground service for the application program.
In some embodiments, the following steps may also be included: and storing the application package name of the application program as an interception record, and displaying the interception record to a user.
In some embodiments, the following steps may also be included: and if the application program is the application built in the system, allowing the application program to set foreground service.
In some embodiments, the following steps may also be included: and locally acquiring the preset foreground setting strategy from a server or a mobile terminal.
In some embodiments, before determining whether the application program can set the foreground service based on the application information according to a preset foreground service setting policy, the method may further include the following steps: judging whether a target service requested to be set as a foreground service by the application program meets a second set condition, if so, determining that the target service can be set as the foreground service by the application program; if not, judging whether the application program can set foreground service or determining that the application program can not set the target service as the foreground service according to a preset foreground service setting strategy based on the application information. The second set condition may be that the service name of the target service is in a preset service white list, or that the service type of the target service is a set service type, such as a payment service type.
According to the method provided by the embodiment, whether the application program can set the foreground service is judged by acquiring the application information of the application program requesting to set the foreground service and based on the application information according to the preset foreground service setting strategy, if the judgment result is that the application program can not set the foreground service, the application is prohibited from setting the foreground service, so that the application program is prevented from being kept alive by setting the foreground service, the keep-alive operation of the application program can be reasonably controlled, the phenomenon that running resources, electric quantity and flow of the mobile terminal are wasted due to the keep-alive of some rogue applications is avoided, and the running smoothness of the mobile terminal is improved.
Fig. 2 is a flowchart of another method for managing and controlling application keep-alive according to an embodiment of the present application, and as shown in fig. 2, the method provided in this embodiment includes the following steps:
In some embodiments, this step 202 may include: if the application program is in a set white list, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service; or if the self-starting switch of the application program is turned on, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service. If the application program is in the set white list and indicates that the application program is normal application, determining that the application program can set the foreground service, otherwise, determining that the application program cannot set the foreground service if the application program indicates that the application program is rogue application; if the self-starting switch of the application program is turned on, the application program is a normal application which can be self-started and can be timely kept alive, the application program can be determined to be capable of setting the foreground service, and otherwise, the application program is determined to be a rogue application, and the application program cannot be set with the foreground service. In which user-used or comparison-based applications may be placed in a white list, e.g., WeChat applications are placed in a white list, while gaming applications are not placed in a white list.
Optionally, the method further comprises the following steps: and locally acquiring the preset white list from a server or a mobile terminal. Further, the preset white list may be updated in real time, for example, when an update instruction of a user is received, the preset white list is updated, or when a target application meeting an update condition is detected, the target application is added to the preset white list, where the update condition may include that the target application is added to the preset white list when the number of times of starting by the user reaches a set starting number, or is deleted from the preset white list when the number of times of self-starting is greater than the set starting number.
Optionally, after determining that the application may set a foreground service, the method may further include: judging whether the system sends out a corresponding notice after the application program sets foreground service; if not, the application program is listed in a blacklist, and the application program is not allowed to set foreground service subsequently. Typically, if an application shows a corresponding notification in the status bar after setting up the foreground service, if the system does not issue a notification, it is said that the rogue application clears the notification in order to not let the user know that it is running surreptitiously, and the application can be added to the blacklist.
And 203, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service.
And step 204, controlling and executing the operation of setting the foreground service for the application program.
According to the method provided by the embodiment, whether the application program can set the foreground service is judged by acquiring the application information of the application program requesting to set the foreground service and based on the application setting information of the application program according to the first preset foreground service setting strategy, if the judgment result is that the application program can not set the foreground service, the application is prohibited from setting the foreground service so as to prevent the application program from keeping alive by setting the foreground service, the keep-alive operation of the application program can be reasonably controlled, the phenomenon that running resources, electric quantity and flow of the mobile terminal are wasted due to the keep-alive of some rogue applications is avoided, and the running smoothness of the mobile terminal is also improved.
Fig. 3 is a flowchart of another method for managing and controlling application keep-alive according to an embodiment of the present application, and as shown in fig. 3, the method provided in this embodiment includes the following steps:
In some embodiments, this step 302 may include: if the set attribute of the application program meets a first set condition, determining that the application program can set foreground service, otherwise, determining that the application program can not set foreground service, wherein the set attribute comprises at least one of use frequency, operation priority and type; or if the application program is the application program without the foreground interface and the number of times of setting the foreground service is greater than the set number of times, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service. The first setting condition may include that the usage frequency is greater than the setting frequency, the operation priority is greater than the setting priority, and the application type is at least one of the setting types. When the use frequency is greater than the set frequency, the application program is an application frequently used by the user and is a normal application. Illustratively, the setting type may be a calendar, a shooting type, or the like.
Optionally, after determining that the application can set a foreground service, the method further includes: judging whether a system sends out a notification after the application program sets foreground service; if not, the application program is listed in a blacklist, and the application program is not allowed to set foreground service subsequently.
And 303, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service.
And step 304, controlling to execute the operation of setting the foreground service for the application program.
According to the method provided by the embodiment, whether the application program can set the foreground service is judged by acquiring the application information of the application program requesting to set the foreground service and based on the application running information of the application program according to the second preset foreground service setting strategy, if the judgment result is that the application program can not set the foreground service, the application is prohibited from setting the foreground service so as to prevent the application program from keeping alive by setting the foreground service, the keep-alive operation of the application program can be reasonably controlled, the running resource, the electric quantity and the flow of the mobile terminal are prevented from being wasted due to the keep-alive of some rogue applications, and the running smoothness of the mobile terminal is also improved.
Fig. 4 is a schematic structural diagram of a control device for keeping alive an application program according to an embodiment of the present disclosure, where the control device can be implemented by software and/or hardware and is integrated in a mobile terminal. As shown in fig. 4, the apparatus includes an application information acquisition module 41, a foreground service setting judgment module 42, and a foreground service setting prohibition module 43.
The application information obtaining module 41 is configured to obtain application information of an application requesting to set a foreground service;
the foreground service setting judgment module 42 is configured to judge whether the application program can set a foreground service based on the application information according to a preset foreground service setting policy;
the foreground service setting prohibition module 43 is configured to prohibit the application from setting the foreground service if the application cannot set the foreground service, so as to prohibit the application from starting by setting the foreground service.
According to the control device for keeping alive of the application program, whether the application program can be provided with the foreground service is judged by acquiring the application information of the application program requesting to set the foreground service and based on the application information according to the preset foreground service setting strategy, if the judgment result is that the application program cannot be set with the foreground service, the application program is prohibited from being provided with the foreground service, so that the application program is prevented from being kept alive by setting the foreground service, the keep-alive operation of the application program can be reasonably controlled, the phenomenon that running resources and electric quantity of the mobile terminal are wasted due to the fact that some rogue application keep-alive is avoided, and the running smoothness of the mobile terminal is improved.
Optionally, the foreground service setting determining module includes:
and the first foreground service setting judgment unit is used for judging whether the application program can set foreground service or not based on the application setting information of the application program according to a first preset foreground service setting strategy.
Optionally, the foreground service setting determining module includes:
and the second foreground service setting judgment unit is used for judging whether the application program can set foreground service or not based on the application running information of the application program according to a second preset foreground service setting strategy.
Optionally, the first foreground service setting judgment unit is specifically configured to:
if the application program is in a set white list, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service; alternatively, the first and second electrodes may be,
and if the self-starting switch of the application program is turned on, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service.
Optionally, the second foreground service setting determining unit is specifically configured to:
if the set attribute of the application program meets a first set condition, determining that the application program can set foreground service, otherwise, determining that the application program can not set foreground service, wherein the set attribute comprises at least one of use frequency, operation priority and type; alternatively, the first and second electrodes may be,
and if the application program is the application program without the foreground interface and the frequency of setting the foreground service is greater than the set frequency, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service.
Optionally, the apparatus may further include:
the preset foreground setting strategy acquisition module is used for locally acquiring the preset foreground setting strategy from a server or a mobile terminal; and/or the presence of a gas in the gas,
and the preset white list acquisition module is used for locally acquiring the preset white list from a server or a mobile terminal.
Optionally, the apparatus may further include:
the notification sending judging module is used for judging whether the system sends a notification after the application program sets the foreground service after determining that the application program can set the foreground service;
and the blacklist adding module is used for listing the application program in a blacklist if no notice is sent, and subsequently, the application program is not allowed to set foreground service.
Optionally, the apparatus further comprises:
and the foreground service setting module is used for judging whether the target service which is requested to be set as the foreground service by the application program meets a second set condition, and if so, determining that the target service can be set as the foreground service by the application program.
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a method for managing application keep-alive, the method including:
acquiring application information of an application program requesting to set foreground service;
judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy;
and if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service.
Storage medium-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Lanbas (Rambus) RAM, etc.; non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network (such as the internet). The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems that are connected by a network. The storage medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.
Of course, the storage medium containing the computer-executable instructions provided in the embodiments of the present application is not limited to the foregoing control operation of keeping alive the application program, and may also perform related operations in the control method of keeping alive the application program provided in any embodiment of the present application.
The embodiment of the application provides a mobile terminal, and a control device for keeping application program alive, which is provided by the embodiment of the application, can be integrated in the mobile terminal. Fig. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application. The mobile terminal 500 may include: the application keep-alive management and control method comprises a memory 501, a processor 502 and a computer program stored on the memory 501 and capable of being run by the processor 502, wherein the processor 502 executes the computer program to realize the application keep-alive management and control method according to the embodiment of the application.
The mobile terminal provided by the embodiment of the application can reasonably manage the keep-alive operation of the application, prevents rogue application from keeping alive by setting the foreground service, wastes running resources and electric quantity of the mobile terminal, and improves the running smoothness of the mobile terminal.
Fig. 6 is a schematic structural diagram of another mobile terminal provided in the embodiment of the present application, and as shown in fig. 6, the mobile terminal may include: a memory 601, a Central Processing Unit (CPU) 602 (also called a processor, hereinafter referred to as CPU), and the memory 601, configured to store executable program codes; the processor 602 executes a program corresponding to the executable program code by reading the executable program code stored in the memory 601, for performing: acquiring application information of an application program requesting to set foreground service; judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy; and if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service.
The mobile terminal further includes: peripheral interfaces 603, RF (Radio Frequency) circuitry 605, audio circuitry 606, speakers 611, power management chip 608, input/output (I/O) subsystem 609, touch screen 612, other input/control devices 610, and external ports 604, which communicate via one or more communication buses or signal lines 607.
It should be understood that the illustrated mobile terminal 600 is merely one example of a mobile terminal and that the mobile terminal 600 may have more or fewer components than shown, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
The following describes in detail a mobile terminal for managing application keep-alive provided in this embodiment, where the mobile terminal is a mobile phone as an example.
A memory 601, the memory 601 being accessible by the CPU602, the peripheral interface 603, and the like, the memory 601 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices.
A peripheral interface 603, said peripheral interface 603 may connect input and output peripherals of the device to the CPU502 and the memory 601.
An I/O subsystem 609, the I/O subsystem 609 may connect input and output peripherals on the device, such as a touch screen 612 and other input/control devices 610, to the peripheral interface 603. The I/O subsystem 609 may include a display controller 6091 and one or more input controllers 6092 for controlling other input/control devices 610. Where one or more input controllers 6092 receive electrical signals from or transmit electrical signals to other input/control devices 610, the other input/control devices 610 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels. It is noted that the input controller 6092 may be connected to any one of: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.
A touch screen 612, which touch screen 612 is an input interface and an output interface between the user terminal and the user, displays visual output to the user, which may include graphics, text, icons, video, and the like.
The display controller 6091 in the I/O subsystem 609 receives electrical signals from the touch screen 612 or transmits electrical signals to the touch screen 612. The touch screen 612 detects a contact on the touch screen, and the display controller 6091 converts the detected contact into an interaction with a user interface object displayed on the touch screen 612, that is, to implement a human-computer interaction, where the user interface object displayed on the touch screen 612 may be an icon for running a game, an icon networked to a corresponding network, or the like. It is worth mentioning that the device may also comprise a light mouse, which is a touch sensitive surface that does not show visual output, or an extension of the touch sensitive surface formed by the touch screen.
The RF circuit 605 is mainly used to establish communication between the mobile phone and the wireless network (i.e., network side), and implement data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving short messages, e-mails, etc. In particular, RF circuitry 605 receives and transmits RF signals, also referred to as electromagnetic signals, through which RF circuitry 605 converts electrical signals to or from electromagnetic signals and communicates with a communication network and other devices. RF circuitry 605 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC (CODEC) chipset, a Subscriber Identity Module (SIM), and so forth.
The audio circuit 606 is mainly used to receive audio data from the peripheral interface 603, convert the audio data into an electric signal, and transmit the electric signal to the speaker 611.
The speaker 611 is used to convert the voice signal received by the handset from the wireless network through the RF circuit 605 into sound and play the sound to the user.
And a power management chip 608 for supplying power and managing power to the hardware connected to the CPU602, the I/O subsystem, and the peripheral interface 603.
The control device, the storage medium, and the mobile terminal for keeping alive of the application program provided in the above embodiments may execute the control method for keeping alive of the application program provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. Technical details that are not described in detail in the above embodiments may be referred to a method for managing application keep-alive provided in any embodiment of the present application.
The foregoing is considered as illustrative of the preferred embodiments of the invention and the technical principles employed. The present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the claims.
Claims (11)
1. A control method for keeping alive of an application program is characterized by comprising the following steps:
acquiring application information of an application program requesting to set foreground service;
judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy;
if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service;
the determining whether the application program can set foreground service based on the application information according to the preset foreground service setting policy includes:
and if the application program is the application program without the foreground interface and the frequency of setting the foreground service is greater than the set frequency, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service.
2. The method of claim 1, wherein the determining whether the application program can set the foreground service based on the application information according to the preset foreground service setting policy comprises:
and judging whether the application program can set foreground service or not based on the application setting information of the application program according to a first preset foreground service setting strategy.
3. The method of claim 1, wherein the determining whether the application program can set the foreground service based on the application information according to the preset foreground service setting policy comprises:
and judging whether the application program can set foreground service or not based on the application running information of the application program according to a second preset foreground service setting strategy.
4. The method of claim 2, wherein the determining whether the application can set the foreground service based on the application setting information of the application according to the first preset foreground service setting policy comprises:
if the application program is in a set white list, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service; alternatively, the first and second electrodes may be,
and if the self-starting switch of the application program is turned on, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service.
5. The method according to claim 3, wherein the determining whether the application program can set the foreground service based on the application running information of the application program according to the second preset foreground service setting policy comprises:
if the set attribute of the application program meets a first set condition, determining that the application program can set foreground service, otherwise, determining that the application program can not set foreground service, wherein the set attribute comprises at least one of use frequency, operation priority and type.
6. The method of claim 4, further comprising:
locally acquiring the preset foreground setting strategy from a server or a mobile terminal; and/or the presence of a gas in the gas,
and locally acquiring the set white list from a server or a mobile terminal.
7. The method of claim 4 or 5, after determining that the application can set a foreground service, further comprising:
judging whether the system sends out a corresponding notice after the application program sets foreground service;
if not, the application program is listed in a blacklist, and the application program is not allowed to set foreground service subsequently.
8. The method of claim 1, further comprising:
and judging whether the target service set as foreground service requested by the application program meets a second set condition, and if so, determining that the target service can be set as foreground service by the application program.
9. The utility model provides a management and control device of application keep-alive which characterized in that includes:
the application information acquisition module is used for acquiring the application information of the application program requesting to set the foreground service;
a foreground service setting judgment module, configured to judge whether the application program can set a foreground service based on the application information according to a preset foreground service setting policy;
a foreground service setting prohibition module, configured to prohibit the application from setting a foreground service if the application cannot set the foreground service, so as to prohibit the application from starting by setting the foreground service;
the foreground service setting judgment module comprises: a second foreground service setting judgment unit;
the second foreground service setting judgment unit is specifically configured to: and if the application program is the application program without the foreground interface and the frequency of setting the foreground service is greater than the set frequency, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service.
10. A computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a method of governing application bootstrapping according to any one of claims 1-8.
11. A mobile terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for managing application self-launching as claimed in any one of claims 1 to 8 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711168305.3A CN107844342B (en) | 2017-11-21 | 2017-11-21 | Control method and device for keeping application program alive, storage medium and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711168305.3A CN107844342B (en) | 2017-11-21 | 2017-11-21 | Control method and device for keeping application program alive, storage medium and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107844342A CN107844342A (en) | 2018-03-27 |
| CN107844342B true CN107844342B (en) | 2021-07-09 |
Family
ID=61679930
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711168305.3A Active CN107844342B (en) | 2017-11-21 | 2017-11-21 | Control method and device for keeping application program alive, storage medium and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107844342B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756888B (en) * | 2019-01-03 | 2021-07-06 | 中国—东盟信息港股份有限公司 | eSIM service keep-alive system for terminals of different brands |
| CN111782347A (en) * | 2019-04-03 | 2020-10-16 | 安克创新科技股份有限公司 | Mobile phone application keep-alive method, device and system and storage medium |
| CN112416380B (en) * | 2019-08-21 | 2024-03-29 | 成都鼎桥通信技术有限公司 | Method and device for killing and freezing prevention by application |
| CN112445539A (en) * | 2019-09-02 | 2021-03-05 | 珠海市魅族科技有限公司 | Method, device, electronic equipment and storage medium for identifying disguised music playing |
| CN112835656A (en) * | 2019-11-01 | 2021-05-25 | 科美诊断技术股份有限公司 | Client starting method and device |
| CN114168212A (en) * | 2020-09-09 | 2022-03-11 | 成都鼎桥通信技术有限公司 | Application processing method, device, equipment and computer readable storage medium |
| CN112307465A (en) * | 2020-10-30 | 2021-02-02 | 上海中通吉网络技术有限公司 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
| CN112988282B (en) * | 2021-04-27 | 2021-08-20 | 荣耀终端有限公司 | Application keep-alive method and terminal equipment |
| CN113407348B (en) * | 2021-07-07 | 2024-04-09 | Tcl通讯（宁波）有限公司 | Application process management method, device, equipment and storage medium |
| CN117076089B (en) * | 2023-10-07 | 2024-03-26 | 荣耀终端有限公司 | Application management method, terminal device and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6189047B1 (en) * | 1997-03-20 | 2001-02-13 | Sun Microsystems, Inc. | Apparatus and method for monitoring event queue operations with pluggable event queues |
| CN105653934A (en) * | 2015-12-25 | 2016-06-08 | 惠州Tcl移动通信有限公司 | Mobile terminal and application protection method thereof |
| CN105701025A (en) * | 2015-12-31 | 2016-06-22 | 华为技术有限公司 | Memory recovery method and device |
| CN106874713A (en) * | 2017-01-09 | 2017-06-20 | 广东小天才科技有限公司 | A kind of application program runs right management method and device, user equipment |
| CN106933660A (en) * | 2017-02-17 | 2017-07-07 | 广州启生信息技术有限公司 | The implementation method of application process keep-alive under a kind of Android platform |
| CN107291549A (en) * | 2016-03-31 | 2017-10-24 | 阿里巴巴集团控股有限公司 | A kind of method and device for managing application program |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101144346B1 (en) * | 2009-02-20 | 2012-05-11 | 에스케이플래닛 주식회사 | Method of managing java application and computer-readable medium having thereon program performing function embodying the same |
| CN104021019B (en) * | 2014-06-18 | 2016-09-14 | 腾讯科技（深圳）有限公司 | A kind of apply the control method of self-starting, terminal and server |
| CN106648855B (en) * | 2016-11-21 | 2020-04-10 | 武汉斗鱼网络科技有限公司 | Method and device for controlling application program of terminal |
| CN106648861B (en) * | 2016-12-05 | 2020-07-14 | 阿里巴巴（中国）有限公司 | Keep-alive method and device for background service process |
| CN106874086B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
-
2017
- 2017-11-21 CN CN201711168305.3A patent/CN107844342B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6189047B1 (en) * | 1997-03-20 | 2001-02-13 | Sun Microsystems, Inc. | Apparatus and method for monitoring event queue operations with pluggable event queues |
| CN105653934A (en) * | 2015-12-25 | 2016-06-08 | 惠州Tcl移动通信有限公司 | Mobile terminal and application protection method thereof |
| CN105701025A (en) * | 2015-12-31 | 2016-06-22 | 华为技术有限公司 | Memory recovery method and device |
| CN107291549A (en) * | 2016-03-31 | 2017-10-24 | 阿里巴巴集团控股有限公司 | A kind of method and device for managing application program |
| CN106874713A (en) * | 2017-01-09 | 2017-06-20 | 广东小天才科技有限公司 | A kind of application program runs right management method and device, user equipment |
| CN106933660A (en) * | 2017-02-17 | 2017-07-07 | 广州启生信息技术有限公司 | The implementation method of application process keep-alive under a kind of Android platform |
Non-Patent Citations (1)
| Title |
|---|
| Android进程保活;zhichu_2025;《https://blog.csdn.net/ZhiChu_2025/article/details/52434525》;20160904;第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107844342A (en) | 2018-03-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107844342B (en) | Control method and device for keeping application program alive, storage medium and mobile terminal | |
| CN107748686B (en) | Application program starting optimization method and device, storage medium and intelligent terminal | |
| CN107748685B (en) | Application program starting control method and device, terminal equipment and storage medium | |
| CN108270786B (en) | Authority management method and device of application program, storage medium and intelligent terminal | |
| CN107783803B (en) | System optimization method and device of intelligent terminal, storage medium and intelligent terminal | |
| CN107943270B (en) | Application service control method and device, storage medium and mobile terminal | |
| CN107797841B (en) | Window control method and device, terminal equipment and storage medium | |
| CN107844341B (en) | Process starting control method and device, storage medium and mobile terminal | |
| CN107026933B (en) | Multi-open application message management method and device and intelligent terminal | |
| CN108804153B (en) | Application program preloading method and device, storage medium and terminal | |
| CN106484547B (en) | Multi-open application management method and device and terminal | |
| CN107831886B (en) | Control method and device for associated starting application, storage medium and intelligent terminal | |
| EP3486770B1 (en) | Processing method, device and storage medium for implementing automatic startup | |
| CN106896900B (en) | Display control method and device of mobile terminal and mobile terminal | |
| CN106817753B (en) | Method and device for saving electricity by switching background gray scales and mobile terminal | |
| CN108829229B (en) | Screen control method and device, storage medium and intelligent terminal | |
| CN107943269B (en) | Scheduling job control method, device, terminal equipment and storage medium | |
| CN109408465B (en) | File attribution information recording method, device, storage medium and terminal | |
| CN107885588B (en) | Application service control method and device, storage medium and mobile terminal | |
| EP3486823B1 (en) | System notification service control method, apparatus, terminal device, and storage medium | |
| CN107957913A (en) | Associate management-control method, device, storage medium and the mobile terminal started | |
| CN108845838B (en) | Application program preloading method and device, storage medium and terminal | |
| CN108710512B (en) | Application program preloading method and device, storage medium and intelligent terminal | |
| CN107423064A (en) | Message treatment method, device, terminal device and storage medium | |
| CN106502732B (en) | Application closing method and device and intelligent terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| 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. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |