Patent Grant
10901779
The present disclosure relates to the field of communications technologies, and in particular, to a method for starting an application in background and a terminal device.
Android is a multitask system. In other words, Android can run a plurality of programs at the same time. Generally, it takes particular time overheads to start and run a program. Considering this, to accelerate a running speed, Android does not instantly “kill” a program that is exited, so that when the program is run again next time, the program can be rapidly started. As more programs are reserved in the system, a memory size is definitely insufficient. Low Memory Killer (LMK) is used to clear related application programs when the system memory size is less than a value, ensuring that the system maintains a particular amount of idle memory space.
The cleared application programs, when used again, are cold started instead of being hot started, and a start time is prolonged. For example, a start time of WeChat changes from 0.5 s to 2 s. Currently, a common method for increasing a cold start time of an application preloading a process of the application in background. When the application is used by a user next time, a start speed of the application can be accelerated. However, the following problem emerges: In a process of starting the application in the background, different types of prompt information, for example, a Toast, a permission selection box, a notification bar message, and a floating window occur, and user experience is affected.
A method and an apparatus for silently starting an application in background and a terminal device provided in embodiments of the present disclosure are used to resolve, to some extent, a problem that it takes an excessively long time to cold start an application that is cleared in background of an Android system, thereby not only avoiding a cold start problem, but also avoiding a problem of interference caused by different types of prompt information to a user.
According to a first aspect, the present disclosure provides a method for silently starting an application in background, including:
monitoring running statuses of applications on a terminal; and
when it is detected that a first application exits running, determining whether the first application is a silently started application; and if yes, intercepting prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the method provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the solution provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the first aspect, in a first possible implementation of the first aspect, before the determining whether the first application is a silently started application, and after the monitoring running statuses of applications on a terminal, the method further includes: obtaining, when it is detected that a second application exits running, a package name of the second application;
obtaining a process name of the second application based on the package name of the second application;
obtaining a process record of the second application based on the process name of the second application; and
restarting the second application based on the process record of the second application, and recording the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
This implementation provides a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used in subsequent actions to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use, or may be updated in real time. This is not limited herein.
With reference to the first possible implementation of the first aspect, in a second possible implementation of the first aspect, the obtaining, when it is detected that a second application exits running, a package name of the second application includes:
when it is detected that the second application exits running, detecting whether CPU load of the terminal is less than a first preset threshold; if yes, detecting whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtaining the package name of the second application.
With reference to any one of the first aspect, the first possible implementation of the first aspect, and the second possible implementation of the first aspect, in a third possible implementation of the first aspect, the prompt information for the first application includes one or more of the following information: a Toast toast, a permission selection box, notification bar information, and a floating window; and
the intercepting prompt information for the first application includes:
intercepting different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast.
Specifically, the modifying an NMS module may be: modifying an import queue (enqueue Toast) function in the NMS module, so that the import queue function is directly returned without creating a toast.
An interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box.
Specifically, the directly skipping an AMS module may be specifically: directly skipping a permission selection box popup function in the AMS module, so that the permission selection box is not displayed.
An interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information.
Specifically, the modifying the NMS module may be specifically: modifying an import notification (enqueue Notification Internal) function in the NMS module, so that the notification bar information is directly deleted.
An interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Specifically, the modifying a WMS module may be specifically: modifying a window visibility (set Win And Children Visibility) function and an add window (Add Window) function in the WMS module, so that a window of the floating window is invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the first possible implementation of the first aspect or the second possible implementation of the first aspect, in a fourth possible implementation of the first aspect, the obtaining a process name of the second application based on the package name of the second application includes:
obtaining information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtaining the process name of the second application based on the information about the second application.
According to a second aspect, an embodiment of the present disclosure provides an apparatus for silently starting an application in background, including:
a monitoring module, configured to monitor running statuses of applications on a terminal;
a prompt information interception module, configured to: when it is detected that a first application exits running, determine whether the first application is a silently started application;
and if yes, intercept prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the apparatus provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the apparatus provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the second aspect, in a first possible implementation of the second aspect, the apparatus further includes: a silent application list generation module, configured to:
obtain, when the monitoring module detects that a second application exits running, a package name of the second application;
obtain a process name of the second application based on the package name of the second application;
obtain a process record of the second application based on the process name of the second application; and
restart the second application based on the process record of the second application, and record the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
In the apparatus provided in this embodiment of the present disclosure, the silent application list generation module implements a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used by the prompt information interception module to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use before the prompt information interception module performs the foregoing steps, or may be updated in real time. This is not limited herein.
With reference to the first possible implementation of the second aspect, in a second possible implementation of the second aspect, the silent application list generation module is further configured to:
when the monitoring module detects that the second application exits running, detect whether CPU load of the terminal is less than a first preset threshold; if yes, detect whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtain the package name of the second application.
It should be noted that in a preferred implementation, the first preset threshold may be 60%, and the second preset threshold may be 800 M.
With reference to any one of the second aspect, the first possible implementation of the second aspect, and the second possible implementation of the second aspect, in a third possible implementation of the second aspect, the prompt information for the first application includes one or more of the following information: a Toast, a permission selection box, notification bar information, and a floating window; and
the prompt information interception module is specifically configured to intercept different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast.
Specifically, the modifying an NMS module may be: modifying an import queue (enqueue Toast) function in the NMS module, so that the import queue function is directly returned without creating a toast.
An interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box.
Specifically, the directly skipping an AMS module may be specifically: directly skipping a permission selection box popup function in the AMS module, so that the permission selection box is not displayed.
An interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information.
Specifically, the modifying the NMS module may be specifically: modifying an import notification (enqueue Notification Internal) function in the NMS module, so that the notification bar information is directly deleted.
An interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Specifically, the modifying a WMS module may be specifically: modifying a window visibility (set Win And Children Visibility) function and an add window (Add Window) function in the WMS module, so that a window of the floating window is invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the first possible implementation of the second aspect or the second possible implementation of the second aspect, in a fourth possible implementation of the second aspect, the silent application list generation module is further configured to:
obtain information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtain the process name of the second application based on the information about the second application.
According to a third aspect, an embodiment of the present disclosure provides a terminal device for silently starting an application in background, including a processor and a memory, where
the processor is configured to: monitor running statuses of applications on a terminal; and when it is detected that a first application exits running, determine whether the first application is a silently started application; and if yes, intercept prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list; and
the memory is configured to store the silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the terminal device provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the terminal device provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the third aspect, in a first possible implementation of the third aspect, the processor is further configured to obtain, when it is detected that a second application exits running, a package name of the second application;
obtain a process name of the second application based on the package name of the second application;
obtain a process record of the second application based on the process name of the second application; and
restart the second application based on the process record of the second application, and record the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
In the terminal device provided in this embodiment of the present disclosure, the processor implements a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used by the processor to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use, or may be updated in real time. This is not limited herein.
With reference to the first possible implementation of the third aspect, in a second possible implementation of the third aspect, the processor is specifically configured to: when it is detected that the second application exits running, detect whether CPU load of the terminal is less than a first preset threshold; if yes, detect whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtain the package name of the second application.
It should be noted that in a preferred implementation, the first preset threshold may be 60%, and the second preset threshold may be 800 M.
With reference to any one of the third aspect, the first possible implementation of the third aspect, and the second possible implementation of the third aspect, in a third possible implementation of the third aspect, the prompt information for the first application includes one or more of the following information: a Toast, a permission selection box, notification bar information, and a floating window; and specifically, the processor is configured to intercept different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast.
Specifically, the modifying an NMS module may be: modifying an import queue (enqueue Toast) function in the NMS module, so that the import queue function is directly returned without creating a toast.
An interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box.
Specifically, the directly skipping an AMS module may be specifically: directly skipping a permission selection box popup function in the AMS module, so that the permission selection box is not displayed.
An interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information.
Specifically, the modifying the NMS module may be specifically: modifying an import notification (enqueue Notification Internal) function in the NMS module, so that the notification bar information is directly deleted.
An interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Specifically, the modifying a WMS module may be specifically: modifying a window visibility (set Win And Children Visibility) function and an add window (Add Window) function in the WMS module, so that a window of the floating window is invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
With reference to the first possible implementation of the third aspect or the second possible implementation of the third aspect, in a fourth possible implementation of the third aspect, the processor is specifically configured to:
obtain information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtain the process name of the second application based on the information about the second application.
To describe the technical solutions in the embodiments of the present disclosure or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may derive other drawings from these accompanying drawings without creative efforts.
To make a person skilled in the art understand the technical solutions in the present disclosure better, the following clearly describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are merely some rather than all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.
Data structures and code described in the embodiments of the present disclosure are usually stored in a computer-readable storage medium. The computer-readable storage medium may be any device or medium that may store code and/or data to be used by a computer system. The computer-readable storage medium includes but is not limited to, a volatile memory, a non-volatile memory, a magnetic and optical storage device such as a disk drive, a magnetic tape, a CD (compact disc), and DVD (digital video disc), or other media that can store code and/or data.
Methods and processes described in the embodiments of the present disclosure may be implemented by using code and/or data, and the code and/or data may be stored in the computer-readable storage medium described above. When the computer system reads and runs the code and/or data stored in the computer-readable storage medium, the computer system can perform the methods and processes described in the embodiments of the present disclosure. In addition, the methods and processes described in the embodiments of the present disclosure may be included in hardware modules or apparatuses. The modules or apparatuses may include but are not limited to, an application-specific integrated circuit (ASIC) chip, a field programmable gate array (FPGA), a dedicated or shared processor that runs a particular software module or a segment of code at a particular time, and/or another programmable logic device. The hardware modules or apparatuses, when activated, perform the methods and processes included therein.
It should further be understood that, although terms first, second, and the like may be used in this specification to describe various elements, the terms are merely used to distinguish the elements from other related objects. For example, a first application may also be referred to as a second application, and similarly, a second application may also be referred to as a first application without departing from the scope of the present disclosure.
The terms used in the description of the present disclosure are merely for the purpose of illustrating specific embodiments, and are not intended to limit the present disclosure. The terms “a” and “the” of singular forms used in the specification and the appended claims of the present disclosure are also intended to include plural forms, unless otherwise specified in the context clearly. It should also be understood that, the term “and/or” used herein indicates and includes any or all possible combinations of one or more associated features.
S101. Monitor running statuses of applications on a terminal.
S103. When it is detected that a first application exits running, determine whether the first application is a silently started application, and if yes, intercept prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the method provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the solution provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
Based on the solution provided in the foregoing embodiment, an embodiment of the present disclosure further provides a method 200. The method 200 further includes S102 before S103 of “determining whether the first application is a silently started application”, and after S101 of “monitoring running statuses of applications on a terminal”. Specifically, S102 includes:
S1021. Obtain, when it is detected that a second application exits running, a package name of the second application.
S1022. Obtain a process name of the second application based on the package name of the second application.
S1023. Obtain a process record of the second application based on the process name of the second application.
S1024. Restart the second application based on the process record of the second application, and record the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
The method 200 in this embodiment of the present disclosure provides a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps S1021 to S1024 are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used in a subsequent step S103 to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use before the entire method 100, or updated in real time. This is not limited herein.
It should be noted that, S1021 may be detailed as follows: When it is detected that the second application exits running, detecting whether CPU load of the terminal is less than a first preset threshold; if yes, further detecting whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtaining the package name of the second application. In a preferred implementation, the first preset threshold may be 60%, and the second preset threshold may be 800 M.
In the foregoing embodiment provided in the present disclosure, optionally, the prompt information for the first application may include one or more of the following information: a Toast, a permission selection box, notification bar information, and a floating window; and
correspondingly, the step S103 of “intercepting prompt information for the first application” includes:
intercepting different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast;
an interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box;
an interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information; and
an interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
In the foregoing embodiment provided in the present disclosure, optionally, the obtaining a process name of the second application based on the package name of the second application includes:
obtaining information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtaining the process name of the second application based on the information about the second application.
The following describes in detail related technical details by using an Android architecture as an example. A terminal device described in the embodiments of the present disclosure may be a mobile phone, a tablet computer, a portable media player, or another small-sized electronic device having a digital media function.
In addition, the application layer may include various application programs such as a home (home) screen, a media player, and a browser.
Based on the logical architecture of the terminal device described above, the monitoring action described in S101 in this embodiment of the present disclosure is mainly used to: monitor application programs run on the hardware layer of user equipment; and when it is detected that an application exits running, further determine whether the application is a silently started application; and if yes, invoke hardware of the device to perform encoding, and modify a function in a corresponding module to intercept prompt information related to the application.
In another embodiment provided in the present disclosure, referring to
the monitoring module 301 is configured to monitor running statuses of applications on a terminal.
the prompt information interception module 303 is configured to: when it is detected that a first application exits running, determine whether the first application is a silently started application; and if yes, intercept prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the apparatus provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the apparatus provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
Based on the apparatus provided in the foregoing embodiment, an embodiment of the present disclosure further provides another apparatus. Based on the apparatus 300, the apparatus further includes: a silent application list generation module 305. Specifically, the silent application list generation module 305 is configured to:
obtain, when the monitoring module detects that a second application exits running, a package name of the second application;
obtain a process name of the second application based on the package name of the second application;
obtain a process record of the second application based on the process name of the second application; and
restart the second application based on the process record of the second application, and record the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
In the apparatus provided in this embodiment of the present disclosure, the silent application list generation module 305 implements a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used by the prompt information interception module 303 to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use before the prompt information interception module 303 performs the foregoing step, or may be updated in real time. This is not limited herein.
Further optionally, the silent application list generation module 305 may be specifically configured to: when it is detected that the second application exits running, detect whether CPU load of the terminal is less than a first preset threshold; if yes, further detect whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtain the package name of the second application. In a preferred implementation, the first preset threshold may be 60%, and the second preset threshold may be 800 M.
In the foregoing embodiment provided in the present disclosure, optionally, the prompt information for the first application includes one or more of the following information: a Toast, a permission selection box, notification bar information, and a floating window; and
the prompt information interception module 303 is specifically configured to intercept different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast;
an interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box;
an interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information; and
an interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
In the foregoing embodiment provided in the present disclosure, optionally, the silent application list generation module 305 is further configured to:
obtain information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtain the process name of the second application based on the information about the second application.
In still another embodiment provided in the present disclosure, referring to
The following specifically describes the components of the terminal device 400 with reference to
The RF circuit 410 may be configured to receive and send signals in an information receiving and sending process or a call process. Particularly, the RF circuit 410 receives downlink information from a base station, delivers the downlink information to the processor 480 for processing, and additionally sends uplink data to the base station. Usually, the RF circuit 410 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, and the like. In addition, the RF circuit 410 may also communicate with a network and another device through wireless communication. The wireless communication may use any communication standard or protocol, which includes, but is not limited to, a Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), an email, a short messaging service (SMS), and the like.
The memory 420 may be configured to store an operating system and an application program. The processor 480 runs the application program and the operating system stored in the memory 420 to invoke a hardware resource to perform various functions and data processing. Specifically, the processor 480 may perform the application program and the operating system stored in the memory 420 to perform the method steps described in
The input unit 430 may be configured to receive input digit or character information, and generate a key signal input related to a user setting and function control of a mobile device. Specifically, the input unit 430 may include a touch panel 431 and another input device 432. The touch panel 431, also referred to as a touchscreen, may collect a touch operation of a user on or near the touch panel (such as an operation of a user on or near the touch panel 431 by using any suitable object or attachment, such as a finger or a touch pen). In addition to the touch panel 431, the input unit 430 may further include the another input device 432. Specifically, the another input device 432 may include, but is not limited to, one or more of a physical keyboard, a functional key (such as a volume control key or a switch key), a trackball, a mouse, and a joystick.
The display unit 440 may be configured to display a system desktop or a graphical interface of an application program. The display unit 440 may include a display panel 441. Optionally, the display unit 640 may be in a type of a liquid crystal display (LCD), an organic lighting-emitting diode (OLED), and the like. Further, the touch panel 431 may cover the display panel 441. After detecting a touch operation on or near the touch panel 431, the touch panel 431 transfers a touch event to the processor 480, to determine a type of the touch event. Then, the processor 480 provides a corresponding visual output on the display panel 441 according to the type of the touch event, for example, updates a graphical interface currently displayed on the application program. Although, in
The terminal device 400 may further include at least one sensor 450 such as an optical sensor, a motion sensor, and another sensor. As to other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor that may be further configured on the terminal device, details are not repeatedly described herein.
The audio circuit 460, a speaker 461, and a microphone 462 may provide an audio interface between a user and the terminal device. The audio circuit 460 may transmit an electrical signal, which is converted from received audio data, to the speaker 461. The speaker 461 converts the electrical signal into a sound signal and outputs the sound signal. On the other hand, the microphone 462 converts a collected sound signal into an electrical signal. After receiving the electrical signal, the audio circuit 460 converts the electrical signal into audio data, and then outputs the audio data. After being processed by the processor 480, the audio data is sent through the RF circuit 410 to another user equipment or the audio data is output to the memory 420 for further processing.
Wi-Fi belongs to a short-distance wireless transmission technology. Although
The processor 480 is a control center of the terminal device 400, connects components of the entire terminal device by using various interface and buses, and performs various functions of the terminal device by running the operating system and the application program stored in the memory 420. Although not shown in the figure, the terminal device 400 may further include a camera, a Bluetooth module, and the like, which are not further described herein.
Based on the description of the components of the terminal device 400, the following describes in detail how the terminal device 400 is specifically applied to silently start an application in background. The processor 480 is configured to: monitor running statuses of applications on a terminal; and when it is detected that a first application exits running, determine whether the first application is a silently started application; and if yes, intercept prompt information for the first application, where the first application is any one of the applications on the terminal, and the silently started application is an application recorded in a silent application list.
The memory 420 is configured to store the silent application list.
The silently started application is an application that is restarted by a system in a manner not perceived by a user.
In this way, when system memory of an Android system is lower than a value, or when an Android system clears, due to other reasons, applications reserved to run in background, the terminal device provided in this embodiment of the present disclosure can prevent the applications from being cleared. In this case, when the applications are restarted, the applications are not cold started and an excessively long start time is avoided, thereby improving user experience. Moreover, according to the terminal device provided in this embodiment of the present disclosure, prompt information for the application is intercepted when it is determined that the application is a silently started application, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
Based on the terminal device provided in the foregoing embodiment, further, the processor 480 of the terminal device 400 is further configured to:
obtain, when it is detected that a second application exits running, a package name of the second application;
obtain a process name of the second application based on the package name of the second application;
obtain a process record of the second application based on the process name of the second application; and
restart the second application based on the process record of the second application, and record the package name of the second application into the silent application list after the second application is successfully started, where the second application is any one of the applications on the terminal.
In the terminal device provided in this embodiment of the present disclosure, the processor 480 implements a generation process of the silent application list. That is, when it is detected that an application exits running, the foregoing steps are performed on the application, to generate a list of silent applications, or referred to as a silent application list. The silent application list is used by the processor 480 to “determine whether the first application is a silently started application”. To be specific, when the first application is recorded in the silent application list, the first application is a silently started application, or when the first application is not recorded in the silent application list, the first application is not a silently started application. The generation process of the silent application list may be obtained in advance for later use, or may be updated in real time. This is not limited herein.
Further, optionally, the processor 480 may be specifically configured to: when it is detected that the second application on the terminal device exits running, detect whether CPU load of the terminal is less than a first preset threshold; if yes, detect whether effective memory of the terminal is greater than a second preset threshold; and if yes, obtain the package name of the second application. In a preferred implementation, the first preset threshold may be 60%, and the second preset threshold may be 800 M.
In the foregoing embodiment provided in the present disclosure, optionally, the prompt information for the first application includes one or more of the following information: a Toast, a permission selection box, notification bar information, and a floating window; and
the processor 480 is specifically configured to intercept different prompt information in the prompt information for the first application in different interception manners, where
an interception manner for the Toast toast is: modifying an NMS (Notification Manager Service notification manager service) module and skipping creating a toast;
an interception manner for the permission selection box is: directly skipping an AMS (Activity Manager Service activity manager service) module, and skipping displaying the permission selection box;
an interception manner for the notification bar information is: modifying the NMS module, and directly deleting the notification bar information; and
an interception manner for the floating window is: modifying a WMS (Window Manager Service window manager service) module, and setting a window of the floating window to be invisible.
Therefore, the prompt information for the first application is intercepted, so that different types of prompt information do not pop up to divert attention of the user in a process of starting the application in the background, thereby improving overall user experience.
In the foregoing embodiment provided in the present disclosure, optionally, the processor 480 is further specifically configured to:
obtain information about the second application based on the package name of the second application, where the information about the second application includes: a version, a version number, a developer, and developer vendor information of the second application; and
obtain the process name of the second application based on the information about the second application.
The method and apparatus for silently starting an application in background and the terminal device provided in the embodiments of the present disclosure are described above in detail. Although the principles and implementations of the present disclosure are described by using specific examples in this specification, the foregoing descriptions of the embodiments are only intended to help understand the method and core idea of the method of the present disclosure. Meanwhile, a person of ordinary skill in the art may make modifications to the specific implementations and application range according to the idea of the present disclosure. In conclusion, the content of the specification should not be construed as a limitation on the present disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2016 1 0817836 | Sep 2016 | CN | national |
This application is a continuation of International Application No. PCT/CN2017/100553, filed on Sep. 5, 2017, which claims priority to Chinese Patent 201610817836.X, filed on Sep. 12, 2016. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20050229185 | Stoops et al. | Oct 2005 | A1 |
| 20060206587 | Fabbrocino | Sep 2006 | A1 |
| 20080148411 | Murakami | Jun 2008 | A1 |
| 20120246655 | Chaar | Sep 2012 | A1 |
| 20140372356 | Bilal et al. | Dec 2014 | A1 |
| 20150350232 | Liu | Dec 2015 | A1 |
| 20160054990 | Qin | Feb 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 103176842 | Jun 2013 | CN |
| 103781057 | May 2014 | CN |
| 104680060 | Jun 2015 | CN |
| 105045588 | Nov 2015 | CN |
| 105045637 | Nov 2015 | CN |
| 105095746 | Nov 2015 | CN |
| 105260247 | Jan 2016 | CN |
| 105260671 | Jan 2016 | CN |
| 105718284 | Jun 2016 | CN |
| 201232400 | Aug 2012 | TW |
| Number | Date | Country | |
|---|---|---|---|
| 20190205159 A1 | Jul 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2017/100553 | Sep 2017 | US |
| Child | 16351011 | US |
