62
Tempus v4.2.4 android subsonic client release (github.com)
submitted 11 months ago by to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
 

To the mods: I'm releasing a few times a month so I'm trying to post every other release as to note spam the sub. Please advise on proper protocol.

A couple of nice features and some several fixes

Updates:

  • chore: Update russian strings.xml
  • fix: disallow duplicate songs in queue
  • fix:github release check
  • fix: Fixed crash when viewing share
  • chore: Update Polish translation
  • fix: add podcast/radio channel visible when empty podcasts/radio
  • fix: Equalizer fix in main build variant
  • fix: Images not filling holder
  • feat: Make artist and album clickable
  • feat: implement scroll to currently playing feature
  • fix: shuffling genres only queuing 25 songs

note app-tempo* <- The github release with all the android auto/chromecast features

app-degoogled* <- The izzyOnDroid release that goes without any of the google stuff.

As usual, any dev contributions appreciated as I am not actually a java/mobile dev, so my progress is significantly slower than those who do this on the daily.

Big thanks to all the folks who have been contributing. We have a new icon designed but I could use some help if anyone wants to do a PR to implement it.

all 24 comments

sorted by: hot top controversial new old
[–] 7 points 11 months ago (1 child)

Thank you for your work on this! I switched from Tempo to Tempus after seeing one of these updates a few weeks ago. It's great to this is being maintained!

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 3 points 11 months ago

    Sweet, yeah I loved tempo, just wasn't getting updates or making any progress so decided to stop waiting and fork it, eventually rebrand in order to get back into repos. Seems like a lot of people still use tempo and are filing bugs but no one is over there. I do go back over to post about a bug fix or let them know.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 11 points 11 months ago (10 children)

    Tempus is an open-source and lightweight music client for Subsonic, designed and built natively for Android.

  • permalink
  • fedilink
  • source
  • hideshow 10 child comments
    •
  • [–] 7 points 11 months ago* (9 children)

    Feels like this is the sort of important information OP should have included in their post.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 5 points 11 months ago (8 children)

    Release dumping is a real issue on Lemmy. It's quite annoying. But at least this info was readily available in the README.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 5 points 11 months ago (4 children)

    What is Subsonic ?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 11 months ago (3 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 11 months ago* (2 children)

    Close, In this context, it's this: https://subsonic.org/pages/api.jsp

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 11 months ago (1 child)

    Surely that's the same product being referenced by this project? The API is being used by this project, to interact with Subsonic, the media server. No?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 11 months ago

    Sorry, I bungled that by not adding context.

    You're right, subsonic server and its api are the source of all this. However, that api is completely open, which means there are many, many client and server applications that use it successfully.

    Navidrome is a good server one, tempus, and here are a ton more!

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 3 points 11 months ago (2 children)

    What you prefer to see? I don't want to be annoying, just share updates as it seems each time I post, new people discover the app for the first time or realize the original repo is no longer updating.

    I did not see any policy regarding release dumping but I do appreciate the fact that my post could have a lot more context. So thanks for that regardless.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 11 months ago* (1 child)

    You're not being annoying as a person ☺️🫂 I just mean that there's a lot of posting with like a link to the release page of a project in GitHub and the title just says "Software X version Y released" and no more info.

    Sometimes it can be really difficult to understand what the software is or why we should be interested in it, or even this release in particular.

    But I believe you at least posted what you found interesting about this release, in the description. 👍 That's great! I didn't mean you were the one release dumping, I just meant it's annoying when it does happen. 😁

    Take care!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 2 points 11 months ago (3 children)

    What are the differences between Tempus and Tempo?

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 6 points 11 months ago (2 children)

    @Courantdair @eddyizm Two vowels and a consonant![I kid, I kid. Tempo development has slowed or stopped and has a number of outstanding annoying bugs. Tempus is a fork with more active development happening.]

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 6 points 11 months ago (1 child)

    The last release from tempo was Dec 2024. The last commit was I'm Jan 2025 for a grade version bump.

    Started with a fork and merged outstanding prs and have been addressing as many bugs that I can as well as adding features.

    I loved tempo so I didn't want to let it die, it just needed to keep moving forward.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 2 points 11 months ago (1 child)

    Why is the Tempus logo green on the phone's homescreen but red in the application itself? Is this to differentiate the "degoogled version"?

    Btw, thanks for keeping Tempo alive !

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 4 points 11 months ago

    yup, the green is the icon in the izzyOnDroid repo (degoogled) and the red all the way through contains the google libraries. I kept the same convention that tempo was using before.

    We will be doing a icon redesign soon and may change it a up a bit.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 1 point 11 months ago (4 children)

    Glad this project is alive and well! For strange reasons, covers are not displayed in-app (replaced by a generic placeholder) but do appear in the android media related screens (media controls, lock screen, etc).

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 11 months ago (3 children)

    Open a ticket up and post a screenshot, that is indeed weird. What back end are you using and how do you tag your metadata? There are some settings regarding artwork and sizing along with mobile/wifi settings that could possibly affect it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 11 months ago (2 children)

    Looks like it was caused by the "size of streaming cache" which I had set to 0 under the assumption/hope it would mean "unlimited". Though I had to log out and back on for album art to effectively reappear.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 11 months ago (1 child)

    yeah that is confusing - I realized later that it is also what happens when you go into data saving mode, no artwork. That is why I suggested looking at the settings. Glad you figured it out. We will need to make the cache better and clearly. I, for one, want to cache everything and store everything locally, however, there is a performance aspect that is generally the challenge.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months ago

    Glad to hear that! That's an area of dsub which I appreciate: it's pretty clear what's cached offline and not, transitioning to offline is one tap away, and caching whole sub-trees of the library is easy and convenient. As a frequent flyer, I get that I might be an atypical user, but I rely on this very much.

  • permalink
  • fedilink
  • source
  • parent