CN107992308B - Plug-in management method for android terminal application program - Google Patents
Plug-in management method for android terminal application program Download PDFInfo
- Publication number
- CN107992308B CN107992308B CN201711176728.XA CN201711176728A CN107992308B CN 107992308 B CN107992308 B CN 107992308B CN 201711176728 A CN201711176728 A CN 201711176728A CN 107992308 B CN107992308 B CN 107992308B
- Authority
- CN
- China
- Prior art keywords
- plug
- manager
- host application
- server
- management method
- 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
Images
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/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a plug-in management method of an android terminal application program, which is characterized in that a plug-in byte code resource path is added into a system resource path set to ensure that a plug-in can directly use a resource file of the plug-in without depending on a host; supporting the plug-in to start a plurality of Service components simultaneously; supporting the plug-in to use the dynamic shared library file of the third party; the plug-in manager can be updated automatically without relying on the host application.
Description
Technical Field
The invention belongs to the technical field of intelligent terminals, and particularly relates to a plug-in management method for an android terminal application program.
Background
With the advent of the Android operating system, the influence of the mobile embedded device changes due to the natural turnover. Nowadays, users increasingly rely on terminal applications based on the Android system, and the functions of the applications are continuously improved and expanded. Therefore, many Android applications in the market become too cumbersome, which causes inconvenience to the expansion of application functions. By using the plug-in technology, an application program (host) which is already installed in the Android system can run the APK files which are not recognized and installed by the Android system. Therefore, the flexibility of application program extension and update is greatly improved.
According to the common Android plug-in technology at present, after the validity of the plug-in is checked, the plug-in is analyzed, a sandbox environment is created in a host program, the host and a resource manager of a system are used, the program and the method in the plug-in are called in a reflection mode, and the plug-in is started.
The technical scheme in the prior art has the following defects:
firstly, the plug-in resource manager depends on a host program and cannot independently use related resource files in the plug-in files;
secondly, the plug-in is not supported to start a plurality of Service components simultaneously;
thirdly, the plug-in manager is embedded in the host application APK, does not support the dynamic update of the plug-in manager, and needs to be updated together with the host application program.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a plug-in management method for an android terminal application program.
1. And starting the host application program, checking the version of the plug-in manager, downloading the plug-in manager with the latest version from the server side through the network, and checking the integrity of the plug-in manager.
2. And initializing a plug-in manager, and performing interception operation when the Android system creates an Activity component and a Service component to replace the specified class loader.
3. And loading the plug-in, firstly downloading the APK file of the plug-in with the latest version from the server, checking the integrity, and starting an independent thread to carry out asynchronous loading after the check is passed.
4. Starting the running plug-in, and using the plug-in related function comprises the following aspects:
a plug-in interface is operated, and a user can interact with the plug-in interface through behaviors such as touch, key pressing, voice input and the like;
one or more Service components are operated to independently complete some logic tasks, and feedback information is displayed to a user through interface interaction;
loading a dynamic shared library file prefabricated in the running plug-in unit, and performing more efficient operation;
the calling of the function encapsulated by the plug-in application program can realize cooperative communication with the host application in a multithreading mode.
Therefore, the method and the device realize that the byte code resource path of the plug-in is added into the system resource path set, and ensure that the plug-in can directly use the resource file of the plug-in without depending on a host; supporting the plug-in to start a plurality of Service components simultaneously; supporting the plug-in to use the dynamic shared library file of the third party; the plug-in manager can be updated automatically without relying on the host application. The plug-in management method of the android terminal application program specifically comprises the following steps:
s101, starting a host application program and establishing a sandbox process of the Android application;
s102, reading the version of the plug-in manager in the host application, and sending a network request to a server end to upload the version value;
s103, receiving update data of the plug-in manager issued by the server;
s104, judging whether the plug-in manager needs to be updated or not; if the judgment result is that updating is needed, executing S105, and if the judgment result is that updating is not needed, entering step S107;
s105, downloading the plug-in manager by the host application;
s106, judging whether the integrity of the downloaded plug-in manager is correct or not, and executing S107 if the integrity is judged to be correct; if the integrity is judged to be incorrect, returning to S105;
s107, initializing a plug-in manager;
s108, checking the plug-in version in the host application; s109, judging whether the plug-in needs to be updated, if so, entering the step S110, and if not, entering the step S112;
s110, the host application downloads the plug-in APK file;
s111, judging whether the plug-in is downloaded successfully, if so, entering the step S112, and if not, re-executing the step S110;
s112, loading the plug-in, and initializing a resource manager and a class loader of the plug-in; according to a preferred embodiment of the present invention, the class loader of the plug-in preferentially searches the class file related to the plug-in package name;
s113, the user uses the plug-in to realize the specific application function through the plug-in;
and S114, finishing the related operation and exiting the host application program.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood and to implement them in accordance with the contents of the description, the following detailed description is given with reference to the preferred embodiments of the present invention and the accompanying drawings.
Drawings
FIG. 1 illustrates a plug-in management flow diagram according to one embodiment of the invention;
FIG. 2 illustrates a flowchart for initializing a plug-in manager according to one embodiment of the invention;
FIG. 3 illustrates a further plug-in management flow diagram according to an embodiment of the present invention.
Detailed Description
To further illustrate the technical means and effects of the present invention adopted to achieve the predetermined purpose, the following detailed description will be given to the specific implementation, features and effects of the plug-in management method for android terminal application according to the present invention with reference to the accompanying drawings and preferred embodiments. In the following description, different "one embodiment" or "an embodiment" refers to not necessarily the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
The terminology used in the present invention is as follows:
android, namely translating Chinese into Android, wherein the Linux-based operating system of free and open source codes 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;
APK: the method is an application program installation file format on an Android operating system, and the application program installation file format is all called as an Android application package in English;
the Activity component is an application component in the Android system and responsible for creating a window display interface;
a Service component: the method refers to an application component which has no user interface and runs in the background to execute time-consuming operation in the Android system.
In an embodiment of the present invention, the plug-in management method specifically includes:
s101, starting a host application program and establishing a sandbox process of the Android application; the sandbox process means that the Android allocates a separate space to each APK process, and a sandbox is created for the APK process to prevent other applications from being influenced (or other applications from influencing the APK process);
s102, reading the version of the plug-in manager in the host application, and sending a network request to a server end to upload the version value;
s103, receiving update data of the plug-in manager issued by the server; according to a preferred embodiment of the present invention, if no update is required, the received update data is null;
s104, judging whether the plug-in manager needs to be updated or not; if the judgment result is that updating is needed, executing S105, and if the judgment result is that updating is not needed, entering step S107;
s105, downloading the plug-in manager by the host application; according to a preferred embodiment of the present invention, after the downloading of the plug-in manager is completed, the integrity of the downloaded file is calculated through a predetermined algorithm;
s106, judging whether the integrity of the downloaded plug-in manager is correct or not, and executing S107 if the integrity is judged to be correct; if the integrity is judged to be incorrect, returning to S105; according to a preferred embodiment of the invention, integrity judgment can be carried out by calculating the md5 value of the downloaded plug-in manager, and the calculated md5 value of the plug-in manager is compared with the md5 value issued by the server, if the md5 value of the plug-in manager is consistent with the md5 value of the server, integrity is indicated, and if the md5 value of the plug-in manager is inconsistent with the md5 value of the server, integrity is indicated;
s107, initializing a plug-in manager; according to a preferred embodiment of the invention, when an Android system creates an Activity component and a Service component, an interception operation is carried out to replace a specified class loader;
s108, checking the plug-in version in the host application; according to a preferred embodiment of the invention, firstly, reading the version of the plug-in, sending a network request to a server to check whether the plug-in needs to be updated, and finally obtaining update data sent by the server;
s109, judging whether the plug-in needs to be updated, if so, entering the step S110, and if not, entering the step S112;
s110, the host application downloads the plug-in APK file; according to a preferred embodiment of the invention, the plug-in can be downloaded to the readable and writable catalog of the host application through the url address issued by the server;
s111, judging whether the plug-in is downloaded successfully, if so, entering the step S112, and if not, re-executing the step S110;
s112, loading the plug-in, and initializing a resource manager and a class loader of the plug-in; according to a preferred embodiment of the present invention, the class loader of the plug-in preferentially searches the class file related to the plug-in package name;
s113, the user uses the plug-in to realize the specific application function through the plug-in;
and S114, finishing the related operation and exiting the host application program.
According to a preferred embodiment of the present invention, the specific functional applications include:
the method comprises the steps of running a plug-in interface, running a Service component of the plug-in, running a plug-in dynamic sharing library and calling a function which is open to the outside of the plug-in a host application program; wherein:
the operation plug-in interface is a functional module used for interacting with a user and supporting the user to perform interaction operation by touching a screen, clicking a virtual key, inputting voice and the like;
the Service component of the running plug-in supports the plug-in to start one or more Service components, and the backstage runs independently;
the dynamic Shared library is named Shared Object in English, is similar to DLL of Windows, can load and execute C/C + + codes when a program runs, and can provide high operation efficiency. And calling a function which is opened by the plug-in to the outside in the host application program to acquire the data returned by use.
As shown in fig. 2, according to an embodiment of the present invention, the initializing plug-in manager in S107 specifically includes the following processes:
s201, adding a self-defined Instrumentation instrument into an Android system; according to a preferred embodiment of the invention, when an Android system creates an Activity component or a Service component, a user-defined Instrumentation instrument is preferentially executed, and a registered ClassLoader class loader can be correctly used;
s202, registering and caching the ClassLoader class loader in the plug-in manager downloaded in the step S105;
s203, initializing a manager of the dynamic sharing library of the plug-ins, setting a designated directory to uniformly manage the files of the dynamic sharing library of all the plug-ins, ensuring that each plug-in can only load the own dynamic sharing library, and avoiding unnecessary confusion;
s204, initializing a proxy Service component pool, extracting and using the Service component from the proxy Service component pool when the plug-in starts the Service component, and returning after the use is finished.
After the host application program is installed, when an Android mobile phone is used, in a mobile phone networking state, if an application icon is clicked, a certain specified url is requested in a background to check and update the plug-in manager and the plug-ins, and then APK files such as Dolphin. As shown in fig. 3, according to a plug-in management embodiment of an embodiment of the present invention:
s301, starting a host application program;
s302, reading the version of the plug-in manager in the host application program, for example, the read version of the plug-in manager is 101, and sending a network request to a server end to upload the version value; the server-side address is, for examplewww.plugin- manager.php；
S303, receiving the update data of the plug-in manager issued by the server; according to a preferred embodiment of the present invention, since the uploaded version value is 101, the version value returned by the server is 102 at this time, and the specific contents are as follows: 102, url, www.plugin-manager, php/102/PluginManager, apk, md5, abcdefgh 12345678;
s304, downloading a plug-in manager PluginManager. apk file according to url content; download plug-in manager plug-manager. apk file, e.g. according to www.plugin-manager. php/102/plug-manager. apk;
s305, judging whether the integrity of the downloaded plug-in manager PluginManagerapk file is correct, calculating the md5 hash value of the PluginManagerapk file, comparing the hash value with an md5 value abcdefgh12345678 issued by a server, if the hash value is the same, entering S306, and if the hash value is different, re-executing 305;
s306, initializing a plug-in manager; according to a preferred embodiment of the invention, when an Android system creates an Activity component and a Service component, an interception operation is carried out to replace a specified class loader;
s307, checking the Dolphin plug-in version in the host application and uploading the version value to a background server; according to a preferred embodiment of the present invention, for example, if the checked Dolphin plug-in version is 101, the version value is uploaded to the backend server (www.plugin.php);
s308, receiving plug-in update data sent by a server, wherein according to a preferred embodiment of the invention, the content is { "version": 102, "url": www.plugin.php/102/Dolphin.apk "," md5 ": 12345678 abcdefgh" };
s309, downloading plug-in Dolphin.apk file by the host application; according to a preferred embodiment of the invention, the plug-in can be downloaded to the readable and writable catalog of the host application through the url address issued by the server;
s310, judging whether the integrity of the downloaded Dolphin.apk plug-in is correct, calculating the md5 hash value of the Dolphin.apk, comparing the hash value with the md5 value sent by the server, for example, if the md5 value is 12345678abcdefgh, if the same, entering the step S112, and if the different, re-executing the step S309;
s311, loading the plug-in, and initializing the resource manager and the class loader of the plug-in; according to a preferred embodiment of the present invention, the class loader dolphin plugin classloader of the plug-in will preferentially search the class file associated with the plug-in package name;
s312, clicking the host icon by the user, and entering the plug-in Dolphin;
s313, finishing the relevant operation and exiting the host application program.
By implementing the technical scheme of the invention, the configuration and the expansion of the functional module of the Android application program can be effectively improved, the plug-in manager and the plug-in APK file can be dynamically updated and managed, the update can be rapidly upgraded, and the later maintenance and release cost of the Android application program is reduced. The development process of the plug-in is basically consistent with that of common Android application development, and the research and development cost of a research and development team is reduced. The plug-in manager enables the originally bloated Android program structure modules to be clearer, reduces the coupling among the modules and enhances the usability and the expandability of the Android application program.
Although the present invention has been described with reference to a preferred embodiment, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (8)
1. A plug-in management method for an application program of an android terminal is characterized by comprising the following steps:
s101: starting a host application program, and establishing a sandbox process of the Android application;
s102: reading the version of the plug-in manager in the host application, and sending a network request to a server side to upload the version value;
s103: receiving update data of a plug-in manager issued by a server;
s104: judging whether the plug-in manager needs to be updated or not; if the judgment result is that updating is needed, executing S105, and if the judgment result is that updating is not needed, entering step S107;
s105: a host application download plug-in manager;
s106: judging whether the integrity of the downloaded plug-in manager is correct or not, and executing S107 if the integrity is judged to be correct; if the integrity is judged to be incorrect, returning to S105;
s107: initializing a plug-in manager;
s108: checking the plug-in version in the host application;
s109: judging whether the plug-in needs to be updated, if so, entering step S110, and if not, entering step S112;
s110: the host application downloads the plug-in APK file;
s111: judging whether the plug-in is downloaded successfully or not, if so, entering the step S112, and if not, re-executing the step S110;
s112: loading a plug-in, and initializing a resource manager and a class loader of the plug-in; the class loader of the plug-in preferentially searches class files related to the plug-in package name;
s113: the user uses the plug-in to realize the specific application function through the plug-in;
s114: finishing the relevant operation and exiting the host application program;
the initializing plug-in manager in S107 specifically includes the following procedures:
s201: adding a self-defined Instrumentation instrument to the Android system;
s202: registering and caching the ClassLoader class loader in the plug-in manager downloaded in the step S105;
s203: initializing a manager of the dynamic sharing library of the plug-ins, setting a designated directory to uniformly manage the dynamic sharing library files of all the plug-ins, ensuring that each plug-in can only load the own dynamic sharing library, and avoiding unnecessary confusion;
s204: and initializing a proxy Service component pool, extracting and using the Service component from the proxy Service component pool when the plug-in starts the Service component, and returning after the use is finished.
2. The android terminal application plug-in management method of claim 1, comprising:
and when the update data of the plug-in manager issued by the server end is received, if the update is not needed, the received update data is null.
3. The android terminal application plug-in management method of claim 1 or 2, characterized in that:
after the download of the plug-in manager is completed, the integrity of the downloaded file will also be calculated by a predetermined algorithm.
4. The android terminal application plug-in management method of claim 3, wherein:
and (3) carrying out integrity judgment by calculating the md5 value of the downloaded plug-in manager, and comparing the calculated md5 value of the plug-in manager with the md5 value issued by the server, wherein if the md5 value of the plug-in manager is consistent with the md5 value issued by the server, the integrity is correct, and if the md5 value of the plug-in manager is inconsistent with the md5 value, the integrity is incorrect.
5. The android terminal application plug-in management method of claim 1, comprising:
the checking the plug-in version in the host application further comprises:
firstly, reading the version of the plug-in, sending a network request to a server to check whether the plug-in needs to be updated, and finally obtaining update data sent by the server.
6. The android terminal application plug-in management method of claim 1, comprising:
the host application downloads the plug-in APK file, and further comprises the following steps:
and downloading the plug-in to the readable and writable directory of the host application through the url address issued by the server.
7. The android terminal application plug-in management method of claim 1, comprising:
the user uses the plug-in, and the specific application functions realized by the plug-in comprise:
the method comprises the steps of running a plug-in interface, running a Service component of the plug-in, running a dynamic sharing library of the plug-in and calling a function which is open to the outside of the plug-in a host application program.
8. The android terminal application plug-in management method of claim 7, wherein:
the operation plug-in interface is a functional module used for interacting with a user and supporting the user to perform interaction operation by touching a screen, clicking a virtual key and inputting voice;
the Service component of the running plug-in supports the plug-in to start one or more Service components, and the backstage runs independently;
and calling a function which is opened by the plug-in to the outside in the host application program to acquire the data returned by use.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711176728.XA CN107992308B (en) | 2017-11-22 | 2017-11-22 | Plug-in management method for android terminal application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711176728.XA CN107992308B (en) | 2017-11-22 | 2017-11-22 | Plug-in management method for android terminal application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107992308A CN107992308A (en) | 2018-05-04 |
| CN107992308B true CN107992308B (en) | 2020-10-20 |
Family
ID=62032704
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711176728.XA Active CN107992308B (en) | 2017-11-22 | 2017-11-22 | Plug-in management method for android terminal application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107992308B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108664265A (en) * | 2018-05-15 | 2018-10-16 | 玩咖欢聚文化传媒（北京）有限公司 | The interpolation method and system of Android application program |
| CN109388416A (en) * | 2018-09-29 | 2019-02-26 | 智器云南京信息科技有限公司 | A kind of plug-in unit realization method and system of application software |
| CN111399927B (en) * | 2018-12-14 | 2024-06-18 | 北京奇虎科技有限公司 | Method and device for sharing Class files by application and computing equipment |
| CN109725952B (en) * | 2019-01-07 | 2021-09-24 | 深圳市网心科技有限公司 | A method, system and related device for application plug-in |
| CN109891385B (en) * | 2019-01-10 | 2023-02-10 | 福建联迪商用设备有限公司 | Method and terminal for installing POS machine initialization configuration information |
| CN110209416A (en) * | 2019-05-31 | 2019-09-06 | 彩讯科技股份有限公司 | Application software update method, device, terminal and storage medium |
| CN111258587B (en) * | 2020-01-17 | 2023-08-22 | 苏宁云计算有限公司 | Android application plug-in implementation method, device, equipment and storage medium |
| CN112148332B (en) * | 2020-09-30 | 2023-09-05 | 亮风台（上海）信息科技有限公司 | Tool system, updating method thereof, terminal device and storage medium |
| CN112148414B (en) * | 2020-09-30 | 2024-05-31 | 亮风台（上海）信息科技有限公司 | Interactive response method and system of interface and terminal equipment |
| CN112732314A (en) * | 2020-12-30 | 2021-04-30 | 北京一亩田新农网络科技有限公司 | Plug-in differential packaging method and device based on android, electronic equipment and computer readable medium |
| CN114117409A (en) * | 2021-11-19 | 2022-03-01 | 上海商汤临港智能科技有限公司 | User code operation method and device, electronic equipment and storage medium |
| CN115430140A (en) * | 2022-07-28 | 2022-12-06 | 完美世界(重庆)互动科技有限公司 | Extended tool management method and device |
| CN118760480B (en) * | 2024-06-05 | 2025-03-11 | 北京蓝犀牛信息技术有限公司 | Android-based application plug-in method and device, storage medium and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714828A (en) * | 2015-03-31 | 2015-06-17 | 北京奇虎科技有限公司 | Methods and devices for installing and operating application |
| CN105893094A (en) * | 2016-03-31 | 2016-08-24 | 百度在线网络技术（北京）有限公司 | Achieving method and device for application program plug-in |
| CN105955787A (en) * | 2016-05-18 | 2016-09-21 | 深圳市掌玩网络技术有限公司 | Method and device used for loading plug-in of Android system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902265B (en) * | 2012-12-26 | 2018-01-09 | 腾讯科技（深圳）有限公司 | One kind applies implementation method and relevant apparatus |
-
2017
- 2017-11-22 CN CN201711176728.XA patent/CN107992308B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714828A (en) * | 2015-03-31 | 2015-06-17 | 北京奇虎科技有限公司 | Methods and devices for installing and operating application |
| CN105893094A (en) * | 2016-03-31 | 2016-08-24 | 百度在线网络技术（北京）有限公司 | Achieving method and device for application program plug-in |
| CN105955787A (en) * | 2016-05-18 | 2016-09-21 | 深圳市掌玩网络技术有限公司 | Method and device used for loading plug-in of Android system |
Non-Patent Citations (1)
| Title |
|---|
| Android 插件化原理解析——Service的插件化;omnispace;《CSDN：https://blog.csdn.net/omnispace/article/details/73320933》;20170616;第7页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107992308A (en) | 2018-05-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107992308B (en) | Plug-in management method for android terminal application program | |
| US9367403B2 (en) | Terminal and application restoring method | |
| CN106325847B (en) | Method and device for acquiring application program function based on iOS platform | |
| US7899959B2 (en) | Method of loading software in mobile and desktop environments | |
| CN105786538B (en) | software upgrading method and device based on android system | |
| CN107015870B (en) | Method and device for realizing communication between web page and local application and electronic equipment | |
| CN111427594B (en) | Application program running method and device | |
| CN104506639A (en) | A method and device for obtaining root authority | |
| CN102932441A (en) | Method and system for downloading application, terminal and server | |
| US20170351507A1 (en) | Silent upgrade of software with dependencies | |
| CN105516154A (en) | Security policy configuration method and device applied to SEAndroid (Security-Enhanced Android) system | |
| CN110221840B (en) | Function implementation method and device of application program, equipment and storage medium | |
| CN112162795A (en) | Plug-in starting method and device, computer equipment and storage medium | |
| CN111026408A (en) | Method and device for managing application and computer storage medium | |
| CN112612493B (en) | Software upgrade method, device, equipment and storage medium for software set | |
| EP2972829A1 (en) | Modification of compiled applications and application management using retrievable policies | |
| CN101895883A (en) | Smart card supporting authentication arithmetic update and method for updating authentication arithmetic | |
| CN107729042A (en) | Mobile solution upgrade method and device, storage medium, electronic equipment | |
| CN113094064A (en) | Gateway software module upgrading method, device, equipment and storage medium | |
| CN107193565B (en) | How to develop native apps across mobile terminals | |
| CN113760306A (en) | Method and device for installing software, electronic equipment and storage medium | |
| CN115129348A (en) | Resource updating method, device and equipment of application program and readable storage medium | |
| CN114417322A (en) | Application isolation implementation method, mobile terminal, computer equipment and storage medium | |
| CN109144544A (en) | Application program update method, system and device used in a kind of bank | |
| CN106484476B (en) | Method, device and intelligent terminal for deleting multi-open application |
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 |