Search Results for "only one"

RePlugin is a complete Android plug-in solution which is suitable for general use. Apps do not need to be upgraded to support new components, even brand new plug-ins. With only ONE hook (ClassLoader), NO BINDER HOOK. RePlugin’s Crash ratio is as low as Ten thousandth (0.01%). In addition, RePlugin is compatible with almost ALL Android ROMs in the market. RePlugin supports almost all features seamlessly as an installed application, including static Receiver, Task-Affinity, user-defined Theme, AppCompat, DataBinding, etc. ...

...But if the iterative development in only one plugin module will make it more and more cluttered, for the code is deeply coupled. So an idea was raised. It could make sense to build a bytecode plugin platform, and the new feature can be extended based on it as a new plugin.

...The plugin will compile the source code with java8 and then replace the class files with the output of retrolambda. Set the java version to compile to. The default is 6. Only 5, 6 or 7 are accepted. The default version of retrolambda used is 'net.orfjackal.retrolambda:retrolambda:2.5.6'. If you want to use a different one, you can configure it in your dependencies. If you are running with java 6 or 7 you should really consider updating. First try updating to the latest version of the android gradle plugin. ...

Android, multidex, splitdex, subpackage plugin. The Gradle script was integrated into the plug-in, so that only one configuration file needs to be maintained. Readers can choose separate configuration or integrated configuration according to their own needs. In this way, we maintain the number of methods of the main Dex at about 15,000, and we no longer have to worry about the number of methods. Through the above official subcontracting, the original Dex has been divided into 1 master Dex and more slave Dex. ...

...Given its .apk file, the plugged app could be run either independently or as a plugin of the host, NO source code is needed. The plugged app are recognized as Installed by the host and other plugged apps. Very low level of code invasion, indeed just one line code to integrate DroidPlugin into the host app. Complete code level separation between host and plugged apps, only system-level message passing method provided by Android allowed. Resources management are also completely separated between host and plugged apps. Process management for plugged apps, idle processed of the plugged app will be timely recycled to guarantee minimum memory usage.