CN108228321B

CN108228321B - Android system application closing method and device

Info

Publication number: CN108228321B
Application number: CN201810058686.8A
Authority: CN
Inventors: 张辉
Original assignee: Beijing Qihoo Technology Co Ltd
Current assignee: Beijing Qihoo Technology Co Ltd
Priority date: 2014-12-16
Filing date: 2014-12-16
Publication date: 2021-08-10
Anticipated expiration: 2034-12-16
Also published as: CN104484223A; CN104484223B; CN108228321A

Abstract

The invention discloses an application closing method of an android system, mainly relating to the technical field of computers, and specifically comprising the following steps: monitoring whether an incubation process is started in the android system; if the hatching process is started, judging whether the process belongs to a process within a system necessary range; if the process does not belong to the process within the system necessary range, recording the process information of the process; judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system; and if a closing instruction is received, closing the process according to the recorded process information. According to the method and the device, the process information of the app can be recorded, after the system is locked, if a user triggers a closing instruction through a function key of the terminal, the process can be closed according to the recorded process information, the process which is not in the system necessary range and can operate in the android system in a locked state can be conveniently closed, and the beneficial effect of reducing the power consumption of the system is achieved.

Description

Android system application closing method and device

The patent application of the invention is a divisional application of Chinese invention patent application with the application date of 2014, 12 and 16, the application number of 201410784204.9 and the invention name of' an android system application closing method and device

Technical Field

The invention relates to the technical field of computers, in particular to an application closing method and device of an android system.

Background

With the development of smart phones, various systems for supporting smart phones have appeared. Such as android systems. Android is an open source code operating system based on Linux, and is mainly used for mobile terminals such as mobile phones. The Android platform consists of an operating system, middleware, a user interface and application software.

With the increase of the market share of the Android system, more and more developers develop apps (applications) based on the Android system, so that users can use Android mobile phones more conveniently. In a traditional android system, an application closing method exists, namely in a system unlocking state, a user presses an exit function key for a long time, namely a window interface of an application opened in the current system is popped up, and then the user can operate and close the corresponding application. But the closing of the application requires the operating system to enter an unlocked state before entering the application closing process.

Disclosure of Invention

In view of the above, the present invention has been made to provide an android system application shutdown device and a corresponding android system application shutdown method that overcome or at least partially solve the above-mentioned problems.

According to one aspect of the invention, an android system application closing method is provided, and comprises the following steps:

monitoring whether an incubation process is started in the android system;

if the hatching process is started, judging whether the process belongs to a process within a system necessary range; if the process does not belong to the process within the system necessary range, recording the process information of the process;

judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system;

and if a closing instruction is received, closing the process according to the recorded process information.

Preferably, the method further comprises the following steps:

replacing the initial process incubator of the android system with a specific first process incubator; and monitoring whether the android system starts an incubation process or not through the first process incubator.

Preferably, the monitoring, by the first course incubator, whether the android system starts an incubation course includes:

creating a java virtual machine through the first process incubator;

and registering a monitoring socket through the java virtual machine, and monitoring whether the android system starts an incubation process through the monitoring socket.

Preferably, the listening, through the socket, whether to start hatching window service includes:

monitoring whether a creating message of an incubation process is received in the socket; if the listening socket receives a create message, it is determined to start an incubation process.

Preferably, the determining whether a closing instruction triggered by a user is received in the screen locking state of the android system includes:

receiving a trigger operation of a user on an appointed key in a screen locking state, and judging whether the trigger operation on the appointed key meets a preset rule or not; and if the triggering operation of the specified key accords with a preset rule, judging that a closing instruction is received.

Preferably, the method further comprises the following steps:

intercepting the call of an initial window object acquisition function in the android system before a window object acquisition function called by a window service;

replacing the intercepted initial window object acquisition function with a first window object acquisition function;

when the window service is triggered to acquire the window object, the window service acquires the window object by calling the first window object acquisition function and returns to the designated process to record the window object.

Preferably, after receiving the closing instruction, the method further includes:

acquiring a window thumbnail from a corresponding window object according to the corresponding relation between the process information and the window object, and displaying the window thumbnail at an appointed position of a screen locking interface;

further, the method also comprises the following steps:

receiving a second closing instruction of the user for at least one window thumbnail; and when a second closing instruction aiming at least one window thumbnail is received, closing the corresponding process according to the recorded process information.

Preferably, intercepting the call to the initial window object obtaining function in the android system before the window object obtaining function called by the window service includes:

monitoring whether to start hatching window service or not through the first process incubator;

