You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although VirtualXposed can run Xposed modules, there are some differences between Xposed and VirtualXposed:
VirtualXposed can not hook into system process, so the modules(eg: Gravity Box) which modify system process(such as system_server, systemui) can never work.
Methods which are too short(less than 2 assembly instructions) can not be hooked or not stable.(eg: methods with empty body or return constant directly) 。If the method is in your app, you can add redundant statement : Log.d("fake", "just for vxp") to avoid this.
When hook native method in VirtualXposed, you must load the corresponding so first. see:#39
IXposedHookZygoteInit hooks into app process, not zygote.
The field : isFirstApplication in XC_LoadPackage is always true.
Do not support Resources hooks.
When you need to call original method, please always use XposedBridge.invokeOriginalMethod()
How to know if app/modules run in VirtualXposed ?
if (System.getProperty("vxp") != null) {
// running in VirtualXposed
}