Files
pmaports-rtwo/device/testing/device-motorola-rtwo/rtwo-dashboard.service
T
snlavaiseandClaude Opus 5.5 98b3104e94 device-motorola-rtwo: package the dashboard and the 5 GHz WiFi workaround
Both lived only in the rootfs (/usr/local, /etc). Move them into the
device package:

- rtwo-dashboard: sway always runs with the system dashboard on the panel
  (DSI-1); the launcher follows the DP-1 HPD and opens a login console on
  the external monitor while one is connected. The console runs login as
  a session leader (setsid -c) and reopens the tty on every loop, since
  login's vhangup() otherwise leaves the loop with dead fds. Files go to
  /usr/libexec and /usr/share/rtwo-dashboard.
- rtwo-wifi-5ghz-scan: unsticks wpa_supplicant after boot (ath12k). The
  network now comes from NetworkManager (first WiFi connection) or from
  /etc/default/rtwo-wifi-5ghz-scan instead of a hardcoded SSID.

Both services are enabled through multi-user.target.wants, like
rtwo-panel-revive. New dependencies: sway, foot, seatd-launch, python3,
font-jetbrains-mono-nerd, font-noto-emoji, iw, networkmanager-cli.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DnHwDU5yL8L6qgPEN5CV5m
2026-09-26 20:36:18 -03:00

14 lines
342 B
Desktop File

[Unit]
Description=rtwo dashboard (sway: dashboard en el panel; consola en el monitor DP-1 si hay)
After=systemd-user-sessions.service getty@tty1.service plymouth-quit-wait.service
Wants=getty@tty1.service
[Service]
Type=simple
ExecStart=/usr/libexec/rtwo-dashboard-launcher
Restart=always
RestartSec=2
[Install]
WantedBy=multi-user.target