and if the window service which starts hatching is monitored, intercepting the creation of the window service, thereby intercepting the loading of the window service on an initial window object acquisition function in the android system which needs to be called.

Preferably, replacing the intercepting window object obtaining function with a first window object obtaining function comprises:

after intercepting the creation of the window service, replacing an initial window object acquisition function which needs to be loaded by the window service with a first window object acquisition function;

and creating the window service and loading the first window object acquisition function.

Preferably, the replacing the initial window object obtaining function that the window service needs to load with the first window object obtaining function includes:

replacing an initial getfocuswindow function needing to be loaded by the window service with a first getfocuswindow function; and the return time sequence of the first getfocuscenter function is a return appointed process.

Preferably, the window service acquiring the window object by calling the first window object acquisition function includes:

and finding the windowsta window object at the top of the window object stack through the first getfocuscindow function.

Preferably, the method further comprises the following steps:

when a window object at the top of a window object stack changes, judging whether the window object is acquired;

and if the window object is not acquired, continuing to return the window object to the specified process.

According to another aspect of the present invention, there is provided an android system application shutdown device, including:

the process creation monitoring module is suitable for monitoring whether an incubation process starts in the android system;

the information recording module is suitable for judging whether the process belongs to a process within a system necessary range if the hatching process is started; if the process does not belong to the process within the system necessary range, recording the process information of the process;

the closing triggering module is suitable for judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system;

and the process closing module is suitable for closing the process according to the recorded process information if a closing instruction is received.

Preferably, the method further comprises the following steps:

the process incubator replacing module is suitable for replacing the initial process incubator of the android system with a specific first process incubator; and monitoring whether the android system starts an incubation process or not through the first process incubator.

Preferably, the process creation monitoring module includes:

the Java virtual machine creating module is suitable for creating a Java virtual machine through the first process incubator;

and the monitoring socket registration module is suitable for registering a monitoring socket through the java virtual machine and monitoring whether the android system starts an incubation process through the monitoring socket.

Preferably, the process creation monitoring module includes:

the first process creation monitoring module is suitable for monitoring whether a creation message of an incubation process is received in the socket; if the listening socket receives a create message, it is determined to start an incubation process.

Preferably, the shutdown trigger module includes:

the first closing triggering module is suitable for receiving the triggering operation of a user on an appointed key in a screen locking state and judging whether the triggering operation on the appointed key meets a preset rule or not; and if the triggering operation of the specified key accords with a preset rule, judging that a closing instruction is received.

Preferably, the method further comprises the following steps:

the window interception module is suitable for intercepting the call of an initial window object acquisition function in the android system before the window object acquisition function called by the window service;

a function replacement module adapted to replace the intercepted initial window object acquisition function with a first window object acquisition function;

and the window acquisition module is suitable for acquiring the window object by calling the first window object acquisition function and returning to the specified process to record the window object when the window service is triggered to acquire the window object.

Preferably, after the triggering module is turned off, the method further comprises:

the window display module is suitable for acquiring a window thumbnail from a corresponding window object according to the corresponding relation between the process information and the window object and displaying the window thumbnail at the designated position of the screen locking interface;

further, the method also comprises the following steps:

the second closing instruction module is suitable for receiving a second closing instruction of the user aiming at the at least one window thumbnail; and when a second closing instruction aiming at least one window thumbnail is received, closing the corresponding process according to the recorded process information.

Preferably, the window intercepting module includes:

the first monitoring module is suitable for monitoring whether to start hatching window service through the first progress incubator;

the first intercepting module is suitable for intercepting the creation of window services if the window services starting hatching are monitored, so that the window services are intercepted from loading the initial window object acquisition function in the android system needing to be called.

Preferably, the function replacing module includes:

the first function replacing module is suitable for replacing an initial window object obtaining function which needs to be loaded by the window service with the first window object obtaining function after the creation of the window service is intercepted;

and the window service creating module is suitable for creating the window service and loading the first window object acquisition function.

the second function replacing module is suitable for replacing the initial getfocuswindow function needing to be loaded by the window service with the first getfocuswindow function; and the return time sequence of the first getfocuscenter function is a return appointed process.

and the first window object acquisition module is suitable for searching the windowstata window object at the top of the window object stack through the first getfocuscindow function.

Preferably, the method further comprises the following steps:

the window object judging module is suitable for judging whether the window object is acquired or not when the window object at the top of the window object stack changes; and if the window object is not acquired, continuing to return the window object to the specified process.

