yashsingh1/xdaforums huggingface dataset:
[Xposed General] enetec:
Tested "new" v.0.5.1.0... 😏

Ambient: Moto Z2 Force on Android P stock

Magisk: 21100

Riru: 23

EdXposed: 4603 Sandhook

Boot? Yes, quite fast, few errors on logs.

Loads? NO. EdXposed installed fine, detected too, but it doesn't start.

(I've logs but... they don't like my tickets... 😏)

Xposed modules working: NONE (obviously...)

Rolled back once again to 4569... 😑
[Xposed General] Mikanoshi:
I don't envy you then :D

What are you doing? :) You obviously have a lot of free time to rip canary builds basically in the middle of active development in hope of getting stable framework and modules.

Want to help devs debug a build? You don't even post logcat during boot, I'm sure devs will appreciate it if it's not accompanied by condescending remarks.

Just wait for a release. I won't even consider EdXposed 0.5+ until devs decide it is stable enough for a release.

If they bring back XSharedPreferences to life and make them reliable then updating Xposed modules would be trivial.
[Xposed General] enetec:
What am I doing?

Simple... I'm just showing (and warning users...) that are about *33* (thirtythree!) consecutive Canary versions which don't work at all on a quite stock system as mine...!!!

I think it's clear that something is going wrong with development lately.

More if you consider we don't have any stable or beta compatible with Riru v.22/v.23...

I posted my logcat on GitHub when I still could (but they said they haven't the time to look on them...), now I can't anymore, and not for my choice.

If they want them, they have simply to ask for.

And no... I've not "a lot of time"... but I have a spare device for my tests and I'm enough trained to do a test in few minutes... and I HATE when a good project is going ballistic because of... dumb ideas!

P.S.: please note that we have never had before so many "bad canary" versions and, together, never had so few open tickets on official GitHub (less than 20 vs. an average of 40/50 in the past...). They are simply closing all of them with no reply/solution/analisys/fix. Just take a look to check... 😏
[Xposed General] JudgeDread11:
Before anybody tries the canary, please read the warning.

For who doesn't understand what this means:

These are builds that are being built automatically when a change (small or big) has been made, without any checks. These changes could be anything from improvements to tests or temporary changes.

No stability or improvement is guaranteed and if it doesn't work no claims can be made. And this has nothing todo with how many versions (changes) had been made.

On top of that the devs work on this and provide this to the community without asking for anything in return.

They can do with it whatever the f they want. The only choice we have is accept our help improve.

If they feel we are not grateful or they don't enjoy doing what they are doing anymore it's their full right to take everything down.
[Xposed General] enetec:
Well it's not exactly this way... 😏

When you decide to develop a sw (any type of sw...) and you decide to go public with it you have *anyway* some responsability towards your users (read "support", sources, contact channels, communication and so on...).

If you don't like this or you think it is too "hard" for you, or you are simply not so keen on receiving negative feedback on your development, you should work *only* for yourself and not for "public". 🙄

When you decide to go public you _implicitly_ agree to receive (hopefully...) good but even bad feedback eventually. And it's not banning or ignoring users who reports documented issues that you don't like that would make your work better...

About the Canary versions, only two comments...

- I know exactly what they are BUT if we are talking about those is because we don't have (and they don't want to develop too...) a working stable or an alpha/beta able to simply recognize Riru v.22/23...

- I have *ever* tested Canary in past and *never* found 33 consecutive not working releases... somethin' wrong is happening.

And I shouldn't be the only reporting this.... 😑

So, please, save your "lessons" and let me do (and report...) my tests...
[Xposed General] TNSMANI:
Guys, already a Moderator has posted a message on 7th of this month to keep things under control. Though I would say that this has not so far crossed the line it looks to be on the way to it.

So unless the interaction remains civil and useful, Moderators would have to intervene. Please avoid such a situation and we would be thankful for it.

Cheers!(y)
[Xposed General] enetec:
I agree. I would like to not have somebody coming out every time to comment my tests reports.

Every time. 😉
[Xposed General] Mikanoshi:
- There is no stable EdXposed that supports Riru 22+ and they don't have to create one. What do you need it for? To hide Riru? EdXposed 0.4 injects its classloaders into zygote process that is then forked to all other processes and this can be detected, so there is no point in updating EdXposed 0.4 for Riru 22+. At least that's how I understand it.

- Intermediary builds are buggy, so what? Use stable branch.
[Xposed General] Lord Sithek:
But doesn't stable EdXposed work on Android 11, does it? 🤔 I think most of us are interested in progess with EdXposed for the latest Android version... Me too, although I still use stable
[Xposed General] enetec:
You missed the point sorry...

