WO2018000675A1 - 一种后台应用管理装置、终端及后台应用管理方法 - Google Patents
一种后台应用管理装置、终端及后台应用管理方法 Download PDFInfo
- Publication number
- WO2018000675A1 WO2018000675A1 PCT/CN2016/103991 CN2016103991W WO2018000675A1 WO 2018000675 A1 WO2018000675 A1 WO 2018000675A1 CN 2016103991 W CN2016103991 W CN 2016103991W WO 2018000675 A1 WO2018000675 A1 WO 2018000675A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- cleaning
- background
- background application
- terminal
- application
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
-
- 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/466—Transaction processing
- G06F9/467—Transactional memory
Definitions
- the present invention relates to the field of terminal applications, and in particular, to a background application management device, a terminal, and a background application management method.
- the application of long-term residency causes serious waste of system resources and may also pose a threat to user privacy.
- the Android native mechanism cannot solve this problem.
- the existing mobile phone based on Android system adopts passive management mode, and generally triggers the memory recovery mechanism under the following three conditions: the available memory reaches the threshold, triggers LowMemoryKiller to perform process level memory recovery; Reports a runtime exception or other cause of process death, passive recovery of its child processes; application exit or memory space objects that are idle for a long time, garbage generated internally, and these garbage are recycled by GC (Garbage Collection) .
- the embodiment of the invention provides a background application management device, a terminal and a background application management method, so as to solve the problem that the prior art cannot actively manage the terminal background program.
- the embodiment of the present invention adopts the following technical solutions:
- a background application management device comprising:
- the detecting module is configured to detect whether the cleaning condition of the cleaning background application is met
- the cleaning condition includes that the terminal standby duration is greater than a threshold; the detecting module is configured to detect the standby duration of the terminal, determine whether the standby duration is greater than a threshold, and if greater, satisfy the cleaning condition.
- a timer is further included, the timer is used to start timing when the terminal enters the standby state, and the detection module is configured to detect the timing result of the timer to determine the standby duration.
- the cleanup module is configured to perform process level memory recovery on the application belonging to the cleanup list in the background running application by means of attribute setting.
- a terminal includes a background application management apparatus provided by an embodiment of the present invention.
- a background application management method including:
- the cleaning condition includes that the terminal standby duration is greater than a threshold; and detecting whether the cleaning background application condition is met includes:
- the cleaning condition is not met.
- detecting the standby duration of the terminal includes:
- the activation timer starts counting
- the timing of the detection timer determines the duration of the standby.
- detecting whether the cleaning conditions of the cleaning background application are met includes:
- the wake-up alarm is activated, and the wake-up alarm is used to trigger the cleaning of the background application;
- cleaning up applications running in the background includes:
- the background application management method detects whether the cleanup condition of the cleanup background application is met. If the cleanup condition is met, the application running in the background is cleaned according to the cleanup list, so that the user can set the cleanup list to the background.
- the application is managed, that is, the present invention proposes an active recycling method to recover the memory, and solves the problem that the prior art cannot actively manage the terminal background program, kills the application that does not have to reside, releases the system resources, and protects at the same time.
- the privacy of the user prevents a large number of third-party low-quality Android applications from pulling down system performance, resulting in a poor user experience.
- FIG. 1 is a flowchart of a background application management method according to Embodiment 1 of the present invention
- FIG. 2 is a schematic diagram of a background application management apparatus according to Embodiment 2 of the present invention.
- FIG. 3 is a flowchart of a background application management method according to Embodiment 3 of the present invention.
- Embodiment 4 is an effect diagram of a cleanup list provided by Embodiment 3 of the present invention.
- FIG. 5 is a schematic structural diagram of a terminal according to Embodiment 4 of the present invention.
- the present invention is applicable to all terminals, including PCs, mobile phones, PADs, and the like.
- the present invention will be further described in detail below with reference to the accompanying drawings.
- Embodiment 1 is a diagrammatic representation of Embodiment 1:
- FIG. 1 is a flowchart of a background application management method according to Embodiment 1 of the present invention. Referring to FIG. 1, the following process is included:
- the cleaning condition of the foregoing embodiment includes that the standby duration of the terminal is greater than a threshold; and detecting whether the cleaning condition of the cleaning background application is met includes:
- the cleaning condition is not met.
- the standby duration of the detecting terminal of the foregoing embodiment includes:
- the activation timer starts counting
- the timing of the detection timer determines the duration of the standby.
- whether the detection of the foregoing embodiment meets the cleaning conditions of the cleaning background application includes:
- the wake-up alarm is activated, and the wake-up alarm is used to trigger the cleaning of the background application;
- the cleaning of the background running application in the foregoing embodiment includes:
- Embodiment 2 is a diagrammatic representation of Embodiment 1:
- FIG. 2 is a schematic diagram of a background application management apparatus according to Embodiment 2 of the present invention.
- the background application management apparatus provided in this embodiment includes:
- the detecting module 21 is configured to detect whether the cleaning condition of the cleaning background application is met;
- the cleaning module 22 is configured to clean the application running in the background according to the cleaning list if the cleaning condition is met.
- the cleaning condition of the foregoing embodiment includes that the terminal standby duration is greater than a threshold; the detecting module 21 is configured to detect the standby duration of the terminal, determine whether the standby duration is greater than a threshold, and if greater than, meet the cleaning condition.
- the background application management apparatus of the above embodiment further includes a timer for starting timing when the terminal enters a standby state, and the detecting module 21 is configured to detect a timing result of the timer to determine a standby duration.
- the cleaning module 22 of the above embodiment is configured to perform process level memory recovery on the application belonging to the cleanup list in the background running application by means of attribute setting.
- the present invention provides a terminal, which includes a background application management apparatus provided by an embodiment of the present invention.
- the functional modules in all the above embodiments may be implemented by a processor, and the implementation of the processor includes but is not limited to a programmable device, a combination of a processor chip and a memory. Waiting for the way.
- Embodiment 3 is a diagrammatic representation of Embodiment 3
- This embodiment provides a method for releasing system resources through process level memory recovery during standby, thereby protecting user privacy and improving user experience.
- those applications with poor user perception are forced to exit, reclaim memory, and release the system resources occupied by them.
- it provides users with a list of configurable applications, understands user intent, and establishes recycling priority.
- the background application management method provided in this embodiment includes: after the terminal enters the standby state, if the information is provided after the screen is off for 10 minutes, the process level memory is collected according to the information provided by the list, and the kill signal is directly sent by using the method. For the process, the specific steps will not be described again.
- the configuration interface of the cleanup list can include all non-system applications in the terminal. You can select some or all applications as cleanup objects according to requirements.
- the user configures the cleanup list.
- the system saves the package name in the list to the data partition. To ensure that the data will not be erased after the user upgrades through OTA (Over-the-Air).
- OTA Over-the-Air
- the newly installed third-party application will join this list by default.
- the system determines that the cleanup condition is met, it will refer to this list to complete the cleanup. List design, each item only needs to show the user icon, application name, and a radio button to let the user choose whether to join.
- the general system Since the cleaning action starts to trigger after the screen is turned off for ten minutes, the general system will enter the standby state within one minute after the screen is not operated. The CPU under standby will not be calculated, so the alarm time is used to set the startup time. 10 minutes after the screen is off, at this time, a wakelock is applied to ensure that the device does not enter the standby state again because there is no user input event when the wake-up device starts to perform the cleaning task.
- the cleaning plan should be canceled when the screen is off. Otherwise, the original cleaning action will be performed during the user's use, which may result in the user using the device. Click on the application in the Launcher to be pulled up and flash back. Therefore, if you receive a bright event at this stage, you will remove the alarm, cancel the plan, and wait for the next time to reset the alarm.
- AMS's forceStopPackage(String) is usually time consuming, so the cleaning time will last for a long time. If the user chooses the bright screen during the cleaning process, and the operation starts. Equipment, then there is a high probability of flashback.
- This shell script is then declared as a service in rc, which is started by the property (ctl.start). If it is bright, it can be terminated at any time using the property settings.
- FIG. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
- the terminal 500 in the embodiment of the present invention may be different types of electronic devices, such as: a smart phone, a tablet computer, a palmtop computer, and a mobile internet device, a personal digital assistant, a media player, a smart TV, and a smart watch. , smart glasses, smart bracelets, etc.
- the terminal 500 in the embodiment of the present invention includes: at least one processor 510, such as a CPU, at least one receiver 513, at least one memory 514, at least one transmitter 515, and at least one communication bus 512.
- the communication bus 512 is used to implement connection communication between these components.
- the receiver 513 and the transmitter 515 may be wired transmission ports, or may be wireless devices, for example, including antenna devices for performing data communication with other devices.
- the memory 514 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.
- the processor 510 can execute the operating system of the terminal 500 and various installed application programs, program codes, and the like.
- each module described above includes the detecting module 21, the cleaning module 22, and the like.
- Program code is stored in the memory 514, and the processor 510 can invoke program code stored in the memory 514 via the communication bus 512 to perform related functions.
- the various modules eg, the detection module 21, the cleaning module 22, etc.
- FIG. 2 are program code stored in the memory 514 and executed by the processor 510 to implement The functions of the various modules are implemented to implement management of background applications.
- the memory 514 stores a plurality of instructions that are executed by the processor 510 to implement background application management. Specifically, the process 510: detecting whether the cleaning condition of the cleaning background application is met; if the cleaning condition is met, cleaning the application running in the background according to the cleaning list.
- the cleaning condition includes that the terminal standby duration is greater than a threshold; and the detecting whether the cleaning condition of the cleaning background application is met includes:
- the cleaning condition is not met.
- the standby duration of the detecting terminal includes: when the terminal enters the standby state, the activation timer starts counting; and detecting the timing result of the timer determines the standby duration.
- the detecting whether the cleaning condition of the cleaning background application is met includes: when the terminal enters the standby state, activating the wake-up alarm, the wake-up alarm is used to trigger the cleaning of the background application; determining whether the wake-up alarm expires If the wake-up alarm expires, the cleaning condition is met; if the wake-up alarm is not expired, the cleaning condition is not met.
- the cleaning the application running in the background comprises: determining, according to the cleaning list, a target application that needs to be cleaned in the background running application; performing process level memory on the target application by using an attribute setting manner Recycling.
- the background application management method detects whether the cleanup condition of the cleanup background application is met. If the cleanup condition is met, the application running in the background is cleaned according to the cleanup list, so that the user can set the cleanup list to the background.
- the application is managed, that is, the present invention proposes an active recycling method to recover the memory, and solves the problem that the prior art cannot actively manage the terminal background program, kills the application that does not have to reside, releases the system resources, and protects at the same time.
- the privacy of the user prevents a large number of third-party low-quality Android applications from pulling down system performance, resulting in a poor user experience.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
一种后台应用管理装置、终端及后台应用管理方法，该方法包括：检测是否满足清理后台应用的清理条件（S101）；若满足清理条件，则根据清理名单，对后台运行的应用进行清理（S102）。一种主动回收的方式对内存进行回收，解决了现有技术无法主动对终端后台程序进行管理的问题，杀掉非必须驻留的应用，释放系统资源，同时保护了用户的隐私，防止现在大量的第三方低质量Android应用拉低系统性能，导致不良的用户体验。
Description
本申请要求于2016年6月30日提交中国专利局，申请号为201610506780.6、发明名称为“一种后台应用管理装置、终端及后台应用管理方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本发明涉及终端应用领域，尤其涉及一种后台应用管理装置、终端及后台应用管理方法。
现有终端，例如基于Android系统的手机，由于Android系统开源，并且Android众多面向应用层API给Android应用开发者带了巨大的自由发挥空间，这使得用户可以安装大量的APK在手机上，应用开发者在应用层面，对系统的资源，尤其是内存和计算资源的合理使用方面重视度不够，或者出于其他原因，如为了应用背后的商家消息推送，恶意的用户信息搜集，长时间占用系统资源而不释放。虽然用户知道这些应用对设备使用造成了困扰，但是束手无策。
应用长时间的驻留，对系统资源造成了严重的浪费，同时也可能对用户的隐私造成威胁。Android原生机制无法解决这种问题。现有基于Android系统的手机，其手机内存管理方案采用被动管理方式，一般在以下三种条件下才会去触发内存回收机制：可用内存到达阀值，触发LowMemoryKiller进行进程级别的内存回收；应用内部报出运行时异常或者其他原因导致的进程死亡，对其子进程进行的被动回收；应用退出或者存在长时间闲置的内存占用对象，进程内部产生垃圾，通过GC（Garbage Collection）对这些垃圾进行回收。
本发明实施例提供一种后台应用管理装置、终端及后台应用管理方法，以解决现有技术无法主动对终端后台程序进行管理的问题。
为解决上述技术问题，本发明实施例采用以下技术方案:
一种后台应用管理装置，包括：
检测模块，设置为检测是否满足清理后台应用的清理条件；
清理模块，设置为若满足清理条件，则根据清理名单，对后台运行的应用进行清理。
进一步地，清理条件包括终端待机持续时长大于阈值；检测模块设置为检测终端的待机持续时长，判断待机持续时长是否大于阈值，若大于，则满足清理条件。
进一步地，还包括计时器，计时器用于在终端进入待机状态时开始计时，检测模块设置为检测计时器的计时结果确定待机持续时长。
进一步地，清理模块设置为通过属性设置的方式，对后台运行应用中属于清理名单的应用进行进程级别内存回收。
一种终端，其包括本发明实施例提供的后台应用管理装置。
一种后台应用管理方法，包括：
检测是否满足清理后台应用的清理条件；
若满足清理条件，则根据清理名单，对后台运行的应用进行清理。
进一步地，清理条件包括终端待机持续时长大于阈值；检测是否满足清理后台应用的清理条件包括：
检测终端的待机持续时长；
判断待机持续时长是否大于阈值；
若待机持续时长大于阈值，则满足清理条件；
若待机持续时长小于阈值，则不满足清理条件。
进一步地，检测终端的待机持续时长包括：
在终端进入待机状态时，激活计时器开始计时；
检测计时器的计时结果确定待机持续时长。
进一步地，检测是否满足清理后台应用的清理条件包括：
在终端进入待机状态时，激活唤醒闹钟，唤醒闹钟用于触发清理后台应用；
判断唤醒闹钟是否到期；
若唤醒闹钟到期，则满足清理条件；
若唤醒闹钟没有到期，则不满足清理条件。
进一步地，对后台运行的应用进行清理包括：
根据清理名单确定后台运行应用中需要被清理的目标应用；
通过属性设置的方式，对目标应用进行进程级别内存回收。
本发明实施例提供的后台应用管理方法，检测是否满足清理后台应用的清理条件，若满足清理条件，则根据清理名单，对后台运行的应用进行清理，这样，用户可以通过设置清理名单来对后台应用进行管理，即本发明提出一种主动回收的方式对内存进行回收，解决了现有技术无法主动对终端后台程序进行管理的问题，杀掉非必须驻留的应用，释放系统资源，同时保护了用户的隐私，防止现在大量的第三方低质量Android应用拉低系统性能，导致不良的用户体验。
图1为本发明实施例一提供的后台应用管理方法的流程图；
图2为本发明实施例二提供的后台应用管理装置的示意图；
图3为本发明实施例三提供的后台应用管理方法的流程图；
图4为本发明实施例三提供的清理名单的效果图；
图5为本发明实施例四提供的终端结构示意图。
本发明适用于所有终端，包括PC、手机、PAD等。下面通过具体实施方式结合附图对本发明作进一步详细说明。
实施例一：
图1为本发明实施例一提供的后台应用管理方法的流程图，请参考图1，包括如下流程：
S101：检测是否满足清理后台应用的清理条件；
S102：若满足清理条件，则根据清理名单，对后台运行的应用进行清理。在一实施例中，上述实施例的清理条件包括终端待机持续时长大于阈值；检测是否满足清理后台应用的清理条件包括：
检测终端的待机持续时长；
判断待机持续时长是否大于阈值；
若待机持续时长大于阈值，则满足清理条件；
若待机持续时长小于阈值，则不满足清理条件。
在一实施例中，上述实施例的检测终端的待机持续时长包括：
在终端进入待机状态时，激活计时器开始计时；
检测计时器的计时结果确定待机持续时长。
在一实施例中，上述实施例的检测是否满足清理后台应用的清理条件包括：
在终端进入待机状态时，激活唤醒闹钟，唤醒闹钟用于触发清理后台应用；
判断唤醒闹钟是否到期；
若唤醒闹钟到期，则满足清理条件；
若唤醒闹钟没有到期，则不满足清理条件。
在一实施例中，上述实施例的对后台运行的应用进行清理包括：
根据清理名单确定后台运行应用中需要被清理的目标应用；
通过属性设置的方式，对目标应用进行进程级别内存回收。
实施例二：
图2为本发明实施例二提供的后台应用管理装置的示意图， 如图2所示，本实施例提供的后台应用管理装置包括：
检测模块21，设置为检测是否满足清理后台应用的清理条件；
清理模块22，设置为若满足清理条件，则根据清理名单，对后台运行的应用进行清理。
在一实施例中，上述实施例的清理条件包括终端待机持续时长大于阈值；检测模块21设置为检测终端的待机持续时长，判断待机持续时长是否大于阈值，若大于，则满足清理条件。
在一实施例中，上述实施例的后台应用管理装置还包括计时器，计时器用于在终端进入待机状态时开始计时，检测模块21设置为检测计时器的计时结果确定待机持续时长。
在一实施例中，上述实施例的清理模块22设置为通过属性设置的方式，对后台运行应用中属于清理名单的应用进行进程级别内存回收。
对应的，本发明提供了一种终端，其包括本发明实施例提供的后台应用管理装置。
在一些实施例，上述所有实施例中的功能模块，如检测模块21及清理模块22都可以由处理器实现，处理器的实现方式包括但不局限于可编程器件、处理器芯片与存储器的组合等方式。
实施例三：
现结合具体应用场景对本发明做进一步的诠释说明。
本实施例提供一种在待机过程中通过进程级别内存回收来释放系统资源，保护用户隐私，同时提升用户的使用体验。在待机过程中，对那些用户可感知度差的应用进行强制退出，回收内存，释放其占用的系统资源。同时为用户提供可配置应用名单，理解用户意图，建立回收优先级。
作为独立的内存管理模块，需要设定其功能触发的时机和制订回收策略，关于用户可配置名单，即清理名单等，需要提供单独的人机交互界面，系统或者系统预置管理类应用在data（数据）分区创建文件记录。
如图3所示，本实施例提供的后台应用管理方法包括：终端进入待机状态后，如灭屏10分钟后开始按照该名单提供的信息进行进程级别的内存回收，采用的方式直接发kill信号给该进程，其具体步骤不再赘述。
关于清理名单的配置界面：
如图4所示，清理名单的配置界面可以包括终端内所有的非系统应用，用户可以根据需要选择部分或全部应用作为清理对象，用户配置清理名单，系统将名单中的包名保存存在data分区，保证当用户通过OTA（Over-the-Air，空中下载）的方式升级后该数据不会被擦除。新安装的第三方应用会默认加入此名单，当系统判定满足清理条件时，会参考此名单完成开始清理。名单设计，每条只需向用户展示应用icon，应用名称，一个单选框让用户选择是否加入。
关于清理过程：
由于清理动作在灭屏十分钟之后开始触发，但是一般系统在灭屏无操作一分钟之内会进入待机状态，待机下的CPU是不会进行计算的，所以使用闹钟的方式，将启动时间放在灭屏后的10分钟，这时申请一个wakelock，保证唤醒设备开始执行清理任务时，设备不会因为没有用户输入事件而再次进入待机状态。
如果在灭屏开始后的10min之内，设备屏幕电量，待机结束，那么在灭屏时的清理计划应该被取消，否则在用户使用中进行原有的清理动作，可能会导致用户使用设备过程中点击Launcher中的应用被拉起后闪退现象。因此需要在此阶段如果接到亮屏事件，则将闹钟移除，取消计划，等待下一次灭屏重新设置闹钟。
关于清理动作：
由于清理过程耗时要求足够短暂，使用frameworks层的接口进行清理，如AMS的forceStopPackage(String)通常很耗时，这样在清理时间会持续很久，如果在清理过程中用户选择亮屏，并且开始操作设备，那么很有可能出现闪退现象。鉴于此，我们可以使用shell脚本的形式，直接使用native层的指令对应用的进程进行操作。然后将此shell脚本在rc中声明为一个服务，采用属性(ctl.start)触发的形式启动此服务执行操作。如果亮屏，那么可以同样使用属性设置的方式随时终止。
实施例四
图5为本发明实施例提供的终端结构示意图。如图5所示，本发明实施例中的终端500可以是不同类型的电子设备，例如：智能手机、平板电脑、掌上电脑以及移动互联网设备、个人数字助理、媒体播放器、智能电视、智能手表、智能眼镜、智能手环等。
如图5所示，本发明实施例中的终端500包括：至少一个处理器510，例如CPU，至少一个接收器513，至少一个存储器514，至少一个发送器515，至少一个通信总线512。其中，所述通信总线512用于实现这些组件之间的连接通信。其中，所述接收器513和所述发送器515可以是有线发送端口，也可以为无线设备，例如包括天线装置，用于与其他设备进行数据通信。所述存储器514可以是高速RAM存储器，也可以是非易失性存储器（non-volatile memory），例如至少一个磁盘存储器。
所述处理器510可执行所述终端500的操作系统以及安装的各类应用程序、程序代码等，例如，上述的各个模块，包括所述检测模块21、所述清理模块22等。
所述存储器514中存储有程序代码，且所述处理器510可通过通信总线512，调用所述存储器514中存储的程序代码以执行相关的功能。例如，图2中所述的各个模块（例如，所述检测模块21、所述清理模块22等）是存储在所述存储器514中的程序代码，并由所述处理器510所执行，从而实现所述各个模块的功能以实现对后台应用的管理。
在本发明的一个实施例中，所述存储器514存储多个指令，所述多个指令被所述处理器510所执行以实现后台应用管理。具体而言，所述处理510：检测是否满足清理后台应用的清理条件；若满足所述清理条件，则根据清理名单，对后台运行的应用进行清理。
在进一步的实施例中，所述清理条件包括终端待机持续时长大于阈值；所述检测是否满足清理后台应用的清理条件包括：
检测终端的待机持续时长；
判断所述待机持续时长是否大于阈值；
若所述待机持续时长大于所述阈值，则满足清理条件；
若所述待机持续时长小于所述阈值，则不满足清理条件。
在进一步的实施例中，所述检测终端的待机持续时长包括：在终端进入待机状态时，激活计时器开始计时；检测所述计时器的计时结果确定所述待机持续时长。在进一步的实施例中，所述检测是否满足清理后台应用的清理条件包括：在终端进入待机状态时，激活唤醒闹钟，所述唤醒闹钟用于触发清理后台应用；判断所述唤醒闹钟是否到期；若所述唤醒闹钟到期，则满足清理条件；若所述唤醒闹钟没有到期，则不满足清理条件。
在进一步的实施例中，所述对后台运行的应用进行清理包括：根据所述清理名单确定后台运行应用中需要被清理的目标应用；通过属性设置的方式，对所述目标应用进行进程级别内存回收。
通过以上实施例的实施可知，本发明实施例提供的方法具备以下有益效果：
本发明实施例提供的后台应用管理方法，检测是否满足清理后台应用的清理条件，若满足清理条件，则根据清理名单，对后台运行的应用进行清理，这样，用户可以通过设置清理名单来对后台应用进行管理，即本发明提出一种主动回收的方式对内存进行回收，解决了现有技术无法主动对终端后台程序进行管理的问题，杀掉非必须驻留的应用，释放系统资源，同时保护了用户的隐私，防止现在大量的第三方低质量Android应用拉低系统性能，导致不良的用户体验。
以上内容是结合具体的实施方式对本发明所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。
Claims (10)
- 一种后台应用管理装置，包括：检测模块，设置为检测是否满足清理后台应用的清理条件；清理模块，设置为若满足所述清理条件，则根据清理名单，对后台运行的应用进行清理。
- 如权利要求1所述的后台应用管理装置，其特征在于，所述清理条件包括终端待机持续时长大于阈值；所述检测模块设置为检测终端的待机持续时长，判断所述待机持续时长是否大于阈值，若大于，则满足清理条件。
- 如权利要求2所述的后台应用管理装置，其特征在于，还包括计时器，所述计时器用于在终端进入待机状态时开始计时，所述检测模块设置为检测所述计时器的计时结果确定所述待机持续时长。
- 如权利要求1至3任一项所述的后台应用管理装置，其特征在于，所述清理模块设置为通过属性设置的方式，对后台运行应用中属于所述清理名单的应用进行进程级别内存回收。
- 一种终端，其特征在于，包括如权利要求1至4任一项所述的后台应用管理装置。
- 一种后台应用管理方法，包括：检测是否满足清理后台应用的清理条件；若满足所述清理条件，则根据清理名单，对后台运行的应用进行清理。
- 如权利要求6所述的后台应用管理方法，其特征在于，所述清理条件包括终端待机持续时长大于阈值；所述检测是否满足清理后台应用的清理条件包括：检测终端的待机持续时长；判断所述待机持续时长是否大于阈值；若所述待机持续时长大于所述阈值，则满足清理条件；若所述待机持续时长小于所述阈值，则不满足清理条件。
- 如权利要求7所述的后台应用管理方法，其特征在于，所述检测终端的待机持续时长包括：在终端进入待机状态时，激活计时器开始计时；检测所述计时器的计时结果确定所述待机持续时长。
- 如权利要求6所述的后台应用管理方法，其特征在于，所述检测是否满足清理后台应用的清理条件包括：在终端进入待机状态时，激活唤醒闹钟，所述唤醒闹钟用于触发清理后台应用；判断所述唤醒闹钟是否到期；若所述唤醒闹钟到期，则满足清理条件；若所述唤醒闹钟没有到期，则不满足清理条件。
- 如权利要求6至9任一项所述的后台应用管理方法，其特征在于，所述对后台运行的应用进行清理包括：根据所述清理名单确定后台运行应用中需要被清理的目标应用；通过属性设置的方式，对所述目标应用进行进程级别内存回收。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610506780.6 | 2016-06-30 | ||
| CN201610506780.6A CN106155777A (zh) | 2016-06-30 | 2016-06-30 | 一种后台应用管理装置、终端及后台应用管理方法 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2018000675A1 true WO2018000675A1 (zh) | 2018-01-04 |
Family
ID=57350756
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/103991 WO2018000675A1 (zh) | 2016-06-30 | 2016-10-31 | 一种后台应用管理装置、终端及后台应用管理方法 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106155777A (zh) |
| WO (1) | WO2018000675A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209114A (zh) * | 2019-12-31 | 2020-05-29 | 深圳Tcl新技术有限公司 | 系统内存释放方法、装置和存储介质 |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776038B (zh) | 2016-12-30 | 2019-12-27 | Oppo广东移动通信有限公司 | 一种热门应用资源分配方法及移动终端 |
| CN107450952B (zh) * | 2017-07-31 | 2019-08-06 | Oppo广东移动通信有限公司 | 应用管控方法、装置、存储介质及电子设备 |
| CN107728769B (zh) * | 2017-09-21 | 2021-11-09 | 深圳Tcl新技术有限公司 | 后台应用管理方法、装置及计算机可读存储介质 |
| CN107643948B (zh) * | 2017-09-30 | 2020-06-02 | Oppo广东移动通信有限公司 | 应用程序管控方法、装置、介质及电子设备 |
| CN109992402B (zh) * | 2017-12-29 | 2021-07-09 | Oppo广东移动通信有限公司 | 内存处理方法和装置、电子设备、计算机可读存储介质 |
| CN110032397B (zh) * | 2018-01-10 | 2023-01-31 | Oppo广东移动通信有限公司 | 应用处理方法和装置、电子设备、计算机可读存储介质 |
| CN112905266A (zh) * | 2021-03-31 | 2021-06-04 | 读书郎教育科技有限公司 | 一种智能手表后台程序管理的系统及方法 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981825A (zh) * | 2012-10-31 | 2013-03-20 | 广东欧珀移动通信有限公司 | 一种移动终端后台数据的管理方法及系统 |
| US20140031026A1 (en) * | 2012-07-30 | 2014-01-30 | Tencent Technology (Shenzhen) Company Limited | Method and device for performing a cleaning process on a portable electronic device |
| CN103902266A (zh) * | 2012-12-26 | 2014-07-02 | 中兴通讯股份有限公司 | 清理后台运行应用的方法和装置 |
| CN104298549A (zh) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | 移动终端中应用程序的清理方法、装置和移动终端 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104298335B (zh) * | 2013-07-19 | 2017-11-21 | 贝壳网际（北京）安全技术有限公司 | 移动终端的应用程序进程清理方法、装置和移动终端 |
| CN103914338A (zh) * | 2014-03-27 | 2014-07-09 | 可牛网络技术（北京）有限公司 | 一种清理终端后台应用的方法、终端及系统 |
| CN104462264A (zh) * | 2014-11-21 | 2015-03-25 | 北京奇虎科技有限公司 | 清理操作系统中垃圾文件的方法和装置 |
-
2016
- 2016-06-30 CN CN201610506780.6A patent/CN106155777A/zh active Pending
- 2016-10-31 WO PCT/CN2016/103991 patent/WO2018000675A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140031026A1 (en) * | 2012-07-30 | 2014-01-30 | Tencent Technology (Shenzhen) Company Limited | Method and device for performing a cleaning process on a portable electronic device |
| CN102981825A (zh) * | 2012-10-31 | 2013-03-20 | 广东欧珀移动通信有限公司 | 一种移动终端后台数据的管理方法及系统 |
| CN103902266A (zh) * | 2012-12-26 | 2014-07-02 | 中兴通讯股份有限公司 | 清理后台运行应用的方法和装置 |
| CN104298549A (zh) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | 移动终端中应用程序的清理方法、装置和移动终端 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209114A (zh) * | 2019-12-31 | 2020-05-29 | 深圳Tcl新技术有限公司 | 系统内存释放方法、装置和存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106155777A (zh) | 2016-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018000675A1 (zh) | 一种后台应用管理装置、终端及后台应用管理方法 | |
| TWI684859B (zh) | 遠端系統復原之方法 | |
| CN110908879B (zh) | 埋点数据的上报方法、装置、终端和存储介质 | |
| WO2018000673A1 (zh) | 一种终端应用程序运行的方法及装置 | |
| WO2016090902A1 (zh) | 一种操作系统热切换的方法、装置及移动终端 | |
| WO2013149460A1 (zh) | 一种Android手持设备连续增量的空中升级方法 | |
| WO2018041020A1 (zh) | 一种广播消息的管理方法及装置 | |
| WO2014079228A1 (zh) | 电子设备后台应用的自动清理方法、电子设备及存储介质 | |
| WO2017096796A1 (zh) | 用于智能手机的系统更新方法和装置 | |
| CN105676987A (zh) | 关闭移动终端后台应用的方法、装置及移动终端 | |
| WO2018018772A1 (zh) | 一种后台进程管理方法及终端设备 | |
| WO2019139364A1 (en) | Method and apparatus for modifying features associated with applications | |
| WO2017148117A1 (zh) | 一种安全刷机的方法及装置 | |
| WO2018094839A1 (zh) | 一种移动终端预装应用的安装方法及装置 | |
| CN102014021A (zh) | 一种控制数据链路通断的方法及装置 | |
| CN105610915A (zh) | 数据上报方法和系统 | |
| WO2017219535A1 (zh) | 应用程序的管理方法、管理装置及终端 | |
| WO2018018701A1 (zh) | 应用程序分级管理方法及系统 | |
| WO2018018819A1 (zh) | 应用程序的管理方法、管理装置及终端 | |
| WO2019024646A1 (zh) | 应用管控方法、装置及电子设备 | |
| Cinque et al. | How do mobile phones fail? a failure data analysis of symbian os smart phones | |
| WO2017219534A1 (zh) | 一种应用程序的处理方法及系统 | |
| WO2018068740A1 (zh) | 终端及其应用程序的启动管理方法 | |
| WO2018113529A1 (zh) | 一种快速查看通知的方法及移动设备 | |
| WO2015034246A1 (en) | Electronic device and method of processing user input by electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16907071 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16907071 Country of ref document: EP Kind code of ref document: A1 |