According to the android system application closing method, when an android system hatching (fork) process starts, process information of the process can be acquired, processes within a system necessary range, such as a systemsever process, are basic processes executed by the android system, including a call process and a notification bar process, are not recorded, and process information of APPs can be recorded for other processes except the system necessary process, such as an APP (application) process. After the system is locked, if the user triggers a closing instruction through a function key of the terminal, the necessary process of the system is not closed according to the recorded process information, so that the influence on the normal use of the user caused by the closing of the related process of the system is avoided, and the process except the necessary process of the system can be closed. The method and the device solve the problem that the process outside the non-system-essential range running in the android system cannot be quickly closed after the screen is locked, obtain the process which can be conveniently and quickly closed in the non-system-essential range running in the android system in the screen locking state, and reduce the power consumption of the system.

The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 shows a flowchart of an application shutdown method of an android system according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a method for obtaining a window object of an android system according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a method for obtaining a window object of an android system according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an android system application shutdown device according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an android system application shutdown device according to an embodiment of the present invention;

fig. 6 shows a schematic structural diagram of an application shutdown device of an android system according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

One of the core ideas of the invention is as follows: when an android system hatching (fork) process starts, process information of the process can be obtained, and then it is judged which processes are not essential for the android system (for example, a systemsever process is a basic process executed by the android system, the systemsever also includes a call process, a notification bar process and the like). And then according to a closing instruction triggered by a user, closing the processes according to the recorded process information. The method can conveniently close the process out of the non-system-essential range running in the android system in the screen locking state, and reduces the power consumption of the system.

Example one

Referring to fig. 1, which shows a flowchart of an application shutdown method of an android system in the present invention, including:

step 110, monitoring whether an incubation process is started in an android system;

in the Android system, all application program processes and a system service process SystemServer are hatched by a zygate process (fork), and the method can monitor the hatching process when the zygate process hatches other processes, namely monitor the creation of the processes.

Preferably, the method further comprises the following steps:

substep 100, replacing the initial process incubator of the android system with a specific first process incubator; and monitoring whether the android system starts an incubation process or not through the first process incubator.

In the invention, in order to realize monitoring of a process incubation process, an initial process incubator, namely a zygate process, of an android system needs to be replaced by a specified first process incubator, namely a first zygate process, and the first zygate process can monitor whether an android system starts an incubation process. The method can realize the monitoring and acquiring process by replacing the initial zygate process of the android system with the first zygate process.

Of course, after the initial zygate process of the android system is replaced by the first zygate process, the android system needs to be restarted. The function of the replaced first zygate process includes the function of the android system initial zygate process, and adds various processing logics for monitoring whether the android system starts an incubation process and after monitoring.

Of course, for the android system, the root authority of the system can be obtained in advance in the replacement process, and then the replacement is performed.

Preferably, the monitoring, by the first process incubator, whether the android system starts an incubation process includes:

a substep 112 of creating a java virtual machine by said first process spawner;

and a substep 113, registering a monitoring socket through the java virtual machine, and monitoring whether the android system starts an incubation process through the monitoring socket.

During the normal startup of the android system, approximately: the method comprises the steps that a starting system is read by an init process, the starting init is rc, the init process creates a zygate process, the zygate process creates a java virtual machine to be loaded into a zygate init class, and the virtual machine registers a socket, the ActivityManagerService is waited to write a creating message of a creating process into the socket, and the zygate process creates a corresponding process according to the creating message.

Then, after the initial zygate process of the android system is replaced by the first zygate process specified by the invention in the previous steps, after the android system is restarted, the init process of the android system can create the first zygate process of the android system, then the first zygate process can create a java virtual machine, a monitoring socket is registered, and whether the android system starts an incubation process is monitored through the monitoring socket.

a substep 134, monitoring whether a creation message of an incubation process is received in the socket; if the listening socket receives a create message, it is determined to start an incubation process.

In the embodiment of the present invention, when the android system needs to create a process, the system (for example, activitymanageriarvice) needs to write a creation message for creation into the monitoring socket, and then whether the creation message is received in the monitoring socket is monitored, so that whether the system starts an incubation process can be determined. If the listening socket receives a create message, it is determined to start an incubation process. If the listening socket does not receive a create message, then it indicates that no process needs to be hatched.

Step 120, if the incubation process is started, judging whether the process belongs to a process within a system necessary range; if the process does not belong to the process within the system must scope, go to step 130;

step 130, recording the process information of the process;

