playback position not remembered

Thanks a lot for reporting your experience with Funkwhale! 🐳 A member of the team will have a look at this ticket as soon as possible. Afterwards this ticket will follow our issue workflow. We would really appreciate if you could check back to answer questions. Enjoy!

/cc @funkwhale/steering-commitee

added StatusNeeds triage label

Original issue: https://github.com/apognu/otter/issues/110

added TypeBug label

Also being slightly annoyed by this, as it's a small issue but it's coming over and over again.

I don't see anyone else being annoyed. If this bugs you so much, feel free to provide a fix or fund a developer fixing this. Thank you!

Well, do you know how many people use the app daily?

I already give monthly to Funkwhale, and I know that the budget is tight, but also that a developer IS currently paid to work on Funkwhale. That may or may not cover the Android app, but considering Funkwhale community took over the app some time ago, I was hoping it would get more attention, if not to develop new features, at least to FIX issues.

I am no developer (or are you expecting people coming on Gitlab to be developers?), so I don't see how I'll be providing a fix.

I've been a supporter of this great project for a while (and I DID provide Ansible modifications long ago to broaden the installation types), and I don't really see where this kind of pushing back is coming from.

If you don't have the time or resources to fix issues on the Android App, say so, no need to pretend all is fine.

@popindavibe At first, I am sorry. I probably was too harsh and I didn't meant to blame you.

Its just a fact that users stating their annoyance is not helpful and eventually hurtful, so I am interested in keeping the discussions friendly. Its clear that I myself did not managed to do this, and I am sorry.

I already give monthly to Funkwhale

<3 Much love!

but also that a developer IS currently paid to work on Funkwhale

Thats not entirely correct. I will get paid from October, but my tasks are mostly managing the project. On the other hand we are currently finalizing another NLNet funding.

considering Funkwhale community took over the app some time ago, I was hoping it would get more attention, if not to develop new features, at least to FIX issues.

We all hoped this. In fact the app is still usable, which is a huge win from my perspective. Sadly there were some unforeseeable issues which diminished the attention. I can understand your frustration, I really do. I did not meant to play down the importance of the issue, but I somehow did by stating "I don't see anyone else being annoyed". However, I fear there wont be any movement in the close future.

To be a bit more constructive: If you know an Android Developer who is willing to look into this and fix the bug, we might be able to find an arrangement. Meanwhile we are aware of the issues with the Android App and we do have some idea about how to improve the situation in the future, but this is something we will announce after the new funding round is signed, stay tuned.

Again, sorry for my harsh words and thank you for all your contributions!

To be entirely precisely: My contract starts in October, but I will be available for Funkwhale starting next month (April) funded by payouts of the NLNet funding I got last year

Thank you for feedback, much appreciated.

I initially posted here because I saw that one previous issue with the Android App (token renewal) had been fixed some time after it became Funkwhale for Android. Seeing that this other issue was still in status 'Needs triage', I thought maybe confirming the issue and the small but real impact it has on UX would help raising more attention to it, even though I am aware that resources for the webapp are very thin.

I am confident in the future of the project though, and my post was not meant as a cry of despair or a pushover. Time is often a relative nothion in FOSS project and communities, and that's fine. We both agree that the app is functional as it is, and that's already a huge win.

We have a bot which assigns this status label to all issues in the Funkwhale group, but I don't think the Android App uses our triaging schema, so its not relevant here. But jeah, its confusing, I need to think about how to solve this

@popindavibe I tried to reproduce this on current develop, but failed. Would you mind testing the development version to verify its already fixed there?

Well I've been doing different tests yesterday (on current stable), and so far I can't find a 100% way to reproduce the issue, which itself is a bit different that what is described in the initial post I realize.

The issue I am often facing is not that it restart the play from the beginning, it's actually that it does not resume anything when I try from the Android shortcut (swiping down from the top of the screen).

However, yesterday I tried to:

shuffle on an album
pause
wait +3-10 minutes
resume

In some cases it worked fine, in others I got the issue.

I have to do more tests, comparing between resuming from the app, and from the shortcut.

When the issue happen, I'm usually attempting to resume from the Android shortcut/widget. As it fails, I then open the App, and instead of the queue it tells me me that the queue list is empty. Basically it lost the information on where it was and what to play next.

My apologies for not realizing it may be different issue altogether. I will do more tests and update here once I have a found a definite way to reproduce the issue.

@popindavibe I released 0.2.0 yesterday, it contains a bunch of fixes and improvements. Please start testing there.

Also, our development builds (available in our own FDroid-Repository at https://fdroid.funkwhale.audio/) now have error tracking, so if you want, you can test there. It will automatically report crash-reports to our self hosted error tracking. This makes it easier to actually fix bugs.

I did a bunch of tests, too. I tried to pause tracks, close the app, open again, start playback again. This works properly in the sense of this bug report. What doesn't work is starting the playback using a widget/bluetooth-device when the app is in background, but I'd consider this to be another error.

I therefore tend to close this report, we can create a new one for the background issues.

I'll install the development builds and will continue testing from there.

I concur, the problem is different from what was first reported in this issue, and seems to be more of a background / audio widget problem.

mentioned in merge request !300 (merged)

added StatusInput wanted label and removed StatusNeeds triage label

Ok, so I've been listening to Funkwhale all day on the dev app, and so far so good!

I haven't had to reset artist / album search even once today, even during bad network connections. I will continue testing in the days to come, will report again in a week or so.

Today again, it's been working flawlessly so far. Even with long pauses, disconnecting / reconnecting bluetooth, managing through widget... it's great 😃

Ah, I've finally found something that is not working: trying to access artist / album from the 'play' view (when I swipe up from the current played track).

This is a new bug to me, because I'm sure that it was working fine before. I'm on version 0.2.0

Trying to access artist / album from the vertical 3-button menu now just does nothing. No crash, and the reader continues playing, but nothing happens.

@popindavibe Thank you for all the testing. I am going to close this now since I think the original issue is solved.

Please feel free to open a new one for new issues. If you use the development version, we get free error tracking so it should be easy enough to track those issues down.

Sure, this can be closed 🖖

closed

playback position not remembered

Designs

Child items ...

Activity