yeah for sure! oh man, I was using subtracks for a bit as well, that was a great and i had even forked it and was trying to compile that codebase - in the end I went with tempo because it was further along in the dev process and my time is limited.
Sweet! The app has a lot of small, very annoying bugs. Still my fave, I just got tired of waiting for updates and did not want to see it go by the wayside.
Yup, no commits since Dec 2024, or much of any activity. I opened a discussion but never got a response. I did track him down, (i think its him) on linkedin to ask for repo rights when I first got started but then decided I was a little too stalking and didn’t want to invade his space, so figured I just fork it and keep going. My hope is that he is doing well and it looks like he started a small android app biz and it’s doing well.
Thanks, got a lot of community effort this time round. The album track list was something we introduced in the last release, 4.1.0, that caused albums to display multi disc tracks all goofy, screenshots -> https://github.com/eddyizm/tempus/issues/234
It was in effort to improve performance and deal with lag/large libraries. We will have to go back and figure it out.
I believe there is a ticket for what you are describing?
❤️
Feel free to make a PR to add this to the documentation, i am hoping to document more and could use the help -> https://eddyizm.github.io/tempus/USAGE.html
Glad to hear!
Depending on which version of Tempo you switched it, most things would be the same as I had forked it at 3.9 and started my releases at 3.10 I love listenbrainz! Playlists still need work. the only format I’ve seen consistent issues is wma (i know i have some old files I had to replace)
hi @flightyhobler@lemmy.world the degoogled version does not work with android auto - you need the github version with the google stuff
Hi Sips, The playlists don’t show up by default when you select that flag - (this is confusing i know) But you have to go to the playlist -select the option to ADD TO HOME, Then it will show up on your home if that part is enabled.
There are issues with playlists in general and inparticular with the home location, if you see the issues there are some open ones intend to get to soon but there is a playlist revamp that is needed so there is that.
It’s not out of the question, there are a lot of requests for android auto in the repo, I just can’t get to them yet with any confidence until I can test.
Some ideas are good, but I will use the safety rules as a hard guidance once I do get to it.
I did get to use auto while on holiday and it was sweet. I can see wanting more control but also feel too much can be a bit dangerous, might as well be looking at my phone while driving which is bad lol.
I need a dev environment to even see the changes I make actually make it there. There is a flag to enable the 5 star rating on the main screen, it’s off by default. Have you tried that? I am not sure if that transfers to auto (i don’t think it does)
As far as the safety thing, I have to read the docs -> I believe there are guidelines and if it fails them, they block the whole app. So I want to keep it simple until I understand the requirements.
✌️
I’m still working on setting up an android auto dev environment. It’s been a challenging however I’ve made progress so I may have it up soon.
That being said, I’ve been told I need to make sure I pass the safety test/guidance to get into the google play store.
Thanks, Not particularly. I’ve already have a bug where something broken between updates I’m tracking down but feel free to open a ticket if you find something that is not already a open issue.
return of the clippy, now named skynet.
Try it, I’d be curious to see what happens? The release before has a debug version if you want to grab the logs.
Fantastic! I just added the heart/like feature there as well and wasn’t sure if showed up on android auto.
Need to figure out how to get a test environment for that.
That’s an old version from last year. If you get the latest from github you should have android support, given the caveat that you have to make the adjustments for an unknown app (check out the docs)
The other thing that might hang you up is if you use graphene OS. The degoogled version lacks auto support.
Yeah, I’m not sure. I know a few people who run their servers behind a reverse proxy. I don’t think the app cares as long as the response is correct and endpoints exposed properly.
I know there is a PR for basic auth that I have not yet rolled in because I need to test it but perhaps you can test this out and let me know?
same here, i didn’t want to see it die!
Hi @non_burglar@lemmy.world 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.