Momo "ART parameters are abnormal" from Lsposed 1.9.2

[bengalih]

• Pixel 3 XL running stock A11 ROM.
• TJW Magisk 26.4 Zygisk enabled
• LSposed 1.9.2
• Momo - 4.3.1 and 4.4.1

In short, Momo 4.4.1 will report the following detail warning as soon as Lsposed is installed and the device rebooted:

"ART parameters are abnormal"

Removing Lsposed does not stop this warning from showing.
In fact, even removing root (by reflashing the boot.img file) does not rid the device of this warning.

I can find nothing short of a full factory reset that removes it.

Can someone explain what LSposed is doing that triggers this modification and why even removing it does not revert.

This is referenced here:
https://github.com/orgs/LSPosed/discussions/2090

But claimed fixed in 1.9.0, which it clearly does not appear to be (or there was a regression).

[Howard20181]

For Android 10 and above, always keep SELinux enforced should fix it
For Android 9 and below there are no fixes that can be applied

[bengalih]

The installation of LSposed introduces the error, and the removal of it does not remove the error.
This can be recreated at will.

Only the LSposed team can provide information as to what exactly Momo is complaining about with the ART error.

The correct way to resolve this is to disclose what Momo is checking in order to generate this error.

Then, these appropriate settings can be validated before and after LSposed install and removal.

I don't see what AOSP has to do with any of it.

[bengalih]

Thank you for your reply.
So you confirm that an ART parameter is being modified because of the LSposed install?
If the removal of LSPosed does not revert this parameter, can it be done manually?

Can you disclose what parameter is being modified so that it can be manually checked.

I think the general understanding is that if the LSposed module is removed, any changes made by the module itself are also removed.
It sounds like you are saying that is not the case and blaming it on the OS/ROM when this can not be done?

I just would like clarification here because if simply installing LSposed can issue destructive changes that are not reverted on a removal of the module, then the user community should be aware.

[bengalih]

So I want to give you one additional piece of information.
I think that it is possible that LSposed is not the guilty party here, but Momo.
My understanding is your team also supports Momo, so I will continue to post here.
If this is not the case, please let me know.

The problem is very strange, and I do not exactly know how to explain it other than to explain the process.
Again, I am doing this on a stock A11 Pixel 3XL ROM after a fresh factory flash.
The only other thing that was installed was Magisk 26.4 (no modules apart from LSposed and Shamiko).

The process is this after installing Momo 4.4.1

1. Momo does not report an ART error
2. After installing Lsposed and Shamiko, Momo still does NOT report the ART error
3. Do an extra reboot to confirm no error
4. Uninstall Momo and reboot
5. Reinstall Momo and ART error is reported!! (NB: that the behavior is the same even without a reboot)
6. Remove Lsposed, Shamiko and reboot
7. Momo still reports ART error!
8. Clear Momo cache and reboot again
9. Momo still reports ART error!
10. Remove Momo and reinstall
11. Momo does NOT report ART error
12. Reinstall LSposed (and Shamiko) and reboot
13. Momo does NOT report ART error

I cannot explain this behavior. Clearly LSPosed being installed influences Momo's behavior, but following these steps it is possible to create the ART error or remove it based more on when and how Momo is installed.

I cannot continue to do this testing from clean device since I need to finish configuring my phone.

I hope that this information is useful to you since there is clearly a very strange condition with the Momo's app interoperation that I hope you can resolve.

Thank you for your attention to the matter.

[bengalih]

After some more tests, in addition to the above, I think the results with Momo can be more succinctly stated with the following:

1. If Momo is installed PRIOR to LSposed being active, it will NOT report the ART error.
2. However, if you install Momo AFTER LSposed, it will display the ART error (this includes a reinstall or upgrade of Momo).*
3. If the error is generated by # 2, it will not go away even after LSposed is removed.
4. The only way to remove the error is to disable LSposed, uninstall Momo, reboot, and install Momo prior to reactivating LSposed.

* This also includes removing the app and reinstalling with a Swift backup (which technically should be restoring all data).

So, once again this would show that the issue is with Momo.
While LSposed is the cause of Momo misbehaving, it is Momo which is providing inconsistent results.

Thank you.

[heximing]

I have the same issue with @bengalih and the above information is very helpful. At least I understand now the issue is Momo.

However, it is interesting that Momo knows LSPosed existed when we install Momo (Momo knows LSPosed existed to trigger ART error; otherwise, Momo will not trigger ART error, i.e. somehow Momo knows LSPosed existed even if I use Dr-TSNG/Hide-My-Applist).

I use Pixel 6 with the official Android 13.0.0 (TQ3A.230901.001, Sep 2023), LSposed 1.9.2 (7024), Magisk 26.4 (26400), Shamiko 0.7.4 (188), Momo 4.4.1.

One thing I do not understand is, why my LSposed says Dex Optimizer Wrapper Unsupported (SELinux is permissive)? How to make it enforced? Never mind. rebooting the phone will make Dex Optimizer Wrapper Supported.