[Xposed Framework Modules] Eleo:
Let me explain some of the reasons:

1) If your custom ROM is not supporting AOSPMods, i.e. :

- Officially only Pixel Experience ROMs and pixel stock firmware are supported - other may have compatibility issues depending on how much difference they have with respect to AOSP source code

Then you may have errors in lsposed logs. And since it is practically and theoretically impossible to support all the different custom ROMs, only the one that is similar to stock pixel firmware, i.e., Pixel Experience normal and plus editions are supported officially.

2) If you are using several modules that try to change same value, i.e. :

- If you are using project themer or similar app to change quick settings in addition to AOSPMods to change same part of UI, it is imminent that you will have errors. And these may or may not reveal themselves as apparent Force closes.

3) Not all errors are coming from AOSPMods, i.e.:

- Here is one of the links on how to read logs and understand the core of issues:

View logs with Logcat | Android Studio | Android Developers

Learn how to display system messages with the Logcat window in Android Studio.

developer.android.com

Which means if you see errors in logcat the best way of action is to get cleaned view - i.e. remove all other magisk and lsposed modules and check logs to see where you get issues. Some root apps like substratum and repainter should also get their root permission denied to be sure that there is no external action

================

All in all, the experience that I was writing to you was result of all the testing done in our test group and on two of my devices with pixel stock firmware and Pixel Experience Plus Edition. With only using AOSPMods me and out test group got 0 error logs, but when adding a UI editing modules like project themer app we started seeing incompatibility with AOSPMods. And this is because they both try to change same parts.

P.S. If you have errors even with only AOSPMods, it may not be only due to incompatible custom ROM, so in that case please create an issue in our GitHub page with following information:👇

Issues · siavash79/PixelXpert

mixed Xposed+Magisk module for customization of Google Pixel rom of Android 12+ - Issues · siavash79/PixelXpert

github.com

=====BUGREPORT=====

At the time being, only bug reports from Pixel stock ROM or pixel experience will be considered. Read this post till the end and only after that start execution!

Bug reports from other roms will only be considered if also reported from one of the stated ROMs

For bugreport, please collect the following information and put it into a new ISSUE that you will open in our GITHUB page:

- Your device manufacturer and model name

- Android version

- Security update date (if it's a custom ROM, then its name and date of release)

- Your magisk version

- List of your magisk modules and versions

- Your LSposed version

- List of your LSposed modules and versions

- LSposed logs (extracted from the app) if the issue is not reproducible

- Your issue (should also be title of the issue you create). Explain it in words and if also possible with screenshots

--------------------------------

Before taking LSposed logs, be sure to

- delete (not only disable!) all modules other than AOSPMods & LSposed in Magisk Manager

- disable (turn toggle off) all modules in LSposed other than AOSPMods

- Reboot

- Change language to English if you are using another language.

- Try to replicate the bug. If not successful, then it means some other module is causing the issue. If successful, then extract LSposed logs.

👆

This makes sure there are no stains of other magisk/lsposed modules.