Database Develop

Don't use xposed with lollipop

Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
Wut? :/

I installed the beta of xposed for Lp, and not all of modules already supported but I highly recommend on xposed.. Check in thread for it.. If your rom is supported, if yes, go and enjoy..

This is must be a joke.. It has to override ART files with xposed implemented codes to work. There's no other way.

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
1) Using with Dalvik is not so different, only behavior of Dalvik is changed without change the files.
2) Flash a zip or integrate the same files into a ROM is exactly the same thing.
3) What? This already works, if a developers integrate Xposed in his rom, the users can install only the Installer later.
4) We hope that Samsung didn't change those files.

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
1 to 4... Really? For whom did you intend this post? If someone doesn't know the trivia or hadn't read the OP/FAQ and still installed apk he/she/it knows nothing of -> it's their own fault. They bootlooped their samsung device even after Rovo written the red warning? They deserved it.
Everyone! I highly recommend that you don't listen to him (or me, since i too am biased) and think for yourself. If you know how to post logs and have at least basic understanding of android/java - or, at least, understand that any modification made in root may destroy your device/personal data/ whatever (Well, it's an exaggeration, but it's better to be prepared. ) - then help Rovo debug xposed for your device. If you do not - then pls, stop using xposed and posting here.

We waited for it very long time and now you said "sorry, implementation is not good"? Do not use it or create better implementation. When rovo89 had decided for that implementation, he had reasons for it (he wrote them somewhere)

please delete thread

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?

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.

[Help] I can't get the new module template working.

As anyone who works on Magisk modules knows there is a new module template out, and for the life of me I can not get it working whatsoever. No matter what the install will always fail in my test builds. If anyone can be kind enough to submit a pull request with the updated template applied to my 2 modules, F-Droid Privileged Extension and Systemless TZData I would be extremely thankful.
EDIT: I might just have been overthinking due to life at the moment.

ryaniskira said:
As anyone who works on Magisk modules knows there is a new module template out, and for the life of me I can not get it working whatsoever. No matter what the install will always fail in my test builds. If anyone can be kind enough to submit a pull request with the updated template applied to my 2 modules, F-Droid Privileged Extension and Systemless TZData I would be extremely thankful.
EDIT: I might just have been overthinking due to life at the moment.
Click to expand...
Click to collapse
I have a funny feeling it is because the updater-binary is now empty and has to be manually replaced with a proper installer script. Read more here.