in the embodiment of the present invention, the replaced first zygate process further loads a process list, where the process list records processes within a necessary range of the system, such as system processes like a systemsever process, a windowmanager service, and the like, and if the processes are closed, the normal use of the system itself may be affected. For processes outside the process list, such as the processes of APP such as browser and instant messaging, the invention can record the process information, such as the process name. In the embodiment of the invention, the process information can also be returned to the appointed process for recording.

The subsequent steps may then be awaited.

Step 140, judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system; if a close command is received, go to step 150;

after a user installs a system lock screen, if the user wants to close an APP which is started but not closed when the user uses the system lock screen, the user can press preset monitoring on a certain function key, such as a sound key, and press an additional sound key for 3s for a long time in the lock screen state, and then a closing instruction is triggered, and the system needs to enter a step of closing an opened APP process. The preset monitoring for a certain function key can also be executed by setting a monitoring logic through the first zygate process.

Preferably, the step of judging whether a closing instruction triggered by a user is received in the screen locking state of the android system comprises:

a substep 140, receiving the triggering operation of the user to the appointed key in the screen locking state, and judging whether the triggering operation to the appointed key meets the preset rule; and if the triggering operation of the specified key accords with a preset rule, judging that a closing instruction is received.

In the embodiment of the present invention, the replaced first zygate process further loads a predetermined rule logic for triggering the designated key, for example, if the add-sound key 3s is pressed for a long time in the screen-locking state, a close instruction is triggered. Then after the subsequent system is started, the trigger of the sound increasing key in the screen locking state is monitored.

Of course, in the embodiment of the present invention, the user's trigger operation on the designated key may be received after the screen is lighted.

And 150, closing the process according to the recorded process information.

And after the operating system determines that a closing instruction is received, closing the process according to the recorded process information. For example, according to the recorded process information, a killprocess function can be called to close the process.

According to the embodiment of the invention, when an android system hatching (fork) process starts, process information of the process can be acquired, so that processes which are not necessary for the system, such as basic processes executed by an android system, like a systemsever process, and the like, and further such as a call process, a notification bar process and the like, are not recorded, so that the influence on normal use of a user caused by closing of related processes of the system during subsequent closing is avoided, and for other processes except the necessary processes of the system, such as APP processes, the process information of the APP can be recorded. After the system is locked, if the user triggers a closing instruction through a function key of the terminal, closing the process outside the necessary process range of the system according to the recorded process information. The method can conveniently close the process out of the non-system-essential range running in the android system in the screen locking state, and reduces the power consumption of the system.

Example two

Referring to fig. 2, which shows a schematic flow diagram of a method for obtaining a window object of an android system in the present invention, including:

step 210, monitoring whether an incubation process starts in an android system;

step 220, if the hatching process is started, judging whether the process belongs to a process within a system necessary range; if the process does not belong to the process within the system necessary range, recording the process information of the process;

step 230, intercepting the call of the initial window object acquisition function in the android system before the window object acquisition function called by the window service;

in the traditional execution process of the viewer, when the viewer needs to obtain a window object through the viewer, a window object obtaining function needs to be called, after the viewer finishes calling the window object obtaining function to obtain a window object windowstata in a window list stack maintained by a window management service window manager service, the viewer returns to the viewer, and then the viewer transmits all data obtained from the window object through an external socket.

Where Viewserver is a service, which can be understood as a process.

In the embodiment of the present invention, before the viewer calls the window object obtaining function, the call of the initial window object obtaining function in the android system is intercepted, and then step 120 is performed.

In the embodiment of the invention, the initial process incubator of the android system is replaced by the specific first process incubator, and then the first process incubator is used for intercepting the call of the initial window object acquisition function in the android system before the window object acquisition function called by the window service.

a substep 231 of monitoring, by the first process incubator, whether to start an incubation window service;

in the implementation of the present invention, when the initial process incubator of the android system is replaced with a specific first process incubator, that is, the initial process incubator of the android system, that is, the zygate process, is replaced with a specified first zygate process, and the first zygate process may further add logic for monitoring whether to start creating the viewserver, that is, may further monitor whether to start hatching window service through the first process incubator.

Preferably, the monitoring, by the first course incubator, whether to start an incubation window service includes:

substep A2311, creating a java virtual machine through the first process incubator;

this step is the same step as sub-step 112.

Substep A2312, registering a monitoring socket through the java virtual machine, and adding a service logic for judging whether to start hatching window in the monitoring socket so as to judge whether to start hatching process of the android system through the monitoring socket.

This step is performed on the basis of sub-step 113, and adds logic to the listening socket to determine whether to begin hatching window services.

