CN109800567B - Method and device for monitoring foreground application starting and terminal equipment - Google Patents

Abstract

Embodiments of the present invention relate to the technical field of data processing, and disclose a method, a device, and a terminal device for monitoring the startup of a foreground application. In the present invention, the process directory of the system is scanned in a preset period; according to the scanned process directory, it is judged whether there is a new process, and if so, the application package name corresponding to the process is obtained; Whether the application package names obtained by the system auxiliary function callback are the same, if so, it is determined that a foreground application is started. At the same time, the monitoring results of the system process directory and the system callback are considered to make the final judgment result more accurate. In addition, since the system process directory has nothing to do with the Android system version, and the current Android version basically supports the callback function of the system auxiliary function, the compatibility of this solution is good.

Description

Method and device for monitoring foreground application startup, and terminal device

technical field

The embodiments of the present invention relate to the technical field of data processing, and in particular, to a method for monitoring the startup of a foreground application.

Background technique

With the development of Internet technology, in recent years, more and more terminal devices are equipped with the Android system. On the Android system, various programs can be installed to meet people's individual needs. When implementing certain functions, such as the function of placing pictures when the user opens an application interface, the system needs to monitor the startup of the foreground application.

The inventors found that at least the following problems exist in the prior art:

The method of monitoring the startup of the foreground application in the prior art has low accuracy and poor compatibility.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present invention is to provide a method, apparatus and terminal device for monitoring the startup of a foreground application, so that the monitoring accuracy of the startup of the foreground application is high and the compatibility is good.

In order to solve the above technical problems, embodiments of the present invention provide a method for monitoring the startup of a foreground application, including the following steps:

Scan the process directory of the system with a preset cycle; determine whether there is a new process according to the scanned process directory, and if so, obtain the application package name corresponding to the process; determine the application package name and the system auxiliary function callback Whether the obtained application package names are the same, if so, it is determined that a foreground application is started.

Embodiments of the present invention also provide a terminal device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores data that can be executed by the at least one processor The instruction is executed by the at least one processor, so that the at least one processor can execute the above-mentioned method for monitoring the startup of a foreground application.

An embodiment of the present invention also provides a device for monitoring the startup of a foreground application, including: a scanning module, used for scanning the process directory of the system at a preset period; a first judgment module, used for judging whether there is a new The added process; the obtaining module is used to obtain the application package name corresponding to the process when the judgment module determines that there is a newly added process; the second judgment module is used to judge whether the application package name and the application package name obtained by the system auxiliary function callback are not The same, if so, it is determined that a foreground application is started.

Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the above-mentioned method for monitoring the startup of a foreground application is implemented.

Compared with the prior art, the embodiment of the present invention can obtain the latest status of the process directory of the system in time by scanning the process directory of the system at a preset period; when it is determined that a new process is started according to the scanned process directory , obtain the application package name corresponding to the process to know which application process is being started; determine whether the application package name is the same as the application package name obtained by the system auxiliary function callback, and if so, determine that a foreground application is started. At the same time, the monitoring results of the system process directory and the system callback are considered to make the final judgment result more accurate. In addition, since the system process directory has nothing to do with the Android system version, and the current Android version basically supports the callback function of the system auxiliary function, the compatibility of this solution is good.

In addition, after acquiring the application package name corresponding to the process, the method further includes: loading the content to be delivered; after determining that a foreground application is started, the method further includes: delivering the content to be delivered to the interface of the started foreground application. Since the speed of scanning the process directory of the system to obtain the application package name is usually faster than the speed of the application package name obtained by the system auxiliary function callback, loading the delivery content after obtaining the application package name of the process can make the content to be delivered ready in advance. After a foreground application is started, it can be delivered immediately, and there is no need to wait until it is determined that a foreground application is started before loading the content to be delivered, which improves the delivery speed of the content and improves the user experience.

In addition, before loading the content to be delivered, the method further includes: judging whether the newly added process is a newly added process under a preset application scenario; if it is a newly added process under a preset application scenario, then executing the loading of the content to be delivered. Content delivery is only performed for newly added processes in preset scenarios, which can limit the scenarios in which content is delivered and ensure user experience.

