v0.3.0

The screen

The modem's front panel is a colour one, and the gateway now uses it as its standby
screen: the firmware's own status icons along the top, the OCW logo in the middle, and
the websocket state, the data this session has used and the counters along the bottom.

The icons are read from the firmware's icon.xml at startup and drawn where the stock UI
draws them, so a modem that lays them out differently gets its own layout.

Both buttons do something:

• Menu hands the panel back to the stock UI, so its menu, SMS list, data pages and QR
  codes work the way they always did. The gateway takes the panel back 25 seconds after
  the last press.
• Power, while the screen is lit, asks whether to stop or start the gateway. That is
  how you stop and start it with no phone and no PC.

/screen.png serves a shot of the panel, drawn on request, and the status page shows it.
scripts/screenshot.sh saves one from anywhere that can reach the modem.

Start with OCW_SCREEN=0 to leave the stock screen alone.

Nothing is drawn while the panel is dark, readings are taken on a timer rather than per
frame, and a frame that would look like the one already up is skipped. With the screen
dark the whole gateway costs about 40 ms of CPU per minute.

Fixes

The answer to a ^ command was being dropped along with the radio's unsolicited chatter,
which all starts with ^ as well. A command's own reply tag now survives the filter,
which is what +CSQ, ^SYSINFOEX and ^DSFLOWQRY need for the signal, radio type and
data counters.

Install

scripts/install.sh

Built from 3bcff29, Go 1.24.4, ARMv7, static.

sha256  95ee61751b86269a4153e949012148b76c3aee3a5f7daf3556b446d7779c151e

v0.2.0

The binary in v0.1.0 was built from the first commit and is missing everything below.

Heartbeat

ocwgw can push a status line to a monitor on a timer, so something shouts when the
gateway goes quiet. Set a Heartbeat URL on the web page and point it at an Uptime Kuma
push monitor. Off unless you set one. See docs/heartbeat.md.

Fixes

A late +CMS ERROR is no longer blamed on the next AT command.

scripts/start-ocwgw.sh starts the gateway so it survives the adb session that launched
it. It ignores HUP, and keeps stdin off the pty so the session itself does not hang.

install.sh and the binary now write and look for the same autorun marker, so the two
install paths agree about whether autostart is set up. The status page also recognises
the marker older installs used, so it will not offer to add a second boot entry.

install.sh decides the autorun state on the host. This adbd predates shell_v2 and
returns 0 whatever the remote command did, so a remote failure used to be swallowed and
reported as success.

Install

scripts/install.sh

Built from a3e679f, Go 1.24.4, ARMv7, static.

sha256  cd577b93c45e3a4d20166fb7aa17d80e31addfc6de0b645e9433fef638fc9be6

v0.1.0

Prebuilt ARMv7 binary for rooted Huawei Balong MiFis, tested on the E5577s-321. Install with scripts/install.sh (see the README).