Watch
1
0
Fork
You've already forked SouveraineOS
0

blueline: consolidate wifi bring-up, adopt cellular/MMS path, task audit

wifi: bringup unit now carries the union ordering (slpi/adsp for TZ MSA,
rmtfs+tqftpserv for firmware serving — the 2026-07-20 boot proved the old
load unit's ordering incomplete) and supersedes blueline-wifi-load;
msa-release adopted into the repo (shutdown unload that keeps warm
reboots clean).

cellular: adopt blueline-clat service+script. clat script now pins a host
route to the Fido MMS proxy via the CLAT — with wifi up the wlan default
beat the clat default and MMS died off-carrier. mmsd config contract
documented (MMS_APN must match the bearer APN ltemobile.apn; shipped as
netsvcs which matches nothing).

tasks: retire 06 qtpim (no longer the contacts path), archive 10 (done),
index catches up on 11 (archived); 01 re-pointed at a contacts-store
decision.
This commit is contained in:
Fimeg 2026-07-20 22:21:15 -04:00
commit 7ec2479f83
12 changed files with 533 additions and 9 deletions

View file

@ -27,8 +27,18 @@ wake that races the lock can land input on an unlocked surface.
else calls `hyprctl dispatch dpms` — when hypridle still had a raw dpms
call after the toggle became authority, double-tap wake raced `on-resume`
and the touch controller calibrated against a half-ramped panel
(Pixel3Arch `73d0cd0`). Any new wake source (power button, dt2w, proximity
someday) goes through the toggle, or it will reintroduce the race.
(Pixel3Arch `73d0cd0`). Any new wake source (power button, dt2w, proximity)
goes through the toggle, or it will reintroduce the race.
Proximity landed 2026-07-20 (Pixel3Arch): `blueline-screen-toggle` itself
gates DT2W wake on `ProximityNear`, and a new `blueline-proximity-lock`
user service (same `monitor-sensor` watch pattern as `blueline-autorotate`)
blanks an already-on locked screen the moment proximity goes near, via
`blueline-screen-toggle off` — no second DPMS authority introduced. Gated
on `session state`'s `.locked` from the souveraine IPC; unlocked screens
are untouched. `iio-sensor-proxy` is now always-on rather than start/stop
on demand (the old wake-lockup hazard tied to it is confirmed gone — see
Pixel3Arch `PAF/slpi.md`).
## 3. The FTS touch controller has opinions