In addition, the above-mentioned determining whether there is a new process according to the scanned process directory is specifically: determining whether there is a new main process according to the scanned process directory; if there is a new main process, it is determined that there is a new process. Since the same application may create multiple processes, in a specific application, only monitoring the main process can reduce the workload of the system and improve the calculation speed.

In addition, the above-mentioned judging whether there is a newly-added process specifically includes: judging whether there is a newly created folder in the process directory, and if so, judging that there is a newly-added process. Provides a specific method for judging whether there is a new process. Since the system will save the process information in the process directory, as long as it is detected that there is a newly created process folder in the process directory, it can be determined that there is a new process. process, by judging whether there is a newly created process folder to determine whether there is a new process, the judgment result is accurate and fast.

In addition, the above-mentioned determining whether there is a new process according to the scanned process directory is specifically: determining whether there is a new non-system process according to the scanned process directory; if there is a new non-system process, obtain the application package corresponding to the process. name. Obtain only the application package name corresponding to the non-system process, that is, filter out the system process and not monitor the system process.

In addition, before judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, the method further includes: judging whether the application package name is an application package name representing the application being started in the process, and if so, shortening the scanning system process directory until the real application package name of the process is obtained; determine whether the application package name is the same as the application package name obtained by the system auxiliary function callback, specifically: judging whether the real application package name is the same as the application package name obtained by the system auxiliary function callback . Since when the application is being started, the scanning process directory gets the application package name that identifies the application being started, not the real application package name of the application. Period, so that after the application is started, the real application package name can be obtained as soon as possible; by judging whether the real application package name and the application package name obtained by the system auxiliary function callback are the same, the accuracy of the judgment result is guaranteed.

In addition, after obtaining the application package name corresponding to the process, the method further includes: judging whether the application package name is the target application package name, and if so, forcibly ending the process and notifying the user to uninstall. In practical applications, the terminal device may have downloaded rogue applications or malicious software. When monitoring the application package names of these target application package names, if the application is allowed to start, it will cause a very bad user experience and user information security. There is no guarantee, therefore, forcibly ending the process and notifying the user to uninstall can ensure the safety of user information.

Description of drawings

1 is a flowchart of a method for monitoring foreground application startup provided according to a first embodiment of the present invention;

2 is a flowchart of a method for monitoring foreground application startup provided according to a second embodiment of the present invention;

3 is a flowchart of a method for monitoring foreground application startup provided according to a third embodiment of the present invention;

4 is a flowchart of a method for monitoring foreground application startup provided according to a fourth embodiment of the present invention;

5 is a schematic structural diagram of an apparatus for monitoring the startup of a foreground application provided according to a fifth embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a terminal device provided according to a sixth embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can appreciate that, in the various embodiments of the present invention, many technical details are set forth in order for the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present invention, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The first embodiment of the present invention relates to a method for monitoring the startup of a foreground application. In this implementation manner, the process directory of the system is scanned at a preset period; it is judged whether there is a new process, and if so, the application package name corresponding to the process is obtained; Whether the application package names are the same, if so, it is determined that a foreground application is started. By simultaneously monitoring the newly added process in the process directory of the system and the callback of the system auxiliary function, the final judgment result can be made with high accuracy and good compatibility. The method for monitoring the startup of a foreground application in this embodiment is shown in FIG. 1 , and the implementation details of the method for monitoring the startup of a foreground application in this embodiment are described in detail below. The following content is only provided for the convenience of understanding. program must.

Step 101: Scan the process directory of the system at a preset cycle.

Specifically, the Linux system kernel will save process information in the /proc directory, and scan the system's process directory at a preset cycle, that is, create a service and start a thread to scan the system's /proc directory at a preset cycle. Further, in this embodiment, the scanning period used is 150ms, on the one hand, the status of the newly started process can be obtained in time, and on the other hand, the problem of excessive consumption of system resources caused by too short scanning time interval is avoided, That is to say, system resources can be effectively saved while acquiring the newly started process in time.

