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

Ich hab's ja gewusst...der Entwickler-Ehrgeiz lässt keine Ruhe..egal was man in der Community schreibt..nur so hat man erst mal seine Ruhe zum tüfteln[emoji6]
Ganz groß der rovo89

Xposed SuperAlpha v4 mit Unterstützung für Android 5.1.1 + für ARM64-Geräte (z.B. N9)

Original Thread @ XDA

Achtung, das Xposed.zip verträgt sich nicht mit den ART-Tweaks in der build.prop (...dex2oat...)!!! Wenn vorhanden, vorher die betreffenden Zeilen in der build.prop löschen, Caches wipen und Neustart, dann erst das Xposed.zip flashen und noch mal die Caches wipen.

Gut zu wissen mir den art Tweaks...hatte mir gestern die Alpha 4 drauf getan und bin total abgeschmiert ohne zu wissen weshalb...jetzt weiss ich es.Danke

Jo, ich hatte es gelesen mit den ART-Tweaks, aber heute mit OptiPop selbst feststellen müssen. Zeilen gelöscht, dann ging es.;)

rovo89 hat jetzt eine erste offizielle Version von Xposed Framework für Lollipop 5.1 rausgebracht und gleich dazu auch die entsprechenden Uninstaller-Dateien:

Zitat

I finally created an official version for Android 5.1 (aka SDK22). You can download it as v72 from the first post.

This version is not directly based on @romracer's port, however there aren't many differences. He had merged AOSP 5.1 into the Xposed codebase, I did it the other way around and used this opportunity to reorder and combine the commits. So it's a little bit cleaned up now, which will hopefully make it easier to port these changes to future Android versions. I have also cherry-picked two of his changes that weren't in the offical version yet: A fix for a special case in resource handling on 64-bit and compression of the backup Xposed creates during its installation. Many thanks to @romracer for providing the unofficial version - this gave me the chance to fix and improve many things (which were in turn merged by him and others).

That said, there are also a few new changes:
- In error messages, the Android version is now display as well, e.g. "Wrong Android version: 5.1 / SDK22 ... This file is for: 5.0 / SDK21"
- The files for Android 5.1 can now handle gzip-compressed odex files (*.odex.gz). Those files only exist on certain ROMs (e.g. CM) that merged a few commits proposed by Intel. These commits weren't accepted into AOSP because the way they're handling the compressed files has some flaws. With Xposed installed, these files will be unpacked on-the-fly and recompiled.

The gzip support might also be interesting for ROMs where the /system partition is almost full. It should be possible to gzip some of the .odex files before installing Xposed in order to free up some space. This should work on any odexed 5.1 ROM, even if the Intel commits aren't included. However, this would be very experimental. Volunteers are welcome, but don't forget to create a backup.

Finally, I have updated the uninstaller zips. They include a timestamp now, as new installer zips might require new uninstaller versions. You should always be able to uninstall older versions with the latest uninstaller though. v72 requires at least the uninstaller from today (20150831).

xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v72-sdk22-arm.zip
xposed-v72-sdk22-arm64.zip
xposed-v72-sdk22-x86.zip

Update für Xposed Framework:

Zitat

With framework version 73, a bug on 64-bit ROMs is fixed which prevented modules from reading their preferences. I believe that the root cause is a bug in AOSP, but whatever - it should be fixed now. Thanks to @romracer and @cryptyk for the fix.
I have additionally merged a few changes from CyanogenMod. Most of them control when the Dalvik cache is cleared automatically after a bootloop (new feature in 5.1 AOSP, now improved) and one is supposed to increase the compile performance on some ROMs. Don't expect too much though.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v73-sdk21-arm.zip (5.0)
xposed-v73-sdk21-arm64.zip (5.0)
xposed-v73-sdk21-x86.zip (5.0)
xposed-v73-sdk22-arm.zip (5.1)
xposed-v73-sdk22-arm64.zip (5.1)
xposed-v73-sdk22-x86.zip (5.1)

Zitat

In framework version 74, I have fixed some more incompatibilities which could lead to bootloops or crashes. I assume that most of these crash logs contained the string "Incompatible set properties", which is actually a consequence of previous method verification errors. It's hard to say which ROMs and devices were affected - but flashing the new version shouldn't hurt even if everything looks fine with older versions. If you do notice any issues and are sure that it's not caused by yourself, you have higher chances of getting them fixed if you open a detailed GitHub issue (usually I will need at least a full logcat).

I won't be able to work on Xposed for the next 2-3 weeks - no time for development, support or questions at all. If the rumors I have read are right, I should be ready just in time to start porting Xposed to M.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v74-sdk21-arm.zip (5.0)
xposed-v74-sdk21-arm64.zip (5.0)
xposed-v74-sdk21-x86.zip (5.0)
xposed-v74-sdk22-arm.zip (5.1)
xposed-v74-sdk22-arm64.zip (5.1)
xposed-v74-sdk22-x86.zip (5.1)

romracer hat jetzt eine neue experimentelle UNOFFICIAL (Test-)Version auf Basis der offiziellen v74 von rovo89 rausgebracht für Leute, die z.B. Probleme mit der Installation der offiziellen Versionen von rovo89 hatten...

Zitat

Probably, but not without @rovo89's permission. This version was only posted with his permission 6 months ago. Xposed is not a competition between developers, its a collaboration. That's something that sometimes seems to be forgotten on XDA, regardless of which project we're talking about. /endrant

I've uploaded an experimental v74 build for Android 5.1. If the official release works, great, there are no changes. But if you want to test an alternate backup method, or you could never get the official releases to install, give this version a go. I have already discussed these changes some with @rovo89, but neither of us were certain how necessary they were or weren't. So now we'll do a live field test and see...

xposed-uninstaller-20150911-arm.zip
xposed-uninstaller-20150911-arm64.zip
xposed-uninstaller-20150911-x86.zip
xposed-v74-sdk22-arm-by-romracer-20150911.zip (5.1)
xposed-v74-sdk22-arm64-by-romracer-20150911.zip (5.1)
xposed-v74-sdk22-x86-by-romracer-20150911.zip (5.1)

Changelog

20150911 - Never Forget.

• Updated to v74. See @rovo89's post here for details.
• If the official release works for you, there is no need to install this version, unless you want to test LZMA2 compression.
• Experimental - Use LZMA2 compression for our backups. If you get errors while trying to install Xposed, this may help.
• Experimental - Uninstaller supports LZMA2 compressed backups. Its also backward compatible with official and my previous unofficial releases.

rovo89 hat noch mal eine neue offizielle XposedFramework-Version v75 rausgebracht:

Zitat

Framework version 75 adds compatibility with the latest 5.1.1 ROMs (v19 and later) which include a change to app_process. This version should be compatible with both, newer and older 5.1.x ROMs. The change didn't affect 5.0.x. This version also disables the dex2oat watchdog, so especially on older devices with less performance, Xposed might now be working.

Fixing this issue prevented me from gettings started with Marshmallow so far, but I'm on it. My Nexus 9 is running on stock AOSP 6.0 already and the sources are synced to the build server (thanks to XDA for providing it). I assume that integrating the hooking mechanism should work relatively smoothless (although there were some bigger architectural changes). However, there are some new things, e.g. JIT and the optimizing compiler that need more attention to ensure that methods which could potentially be hooked are really called instead of being optimized away.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v75-sdk21-arm.zip
xposed-v75-sdk21-arm64.zip
xposed-v75-sdk21-x86.zip
xposed-v75-sdk22-arm.zip
xposed-v75-sdk22-arm64.zip
xposed-v75-sdk22-x86.zip

rovo89 hat nun Xposex Framework v76 für Android M 6.0 rausgebracht:

Zitat

Marshmallow!

I have just uploaded version 76 with support for Android 6.0 (Marshmallow). Even though I tested it only on my Nexus 9/arm64, I'm confident that the arm and x86 builds will work fine as well. The Xposed Installer app didn't require any changes, you can still use version 3.0 alpha4.

What else can I say about it? Well, as expected, the upgrade from 5.1 to 6.0 was a much bigger one than from 5.0 to 5.1. Therefore, porting the Xposed-related changes in ART was more complicated, but as Google has done a lot of refactoring, I could simplify some of my own changes as well. Pretty much everything is ported now, except for support for gzipped and encrypted files - let's see if vendors even use them on 6.0.

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.

