Database Develop

[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23

I want to start this post off with a couple of very clear points:
@rovo89 is the creator of the Xposed framework
This is a derivative work posted with his permission
This also means the following statements are true:
I have only worked to bring the Xposed framework to Android 5.1
I have only worked to bring systemless support to Xposed on Android 5.1 and 6.0
I have not rewritten the framework from scratch
With that said, I present to you my first unofficial release of Xposed for Android 5.1/6.0. It is my hope that ultimately my changes can be reviewed and an official release posted. But first, the bugs must be squashed! I've written a few Xposed modules that work fine but by posting this unofficial release, I hope to expand my audience of module writers and testers.
How To Test
You must be on Android 5.1/6.0. It will NOT work on Android 5.0 (too many changes to ART).
You should have a working recovery.
If you left the Xposed app installed from Android 5.0, you should disable all modules before installing this framework. Busted modules may keep you from booting after installation otherwise.
I will need Xposed logs (and possibly logcats) to debug any issues. Remember, if your device won't boot after installation, its likely you can reboot to recovery and still grab the Xposed log (assuming Zygote started). It will be in /data/data/de.robv.android.xposed.installer/log as error.log or error.log.old.
Known Issues
Devices with very little free space on /system may have trouble installing. Systemless installations are recommended if your device is supported. Non-systemless installs should be a last resort.
Downloads
First, I'm going to shamelessly point you to the original Xposed for Lollipop thread. Why? Because I want you to read it. This release hardly differs from that one. And maybe, just maybe, it'll save some unnecessary private messages.
Did you read the original Xposed for Lollipop/Marshmallow thread?
xposed-v??-sdk2?-*.zip - Must be flashed with a custom recovery to install the framework.
xposed-uninstaller-*.zip - Can be flashed with a custom recovery to uninstall the framework.
XposedInstaller_3.0-alpha*.apk - Must be installed to manage installed modules.
Use the correct platform and SDK version for your device. Google your device or look in build.prop if you're not sure.
Can't find some of the downloads? Surprise! They're in the original Xposed for Lollipop thread. They're unchanged, so there's no need to post them here too.
Module Developers
It would be incredibly useful to me for people to test the framework in the smallest "units" possible at first. By "unit" I mean things such as "resource replacement", "method replacement", "before method hooks", "after method hooks", etc. It doesn't do me a lot of good to know that some huge, complicated module causes system_server to crash without understanding at what level that's happening. This is actually what held me back from releasing. I have some test modules to use, but I don't have infinite time to write test modules, test the framework, etc.
For discussions, please use this thread or another matching one in this subforum. For historical discussion, please search this thread.
Downloads available here:
Download Here
.

Changelog
20160928
suhide compatibility. See this post for details.
20160709
Updated to v86. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
Experimental - Systemless builds for Android 5.1 (SDK22).
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160620
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
June 20th - Experimental - Systemless builds for Android 5.1 (SDK22). No changes to SDK23.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160617
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless support for SDK23 (Android 6.0). This should work similar to @topjohnwu's though there are some significant differences. The uninstaller has not been updated yet.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
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.
20150816
Disable resource hooking in Sygic
Disable fast access to TypedArray subclasses
Ensure system content providers are compiled before they are needed
See @rovo89's post here for details.
20150808
Merge @rovo89's changes from upstream to support LG encrypted odex files. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150804
Merge @rovo89's changes from upstream to support LG encrypted apps. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150727
Include @rovo89's changes from upstream. See his post here for details.
20150716
Include @rovo89's changes from upstream. There are no changes to the framework. If previous versions installed fine, then there is no need to update to this version unless you just really want to.
20150702
Updated installer and bundled busybox. Should resolve issues with mounting /system during install in some cases and incorrectly detecting recovery's value for ro.build.version.sdk instead of the system's.
20150701
Updated installer and uninstaller again. Installer is now less complex but still works on devices with low /system space. If you had no problems installing previous releases, then there's no need to update to this version. Uninstaller is backward compatible. See this commit for details.
20150630
Updated installer and uninstaller. Installer is now a bit more intelligent in creating your backups. Uninstaller is backward compatible. If you had no problems installing 20150629, then there's no need to update to this version. See this commit for details.
20150629
Update to v65 from @rovo89
Note: If the Xposed installer app (not zip) indicates the framework is not installed, then make sure you are using alpha4 of the installer app. This is a bug in alpha3 of the installer app.
20150514
Updated to include @C3C076's commits here. Buy the man a beer!
For details, see commits #1 and #2.
FAQ
Unofficial FAQ maintained by the community is available here
Miscellaneous
Working and non-working modules can be found here. This is not an official list. Your mileage may vary.
If you get "low space warnings" after installation, make sure you wiped Dalvik cache in recovery. If they persist, your ROM may have modified build.prop. See this post for one way on how to fix it. This seems most common with Chroma ROMs.
If your ROM gzip's (compresses) the .odex files in /system, then Xposed will not work and you will bootloop. This is due to patchoat handling the gzipped odex files, but not correctly patching them for Xposed. This causes Xposed to trigger continuous re-dexopt'ing of the compressed odex file.

Awesome! Been waiting for this since you announced on Github! Thanks so much for bringing it public!
Edit: apologies, got a little ahead of myself when I saw the first post in discussion deleted, missed the end of this post in my excitement.

This is incredible! Thank you
Sent from my Nexus 5 using Tapatalk

Wrong footer and signature verification failed. How do I fix this?
I'm on CM12.1 Unofficial, XT 1033
EDIT: Flashed another recovery (TWRP) and it worked.

Thank you soooooo much, for your hard work!!

Bootloop after installing gravitybox [LP]......My wrong , i forgot to make a NANdroid. I'll check it out again with a Nandroid backup.

Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1

dmatik said:
Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1
Click to expand...
Click to collapse
Same here with gravity box and it seems with CpuTemp in status bar

Nice job would test it asap

Great work! MinMinGuard is working like a charm with this!

blackzigong said:
Great work! MinMinGuard is working like a charm with this!
Click to expand...
Click to collapse
Is busybox working?

So this may seem like a stupid question but where do we download the xposed-installer-alpha from? Original xposed thread alpha-2??
EDIT: All good, original thread it is

Bootloop on my Nexus 5

Can this thread be locked & use this one forum.xda-developers.com/xposed/discussion-xposed-android-5-1-t3072982 instead?

Has anybody tried Amplify if it's working ???
Powered by ET!

Thanks for your effort

advanced power menu is working fine
nexus 5 stock thanks

- Lolistat - Not working
- Youtube Adaway - Not working
- OGXposes (To login with ogyoutube) - Not working
- AcDisplay - Not working
- Advanced power menu - Working

Does greenify work?

[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available

arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"

just in case...

I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.

Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.

Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.

Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.

Framework installation zip attached to OP.

good

Only for 5.1?

auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.

5.0 for samsung galaxy s6 ?

koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!

subscribed.

Feel free to post any problems you have with this here. (arm64 related problems)

Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo

YouTube adaway works fine
For me

Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.

joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense

Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched

Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!

[5.1.1] [2015-08-29] [Xposed Support] CyanogenMod 12.1

CyanogenMod 12.1​These are builds of CyanogenMod 12.1 using JustArchi's repos, modified to support the Xposed Framework.
XPOSED IS NOT INCLUDED, FLASH IT!
Link to Xposed
What's the difference here?
This ROM is DEODEXED, that's the difference. Now, the first boot speed will be slower.
Google says:
Dex file compilation takes more time than dexopt, which can be noticeable when all of a user's apps must be compiled during first boot (after factory reset or after receiving an OTA). To reduce the amount of compilation needed, ART supports the option of pre-optimizing libraries and applications in the system partition. Including the pre-optimized dex files takes space in the system image, so these options trade first boot time for system image size. Enabling WITH_DEXPREOPT causes everything in the system image to be pre-optimized. If this makes the system image too large, additional options can be specified to reduce the amount of pre-optimization.
Click to expand...
Click to collapse
And why Xposed now works?
Xposed for Android 5.1 is on Alpha stage. Therefore, it's unstable and has a lot of problems.
The developer of the unofficial port, romracer, explained:
If your ROM gzip's (compresses) the .odex files in /system, then Xposed will not work and you will bootloop. This is due to patchoat handling the gzipped odex files, but not correctly patching them for Xposed. This causes Xposed to trigger continuous re-dexopt'ing of the compressed odex file.
Click to expand...
Click to collapse
So, a deodexed ROM fixes the problem.
DOWNLOADS
20150829
XDA:DevDB Information
CyanogenMod 12.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
brianelv, JustArchi, Moster2, arter97
Source Code: https://github.com/ArchiDroid
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod 12.1
Version Information
Status: Beta
Created 2015-08-30
Last Updated 2015-08-30

Changelog
2015-08-29
- Initial release

Reserved.

Are these builds just reverting the dlmalloc tweaks?

whatsgood said:
Are these builds just reverting the dlmalloc tweaks?
Click to expand...
Click to collapse
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.

So, is same rom with the change "Enable dex-preoptimization" reverted? u update cm sources too?
Im afraid to flash a rom that dont comes from oficial developer, will u test all build on your phone before post here? i dont want to brick my phone.
Thanks from compile and share this build.

galen2 said:
So, is same rom with the change "Enable dex-preoptimization" reverted? u update cm sources too?
Im afraid to flash a rom that dont comes from oficial developer, will u test all build on your phone before post here? i dont want to brick my phone.
Thanks from compile and share this build.
Click to expand...
Click to collapse
Yes, it's the same ROM. I like CyanogenMod 12.1 so I'll update it frequently. And yes, I do tests before posting, with and without Xposed.

brianelv said:
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.
Click to expand...
Click to collapse
Why do you spread false information? Dex-preoptimization doesn't affect only first boot and I described why.

JustArchi said:
Why do you spread false information? Dex-preoptimization doesn't affect only first boot and I described why.
Click to expand...
Click to collapse
It's the same, odexed or deodexed. I tested it, and there are no improvements. Besides, odexed roms breaks Xposed. So, what's the problem using a deodexed rom?
Archi, you made a LOT of optimizations, you're the best with this. But odexed roms with Xposed are not compatible. With odex I can't see any difference, and I need Xposed, so I disabled it. Other people needs Xposed too (I think) so I shared it.

brianelv said:
It's the same, odexed or deodexed. I tested it, and there are no improvements. Besides, odexed roms breaks Xposed. So, what's the problem using a deodexed rom?
Archi, you made a LOT of optimizations, you're the best with this. But odexed roms with Xposed are not compatible. With odex I can't see any difference, and I need Xposed, so I disabled it. Other people needs Xposed too (I think) so I shared it.
Click to expand...
Click to collapse
There are no improvements?
Keep using your xposed builds then, you're too ignorant to notice the difference.

brianelv said:
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.
Click to expand...
Click to collapse
Brother, Calm down. Don't use so mean words like 'useless' which may not look good to the original developer.
Whatever you are doing is based on the months of hard work done by developers like @JustArchi . Have some respect on their opinions or decisions.
As I said before, many Xposed lovers would appreciate your work which is based on ArchiDroid sources with Xposed support. Just make sure to communicate your thoughts in meaningful good words.

Xposed 5.1 officially released! Now supports odexed roms
I'll update the thread later.
Link of Xposed: http://forum.xda-developers.com/showthread.php?t=3034811

any screenshots ?

Official Xposed Framework for Android Nougat is Here – Download your Favorite Modul

As the Android ecosystem has matured over the years, fewer and fewer users find reasons why they should root their device. There’s a growing trend of users choosing to stay on the stock firmware, either because they find the experience satisfactory or don’t want to play a cat-and-mouse game with Google’s SafetyNet API. But if you asked a user back in early 2016 why they rooted their phones, perhaps the number one reason that was given was so they could install the Xposed Framework. It’s been over a year since Android 7.0 Nougat was first released, but the long wait is finally over: official Xposed Framework for Android Nougat is finally available.
Why install the Xposed Framework?
Want to get custom ROM features without flashing a custom ROM? The mother of all Xposed Modules for tweaking your ROM, known as GravityBox, has you covered. Want to customize display settings on a per-app basis? Try App Settings. How about customizing certain applications like Hangouts? Or modifying Instagram so you can download whatever posts you like?
posed gives developers the ability to modify pretty much whatever they want—mostly aimed at individual applications but even system-wide features can be modified. The examples we listed is just the tip of the iceberg. The number of additional features you can add or apps you can modify is incredible—just search through the official Xposed Module repository to see for yourself. Keep in mind that some modules might need to be updated for this new release and for Nougat support, so be sure to check before installing them on your Nougat ROM!
How do Xposed Modules work?
The gist of it is that the Xposed Framework allows modules to “hook” into the Java methods of any application—be it user-installed or a system application. Xposed lets modules execute their own methods before, during, or in place of the original methods of the target application.
For instance, imagine a method used in the Gmail application that posts notifications for new emails. By default, the method creates a new notification with buttons to archive/delete or reply to the email. A Xposed Module could be made to hook into this method and add a new button such as “mark as read.” (Yes, there’s already a Module for just that.)
The above is an over-simplification of the end result of what the Xposed Framework allows its modules to do. The Framework itself is incredibly complex and making it work nearly universally on rooted devices—without needing a custom ROM—is why Xposed for Android Nougat has taken so long to complete. *install at your own risk, I'm not responsible for anything you do to your device.
Source link:
XDA
https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
Xposed
http://repo.xposed.info/
Installation:
Download the xposed zip file and flash it in recovery (framework files)
Now install the xposed apk
Reboot mobile
*dont open the app before installing the zip
Download link:
xposed-v88.2-sdk24-arm64.zip (7.0)
http://dl-xda.xposed.info/framework/sdk24/arm64/
xposed-v88.2-sdk25-arm64.zip (7.1)
http://dl-xda.xposed.info/framework/sdk25/arm64/
Xposed 3.1.4.apk
https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299
Download any module of your choice
http://repo.xposed.info/module-overview

What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.

spunxhoe said:
What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.
Click to expand...
Click to collapse
I use what I want, you don't want to take care about me and this thread., head to the source link to read the full thread that's all.

Xposed for Oreo and Pie - Edxpoed

EdXposed
A Riru module trying to provide a ART hooking framework (mainly for Android Pie) which delivers consistent APIs with the OG Xposed, leveraging YAHFA hooking framework.
https://github.com/ElderDrivers/EdXposed
Credits
YAHFA: the core java hooking framework
Riru: provides a way to inject codes into zygote process
XposedBridge: the OG xposed framework APIs
dexmaker and dalvikdx: dynamiclly generate YAHFA hooker classes
Whale: used for inline hooking
Known issues
resources hooking is not supported yet
may not be compatible with all ART devices
only a few Xposed modules has been tested for working
file access services are not implemented yet, now simply use magiskpolicy to enable needed SELinux policies
Build requirements
same as Riru-Core's and zip binaries can be downloaded from here
Build
run :Bridge:makeAndCopyRelease in Gradle window to build edxposed.dex
run :Core:zipRelease to build Magisk Riru module flashable zip file
find the flashable under Core/release/
flash the zip in recovery mode or in Magisk Manager
Install
make sure Magisk v17.0 or higher is installed.
download Riru-core v10 or higher and install it in Magisk Manager or recovery.
download EdXposed and install it in Magisk Manager or recovery.
Install companion application(s)
reboot.
have fun
Companion applications
for v0.2.9.5 and before: Xposed Installer
for v0.2.9.6 and v0.2.9.7: Xposed Installer and EdXp Manager(optional)
for v0.2.9.8 and later: EdXposed Installer
Get help
Forum (recommend): Android Forum
GitHub issues (recommend): Issues
For Users using QQ, QQ Group: 855219808
Telegream: Code_of_MeowCat
Discord: Code_of_MeowCat
Contribute
Apparently this framework is far from stable and all kinds of PRs are welcome.

The main EdXposed XDA thread is here:
https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513
Nevertheless, this start post is more informative than the original one.

Is it Xposed replacement for oero/pie?
Sent from my Motorola Moto G (5S) Plus using XDA Labs

QkiZMR said:
Is it Xposed replacement for oero/pie?
Click to expand...
Click to collapse
Is the only Pie compatible version, and also looks like to work on Oreo.
I have a Google Pixel and I can confirm it's working on Pie, a lot of modules works, so far so good.

I started testing it today, on Oreo and I would say that is working stable for now. Some time ago after installing Xposed on my phone, I noticed that Xposed causing that system and application are running little slower than without Xposed. But capabilities that Xposed is giving to me are more important, so I can live with it. Now after installing EdXposed I didn't noticed any impact on system performance.
Sent from Moto G (5S) Plus via Tapatalk

Worked at first and I was able to install fake gapps because I wanted microg, but it stopped working after that. I do have microg working now, but I can't add any more xposed modules as it shows inactive. I read somewhere that it works after a soft reboot, will try that next.