Android TV sendevent not working on GoogleTV (CCwGTV) and input method slow.

[gnoric]

The problem

The sendevent method is not working on the CCwGTV since permission error is returned. The device cannot be rooted to circumvent this issue. Using the default input command is quite slow. This is a known issue and has been documented in quite a few forums. However, I'd like to make a recommendation for a solution:

SCRCPY has a working solution which is fast and supports unrooted devices. It would be great if that snappy functionality could also be implemented into HomeAssistant. It works on unrooted devices and nothing needs to be installed on the device. And it is open source, so it shouldn't be too much effort identifying and copying the relevant functionality.

https://github.com/Genymobile/scrcpy
Genymobile/scrcpy#2248

What version of Home Assistant Core has the issue?

2022.6.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Android TV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/androidtv/

Diagnostics information

No response

Example YAML snippet

# Send the "UP" command using `sendevent` (faster)
- service: androidtv.adb_command
  target:
    entity_id: media_player.fire_tv_living_room
  data:
    command: "sendevent /dev/input/event4 4 4 786979 && sendevent /dev/input/event4 1 172 1 && sendevent /dev/input/event4 0 0 0 && sendevent /dev/input/event4 4 4 786979 && sendevent /dev/input/event4 1 172 0 && sendevent /dev/input/event4 0 0 0"

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant]

androidtv documentation
androidtv source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @JeffLIrion, @ollo69, mind taking a look at this issue as it has been labeled with an integration (androidtv) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[gnoric]

@cdce8p Maybe you can also have a look, please?

[droans]

Looks like this comes down to SELinux policy. Android 10 added this policy to shell.te:

# b/30861057: Shell access to existing input devices is an abuse
# vector. The shell user can inject events that look like they
# originate from the touchscreen etc.
# Everyone should have already moved to UiAutomation#injectInputEvent
# if they are running instrumentation tests (i.e. CTS), Monkey for
# their stress tests, and the input command (adb shell input ...) for
# injecting swipes and things.
neverallow shell input_device:chr_file no_w_file_perms;

https://android.googlesource.com/platform/system/sepolicy/+/refs/heads/android-s-beta-4/public/shell.te#222

[that1guy]

Seems the new SELinux policy causes the user to receive: adb_response: sendevent: /dev/input/event3: Permission denied when following the instructions titled ANDROIDTV.LEARN_SENDEVENT (FOR FASTER ADB COMMANDS).

I'd recommend updating the documentation if there really is no solution to this problem.