Version: 3.0 alpha3 (36)
Package: de.robv.android.xposed.installer
30,245 downloads
0.59 MB (619,547 bytes)
Min: Android 4.0.3 (Ice Cream Sandwich MR1, API 15)
Target: Android 4.0.3 (Ice Cream Sandwich MR1, API 15)
nodpi
Uploaded June 29, 2015 at 4:12PM UTC by Shamsheed
Download APK
There's a newer version available below!

Whoa there!

It looks like you're using an ad blocker, so you'll have to wait 15 more seconds.
Please whitelist this site to skip the wait and help us pay for bandwidth, hosting, and other bills.

APK Notes:

forum.xda-developers.com/showpost.php?p=61594046&postcount=10

I have just upload files for a big update. It includes many general improvements/changes and some smaller fixes.

One of the changes is that I decided to avoid confusion about all the different (yet similar) version numbers for installer, framework zip, app_process and XposedBridge by reducing it to two version numbers:
The framework (i.e. all the files in the flashable) zip is versioned with integers (65 for this release). This is at the same time the Xposed API version. Unofficial builds should use suffixes to label their releases.
The Xposed Installer app will continue to use the well-known, human-readable version numbers, e.g. 3.0 alpha3 for this release.

The next bigger change is the installation script in the flashable ZIP. I use a modified fork of BusyBox now to keep the scripts clean and work with a well-known environment. This should make it pretty reliable, even in case some weird recoveries forget to include the "unzip" command. Those who are interested in the technical details should check out the GitHub project.

While I was working at it, I finally built flashable uninstallation ZIPs as well. They revert all actions done by the installation script, provided you didn't delete the backups (). These ZIPs are only tested with Android 5.0.

The other changes are:
- Installer: Display the installed framework version in green, instead of a static hint about flashing the framework via recovery.
- Fix for incomplete logs on some devices, see github.com/rovo89/Xposed/issues/34
- Fix for updated modules crashing until the next reboot, see github.com/rovo89/Xposed/issues/22
- Ignore unknown parameters to avoid bootloops on some devices, see github.com/rovo89/android_art/issues/7
- Some other internal improvements
- Some cherry-picked ART commits from AOSP
- Devs: Allow hooking native methods, see github.com/rovo89/Xposed/issues/28
- Devs: Several debugger fixes, see github.com/rovo89/android_art/issues/1

I'm also uploading builds for arm64 and x86 devices. I have tested them on my Nexus 9 and on the Genymotion emulator and didn't notice any issues. The unofficial builds don't seem to be modified from my source code either and I didn't get pull requests on GitHub for these platforms, so I assume that they work fine.

By the way, in case you're a dev (or just interested) and want to try out your modules on Genymotion, you can use this collection of scripts to faciliate the Xposed framework installation on Genymotion. Just follow the instructions, then you can simply drop the x86 framework installation ZIP on the emulator window to install the framework. Don't forget to reboot afterwards.

So much for now. Be assured that official Android 5.1 support will come sooner or later, but the changes above required quite some debugging, development and strategic thinking. It's nice to see that some unofficial ports fill the gap for those who don't want to wait.

About M: The AOSP tag for the preview seems to be just a placeholder, just like it was for the L preview. I haven't tried, but I doubt that compiling ART from this tag will fit to the M preview image. Hence, I won't be investing any of the time (that I don't have anyway) to try and get Xposed running on the preview image.

This release does not have a Play Store Description, so we grabbed one from version 3.1:

This is the installer for the Xposed framework, which is a requirement for all modules.

Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
All versions
October 8, 2017
November 1, 2016
October 16, 2016
February 25, 2015
Comments
  • Venkata Gurram

    This version is not working oneplus cos12.

  • Hasan

    Any one tested this on LG G2 D802 v30b?

  • Matt Hay

    Should this not be working with the 5.1.1 framework? Alpha 2 Apk works just fine. I am getting a message my framework is not detected, even after rebooting. On a N4 with latest 5.1.1 and Xposed Framework installed.

    • Sons of Ottoman

      Yeah, it isn’t compatible with 5.1.1 in the way that it cannot detect the xposed framework. But that’s just a wrong display of information on the applications’ part. In fact, xposed is running just fine. The app cannot recognize it. That’s it.

      • Matt Hay

        Thanks there is a v 4 which fixes. Just uploaded

  • Samer R. Gallab

    It’s not working with CM12.1 on OnePlus One. Also Xposed Installer 3.0 alpha4 isn’t working either. It gives false message the framework isn’t installed though all modules are working.

  • wahyu aditya

    how to install xposed and custom rom on acer Z330…? please