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

Pitch black theme mode not working on app startup #3568

Open
Randomguy369 opened this issue Sep 6, 2024 · 6 comments
Open

Pitch black theme mode not working on app startup #3568

Randomguy369 opened this issue Sep 6, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@Randomguy369
Copy link

Steps to reproduce the bug

Settings > UI > Theme Mode > Pitch Black

Expected behavior

While opening the app the pitch black theme mode should be there

Actual behavior

While opening the app pitch black theme mode isn't there , it applies only after playing a song

Screenshots/Screen recordings

Record_2024-09-06-16-26-38.mp4

Logs

No response

RiMusic version

0.6.50

Android version

Android 14

Additional information

No response

@Randomguy369 Randomguy369 added the bug Something isn't working label Sep 6, 2024
@twistios
Copy link

twistios commented Sep 6, 2024

"Pitch Black" does not exist. There is "Modern Black" and "Pure Black". I have tested with both of them and it works as expected.
Please provide more information, for example the actual theme and other appearance settings and your System theme.

@Randomguy369
Copy link
Author

Screenshot_2024-09-07-07-41-28-13_91b67804b5fb3353a77fb824d6bb0b50

As you can see here , the theme is dynamic and theme mode is pitch black

@twistios
Copy link

twistios commented Sep 7, 2024

Ah sorry, I read "theme". I was testing with "System" for theme mode.

@twistios
Copy link

twistios commented Sep 7, 2024

It looks like I can confirm your bug at least with these two specific settings from you.

Video example

Screen_Recording_20240907_095915_One.UI.Home.mp4

@Randomguy369
Copy link
Author

Hey! This bug is still there in the latest version

@twistios
Copy link

twistios commented Sep 14, 2024

The bug is still opened (it is not closed), neither marked with "fixed" nor has fast4x (the maintainer) answered yet. So neither fast4x has fixed it yet nor was there notable progress on this bug.
I currently do not have much time to look into it so you have to wait until it gets fixed someday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants