One of my main annoyances with this integration has been with powering on my device. The default is for the device to send the power button followed by home if it is off.
|
await self._adb.shell(constants.CMD_SCREEN_ON + " || (input keyevent {0} && input keyevent {1})".format(constants.KEY_POWER, constants.KEY_HOME)) |
and
|
self._adb.shell(constants.CMD_SCREEN_ON + " || (input keyevent {0} && input keyevent {1})".format(constants.KEY_POWER, constants.KEY_HOME)) |
this effectively breaks the television turning on the last input if it is configured to do so.
While this can easily be fixed by adding:
turn_on_command: "input keyevent 26"
to the configuration, in order to override the default... I was curious if it might be feasible to make the default functionality follow what the television settings are set to. This can be determined by:
adb shell settings get secure power_on_launch_mode
where
0 = home
1 = last input
I'm not really sure if there's anything being stored in this implementation that would determine that dynamically though.
thanks in advance.
One of my main annoyances with this integration has been with powering on my device. The default is for the device to send the power button followed by home if it is off.
python-androidtv/androidtv/firetv/firetv_async.py
Line 177 in a2a0f33
python-androidtv/androidtv/firetv/firetv_sync.py
Line 177 in a2a0f33
While this can easily be fixed by adding:
turn_on_command: "input keyevent 26"to the configuration, in order to override the default... I was curious if it might be feasible to make the default functionality follow what the television settings are set to. This can be determined by:
adb shell settings get secure power_on_launch_modewhere
0 = home
1 = last input
I'm not really sure if there's anything being stored in this implementation that would determine that dynamically though.
thanks in advance.