Step 102 : Determine whether there is a new process according to the scanned process directory, if the determination result is yes, execute Step 103 , otherwise return to Step 101 .

Specifically, to determine whether there is a new process, that is, to determine whether there is a new process folder in the process directory, the /proc directory contains many subdirectories named with numbers, and these numbers represent the process number of the currently running process in the system. , which contains multiple information files related to the corresponding process. The process folder here refers to the subdirectory named by the number. If there is a new process folder, that is, there is a new subdirectory named by the number, which can be determined There are new processes. By judging whether there is a newly created process folder to determine whether there is a new process, the judgment result is accurate and fast.

In addition, in the specific implementation, it is determined whether there is a newly added process according to the scanned process directory, specifically: determining whether there is a newly added main process according to the scanned process directory; if there is a newly added main process, it is determined that there is a newly added process. process. Since the same application may create multiple processes, in practical applications, only monitoring the main process can reduce the workload of the system and improve the computing speed.

In addition, when the user opens some system applications (for example, when the camera is turned on), he does not want the content to appear. Therefore, when scanning the /proc directory of the system and reading the process attributes, the processes belonging to the system applications can be filtered out. Determine whether there are new non-system processes. In actual implementation, processes with user IDs between 1000 and 9999 in the process attributes will be filtered out (processes with user IDs between 1000 and 9999 are system processes). Add a process, that is, only determine whether there is a new non-system process.

Step 103: Obtain the application package name corresponding to the process.

Specifically, the application package name corresponding to the process can be obtained by reading the process attribute.

Step 104 : judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, if the judgment result is yes, go to step 105 , otherwise return to step 101 .

Specifically, because the Android system provides the functional service AccessibilityService, when the application starts, the AccessibilityService is called back so that the application package name of the application can be obtained, and it can be judged whether the application package name corresponding to the process is the same as the application package name obtained by the system auxiliary function callback. , if the same, go to step 105.

Step 105: It is determined that a foreground application is started.

Specifically, when it is detected that the application package name corresponding to the newly added process is the same as the application package name obtained by the system auxiliary function callback, that is, the application package name obtained by the two methods is the same, at this time, it can be determined that a foreground application is started.

In specific implementation, the method adopted in this embodiment can be configured as an application program of the system, so as to have higher authority such as self-starting and monitoring the startup of other applications. That is to say, the present embodiment can be implemented by configuring the apk file and placing the configured apk file in the system/app directory.

Compared with the prior art, in this embodiment, by scanning the process directory of the system at a preset period, the latest status of the process directory of the system can be obtained in time; when it is determined that a new process is started, the application package name corresponding to the process is obtained. It can know which application process is starting; judge whether the application package name is the same as the application package name obtained by the system auxiliary function callback, and if so, it is judged that a foreground application is started. At the same time, the monitoring results of the system process directory and the system callback are considered to make the final judgment result more accurate. In addition, since the system process directory has nothing to do with the Android system version, and the current Android version basically supports the callback function of the system auxiliary function, the compatibility of this solution is good.

The second embodiment of the present invention relates to a method for monitoring the startup of a foreground application. The second embodiment is roughly the same as the first embodiment, and the main difference is that: in this embodiment, not only the startup of the foreground application can be monitored, but also Serving content in the foreground application interface. The flowchart of this embodiment is shown in FIG. 2 and will be described in detail below.

Step 201: Scan the process directory of the system at a preset cycle.

Step 202 : Determine whether there is a new process according to the scanned process directory, if the determination result is yes, execute Step 203 ; otherwise, return to Step 201 .

Step 203: Obtain the application package name corresponding to the process.

Steps 201 to 203 are substantially the same as steps 201 to 203 in the first embodiment, and to avoid repetition, they will not be repeated here.

Step 204: Load the content to be delivered.

Specifically, after monitoring that a new process is started, the system can load the corresponding content with delivery according to the acquired application package name, such as loading pictures and videos to be delivered. In a specific implementation, an advertisement delivery provider may also use the method provided by this embodiment to deliver advertisements, that is, the content to be loaded is the advertisement to be delivered.

