CN113900851B - Android application software control method and device - Google Patents
Android application software control method and device Download PDFInfo
- Publication number
- CN113900851B CN113900851B CN202111275505.5A CN202111275505A CN113900851B CN 113900851 B CN113900851 B CN 113900851B CN 202111275505 A CN202111275505 A CN 202111275505A CN 113900851 B CN113900851 B CN 113900851B
- Authority
- CN
- China
- Prior art keywords
- type
- abnormal
- information
- abnormality
- android system
- 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
- 238000000034 method Methods 0.000 title claims abstract description 41
- 230000002159 abnormal effect Effects 0.000 claims abstract description 193
- 230000005856 abnormality Effects 0.000 claims description 81
- 230000007246 mechanism Effects 0.000 claims description 11
- 238000006243 chemical reaction Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 19
- 238000004891 communication Methods 0.000 description 7
- 206010016754 Flashback Diseases 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
- G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a control method and a device for android application software. According to the scheme, after the abnormal information is acquired from the android system, the abnormal type of the abnormal information is obtained through the abnormal classification of the acquired abnormal information, and corresponding instructions are sent to different types, if the abnormal information belongs to the first abnormal type, the software continuous operation instructions are sent to the android system, so that the application software can continue to operate, the problem of application software flashing back caused by a part of abnormal information is reduced, the flashing back frequency of the APP is further reduced, and the experience degree of a user on the APP is improved.
Description
Technical Field
The application relates to the technical field of android application software, in particular to a method and a device for controlling the android application software.
Background
With the development of internet technology, electronic products are becoming popular, wherein an Android system is an operating system of free and open source code based on a Linux kernel (not including GNU components). The method is mainly used for mobile equipment such as smart phones and tablet computers.
However, in the process of using the Android system, when an APP (application software) is abnormal to cause an APP program to Crash, the Android system starts a default abnormal killing process mechanism, the system kills an APP process which generates a Crash so that the APP is subjected to a flash-back phenomenon, if multiple crashes occur, a Crash popup window can also be generated, multiple flash backs of the APP very affect user experience, further affect the public praise of the APP, and how to reduce the flash back frequency of the APP is a concern.
Disclosure of Invention
In view of the above, the application provides a method and a device for controlling android application software, which are used for reducing the flash back frequency of APP.
In order to achieve the above object, the following solutions have been proposed:
a control method of android application software comprises the following steps:
Obtaining abnormal information from an android system;
Determining the abnormality type of the abnormality information according to a preset rule;
And if the abnormal type of the abnormal information is the preset first abnormal type, sending a software continuous operation instruction to the android system.
Optionally, the obtaining the abnormal information from the android system includes:
and acquiring the abnormal information from the android system by using a preset abnormal capturing instruction, wherein the preset abnormal capturing instruction is inserted into a message queue of a Hanlder mechanism of the android system.
Optionally, the obtaining the abnormal information from the android system by using a preset abnormal capturing instruction includes:
An interface for capturing the abnormality, which is provided by the android system, is accessed;
and acquiring the abnormal information of the android system from an interface for capturing the abnormality provided by the android system by utilizing the abnormal capturing instruction.
Optionally, the determining the anomaly type of the anomaly information according to a preset rule includes:
converting the abnormal information into a plurality of lines of text;
extracting abnormal characteristics of the plurality of lines of text;
and determining the abnormality type of the abnormality information according to the preset rule and the abnormality characteristic.
Optionally, the determining, according to the preset rule and the anomaly characteristic, the anomaly type of the anomaly information includes:
If the abnormal characteristics corresponding to the abnormal information are the appointed abnormal characteristics, converting the abnormal information into java type target abnormal information;
Determining whether the app package name and the view type contained in the target abnormal information are consistent with the information recorded in the android system;
and when the app package name and the view type contained in the target exception information are respectively consistent with the app package name and the view type in the android system and the view control is invisible, determining the exception information as a non-visible UI operation interface type in the first exception type.
Optionally, the first exception type includes a system bug type and a non-visible UI operation interface type.
Optionally, after determining the anomaly type of the anomaly information according to a preset rule, the method further includes:
And if the type of the abnormal information is a preset second abnormal type, sending a software crash instruction to the android system, wherein the second abnormal type comprises other types except the first abnormal type.
An android application software control device, comprising:
the abnormal acquisition unit is used for acquiring abnormal information from the android system;
an anomaly type determining unit for determining an anomaly type of the anomaly information according to a preset rule;
and the instruction sending unit is used for sending a software continuous operation instruction to the android system if the abnormality type of the abnormality information is a preset first abnormality type.
Optionally, the anomaly acquisition unit includes:
The instruction capturing exception unit is used for acquiring exception information from the android system by utilizing a preset capturing exception instruction, wherein the preset capturing exception instruction is inserted into a message queue of a Hanlder mechanism of the android system.
Optionally, the first exception obtaining subunit includes:
the first instruction capturing exception subunit is used for accessing an interface for capturing exception provided by the android system;
And the second instruction capturing exception subunit is used for acquiring exception information of the android system from an exception capturing interface provided by the android system by utilizing the exception capturing instruction.
According to the technical scheme, the method and the device for controlling the android application software are provided, the abnormal information is obtained from the android system, the abnormal type of the abnormal information is determined according to the preset rule, and if the abnormal type of the abnormal information is the preset first abnormal type, a software continuous operation instruction is sent to the android system. According to the scheme, after the abnormal information is acquired from the android system, the abnormal type of the abnormal information is obtained through the abnormal classification of the acquired abnormal information, and corresponding instructions are sent to different types, if the abnormal information belongs to the first abnormal type, the software continuous operation instructions are sent to the android system, so that the application software can continue to operate, the problem of application software flashing back caused by a part of abnormal information is reduced, the flashing back frequency of the APP is further reduced, and the experience degree of a user on the APP is improved.
Drawings
Fig. 1 is a flowchart of a control method of android application software provided by an embodiment of the present application;
FIG. 2 is a flowchart for obtaining abnormal information from an android system according to an embodiment of the present application;
FIG. 3 is a flowchart of determining an anomaly type of the anomaly information according to an embodiment of the present application;
FIG. 4 is a flowchart of classifying abnormal information according to an embodiment of the present application;
FIG. 5 is a target anomaly information display diagram provided by an embodiment of the present application;
Fig. 6 is a schematic structural diagram of an android application software control device according to an embodiment of the present application;
fig. 7 is a hardware structure block diagram of an android application software control device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The scheme of the application can be realized based on the terminal with the data processing capability, and the terminal can be a computer, a server, a cloud end and the like.
Next, a method for compressing an android application package according to the present application is described with a terminal view angle, and fig. 1 is a flowchart of a method for controlling android application software according to an embodiment of the present application, where the flowchart may include:
and S100, acquiring abnormal information from the android system.
Specifically, the terminal can obtain the intercepted abnormal information from the android system.
Step S110, determining the abnormality type of the abnormality information according to a preset rule.
Specifically, the terminal may classify the obtained abnormal information according to a preset rule, and determine an abnormal type of the obtained abnormal information.
And step 120, if the abnormality type of the abnormality information is a preset first abnormality type, sending a software continuous operation instruction to the android system.
Specifically, the abnormal information, part of which does not affect most of the running functions of the application software, may be classified as a first abnormal type, and when the abnormal type of the abnormal information belongs to the first abnormal type in a preset rule, in order to enable the android system to ignore the abnormalities, the terminal may send a software continuous running instruction to the android system so as to supply the application software to continue running.
According to the technical scheme, the method and the device for controlling the android application software are provided, the abnormal information is obtained from the android system, the abnormal type of the abnormal information is determined according to the preset rule, and if the abnormal type of the abnormal information is the preset first abnormal type, a software continuous operation instruction is sent to the android system. According to the scheme, after the abnormal information is acquired from the android system, the abnormal type of the abnormal information can be obtained through the abnormal classification of the acquired abnormal information, if the abnormal information belongs to the first abnormal type, a software continuous operation instruction is sent to the android system, so that the application software can continue to operate even if the abnormal information appears, the problem of application software flashing back caused by a part of abnormal information is reduced, the flashing back frequency of the APP is further reduced, and the experience degree of a user on the APP is improved.
In some embodiments of the present application, the exception information may be categorized into two major categories, a first exception type and a second exception type, the first exception type including a system bug hole type, a non-visible UI operation interface type, and the second exception type including other types than the first exception type.
Specifically, an abnormality processing mechanism of the android system can process the abnormality occurring in each operation process, and the occurrence of the abnormality can lead to the occurrence of a crash sending flashing phenomenon of application software.
In some embodiments of the present application, there are many cases where an exception occurs in an application software during a running process, and all exceptions cannot be handled correctly, so the embodiments of the present application may further include the following steps:
And if the type of the abnormal information is a preset second abnormal type, sending a software crash instruction to the android system.
Specifically, in the embodiment of the application, the processing of the unified restart APP can be performed on the exception information classified as the exception information beyond the first exception type to eliminate the exception operation, and in the embodiment of the application, when the exception information is classified as the second exception type in the preset rule, the terminal can send a software crash instruction to the android system to supply the software crash restart.
In some embodiments of the present application, in order to reduce the situation that a part of abnormal information causes an application software to crash and flash back, the embodiments of the present application may capture all abnormal information that occurs in the running process of the android application software, and the following describes a process of obtaining abnormal information from the android system in step S100, where the process may include:
and acquiring the abnormal information from the android system by using a preset abnormal capturing instruction, wherein the preset abnormal capturing instruction is inserted into a message queue of a Hanlder mechanism of the android system.
Specifically, the capturing abnormal instruction can capture the required abnormal information from the android system according to the requirement, the capturing abnormal instruction is required to be inserted into a message queue of Hanlder mechanism of the android system, and the function of capturing the abnormal instruction is realized through the refreshing principle of Hanlder mechanism.
Further, the process of acquiring the abnormal information from the android system by using the preset abnormal capturing instruction is shown in fig. 2, and may specifically include the following steps:
Step S1, an interface for capturing the abnormality, which is provided by the android system, is accessed.
Specifically, in order to obtain abnormal information generated by application software in the operation process of the android system, the android system can be accessed through an interface provided by the android system for capturing the abnormality so as to be used for subsequent operation of the scheme.
And S2, acquiring the abnormal information of the android system from an interface for capturing the abnormality provided by the android system by utilizing the abnormal capturing instruction.
Specifically, according to the embodiment of the application, the abnormal information in the android system can be captured through the abnormal capturing instruction inserted into the Hanlder mechanism, and the data transmission of the captured abnormal information is realized through an abnormal capturing interface provided by the android system.
According to the embodiment, the abnormal information generated when the application software runs in the android system can be obtained through the interface for capturing the abnormality externally provided by the android system, so that a road is provided for the subsequent processing of the abnormal information.
In some embodiments of the present application, due to the continuous perfection of the android language, a small piece of android language or abnormal stack information is often generated when the application software crashes and flashes back, and for convenience of analysis, a certain amount of a piece of android language is intercepted as the abnormal information of the abnormal problem, and the following description will be given to a process of determining the abnormal type of the abnormal information according to the preset rule in step S110, where the process is shown in fig. 3, and may specifically include the following steps:
step S111, converting the abnormal information into a plurality of lines of text.
Specifically, in order to facilitate extraction of the abnormal features in the abnormal information, the terminal may convert the abnormal information into a plurality of lines of text.
And step S112, extracting abnormal characteristics of the multi-line text.
Specifically, the abnormal feature may be set according to the requirement, for example, the abnormal feature may include DeadSystemException and NullPointerException, packet name information of an abnormality cause, and state information of a view control, and in order to determine an abnormality type of the abnormal information, the terminal may extract the abnormal feature from the multiple lines of text.
Step S113, determining the abnormality type of the abnormality information according to the preset rule and the abnormality characteristic.
Specifically, according to the abnormality type corresponding to the abnormality feature recorded in the preset rule, the terminal may determine the abnormality type of the abnormality information based on the extracted abnormality feature.
As can be seen from the above embodiments, the present application can implement the function of extracting the abnormal features by converting the abnormal information into a plurality of lines of text, so that the abnormal information can be further analyzed
Further, in the embodiment of the present application, the first exception type may include a system bug hole type and a non-visible UI operation interface type.
Specifically, the exception types belonging to the first exception type may be preset according to the requirement, and the system bug vulnerability type and the invisible UI (User Interface) operation interface type may be preset. If the abnormality characteristic of the abnormality information is DeadSystemException, the abnormality information can be classified as the abnormality of the bug vulnerability type of the system according to a preset rule, and then the abnormality information is further classified as the first abnormality type.
In the embodiment of the present application, in order to better classify different abnormal features, a classifying process of the abnormal information with the abnormal feature being the specified abnormal feature may be as shown in fig. 4, and the following step S113 further describes a process of determining an abnormal type of the abnormal information according to the preset rule and the abnormal feature, where the process may include:
step S1131, converting the anomaly information into java type target anomaly information.
If the abnormal characteristics corresponding to the abnormal information are the appointed abnormal characteristics, converting the abnormal information into java type target abnormal information.
Specifically, the specified exception feature may be set according to the requirement, for example, the specific exception feature may be NullPointerException or other Exception exception feature, and since the preset rule classifies the exception feature NullPointerException into a null pointer type, and the null pointer type includes a UI (User Interface) operation interface type and a non-visible UI (User Interface) operation interface type, in order to determine the specific exception type of the exception information including the exception feature NullPointerException, the exception information may be converted into target exception information of a java type.
Step S1132, determining whether the app package name and the view type contained in the target exception information are consistent with the information recorded in the android system and the view control is invisible.
Specifically, fig. 5 is a view showing target exception information converted into java type, where the target exception information may be shown in the form of an address, where the address includes an app package name and a view type, and the app package name and the view type recorded in the android system may be compared with the app package name and the view type included in the target exception information, and if the app package name and the view type are the same and the view control is not visible, the subsequent steps are executed.
Step S1133, determining the abnormal information as a non-visible UI operation interface type.
When the app package name and the view type contained in the target exception information are respectively consistent with the app package name and the view type in the android system, and the view control is invisible, determining the exception information as a non-visible UI operation interface type in the first exception type.
Specifically, the first exception type may include a non-visible UI operation interface type, and when it is determined that the app package name included in the target exception information is consistent with the app package name in the android system, and the target exception information inherits the view type of the android system and the view control is not visible, the exception information may be determined as the non-visible UI operation interface type in the first exception type.
According to the technical scheme, the embodiment of the application can further analyze the abnormal information by converting the abnormal information into the target abnormal information of the java type, and when the target abnormal information is determined to be of the invisible UI operation interface type, the corresponding abnormal information can be determined to be of the first abnormal type, so that the classification accuracy of different abnormal information is improved.
The following describes an android application software control device provided by the embodiment of the present application, and the android application software control device described below and the android application software control method described above may be referred to correspondingly.
As shown in fig. 6, a schematic structural diagram of an android application software control device is disclosed, where the android application software control device may include:
An anomaly acquisition unit 11 for acquiring anomaly information from the android system;
An anomaly type determining unit 12 for determining an anomaly type of the anomaly information according to a preset rule;
and the instruction sending unit 13 is configured to send a software continuous operation instruction to the android system if the anomaly type of the anomaly information is a preset first anomaly type.
Alternatively, the abnormality acquisition unit 11 may include:
The instruction capturing exception unit is used for acquiring exception information from the android system by utilizing a preset capturing exception instruction, wherein the preset capturing exception instruction is inserted into a message queue of a Hanlder mechanism of the android system.
Alternatively, the instruction capture exception unit may include:
the first instruction capturing exception subunit is used for accessing an interface for capturing exception provided by the android system;
And the second instruction capturing exception subunit is used for acquiring exception information of the android system from an exception capturing interface provided by the android system by utilizing the exception capturing instruction.
Alternatively, the abnormality type determination unit 12 may include:
A first abnormality type determination subunit configured to convert the abnormality information into a plurality of lines of text;
a second abnormality type determination subunit configured to extract abnormality features of the plurality of lines of text;
And the third abnormality type determining subunit is used for determining the abnormality type of the abnormality information according to the preset rule and the abnormality characteristic.
Optionally, the third anomaly type determining subunit may include:
The java type conversion unit is used for converting the abnormal information into target abnormal information of the java type when the abnormal characteristics corresponding to the abnormal information are designated abnormal characteristics;
The target abnormal information determining unit is used for determining whether the app package name and the view type contained in the target abnormal information are consistent with the information recorded in the android system;
And the invisible UI operation interface type determining unit is used for determining the abnormal information as the invisible UI operation interface type in the first abnormal type when the app package name and the view type contained in the target abnormal information are respectively consistent with the app package name and the view type in the android system and the view control is invisible.
Optionally, the device further includes:
And the crash instruction sending unit is used for sending a software crash instruction to the android system if the type of the abnormal information is a preset second abnormal type after the abnormal type determining unit is executed, wherein the second abnormal type comprises other types except the first abnormal type.
The android application software control device provided by the embodiment of the application can be applied to android application software control equipment. The android application software control device may be a terminal. Fig. 7 shows a hardware structure block diagram of the android application software control apparatus, and referring to fig. 7, the hardware structure of the android application software control apparatus may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4;
In the embodiment of the application, the number of the processor 1, the communication interface 2, the memory 3 and the communication bus 4 is at least one, and the processor 1, the communication interface 2 and the memory 3 complete the communication with each other through the communication bus 4;
The processor 1 may be a central processing unit CPU, or an Application-specific integrated Circuit ASIC (Application SPECIFIC INTEGRATED Circuit), or one or more integrated circuits configured to implement embodiments of the present invention, etc.;
The memory 3 may comprise a high-speed RAM memory, and may further comprise a non-volatile memory (non-volatile memory) or the like, such as at least one magnetic disk memory;
wherein the memory stores a program, the processor is operable to invoke the program stored in the memory, the program operable to:
Obtaining abnormal information from an android system;
Determining the abnormality type of the abnormality information according to a preset rule;
And if the abnormal type of the abnormal information is the preset first abnormal type, sending a software continuous operation instruction to the android system.
The embodiment of the present application also provides a storage medium storing a program adapted to be executed by a processor, the program being configured to:
Obtaining abnormal information from an android system;
Determining the abnormality type of the abnormality information according to a preset rule;
And if the abnormal type of the abnormal information is the preset first abnormal type, sending a software continuous operation instruction to the android system.
Alternatively, the refinement function and the extension function of the program may be described with reference to the above.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the present specification, each embodiment is described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and each embodiment may be combined with each other, and the same similar parts may be referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. The android application software control method is characterized by comprising the following steps of:
Obtaining abnormal information from an android system;
Determining the abnormality type of the abnormality information according to a preset rule;
If the abnormal type of the abnormal information is a preset first abnormal type, sending a software continuous operation instruction to an android system;
the determining the abnormality type of the abnormality information according to a preset rule comprises the following steps:
converting the abnormal information into a plurality of lines of text;
extracting abnormal characteristics of the plurality of lines of text;
determining the abnormality type of the abnormality information according to the preset rule and the abnormality characteristic;
the determining the abnormality type of the abnormality information according to the preset rule and the abnormality feature includes:
If the abnormal characteristics corresponding to the abnormal information are the appointed abnormal characteristics, converting the abnormal information into java type target abnormal information;
Determining whether the app package name and the view type contained in the target abnormal information are consistent with the information recorded in the android system;
And when the app package name and the view type contained in the target exception information are respectively consistent with the app package name and the view type in the android system, and the view control is invisible, determining the exception information as a non-visible UI operation interface type in the first exception type.
2. The method of claim 1, wherein the obtaining exception information from the android system comprises:
and acquiring the abnormal information from the android system by using a preset abnormal capturing instruction, wherein the preset abnormal capturing instruction is inserted into a message queue of a Hanlder mechanism of the android system.
3. The method according to claim 2, wherein the obtaining the exception information from the android system by using a preset capturing exception instruction includes:
An interface for capturing the abnormality, which is provided by the android system, is accessed;
and acquiring the abnormal information of the android system from an interface for capturing the abnormality provided by the android system by utilizing the abnormal capturing instruction.
4. A method according to any of claims 1-3, wherein the first exception type comprises a system bug hole type, a non-visible UI operator interface type.
5. The method according to claim 4, further comprising, after the determining of the abnormality type of the abnormality information according to a preset rule:
And if the type of the abnormal information is a preset second abnormal type, sending a software crash instruction to the android system, wherein the second abnormal type comprises other types except the first abnormal type.
6. An android application software control device, which is characterized by comprising:
the abnormal acquisition unit is used for acquiring abnormal information from the android system;
an anomaly type determining unit for determining an anomaly type of the anomaly information according to a preset rule;
the instruction sending unit is used for sending a software continuous operation instruction to the android system if the abnormality type of the abnormality information is a preset first abnormality type;
The abnormality type determination unit includes:
A first abnormality type determination subunit configured to convert the abnormality information into a plurality of lines of text;
a second abnormality type determination subunit configured to extract abnormality features of the plurality of lines of text;
The third abnormality type determining subunit is used for determining the abnormality type of the abnormality information according to the preset rule and the abnormality characteristic;
the third abnormality type determination subunit includes:
The java type conversion unit is used for converting the abnormal information into target abnormal information of the java type when the abnormal characteristics corresponding to the abnormal information are designated abnormal characteristics;
The target abnormal information determining unit is used for determining whether the app package name and the view type contained in the target abnormal information are consistent with the information recorded in the android system;
And the invisible UI operation interface type determining unit is used for determining the abnormal information as the invisible UI operation interface type in the first abnormal type when the app package name and the view type contained in the target abnormal information are respectively consistent with the app package name and the view type in the android system and the view control is invisible.
7. The apparatus according to claim 6, wherein the abnormality acquisition unit includes:
The instruction capturing exception unit is used for acquiring exception information from the android system by utilizing a preset capturing exception instruction, wherein the preset capturing exception instruction is inserted into a message queue of a Hanlder mechanism of the android system.
8. The apparatus of claim 7, wherein the instruction capture exception unit comprises:
the first instruction capturing exception subunit is used for accessing an interface for capturing exception provided by the android system;
And the second instruction capturing exception subunit is used for acquiring exception information of the android system from an exception capturing interface provided by the android system by utilizing the exception capturing instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111275505.5A CN113900851B (en) | 2021-10-29 | 2021-10-29 | Android application software control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111275505.5A CN113900851B (en) | 2021-10-29 | 2021-10-29 | Android application software control method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113900851A CN113900851A (en) | 2022-01-07 |
| CN113900851B true CN113900851B (en) | 2024-06-25 |
Family
ID=79027085
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111275505.5A Active CN113900851B (en) | 2021-10-29 | 2021-10-29 | Android application software control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113900851B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708655A (en) * | 2020-06-19 | 2020-09-25 | 北京达佳互联信息技术有限公司 | Application crash processing method, device and system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0965923A3 (en) * | 1998-06-19 | 2001-04-04 | Intellution Inc. | System and method for secure software component containment |
| CA2347404C (en) * | 2001-05-10 | 2008-11-18 | Corel Corporation | System and method for recovering applications |
| CN108334415A (en) * | 2017-01-20 | 2018-07-27 | 百度在线网络技术（北京）有限公司 | A kind of fault-tolerance processing method, device, terminal and storage medium |
| CN107391295A (en) * | 2017-08-11 | 2017-11-24 | 东软集团股份有限公司 | The processing method and processing device of application exception |
| CN108345542B (en) * | 2018-02-28 | 2021-01-29 | 腾讯科技（深圳）有限公司 | Method and device for processing exception in application program |
| CN109766205A (en) * | 2018-12-19 | 2019-05-17 | 益萃网络科技（中国）有限公司 | Abnormality eliminating method, device, computer equipment and storage medium |
| CN110765007A (en) * | 2019-09-29 | 2020-02-07 | 南京大学 | Crash information online analysis method for android application |
-
2021
- 2021-10-29 CN CN202111275505.5A patent/CN113900851B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708655A (en) * | 2020-06-19 | 2020-09-25 | 北京达佳互联信息技术有限公司 | Application crash processing method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113900851A (en) | 2022-01-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108804299B (en) | Application program exception handling method and device | |
| US8788944B1 (en) | Personalized mobile device application presentation using photograph-based capability detection | |
| US8516308B1 (en) | Crash based incompatibility prediction for classes of mobile devices crash data | |
| WO2020024407A1 (en) | Electronic device, method for intelligently processing car insurance claim, and storage medium | |
| CN107390983B (en) | Service instruction execution method, client and storage medium | |
| US9372776B2 (en) | Monitoring user activity and performance of computerized devices | |
| CN109684008B (en) | Card rendering method, device, terminal and computer readable storage medium | |
| CN111552633A (en) | Interface abnormal call testing method and device, computer equipment and storage medium | |
| CN111130987A (en) | Automatic acquisition method and device for AWR report, electronic equipment and storage medium | |
| US20190369825A1 (en) | Electronic device and method for providing information related to image to application through input unit | |
| CN111831542B (en) | API application debugging method and device and storage medium | |
| CN113127320B (en) | Application program abnormity detection method, device, equipment and system | |
| WO2017206476A1 (en) | Method, device and apparatus for detecting cpu occupation | |
| US8572553B2 (en) | Systems and methods for providing feedback for software components | |
| CN116244138A (en) | Method and device for identifying abnormal operation of application, electronic equipment and storage medium | |
| CN111522706A (en) | Method and device for monitoring page abnormity of front-end application | |
| CN113050921A (en) | Webpage conversion method, device, storage medium and computer equipment | |
| US8161496B2 (en) | Positive and negative event-based testing | |
| CN112597828B (en) | Webpage recognition model training method and device and webpage recognition method | |
| CN113900851B (en) | Android application software control method and device | |
| CN104657248A (en) | Java thread stack analysis method and system | |
| CN115017428A (en) | Information display method, device, system and storage medium | |
| CN112307386A (en) | Information monitoring method, system, electronic device and computer readable storage medium | |
| CN109684156B (en) | Monitoring method, device, terminal and storage medium based on mixed mode application | |
| US20210382764A1 (en) | Comparisons of application programming interface interactions to determine compatibilities |
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 |