Three more things:
- I plan to publish a new version for Lollipop (5.0/5.1) within the next days, with backports of some of the changes I did for Marshmallow. This needs some more testing though.
- I know that some vendors seem to have backported the latest 5.1 security fix (see a few posts above) to 5.0, due to which Xposed is no longer working. This should also be fixed with the next version.
- I will push the changes to GitHub soon, also within the next days (once I have made sure they don't break 5.0/5.1).

And now: Have fun flashing Marshmallow and Xposed! Discussions gohere.

(*) For developers: Marshmallow now lets apps run with context "u:r:untrusted_app:s0:c512,c768" instead of "u:r:untrusted_app:s0". If the app is run by a secondary user, the level ("c<nnn>,c<nnn>") is different, and system apps (like Settings) don't have such a level at all. The SELinux policy allows access to app data files only when the the level of the file and the process matches exactly, therefore you can no longer access preferences created by a primary user app from apps like Settings or while logged in as secondary user. I do have workarounds for Zygote and system_server, but I can't use them for normal apps in their current state as it might open big security holes.

Alles anzeigen

Zitat

"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)."

Yeah. I was wondering why I didn't come across any issues at all with the optimizing compiler during development - especially as Xposed Installer relies on certain methods not being optimized away. It turned out that a special kind of optimization wasn't done for debuggable versions of apps - so on my device, with Xposed Installer installed via Eclipse, everything was fine, but when you have the release build, some hooks are ineffective because the method is never really called, so the active Xposed version wasn't detected properly...

That's why I had to upload a new version 77 which disables the method inliner for the optimizing compiler as well, just like it was for the normal ("quick") compiler already. It will also trigger the recompilation of all oat files, so the first boot will take longer again.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v75-sdk21-arm.zip (5.0)
xposed-v75-sdk21-arm64.zip (5.0)
xposed-v75-sdk21-x86.zip (5.0)
xposed-v75-sdk22-arm.zip (5.1)
xposed-v75-sdk22-arm64.zip (5.1)
xposed-v75-sdk22-x86.zip (5.1)
xposed-v77-sdk23-arm.zip (6.0)
xposed-v77-sdk23-arm64.zip (6.0)
xposed-v77-sdk23-x86.zip (6.0)

rovo89 hat jetzt für alle Android-Versionen ab LP 5.0 bis M 6.0 das Xposed Framework angeglichen:

Zitat

As promised, I have just uploaded version 78. It contains:
- [5.0 only] Bootloop on ROMs where the vendor has merged a recent security fix from 5.1
- [5.0/5.1 only] Backports of a few changes on Xposed that I had initially done for 6.0
- [6.0 only] Fix XModuleResources.createInstance() API method
- Fix for the invokeOriginalMethod() API method

Now, the 5.0, 5.1 and 6.0 ZIPs are in sync again. In the future, I plan to release ZIPs for all three Android versions at the same time again - even in case the changes affect only one version. I think that's better than having to keep track of the latest release per version. This time was an exception due to the backports that I needed to verify.

The source code is also published on GitHub now.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v78-sdk21-arm.zip (5.0)
xposed-v78-sdk21-arm64.zip (5.0)
xposed-v78-sdk21-x86.zip (5.0)
xposed-v78-sdk22-arm.zip (5.1)
xposed-v78-sdk22-arm64.zip (5.1)
xposed-v78-sdk22-x86.zip (5.1)
xposed-v78-sdk23-arm.zip (6.0)
xposed-v78-sdk23-arm64.zip (6.0)
xposed-v78-sdk23-x86.zip (6.0)

Zitat

In version 79, I have fixed many crashes and bootloops that were reported on GitHub. It's hard to say which devices and ROMs profit from the changes. Affected devices mentioned in the issues were mainly HTC and LG, plus any devices which have activated the compiler filter "everything" for ART.

Background:
The reason for these issues is in pretty much all cases that AOSP can't handle so called "quickened" instructions like "invoke-virtual-quick". They're the result of optimizations when the ROM was compiled, and usually just need to be executable by the runtime. However, as Xposed needs to recompile the whole ROM to disable a few optimizations that would prevent hooks from being called, these instructions need to be understood by the compiler as well, which isn't always the case. It did get better in Android 6.0 due to beginning JIT support, so I could port several changes to 5.0 and 5.1 (which isn't as easy as it sounds). But even on 6.0, several fixes were required. Unfortunately, debugging the issues to find those fixes often takes many hours or even days, hence the rather long time between v78 and v79.

More issues?
I hope that by now, most of these issues should be solved. If you still come across any bootloops - even without any active modules - please open an issue on GitHub. You must include a logcat of the failing boot attempt, otherwise I can't help you. My recommendation: Clear Dalvik cache, restart device, execute "adb logcat -v time > logcat.txt" as early as possible, wait a few minutes, press Ctrl+C.

Android 6.0.1:
Additionally, I have merged the AOSP changes from 6.0.0 to 6.0.1. They're just a few fixes, so the SDK23 ZIP works on any 6.0.x ROM.

