a screenshot can't show it obviously, but I got amused (my little music player) working on #android via #termux   

it required writing a custom audio backend using the oboe library, and there are a few hack here still, but it's a start.

actually... amused-web works too, so I have the control UI available too. this is starting to become an interesting option. I only need to discover if the android scheduler will let my audio thread working in the background.

even if it's running on termux the scheduler is nice with amused, so it actually manages to play in the background without lags.

oh, and now I've seen `termux-notification`. maybe this is really viable

oh yeah. once I realized that termux-notification needed Termux::API to be installed, even the notification works!

Ideally I should find a way to intercept the headsets buttons, but for now I'm already happy 

@op Interesting! Perhaps you knew already, but you can use the termux-elf-cleaner package to get rid of the "unsupported flags" warnings.
@tim I didn't know, thanks! I was wondering why every time I build something I have that warnings.