-
Notifications
You must be signed in to change notification settings - Fork 43
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
Vi Tune error #671
Comments
I just came here to see if someone also encountered this error, and before I switched to vitune, I was using vimusic which also had this same error, maybe 🤔🧐 is a sign of this app not being continued |
Is there any other source which can give the same experience as vi music?
…On Sat, 28 Dec 2024, 13:05 Emmanuel Nwaohiri, ***@***.***> wrote:
I just came here to see if someone also encountered this error, and before
I switched to vitune, I was using vimusic which also had this same error,
maybe 🤔🧐 is a sign of this app not being continued
—
Reply to this email directly, view it on GitHub
<#671 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BMIFSQLUU6O3UXNVBC57MS32HZIFXAVCNFSM6AAAAABUJRVKCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGI2DOMZZGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
At least for me RiMusic suffers the same issue. BlackHole was one option, but it's not available anywhere right now. |
https://github.com/DanielSevillano/music-you Try this |
I'm having the exact same error like this. Is there a solution? |
Steps to reproduce the bug
Expected behavior
The music should start playing
Actual behavior
Error on each track showing the message :- "An unknown error has occured"
Screenshots/Screen recordings
Logs
No response
ViTune version
v1.1.1
What kind of build are you using?
Debug (self-built / unsigned from source)
Android version
Android 15
Device info
I am using Redmi 13 5G, using Android version 15
Upstream reproducibility
No response
Additional information
No response
Checklist
The text was updated successfully, but these errors were encountered: