Excellent app and integration! Many of the devices me might have always-powered on for home automation purposes are quite low end and sometimes struggle with subpar touchscreen performance. In my case, a handful of NSPanel PROs.
However, changing the CPU governor from 'interactive' to 'performance' greatly improves the performance and thus perceived speed for many of these older tablets. And in AC-Powered devices, we have no power consumption constraints.
su 0
for gov in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do echo performance > $gov; done
This can easily be performed with an adb command. However, getting both termux:boot to run with root or other installing methods require interacting the device (very annoying when there are many tablets installed directly on walls!), and are yet another component to mess with. The most beautiful thing about the ViewAssist companion app is that you don't need to interact with the device for it to be configured! Multi-device deploys become a breeze.
I suppose the VACA app could run commands Process process = Runtime.getRuntime().exec(cmd); on boot.
Another useful command is setting the ntp server to a local address:
settings put global ntp_server <new-ntp-server>
Which could be run on startup to sync to your local time server, since these older devices should always be on an airgapped network without internet access, and if the time clock is incorrect from the factory, drifts too much or gets lost with a power outage, they won't be able to login to HA (yes, it has happened to me).
Would it make sense for VACA to support running commands on boot, or setting the governor?
Excellent app and integration! Many of the devices me might have always-powered on for home automation purposes are quite low end and sometimes struggle with subpar touchscreen performance. In my case, a handful of NSPanel PROs.
However, changing the CPU governor from 'interactive' to 'performance' greatly improves the performance and thus perceived speed for many of these older tablets. And in AC-Powered devices, we have no power consumption constraints.
This can easily be performed with an adb command. However, getting both termux:boot to run with root or other installing methods require interacting the device (very annoying when there are many tablets installed directly on walls!), and are yet another component to mess with. The most beautiful thing about the ViewAssist companion app is that you don't need to interact with the device for it to be configured! Multi-device deploys become a breeze.
I suppose the VACA app could run commands
Process process = Runtime.getRuntime().exec(cmd);on boot.Another useful command is setting the ntp server to a local address:
Which could be run on startup to sync to your local time server, since these older devices should always be on an airgapped network without internet access, and if the time clock is incorrect from the factory, drifts too much or gets lost with a power outage, they won't be able to login to HA (yes, it has happened to me).
Would it make sense for VACA to support running commands on boot, or setting the governor?