[FR] support more players

[ildar]

namely Odyssey.
If the app/widget is going to develop it's worth thinking on support more players, starting with those available at F-Droid.

[yourealwaysbe]

Thanks for the suggestion. In theory supporting Odyssey is straightforward, once the intents it uses are identified. These can then be added through the current interface as a "custom" player, though this is not user-friendly. If you know the intents i can hardcode them as an option. Otherwise i will investigate when i have some free time, which may not be soon.

[quantenzitrone]

Any updates? I tried to do stuff, but I don't understand what all the fields mean...

https://github.com/gateship-one/odyssey/blob/677872964ace4c5eb005ea7c062b3495fff1f582/app/src/main/java/org/gateshipone/odyssey/playbackservice/PlaybackService.java#L125-L133

These lines seem to be some of the needed actions, but i don't understand what command and command field label are...

[yourealwaysbe]

Sorry, i'm not really maintaining this anymore.

TeaCup is only really generic if it uses a similar format to the standard Android and LineageOs players. E.g. to jump to the next track, the LineageOs player broadcasts an intent with "url com.cyanogenmod.eleven.musicservicecommand", and extra info in a field called "command" with value "next". Similarly for the previous track, except the value is "previous". The stock Android player uses the same style, but with a different URL.

Odyssey does things a bit differently. For the next track it just sends an intent with URL "com.gateshipone.odyssey.next" and no extra info. It wouldn't be too difficult to add this flexibility to TeaCup. I think i experimented with something along those lines when i looked at it in 2017.

However, the kicker was keeping the TeaCup widget up to date with which track was playing. Android/LineageOs broadcast an intent with the information straightforwardly added as fields (i think just some kind of id that can be looked up some other way). Odyssey, however, parcels its own internal object into the intent. So TeaCup would need to borrow the code for Odyssey so it can unparcel the current state intent. This is more fragile than just reading a string or whatever from an "id" field. I think i had some intention to try that out, but it fell off the end of my todo list.

[ildar]

1st I personally think that the TeaCup widget will be demanded quite regularly. That's because new music players appear every few month or even more often. And firstly they appear without any widgets. This is where a universal widget (I mean TeaCup) comes in its glory :-)

[ildar]

Also is anybody aware if it's possible to use Media Button intents to control a player? That would remove most of the pain when adding a new player support.