document installation on non Linux proper hardware #7
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
e.g Android with PineNote, relatively easy, then trickier due to the lack of screen (and virtual keyboard) e.g Ricoh Theta V (and still rely on Termux and scrcpy) to potential e.g Flipper to probably infeasible e.g Monocle or PineTime yet that should still be considered otherwise, relying on e.g BT via an existing peer.
Could provider a route, e.g
/localsatellites, for satellite devices that can't become peers proper, e.g BT devicesFor example with the monocle e.g https://twitter.com/utopiah/status/1651089075904868352
Consider
uinputtoo, see also past work via the Web https://twitter.com/utopiah/status/1534055718462099457 but requires a browser.Ricoh Theta V should have been the usual Android setup, like the PineNote
Unfortunately it seems impossible to get a keyboard on screen or even via BlueTooth. Consequently impossible to install and start sshd.
What is surprising is that sending keyevent via adb works but only for some, namely
input keyevent "KEYCODE_HOME"does work but nothing else. Not keycode 108 that should bring up the virtual keyboard not even 29 that should put in the letter 'a'. Also to consider is that seeing a virtual keyboard in any app, starting by Termux but also in the home screen, viascrcpyseems impossible.Tried run-as-termux.sh with a debuggable apk from Github but failed, maybe root required for file permissions. Also tried https://github.com/termux/termux-app/wiki/RUN_COMMAND-Intent as mentioned in https://github.com/termux/termux-app/issues/924 but requires https://github.com/termux/termux-tasker#allow-external-apps-property-optional which can't be setup headlessly.
See also
usbipas a way to share USB devices themselves.See also https://developers.home-assistant.io/docs/api/rest/ as example of integrating Zigbee hardware, IoT more generally.
see also https://nitter.net/utopiah/status/1746459313151848517 as a potential ZigBee example that itself could be relayed with Home Assistant as a Zigbee controller exposing its HTTP API.
See also
neteventcf https://twitter.com/utopiah/status/1565313431409934336Consider ESP32 via ESPHome
See also https://meshtastic.org
See also handeld (gaming) running Linux yet dedicated distribution, cf https://fabien.benetou.fr/Tools/Shell#handeld with own ways to distribute software, e.g. PortMaster, typically because the hardware is limited and with different architecture e.g ARMv8-A 64-bit SoCs from RockChip.
See https://gadgetbridge.org e.g. https://gadgetbridge.org/gadgets/wearables/yawell/ but without Web (e.g. WebSocket or EventSource) in current https://gadgetbridge.org/basics/integrations/
Might be possible to relay events, assuming they are Android Intent or equivalent, via Termux (see https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/1378 linking to https://github.com/termux/termux-app/wiki/RUN_COMMAND-Intent#Basic-Examples ), e.g. SSE or WebSocket Express server.
Provides
Commented on opened issue https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/1378#issuecomment-7523386
Consider build environment for such devices to enable quasi https://fabien.benetou.fr/Languages/OwnConcepts#ResponsiveProgramming via e.g. dockcross.