Most of users are not XDA experts, they got Magisk, download latest stable versions by market and install them. Point.

These are Riru v.23 and EdXposed v.0.4.6.4 4563 and boom... It doesn't work.

So what? Beta? None. Alpha? None. Canary? And bootloops. Bang.

Do you understand now?

Canary are buggy? 4469 is buggy (not all modules work fine...).

The successive 33 (thirtythree...) "intermediate" don't work AT ALL (most with bootloops!).

It's pure nonsense to continue with wrong direction.

When things aren't going as hoped it's time to rollback and start again from scratch.

Capish?!? 😒

It seems to me that many of you, simply, don't want to understand... 😏
[Xposed General] Lord Sithek:
Well, I agree with you with the most part and I'm grateful for your tests, but... I'm sure that as the developer of the best MIUI Xposed module @Mikanoshi is well aware of what is involved with it 😏
[Xposed General] enetec:
You are right. It doesn't. Not with ANY Riru (for different reasons...).

More... when, AT LAST we will (hopefully...) have a "stable" v. 0.5.x.x you'll find that *many* Xposed modules won't work anymore.... (this is the reason I'm trying to advise you all) because of the wrong development choices done with v.0.4.x.x -> v.0.5.x.x transition...

What's the point of having an Xposed unable to run most modules?
[Xposed General] Mikanoshi:
So your problem is that your don't read changelogs before updating modules from Magisk repo, now I understand.

Riru was updated first, it's impossible to support it before the release. Just go back to 21.3, stable EdXposed is not compatible with 22+, that happens.
[Xposed General] enetec:
New test...

Ambient: Moto Z2 Force on Android P stock

Magisk: 21100

Riru: 23

EdXposed: 4604 Sandhook

Boot? Yes, quite fast, several errors on logs.

Loads? NO. EdXposed installed fine, detected too, but it doesn't start.

Xposed modules working: NONE.

34! 😑
[Xposed General] enetec:
Wow, amusing. 🤓🎈
[Xposed General] enetec:
Interesting points of view... 😏

[Bug] Ignored and Serious Bug · Issue #697 · ElderDrivers/EdXposed

Respectfully to the devs, I know this has been in the knowledge and you've done an announcement in this regard, but I would really love if the respected devs can give a transparent and clear cut an...

github.com
[Xposed General] Mikanoshi:
See, everything was answered 2 weeks ago already. And it's hard to take a person seriously when he can't even write the name of the framework correctly.
[Xposed General] yujincheng08:
Well, as one of the devs of EdXposed, let me clarify the thing AGAIN as I said 2 weeks ago.

It's IMPOSSIBLE to do a quick fix for the compatibility for Riru22+.

The injecting strategy of Riru changed and the timing of loading Riru modules has been postponed. So, we can no longer get pointers of Runtime and ClassLinker by hooking their constructors.

So, EdXposed is not of one those 99% Riru modules that can do a quick fix.

Someone, claiming himself as an IT professional, just ignored this fact and keep forcing us to do a quick fix. Shame on him.
[Xposed General] TNSMANI:
Well, guys, I think that enough has been said already and all of you have made your points clear. And one of the Devs himself has clarified the issue. I request all of you to refrain from further arguments on this.

Any of you who would like to continue in this line even after this is free to do so on Conversations (PM). Any further posts on the same lines will be removed.
[Xposed General] Mikanoshi:
So are pre-fork hooks in initZygote no longer possible because of Riru or it's an intentional EdXposed 0.5+ stealth feature?

I'm confused about the injection, both in old regular mode and in app list mode.

What classes are available for hooking when initZygote() is called with startParam.startsSystemServer == true and false, in both modes?
[Xposed General] yujincheng08:
It's partially because of Riru. We introduced Dobby for the Riru compatibility and it somehow causes camera crashes on some devices. So we need to keep the zygote process clear to fork other processes.

And startParam.startsSystemServer == true should only appear once (for system server). Other app processes won't have it true. This is ensured in 0.5.x ver. I don't know if 0.4.x has some bugs that make it true for app processes.
[Xposed General] Mikanoshi:
What's Dobby? :) I thought clear zygote is for detection prevention.

But in 0.5 there is no place to store a system-wide data for the mods, even with working XSharedPreferences every time ANY process is created it will have to not only load shared prefs xml, but also apply all the hooks to framework classes from initZygote. Not having data forked from zygote is terrible for performance.

As I understand, in regular mode initZygote is called twice - once for zygote itself, once for system_server. Zygote loads classes from framework.jar and some others, system_server additionally loads services.jar. If I want to hook framework class and make it work everywhere I have to apply hook both times, right? Some modules like GravityBox check startsSystemServer and hook only when it's true, but that means framework hooks will only work for services. Unless module has no system-wide framework hooks I have no idea how that can work at all.
[Xposed General] anjarys:
Why riru change its injection strategy? Is it an urgent to do so right now?
[Xposed General] yujincheng08:
Dobby's an inline hook framework.

Yes, I see your point of performance consideration. So we recommend users to use the whitelist mode and the module activation scope to retain the minimum number of hooks.

And, there's nearly no module that needs to hook system-wise. Most of the things can be done in the system server process, like CorePatch or something the gravity box does. And the rest of things can be done by some system package say, systemui, or so. I mean, hooking contacts or so isn't meaningful most of the time.
[Xposed General] yujincheng08:
This is for better hidden.
[Xposed General] anjarys:
Ah i see. Great work.

But can you make those two different version (below 22.x and 22.x up) available side by side on the magisk repo? At least until everyone ready for the big updates.

Let the user chose for the meanwhile. I think that give better options and everyone can calm down for a moment.
[Xposed General] yujincheng08:
Jhon Wu, dev of magisk always complains about having two backend of edxp. So, it's not a good idea.
[Xposed General] TNSMANI:
MOD ACTION:

Thread cleaned. I request all of you to read my previous post.
[Xposed General] enetec:
We were doing a productive discussion for a better product.

You deleted my posts which required my time to be written and taken no action in past on offending posts.

This not so different to close tickets as they did on Github. You are doing their game this way.

This is not respectful. So I won't partecipate anymore to this thread.

You'll be happy. Users less, I'm sure. Bye. 👋
[Xposed General] Mikanoshi:
Any examples how to use these scopes? What do they do? Make initZygote hooks apply only to a selected packages similar to handleLoadPackage?

I have tons of mods in my module that hook:

android.content.res.Resources (replacement for broken IXposedHookInitPackageResources that works for dynamically loaded resources only of course)
android.view.WindowManagerGlobal
android.view.Window (some action that must be done in setFlags() of every single window)
android.app.Activity (some action that must be done in onCreate() or onResume() of every single activity)
android.app.Notification.Builder
android.media.session.MediaSession
android.media.MediaPlayer
android.media.SoundPool
android.app.NotificationChannel
android.appwidget.AppWidgetHostView
android.widget.Magnifier
android.widget.Toast
android.widget.AbsListView
android.provider.Settings
com.android.internal.widget.LockPatternUtils

And a lot of MIUI-specific ones:

android.app.MiuiNotification
android.media.AudioServiceInjector
android.provider.MiuiSettings
android.util.MiuiMultiWindowAdapter
miui.maml.ScreenElementRoot

I don't see how there can be alternative hooks for them in system_server, because they can be used by any process in the system and those processes are forked from zygote.

CorePatch has such hooks too btw:

coderstory/CorePatch

Disable signature verification For Android. Contribute to coderstory/CorePatch development by creating an account on GitHub.

github.com

I also have a mod to disable signature verification in my module and it also hooks android.content.pm.PackageParser.
[Xposed General] yujincheng08:
For example, I have a youtube adway module, and I can set the scope of this module to only hook youtube, other hooked apps won't load this module. This is done by EdXposed and this is transparent to modules.

There may be some ways by hooking like systemui to do so.

I know Coderstory well, and his module only needs to hook systemserver. You only have to hook the backend of PM. And the frontend is contacting the backend by binder.
[Xposed General] Mikanoshi:
Got it, it will certainly improve performance by breaking mods for all blacklisted/non-whitelisted apps :)

Use SystemUI to modify MediaPlayer framework class that can be used by any app? I somehow doubt that.

There is no alternative, classes loaded in zygote are forked to other apps, without this all framework hooks must applied to each process separately. That's by design.

Maybe, but that is not reflected in the source code, it still hooks both zygote and system_server processes.
[Xposed General] yujincheng08:
Take toast for example. It uses `NotificationManager` to finish its showing. So definitely you can hook `NotificationManager` in the system server to implement most of the tweaks.
[Xposed General] Mikanoshi:
Not all framework classes are front-ends for the services, MediaPlayer for example is mostly a static class that calls native methods directly.

Even in example above there is android.widget.ToastInjector class in MIUI that modifies the title of a toast depending on device before sending it to service, so to remove that I'll have to parse a title's string. I'm just saying that app list mode is bad for system-wide framework hooks by design and there is no easy fix.
[Xposed General] yujincheng08:
I know. At that time you can tell users to enable scope for apps that use MediaPlayer.

Hooking all apps is a very bad idea nowadays. Many reports were received that once we hook zygote, the camera will crash.

[BUG] Camera app issue · Issue #711 · ElderDrivers/EdXposed

什么情况/What happened? Camera app crashes when edxposed is installed 如无法开机/模块无效等 Xposed模块列表/Xposed Module List Jasi Patcher (disabled) Magisk模块列表/Magisk Module List Riru Core EdXposed YAHFA EdXposed及R...

