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.

(i.e. all the files in the flashable) zip is versioned with integers ( 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.

I have just upload files for a. 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)for installer, framework zip, app_process and XposedBridge by reducing it to two version numbers:The next bigger change is the. 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 flashableas 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.Theare:- 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 https://github.com/rovo89/Xposed/issues/34 - Fix for updated modules crashing until the next reboot, see https://github.com/rovo89/Xposed/issues/22 - Ignore unknown parameters to avoid bootloops on some devices, see https://github.com/rovo89/android_art/issues/7 - Some other internal improvements- Some cherry-picked ART commits from AOSP- Devs: Allow hooking native methods, see https://github.com/rovo89/Xposed/issues/28 - Devs: Several debugger fixes, see https://github.com/rovo89/android_art/issues/1 I'm also uploading builds fordevices. 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.