Tracking issue for DS on Driver Hub

[qwertychouskie]

I keep forgetting and re-remembering various issues and TODOs, so I'm making a list here to better keep track. (This is a mix of DS issues specific to dhub usage, and issues with the new OS itself, in no particular order.)

• Add tab/menu/such to control Wi-Fi configuration
  • Consider Bluetooth as well; might be nice to save the USB ports some wear/damage when around the lab, and avoids annoying wires as well
• Fix "About" button crashing the DS (tries to open dialog, which is not a thing with embedded)
• Fix dhub battery monitoring (/sys/class/power_supply/ is currently empty; probably the devicetree not being correct; may or may not also be DS issues)
• Make power button shutdown dhub when held for a second or so (rn you have to hold for like 10 seconds to hard-power-off)
• Investigate whether sleep is possible (may not be possible on mainline Linux), implement some sort of pseudo-sleep if not (e.g. turn screen off, force CPU/GPU to lowest clocks, etc)
• Imement some sort of auto-shutdown when idle for long enough (e.g. if not connected to robot, and idle for 1 hour, shut down)
• Fix some missing icons on the on-screen keyboard (probably need to include a font with these icons)
• Replace Exit button with something a bit more fitting (e.g. shut down)
• Add some sort of first-boot wizard; at a minimum, country needs to be set for Wi-Fi purposes (currently this is hard-coded to US in the relevant network config file)
• Expand rootfs/fix GPT table on first boot
• Further work on general performance issues (e.g. try the new stencil buffer option just merged into Avalonia)
• Try systemd for parallel init (might be able to save another second or so during bootup vs sequential loading)
• Fix/test sound
• Add volume control to DS app
• Experiment with/implement USB tethering for sharing the robot network to a computer
• Don't show setting for docked vs windowed on dhub (doesn't actually do anything)
• Figure out rythmic once-per-second or so CPU usage spikes when DS has been running a very long time
• Include DS config json in OS image with FTC-specific defaults, like match time settings (people probably aren't using a dhub for FRC, and if they are, they can trivially easily reset that to FRC defaults)
• Create and/or document a simple way to flash the new OS image (maybe just vibecode an extremely simple GUI around rkdeveloptool?)

As it stands right now, Wi-Fi config and making it sime to flash the new OS are probably the only things stopping an early alpha release of the new dhub OS for teams to test, but ideally I can knock out some of the low-hanging fruit of the OS issues in this list in the next few days as well.