Related
Extremely sorry if I am spamming the forum with this thread, but thought of starting this discussion to see if the geeks can help with sharing the knowledge.
I don't think I have to emphasize on why Magisk over Xposed (The Magisk Forum has a lot of articles on why.), but I am surprised to realize that Magisk is still the so called "new guy" even after these many years of launch..
All I get for a sample search "best modules Magisk" is a bunch of tweaking modules which say they can alter your ART mechanism or save your battery, I mean, who cares for the performance in 2019!!! we have got beastly phones and just want magik to happen on them. Magisk is still the same serious experimental mod that lets you root and hide it from banking/work apps but not yet cool.
For example, every time I installed Xposed on a new phone, I would go look for the famous "Gravity Box" just to enable the status bar brightness control gesture.
And the "X-insta" that lets me download media from Instagram . (Of course this module seems to be dead for a few months).
And a bunch of adblockers.
And a hell lot mods that I don't remember from the top of my head, but it was really magic.. And it is slowing down (I feel so..)
Well, someone might say that we can install Xposed itself as a module, but that just crashes the "SafetyNet" which is very annoying, it makes the phone useless without being able to open GooglePay and other banking apps.
I know I might be wrong but I am posting just to see if people use any equivalent "cool" modules in Magisk that are not easily seen in the Magisk Modules repo or if someone has found a way to pass the "SafetyNet" with Xposed+Magisk to make Android awesome again!!:good:
sagar2208 said:
Extremely sorry if I am spamming the forum with this thread, but thought of starting this discussion to see if the geeks can help with sharing the knowledge.
I don't think I have to emphasize on why Magisk over Xposed (The Magisk Forum has a lot of articles on why.), but I am surprised to realize that Magisk is still the so called "new guy" even after these many years of launch..
All I get for a sample search "best modules Magisk" is a bunch of tweaking modules which say they can alter your ART mechanism or save your battery, I mean, who cares for the performance in 2019!!! we have got beastly phones and just want magik to happen on them. Magisk is still the same serious experimental mod that lets you root and hide it from banking/work apps but not yet cool.
For example, every time I installed Xposed on a new phone, I would go look for the famous "Gravity Box" just to enable the status bar brightness control gesture.
And the "X-insta" that lets me download media from Instagram . (Of course this module seems to be dead for a few months).
And a bunch of adblockers.
And a hell lot mods that I don't remember from the top of my head, but it was really magic.. And it is slowing down (I feel so..)
Well, someone might say that we can install Xposed itself as a module, but that just crashes the "SafetyNet" which is very annoying, it makes the phone useless without being able to open GooglePay and other banking apps.
I know I might be wrong but I am posting just to see if people use any equivalent "cool" modules in Magisk that are not easily seen in the Magisk Modules repo or if someone has found a way to pass the "SafetyNet" with Xposed+Magisk to make Android awesome again!!:good:
Click to expand...
Click to collapse
Magisk doesn't work the same way as Xposed,one mounts and modifies files and the other hooks and modifies app code at runtime,and yes there is a way to use Xposed and pass safetynet if you are either on Oreo or Pie,it's called Edxposed
Edxposed is an open source Xposed alternative released early this year that uses a different method to hook into the system which allows it to pass safetynet and it allows you to blacklist apps in which you don't to load Xposed into,and if you are in pie there is already a beta of gravitybox that fully supports Pie (it's not yet in the Xposed repo because it's not fully stable yet)
Here are some pictures showing edxposed passing safetynet and me using the event lock module on Android pie,incase you are interested here are the links to edxposed https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513 it works on both Oreo and Pie (ignore the last step and just use edxposed installer) it's the last link and the first post,if you have any doubts feel free to ask there
DanGLES3 said:
Here are some pictures showing edxposed passing safetynet and me using the event lock module on Android pie,incase you are interested here are the links to edxposed https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513 it works on both Oreo and Pie (ignore the last step and just use edxposed installer) it's the last link and the first post,if you have any doubts feel free to ask there
Click to expand...
Click to collapse
A Hope!!
Thank you very much for the info, will try and post an update..
Even after these many years of launch people seems to not understand Magisk purpose, features and way of work. Same for Xposed.
Does Magisk has "modules" ? Yes! Does Xposed has "modules" ? Yes! But that's it. The name. The only thing in common between Magisk and Xposed is _the name, the word, "module" _ for their respective plug-ins, addons. Nothing more. Period.
Magisk attachs to Android, works completely different from the way Xposed does. What they do and what they can do are different. They are not even closer to be an alternative of one to another.
Having that said, do not expect that modules of one can deliver similar features of a module of another. If this somehow someday for an specific pair of modules happen be sure they are accomplishing that but doing in complete different ways behind the scenes.
About Xposed not breaking SafetyNet, we have now for Android O+ the alternatives EdXposed (open source) and Tai Chi (closed source). They do not break it because the way they're implemented is different from original Xposed by Rovo. They are different approachs, new code with new ways of work, but that delivers same entrance points, same nomenclature, as original Xposed itself. Thus being (generally speaking) compatible with modules originally built to original Xposed.
Both EdXposed and Tai Chi are experimental yet, although working fine at least on Android P. If they show themselves as solid solutions then probably we will see new Xposed like modules appearing out there. I do hope so.
wilsonhlacerda said:
Even after these many years of launch people seems to not understand Magisk purpose, features and way of work. Same for Xposed.
Does Magisk has "modules" ? Yes! Does Xposed has "modules" ? Yes! But that's it. The name. The only thing in common between Magisk and Xposed is _the name, the word, "module" _ for their respective plug-ins, addons. Nothing more. Period.
Magisk attachs to Android, works completely different from the way Xposed does. What they do and what they can do are different. They are not even closer to be an alternative of one to another.
Having that said, do not expect that modules of one can deliver similar features of a module of another. If this somehow someday for an specific pair of modules happen be sure they are accomplishing that but doing in complete different ways behind the scenes.
About Xposed not breaking SafetyNet, we have now for Android O+ the alternatives EdXposed (open source) and Tai Chi (closed source). They do not break it because the way they're implemented is different from original Xposed by Rovo. They are different approachs, new code with new ways of work, but that delivers same entrance points, same nomenclature, as original Xposed itself. Thus being (generally speaking) compatible with modules originally built to original Xposed.
Both EdXposed and Tai Chi are experimental yet, although working fine at least on Android P. If they show themselves as solid solutions then probably we will see new Xposed like modules appearing out there. I do hope so.
Click to expand...
Click to collapse
Couldn't have said it better (my previous texts were written at 3am so pardon for any mistake I did XD)
Hello!
Is the magisk safe to use, or will i get banned in netflix/google account etc?
Thank you for any answer regarding my issue
That depends on what you mean by safe.
You are unlocking your bootloader and modding your device when installing Magisk, so you are in some ways making your device less safe against certain kinds of things (like if someone gets physical access to your device, etc).
Many apps look for modifications and a rooted device and won't work if they detect it. That's where MagiskHide comes in and can hide Magisk from most detection methods. Google is stepping things up though and they have briefly showed us that they are on the way to implement proper key attestation in the SafetyNet CTS profile check. That is not something that Magisk will be able to hide from and as soon as that is implemented properly there is nothing we will be able to do.
So far you shouldn't be worried about getting banned (most of the time), but some services will not work if they can detect root. Netflix is one of them, Google Pay, banking apps, some games, etc. Some services might ban you (maybe Snapchat), but as far as I've seen those are in the minority.
Another aspect of being safe is that you should be careful with what apps you allow to have superuser access. With su, an app/service can wreck all kinds of havoc...
There's a lot to be said on this subject and I'm sure others will join in. If you search around a bit you can find lots of info on pros and cons of having an unlocked booloader, rooting, modding your device, etc.
Overall I'd say yes, the Magisk is safe. The Magisk and the modules that are available, much like the hammer and sickle, has the ability to be abused by the users when used for other purposes outside of its scope.
It's not malware either, if that's what you meant.
it is safe if you are know what you doing
I specifically recall this being present in 20.4. But ever since I have updated to 21.1, there is no core only mode option in the manager. Has it been removed? If not, how to enable it? And if it's been removed then...WHY?! I find it very useful for troubleshooting/diagnostics.
It has indeed been removed, in favour of Safe Mode, a much more reliable way for users to disable their modules in case of not being able to boot.
As to why it was removed, you'd have to ask John. But if I would have to guess: to remove some complexity in a very complex system.
@Didgeridoohan: If @topjohnwu really wants to reduce complexity, then I'd suggest that he release a separate "Magisk Lite" that is su only. No modules support, hiding, core only, SafetyNet testing, bind mounting, script execution, etc. *JUST ROOT*. He could just make it a separate branch that only receives occasional updates, when they're necessary. I honestly use very little of Magisk's functionality with the exception of root. I'd donate a decent amount of money for a Magisk that is root only without all the extra fluff. Simply by virtue of being a systemless module framework, he has already made it extremely complex with that alone.
If you have ideas for features you can always post those on GitHub.
I'm not clear on the differences between them, and it seems that there are even more alternatives.
Is one better than another?
I just got an Android 10 phone, was previously on 7 for a short time, but was otherwise still on 5 and 6.
AllanonMage said:
I'm not clear on the differences between them, and it seems that there are even more alternatives.
Is one better than another?
I just got an Android 10 phone, was previously on 7 for a short time, but was otherwise still on 5 and 6.
Click to expand...
Click to collapse
The main difference is that in LSPosed you have to whitelist apps to be hooked instead of blacklist. The second one is that EdXposed seems to break SafetyNet in latest version. And it seems that it's not that actively developed as LSPosed
They both have whitelist and on LSPosed it set in default. But only EdXposed have blacklist. I saw some comment like "have too much modules and too much apps to hook, how painful to check everything by manually".
Yes, Edxposed still break SafetyNet.
Yes, now Edxposed is not that actively update than LSPosed.
Something about LSPosed
If you can read Chinese, maybe you can read these below: https://www.bilibili.com/read/cv9603603/ https://www.bilibili.com/read/cv9603669/ https://www.zhihu.com/question/442534533 https://www.zhihu.com/question/442531709 I am very troubled by...
forum.xda-developers.com
I personally tried both. Not that much difference. Yeah, because basically LSPosed just forked Edxposed and did a little improvement.
In the end I choose Edxposed rather than LSPosed. Because I can't trust one dev who made a prank about "rm -rf" and the rest dev have no objection to this and even help him to hide it. And those personal attack with filthy language of course.
Arakawa. said:
They both have whitelist and on LSPosed it set in default. But only EdXposed have blacklist. I saw some comment like "have too much modules and too much apps to hook, how painful to check everything by manually".
Yes, Edxposed still break SafetyNet.
Yes, now Edxposed is not that actively update than LSPosed.
Something about LSPosed
If you can read Chinese, maybe you can read these below: https://www.bilibili.com/read/cv9603603/ https://www.bilibili.com/read/cv9603669/ https://www.zhihu.com/question/442534533 https://www.zhihu.com/question/442531709 I am very troubled by...
forum.xda-developers.com
I personally tried both. Not that much difference. Yeah, because basically LSPosed just forked Edxposed and did a little improvement.
In the end I choose Edxposed rather than LSPosed. Because I can't trust one dev who made a prank about "rm -rf" and the rest dev have no objection to this and even help him to hide it. And those personal attack with filthy language of course.
Click to expand...
Click to collapse
The developer you mentioned has left the development group long ago
All I wanna know is which one passes safetytest. Installed edxposed for the first time in 2 years only to discover that safetytest is completely fubar'd. And all the tutorials I've found are old and seemingly obsolete.
This moment, LSPosed is alot better than EdXposed.
Simple that.
I say many thanks to EdXposed, but LSPosed is the future.
We Love EdXposed
We Love LSPosed
We Love Better Future
More than 100 commits less than 20 days
Commits · LSPosed/LSPosed
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Arakawa. said:
who made a prank about "rm -rf"
Click to expand...
Click to collapse
Which prank? Will you share the source of the prank? Plz let us know.
Edit: Sorry, haven't noticed the quoted post, got it.
cracky.ice said:
The developer you mentioned has left the development group long ago
Click to expand...
Click to collapse
The man left temporarily, but what he had done was still there. And the rest of the developers don't think rm -rf is wrong. The whole development team had problems, they even excused the malicious code. Communities should not forgive this.
LSPosed is not a good choice for Xposed: from the software itself, module scopes and Xposed Hide (White) were designed as advanced features for advanced users only, and forcing them to be enabled is abusive and will increase the learning cost for users, increase the cost for module developers, break the functionality of global modules, and make modules much less compatible. On the developer level, the LSPosed development team has been suppressing and abusing other Xposed implementations and their developers since the project's inception, attacking third-party ROM developers with web violence, and committing community divisive acts like this; one of the development team members submitted rm -rf /* malicious code to EdXposed, which was responsible for emptying CI user data. The culprit has no credibility.
mlgmxyysd said:
The man left temporarily, but what he had done was still there. And the rest of the developers don't think rm -rf is wrong. The whole development team had problems, they even excused the malicious code. Communities should not forgive this.
Click to expand...
Click to collapse
We will never forgive.
But it is past.
We just need MORE attention before to accept any commit.
We will have bad people everywhere.
Nothing more.
mlgmxyysd said:
LSPosed is not a good choice for Xposed: from the software itself, module scopes and Xposed Hide (White) were designed as advanced features for advanced users only, and forcing them to be enabled is abusive and will increase the learning cost for users, increase the cost for module developers, break the functionality of global modules, and make modules much less compatible. On the developer level, the LSPosed development team has been suppressing and abusing other Xposed implementations and their developers since the project's inception, attacking third-party ROM developers with web violence, and committing community divisive acts like this; one of the development team members submitted rm -rf /* malicious code to EdXposed, which was responsible for emptying CI user data. The culprit has no credibility.
Click to expand...
Click to collapse
YES.
Xposed is for ADVANCED USERS only !!!!
Xposed is not a play for kids.
I agree with you about the difficulty for developers, but well, the future is here.
And we will not accept to remain in the past.
Long Life to LSPosed
But, we love EdXposed too
VD171 said:
YES.
Xposed is for ADVANCED USERS only !!!!
Xposed is not a play for kids.
I agree with you about the difficulty for developers, but well, the future is here.
And we will not accept to remain in the past.
Long Life to LSPosed
But, we love EdXposed too
Click to expand...
Click to collapse
Put away your false future, Xposed (even ROMs) will die because of LSPosed Developers. You don't know what disgusting things LSPosed Developers are doing behind the scenes.
mlgmxyysd said:
Put away your false future, Xposed (even ROMs) will die because of LSPosed Developers. You don't know what disgusting things LSPosed Developers are doing behind the scenes.
Click to expand...
Click to collapse
The point is we need xposed for Android 9, Android 10, Android 11, Android 12, Android 13, Android 14...
We currently have no choices.
Or do you have any?
VD171 said:
The point is we need xposed for Android 9, Android 10, Android 11, Android 12, Android 13, Android 14...
We currently have no choices.
Or do you have any?
Click to expand...
Click to collapse
There will be, just need to wait.
mlgmxyysd said:
There will be, just need to wait.
Click to expand...
Click to collapse
I can't wait.
I have a solution, so I will use it.
But, I'm totally open for new XPOSED alternatives.
Let's keep watching
I did a test with the old original Xprivacy app. Oreo 8.1, Magisk v23, Riru v 25.4.4
With EdXposed: it works, but whole phone is slowed down. Every app is checked and Xprivacy popup asks you how to proceed (accept or deny internet/load/whatever request). It works how it should but sadly phone is slowed down and wallpaper doesn't load after phone bootup
With LSposed: it doesn't work, because: Every app just bypasses most Xprivacy functions, you only get a meaningless Binder Xprivacy popup. Xprivacy has no control over what apps do. Apps do what they want and don't ask for your permission
With Xposed Installer: it runs perfectly, flawlessly. Using the good old "Xposed Installer" with Xposed Framework version 90-beta3, the original. You know every url and request every app does, if they scan your nearby wifi, if or when they use record in cam or audio, scan your contacts, request some device identifiers, you can whitelist the urls, internet requests and loads you want. All app requests logged, apps can't do nothing without your permission. Very useful because you can use (whitelist) the functions in any app that you use and want, and dismiss the rest that's bundled within the app (ad networks, telemetry requests, proprietary functions. resource-hungry unnecessary actions). In the new XprivacyLua these features and logs and this sort of control is not possible. This is why the old original Xprivacy is superior.
jason382 said:
I did a test with the old original Xprivacy app. Oreo 8.1, Magisk v23, Riru v 25.4.4
With EdXposed: it works, but whole phone is slowed down. Every app is checked and Xprivacy popup asks you how to proceed (accept or deny internet/load/whatever request). It works how it should but sadly phone is slowed down and wallpaper doesn't load after phone bootup
With LSposed: it doesn't work, because: Every app just bypasses most Xprivacy functions, you only get a meaningless Binder Xprivacy popup. Xprivacy has no control over what apps do. Apps do what they want and don't ask for your permission
With Xposed Installer: it runs perfectly, flawlessly. Using the good old "Xposed Installer" with Xposed Framework version 90-beta3, the original. You know every url and request every app does, if they scan your nearby wifi, if or when they use record in cam or audio, scan your contacts, request some device identifiers, you can whitelist the urls, internet requests and loads you want. All app requests logged, apps can't do nothing without your permission. Very useful because you can use (whitelist) the functions in any app that you use and want, and dismiss the rest that's bundled within the app (ad networks, telemetry requests, proprietary functions. resource-hungry unnecessary actions). In the new XprivacyLua these features and logs and this sort of control is not possible. This is why the old original Xprivacy is superior.
Click to expand...
Click to collapse
No. Xprivacy is NOT superior.
Xprivacy is totally deprecated and uses old methods and old functions.
XPRIVACYLUA is totally better, superior and CUSTOMIZABLE.
XprivacyLua WORKS PERFECTLY WITH LSPOSED, because I am using it on my main phone.
I LOVE XPRIVACYLUA.
I CAN'T LIVE WITHOUT ROOT, XPOSED AND XPRIVACYLUA !!!!
I LOVE YOU @M66B
LSPosed is the future and as of this date clearly the winner as Edxposed development has halted, it's incompatible with the latest Riru and breaks Safetynet.
We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
You can vote at the LSPosed Telegram group or write your opinion here. Also we are glad to hear your suggestions about the new API.
@AndroidX @siavash79 @Dark_Eyes_ @firefds @David B. @Quinny899 @wanam
Just mentioning you guys since you're all active here on XDA. Please see the first post.
Regards,
shadowstep
Senior Moderator
Dr-TSNG said:
We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
You can vote at the LSPosed Telegram group or write your opinion here. Also we are glad to hear your suggestions about the new API.
Click to expand...
Click to collapse
Thanks for getting opinions
1. Xshared preferences interface overhaul is good news since it was always unstable for me. I personally switched to remote preferences API for AOSPMods
2. When going to systemUI and framework, it's sometimes very difficult and complicated to change some variable values through Xposed, specially with R8 code optimizations which dramatically limit the points we can hook into code.
There are two workarounds I know of, being Xposed resource hooking that can be also dynamic in runtime, or overlays, which being static, still limit the way we can change resources dramatically.
So, I'd really suggest keeping it in the API
siavash79 said:
2. When going to systemUI and framework, it's sometimes very difficult and complicated to change some variable values through Xposed, specially with R8 code optimizations which dramatically limit the points we can hook into code.
Click to expand...
Click to collapse
For R8 code optimizations, we introduced a new API to parse dex file, which allows modules to find methods/fields more accurately.
Anyway if we finally decide to keep resources hook API, do you have any suggestions on keeping/adding/removing specific methods of it or refine it to a more modern interface?
Perfect news.
About resource hooking, few things to note are that: it can't differentiate between different resource files, for example normal values vs landscape or dark/light values. It would be great if there's a way to push different values to different resource files.
Also, there are more limitations when talking about special resources such as themes. As an example, in AOSPMods, one of the reasons it's a magisk module instead of being a normal APK is that overlay files have to be used in cases that need modification of theme resources and that can't be done via resource hooking.
I personally love to get a more complete/flexible resource hooking API, but I completely understand if that's too much to ask. So even keeping it as currently is would be good enough
Thank you @shadowstep for bringing this to my attention!
Dr-TSNG said:
We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Click to expand...
Click to collapse
That's wonderful news, although I do not quite understand what you have against the new XSharedPreferences interface. I use it in my modules, and I've never had any issues with it.
Dr-TSNG said:
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
Click to expand...
Click to collapse
I am not currently using the resources hook in any of my modules, so removing it would not impact me, but even so, I'm not a fan of the suggestion to get rid of it completely. I think that at the very least, it should be kept as maintain-only. It is unfortunate that it does not work with Taichi, but given that Taichi isn't a true Xposed implementation, I'm not sure that it's worth worrying about.
This looks great, I've been waiting for it since the initial issue talking about it. Prefs are always a pain to handle, and while the "new" method worked, I always preferred to use a Content Provider, which was nerfed in Android 12.
Really like the idea of setting the scope, it would be beneficial to the Xposed part of DarQ, the only suggestion I have is to make sure it includes some sort of "am I enabled?" check - currently I use self hooks (literally the module hooking itself and changing a method returning false to true) to verify it's enabled, but it doesn't seem to be foolproof as people sometimes still complain it doesn't work.
Quinny899 said:
the only suggestion I have is to make sure it includes some sort of "am I enabled?" check
Click to expand...
Click to collapse
Of course does, and the module app can get more info about the the Xposed state like it's under which framework and which version, and whether it is rootless or not without self-hooking.
You can view the detail here.
@shadowstep Thanks for the head up.
Glad to see a new api to manage configs across apps, shared prefs has been always painful to handle even with the new-xshared prefs.
I would suggest having an api to get the version name of scope's package, I'm aware of some workarounds that help get the version name, but it's not a reliable solution on the latest Android versions, this information is needed for logging/debugging purposes.
@Dr-TSNG thanks and keep up the good work.
@Dr-TSNG Thanks for new api I was wating for this api from more then 1 year coz when I build my first module (Android Faker) its was really pain in ass coz of Xsharedpreference after some research I found better solution which was remote preference but Quinny899 mention in Github issue that its not work in android 11 so after that I move to new Xsharedpreference which was introduce by lsposed team and its working great but its still create issue in some devices so I think it will be a better solution if we get it soon and I am not sure about resources hook coz I don't use it before .
The problem with xshared preferences is that if the apk is a system app it won't work for some reason. Only works on user apps
siavash79 said:
The problem with xshared preferences is that if the apk is a system app it won't work for some reason. Only works on user apps
Click to expand...
Click to collapse
Interesting. I use XSharedPreferences in a System Framework hook and haven't had any issues with it.
David B. said:
Interesting. I use XSharedPreferences in a System Framework hook and haven't had any issues with it.
Click to expand...
Click to collapse
Is your module installed as APK or as magisk module?
Try mounting it to system through magisk and preferences will stop working
siavash79 said:
Is your module installed as APK or as magisk module?
Try mounting it to system through magisk and preferences will stop working
Click to expand...
Click to collapse
It's installed as an APK. I misunderstood what you had said earlier. I thought you meant that the hook doesn't work when you try to use it on system APKs. I didn't realize that you meant that it doesn't work when the module is itself a system APK.
siavash79Yeah I agree with this and in my testing if you set target sdk 23 its doesn't matter if its as system app or user its work without any issues but its not worth coz it have some other issues
Thank you for accepting the API invokeSpecial() !
Add invokeSpecial · libxposed/[email protected]
Fix #2
github.com
Implement invoke special and new instance special · LSPosed/[email protected]
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Looking forward to the new API release.
Happy Chinese New Year!
I just want to see @M66B happy again
Somewhat unrelated, but is there any chance of seeing original Xprivacy return or compatibility? I think it's a lot better than Lua
lawrencee said:
Somewhat unrelated, but is there any chance of seeing original Xprivacy return or compatibility? I think it's a lot better than Lua
Click to expand...
Click to collapse
No. Xprivacy will never "return".
XPrivacyLua is the best ever