github.com

[BUG] Google camera 8.x crashes upon opening · Issue #727 · ElderDrivers/EdXposed

什么情况/What happened? After Nov 17th app update to Google camera v 8.1 the app will crash upon opening of Edxposed is enabled. 如无法开机/模块无效等 Xposed模块列表/Xposed Module List Fingerface Edge Sense Magisk模块...

github.com

[BUG] can't access camera on miui 11/12 · Issue #707 · ElderDrivers/EdXposed

什么情况/What happened? camera app doesn't work and if an app trying to access camera, the app freeze 如无法开机/模块无效等 Xposed模块列表/Xposed Module List nothing 允许截图/Screenshot allowed Magisk模块列表/Magisk Module ...

github.com

So, we have to preserve zygote as pure as possible. Note that the crashes aren't caused by detection.
[Xposed General] Mikanoshi:
I heard something about meta data in module's manifest to define scopes.

Anyway, I have 250 mods in my module and tons of hooks, I think neither I nor users want to manually scope them.

Especially when some mods only make sense when hooking all apps.

And the source of the issue is unknown? I've never used app list mode, so I'm hooking everything, MIUI camera and GCam are working fine on MIUI 11/12, basically on every ROM I ever used.
[Xposed General] yujincheng08:
There is such a plan. However, mlgmxyysd does not want to enable it by default. It's just a useless hint btw.

We know what causes it: inline hook of Heap and ClassLinker. But we don't know why and how it crashes. The crash point is weird and many people reported it. (One of our dev @kotori2 can reproduce it, btw.)
[Xposed General] kotori2:
I believe the source of the crash is some anti-Xposed things. Even single art::Heap hook will cause Gcam crash. The source of the crash is a Java branch that you will never reach. Also Gcam has some heavy-obfuscated code and even a VM which make me believe they are anti-hooking.
[Xposed General] simcold:
EdXposed works on miui12 android 11? (xiaomi mi10)
[Xposed General] MaXAiRO:
Yes, use latest Riru from magisk repo and EdXposed Canary 0.5.0.6 from Edxposed Manager.
[Xposed General] purgy:
Is there a version of edxposed which is compatible with Riru 21.3 and passes SN? Afaik gravity box has issues with later versions of Riru, and if I have to pick GB or SN, GB wins. Running A10 if relevant.
[Xposed General] Tyakrish:
Thats awesome. :D

Edit: The Canary Build passes.

Bigger Hammer no doubt :D

---------- Post added at 10:56 AM ---------- Previous post was at 10:26 AM ----------

No such problem here. It passes even if Edxposed Manager is hibernated.
[Xposed General] adriansticoid0312:
Which Google apps did you blacklisted? For me it fails,and then I launch the manager, then it succeeds again.
[Xposed General] Hirs_E_Fruit:
[MENTION=7530619]Tyakrish[/MENTION]

[MENTION=8430637]mlgmxyysd[/MENTION]

It shows me the message "EdXposed Framework is installed, but not active"

Is there special Mangager or set up for the canary build (4536)?

YAHFA

v4.5.5 (45510) shows active while above I get the not active message
[Xposed General] Al765436:
What is 4536,,,? you could make sure autorun is enabled and have no battery restrictions on it, and lock it in memory through recents menu
[Xposed General] Soumy1234:
In Edxp Manager 4.5.7, there's a new Enhanced mode. I think it's made partially to allow Edxposed Manager to run in the background. It shows up as a module in the modules section and you have to enable that.
[Xposed General] adriansticoid0312:
That did the trick. Thank you!
[Xposed General] svendsvin:
Shouldn't the Edxposed manager get superuser rights? Can I somehow grant it myself?
[Xposed General] Soumy1234:
Edxp Manager doesn't need superuser permissions except if you want it to install Xposed modules automatically without a prompt. You can do this by enabling Silent Installation (Root) in Edxp Manager settings.
[Xposed General] DarkSJ1998:
I have Magisk v20.3 installed with Riru Core v19.8 & EdXposed 0.4.6.2 YAHFA, all the modules are working fine, but EdXposed Manager shows this.

