Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Status bar always displays 4 notification icons + dot, unregarding of maximum number setting #853

Closed
gygabyte017 opened this issue Jun 16, 2024 · 3 comments

Comments

@gygabyte017
Copy link

gygabyte017 commented Jun 16, 2024

Describe the issue

Whatever value I put under "maximum number of notification icons, I always see maximum 4 icons + dot when there are more than 4 (see screenshot)

Steps to reproduce

Set any number N different from 4 or empty, and wait until there are more than N icons to see that status bar always displays 4 notification icons + dot unregarding of N.

Expected behavior

To see a maximum number of notification icons as determined by the corresponding setting

Your device setup (Please take some time to give correct information here)

  • Google Pixel 8

  • 14

  • AP2A.240605.024

  • 27.0

  • Logcat Reader, MiXplorer, Nova Launcher, Pixel Xpert, Shell, SSHelper, Swift Backup, Termux, zygisk-detach

  • Pixel Expert (canary-367), Play Integrity Fix (v15.9.9), YouTube ReVanced eXtended (v19.20.34), Zygisk - LSPosed (v1.9.3 mod 7244), zygisk-detach (v1.16.1)

  • v1.9.3 mod 7244

  • Only Pixel Xpert

Logs

Screenshot_20240616-182548
PixelXpert_Config.zip
LSPosed_2024-06-16T22_04_16.360559.zip

@EleoXDA
Copy link
Collaborator

EleoXDA commented Jun 16, 2024

You need to use LSposed_mod instead of standard one:
http://github.com/mywalkb/lsposed_mod

@EleoXDA EleoXDA closed this as completed Jun 16, 2024
@gygabyte017
Copy link
Author

Thank you very much, done that, updated issue description and also uploaded LSposed logs (the issue still applies!)

@EleoXDA
Copy link
Collaborator

EleoXDA commented Jun 16, 2024

I noticed that you are still on android 14. It could be that with newer canary versions Android 14 compatibility is broken. Try to move back to a version which this was working still. We will not be maintaining old versions on canary versions anymore.

@EleoXDA EleoXDA closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants