Hey everyone 馃憢
Linthra is getting closer to being available on Google Play, and I need a bit of help from the community to make it happen.
Before I can properly release it there, I need people to join the Google Play closed test, install Linthra, actually use it for a while, and tell me if something feels broken or weird.
You don't need to be a developer at all.
If you have an Android phone and you're willing to install Linthra and play around with it, you're already helping a lot.
What I need
I'm looking for at least 12 Android testers for 15 days, but honestly I'd really like to have more than the minimum.
The more different phones and Android versions we test, the better.
What I need from you is pretty simple:
- join the Google Play closed test;
- install Linthra from Google Play;
- stay enrolled during the testing period;
- use the app like you normally would use a music player;
- tell me when something doesn't work, looks wrong, feels confusing, or just annoys you.
You don't have to spend hours trying to break everything.
Even just using Linthra normally is useful.
How to join
Please do not post your Gmail address publicly in this issue.
I'll provide a Google Group for Linthra testers and the Google Play testing link here.
You'll basically need to:
- Join the Linthra testing group.
- Open the Google Play testing link with the same Google account.
- Click Become a tester.
- Install Linthra from Google Play.
- Use it normally.
- Stay enrolled for the full testing period.
That's it.
If Google Play refuses to let you join for some reason, just comment here and tell me what happened. Don't post your email address.
What should you test?
Whatever you actually use.
Seriously.
I don't want everyone running the exact same checklist just for the sake of it. I'd rather have people use Linthra normally and find the things I wouldn't necessarily think about myself.
But if you want ideas, here are some useful things to try.
Installing and updating Linthra
Please tell me if:
- installing from Google Play doesn't work;
- Linthra crashes on the first launch;
- an update breaks your settings;
- your library disappears after updating;
- something weird happens after uninstalling/reinstalling.
Local music
If you have music directly on your phone, please try it.
Especially:
- selecting a music folder;
- using All music on this device;
- granting or denying the Android music permission;
- rescanning your library;
- revoking the permission in Android settings;
- reopening Linthra after changing permissions;
- background playback.
If a permission disappears or a scan fails, Linthra should not just destroy your indexed music library. If you ever see something like that, I definitely want to know.
Jellyfin / Navidrome / self-hosted music
If you're already running something like Jellyfin or Navidrome at home, you're exactly the kind of tester I need too.
Please try things like:
- connecting your server;
- loading your library;
- browsing artists and albums;
- starting playback;
- background playback;
- closing and reopening Linthra;
- reconnecting after losing network access;
- switching between Wi-Fi and mobile data.
And please don't put passwords, tokens, private server URLs or anything sensitive inside a GitHub issue.
Playback
Try to use Linthra like a normal music player:
- play / pause;
- next / previous;
- seek;
- shuffle;
- repeat;
- lock your phone while music is playing;
- use the notification controls;
- use Bluetooth headphones or speakers;
- try car/media controls if you normally use them.
If something behaves differently from what you'd expect from a normal Android music player, tell me.
You don't only have to report bugs
This part is important.
If something technically works but you look at it and think:
"Why the hell is this button here?"
Tell me. 馃槄
If something is confusing, too hidden, ugly, annoying, slow, or just doesn't feel right, that's useful feedback too.
A lot of things are obvious to me because I've been working on Linthra for a long time.
They might not be obvious at all to someone installing it for the first time.
That's exactly what I want to find before the proper Google Play release.
How to report a bug
If you find an actual bug, please create a separate GitHub issue instead of putting every bug in this thread.
Something simple like this is perfect:
Phone:
Pixel 8 Pro / Galaxy S24 / etc.
Android version:
Android 15 / 16 / etc.
Linthra version:
You can find it in the app.
Music source:
Local / Jellyfin / Navidrome / etc.
What did you do?
What did you expect to happen?
What happened instead?
Can you reproduce it?
Always / Sometimes / Only happened once
Screenshots and screen recordings are absolutely welcome when they help.
Just please check that they don't contain private information before uploading them.
Why I'm doing this
Yeah, part of this is because Google Play requires testing before I can push Linthra further.
But I don't want to do a fake test where 12 people install the app, never open it again, and we call it done.
If we're going to do this, I want to actually use it to make the Android version better.
I'd like the version that eventually goes public on Google Play to be something I'm comfortable putting in front of normal users, not just people who already follow the project and know how to work around bugs.
Want to help?
Just leave a comment saying you're interested.
If you can, also tell me:
- your phone model;
- your Android version.
That's already enough for me to get an idea of what devices we'll be testing on.
And again, please don't post your Google/Gmail address publicly here.
Thanks to everyone who tests Linthra, reports issues, submits PRs, stars the project, or even just uses it.
We're slowly turning this thing into a pretty serious little music player. 鉂わ笍
Hey everyone 馃憢
Linthra is getting closer to being available on Google Play, and I need a bit of help from the community to make it happen.
Before I can properly release it there, I need people to join the Google Play closed test, install Linthra, actually use it for a while, and tell me if something feels broken or weird.
You don't need to be a developer at all.
If you have an Android phone and you're willing to install Linthra and play around with it, you're already helping a lot.
What I need
I'm looking for at least 12 Android testers for 15 days, but honestly I'd really like to have more than the minimum.
The more different phones and Android versions we test, the better.
What I need from you is pretty simple:
You don't have to spend hours trying to break everything.
Even just using Linthra normally is useful.
How to join
Please do not post your Gmail address publicly in this issue.
I'll provide a Google Group for Linthra testers and the Google Play testing link here.
You'll basically need to:
That's it.
If Google Play refuses to let you join for some reason, just comment here and tell me what happened. Don't post your email address.
What should you test?
Whatever you actually use.
Seriously.
I don't want everyone running the exact same checklist just for the sake of it. I'd rather have people use Linthra normally and find the things I wouldn't necessarily think about myself.
But if you want ideas, here are some useful things to try.
Installing and updating Linthra
Please tell me if:
Local music
If you have music directly on your phone, please try it.
Especially:
If a permission disappears or a scan fails, Linthra should not just destroy your indexed music library. If you ever see something like that, I definitely want to know.
Jellyfin / Navidrome / self-hosted music
If you're already running something like Jellyfin or Navidrome at home, you're exactly the kind of tester I need too.
Please try things like:
And please don't put passwords, tokens, private server URLs or anything sensitive inside a GitHub issue.
Playback
Try to use Linthra like a normal music player:
If something behaves differently from what you'd expect from a normal Android music player, tell me.
You don't only have to report bugs
This part is important.
If something technically works but you look at it and think:
Tell me. 馃槄
If something is confusing, too hidden, ugly, annoying, slow, or just doesn't feel right, that's useful feedback too.
A lot of things are obvious to me because I've been working on Linthra for a long time.
They might not be obvious at all to someone installing it for the first time.
That's exactly what I want to find before the proper Google Play release.
How to report a bug
If you find an actual bug, please create a separate GitHub issue instead of putting every bug in this thread.
Something simple like this is perfect:
Phone:
Pixel 8 Pro / Galaxy S24 / etc.
Android version:
Android 15 / 16 / etc.
Linthra version:
You can find it in the app.
Music source:
Local / Jellyfin / Navidrome / etc.
What did you do?
What did you expect to happen?
What happened instead?
Can you reproduce it?
Always / Sometimes / Only happened once
Screenshots and screen recordings are absolutely welcome when they help.
Just please check that they don't contain private information before uploading them.
Why I'm doing this
Yeah, part of this is because Google Play requires testing before I can push Linthra further.
But I don't want to do a fake test where 12 people install the app, never open it again, and we call it done.
If we're going to do this, I want to actually use it to make the Android version better.
I'd like the version that eventually goes public on Google Play to be something I'm comfortable putting in front of normal users, not just people who already follow the project and know how to work around bugs.
Want to help?
Just leave a comment saying you're interested.
If you can, also tell me:
That's already enough for me to get an idea of what devices we'll be testing on.
And again, please don't post your Google/Gmail address publicly here.
Thanks to everyone who tests Linthra, reports issues, submits PRs, stars the project, or even just uses it.
We're slowly turning this thing into a pretty serious little music player. 鉂わ笍