3 ms·

Looks a lot like XposedFramework: https://github.com/rovo89/XposedBridge/wiki/Development-tutorial https://github.com/rovo89/XposedBridge/wiki/Development-tuto

Looks a lot like XposedFramework: https://github.com/rovo89/XposedBridge/wiki/Development-tutorial https://github.com/rovo89/XposedBridge/wiki/Development-tuto... Xposed has allowed me to iterate much more rapidly on framework tweaks, and also keep them much cleaner (since now I just have the "hooks" instead of directly changing Android framework). Also, I can run on more devices because I don't have to replace some framework JAR which the vendor tweaked substantially.

britta 13y ago
saurik wrote a comparison of Xposed and Substrate that may be interesting to you: http://www.cydiasubstrate.com/id/34058d37-3198-414f-a696-73e97e0a80db/ http://www.cydiasubstrate.com/id/34058d37-3198-414f-a696-73e... > That said, at some level the libraries are fairly similar: the core mechanism by which a method is hooked in Xposed (swapping it out for a JNI implementation) is actually the same one that I described in the talk I gave on Substrate at a conference called Android Open in 2011. The result is that there are some similarities in the functionality offered by the two frameworks. > Thankfully, Substrate's injection mechanism does not conflict with the one used by Xposed: therefore, if users or developers would like to have both frameworks installed, that is actually possible. There are some places where the two libraries "disagree" (such as Xposed totally removing the Java security model that Substrate preserves), but the resulting behavior is harmless.