You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2021. It is now read-only.
I initially started using Radiant Player because it didn't have the bluetooth connection issues that Chrome has. For me, when I use my wireless headphones, Chrome + google play music seem to misbehave in ways I don't see anywhere else. Radiant Player solved that for me - it turned out that Safari never had the issues that Chrome has with Bluetooth. When I tested Radiant Player Electron, the issues came right back, so I would not want to use this but instead to continue using the old Radiant player.
Just FYI - Thanks for all the development work.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I initially started using Radiant Player because it didn't have the bluetooth connection issues that Chrome has. For me, when I use my wireless headphones, Chrome + google play music seem to misbehave in ways I don't see anywhere else. Radiant Player solved that for me - it turned out that Safari never had the issues that Chrome has with Bluetooth. When I tested Radiant Player Electron, the issues came right back, so I would not want to use this but instead to continue using the old Radiant player.
Just FYI - Thanks for all the development work.
The text was updated successfully, but these errors were encountered: