My approach was just to use the pi hdmi output and run the native interface on the TV. Since there is no mouse, I run a script to read HDMI-CEC controls and convert to mouse movements. There are also other clients. If I’m watching TV on Android TV then I’m not using volumio and vice versa, so having a client on the TV side seems redundant
Bravo! And I’m glad you sharing your experience as it might be other ways to address this “conundrum”.
I do not consider myself an “Audiophile” per se, but trying to get the best sound quality possible (at a reasonable cost). That said, HDMI might not be the best output option for Audio (as in my case, RPi4 with Volumio and Allo Digione HAT).
Having a AndroidTV client is not redundant, but to have a HDMI-CEC script to convert to mouse movements might be of interest to others (if you don’t mind to share).
I dont use the hdmi output for audio, just video. My AVR lets me pair any HDMI video input with any audio input, so the HDMI video is paired with the analog from my USB DAC.
As for the CEC script, I just googled it and used one someone else wrote rather than reinventing the wheel. The only tough part is some of the dependencies. You’ll need to use a different repository from the volumio one to install the cec binary, then switch back the repository line for proper updates.
An AndroidTV client would be no different than running the Pi HDMI output into the TV. You might be able to sideload the official android client if you really want to go that route.