During the normal startup of the android system, approximately: the method comprises the steps that a starting system is read by an init process, the starting init is rc, the init process creates a zygate process, the zygate process creates a java virtual machine to be loaded into a zygate init class, and the virtual machine socket is enabled to wait for ActiviyManagerService to write creating information of a creating process into the socket, and the zygate process creates a corresponding process according to the creating information.

Then, in the invention, after the initial zygate process of the android system is replaced by the first zygate process specified by the invention in the aforementioned steps, after the android system is restarted, the init process of the android system can create the first zygate process of the invention, then the first zygate process can create a java virtual machine, and register a monitoring socket through the java virtual machine, wherein the monitoring socket of the invention not only monitors the logic of whether each process starts hatching, but also further has monitoring logic for the specific process of the viewserver.

substep a215, monitoring whether a first message of hatching window service is received in the socket; determining to start hatching window service if the socket receives a first message of hatching window service.

In the embodiment of the present invention, the registered socket listens for a received message in the socket. When the android system needs to create a process, the system needs to send a first message for creating the viewserver to the socket, and then whether the first message for hatching window service is received in the socket is monitored, so that whether the system starts to create the viewserver can be judged. Determining to start hatching window service if the socket receives a first message of hatching window service. If the socket does not receive the first message of the hatching window service, the system does not have the hatching window service.

And a substep 232, if the window service for starting hatching is monitored, intercepting the creation of the window service, so as to intercept the loading of the window service on an initial window object acquisition function in the android system which needs to be called.

Then the embodiment of the invention intercepts the creation of the viewserver after monitoring the start of the creation of the viewserver. In the embodiment of the present invention, the process of intercepting the creation of the viewserver is intercepting the loading of the viewserver on the function which needs to be called, for example, intercepting the loading of the viewserver on the window object which needs to be called by the window object acquisition function.

Step 240, replacing the intercepted initial window object obtaining function with a first window object obtaining function;

in the embodiment of the invention, the intercepted initial window object acquisition function is replaced by the own first window object acquisition function, namely the first window object acquisition function; in the embodiment of the present invention, the function and interface of the first window object obtaining function are consistent with the function and interface of the window object obtaining function of the android system, and both the function and interface of the first window object obtaining function and the function and interface of the first window object obtaining function can be used for obtaining the windows stata from the window object list stack maintained by the windows manager service.

Preferably, replacing the intercepting window object obtaining function with a first window object obtaining function includes:

substep 241, after intercepting the creation of the window service, replacing the initial window object obtaining function which needs to be loaded by the window service with the first window object obtaining function;

in this embodiment of the present invention, when the initial zygate process of the replacement android system is the first zygate process of the present invention, in the process of replacing the initial zygate class with the modified zygate class of the present invention, in the modified zygate class, a first window object obtaining function required by the present invention is also added, a process of the first window object obtaining function before obtaining the windowsta is consistent with an original window object obtaining function of the android system, and only a return timing sequence of the first window object obtaining function after obtaining the windowsta is changed to a direct return specified process.

Substep 242, creating the window service and loading the first window object acquisition function.

After the initial window object obtaining function of the android system is replaced by the first window object obtaining function of the invention, the process of creating the viewserver can be continuously executed, and the required functions are loaded after the creation, wherein the required functions comprise the first window object obtaining function.

Step 250, when a window service is triggered to acquire a window object, the window service acquires the window object by calling the first window object acquisition function and returns to an appointed process to record the window object;

after the intercepted initial window object obtaining function is replaced by the first window object obtaining function of the invention, the calling of the viewserver is continuously executed, the called window object obtaining function is the first window object obtaining function of the invention, the object returned after the first window object obtaining function obtains the windowsta is changed into the appointed process appointed by the embodiment of the invention, and then the information of each windowsta can be recorded through the appointed process.

When the viewer calls the first window object acquisition function to acquire the windowsta from the window list stack maintained by the windows manager service, the windowsta can directly return to the specified process of the android system through a pipe of pipe between the viewer and the specified process.

Step 260, judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system; if a close command is received, go to step 270;

step 270, acquiring a window thumbnail from the corresponding window object according to the corresponding relation between the process information and the window object, and displaying the window thumbnail at the designated position of the screen locking interface;

in the embodiment of the present invention, the windows stata corresponding to the recorded process information may be acquired from the windows stata recorded in the designated process, and then corresponding window thumbnails may be generated based on the window messages in these windows stata.

Step 280, receiving a second closing instruction of the user aiming at least one window thumbnail;

and 290, when a second closing instruction for at least one window thumbnail is received, closing the corresponding process according to the recorded process information.