Genymotion:
The latest version of Genymotion emulator contains improved flashing scripts based on my GenyFlash project, allowing you to flash recovery ZIPs properly. Now you can simply drag & drop the Xposed Installer APK and then the x86 framework ZIPs from the first post onto the window, without the extra step of flashing GenyFlash. Due to the great boot speed and overall performance, module development becomes much more efficient (and no, they don't sponsor me, I really just like it).

Two final statements:
- Making Xposed "systemless" (i.e. work without modifying the /system partition) should be generally possible. However, it will certainly be much effort, especially due to the high diversity of devices. I follow the process of @Chainfire's systemless SuperSU experiment to see how feasible it is. Maybe once this approach has become more mature, it can be re-used by other projects such as Xposed. I'd want to avoid incorporating the whole kernel modification stuff though - if there was some kind of init.d-like interface that allows other projects to plug in and execute some commands at very early boot time (e.g. to mount a custom libart.so over the original one), that would be great. So much for wishful thinking - currently, I'm not working on this.

- It seems that some vendors have ported a change that was originally made in 5.1 back to 4.4 (KitKat). Xposed currently doesn't work with such ROMs. Why isn't this fixed yet? Well, I have completely restructured the source code and installation procedures for ART on Lollipop. Even though I kept Dalvik in mind, it will still require much more work and testing. Therefore, I'm not able to release pre-Lollipop files at the moment and due to the focus on Lollipop/Marshmallow, I don't think this will change for the next weeks or maybe even months.

Alles anzeigen

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v79-sdk21-arm.zip (5.0)
xposed-v79-sdk21-arm64.zip (5.0)
xposed-v79-sdk21-x86.zip (5.0)
xposed-v79-sdk22-arm.zip (5.1)
xposed-v79-sdk22-arm64.zip (5.1)
xposed-v79-sdk22-x86.zip (5.1)
xposed-v79-sdk23-arm.zip (6.0/.x)
xposed-v79-sdk23-arm64.zip (6.0/.x)
xposed-v79-sdk23-x86.zip (6.0/.x)

Zitat

Version 80:

• 6.0 only: Fixed a bootloop, especially on LG devices, even though some crashes still occur in the settings (https://github.com/rovo89/Xposed/issues/100)
• 5.0/5.1 only: Fixed a bootloop on MediaTek devices (https://github.com/rovo89/Xposed/issues/81)
• 5.0/5.1 only: Fixed a crash of MyAndroidTools (and other apps with the same weird APK protection) (https://github.com/rovo89/Xposed/issues/102)
• Migrated the Java part (XposedBridge) to Android Studio / Gradle and integrated it into the build scripts.

XposedBridgeApi-20150213.jar
XposedInstaller_3.0_alpha4.apk
xposed-uninstaller-20150831-arm.zip
xposed-uninstaller-20150831-arm64.zip
xposed-uninstaller-20150831-x86.zip
xposed-v80-sdk21-arm.zip (5.0)
xposed-v80-sdk21-arm64.zip (5.0)
xposed-v80-sdk21-x86.zip (5.0)
xposed-v80-sdk22-arm.zip (5.1.)
xposed-v80-sdk22-arm64.zip (5.1)
xposed-v80-sdk22-x86.zip (5.1)
xposed-v80-sdk23-arm.zip (6.0/.x)
xposed-v80-sdk23-arm64.zip (6.0/.x)
xposed-v80-sdk23-x86.zip (6.0/.x)

Kleines update auf v81:

Zitat

After a long time with mainly bug fixes, version 81 focuses on improvements for developers:

• There is a proper API now. Previously, I basically published the sources of XposedBridge.jar, which included many internal classes/methods that modules shouldn't use. Hiding them makes it easier to find the correct methods to use and also makes it easier for me to change implementation details.
• The API is published on Bintray/JCenter, so it's easy to use, especially with Gradle/Android Studio. Full explanations here:https://github.com/rovo89/XposedBrid...-Framework-API
• 100% of the API are documented with Javadoc now: http://api.xposed.info/

Apart from that, downloads have moved to http://dl-xda.xposed.info/framework/ and are GPG-signed now. You can verify them against this key (fingerprint: 0DC8 2B3E B1C4 6D48 33B4 C434 E82F 0871 7235 F333). That's actually the master key, the files are signed with subkey 852109AA.

There are no real changes for end-users in this release, nevertheless I would recommend that at least developers test their modules with it.