[ALPHA] [UNOFFICIAL] Xposed Android 5.1.1 - ARM & ARM64 / Alpha 4 / 20150609

Update auf v82:

Zitat

With version 82, compatiblity with Huawei devices is improved, see https://github.com/rovo89/Xposed/issues/72.

Note that there's still an incompatiblity with their theming engine. You can either go to the Xposed Installer settings and disable the Xposed resource APIs (with the effect that some modules won't be loaded), or you have to disable their theming engine (obviously leading to theme limitations) by setting "ro.config.hwtheme" and "ro.config.hw_theme" to "0" in /system/build.prop. See also: Beitrag im Thema "Politik Talk"

http://dl-xda.xposed.info/framework/

Guess what...update!

Zitat

Version 83:

• Fixed some bootloops/crashing apps. At least some Nexus devices seem to be affected, but it might help on other devices as well (see https://github.com/rovo89/android_art/issues/28).
• 6.0 only: Fixed crashing apps and optimizing on every reboot on various HTC devices (seehttps://github.com/rovo89/Xposed/issues/149, https://github.com/rovo89/android_art/issues/21).

http://dl-xda.xposed.info/framework/

Zitat

Version 84:

• Added a warning in the Xposed log if a module isn't compiled correctly, i.e. the APK includes the Xposed API classes instead of just referencing them. Developers, seehttps://github.com/rovo89/XposedBrid...-Framework-API for how to do it correctly.
• 6.0 only: Added support for LG's encrypted apps, fixing crashes of their weather app/service.
• 6.0 only: Fixed crashes in Yandex apps, which were caused by an obviously unfinished AOSP commit.

Zitat

Version 85:

• Fixed frequent boot freezes, especially with modules that access many files (details)
• Built-in way to get a full logcat (details)
• Crashes not related to Xposed/ART are no longer written to the normal Xposed logs
• On encrypted devices with boot password, the password prompt is now shown quicker
• Warning for developers to disable "Instant Run" in Android Studio, otherwise the module can't be loaded
• 6.0 only: Cherry-picked some ART commit included in CyanogenMod and other ROMs
• 6.0 only: Forced clearing Dalvik cache when upgrading from versions before 85 (would have been necessary for 84 and might have caused some boot loops)

I have also created a wiki page with detailed information how bugs should be reported: https://github.com/rovo89/XposedBridge/wiki/Bugs

Finally, a word to all module developers: In v84, I added a warning when a module's APK includes the Xposed API classes instead of just referencing them. I have also sent an email to the developers of all modules I could identify. With v86, I will turn the warning into an error and prevent the module from loading, as it could causes strange issues otherwise. Please update your module as soon as possible./QUOTE]

Zitat

Version 86:

• More compatiblity with ROMs that use a Resources subclass for e.g. theming, like most Huawei stock ROMs (*)
• Incorrectly compiled modules are now rejected, the warning which started to appear with v84 is now an error
• A bit of general cleanup and minor fixes

(*) In the Xposed logs, it would usually say "XyzResources doesn't extend XResources" in such cases.
If you had to select "Disable resource hooks" in Xposed Installer in the past, it's now worth to try again without this workaround.
On Huawei devices, Xposed should now work with and without their theming engine enabled.

Next step (planned for the next version): Official systemless Xposed for Marshmallow. I have already started working on that, but I don't have much time and making something robust takes a while.
Note that the systemless installation will require SuperSU 2.76 or higher. That might be considered a disadvantage compared to the unofficial versions, however I think that it's the better way. @Chainfire put a lot of effort into developing and testing a solution that works reliably on virtually every device. Whenever new devices and Android versions pop up, he's fast at making SuperSU compatible. I think it totally makes sense to build upon those achievements instead of maintaining a fork of them or even reinventing the wheel, which could in the worst case even cause conflicts. I'll rather spend that time focusing on Xposed development itself, not on dealing with all kinds of different bootloaders etc.

Für die nächste Version plant rovo89 eine offizielle Version von systemless Xposed Framework.