Exposing Client Battery/Power Status (and Levels)

[zsp03]

As people use Artemis mostly for streaming with Apollo, it would make sense for the server to know the battery level of the client right? Few things that I have in mind:

1. Automated server action such as fps and bitrate change, preparing to do graceful exits, etc.
2. Persistent information (something like in a UI) both in the client and server.
3. Adjust client behaviour based on (1)

Right now you can do most of that in client since we are still running Android on top of Artemis. But, they are in a different ecosystem and it differs for each device especially in something like an Android TV. However with enough exposed client information, we could essentially make the server as just external power boost for the phone, not some "detached" devices. This is just one of them. Gamepad support is great enough that they send their battery information

Of course there will be many issues such as the nonexistent software support. Whoever is going to use it will need to specifically made an app to consume the exposed data as there is no way to replace the server battery function that is non-dangerous (and it should not be replaced). The other problem is where could this be implemented? And as what? Do we need Websocket, or just plain API, or a simple variable?

What do you guys think? Do you have other device information that would make sense to expose to the server?

[ClassicOldSong]

I don't quite understand what you want to achieve. Do you want to make automations based on client info? Or show client status with RTSS?

What parameters do you expect the server to adjust based on real time client info?

[zsp03]

When you're far away from the client, mostly it's a TV or a box that doesn't need to worry about battery life,

I get this.

while when the host itself has a battery, mostly you won't stream from it on battery

I use them for the battery specifically (traveling). Of course when there are power outlets it's ideal to put it on charge.

and most host side overlays already includes the battery stats on their OSD.

The host battery is not an issue, it's just things to look out for when both devices have batteries. If both devices have batteries, then how do we show them in a meaningful way without compromising?

There're apps that can display client status on the client itself if you wish to see more info about your client.

Back to the previous issue, you can't control the Android UI necessarily if you are streamed and in a fullscreen application which the gamepad is currently on focus. Most of the time you either swipe down constantly to check for battery, or have always shown notifications bar option.

If you are on handheld, they usually have extra buttons for macros or controlling the client (Android).

Not trying to debate here, just showing my view on this.

[ClassicOldSong]

I mean there are apps that can display an overlay on your screen, so you still can see the stats on your client while streaming

[zsp03]

I mean there are apps that can display an overlay on your screen, so you still can see the stats on your client while streaming

The app that people use for benchmarking? I did use them, but It's inconvenient sometimes as "Display on other Apps" could break things and could be dangerous. Double overlay with the host overlay will happen. Gamepad doesn't work with them either.

Do you have recommendation?

I feel like I'm putting too much on other apps (especially not open sourced). I might try to fiddle with a fork of this or a "companion" app of some sort to compare.

[ClassicOldSong]

Something like DevInfoOverlay?

[zsp03]

Thanks, it does work.

As previously mentioned it still blocks interaction, only way turn it off is also only through the app. I'll keep it as comparison.

[kayti]

Potentially, battery status of client could be usefull (something like windows pop up like when starting stream). I already had at least few times situation, where when playing on my laptop on battery, I completely drained it without noticing. It was especially bad when playing some ranking match in online game :D So, as far as I don't have any idea how efficiently use that kind of info, I wouldn't dismiss this idea completly.