Whats should I do? The logs also show nothing.

Logs : https://drive.google.com/file/d/108rwG4gPIt4nHgewV2M-HycfbYH4Z_Ly/view?usp=drivesdk
[Xposed General] Keule-Tm:
Sometimes another reboot does the trick.
[Xposed General] DarkSJ1998:
Have done multiple times, have also tried installing Riru & EdXposed also multiple times, toggling them from Magisk Manager. Nothing just works...
[Xposed General] Hirs_E_Fruit:
Try the v0.4.5.5 Manger, did the trick for me
[Xposed General] Al765436:
I have magisk 20.4, riui 19.7 and 0461 sandhook and all's working well. flash and reboot each module separate..
[Xposed General] Hirs_E_Fruit:
We talk here about a canary version which passes safetynet while you just use an old working version ;)

I have the same bug as him but an older EdXposed manager works for me
[Xposed General] fishstik:
got it working on my xz1 compact (android 9) with:

magisk 20.4

riru 19.8

edxposed 0.4.6.3 sandhook (canary) with these settings in xposed manager:

☑ app list mode

☑ instant module list

☑ force hook modules

☑ pass safetynet
[Xposed General] DarkSJ1998:
Thanks for the help guys but now suddenly out of the blue, EdXposed started giving green tick mark [emoji81] I didn't even do anything. Really SafetyNet and EdXposed Manager have been playing a game of cat and mouse now.
[Xposed General] dr4go:
Beware of this enhanced mode: this causes my banking app to recognize, that my device is rooted.
[Xposed General] Soumy1234:
It's probably cause part of the enhanced mode is to trick apps into thinking Xposed Installer installed. Maybe there should be an option to disable this part. Did you Blacklist your banking app in Edxposed Manager?
[Xposed General] Johnn78:
In Edxposed manager has the options about SandHook & Yahfa to download but it exists in three different categories. The Alpha , the Canary and the Snapchat. Each category has different versions of SandHook & Yafha. From which category to select to download ? And what are the categories ?
[Xposed General] dr4go:
I thought exactly the same. Of course I did, otherwise it also doesn't work. And yes, I have obviously also hidden it in Magisk.

---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------

Oh forgot to mention as well... Check your root beer, which won't be green anymore with activated enhanced mode.
[Xposed General] Mikanoshi:
It has issues with EdXposed 0.5+, not Riru. Should work on 0.4.x.x, how to pass SN there is another question.
[Xposed General] purgy:
Passing SN on Riru 22.0, yahfa 0.5.0.6 (4569).

Had to clear out all the sandhook files with app cleaner function of SD maid, and used magisk hide props config to force basic attestation.

GravityBox (and all my other modules) working fine on this version.
[Xposed General] siealex:
Strange problems with EdXposed 0.5.1.3.

LG Nexus 5X, Android 8.1.0 (official), Magisk 21.1, Riru 23.1.

SANDHOOK:

1. The system is EXTREMELY slow. Startup takes up to 15 minutes, every application launch or other similar action - 10 seconds.

2. Some modules are broken completely (xToast) or partially (GravityBox).

No such issues with 0.4.6.4 on Riru 19.

YAHFA:

Boot animation, then black screen with backlight. No desktop, no SystemUI, but (sometimes) the power-off menu works.

Does anyone experience something like this?

The log file is on the Sandhook version, YAHFA does not connect to ADB at all.
[Xposed General] purgy:
Yeah, I managed to get Riru 23.1 working with sandhook v0.5.1.0 (4596), but my phone was painfully slow as you described, and half the features of GB didn't work, and xposed edge wasn't able to hide the navbar. probably a lot of other mods were broken too, but the slowdown was so painful I just gave up and rolled back.

Just sticking with Riru 22.0 and yahfa 0.5.06 (4569) for now, as all my mods work and it gets past SN.
[Xposed General] bush911:
Hi mate,

Could you please help confirm whether this faking location module "lataclysm" work with your current setup?

I am using Pixel 3 and on android 10. Google has informed me many many times to upgrade to Android 11.

But I am hesitating as this module is a must for me. I am using v0.4.6.2 YAHFA+Riru 21.3

I would be most grateful if you could help with this.

Best regards and stay safe