Originally Posted by Danation
Ah, I thought that even if you hooked to it within handleLoadPackage it would still run for every app, since it was for the global Activity class. Thank you for the correction. I'll go with that option. Thanks for your help!
It's limited because different processes have different memory, so hooking a method in one process doesn't have any effect on other processes. Only exception: Zygote is the parent process of every app, so changes done in the Zygote process before the app start are automatically inherited.
sent me a useful logcat and the libdvm.so file. I had a look at both and I have to say: Sorry, but they have modified Android way too much to be compatible with Xposed. There are files called "core.jar.jex" (instead of "core.jar.dex") and the library is full of methods related to a compiler called "jazz" - probably their own one. It seems to have be an Ahead-of-time compiler, a bit like ART, but yet completely different. No way I can support that.
Note that this error is related to the ROM - if there are ROMs for these devices which are closer to AOSP, Xposed might actually work on those.
mentioned that these ROMs are running on"Aliyun OS" - an Android fork that even Google declared as "incompatible with Android". If you have an AOSP-based ROM, it should work.
Tired of updating your mod for every new ROM release?
You want give users the possibility to combine different mods without creating tons of different files for all possible combinations?
Then have a look at my Xposed framework
- modifications without APK changes!