For example, A, B, C is available for app processes running in the current system memory, after the window thumbnail of A, B, C is displayed in step 280, the user may select to close all app processes or to close a certain app process, and then after selection, the process information of the selected app process may be searched according to the recorded process information, and a close function is invoked to close the corresponding app process.

Preferably, the method further comprises the following steps:

step 292, when the window object at the top of the window object stack changes, determining whether the window object has been acquired;

step 294, if the window object is not obtained, continuing to return the window object to the designated process.

In the embodiment of the present invention, because the first getfocuscindow function is the obtained windowsta of the stack top, and the windowsta of the stack top represents the window object currently shown or activated for the application, other window objects in the background may be at a position below the stack top. According to the embodiment of the invention, the changed windows can be obtained as long as the windows at the top of the stack are changed, namely the app currently displayed by the android system is changed.

The method can continuously acquire the windows at the top of the stack, records the acquired windows, and does not need to acquire the windows if the windows at the top of the stack are not changed according to the records when the windows are acquired next time, and continues to return the window objects to the specified process if the windows at the top of the stack are changed.

The embodiment of the invention can record the process information and simultaneously record the window object corresponding to the process, and can display the corresponding window information according to the recorded process in the screen locking state, thereby facilitating the user to control which processes are closed. The method has the advantages that the user can conveniently close processes which run in the android system and are out of the range of the non-system necessity in the screen locking state, and the power consumption of the system is reduced.

EXAMPLE III

Referring to fig. 3, which shows a schematic flow diagram of a method for obtaining a window object of an android system in the present invention, including:

step 310, replacing an initial process incubator of the android system with a specific first process incubator;

replacing the initial zygate process of the android system with a first zygate process preset by the invention; the functionality of the first zygate process, in addition to the functionality of the initial zygate process, adds processing logic to listen whether to start listening whether the android system starts the hatching process and hatching window service and after listening. After the replacement, the system may be restarted, starting the initial init process of the system.

Step 312, creating a java virtual machine through the first process incubator;

step 314, registering a monitoring socket through the java virtual machine, so as to monitor whether the android system starts an incubation process and further monitor whether the android system starts an incubation window service through the monitoring socket; if the android system is monitored to start the hatching process, the step 316 is carried out; if the android system is monitored to start hatching window service, step 322 is entered;

step 316, judging whether the process belongs to a process within a system necessary range; if the process does not belong to a process within the system must scope, go to step 318;

step 318, recording the process information of the process;

step 322, intercepting the creation of the window service, thereby intercepting the loading of the getfocuscondow function which needs to be called by the window service;

step 324, after the creation of the window service is intercepted, replacing the initial getfocusdrive function which needs to be loaded by the window service with a first getfocusdrive function; the return time sequence of the first getfocuscenter function is a return designated process;

the first getfocuswindow function of the invention has the same parameter setting as the original getfocuswindow function in the android system, and only the return object of the original getfocuswindow function of the system is modified to be the designated process of the invention.

Step 326, creating the window service and loading the first getfocuscenter function;

after the function is replaced, the process hatching process can continue to be executed, the first zygate process can continue to create the viewserver, and the relevant parameters of the first getfocuscenter function are loaded after the creation.

Step 328, the window service searches for a windowsta window object at the top of the window object stack through the first getfocuscindow function, and returns the windowsta window object to the specified process to process the record of the window object;

after the foregoing steps, when the window service executes to acquire the window object, the first getfocuscindow function may be called to acquire the windowsta at the top of the stack from the stack storing the window object, and then the windowsta may be returned to the designated process through the pipe between the viewer and the designated process. Of course the pipe of pipe between the viewserver and the specified process can be built at the time of use.

In the embodiment of the present invention, when any app is opened, the corresponding windows sta is at the top of the stack, and then the windows stas of all opened apps can be recorded through the above steps.

Step 330, judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system; if a close command is received, go to step 332;

step 332, acquiring a window thumbnail from the corresponding window object according to the corresponding relation between the process information and the window object, and displaying the window thumbnail at the designated position of the screen locking interface;

step 334, receiving a second closing instruction of the user for the at least one window thumbnail;

and 336, when receiving a second closing instruction aiming at least one window thumbnail, closing the corresponding process according to the recorded process information.

Example four

Referring to fig. 4, which shows a schematic structural diagram of an application shutdown device of an android system in the present invention, including:

a process creation monitoring module 410 adapted to monitor whether an incubation process starts in the android system;

a process information recording module 420 adapted to determine if the incubation process is initiated if the process is within a system-required range; if the process does not belong to the process within the system necessary range, recording the process information of the process;