Step 205 : judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, if the judgment result is yes, execute step 206 , otherwise return to step 201 .

Step 206: It is determined that a foreground application is started.

Steps 205 and 206 are substantially the same as steps 104 and 105 in the first embodiment, and to avoid repetition, they will not be repeated here.

Step 207: Put the content to be put on the interface of the activated foreground application.

Specifically, after it is determined that a foreground application is started, the loaded content to be delivered can be delivered to the foreground application interface.

In a specific example, before loading the content to be delivered, it is first determined whether the newly added process is a newly added process under the preset application scenario; if it is a newly added process under the preset application scenario, then the loading pending process is executed Deliver content. Content delivery is only performed for newly added processes in the preset scenario, and the scenarios in which the content is delivered can be restricted. The preset scenario may be the current interface of the application store interface or the system launcher interface, etc. Here, the application store is used as an example. Since the apps opened from the app store are all apps downloaded from the app store, generally not system apps, it is limited to monitor only when the current app interface is the app store interface, which can limit the scope of monitored apps. Specifically, the AccessibilityService, an accessibility service provided by the Android system, can be used to monitor the application package name returned by this callback by registering the observer mode, to determine the current foreground application package name, and to determine whether the returned application package name is specified. , and if so, start loading with serving content. In the preset application scenario, the content of pictures and videos waiting to be loaded can be placed on the newly launched application, which can limit the scope of the content to be placed and ensure the user experience. In addition, if the content to be delivered is an advertisement, by designing a preset application scenario, the advertisement is loaded and delivered only in the preset application scenario, which can minimize the disturbance to the user's normal use of other applications and ensure the user experience.

Compared with the prior art, in this embodiment, the speed of scanning the process directory of the system to obtain the application package name is usually faster than the speed of obtaining the application package name obtained by the system auxiliary function callback. The content to be delivered is prepared in advance, and can be delivered immediately after it is determined that a foreground application is started, without waiting until it is determined that a foreground application is started before loading the content to be delivered, which improves the delivery speed of the content and improves the user experience.

The third embodiment of the present invention relates to a method for monitoring the startup of a foreground application. The third embodiment is substantially the same as the first embodiment, and the main difference is that: in the third embodiment of the present invention, a specific method for obtaining an application package name corresponding to a process is provided. The flowchart of this embodiment is shown in FIG. 3 and will be described in detail below.

Step 301: Scan the process directory of the system at a preset cycle.

Step 302 : Determine whether there is a new process according to the scanned process directory, if the determination result is yes, go to Step 303 , otherwise return to Step 301 .

Step 303: Obtain the application package name corresponding to the process.

Steps 301 to 303 are substantially the same as steps 101 to 103 in the first embodiment, and to avoid repetition, they will not be repeated here.

Step 304: Determine whether the application package name is an application package name representing the application being started in the process, if so, go to step 307, otherwise go to step 305.

Specifically, the name of the application package representing the application being started is usually pre-initialized, that is, if the name of the application package corresponding to the process obtained in step 303 is pre-initialized, then step 307 is performed, otherwise, step 307 is performed. 305.

Step 305: Determine whether the application package name is the same as the application package name obtained by the system auxiliary function callback. If the determination result is yes, then step 306 is executed, otherwise, the process ends.

Step 306: It is determined that a foreground application is started.

Step 306 is substantially the same as step 105 in the first embodiment, and to avoid repetition, details are not repeated here.

Step 307: Shorten the period of scanning the system catalog.

That is to say, in this embodiment, it is determined whether the real application package name of the process is the same as the application package name obtained by the system auxiliary function callback. Before judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, first determine whether the application package name is pre-initialized. If so, shorten the cycle of scanning the system process directory, for example, shorten it from 150ms to 10ms, until the acquisition The real application package name of the process; determine whether the real application package name is the same as the application package name obtained by the system auxiliary function callback.

Compared with the prior art, in this embodiment, when the application is being started, what is obtained by scanning the process directory is the application package name that identifies the application being started, not the real application package name of the application. , shorten the cycle of scanning the process directory of the system, so that after the application is started, the real application package name can be obtained as soon as possible; by judging whether the real application package name and the application package name obtained by the system auxiliary function callback are the same, the judgment result is guaranteed. accuracy.

