Related
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?
This module doubles the number of steps in volume adjustment for both media and in-call volume.
WARNING: Apparently doesn't work on all devices, for example OnePlus 3 according to this.
what about a collection thread for build prop tweaks to use in Magisk?
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Bettik said:
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Click to expand...
Click to collapse
Could be hardware/driver-dependant. I've used a (non-systemized) prop modification before on a tablet and it was pretty smooth.
time comes, good modules too :good:
Just a reminder for those who encounter problems. ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30 won't work for all devices, such as OnePlus 3, at least on its official OxygenOS.
Once you change your media volume steps from default 15 to the 30, using the script above which is included in the module, on your OnePlus 3. The steps are increased, while it's just a loop. The volume drop back to the lowest again at the 16th step and totally silent at some steps bigger than 20.
BTW, the xposed module VolumeSteps+ won't work on OnePlus 3 either.
accidentally quoted OP instead of editing it.
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
chjun90 said:
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
Click to expand...
Click to collapse
Remove module, reboot. When asking for help, provide logs.
stangri said:
Remove module, reboot. When asking for help, provide logs.
Click to expand...
Click to collapse
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
chjun90 said:
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
Click to expand...
Click to collapse
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
stangri said:
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
Click to expand...
Click to collapse
i had
Is it compatible with the latest 11.6 magisk? Anyone tested?
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
11.0.0 version is and I have.
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
Causes systemui FC.
This is because of system.prop. I had this same issue when changing.
To 11.6.
ahrion said:
Causes systemui FC.
Click to expand...
Click to collapse
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
stangri said:
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
Click to expand...
Click to collapse
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
ahrion said:
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
Click to expand...
Click to collapse
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Didgeridoohan said:
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Click to expand...
Click to collapse
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
ahrion said:
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
Click to expand...
Click to collapse
I get it that you're trying to promote use of your own audmodlib template over the standard magisk template. Have you personally tried using *this* module *without* any other borked/broken modules? If so, please list the HW/SW (ROM, kernel, magisk and magisk manager versions, list of installed modules) combination which results in a bootloop.
PS. This is not a support thread for other broken modules.
Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?
s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.
When users provide logs...
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.
BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.
ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?
Please stop putting template=1500 in your props. you can not install even when V15 is installed. it throws an error saying saying please install magisk 15+. you have to put minMagisk=1500. i know wireguard installer 1.1 did this and Systemless_TZData did this. thank you very much and happy holidays and new year to all
"minMagisk=1500" is also in the actual module-template, so if the update to new template is done properly it should be not a problem.
Nevertheless, the change could be stated clearly or magisk can accept it silently (at least for some time).
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Didgeridoohan said:
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Click to expand...
Click to collapse
I did not read this.
Didgeridoohan said:
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Click to expand...
Click to collapse
yes your right. it says it should accept either but when i changed the two modules mentioned from template to minMagisk they both installed with no problems but using template they both gave me the error please install magisk 15+.
@Didgeridoohan already mentioned this issue in the magisk slack-group, so it should be fixed in the next beta/release. Unfortunately until this will be pushed, you have to stick with minMagisk.
And as written before: great find.
Hi there,
I use/used to use CrossBreeder lite ( Github / XDA ), and it hasn't been updated in awhile by its developer. You can no longer install it if your Magisk version is greater than v16.3. The actual module works fine, that code doesn't need to be touched, as it works fine on my device on v18.1 (which had the module installed since v15), it's just the installation part that needs to be updated. I'm trying to update it using the latest Magisk Module Template, but I'm having some issues. I never made a Magisk module/Android app before. I got it to install, but, it's basically just a blank module, it won't install the actual main files (/sbin/.magisk/img/<module>/system/*). My updated repo is here, if an experienced dev could look at my newest commit and maybe tell me what I'm doing wrong, or missing/forgetting, or any other help would be highly appreciated. Thanks!