Xposed 3.0 ALPHA 4 für Lollipop {5.0.2}


AP - Maskottchen

It seems that many people have waited for this moment, and here we are:

Xposed for Lollipop is finally here!
You can find a list with Q&A on the XDA Portal. Please read it, you will find many answers there.

Note that this is still an alpha version and for Lollipop 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 @ xda:
: 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.

How to install Xposed Framework on Android Lollipop 5.0
Xposed has finally been released for Android 5.0 Lollipop. Previously the lead developer already released several screenshots but has now finally officially launched the popular framework for Android Lollipop.

Xposed is currently in alpha version and for Lollipop on ARMv7+ devices only. The installation process isn’t easy and has to be performed manually in a custom recovery, we will take a look at both the installation process and how to use Xposed.


  • ARMv7+ device
  • Custom Recovery installed
  • Have “unknown sources” enabled
  • Run Android 5.0 Lollipop
  • Download the Framework.zip file and XposedInstaller.apk file (download links bellow)

How to install Xposed Framework on Android Lollipop 5.0

  1. First, we highly recommend you make a backup of your device. You can learn how to do so here
  2. First, Download Xposed Framework Lollipop.zip
  3. Then download Xposed Framework Lollipop.apk file
  4. Boot into custom recovery
  5. Flash the previously downloaded .zip files
  6. Navigate to Install from .zip and then select the ”xposed-arm.zip”
  7. Once finished, make sure to reboot your system.
  8. Once your device is back on, install the “XposedInstaller_3.0-alpha.apk” app
  9. A menu will pop up, press “Install” and then “Open”
  10. It should look something like this: Xposed-Framework-Lollipop.jpg

Xposed For Lollipop well known issues and Troubleshooting

Since Xposed for Android 5.0 is still in Alpha there are many users that have already encountered some issues. Here is a list of well known issues:

  • It seems to boot loop on Samsung stock ROMs
  • If you have downloaded the files within the first hour, your phone boots but the installer says that the framework is not installed, please download the updated version and flash again. XposedBridge version must be 61 afterwards.
  • the app_process version is not displayed, it’s just a display error that can be ignored (will be fixed later).

How to fix the Xposed app Missing Framework issue

One of the more frequent issues we see that can be prevented is the Missing Framework problem. Here is how to fix it:

  1. boot back into custom recovery
  2. flash the Framework ZIP (xposed-arm.zip) again
  3. The issue should be resolved. If it isn’t, continue to step 4.
  4. try installing any module and Activate it
  5. Then reboot your Android device
  6. Check if the framework is active once your device has rebooted.

Xposed Android 5.0 Lollipop app_process showing blank


Many users have complained about App_Process showing no information. This is because the Xposed Framework is currently in Alpha. The only thing that should show information is XposedBridge.jar which should show number 61

- See more at: http://www.amongtech.com/how-to-install-xposed-framework-on-android-lollipop-5-0/#sthash.ViJwEeZ2.dpuf

[Sammlung] Lollipop Xposed kompatible Module
[OFFICIAL] Xposed for Lollipop
Zuletzt bearbeitet:

G Tom

Teammitglied a. D
Schon wer von euch probiert? :)
Bin momentan nicht auf L, kann daher nicht testen :(

Gesendet von meinem LG-E975 mit Hilfe von Android-Port


AP - Maskottchen
News/Status vom Dev

Current status (Feb 19):

The most important issue seems to be the incompatibility with Samsung stock ROMs, especially because it's leading to boot loops. I have been working hard on fixing this in the days since the release, however it's not just a single spot that needs fixing. Thanks to GermainZ for testing and providing good log files! So far, I have detected the following issues:
- Enhanced .oat file format: Samsung has added a "TypeLookupTable", probably for performance reasons. The table itself will be ignored by Xposed, but it also means that the file format is slightly different. I have finally understood what they have done and added some logic to skip the referenes to this table.
- Different size of the String class: They have added a clear() method, which is unusual as strings are usually immutable. As this class is one of few that have special support in native code, I had to add one entry to the virtual table of the class.
- Additional fields in DexCache class: Offsets to some fields are different due to this and need to be handled in native code (as this another central class with native parts directly implemented in ART).
- Verifier rejects ViewDebug class: Doesn't seem to be overly critical to me, yet to be tested whether it's working fine with original libraries.
- Implementation missing for some native methods: Some methods in the reflection classes have been implemented in native code instead of Java. This means I will have to implement them as well.

The changes done by Samsung are bigger than I expected, especially given that ART is very complex and mostly undocumented. Anyway, I still think that once these issues have been overcome, it's better to replace the libaries than trying to manipulate data structures and behavior from "outside" (app_process). Think about it: If they have done such big changes, it's very likely that offsets in these data structures are different from AOSP and would need special handling as well.

It would of course be helpful to have an uninstaller ZIP in case you run into a bootloop. I didn't have time for that yet, but maybe someone can build an initial version that basically reverses the steps of the installer ZIP. For the ART libraries, that should be rather easy. You might want to stay away from moving app_process32 back in case you have SuperSU installed. It will need a special procedure to ensure you don't break either part or even your ROM.

There are other issues for sure, for example it seems that some methods cannot be hooked. That's something that needs more investigation, but I would like to fix the more critical issue like the ones for Samsung first.

That said, I won't be able to work on Xposed for the next days, definitely not before Monday. Keep in mind that this isn't my fulltime job and that an alpha phase might take some time. It would be illusionary to assume that we reach a stable state after a few days, with all the changes that have been done.


AP - Maskottchen
News vom Dev >>

Originally Posted by rovo89

One of the next steps will be the creation of some scripts that help me to compile and package Xposed. Apart from simplification for me, I hope that this might help other experienced developers to try and contribute themselves (e.g by analysing the issues they noticed themselves).

It took longer than expected, but I also think it's better than what I had planned originally:

I hope this makes it easier for others to compile the native parts of Xposed and the modified ART runtime themselves and get involved, just like @romracerdid. It also makes it easier for me to build and package the Xposed framework, as it was quite a hassle to make sure that all files are compiled correctly, pushed to my PC etc.


AP - Maskottchen
Update Time!

I have just uploaded a new flashable ZIP for Xposed 3.0 alpha3 (xposed-sdk21-arm-20150426.zip).

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.

- Fixed issues with replacing drawables
- Fixed NoSuchMethodError in handleInitPackageResources
- Possibly fixed some errors on ROMs that start in permissive SELinux mode and switch to enforcing mode later


AP - Maskottchen
OP Update & Info >>

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.

I will eventually support them as well, but as there are unofficial versions for these, I try to work on a few known issues for Android 5.0 before (when I find time for it).

Regarding Samsung ROMs: No progress. No ETA. No promise that it will be supported, although I don't exclude it either. It's simply unclear what further differences between their and AOSP's ART variant come up.