CN114217879A - Method for breaking limitation of android ghost process during program starting and running - Google Patents
Method for breaking limitation of android ghost process during program starting and running Download PDFInfo
- Publication number
- CN114217879A CN114217879A CN202111590364.6A CN202111590364A CN114217879A CN 114217879 A CN114217879 A CN 114217879A CN 202111590364 A CN202111590364 A CN 202111590364A CN 114217879 A CN114217879 A CN 114217879A
- Authority
- CN
- China
- Prior art keywords
- program
- barrier
- free service
- android
- starting
- 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.)
- Granted
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 the limitation of android ghost processes during program starting and running, which comprises the following steps: (1) developing a corresponding debuggable assistant program for a main program to be started in an android system, and sharing the debuggable assistant program with the main program data; (2) downloading a debuggable assistant program, and installing and operating the assistant program in the android system; (3) acquiring the shell permission of android system terminal equipment; (4) creating tty of shell authority, entering a data directory of a debuggable helper program through a run-as command, and (5) entering the data directory of a main program through a cd command; (6) the main program is executed. The method is created from the adbd system process, can modify the process authority into the authority of the common program through the run-as command, is not limited by the android system ghost process, and 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
The Android (Android) system is widely applied due to the characteristics of open sources, and all large mobile phone manufacturers put into production and design own Android systems, which become the most influential mobile phone operating systems.
The update speed of the android system is very fast, the android12 is updated at present, on the android12 system, in order to effectively manage and control the power consumption of the program and the occupation of the CPU performance, the android12 can mark the self-formed processes of the program through a cgroup mechanism, so as to manage the processes, the processes of the android program are formed for the processes of the zygate system, and all the android processes can be sub-processes of the zygate system; the method is characterized in that the android is marked as PhantomProcesses (ghost processes, namely processes below grandson and grandson of zygate system process and grandson of the android program) for the processes created by the program, the ghost processes have definite CPU occupation limit and process number upper limit, the limit of the android12 system to the ghost processes is 32, the limit of the ghost processes can cause incompatibility of partial programs which are not actively compatible with the android12, and the ghost processes operated by the program can be killed by the system, so that the program is crashed and cannot be started to operate normally.
In view of the foregoing, it is desirable to provide a method for a target application to break the android ghost process restriction when the android system is booted.
Disclosure of Invention
The invention aims to provide a method for breaking through android ghost process limitation in program starting and running, which does not generate ghost processes and is not limited by android system ghost processes.
The above purpose is realized by the following technical scheme: a method for breaking the limit of android ghost processes during program starting and running comprises the following steps:
(1) developing a corresponding debuggable assistant program for a main program to be started in an android system, and sharing the debuggable assistant program with the main program data;
(2) downloading a debuggable assistant program, and installing and operating the assistant program in the android system;
(3) acquiring the shell permission of android system terminal equipment;
(4) create tty of shell rights, enter the data directory of the debuggable helper program through run-as command,
(5) entering a data directory of a main program through a cd predetermined command;
(6) the main program is executed.
Those skilled in the art should understand that, because the android processes are all created by zygate system processes, the number of the processes created by a program is limited to 32 at android12, the processes created by the technical solution of the present invention are not created from zygate system processes, but are created from adbd system processes, and the adb authority is obtained through wireless debugging, so that the process authority can be modified into the authority of a common program by entering a directory of the program through a run-as command, the started process is not limited by a ghost process of an android system, the limitation of android12 on the processes is avoided, and better compatibility is achieved, and a program which is not compatible with a new android version system can normally run.
The method further comprises the technical scheme that the debuggable assistant program is a debugging version of a main program, and sharedUserId of the debuggable assistant program and the main program is the same value. At this time, the main program is a formal version, the debug value of the main program is false, that is, the main program is not debuggable, the formal version can be released to the application market, the debuggable helper program is a debug version, and the debug value of the debuggable helper program is tune, that is, the debuggable helper program is debuggable.
The method further adopts the technical scheme that a step of detecting the android system version carried by the android system terminal equipment is carried out after the main program is started or downloaded after the step (1), and when the detection result shows that the android system version is higher than or equal to 12, a user is prompted to enter the step (2) to download the debuggeable assistant program of the main program.
The further technical scheme is that the step of obtaining the shell permission of the android system terminal device in the step (3) is specifically as follows:
s1, connecting the terminal equipment with a wireless network, and installing a barrier-free service program into the terminal equipment, wherein the barrier-free service program is used for automatically acquiring the shell authority of the terminal equipment;
s2, running a barrier-free service program, starting barrier-free service, jumping to barrier-free setting of an android system, and starting barrier-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell permission in the barrier-free service program, and automatically acquiring the Shell permission after the step S4 is carried out;
s4, jumping to 'about mobile phone' interface from the barrier-free service program, and 'one-key starting wireless debugging' barrier-free service starting 'developer option' entrance;
s5, starting wireless debugging by one key, entering a developer option interface by barrier-free service, starting wireless debugging and displaying pairing codes;
s6, the barrier-free service of 'one-key starting wireless debugging' extracts pairing codes, IP addresses and port numbers and informs barrier-free service programs to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair with the android system ADBD through a standard ADB pairing protocol;
and S8, running a preset script program by the barrier-free service program, starting a daemon process in the script program, wherein the daemon process has the shell authority.
Therefore, characters in the interface and the characteristic of simulating clicking can be obtained by using barrier-free service, the automation of starting wireless debugging is realized, the purpose of starting wireless debugging in a one-key mode is achieved, and the shell is obtained through wireless debugging. It should be noted that it is clear to those skilled in the art that such a program can be programmed according to the functions and steps to be implemented by the barrier-free service program to implement the obtaining of the shell rights of the terminal device. The barrier-free service program comprises a preset script program and a barrier-free service function program of 'one-key starting wireless debugging' to realize the functions. And the step S4-S8 is finished by the operation of the barrier-free service background of 'one-key starting wireless debugging', and the step S4-S8 automatically skip to finish the method for acquiring the shell permission of the terminal equipment based on the android system.
The technical scheme of the invention is based on the barrier-free service and the wireless debugging of an Android system, the wireless debugging can be automatically started through a barrier-free service program, the Shell permission is obtained through the wireless debugging, the whole process from the starting of the barrier-free service to the obtaining of the Shell permission is automatic, the complicated obtaining of the Shell permission current limiting process is automatic, manual operation is not needed, even personnel without relevant professional knowledge can obtain the Shell permission by one key, and the cost and the threshold for obtaining the Shell permission are greatly reduced.
A further technical solution is that, in step S1, the terminal device registers "one key starts wireless debugging" barrier-free service after installing the barrier-free service program.
The further technical solution is that the process of enabling the barrier-free service of "enabling wireless debug by one key" in step S2 includes the following specific steps:
s2.1, clicking 'starting barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of a system;
and S2.2, starting 'one-key starting wireless debugging' in the 'downloaded application' barrier-free setting interface.
A further technical solution is that the process of opening the "developer option" entry in step S4 includes the following steps:
s4.1, automatically jumping to a mobile phone-related interface by the barrier-free service program;
s4.2, acquiring a control of a version number option by using the one-key starting wireless debugging barrier-free service, executing 7 times of simulated click operation, and opening a developer option entrance;
s4.3, the barrier-free service of 'one-key starting wireless debugging' informs the barrier-free service program that the operation of opening the 'developer option' entrance is completed.
Further technical solution is that the process of enabling wireless debugging and displaying pairing codes in step S5 includes the following steps:
s5.1, acquiring a control of a wireless debugging option by using the barrier-free service of 'one-key starting wireless debugging', executing simulated click operation, and entering a 'wireless debugging' interface;
s5.2, the barrier-free service of 'one-key starting wireless debugging' detects that the system is currently in a 'wireless debugging' interface, obtains a 'device for matching equipment using matching codes' control, executes simulated click operation, pops up a matching code popup frame by the system, and displays the matching codes.
The further technical scheme is that the specific steps of the step S6 are as follows:
s6.1, the barrier-free service of 'one-key starting wireless debugging' detects that the pairing code information pop-up box pops up, acquires a pairing code control, an IP address and a port control, acquires characters in the control and acquires a pairing code, the IP address and a port;
s6.2, the barrier-free service of 'one-key starting 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 process.
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, completing the pairing process by using a standard ADB pairing protocol in the background, and successfully pairing.
The further technical scheme is that the specific steps of the step S8 are as follows:
s8.1, running a script program after the barrier-free service program completes pairing;
s8.2, copying a daemon program to a/data/local/tmp folder by a script program execution command;
s8.3, the script program execution command gives a read-write permission to the daemon process program;
and S8.4, executing a command by the script program to start the daemon program, and having the shell authority after starting.
The process created by the technical scheme of the invention is not created from a zygate system process, but is created from an adbd system process, the process permission can be modified into the permission of a common program through a run-as command, the limit of a ghost process of an android system is avoided, the compatible loading is better, and the technical problem that part of programs which are not actively compatible with the android12 are incompatible due to the limit of the ghost process is solved.
Detailed Description
The invention will be further described with reference to specific examples to assist a better understanding of the invention, but the scope of the invention is not limited to these examples.
The embodiment of the invention provides a method for breaking the limitation of android ghost processes during program starting and running, which is characterized by comprising the following steps:
(1) developing a corresponding debuggable assistant program for a main program to be started in an android system, and sharing the debuggable assistant program with the main program data;
(2) downloading a debuggable assistant program, and installing and operating the assistant program in the android system;
(3) acquiring the shell permission of android system terminal equipment;
(4) create tty of shell rights, enter the data directory of the debuggable helper program through run-as command,
(5) entering a data directory of a main program through a cd predetermined command;
(6) the main program is executed.
It should be understood by those skilled in the art that, a process created by the technical solution of the present invention is not created from a zygate system process, but is created from an adbd system process, and the process permission can be modified into the permission of a common program through a run-as command, so that the process is not limited by a ghost process in an android system, and has better compatibility loading.
Based on the foregoing embodiment, in another embodiment of the present invention, the debuggable helper program is a debug version of the main program, and sharedUserId of the debuggable helper program and the main program is the same value. At this time, the main program is a formal version, the debug value of the main program is false, that is, the main program is not debuggable, the formal version can be released to the application market, the debuggable helper program is a debug version, and the debug value of the debuggable helper program is tune, that is, the debuggable helper program is debuggable.
On the basis of the above embodiment, in another embodiment of the present invention, after the step (1), a step of detecting an android system version carried by the android system terminal device is performed when the main program is started or after the main program is downloaded, and when a detection result indicates that the android system version is higher than or equal to 12, the user is prompted to enter the step (2) to download the debuggeable assistant program of the main program. The debuggable helper program may be saved in the cloud server.
On the basis of the above embodiment, in another embodiment of the present invention, the step of obtaining the shell permission of the android system terminal device in step (3) is specifically as follows:
s1, connecting the terminal equipment with a wireless network, and installing a barrier-free service program into the terminal equipment, wherein the barrier-free service program is used for automatically acquiring the shell authority of the terminal equipment;
s2, running a barrier-free service program, starting barrier-free service, jumping to barrier-free setting of an android system, and starting barrier-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell permission in the barrier-free service program, and automatically acquiring the Shell permission after the step S4 is carried out;
s4, jumping to 'about mobile phone' interface from the barrier-free service program, and 'one-key starting wireless debugging' barrier-free service starting 'developer option' entrance;
s5, starting wireless debugging by one key, entering a developer option interface by barrier-free service, starting wireless debugging and displaying pairing codes;
s6, the barrier-free service of 'one-key starting wireless debugging' extracts pairing codes, IP addresses and port numbers and informs barrier-free service programs to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair with the android system ADBD through a standard ADB pairing protocol;
and S8, running a preset script program by the barrier-free service program, starting a daemon process in the script program, wherein the daemon process has the shell authority.
Therefore, characters in the interface and the characteristic of simulating clicking can be obtained by using barrier-free service, the automation of starting wireless debugging is realized, the purpose of starting wireless debugging in a one-key mode is achieved, and the shell is obtained through wireless debugging. It should be noted that it is clear to those skilled in the art that such a program can be programmed according to the functions and steps to be implemented by the barrier-free service program to implement the obtaining of the shell rights of the terminal device. The barrier-free service program comprises a preset script program and a barrier-free service function program of 'one-key starting wireless debugging' to realize the functions. And the step S4-S8 is finished by the operation of the barrier-free service background of 'one-key starting wireless debugging', and the step S4-S8 automatically skip to finish the method for acquiring the shell permission of the terminal equipment based on the android system.
The technical scheme of the invention is based on the barrier-free service and the wireless debugging of an Android system, the wireless debugging can be automatically started through a barrier-free service program, the Shell permission is obtained through the wireless debugging, the whole process from the starting of the barrier-free service to the obtaining of the Shell permission is automatic, the complicated obtaining of the Shell permission current limiting process is automatic, manual operation is not needed, even personnel without relevant professional knowledge can obtain the Shell permission by one key, and the cost and the threshold for obtaining the Shell permission are greatly reduced.
On the basis of the foregoing embodiment, in another embodiment of the present invention, in step S1, the terminal device registers "one-key-on wireless debug" barrier-free service after installing the barrier-free service program.
On the basis of the above embodiment, in another embodiment of the present invention, the process of enabling the barrier-free service of "wireless debug by one key" in step S2 includes the following specific steps:
s2.1, clicking 'starting barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of a system;
and S2.2, starting 'one-key starting wireless debugging' in the 'downloaded application' barrier-free setting interface.
On the basis of the above embodiment, 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 mobile phone-related interface by the barrier-free service program;
s4.2, acquiring a control of a version number option by using the one-key starting wireless debugging barrier-free service, executing 7 times of simulated click operation, and opening a developer option entrance;
s4.3, the barrier-free service of 'one-key starting wireless debugging' informs the barrier-free service program that the operation of opening the 'developer option' entrance is completed.
On the basis of the above embodiment, in another embodiment of the present invention, the process of enabling wireless debugging and displaying pairing codes in step S5 includes the following steps:
s5.1, acquiring a control of a wireless debugging option by using the barrier-free service of 'one-key starting wireless debugging', executing simulated click operation, and entering a 'wireless debugging' interface;
s5.2, the barrier-free service of 'one-key starting wireless debugging' detects that the system is currently in a 'wireless debugging' interface, obtains a 'device for matching equipment using matching codes' control, executes simulated click operation, pops up a matching code popup frame by the system, and displays the matching codes.
On the basis of the foregoing embodiment, in another embodiment of the present invention, the specific steps of step S6 are as follows:
s6.1, the barrier-free service of 'one-key starting wireless debugging' detects that the pairing code information pop-up box pops up, acquires a pairing code control, an IP address and a port control, acquires characters in the control and acquires a pairing code, the IP address and a port;
s6.2, the barrier-free service of 'one-key starting 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 process.
On the basis of the foregoing embodiment, in another embodiment of the present invention, the specific steps of 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, completing the pairing process by using a standard ADB pairing protocol in the background, and successfully pairing.
On the basis of the foregoing embodiment, in another embodiment of the present invention, the specific steps of step S8 are as follows:
s8.1, running a script program after the barrier-free service program completes pairing;
s8.2, copying a daemon program to a/data/local/tmp folder by a script program execution command;
s8.3, the script program execution command gives a read-write permission to the daemon process program;
and S8.4, executing a command by the script program to start the daemon program, and having the shell authority after starting.
The terminology used in the present invention is as follows:
an android system: the Linux-based operating system is a Linux-based free and open source code operating system, 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: the Android debug bridge (adb) is a command line tool with various functions, and can enable you to communicate with the equipment. The adb command may be used to perform various device operations (e.g., install and debug applications) and provide access to the Unix shell (which may be used to run various commands on the device).
ADBD: and running the debugging service in the Android system.
Wireless debugging: android11 and higher supports wireless deployment and debugging of applications from workstations using an Android debug bridge (adb).
Shell: and software (command parser) for providing an operation interface for a user. It receives a user command and then invokes the corresponding application.
And (3) barrier-free: barrier-free services are applications that provide interface enhancement functions to assist a disabled user or a user who may temporarily be unable to fully interact with the device to perform operations.
And (4) control: representing the basic building blocks of the user interface components. Controls occupy a rectangular area on the screen, responsible for drawing and event handling, for creating interactive UI components (buttons, text fields, etc.).
app _ process: an executable file for initiating a program.
The ADB has a Shell access right, so a program started by using an ADB execution command also has the Shell right, and enters an ADB Shell app _ process starting program, so that the program also has the Shell right, and when the ADB needs to be used, ADBD service in an Android system needs to be started, and the ADB and the ADBD can be connected.
Other related terms are introduced in the background.
In the Android10 and below, starting the ADBD needs to be connected with a computer to execute command starting, and in the Android11 and above, the system provides a wireless debugging function, and the wireless debugging is started, namely the ADBD is started.
A specific interface operation step of the step of obtaining the shell permission of the android system terminal device is provided, and taking an android mobile phone as an example, the method comprises the following steps:
connecting the android handset to WIFI (wireless network);
installing a barrier-free service program into the android mobile phone, and registering 'one-key starting of wireless debugging' barrier-free service after installation;
clicking 'barrier-free service starting' of a 'barrier-free service program', jumping to barrier-free setting in an android system, and starting 'one-key starting wireless debugging' barrier-free service;
returning to the barrier-free service program, clicking to acquire the Shell permission, and automatically completing the subsequent steps;
the 'barrier-free service program' jumps to a 'mobile phone' interface set by a system, the 'one-key starting wireless debugging' barrier-free service obtains a control of a 'version number' option, 7 times of simulated click operation is executed, the 'developer option' is started, and the 'barrier-free service program' is informed that an 'developer option' inlet flow is started;
the 'barrier-free service program' jumps to a 'developer option' interface set by a system, and 'one-key starting of wireless debugging' barrier-free service obtains a control of a 'wireless debugging' option, executes simulated click operation and enters a 'wireless debugging' interface;
the one-key starting wireless debugging barrier-free service detects that the system is currently in a wireless debugging interface, starts wireless debugging, acquires a control of using pairing code pairing equipment, executes simulated click operation, pops up a pairing code popup frame by the system, and displays pairing codes;
the method comprises the steps that a barrier-free service of 'enabling wireless debugging by one key' acquires WLAN pairing codes, IP addresses and port controls, extracts characters in the controls, obtains the pairing codes, the IP addresses and the port numbers, and sends the pairing codes, the IP addresses and the port numbers to a barrier-free service program;
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 completes pairing, runs the script, the script copies the daemon program to a/data/local/tmp folder, gives read-write permission, starts the daemon program by using app _ process, and the daemon program runs by the shell user after being started, namely the daemon program has shell permission.
The above embodiments are preferred embodiments of the present invention, but the present invention is not limited to the above embodiments, and any other changes, modifications, substitutions, combinations, and simplifications which do not depart from the spirit and principle of the present invention should be construed as equivalents thereof, and all such changes, modifications, substitutions, combinations, and simplifications are intended to be included in the scope of the present invention.
Claims (10)
1. A method for breaking the limitation of android ghost process in program starting and running is characterized by comprising the following steps:
(1) developing a corresponding debuggable assistant program for a main program to be started in an android system, and sharing the debuggable assistant program with the main program data;
(2) downloading a debuggable assistant program, and installing and operating the assistant program in the android system;
(3) acquiring the shell permission of android system terminal equipment;
(4) create tty of shell rights, enter the data directory of the debuggable helper program through run-as command,
(5) entering a data directory of a main program through a cd command;
(6) the main program is executed.
2. The method for program launch runtime breaching android ghost process limits of claim 1, wherein the debuggable helper program is a debugged version of a main program, and sharedUserId of the debuggable helper program and the main program is the same value.
3. The method for breaking the limitation of the android ghost process in program starting operation according to claim 2, wherein a step of detecting the android system version carried by the android system terminal device is provided after the step (1) when the main program is started or after the main program is downloaded, and when the detection result shows that the android system version is higher than or equal to 12, the user is prompted to enter the step (2) to download the debuggable assistant program of the main program.
4. The method for breaking android ghost process restriction during program startup and operation according to claim 3, wherein the step of obtaining the shell permission of the android system terminal device in the step (3) is specifically as follows:
s1, connecting the terminal equipment with a wireless network, and installing a barrier-free service program into the terminal equipment, wherein the barrier-free service program is used for automatically acquiring the shell authority of the terminal equipment;
s2, running a barrier-free service program, starting barrier-free service, jumping to barrier-free setting of an android system, and starting barrier-free service of 'one-key starting wireless debugging';
s3, starting a function of acquiring Shell permission in the barrier-free service program, and automatically acquiring the Shell permission after the step S4 is carried out;
s4, jumping to 'about mobile phone' interface from the barrier-free service program, and 'one-key starting wireless debugging' barrier-free service starting 'developer option' entrance;
s5, starting wireless debugging by one key, entering a developer option interface by barrier-free service, starting wireless debugging and displaying pairing codes;
s6, the barrier-free service of 'one-key starting wireless debugging' extracts pairing codes, IP addresses and port numbers and informs barrier-free service programs to execute pairing;
s7, the barrier-free service program uses the pairing code, the IP address and the port number to pair with the android system ADBD through a standard ADB pairing protocol;
and S8, running a preset script program by the barrier-free service program, starting a daemon process in the script program, wherein the daemon process has the shell authority.
5. The method for program startup operation to break the android ghost process restriction as claimed in claim 4, wherein in step S1, the terminal device registers "one-touch start wireless debug" barrier-free service after installing the barrier-free service program.
6. The method for program startup operation to break the android ghost process restriction as claimed in claim 5, wherein the step of enabling the "one-touch-enabled wireless debugging" barrier-free service in step S2 comprises the following specific steps:
s2.1, clicking 'starting barrier-free service' in a barrier-free service program, and automatically jumping to a barrier-free setting interface of a system;
and S2.2, starting 'one-key starting wireless debugging' in the 'downloaded application' barrier-free setting interface.
7. The method for program launch runtime breaching android ghost process limitations of claim 6, wherein the process of opening a "developer options" portal in step S4 includes the steps of:
s4.1, automatically jumping to a mobile phone-related interface by the barrier-free service program;
s4.2, acquiring a control of a version number option by using the one-key starting wireless debugging barrier-free service, executing 7 times of simulated click operation, and opening a developer option entrance;
s4.3, the barrier-free service of 'one-key starting wireless debugging' informs the barrier-free service program that the operation of opening the 'developer option' entrance is completed.
8. The method for program startup operation to break the android ghost process restriction as claimed in claim 7, wherein the step S5 of enabling wireless debugging and displaying pairing code comprises the steps of:
s5.1, acquiring a control of a wireless debugging option by using the barrier-free service of 'one-key starting wireless debugging', executing simulated click operation, and entering a 'wireless debugging' interface;
s5.2, the barrier-free service of 'one-key starting wireless debugging' detects that the system is currently in a 'wireless debugging' interface, obtains a 'device for matching equipment using matching codes' control, executes simulated click operation, pops up a matching code popup frame by the system, and displays the matching codes.
9. The method for program startup and operation to break the android ghost process restriction as claimed in claim 8, wherein the specific steps of the step S6 are as follows:
s6.1, the barrier-free service of 'one-key starting wireless debugging' detects that the pairing code information pop-up box pops up, acquires a pairing code control, an IP address and a port control, acquires characters in the control and acquires a pairing code, the IP address and a port;
s6.2, the barrier-free service of 'one-key starting 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 process.
10. The method for program startup and operation to break the android ghost process restriction as claimed in claim 9, wherein the specific steps of the step S8 are as follows:
s8.1, running a script program after the barrier-free service program completes pairing;
s8.2, copying a daemon program to a/data/local/tmp folder by a script program execution command;
s8.3, the script program execution command gives a read-write permission to the daemon process program;
and S8.4, executing a command by the script program to start the daemon program, and having the shell authority after starting.
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 true CN114217879A (en) | 2022-03-22 |
| CN114217879B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860327A (en) * | 2022-07-07 | 2022-08-05 | 北京麟卓信息科技有限公司 | 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 |
|---|
| ADAM CONWAY: "adbd android12 process number limit", 《XDA》 * |
| W_Y8711: "如何让我们的Android应用进程保活？", 《CSDN》 * |
| 边蓓蓓;张东辉;李德胜;: "基于pigpiod C接口的高精度编码器电机速度检测方案", 长春工程学院学报(自然科学版) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860327A (en) * | 2022-07-07 | 2022-08-05 | 北京麟卓信息科技有限公司 | Quick starting method for android application in android compatible environment |
| CN114860327B (en) * | 2022-07-07 | 2022-09-23 | 北京麟卓信息科技有限公司 | Quick starting method for android application in android compatible environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114217879B (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107979508B (en) | Micro-service test method and device | |
| CN109669873B (en) | User interface automatic test method and device, electronic equipment and storage medium | |
| CN106502717B (en) | Application program running method and device | |
| CN111581095A (en) | Self-starting USB debugging method and device based on barrier-free service and storage medium | |
| CN113836505A (en) | Method for rapidly acquiring shell permission of terminal equipment based on android system | |
| CN114217879A (en) | Method for breaking limitation of android ghost process during program starting and running | |
| CN103997684A (en) | Method and device for updating operating system | |
| CN117149469B (en) | Method, device, equipment and storage medium for calling host function by H5 page | |
| CN113360379B (en) | Program test environment creation method and program test environment creation apparatus | |
| CN115421765A (en) | Big data management deployment method applied to domestic operating system | |
| CN113791790A (en) | Application program updating method and device, electronic equipment and storage medium | |
| US11023220B2 (en) | Firmware update with integrated smart sequence and action engine | |
| CN106648697B (en) | Method for lighting terminal and method for automatically controlling terminal | |
| CN113051088B (en) | Program loading method, device, equipment and computer readable medium | |
| CN113791869A (en) | Method for acquiring shell permission of terminal equipment based on android system | |
| CN110764840B (en) | Method, device and system for wirelessly debugging android device | |
| CN115357355A (en) | Method, device and equipment for software cross-system migration and readable storage medium | |
| CN115098116A (en) | Simulation operation method and device of application program, terminal and storage medium | |
| CN109871288B (en) | Method, device, equipment and medium for executing Android system command | |
| CN105786565A (en) | Method for calling background control program through WEB end | |
| CN113031964A (en) | Management method, device, equipment and storage medium for big data application | |
| CN110309000B (en) | Application update prompting method and terminal equipment | |
| CN109428936B (en) | APP upgrading method, device, system, electronic equipment and storage medium | |
| CN107315602B (en) | Application program upgrading method and terminal | |
| CN110688170A (en) | Operation station operation optimization device and method |
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 |