the closing triggering module 430 is suitable for judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system;

a process closing module 440, adapted to close the process according to the recorded process information if a closing instruction is received.

Preferably, the method further comprises the following steps:

Preferably, the process creation monitoring module includes:

Preferably, the shutdown triggering module includes:

EXAMPLE five

Referring to fig. 5, which shows a schematic structural diagram of an application shutdown device of an android system in the present invention, including:

a process creation monitoring module 510 adapted to monitor whether an incubation process starts in the android system;

a process information recording module 520 adapted to determine if the incubation process is initiated if the process is within a system-required range; if the process does not belong to the process within the system necessary range, recording the process information of the process;

a window interception module 530, adapted to intercept the call of the initial window object acquisition function in the android system before the window object acquisition function called by the window service;

a function replacing module 540, adapted to replace the intercepted initial window object obtaining function with a first window object obtaining function;

the window obtaining module 550 is adapted to, when the window service is triggered to obtain the window object, obtain the window object by invoking the first window object obtaining function and return to the designated process to perform window object recording.

A closing triggering module 560, adapted to determine whether a closing instruction triggered by a user is received in the screen locking state of the android system; enter the window presentation module 570;

the window display module 570 is adapted to obtain a window thumbnail from a corresponding window object according to the corresponding relationship between the process information and the window object, and display the window thumbnail at an appointed position of the screen locking interface;

a second close instruction module 580 adapted to receive a second close instruction of the user for the at least one window thumbnail;

the process closing module 590 is adapted to close the corresponding process according to the recorded process information when receiving a second closing instruction for the at least one window thumbnail.

Preferably, the window intercepting module includes:

Preferably, the function replacing module includes:

Preferably, the first process incubator listens whether to start creating a window service.

Preferably, whether to start creating the window service is monitored through the monitoring socket.

Preferably, the window intercepting module includes:

the system comprises a creating message monitoring module, a window creating service processing module and a window creating service processing module, wherein the creating message monitoring module is suitable for monitoring whether a first message for creating a window service is received in the socket; determining to start creating a window service if the socket receives a first message to create a window service.

EXAMPLE six

Referring to fig. 6, which shows a schematic structural diagram of an application shutdown device of an android system in the present invention, including:

a process incubator replacement module 610 adapted to replace an android system initial process incubator with a specific first process incubator;

a virtual machine creation module 612 adapted to create a java virtual machine through the first process spawner;

a first window service creation monitoring module 614, adapted to register a monitoring socket through the java virtual machine, to monitor whether the android system starts an incubation process through the monitoring socket, and further monitor whether the android system starts an incubation window service; if the android system is monitored to start the hatching process, entering a process judgment module 616; if the android system is monitored to start hatching window service, the second interception module 622 is entered;

a process determination module 616 adapted to determine, if an incubation process is started, whether the process belongs to a process within a system must range; if the process does not belong to the process within the range of the system requirement, entering a process recording module 618;

a process recording module 618 adapted to record process information of the process;

the second intercepting module 622, intercepting the creation of the window service, so as to intercept the loading of the getfocuscenter function which the window service needs to call;

a second function replacing module 624, adapted to replace the initial getfocuswindow function that needs to be loaded by the window service with the first getfocuswindow function; the return time sequence of the first getfocuscenter function is a return designated process;

a window service creation module 626 adapted to create the window service and load the first getfocuscenter function;

a first window object obtaining module 628, adapted to find a windows object at the top of the window object stack by the window service through the first getfocuscindow function, and return the windows object to the specified process;

through the record of the modules, data support can be provided for closing the APP process in the screen locking state subsequently.

A closing triggering module 630, adapted to determine whether a closing instruction triggered by a user is received in the screen locking state of the android system; an entry window presentation module 632;

the window display module 632 is adapted to obtain a window thumbnail from a corresponding window object according to the corresponding relationship between the process information and the window object, and display the window thumbnail at an assigned position of the lock screen interface;

a second close instruction module 634 adapted to receive a second close instruction of the user for the at least one window thumbnail;

and a process closing module 636, adapted to close the corresponding process according to the recorded process information when receiving a second closing instruction for at least one window thumbnail.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in an android system application shutdown device in accordance with embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

A1, an android system application closing method, comprising:

monitoring whether an incubation process is started in the android system;

A2, the method of a1, further comprising:

A3, the method of a2, wherein the monitoring, by the first course incubator, whether the android system starts an incubation course comprises:

creating a java virtual machine through the first process incubator;

A4, the method of A3, the listening, via the socket, whether to start hatching window service, comprising:

A5, the method as in a1, where the determining whether a close instruction triggered by a user is received in the android system screen lock state includes:

A6, the method of a2, further comprising:

A7, the method as in a6, further comprising, after receiving the close command:

further, the method also comprises the following steps:

A8, the method as in a6, wherein intercepting a call to an initial window object obtaining function in the android system before a window object obtaining function called by a window service comprises:

A9, the method of A6, wherein replacing the intercepting window object capture function with a first window object capture function comprises:

A10, the method of A9, wherein the replacing the initial window object get function that the window service needs to load with the first window object get function includes:

A11, the method of A10, the window service obtaining a window object by calling the first window object obtaining function comprising:

A12, the method of a10, further comprising:

The invention also provides B13 and an android system application closing device, which comprises:

B14, the apparatus of B13, further comprising:

B15, the apparatus as described in B14, the process creating listening module comprising:

B16, the apparatus as described in B15, the process creating listening module comprising:

B17, the apparatus as in B13, the close trigger module comprising:

B18, the apparatus of B14, further comprising:

The apparatus of B19, as stated in B18, after closing the trigger module, further includes:

further, the method also comprises the following steps:

B20, the apparatus of B18, the window intercepting module comprising:

B21, the apparatus as described in B18, the function replacement module comprising:

B22, the apparatus as in B21, the replacing the initial window object get function that the window service needs to load with the first window object get function includes:

B23, the apparatus as in B22, the window service obtaining the window object by calling the first window object obtaining function comprises:

B24, the apparatus of B23, further comprising:

Claims

1. An android system application closing method comprises the following steps:

monitoring whether an incubation process is started in the android system;

if a closing instruction is received, closing the process which does not belong to the system necessary range according to the recorded process information;

the method further comprises the following steps:

replacing the initial process incubator of the android system with a specific first process incubator; monitoring whether the android system starts an incubation process or not through the first process incubator;

judging whether a closing instruction triggered by a user is received or not in the screen locking state of the android system comprises the following steps:

receiving a trigger operation of a user on an appointed key in a screen locking state, and judging whether the trigger operation on the appointed key meets a preset rule or not; if the triggering operation of the appointed key accords with a preset rule, judging that a closing instruction is received; the appointed key is a sound key.

2. The method of claim 1, wherein said listening, by said first course incubator, whether an android system begins an incubation course comprises:

creating a java virtual machine through the first process incubator;

3. The method of claim 2, wherein said listening through said socket whether to initiate hatching window services comprises:

4. The method of claim 1, further comprising:

5. The method of claim 4, after receiving a close command, further comprising:

further, the method also comprises the following steps:

6. The method of claim 4, wherein intercepting a call to an initial window object acquisition function in the android system prior to a window object acquisition function called by a window service comprises:

7. The method of claim 4, wherein replacing the intercepting window object acquisition function with a first window object acquisition function comprises:

8. The method of claim 7, wherein replacing the initial window object acquisition function that the window service needs to load with the first window object acquisition function comprises:

9. The method of claim 8, wherein the window service obtaining a window object by calling the first window object obtaining function comprises:

10. The method of claim 8, further comprising:

11. An android system application shutdown device, comprising:

the process closing module is suitable for closing the process which does not belong to the system necessary range according to the recorded process information if a closing instruction is received;

the process incubator replacing module is suitable for replacing the initial process incubator of the android system with a specific first process incubator; monitoring whether the android system starts an incubation process or not through the first process incubator;

wherein the shutdown trigger module comprises:

the first closing triggering module is suitable for receiving the triggering operation of a user on an appointed key in a screen locking state and judging whether the triggering operation on the appointed key meets a preset rule or not; if the triggering operation of the appointed key accords with a preset rule, judging that a closing instruction is received; the appointed key is a sound key.

12. The apparatus of claim 11, wherein the process creation listening module comprises:

13. The apparatus of claim 12, wherein the process creation listening module comprises:

14. The apparatus of claim 11, further comprising:

15. The apparatus of claim 14, further comprising, after closing the trigger module:

further, the method also comprises the following steps:

16. The apparatus of claim 14, wherein the window intercepting module comprises:

17. The apparatus of claim 14, wherein the function replacement module comprises:

18. The apparatus of claim 17, wherein replacing the initial window object acquisition function that the window service needs to load with the first window object acquisition function comprises:

19. The apparatus of claim 18, wherein the window service obtaining a window object by calling the first window object obtaining function comprises:

20. The apparatus of claim 19, further comprising: