Xposed for Marshmallow, It’s Real

There is no doubt that Xposed is the most anticipated tools for Android enthusiast out there. We have seen rapid changes in Android world recently, from KitKat to Lollipop and then another Lollipop with a lot of changes, and the most recent, Marshmallow. With this rapid developments, it won’t stop Xposed developer rovo89, a recognized developer on XDA-Developer to push a big update for Xposed, sort of.

 

Xposed v76 was released on 15th November followed by a quick fix Xposed v77, bringing new stuff for Marshmallowers to tinker with. Rovo89 have been working really hard to get it done. Previously, we have waited for a few months as I remember to get the early alpha build. But not this time. Rovo89 said, all the changes are pretty much ported, since Google refactored their codes since Lollipop, thus he can get it done in a short time.

 

But hold on, even with this Xposed support for Marshmallow, there is a few limitation that we have to accept. Below is the complete list given by rovo89: –

The only limitations I’m aware of at this time are:

 

– I have only tested this with SuperSU installed, due to which dm-verity and some SELinux rules are disabled. Especially dm-verity would definitely conflict with the modifications of the system partition.
– Access to preferences files might be blocked by SELinux, and Xposed is currently not able to work around that. (*) Some modules might be affected by this, nevertheless I strongly recommend to keep SELinux enabled and enforcing to keep your device as safe as possible.
I could not test all Xposed APIs. The system is booting without any error messages from Xposed, but some functions that the framework makes available might still need to be adjusted for Marshmallow.
– Obviously, modules themselves might need to be updated as well due to changes in AOSP. Please be patient and give module developers the time to make the required changes. If you absolutely “cannot live” without module X, don’t update to Marshmallow yet.
– Some issues might arise from JIT (disabled by default, even in AOSP) and the “optimizing” compiler (which rewrites apps’ code to be more efficient, due to which some calls might simply be skipped). Both of these are new in Marshmallow and might have various consequences in combination with Xposed, from hooks that silently don’t work to crashes. However, as it’s running stable for me, I decided not to disable them and will instead look into them in more detail if concrete issues are reported.

Other than that, we do need to wait for all the developers to update their masterpiece so we can use it on our Marshmallow.

 

You can head on to the official Xposed thread on XDA to get started.

Follow me!

Anaz Haidhar

Web Designer at CloudHAX
Part time traveler, full time day dreaming. Got anything to say, hit me up on twitter!
Follow me!

Latest posts by Anaz Haidhar (see all)