Affiliate links on Android Authority may earn us a commission. Learn more.
Xposed framework now supports Android 6.0 Marshmallow - customize away!
Fans of the Xposed framework have something to celebrate today. After weeks of telling you support for Android 6.0 Marshmallow was getting closer and closer, developer rovo89 has finally released version 77, with full Marshmallow compatibility.
For those who have no idea what Xposed framework is: it’s a tool for root users, which allows them to customize individual parts of the system and UI. I find that it’s best for those who do not want a full-blown change of experience, but would prefer to tweak a few things here and there.
All the user would need to install Xposed is a custom recovery and a rooted phone (of course). As always, there are certain things to consider, though. Keep in mind that rooting and tinkering with your phone may harm your device and/or void its warranty, so be very careful and spend a good deal of time doing your research.
With that in mind, the developer does have some comments you should keep in mind. Here they 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.
Also, some reports say a few Samsung and Sony phones on stock software are having issues with bootlooping. With that in mind, try to be careful and make a backup before doing anything. Happy flashing!