CN105786519B - Android device program management method and android device - Google Patents
Android device program management method and android device Download PDFInfo
- Publication number
- CN105786519B CN105786519B CN201610153632.0A CN201610153632A CN105786519B CN 105786519 B CN105786519 B CN 105786519B CN 201610153632 A CN201610153632 A CN 201610153632A CN 105786519 B CN105786519 B CN 105786519B
- Authority
- CN
- China
- Prior art keywords
- application program
- background
- services
- application
- allowed
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- 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/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
-
- 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/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5022—Mechanisms to release resources
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a program management method of an android device and the android device, and solves the problem that an application program in operation of the android device with low memory is blocked. It relates to memory management field, especially relates to android device's memory management. The method comprises the following steps: when the Activity is transferred to a background, judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program; if the application programs or the services do not belong to the same application program or service, judging whether the application programs or the services belong to the application programs or the services which allow the background operation of the application programs or the services and judging whether the application programs or the services do not allow the background operation of the application programs or the services; if the background operation is not allowed, closing the application program corresponding to the Activity and releasing the memory occupied by the Activity. According to the technical scheme, the priority of the application program is obtained through the list recorded in the configuration file or the database, when the application program is transferred to the background, the application program with low priority is closed, and the occupied memory of the application program is released, so that the smooth operation of the application program with high priority is realized.
Description
Technical Field
The invention relates to the field of memory management, in particular to memory management of android equipment.
Background
Due to the open source characteristic of the android system, software systems of many consumer electronic products are developed based on android, and many android products for positioning low ends exist at present.
Most of products with low positioning end have relatively low hardware configuration, especially have small DDR capacity configuration, after a system presets a large number of APKs or a user installs a large number of APKs, the background always performs memory recovery to cause the system to be stuck due to insufficient system memory, the time for opening the APKs and switching the APKs is long, and even the system is stuck.
Disclosure of Invention
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The invention provides a program management method of an android device and the android device, and solves the problem that an application program in operation of the android device with low memory is blocked.
In order to achieve the above object, the inventor provides an android device program management method, including the steps of: when the Activity is transferred to the background, judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program or the same task; if the application programs or the services do not belong to the same application program or the same task, judging whether the application programs or the services are allowed to run in the background or not, and judging whether the application programs or the services are not allowed to run in the background or not; if the background operation is not allowed, closing the application program corresponding to the Activity and releasing the memory occupied by the Activity.
Further, the user sets the application programs or services allowing the user to run in the background through the corresponding operation interface, and the application programs or services are allowed to run after being transferred to the background to run.
Further, the method also comprises the following steps: and the user sets the application programs or services which are not allowed to run in the background through the corresponding operation interface, and the application programs or services are closed and the occupied memory of the application programs or services is released after the application programs or services are transferred to the background to run.
Further, comprising the steps of: the method comprises the steps of obtaining a list of application programs and services built in the device, and if background programs started through broadcasting or data services do not belong to the list, not allowing the background programs to be started. Further, the method also comprises the following steps: if the background program started through the broadcast or data service belongs to the google service framework and the equipment is judged to be used in China according to the geographic information of the equipment, the equipment is not allowed to be started.
Further, the method also comprises the following steps: when the application program is transferred to the background, whether the application program belongs to the application program built in the device is judged, if the application program does not belong to the built-in application program, the application program or the service is closed, and the occupied memory is released. Further, the step "closing the application corresponding to the Activity" includes acquiring the time for the application to shift to the background operation, and if the time for shifting to the background operation exceeds a set value, closing the application and releasing the memory occupied by the application.
The inventor also provides an android device comprising a monitoring module; the monitoring module is used for judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program when the Activity is transferred to the background; if the application programs or the services do not belong to the same application program or service, judging whether the application programs or the services belong to the application programs or the services which allow the background operation of the application programs or the services and judging whether the application programs or the services do not allow the background operation of the application programs or the services; and if the background operation is not allowed, closing the application program and releasing the memory occupied by the application program.
Further, the system also comprises a setting module;
the setting module is connected with the monitoring module;
the setting module is used for receiving the operation of the user on the operation interface and setting the application programs or services allowed by the background of the user;
the monitoring module is used for judging whether the application program or service transferred to the background belongs to the application program or service which allows the background to operate, and if so, allowing the application program or service to operate.
Further, the setting module is also used for receiving the operation of the user on the operation interface and setting the application programs or services which are not allowed by the background;
the monitoring module is also used for judging whether the application programs or the services transferred to the background running belong to the application programs or the services which are not allowed by the background running, if so, the application programs or the services are closed, and the occupied memory is released.
Further, the monitoring module is configured to obtain a list of applications and services built in the device, and if the background program started through the broadcast or data service does not belong to the list, the background program is not allowed to be started. Further, the monitoring module is used for not allowing the equipment to be started if the background program started through broadcasting or data service belongs to the google service framework and the equipment is judged to be used in China according to the geographic information of the equipment.
Further, the monitoring module is configured to determine whether the application program belongs to a built-in application program of the device when the application program is transferred to the background, and if the application program does not belong to the built-in application program, close the application program or the service, and release the memory occupied by the application program or the service. Further, the monitoring module is used for acquiring the time for transferring the application program to the background for operation, and if the time for transferring the application program to the background for operation exceeds a set value, the application program is closed, and the memory occupied by the application program is released.
Furthermore, the setting module is also used for optimally configuring android virtual machine parameters, file system parameters and the like aiming at low-memory devices, so that better performance is achieved.
Different from the prior art, according to the technical scheme, the priority of the application program is obtained through the list recorded in the configuration file or the database, when the application program is transferred to the background, the application program with low priority is closed, and the memory occupied by the application program is released, so that the smooth operation of the application program with high priority is realized.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present description is intended to include all such aspects and their equivalents.
Drawings
The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements, and in which:
fig. 1 is a flowchart of a method for managing an android device program according to an embodiment;
fig. 2 is a schematic diagram of an android device module according to the specific embodiment.
Description of reference numerals:
20. an android device;
201. a monitoring module;
202. and setting a module.
Detailed Description
To explain technical contents, structural features, and objects and effects of the technical solutions in detail, the following detailed description is given with reference to the accompanying drawings in conjunction with the embodiments. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details.
Referring to fig. 1, provided herein is an android device program management method, including the steps of: when the Activity is transferred to the background, judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program or the same task; if the application programs or the tasks do not belong to the same application program or the same task, judging whether the application programs or the services are allowed to run in the background or not, or judging whether the application programs or the services are not allowed to run in the background or not; if the background operation is not allowed, closing the application program corresponding to the Activity and releasing the memory occupied by the Activity.
Activity is one of the core components of Android. Activity goes to the background, i.e., is not visible in the display device of the device. When Activity enters the background, it will call onsop () method, and we can execute the above judgment method after Activity calls onsop () method.
In the Android system, an Application (Application) includes at least one Activity, while a Service (Service) is an Application component that runs in the background without a user interface to perform time-consuming operations. The application program and the service both have corresponding Package names, and whether the application program or the service belongs to the same application program or program can be judged by comparing the Activity Name with the Package Name (Package Name).
Task (Task) refers to combining related activities together and managing in an Activity Stack manner. For example, the user stays at the Activity of the short message application program, then jumps to the Activity of the Camera application program, and returns to the Activity of the short message application program after the photographing function is completed; in the above scenario, the short message application and the camera application belong to the same Task. During the starting process of the apk, structures are arranged inside an android system framework to record some information of the current apk, wherein the information includes the task to which the apk belongs.
The information of the application program and the service which are allowed to be operated in the background and the information of the application program and the service which are not allowed to be operated in the background can be recorded in a configuration file or a database file; the description may be a package name describing the application or service.
When an Activity is transferred to a background, inquiring the configuration file or the database, if the Activity name corresponding to the Activity does not exist in an application program or a list which allows the Activity to operate in the background or exists in an application program list which does not allow the Activity to operate in the background, if the Activity is not allowed to operate in the background, closing the application program corresponding to the Activity and releasing the memory occupied by the application program. According to the technical scheme, the priority of the application program is obtained through the list recorded in the configuration file or the database, when the application program is transferred to the background, the application program with low priority is closed, and the occupied memory of the application program is released, so that the smooth operation of the application program with high priority is realized.
And if the application program or service does not belong to the application program or service which allows the background operation, closing the application program or service and releasing the memory occupied by the application program or service.
For example, a list of installed applications and services may be obtained and displayed, and an icon of an application or service on the list may be clicked to set the list as an application that allows its background to run. The application or service that allows its background to run is the selected application or service in the list.
And the user sets the application programs or services which are not allowed to run in the background through the corresponding operation interface, and the application programs or services are closed and the occupied memory of the application programs or services is released after the application programs or services are transferred to the background to run.
For example, a list of installed applications and services may be obtained and displayed, and an application icon on the list may be clicked to set the list as an application whose background is not allowed to run. The application or service whose background is not allowed to run is the selected application or service in the list.
The management of the memory is more in line with the use requirements of different users through the manual setting of the users; and the same user can modify the application program which is allowed to run on the background of the user and the application program which is not allowed to run on the background of the user, so that the user can adopt different strategies to manage the memory according to the use requirements of the current scene at different time.
Preferably, the applications or services that allow their background to run may include applications or services that are built into the device. The method comprises the steps of obtaining a list of application programs and services built in the device, and if background programs started through broadcasting or data services do not belong to the list, not allowing the background programs to be started.
Preferably, applications or services that are not allowed to run in their background may include applications and services under the google services framework in china. Background programs started through broadcasting or data service belong to a Google service framework, and the equipment is judged to be used in China according to the geographic information of the equipment, and the equipment is not allowed to be started. Because the google server cannot be accessed in the Chinese region, part of functions of the application program and the service under the corresponding google service framework are not automatically started through broadcasting or data service under the default condition, and a user can start the corresponding functions through the APK.
In other embodiments, it may also be determined whether the application program belongs to an application program built in the device when the application program is transferred to the background, and if the application program does not belong to the built-in application program, the application program or the service is closed, and the memory occupied by the application program or the service is released.
The step of closing the application program corresponding to the Activity comprises the steps of acquiring the time for the application program to be transferred to the background for running, and if the time for transferring to the background for running exceeds a set value, closing the application program and releasing the memory occupied by the application program.
Starting to calculate after the Activity is transferred into the background, and closing the application program when the time for transferring into the background exceeds a set value; the setting value may be a default value or may be set by the user through a corresponding user interface.
Through the judgment, the user is ensured not to destroy the switched application program in a short time.
Reducing or closing the cache space of the android native memory recovery mechanism can also accelerate the memory recovery of the android device, so that the foreground application program can obtain more memories, and smooth operation of the foreground application program is facilitated. For low-memory devices, android virtual machine parameters (such as dalvik. vm. hoist. android), file system parameters (such as proc/sys/vm/dirty _ ratio), and the like are optimally configured, so that better performance is achieved. Some of the parameters can be seen from the above description
The modification configuration of the partial virtual machine parameters is as follows:
dalvik.vm.dex2oat-flags＝--no-watch-dog
dalvik.vm.dex2oat-filter＝interpret-only
dalvik.vm.image-dex2oat-filter＝speed
Dalvik.vm.heaptargetutilization＝0.85
part of the file system parameters are modified as follows:
write/proc/sys/vm/dirty_ratio 1
write/proc/sys/vm/dirty_writeback_centisecs 200
write/proc/sys/vm/dirty_expire_centisecs 1500
referring to fig. 2, the android device herein is a low memory android device 20 that includes a monitoring module 201. The monitoring module is used for judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program when the Activity is transferred to the background; if the application programs or the services do not belong to the same application program or service, judging whether the application programs or the services belong to the application programs or the services which allow the background operation of the application programs or the services and judging whether the application programs or the services do not allow the background operation of the application programs or the services; and if the background operation is not allowed, closing the application program and releasing the memory occupied by the application program.
Also included is a setup module 202;
the setting module is connected with the monitoring module;
the setting module is used for receiving the operation of the user on the operation interface and setting the application programs or services allowed by the background of the user;
the monitoring module is used for judging whether the application program or service transferred to the background belongs to the application program or service which allows the background to operate, if so, the application program or service is allowed to operate, and if not, the application program or service is closed, and the occupied memory is released.
In some embodiments, the setting module is further configured to receive an operation of the user on the operation interface, and set an application or service whose background is not allowed;
the monitoring module is also used for judging whether the application programs or the services transferred to the background running belong to the application programs or the services which are not allowed by the background running, if so, the application programs or the services are closed, and the occupied memory is released.
In some embodiments, the monitoring module is configured to obtain a list of applications and services built in the device, and if the daemon started through the broadcast or data service does not belong to the list, the daemon is not allowed to be started.
In some embodiments, the monitoring module is configured to disallow the start-up of the device if the daemon started up through the broadcast or data service belongs to the google service framework and it is determined that the device is used in china according to the geographic information of the device.
In some embodiments, the monitoring module is configured to further determine whether the application program belongs to an application program built in the device when the application program is transferred to the background, and if the application program does not belong to the built-in application program, close the application program or the service, and release a memory occupied by the application program or the service. In some embodiments, the monitoring module is configured to obtain a time for transferring the application program to the background operation, and if the time for transferring the application program to the background operation exceeds a set value, close the application program and release the memory occupied by the application program.
In some embodiments, the setting module is further configured to optimally configure parameters of an android virtual machine, parameters of a file system, and the like for low-memory devices, so as to achieve better performance.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrases "comprising … …" or "comprising … …" does not exclude the presence of additional elements in a process, method, article, or terminal that comprises the element. Further, herein, "greater than," "less than," "more than," and the like are understood to exclude the present numbers; the terms "above", "below", "within" and the like are to be understood as including the number.
As will be appreciated by one skilled in the art, the above-described embodiments may be provided as a method, apparatus, or computer program product. These embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. All or part of the steps in the methods according to the embodiments may be implemented by a program instructing associated hardware, where the program may be stored in a storage medium readable by a computer device and used to execute all or part of the steps in the methods according to the embodiments. The computer devices, including but not limited to: personal computers, servers, general-purpose computers, special-purpose computers, network devices, embedded devices, programmable devices, intelligent mobile terminals, intelligent home devices, wearable intelligent devices, vehicle-mounted intelligent devices, and the like; the storage medium includes but is not limited to: RAM, ROM, magnetic disk, magnetic tape, optical disk, flash memory, U disk, removable hard disk, memory card, memory stick, network server storage, network cloud storage, etc.
The various embodiments described above are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a computer apparatus to produce a machine, such that the instructions, which execute via the processor of the computer apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer device to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer apparatus to cause a series of operational steps to be performed on the computer apparatus to produce a computer implemented process such that the instructions which execute on the computer apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although the embodiments have been described, once the basic inventive concept is obtained, other variations and modifications of these embodiments can be made by those skilled in the art, so that the above embodiments are only examples of the present invention, and not intended to limit the scope of the present invention, and all equivalent structures or equivalent processes using the contents of the present specification and drawings, or any other related technical fields, which are directly or indirectly applied thereto, are included in the scope of the present invention.
Claims (12)
1. The android device program management method is characterized by comprising the following steps: when the Activity is transferred to the background, judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program or the same task by calling an onsop () method; if the application programs or the services do not belong to the same application program or the same task, judging whether the application programs or the services are allowed to run in the background or not, and judging whether the application programs or the services are not allowed to run in the background or not; if the background operation is not allowed, closing the application program corresponding to the Activity and releasing the memory occupied by the Activity;
the step of closing the application program corresponding to the Activity comprises the steps of acquiring the time for the application program to be transferred to the background for running, and if the time for transferring to the background for running exceeds a set value, closing the application program and releasing the memory occupied by the application program.
2. The android device program management method of claim 1, wherein a user sets, through a corresponding operation interface, applications or services that allow the user to run in the background, and then the applications or services are allowed to run after being transferred to the background, and if the applications or services do not belong to the applications or services that allow the user to run in the background, the applications or services are closed, and the memory occupied by the applications or services is released.
3. The android device program management method of claim 1, further comprising the steps of: and the user sets the application programs or services which are not allowed to run in the background through the corresponding operation interface, and the application programs or services are closed and the occupied memory of the application programs or services is released after the application programs or services are transferred to the background to run.
4. The android device program management method of claim 1, comprising the steps of: the method comprises the steps of obtaining a list of application programs and services built in the device, and if background programs started through broadcasting or data services do not belong to the list, not allowing the background programs to be started.
5. The android device program management method of claim 1, further comprising the steps of: if the background program started through the broadcast or data service belongs to the google service framework and the equipment is judged to be used in China according to the geographic information of the equipment, the equipment is not allowed to be started.
6. The android device program management method of claim 1, further comprising the steps of: when the application program is transferred to the background, whether the application program belongs to the application program built in the device is judged, if the application program does not belong to the built-in application program, the application program or the service is closed, and the occupied memory is released.
7. The android device is characterized by comprising a monitoring module; the monitoring module is used for judging whether the Activity and the Activity which is about to enter the foreground to run belong to the same application program or the same task by calling an onsop () method when the Activity is switched into the background; if the application programs or the services do not belong to the same application program or the same task, judging whether the application programs or the services are allowed to run in the background or not, and judging whether the application programs or the services are not allowed to run in the background or not; if the background operation is not allowed, closing the application program and releasing the memory occupied by the application program; the monitoring module is used for acquiring the time for transferring the application program to the background operation, and if the time for transferring the application program to the background operation exceeds a set value, closing the application program and releasing the memory occupied by the application program.
8. The android device of claim 7, further comprising a setup module;
the setting module is connected with the monitoring module;
the setting module is used for receiving the operation of the user on the operation interface and setting the application programs or services allowed by the background of the user;
the monitoring module is used for judging whether the application program or service transferred to the background belongs to the application program or service which allows the background to operate, if so, the application program or service is allowed to operate, and if not, the application program or service is closed, and the occupied memory is released.
9. The android device of claim 8, wherein the setup module is further configured to receive an operation of an operation interface by a user, and to set an application or a service whose background is not allowed;
the monitoring module is also used for judging whether the application programs or the services transferred to the background running belong to the application programs or the services which are not allowed by the background running, if so, the application programs or the services are closed, and the occupied memory is released.
10. The android device of claim 7, wherein the monitoring module is configured to obtain a list of applications and services built in the device, and if a daemon started through a broadcast or data service does not belong to the list, the daemon is not allowed to be started.
11. The android device of claim 7, wherein the monitoring module is configured to disallow the device to be started if the daemon started through the broadcast or data service belongs to the google service framework and the device is determined to be used in china according to the geographic information of the device.
12. The android device of claim 7, wherein the monitoring module is configured to determine whether the application program belongs to a built-in application program of the device when the application program is transferred to the background, and if the application program does not belong to the built-in application program, close the application program or the service, and release a memory occupied by the application program or the service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610153632.0A CN105786519B (en) | 2016-03-17 | 2016-03-17 | Android device program management method and android device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610153632.0A CN105786519B (en) | 2016-03-17 | 2016-03-17 | Android device program management method and android device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105786519A CN105786519A (en) | 2016-07-20 |
| CN105786519B true CN105786519B (en) | 2021-04-09 |
Family
ID=56393934
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610153632.0A Active CN105786519B (en) | 2016-03-17 | 2016-03-17 | Android device program management method and android device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105786519B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293910B (en) * | 2016-07-28 | 2020-02-18 | 宇龙计算机通信科技(深圳)有限公司 | Process cleaning method and mobile terminal |
| CN106325990B (en) * | 2016-08-19 | 2019-10-11 | 宇龙计算机通信科技(深圳)有限公司 | Control method, control device and the terminal of application program |
| CN106354561B (en) * | 2016-08-24 | 2020-01-24 | 禄可科技集团有限公司 | Control method for running memory of mobile terminal and mobile terminal |
| CN106445514B (en) * | 2016-09-13 | 2020-01-03 | Tcl集团股份有限公司 | Method and device for managing Activity instance of Android platform |
| CN106648855B (en) * | 2016-11-21 | 2020-04-10 | 武汉斗鱼网络科技有限公司 | Method and device for controlling application program of terminal |
| CN108008958A (en) * | 2017-11-29 | 2018-05-08 | 广东欧珀移动通信有限公司 | Backstage dex optimization methods, device and the computer-readable recording medium of a kind of application |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102866908A (en) * | 2012-07-25 | 2013-01-09 | 广东欧珀移动通信有限公司 | Method for cleaning Android background applications and services |
| CN103092700A (en) * | 2013-02-01 | 2013-05-08 | 华为终端有限公司 | Internal memory cleaning method and cleaning device and terminal device |
| CN103218307A (en) * | 2013-04-18 | 2013-07-24 | 海信集团有限公司 | Memory management system and memory management method |
| CN103559035A (en) * | 2013-10-31 | 2014-02-05 | 青岛海信移动通信技术股份有限公司 | Event processing method and device applied to Android platform |
| CN104268019A (en) * | 2014-09-23 | 2015-01-07 | 广州金山网络科技有限公司 | Software operating method and device and terminal |
| CN105260319A (en) * | 2015-09-11 | 2016-01-20 | 上海卓易科技股份有限公司 | Cleaning method and cleaning system for mobile terminal |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8533716B2 (en) * | 2004-03-31 | 2013-09-10 | Synopsys, Inc. | Resource management in a multicore architecture |
| US8392497B2 (en) * | 2009-11-25 | 2013-03-05 | Framehawk, LLC | Systems and algorithm for interfacing with a virtualized computing service over a network using a lightweight client |
| CN104854561B (en) * | 2012-10-16 | 2018-05-11 | 思杰系统有限公司 | Application program for application management framework encapsulates |
-
2016
- 2016-03-17 CN CN201610153632.0A patent/CN105786519B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102866908A (en) * | 2012-07-25 | 2013-01-09 | 广东欧珀移动通信有限公司 | Method for cleaning Android background applications and services |
| CN103092700A (en) * | 2013-02-01 | 2013-05-08 | 华为终端有限公司 | Internal memory cleaning method and cleaning device and terminal device |
| CN103218307A (en) * | 2013-04-18 | 2013-07-24 | 海信集团有限公司 | Memory management system and memory management method |
| CN103559035A (en) * | 2013-10-31 | 2014-02-05 | 青岛海信移动通信技术股份有限公司 | Event processing method and device applied to Android platform |
| CN104268019A (en) * | 2014-09-23 | 2015-01-07 | 广州金山网络科技有限公司 | Software operating method and device and terminal |
| CN105260319A (en) * | 2015-09-11 | 2016-01-20 | 上海卓易科技股份有限公司 | Cleaning method and cleaning system for mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105786519A (en) | 2016-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105786519B (en) | Android device program management method and android device | |
| CN110493067B (en) | Method and device for updating API gateway service | |
| CN107832100B (en) | APK plug-in loading method and terminal thereof | |
| CN112612214B (en) | Method and system for generating functional interface and electronic equipment | |
| CN106302632A (en) | The method for down loading of a kind of foundation image and management node | |
| CN104503828A (en) | Process management method and terminal | |
| CN104142844A (en) | Method and device for clearing processes of mobile terminal | |
| CN106648563B (en) | Dependency decoupling processing method and device for shared module in application program | |
| CN104899049A (en) | File deletion method and device | |
| CN112286652A (en) | Android APP background keep-alive method | |
| CN112306411A (en) | Data storage method and device, nonvolatile storage medium and processor | |
| CN106375866A (en) | Page loading method and terminal | |
| CN102214107A (en) | Method and device for changing Flash skin and color in client program | |
| CN106557404B (en) | Application control method and mobile terminal | |
| CN106507195A (en) | Method based on the intelligent television application handover management of linux system | |
| CN114040378B (en) | Method, device, computer equipment and storage medium for arranging application | |
| CN105872775A (en) | Silent uninstalling method and device for smart cloud TV application | |
| CN111367577A (en) | Method, device and terminal for loading plug-in of application | |
| CN110007943A (en) | A kind of application program update management method and system based on android system | |
| CN110704157B (en) | Application starting method, related device and medium | |
| CN115098254A (en) | Method and system for triggering execution of subtask sequence and electronic equipment | |
| CN114328196A (en) | Method, device and equipment for testing data leakage prevention system and storage medium | |
| CN108874586B (en) | Data recovery method and related product | |
| CN111913710A (en) | Method and device for setting navigation bar | |
| CN105511932A (en) | Application unloading method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 350003 building 18, No.89, software Avenue, Gulou District, Fuzhou City, Fujian Province Applicant after: Ruixin Microelectronics Co., Ltd Address before: 350003 building 18, No.89, software Avenue, Gulou District, Fuzhou City, Fujian Province Applicant before: Fuzhou Rockchips Electronics Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |