eddyizm

joined 2 weeks ago
[–] eddyizm@lemmy.world 2 points 10 hours ago (2 children)

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

[–] eddyizm@lemmy.world 1 points 10 hours ago

lol - that is a healthy size

[–] eddyizm@lemmy.world 1 points 10 hours ago

I have fixed a bunch of bugs/crashes but there are more as we peel back the layers as we also start to add new features.

[–] eddyizm@lemmy.world 1 points 10 hours ago

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)

[–] eddyizm@lemmy.world 1 points 10 hours ago

hi @flightyhobler@lemmy.world the degoogled version does not work with android auto - you need the github version with the google stuff

[–] eddyizm@lemmy.world 2 points 1 day ago (4 children)

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.

 

cross-posted from: https://lemmy.world/post/38014703

Hi All, my fork of Tempo has had a rebrand, which was a requirement to get back into the app stores as the original Tempo still exists in F-Droid/IzzyOnDroid

Tempus v4.0.7

Attention

This release will not update previous installs as it is considered a new app, no longer Tempo, new icon, new app id, and new app name. Hoping it will not be a huge inconvenience but was necessary in order to publish to app stores izzyDroid

Android Auto Support should be the same as before, however, I was not able to test any of the icons/visuals, so please let me know if there are any remnants of the tempo logo/icon as I believe I removed them all and replaced them successfully.

What's Changed

fix: Crash on share no expiration date or field returned from api
fix: Check also underlying transport 
feat: Unhide genre from album details view 
fix: persist album sorting on resume 
chore: Tempus rebrand 
chore: Update Polish translation 

Now available via the IzzyOnDroid Repository -> https://apt.izzysoft.de/fdroid/index/apk/com.eddyizm.degoogled.tempus

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.

In particular, any android dev is familiar android auto to help me set up a dev environment

[–] eddyizm@lemmy.world 1 points 1 day ago (2 children)

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.

[–] eddyizm@lemmy.world 2 points 1 day ago (4 children)

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.

[–] eddyizm@lemmy.world 2 points 1 day ago (6 children)

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.

 

Hi All, my fork of Tempo has had a rebrand, which was a requirement to get back into the app stores as the original Tempo still exists in F-Droid/IzzyOnDroid

Tempus v4.0.7

Attention

This release will not update previous installs as it is considered a new app, no longer Tempo, new icon, new app id, and new app name. Hoping it will not be a huge inconvenience but was necessary in order to publish to app stores izzyDroid

Android Auto Support should be the same as before, however, I was not able to test any of the icons/visuals, so please let me know if there are any remnants of the tempo logo/icon as I believe I removed them all and replaced them successfully.

What's Changed

fix: Crash on share no expiration date or field returned from api
fix: Check also underlying transport 
feat: Unhide genre from album details view 
fix: persist album sorting on resume 
chore: Tempus rebrand 
chore: Update Polish translation 

Now available via the IzzyOnDroid Repository -> https://apt.izzysoft.de/fdroid/index/apk/com.eddyizm.degoogled.tempus

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.

In particular, any android dev is familiar android auto to help me set up a dev environment

 

Hi All, I am not sure if this is post is ok here so please let me know if not. I did not see any other android community that was a decent size for development so figured there might be some devs in here.

I recently forked an FOSS project that has an android auto component to it. I don't have a physical device to test with in my car so I need to set up an emulator.

Challenge is, I am struggling to figure out how to do so, from what I can gather, it is either the same? or you can launch from a local device connected via usb and it launches to an emulator as if it was a head unit? I am clearly missing something and all the articles I've seen have not really gotten me over the finish line.

Any links or tips appreciated!

 

cross-posted from: https://lemmy.world/post/37454125

Hi All,

my first post over here on lemmy. Thought I'd share my forked tempo release.

Some new fixes for October. v3.17.14

What's Changed

fix: General build warning and playback issues 
fix: persist album sort preference 
Fix album parse empty date field 
fix: Include shuffle/repeat controls in f-droid build's media notific… 
fix: limits image size to prevent widget crash 

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

app-notquitemy* <- The f-droid release that goes without any of the google stuff.

Full Changelog: https://github.com/eddyizm/tempo/compare/v3.17.0...v3.17.14

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.

In particular, any android dev is familiar with changing the name/icon in order get this app published in app stores.

 

Hi All,

my first post over here on lemmy. Thought I'd share my forked tempo release.

Some new fixes for October. v3.17.14

What's Changed

fix: General build warning and playback issues 
fix: persist album sort preference 
Fix album parse empty date field 
fix: Include shuffle/repeat controls in f-droid build's media notific… 
fix: limits image size to prevent widget crash 

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

app-notquitemy* <- The f-droid release that goes without any of the google stuff.

Full Changelog: https://github.com/eddyizm/tempo/compare/v3.17.0...v3.17.14

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.

In particular, any android dev is familiar with changing the name/icon in order get this app published in app stores.

view more: next ›