The412Banner 3aa0162055 Answer for NetworkManager, so the client's network page works ...

The Steam client builds Settings > Internet and its connection indicator on
NetworkManager and looks for one on the system bus as it starts. This runtime
had neither, so the page stopped with "StartScanningForNetworks is not a
function" under a header that showed no connection while downloads ran. A user
on an Odin 2 reported exactly that, and I told him it was cosmetic and unfixed -
wrongly: Max wrote the answer for WinNative (e7a224ae) and Bannerlator has
carried his port for days. This app was the only one without it.

The session now starts a small system bus and his stand-in, which reports one
connection that is up while Android has a route out and refuses what it cannot
do, since nothing here can scan for or join a network. Both the script and the
bus config come from the apk at every launch, so an installed runtime gets this
without a re-host; dbus-daemon and python-gi are already in r9.

Named bannerlator-netmanager rather than steamdeck-: CI copies
overlay/usr/local/bin/bannerlator-* by glob, so anything else would have been
built, committed and never packaged - the same shape as the proot artifact that
was produced and discarded on every run for a week.

Version 0.1.3, and the README gains a section for it.

2026-09-21 21:35:51 -04:00

..

desktop

Logs: one folder per session, a device report, and credentials scrubbed

2026-09-21 12:56:25 -04:00

overlay/usr/local/bin

Answer for NetworkManager, so the client's network page works

2026-09-21 21:35:51 -04:00

preload

Bring the runtime up to date with Bannerlator, and end a session the way proot can survive

2026-09-20 00:55:37 -04:00