The fourth embodiment of the present invention relates to a method for monitoring the startup of a foreground application. The fourth embodiment is substantially the same as the first embodiment, and the main difference is that: in this embodiment, when the application package name is the target application package name , which will force the process to end. The flowchart of this embodiment is shown in FIG. 4 and will be described in detail below.

Step 401: Scan the process directory of the system at a preset cycle.

Step 402 : Determine whether there is a new process according to the scanned process directory, if the determination result is yes, execute Step 403 , otherwise, return to Step 401 .

Step 403: Obtain the application package name corresponding to the process.

Steps 401 to 403 are substantially the same as steps 101 to 103 in the first embodiment, and to avoid repetition, they will not be repeated here.

Step 404: Determine whether the application package name is the target application package name, if yes, go to step 407, otherwise go to step 405.

Specifically, in practical applications, the terminal device may have downloaded rogue applications or malicious software. When listening to the application package names of these target application package names, if the application is allowed to start, it will cause a very bad user experience. Information security is also not guaranteed. Therefore, the application registration corresponding to some known rogue applications or malware can be set as the target application package name in advance. And notify the user to uninstall the application to ensure the user experience.

Step 405 : judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, if the judgment result is yes, execute step 405 ; otherwise, return to step 401 .

Step 406: It is determined that a foreground application is started.

Steps 405 to 406 are substantially the same as steps 104 to 105 in the first embodiment, and to avoid repetition, they will not be repeated here.

Step 407: Forcibly end the process, and notify the user to uninstall.

Specifically, the kill instruction can be used to kill the process of the malicious application, and remind the user that the application is a malicious application, and notify the user to uninstall it.

Compared with the prior art, in this implementation manner, in actual applications, the terminal device may download rogue applications or malicious software. Bad user experience and user information security cannot be guaranteed. Therefore, forcibly ending the process and notifying the user to uninstall can ensure user information security.

The steps of the above various methods are divided only for the purpose of describing clearly. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as the same logical relationship is included, they are all within the protection scope of this patent. ;Adding insignificant modifications to the algorithm or process or introducing insignificant designs, but not changing the core design of the algorithm and process are all within the scope of protection of this patent.

The fifth embodiment of the present invention relates to a device for monitoring the startup of a foreground application, as shown in FIG. 5 , including:

The scanning module 501 is used to scan the process directory of the system with a preset cycle;

The first judging module 502 is used for judging whether there is a new process according to the scanned process directory;

The obtaining module 503 is configured to obtain the application package name corresponding to the process when the judging module determines that there is a newly added process;

The second judging module 504 is configured to judge whether the application package name is the same as the application package name obtained by the system auxiliary function callback, and if so, judge that a foreground application is started.

In one example, after acquiring the application package name corresponding to the process, the method further includes: loading the content to be delivered; after determining that a foreground application is started, the method further includes: delivering the content to be delivered to the interface of the started foreground application.

In one example, before scanning the process directory of the system at a preset cycle, the method further includes: judging whether the current foreground application is a preset application, and if so, scanning the process directory of the system at a preset cycle.

In an example, it is determined whether there is a new process according to the scanned process directory, specifically: determining whether there is a new main process according to the scanned process directory; if there is a new main process, it is determined that there is a new process .

In one example, determining whether there is a newly added process is specifically: determining whether there is a newly added process folder in the process directory, and if so, determining that there is a newly added process.

In an example, before judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, the method further includes: judging whether the application package name is an application package name representing the application being started in the process, and if so, shortening the scanning system The cycle of the process directory until the real application package name is obtained; determine whether the application package name is the same as the application package name obtained by the system auxiliary function callback, specifically: judging whether the real application package name and the application package name obtained by the system auxiliary function callback are not same.

In one example, after acquiring the application package name corresponding to the process, the method further includes: judging whether the application package name is the target application package name, and if so, forcibly ending the process and notifying the user to uninstall.

It is not difficult to find that this embodiment is a system example corresponding to the first embodiment to the third embodiment, and this embodiment can be implemented in cooperation with the first embodiment to the third embodiment. The related technical details mentioned in the first embodiment to the third embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied to the first embodiment to the third embodiment.

It is worth mentioning that each module involved in this embodiment is a logical module. In practical applications, a logical unit may be a physical unit, a part of a physical unit, or multiple physical units. A composite implementation of the unit. In addition, in order to highlight the innovative part of the present invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other units in this embodiment.

The sixth embodiment of the present invention relates to a terminal device, as shown in FIG. 6 , including at least one processor 601; and,

a memory 602 in communication with the at least one processor 601; wherein,

The memory 602 stores instructions executable by the at least one processor 601, and the instructions are executed by the at least one processor 601, so that the at least one processor 601 can execute the above-mentioned method for monitoring the startup of a foreground application.

The memory 602 and the processor 601 are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors 601 and various circuits of the memory 602 together. The bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface between the bus and the transceiver. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor 601 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 601 .

Processor 601 is responsible for managing the bus and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory 602 may be used to store data used by the processor 601 in performing operations.

A fifth embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The above method embodiments are implemented when the computer program is executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

Those skilled in the art can understand that the above-mentioned embodiments are specific examples for realizing the present invention, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present invention. scope.

Claims (10)

1. A method for monitoring foreground application starting, comprising:

scanning a process directory of the system at a preset period;

judging whether a newly added process exists according to the scanned process directory, and if so, acquiring an application package name corresponding to the process;

and judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, if so, judging that foreground application is started.

2. The method for monitoring foreground application startup according to claim 1, further comprising, after the obtaining the application package name corresponding to the process:

loading the content to be released;

after the foreground application is judged to be started, the method further comprises the following steps:

and the content to be delivered is delivered to the interface of the started foreground application.

3. The method for listening to foreground application startup according to claim 2, wherein before loading the content to be delivered, further comprising:

judging whether the newly added process is a newly added process in a preset application scene;

and if the new process is the new process in the preset application scene, the content to be released is loaded.

4. The method for monitoring foreground application startup according to claim 1, wherein the determining whether there is a new process according to the scanned process directory specifically includes:

judging whether a newly added main process exists according to the scanned process directory;

and if the newly added main process exists, judging that the newly added process exists.

5. The method for monitoring foreground application startup according to claim 1, wherein the determining whether there is a new process specifically comprises:

and judging whether the process directory has a newly added process folder or not, and if so, judging that a newly added process exists.

6. The method for monitoring foreground application startup according to any one of claims 1 to 5, wherein judging whether there is a new process according to the scanned process directory specifically includes:

judging whether a newly added non-system process exists according to the scanned process directory;

and if the newly added non-system process exists, acquiring the application package name corresponding to the process.

7. The method for monitoring foreground application startup according to any one of claims 1 to 5, wherein before the determining whether the application package name is the same as an application package name obtained by a system auxiliary function callback, the method further comprises:

judging whether the application package name is an application package name representing that the application is in the starting process, if so, shortening the preset period of the process directory of the scanning system until a real application package name is obtained;

the judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback is specifically as follows:

and judging whether the real application package name is the same as the application package name obtained by the system auxiliary function callback.

8. The method for monitoring foreground application startup according to any one of claims 1 to 5, further comprising, after the obtaining the application package name corresponding to the process:

and judging whether the application package name is a target application package name, if so, forcibly ending the process, and informing a user of unloading.

9. An apparatus for listening for foreground application launches, comprising:

the scanning module is used for scanning the process catalog of the system in a preset period;

the first judgment module is used for judging whether a newly added process exists according to the scanned process directory;

the obtaining module is used for obtaining the application package name corresponding to the process when the judging module judges that the newly added process exists;

and the second judgment module is used for judging whether the application package name is the same as the application package name obtained by the system auxiliary function callback, and if so, judging that the foreground application is started.

10. A terminal device, comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method of listening for foreground application launch as claimed in any one of claims 1 to 7.

Images