It does work if you use the github version, not the degoogled version. There’s also a few things you need to do detailed here in order for a non appstore app to work.

Glad to hear! It seems like it has (and many other apps) have not had many updates recently.

You can create and edit playlists on Tempus (currently working on overhauling this aspect of the app) however it does not have that playlist builder style thing. It can take your created playqueue and save it to a playlist. I’ve used substreamer in the past but it does not seem , at least on android, to have been updated in over 2 years now.

Thanks mate!

no worries mate. I was going to mention the same thing about the android status. It is one of my milestones but as you have seen, the app needs work and I am slowly learning the code base as I go through sections at a time.

Just started working through the playlist milestone with this release, will spend some time here and Android Auto has a milestone where I am grouping all the tickets. I will get to it in the near future for sure. Proper Offline milestone might come before it though.

It’s something I’d like to add as part of the offline milestone, there’s a lot of stuff needing attention, currently working on some playlist stuff atm.

the github version has android auto/chromecast support. I don’t think it works with grapheneos - people use the degoogled version for that os and it doesn’t generally support the google libraries.

Lol damn it, I had caught that earlier and started to edit the post and forgot to hit save. Thanks for the nudge!

If you could open a ticket and detail the steps to recreate. I have not seen this before but perhaps it is server specific.

Just released a new version last Friday!

🙏

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.

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.

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.

feishin is really nice. I use my regular back end (LMS) when not using the app though. Not quite as pretty but very solid.

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.

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.

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.

btw - i realized that this feature was missing from the UI or broken? My back end implemented the podcast subsonic api but did not have a ui, so it still needed to be added from the app. https://github.com/eddyizm/tempus/releases/tag/v4.2.4 for the change

Hi @[email protected] yes it is active. Your backend has to support it and it is loaded from there.

My backend does not support it so I can’t walk you through it. Probably something we should add to the documentation.