CN114217879B - Method for breaking through android ghost process limitation during program starting and running - Google Patents
Method for breaking through android ghost process limitation during program starting and running Download PDFInfo
- Publication number
- CN114217879B CN114217879B CN202111590364.6A CN202111590364A CN114217879B CN 114217879 B CN114217879 B CN 114217879B CN 202111590364 A CN202111590364 A CN 202111590364A CN 114217879 B CN114217879 B CN 114217879B
- Authority
- CN
- China
- Prior art keywords
- program
- barrier
- free service
- android
- pairing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44536—Selecting among different versions
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a method for breaking through the limit of android ghost processes during program starting operation, which comprises the following steps: (1) Developing a corresponding debugged helper program of a main program which needs to be started in the android system, and sharing data of the debugged helper program and the main program; (2) Downloading a debugged helper program, and installing and running the helper program in an android system; (3) acquiring shell rights of android system terminal equipment; (4) Creating tty of shell authority, entering a data directory of the debugged helper program through a run-as command, and (5) entering a data directory of the main program through a cd command; (6) executing the main program. The method is created from the adbd system process, the process authority can be modified into the authority of the common program through the run-as command, the method is not limited by the ghost process of the android system, and the method has better compatibility.
Description
Technical Field
The invention belongs to the technical field of android system application, and particularly relates to a method for breaking through android ghost process limitation during program starting and running.
Background
Android (Android) systems are widely applied due to the characteristic of open sources, and all large mobile phone manufacturers put into production and design of the Android systems, so that the Android systems become mobile phone operation systems with the most influence.
The update speed of the android system is fast, the android system is updated to the android12, and on the android12 system, in order to effectively control the power consumption of a program and the occupation of CPU performance, the android12 can mark the process of the program for self-creation through a cgroup mechanism so as to manage, and the process of the android program is created for the process of the zygate system, or all the android processes are sub-processes of the process of the zygate system; for the process of the self-creation of the program, the android mark is Phantom process (the ghost process is a subprocess of the android program, and the grandchild and grandchild of the process of the zygate system are processes below the grandchild, the clear CPU occupation limit and the upper limit of the process number are arranged for the ghost process, the upper limit of the android12 system to the ghost process is 32, the limit of the ghost process can cause the incompatibility phenomenon of partial programs which are not actively compatible with the android12, and the ghost process which is operated by the program itself can be killed by the system, so that the program is crashed and can not be started normally.
In view of the foregoing, it is desirable to provide a method for a target application program to break through the limitation of android ghost processes during the startup operation of the android system.
Disclosure of Invention
The invention aims to provide a method for breaking through the limitation of the android ghost process during program starting operation, which can not generate ghost process and is not limited by the ghost process of the android system.
The above purpose is realized by the following technical scheme: a method for breaking through android ghost process limit during program starting operation comprises the following steps:
(1) Developing a corresponding debugged helper program of a main program which needs to be started in the android system, and sharing data of the debugged helper program and the main program;
(2) Downloading a debugged helper program, and installing and running the helper program in an android system;
(3) Acquiring shell rights of android system terminal equipment;
(4) Creating tty of shell authority, and entering a data directory of the debugged helper program through a run-as command;
(5) Entering a data directory of the main program through a cd preset command;
(6) And executing the main program.
It should be understood by those skilled in the art that tty=terminal=text input/output environment, because android processes are all created by the process of the zygate system, the number of processes created by the program in android12 is limited to 32, and the processes created by the technical scheme of the invention are not created by the process of the zygate system but created by the process of the adbd system, and the adb permission is obtained through wireless debugging, so that the permission of the process can be modified into the permission of a common program through entering the catalog of the program through a run-as command, the started process is not limited by the ghost process of the android system, the limitation of android12 to the process is avoided, so that the android system has better compatibility, and the program which is not compatible with the android new version system can normally run.
The debugged helper program is a debug version of the main program, and the shareduserids of the debugged helper program and the main program are the same value. At this time, the main program is a formal version, the debug value of which is false, that is, is not debugged, the formal version can be issued to the application market, and the debugged helper program is a debug version, the debug value of which is wire, that is, is debugged.
According to the further technical scheme, after the step (1), a step of detecting the android system version carried by the android system terminal equipment is provided when the main program is started or after the main program is downloaded, and when the detection result is that the android system version is higher than or equal to 12, a user is prompted to enter a debugged helper program for downloading the main program in the step (2).
The further technical scheme is that the step of obtaining shell permission of the android system terminal device in the step (3) specifically comprises the following steps:
s1, connecting terminal equipment with a wireless network, and installing an accessible service program to the terminal equipment, wherein the accessible service program is used for automatically acquiring shell rights of the terminal equipment;
s2, running an obstacle-free service program, starting the obstacle-free service, jumping to the obstacle-free setting of the android system, and starting the obstacle-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell rights in the barrier-free service program, and automatically acquiring Shell rights after entering the step S4;
s4, jumping from the barrier-free service program to a 'about mobile phone' interface, enabling wireless debugging by one key, enabling a 'developer option' entry by the barrier-free service;
s5, enabling wireless debugging by one key, enabling barrier-free service to enter a developer option interface, enabling wireless debugging and displaying a pairing code;
s6, the barrier-free service of the one-key-enabled wireless debugging extracts a pairing code, an IP address and a port number, and notifies a barrier-free service program to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair through a standard ADB pairing protocol and an android system ADBD;
and S8, the barrier-free service program runs a preset script program, and a daemon is started in the script program, and the daemon at the moment has shell rights.
Therefore, characters and the characteristic of simulated clicking in the interface can be obtained by using barrier-free service, the automation of starting wireless debugging is realized, the purpose of starting wireless debugging by one key is achieved, and the shell is obtained by wireless debugging. It should be noted that, it should be clear to those skilled in the art that such a program may be programmed to implement the obtaining of shell rights of the terminal device according to the functions and steps to be implemented by the barrier-free service program. The barrier-free service program comprises a preset script program and a barrier-free service function program of 'one-key-enabled wireless debugging' to realize the functions. And (3) performing steps S4-S8 by enabling wireless debugging through one key and performing background operation of barrier-free services, and performing automatic jump on the steps S4-S8 to obtain shell rights of terminal equipment based on an android system.
According to the technical scheme, based on the wireless debugging of the barrier-free service and the Android system, the wireless debugging can be automatically started through the barrier-free service program, the Shell authority is acquired through the wireless debugging, the whole process from the starting of the barrier-free service to the acquisition of the Shell authority is automatic, a complex Shell authority acquisition process is automatic, manual operation is not needed, even people without related expertise can acquire the Shell authority through one key, and the cost and threshold for acquiring the Shell authority are greatly reduced.
In a further technical scheme, in the step S1, the terminal device registers "one-key-enabled wireless debug" barrier-free service after installing the barrier-free service program.
The further technical scheme is that the process of enabling the one-key-enabled wireless debugging barrier-free service in the step S2 comprises the following specific steps:
s2.1, clicking on 'open barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of the system;
s2.2, enabling 'one-key-enabled wireless debugging' in a 'downloaded application' in the barrier-free setting interface.
The further technical scheme is that the process of opening the "developer option" entry in step S4 includes the following steps:
s4.1, automatically jumping to a 'related to mobile phone' interface by using the barrier-free service program;
s4.2, a control of a 'version number' option is acquired by a 'one-key-enabled wireless debugging' barrier-free service, 7 times of simulated clicking operation are executed, and a 'developer option' entry is opened;
s4.3, the "one-touch enabled wireless debug" barrier-free service notifies the barrier-free service program that the open "developer option" entry operation has been completed.
The further technical scheme is that the process of enabling wireless debugging and displaying the pairing code in the step S5 includes the following steps:
s5.1, enabling a wireless debugging barrier-free service by one key to acquire a control of a wireless debugging option, executing a simulated clicking operation, and entering a wireless debugging interface;
s5.2, the 'one-key-enabled wireless debugging' barrier-free service detects that the 'wireless debugging' interface is currently in, acquires a 'use pairing code pairing device' control, executes a simulated clicking operation, and the system pops up a pairing code bullet frame to display a pairing code.
The further technical scheme is that the specific steps of the step S6 are as follows:
s6.1, detecting that a pairing code information popup frame pops up by using a one-key-enabled wireless debugging barrier-free service, acquiring a pairing code control, an IP address and a port control, and acquiring characters in the control to obtain a pairing code, the IP address and the port;
s6.2, the barrier-free service of the 'one-key-enabled wireless debugging' sends the pairing code, the IP address and the port to the barrier-free service program, and the barrier-free service program executes the pairing flow.
The further technical scheme is that the specific steps of the step S7 are as follows:
s7.1, the barrier-free service program receives the pairing code, the IP address and the port number and executes pairing operation;
s7.2, the standard ADB pairing protocol is used in the background to finish the pairing process, and the pairing is successful.
The further technical scheme is that the specific steps of the step S8 are as follows:
s8.1, after the barrier-free service program finishes pairing, running a script program;
s8.2, a script program execution command copies a daemon program to a/data/local/tmp folder;
s8.3, the script program execution command endows the daemon program with read-write permission;
s8.4, the script program executes a command to start a daemon program, and the daemon program has shell authority after being started.
The process created by the technical scheme of the invention is not created from the zygote system process, but is created from the adbd system process, the process authority can be modified into the authority of the common program through a run-as command, the process is not limited by the ghost process of the android system, the compatibility loading is better, and the technical problem that partial programs which are not actively compatible with the android12 are incompatible due to the limitation of the ghost process is solved.
Description of the embodiments
The invention will be further described with reference to specific examples to facilitate a better understanding of the invention, but the scope of the invention is not limited to these examples.
The embodiment of the invention is as follows, a method for breaking through the limit of android ghost processes in program starting operation, which is characterized by comprising the following steps:
(1) Developing a corresponding debugged helper program of a main program which needs to be started in the android system, and sharing data of the debugged helper program and the main program;
(2) Downloading a debugged helper program, and installing and running the helper program in an android system;
(3) Acquiring shell rights of android system terminal equipment;
(4) Creating tty of shell authority, and entering a data directory of the debugged helper program through a run-as command;
(5) Entering a data directory of the main program through a cd preset command;
(6) And executing the main program.
It should be understood by those skilled in the art that tty=terminal=text input/output environment, and the process created by the technical scheme of the present invention is not created from the zygote system process, but created from the adbd system process, and the process authority can be modified into the authority of the common program through the run-as command, so that the process is not limited by the ghost process of the android system, and the process has better compatibility loading.
In another embodiment of the present invention, the debugged helper program is a debug version of the main program, and sharedUserId of the debugged helper program and the main program are the same value. At this time, the main program is a formal version, the debug value of which is false, that is, is not debugged, the formal version can be issued to the application market, and the debugged helper program is a debug version, the debug value of which is wire, that is, is debugged.
Based on the above embodiment, in another embodiment of the present invention, after the step (1), a step of detecting the android system version carried by the android system terminal device is provided when the main program is started or after the main program is downloaded, and when the detection result is that the android system version is higher than or equal to 12, the user is prompted to enter the debugged helper program of the main program downloaded in the step (2). The debugged helper program may be stored at the cloud server first.
Based on the above embodiment, in another embodiment of the present invention, the step of obtaining shell rights of the android system terminal device in the step (3) specifically includes the following steps:
s1, connecting terminal equipment with a wireless network, and installing an accessible service program to the terminal equipment, wherein the accessible service program is used for automatically acquiring shell rights of the terminal equipment;
s2, running an obstacle-free service program, starting the obstacle-free service, jumping to the obstacle-free setting of the android system, and starting the obstacle-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell rights in the barrier-free service program, and automatically acquiring Shell rights after entering the step S4;
s4, jumping from the barrier-free service program to a 'about mobile phone' interface, enabling wireless debugging by one key, enabling a 'developer option' entry by the barrier-free service;
s5, enabling wireless debugging by one key, enabling barrier-free service to enter a developer option interface, enabling wireless debugging and displaying a pairing code;
s6, the barrier-free service of the one-key-enabled wireless debugging extracts a pairing code, an IP address and a port number, and notifies a barrier-free service program to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair through a standard ADB pairing protocol and an android system ADBD;
and S8, the barrier-free service program runs a preset script program, and a daemon is started in the script program, and the daemon at the moment has shell rights.
Therefore, characters and the characteristic of simulated clicking in the interface can be obtained by using barrier-free service, the automation of starting wireless debugging is realized, the purpose of starting wireless debugging by one key is achieved, and the shell is obtained by wireless debugging. It should be noted that, it should be clear to those skilled in the art that such a program may be programmed to implement the obtaining of shell rights of the terminal device according to the functions and steps to be implemented by the barrier-free service program. The barrier-free service program comprises a preset script program and a barrier-free service function program of 'one-key-enabled wireless debugging' to realize the functions. And (3) performing steps S4-S8 by enabling wireless debugging through one key and performing background operation of barrier-free services, and performing automatic jump on the steps S4-S8 to obtain shell rights of terminal equipment based on an android system.
According to the technical scheme, based on the wireless debugging of the barrier-free service and the Android system, the wireless debugging can be automatically started through the barrier-free service program, the Shell authority is acquired through the wireless debugging, the whole process from the starting of the barrier-free service to the acquisition of the Shell authority is automatic, a complex Shell authority acquisition process is automatic, manual operation is not needed, even people without related expertise can acquire the Shell authority through one key, and the cost and threshold for acquiring the Shell authority are greatly reduced.
In another embodiment of the present invention, in step S1, the terminal device registers "one-touch enabled wireless debug" barrier-free service after installing the barrier-free service program.
Based on the above embodiment, in another embodiment of the present invention, the process of enabling the "one-touch enabled wireless debug" barrier-free service in the step S2 includes the following specific steps:
s2.1, clicking on 'open barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of the system;
s2.2, enabling 'one-key-enabled wireless debugging' in a 'downloaded application' in the barrier-free setting interface.
In another embodiment of the present invention, the process of opening the "developer option" entry in step S4 includes the following steps:
s4.1, automatically jumping to a 'related to mobile phone' interface by using the barrier-free service program;
s4.2, a control of a 'version number' option is acquired by a 'one-key-enabled wireless debugging' barrier-free service, 7 times of simulated clicking operation are executed, and a 'developer option' entry is opened;
s4.3, the "one-touch enabled wireless debug" barrier-free service notifies the barrier-free service program that the open "developer option" entry operation has been completed.
In another embodiment of the present invention, the process of enabling wireless debugging and displaying the pairing code in step S5 includes the following steps:
s5.1, enabling a wireless debugging barrier-free service by one key to acquire a control of a wireless debugging option, executing a simulated clicking operation, and entering a wireless debugging interface;
s5.2, the 'one-key-enabled wireless debugging' barrier-free service detects that the 'wireless debugging' interface is currently in, acquires a 'use pairing code pairing device' control, executes a simulated clicking operation, and the system pops up a pairing code bullet frame to display a pairing code.
On the basis of the above embodiment, in another embodiment of the present invention, the specific steps of the step S6 are as follows:
s6.1, detecting that a pairing code information popup frame pops up by using a one-key-enabled wireless debugging barrier-free service, acquiring a pairing code control, an IP address and a port control, and acquiring characters in the control to obtain a pairing code, the IP address and the port;
s6.2, the barrier-free service of the 'one-key-enabled wireless debugging' sends the pairing code, the IP address and the port to the barrier-free service program, and the barrier-free service program executes the pairing flow.
On the basis of the above embodiment, in another embodiment of the present invention, the specific steps of the step S7 are as follows:
s7.1, the barrier-free service program receives the pairing code, the IP address and the port number and executes pairing operation;
s7.2, the standard ADB pairing protocol is used in the background to finish the pairing process, and the pairing is successful.
On the basis of the above embodiment, in another embodiment of the present invention, the specific steps of the step S8 are as follows:
s8.1, after the barrier-free service program finishes pairing, running a script program;
s8.2, a script program execution command copies a daemon program to a/data/local/tmp folder;
s8.3, the script program execution command endows the daemon program with read-write permission;
s8.4, the script program executes a command to start a daemon program, and the daemon program has shell authority after being started.
The terms used in the present invention are as follows:
android system: the operating system is a free and open source code operating system based on Linux, and is mainly used for mobile equipment such as intelligent terminals and tablet computers, and is led and developed by Google corporation and open terminal alliance.
ADB: android debug bridge (adb) is a command line tool with multiple functions, allowing you to communicate with devices. The adb commands may be used to perform various device operations (e.g., install and debug applications) and provide access to Unix shell (which may be used to run various commands on a device).
ADBD: and the debugging service is operated in the Android system.
Wireless debugging: android11 and higher support the deployment and debugging of applications wirelessly from workstations using an Android debug bridge (adb).
Shell: refer to software (command interpreter, command parser) that provides an operator interface for the user. It receives the user command and then invokes the corresponding application.
No obstacle: the barrier-free service is an application that provides interface enhancement functions to assist handicapped users or users who may temporarily fail to fully interact with the device to complete the operation.
Control: representing the basic building blocks of the user interface component. The control occupies a rectangular area on the screen, responsible for drawing and event handling, for creating interactive UI components (buttons, text fields, etc.).
app_process: executable files for starting the program.
The ADB has Shell access rights, so that a program started by using an ADB execution command also has Shell rights, and when the ADB Shell is started by using an app_process starting program, the program also has Shell rights, and when the ADB is used, an ADBD service in an Android system needs to be started, and connection can be established between the ADB and the ADBD.
Other related terms are described in the background.
In Android10 and below, the ADBD needs to be started by connecting with a computer execution command, in Android11 and above, the system provides a wireless debugging function, and the ADBD is started after wireless debugging is started.
The specific interface operation step of the step of acquiring the shell authority of the android terminal equipment is specifically provided, and takes an android mobile phone as an example, the method comprises the following steps of:
connecting an android mobile phone to WIFI (wireless network);
installing an 'barrier-free service program' to an android mobile phone, and registering 'one-key-enabled wireless debugging' barrier-free service after installation;
clicking the "open barrier-free service" of the barrier-free service program, jumping to barrier-free setting in the android system, and enabling the barrier-free service of the "one-key-enabled wireless debugging";
returning to the barrier-free service program, clicking the Shell authority acquisition, and automatically completing the subsequent steps;
the barrier-free service program jumps to a mobile phone interface set by the system, a control for enabling wireless debugging by one key and obtaining a version number option by barrier-free service is executed for 7 times, a developer option is enabled, and the barrier-free service program is notified that the opening of a developer option entry flow is completed;
the barrier-free service program jumps to a developer option interface set by the system, a one-key starting wireless debugging barrier-free service acquires a control of a wireless debugging option, a simulated clicking operation is executed, and the wireless debugging interface is entered;
the barrier-free service of one-key starting wireless debugging detects that the interface is currently in a wireless debugging interface, wireless debugging is started, a pairing device using pairing codes is obtained, a simulated clicking operation is executed, and a pairing code bullet frame is popped up by the system to display the pairing codes;
the barrier-free service of 'one-key starting wireless debugging' acquires WLAN pairing codes, IP addresses and port controls, extracts characters in the controls, acquires the pairing codes, the IP addresses and the port numbers, and sends the pairing codes, the IP addresses and the port numbers to 'barrier-free service programs';
the barrier-free service program uses a pairing code, an IP address and a port number, and uses a standard ADB pairing protocol and a local android system ADBD to pair in the background;
the barrier-free service program finishes pairing, runs a script, the script copies the daemon program into a data/local/tmp folder, gives read-write permission, starts the daemon program by using an app_process, and runs the daemon program as a shell user after starting, namely, has shell permission.
The above examples are preferred embodiments of the present invention, but the embodiments of the present invention are not limited to the above examples, and any other changes, modifications, substitutions, combinations, and simplifications that do not depart from the spirit and principle of the present invention should be made in the equivalent manner, and the embodiments are included in the protection scope of the present invention.
Claims (9)
1. The method for breaking through the android ghost process limit during program starting and running is characterized by comprising the following steps of:
(1) Developing a corresponding debugged helper program of a main program which needs to be started in the android system, and sharing data of the debugged helper program and the main program;
(2) Downloading a debugged helper program, and installing and running the helper program in an android system;
(3) Acquiring shell rights of android system terminal equipment;
s1, connecting terminal equipment with a wireless network, and installing an accessible service program to the terminal equipment, wherein the accessible service program is used for automatically acquiring shell rights of the terminal equipment;
s2, running an obstacle-free service program, starting the obstacle-free service, jumping to the obstacle-free setting of the android system, and starting the obstacle-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell rights in the barrier-free service program, and automatically acquiring Shell rights after entering the step S4;
s4, jumping from the barrier-free service program to a 'about mobile phone' interface, enabling wireless debugging by one key, enabling a 'developer option' entry by the barrier-free service;
s5, enabling wireless debugging by one key, enabling barrier-free service to enter a developer option interface, enabling wireless debugging and displaying a pairing code;
s6, the barrier-free service of the one-key-enabled wireless debugging extracts a pairing code, an IP address and a port number, and notifies a barrier-free service program to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair through a standard ADB pairing protocol and an android system ADBD;
s8, the barrier-free service program runs a preset script program, a daemon process is started in the script program, and the daemon process at the moment has shell rights;
(4) Creating tty of shell authority, and entering a data directory of the debugged helper program through a run-as command;
(5) Entering a data directory of the main program through a cd command;
(6) And executing the main program.
2. The method for program launch run break-through android process limit of claim 1 wherein said debugged helper is a debugged version of the main program, said debugged helper and shareduser of the main program being the same value.
3. The method for breaking the limit of the android process by the program starting operation according to claim 2, wherein the step (1) is followed by a step of detecting the android system version carried by the android system terminal device when the main program is started or after the main program is downloaded, and when the detection result is that the android system version is higher than or equal to 12, prompting the user to enter the debugged helper program of the main program downloaded in the step (2).
4. The method for breaking android process limit for program start-up operation according to claim 1, wherein in said step S1, said terminal device registers "one-touch enabled wireless debug" no-obstacle service after installing no-obstacle service program.
5. The method for program initiation operation to break through the android process constraint of claim 4, wherein said process of enabling "one-touch enabled wireless debug" barrier-free service in step S2 comprises the following specific steps:
s2.1, clicking on 'open barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of the system;
s2.2, enabling 'one-key-enabled wireless debugging' in a 'downloaded application' in the barrier-free setting interface.
6. The method for program initiation operation to break through the android process constraint as recited in claim 5, wherein said process of opening a "developer option" entry in step S4 comprises the steps of:
s4.1, automatically jumping to a 'related to mobile phone' interface by using the barrier-free service program;
s4.2, a control of a 'version number' option is acquired by a 'one-key-enabled wireless debugging' barrier-free service, 7 times of simulated clicking operation are executed, and a 'developer option' entry is opened;
s4.3, the "one-touch enabled wireless debug" barrier-free service notifies the barrier-free service program that the open "developer option" entry operation has been completed.
7. The method for program initiation operation to break through the android process constraint of claim 6, wherein said process of enabling wireless debugging and displaying pairing codes in step S5 comprises the steps of:
s5.1, enabling a wireless debugging barrier-free service by one key to acquire a control of a wireless debugging option, executing a simulated clicking operation, and entering a wireless debugging interface;
s5.2, the 'one-key-enabled wireless debugging' barrier-free service detects that the 'wireless debugging' interface is currently in, acquires a 'use pairing code pairing device' control, executes a simulated clicking operation, and the system pops up a pairing code bullet frame to display a pairing code.
8. The method for program initiation operation to break through the android process constraint of claim 7, wherein said step S6 comprises the specific steps of:
s6.1, detecting that a pairing code information popup frame pops up by using a one-key-enabled wireless debugging barrier-free service, acquiring a pairing code control, an IP address and a port control, and acquiring characters in the control to obtain a pairing code, the IP address and the port;
s6.2, the barrier-free service of the 'one-key-enabled wireless debugging' sends the pairing code, the IP address and the port to the barrier-free service program, and the barrier-free service program executes the pairing flow.
9. The method for program initiation operation to break through the android process constraint of claim 8, wherein said step S8 comprises the specific steps of:
s8.1, after the barrier-free service program finishes pairing, running a script program;
s8.2, a script program execution command copies a daemon program to a/data/local/tmp folder;
s8.3, the script program execution command endows the daemon program with read-write permission;
s8.4, the script program executes a command to start a daemon program, and the daemon program has shell authority after being started.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111590364.6A CN114217879B (en) | 2021-12-23 | 2021-12-23 | Method for breaking through android ghost process limitation during program starting and running |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111590364.6A CN114217879B (en) | 2021-12-23 | 2021-12-23 | Method for breaking through android ghost process limitation during program starting and running |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114217879A CN114217879A (en) | 2022-03-22 |
| CN114217879B true CN114217879B (en) | 2023-05-23 |
Family
ID=80705432
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111590364.6A Active CN114217879B (en) | 2021-12-23 | 2021-12-23 | Method for breaking through android ghost process limitation during program starting and running |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114217879B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860327B (en) * | 2022-07-07 | 2022-09-23 | 北京麟卓信息科技有限公司 | Quick starting method for android application in android compatible environment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012008825A (en) * | 2010-06-25 | 2012-01-12 | Nec Corp | Program obfuscation device, program control device, program obfuscation method and program |
| CN103365688A (en) * | 2013-06-28 | 2013-10-23 | 深圳市掌讯通讯设备有限公司 | Method for automatic installation and synchronization of software between Android intelligent devices |
| KR20180028851A (en) * | 2016-09-09 | 2018-03-19 | 주식회사 엑츠 | Apparatus, method and computer program for playback of contents based on android operating system |
| CN110032512A (en) * | 2019-03-28 | 2019-07-19 | 腾讯科技（深圳）有限公司 | A kind of adjustment method of small routine, relevant device and terminal |
| CN113791869A (en) * | 2021-09-18 | 2021-12-14 | 湖南小算科技信息有限公司 | Method for acquiring shell permission of terminal equipment based on android system |
-
2021
- 2021-12-23 CN CN202111590364.6A patent/CN114217879B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012008825A (en) * | 2010-06-25 | 2012-01-12 | Nec Corp | Program obfuscation device, program control device, program obfuscation method and program |
| CN103365688A (en) * | 2013-06-28 | 2013-10-23 | 深圳市掌讯通讯设备有限公司 | Method for automatic installation and synchronization of software between Android intelligent devices |
| KR20180028851A (en) * | 2016-09-09 | 2018-03-19 | 주식회사 엑츠 | Apparatus, method and computer program for playback of contents based on android operating system |
| CN110032512A (en) * | 2019-03-28 | 2019-07-19 | 腾讯科技（深圳）有限公司 | A kind of adjustment method of small routine, relevant device and terminal |
| CN113791869A (en) * | 2021-09-18 | 2021-12-14 | 湖南小算科技信息有限公司 | Method for acquiring shell permission of terminal equipment based on android system |
Non-Patent Citations (3)
| Title |
|---|
| adbd android12 process number limit;ADAM CONWAY;《XDA》;全文 * |
| 基于pigpiod C接口的高精度编码器电机速度检测方案;边蓓蓓;张东辉;李德胜;;长春工程学院学报(自然科学版)(02);全文 * |
| 如何让我们的Android应用进程保活？;w_y8711;《CSDN》;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114217879A (en) | 2022-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105955782B (en) | Application program operation control method and device | |
| CN109669873B (en) | User interface automatic test method and device, electronic equipment and storage medium | |
| US11960869B2 (en) | Android penetration method and device for implementing silent installation based on accessibility services | |
| CN106502717B (en) | Application program running method and device | |
| CN104809045B (en) | Running method and device of monitoring script | |
| CN114217879B (en) | Method for breaking through android ghost process limitation during program starting and running | |
| JP2021504826A (en) | How to launch application programs, launchers and computer-readable storage media | |
| CN112968929B (en) | Server management method and system | |
| CN113051088A (en) | Program loading method, device, equipment and computer readable medium | |
| CN113836505A (en) | Method for rapidly acquiring shell permission of terminal equipment based on android system | |
| CN103997684A (en) | Method and device for updating operating system | |
| CN106648678A (en) | System update control method and device | |
| CN113517996A (en) | Network card equipment polling method, system and related device | |
| EP3547109B1 (en) | Installing and uninstalling web applications on an image processing apparatus using a software development kit sdk | |
| CN113791790A (en) | Application program updating method and device, electronic equipment and storage medium | |
| EP3321808B1 (en) | Verification system and verification method | |
| WO2014196366A1 (en) | Information processing device, information processing method, and program | |
| CN103279348B (en) | System boot process shows the method and system of information | |
| US12026503B2 (en) | Device of updating library required by testing program for testing and method thereof | |
| CN109428936B (en) | APP upgrading method, device, system, electronic equipment and storage medium | |
| CN110764840B (en) | Method, device and system for wirelessly debugging android device | |
| CN114880244A (en) | Application testing method and device, storage medium and electronic equipment | |
| CN106708558B (en) | Method and device for closing application program | |
| CN113791869A (en) | Method for acquiring shell permission of terminal equipment based on android system | |
| CN107315602B (en) | Application program upgrading method and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |