-
Notifications
You must be signed in to change notification settings - Fork 151
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
RadioDroid can't connect to stations #1199
Comments
When I open the app, there's a "spinner" next to "Stations". That spinner now sometimes spins for 10+ minutes, and until it stops spinning, the app won't connect to any stations. That spinner indicates to me that something is happening, and whatever it is, it's preventing the app from opening any stations. |
Update: A contributing factor seems to be upstream DNS service. On a connection with good DNS service, I'm not having this problem. On a connection with poor DNS service, this problem persists. I tried this with multiple stations, and they all had the same issue (on the not-so-good connection). Is there some kind of connection the app makes before connecting to the selected station? Possible fix: Can the app cache the IP address of selected stations, and try that cached address before doing a DNS lookup? |
Not sure if same problem, but: running RadioDroid 0.82 on KitKat 4.4.2 -- a couple weeks ago suddenly can only get "Could not connect to station" message on any selection. Same 0.82 release works correctly on Android 9 phone, also on Android 13 tablet. None are rooted. Anxious to get working again on KitKat phone which I use most (night listening). Any help greatly appreciated! |
Recently updated RadioDroid on two devices, both via F-Droid.
Prior to update: Playing a station took a few seconds to connect and buffer.
Since the update: Playing a station often takes 10+ minutes to connect and buffer.
Problem seems to only happen during the first connection after opening the RadioDroid. When switching stations, or opening RadioDroid from a background state, it's fine.
The text was updated successfully, but these errors were encountered: