MIRROR
FLAT SCREEN MONITORS
Xposed Installer v3.0 alpha 4 v78 Apk
Requirements: Android 5.0+ | 5.1+ | 6.0+ ROOT
Overview: Xposed for Lollipop/Marshmallow is finally here!
Note that this is still an alpha version and for Lollipop/Marshmallow on ARMv7+ devices only.
Please install it only if you're willing to take the risk of boot loops. Just because it's working fine and stable for me doesn't mean it will work for everyone the same way.
Downloads:
xposed-arm-*.zip: Must be flashed with a custom recovery to install the framework.
XposedInstaller_3.0-alpha*.apk: Must be installed to manage installed modules
No, it's not using material design yet. Yes, there are more important topics for now.
XposedBridgeApi-20150213.jar: The API for module developers, in case they want to make use of some new features. Might be changed slightly until the stable release!
Known issues:
- It seems to boot loop on Samsung stock ROMs! Update: Samsung has changed quite a few things in their version of ART. It will take more time to adjust Xposed for it.
Xposed 3.0 alpha 4
It fixes bootloops and crashes on some ROMs, especially on Sony devices. In the logs, there used to be "Too many open files" errors.
You only need to flash the ZIP again, the Xposed Installer app remains the same (and therefore still shows version alpha2). If XposedBridge.jar has version 64 after a reboot, the new version is active.
As the question probably comes up:
- No, this version doesn't support Android 5.1 yet.
- No, this ZIP doesn't support arm64/x86 processors yet.
WHAT'S NEW:
v78
As promised, I have just uploaded version 78. It contains:
- [5.0 only] Bootloop on ROMs where the vendor has merged a recent security fix from 5.1
- [5.0/5.1 only] Backports of a few changes on Xposed that I had initially done for 6.0
- [6.0 only] Fix XModuleResources.createInstance() API method
- Fix for the invokeOriginalMethod() API method
Now, the 5.0, 5.1 and 6.0 ZIPs are in sync again. In the future, I plan to release ZIPs for all three Android versions at the same time again - even in case the changes affect only one version. I think that's better than having to keep track of the latest release per version. This time was an exception due to the backports that I needed to verify.