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?
Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).
Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Here is the module on my device :silly:
dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing
Please I need multiuser enable magisk module for Android 6
dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules
You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3
jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz
THIS PROJECT IS NO LONGER SUPPORTED.
Code:
# <Module name goes here>
## Copyright (C) 2017-2018, VR25 @ xda-developers
### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project.
---
#### DESCRIPTION
Hide USB Debugging notification, enable tethering, HDMI (& HDMI mirroring), and wireless display mirroring (Miracast). More features may come.
---
#### PRE-REQUISITES
- Magisk v15+
---
#### SETUP STEPS
1. Install/upgrade from Magisk Manager or custom recovery.
2. Reboot.
3. Go to Settings > Display > Cast > 3 dots; tick the "Enable wireless display" checkbox.
---
#### LINKS
- [Facebook Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/<repo name goes here>/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/module-miracast-tethering-enabler-adb-t3611335/)
---
#### LATEST CHANGES
**2018.10.4 (201810040)**
- Magisk 15+ support
- Set prop values aggressively.
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
LazerL0rd said:
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
Click to expand...
Click to collapse
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
VR25 said:
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
Click to expand...
Click to collapse
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Will it work in Kitkat or Lollipop?
Raynelfss said:
Will it work in Kitkat or Lollipop?
Click to expand...
Click to collapse
Yes, but it may not work on some devices/ROMs. You should try and report back.
LazerL0rd said:
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Click to expand...
Click to collapse
Yes. Miracast on LineageOS only work for now. (It's just fixed this problem, no magisk module, no editing build prop)
VR25 said:
After installing and rebooting, go to Settings > Display > Cast > Click the 3 dots > Enable Wireless Display > Done.
Now you can mirror your phone's screen to any Miracast supported device, such as TVs and Windows 10 PCs.
Note: this may not work on some devices/ROMs.
Click to expand...
Click to collapse
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
n0013z said:
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
Click to expand...
Click to collapse
Usually, this doesn't cause any issue in case it doesn't work. You can easily remove it from the Magisk Manager app. Alternatively, you can also mount magisk.img from recovery and delete the folder "magiskmiracast" inside /magisk.
Use this recovery flashable zip
https://forum.xda-developers.com/attachment.php?attachmentid=4081169&d=1489956274
to mount magisk.img to /magisk.
Miracast is working for me but only for some minutes I play videos, show some pictures and the screen freeze only in my Smartv.
I play videos and more with Allcast and it doesn't happen
Sent from my Moto G (5) Plus using XDA Labs
No luck for me
Oneplus 2 a 2003 rr 5.8.3
Not working on OP3T on OOS
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Shen Ron said:
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Click to expand...
Click to collapse
Something is wrong with TouchWiz.
So, do I need to be rooted? Or can it be flashed from stock recovery on my zte blade v7 lite (android 6.0) without damage being done? Also I do believe the device needs specific hardware, correct me if I'm wrong!?...
Has anyone tested this on OnePlus 3T?
gb_14 said:
Has anyone tested this on OnePlus 3T?
Click to expand...
Click to collapse
Heyyo, lol literally four posts above yours.
ThE_MarD said:
Heyyo, lol literally four posts above yours.
Click to expand...
Click to collapse
Oh yeah, sorry, I haven't noticed.
HTC One m9, bad boys one m9 nougat 4.1 rom.
I dont have a display option in the settings (probably because of sense)
Only have display and gestures but no cast option inside.
I installed on my S7 Edge Nougat ... But I did not find in any menu the options to activate. Has anyone had this problem? I also tried to test mirroring with an LG TV and could not.
THIS PROJECT IS NO LONGER SUPPORTED.
# Sysconfig Patcher
---
## LEGAL
Copyright (C) 2017-2019, VR25 @ xda-developers
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
---
## DISCLAIMER
Always read/reread this reference prior to installing/upgrading this software.
While no cats have been harmed, the author assumes no responsibility for anything that might break due to the use/misuse of it.
To prevent fraud, do NOT mirror any link associated with this project; do NOT share builds (zips)! Share official links instead.
---
## DESCRIPTION
This module patches all relevant XML files from `/system/etc/sysconfig/` for data and battery savings, and auto-repatches these after ROM/GApps updates.
Targeted packages (i.e., `Google Play Services (GMS)`) are deprived of unrestricted access to data and power intensive resources without the user's explicit consent.
`Doze` and `data saver` will act upon these. Core packages such as `Qualcomm's`, `Download Manager`, `Shell`, etc., are excluded by default.
`MagicGApps` module 2019 is supported.
For verbose, refer to `/dev/sysconfig-patcher/post-fs-data.sh.log`.
---
## PREREQUISITES
- Magisk 17-19
---
## SETUP
Install
0. [Optional] Set up /sdcard/.sp_whitelist.txt.
- Use zipFile/common/whitelist.txt as reference.
- Do not remove/blacklist default packages, unless you know exactly what you are doing.
- Reinstall the module to apply new changes.
1. Remove or disable redundant modules (e.g., `Enable Doze for GMS`, `Universal GMS Doze`).
2. Flash live (e.g., from Magisk Manager) or from custom recovery (e.g., TWRP).
Uninstall
- Use Magisk Manager (app) or Magisk Manager for Recovery Mode (utility).
---
## USAGE
Generally, once the module is installed, you don't have to do anything else.
If `Google Play Services` package is not optimized, go to settings > security and try one or all of the following workarounds (a reboot is implied):
- Disable all Google `Trust Agents`. This may break Google `Smart Lock` features.
- Disable all Google `Device Administrators`.
- Disable `Find My Device`.
---
## LINKS
- [Donate](https://paypal.me/vr25xda/)
- [Facebook page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git repository](https://github.com/Magisk-Modules-Repo/sysconfig-patcher/)
- [Telegram channel](https://t.me/vr25_xda/)
- [Telegram profile](https://t.me/vr25xda/)
- [XDA thread](https://forum.xda-developers.com/apps/magisk/module-sysconfig-patcher-t3668435/)
---
## LATEST CHANGES
**2019.4.6 (201904060)**
- Complete redesign
- Custom whitelist (refer to README.md for details)
- Magisk 17-19 and MagicGApps 2019 support
- Updated documentation
**2018.10.22 (201810220)**
- Major optimizations
- Magisk `15.0-17.2` support
- Module ID reverted to `sysconfig-patcher`
- Module template `17000`, with extras
- Rebooting twice to apply changes after disabling/re-enabling the module is no longer necessary.
- Support for MagicGApps versions greater than `2018.9.23`
- Updated building and debugging tools
- Updated documentation
* Release notes: if you have `/data/adb/magisk_simple/system/etc/sysconfig/`, remove it with TWRP file manager (preferably before upgrading). Oreo and Pie users (or even users in general) may need to disable Google device administrators for things to work as expected. This rather inconvenient requirement has nothing to do with Sysconfig Patcher. It's a Google thing.
**2018.8.29 (201808290)**
- Improved compatibility
- Magisk Module Template 1500
- Updated documentation
Archive
I'm currently use your enable doze GMS+, so must I uninstall enable doze module before flash this module?
Sent from my Redmi 3X using Tapatalk
jmmigo said:
I'm currently use your enable doze GMS+, so must I uninstall enable doze module before flash this module?
Click to expand...
Click to collapse
You can install without removing that one. You'll no longer need DozeGMS+, though.
So...
will try this modules
Will the recent version work with magisk14?
jsecruzvalencia said:
Will the recent version work with magisk14?
Click to expand...
Click to collapse
i think so
Sweet.. Is this available in repo
I hd doze battery saver, so i Uninstalled n installed this module. But sonehow I'm getting more wake locks compared to the earlier module. Even though battery optimization shows gplay services to be optimized, i hv the gplay wakelocks.
Cannot see google in battery optimization
Hi,
Unfortunatly I cannot see Google Services in Greenify or in Battery optimization, module installation was made directly with Magisk. There is Enable_Doze_for_GMS_Magisk_Module-v5 also installed
Thanks for you reply.
Mobile : One Plus 5 (ROOT)
ROM : Oos 4.5.8
Magisk 14 - Magisk manager 5.3.0
musprog said:
Hi,
Unfortunatly I cannot see Google Services in Greenify or in Battery optimization, module installation was made directly with Magisk. There is Enable_Doze_for_GMS_Magisk_Module-v5 also installed
Thanks for you reply.
Mobile : One Plus 5 (ROOT)
ROM : Oos 4.5.8
Magisk 14 - Magisk manager 5.3.0
Click to expand...
Click to collapse
Try remove the "Enable_Doze.....v5" module than reboot
Thanks for your reply
Cheer's
kwanthenewbie said:
Try remove the "Enable_Doze.....v5" module than reboot
Click to expand...
Click to collapse
Hi,
Exactly the same issue without this module.
Didn't work for me.
Asus zenfone 2 - stock 6.0.1, Magisk 14.0 / magisk manager 5.3.0 installed .
Someone try it on a Pixel with Oreo?
What do this module? Just remove play service from whitelist?
v2017.9.24 worked for my phone zenfone 2 z00a.
Thanks :good:
Should I flash this even though I have Greenify?
Sh0X31 said:
What do this module? Just remove play service from whitelist?
Click to expand...
Click to collapse
Play Services and everything else that "shouldn't" be there.
Phititan said:
Should I flash this even though I have Greenify?
Click to expand...
Click to collapse
Yes, this module may improve your battery life even further.
Hello, what does this exactly do? I see there is any resource or google.xml file inside? So wondering if it works
Also works flawlessly on my 2nd phone zenfone 3 / stock 7.0 / magisk 14.0. :highfive:
Big thanks OP. :good:
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?