meshsat 0.12.0

meshsat 0.12.0: Home as MeshSat Android's, the welcome, People, About, a chat's own key

• Home is now MeshSat Android's:

  • Getting started: Android's steps, each with its check or empty ring, opening the page that finishes it; Hide puts it away for good.
  • Arrange Home (the arrows button): move a card up or down; the order is kept.
  • The cards, in the order you keep: SOS; Message queue (a bar per lane and the four counts, from the Bridge's delivery queue); Your position (the phone's own fix, with its accuracy, height, speed and heading); Satellite signal and passes (three hours back and ahead) and Mobile signal, last 6 hours; Satellite mailbox (asks before it bills a session, then says what it found); Recent messages (every transport, SMS included).
  • The lanes count what waits on each lane, the satellite lane names the next high pass, and the node's modem out of reach is said first. The old signal-to-noise chart, which Android never had, is gone.

• A welcome at the first start: what the app asks for, and why; the phone asks for its position only after Continue.

• The node banner says when Bluetooth is off (a tap switches it on), which link is down and since when (a tap opens Setup), and keeps quiet while an SOS or a test runs.

• People: your own node in the table as "(you)", Android's table, sorts and colours, how each node was heard (directly with its SNR, or through other nodes), and the empty texts only when nobody is known at all.

• About, in Android's sections. The Satellite page, in Android's words for the RockBLOCK on USB-C, with its own 9704 card and the mailbox's result.

• A chat's own key: the lock in a chat's header opens Android's key section (Show, Generate, Save, Copy, Paste, Remove). The key is kept by the Bridge; an SMS chat's key seals and opens that number's texts, as on Android. A sealed text carries the amber lock.

• Fixed: Home's Message queue card kept its last counts once the queue had emptied.

• Fixed: an SOS text, an alarm test and a cancellation to an emergency contact could go out sealed when Messaging's encryption was on (MESHSAT-1424). They now always go out as written.

• The Bridge underneath (MeshSat Bridge 0c884a00, MESHSAT-1423, MESHSAT-1425 and MESHSAT-1427): the mailbox check a person asks for and what it found; how many hops a packet took, when known; each modem's signal on its own; a chat's own SMS key; SMS that go out exactly as written. An independent review of both batches found three faults before release (a mailbox check that could empty a message a send had just loaded, a lost incoming message after a failed read, and SMS text clean-up skipped for "as written" texts); all three were fixed and tested first.

• Tested: 372 unit tests, among them Android's NodeLinkBannerTextTest and SkyGeometryTest. On the bench phone, the whole suite against the installed package, 183 cases: 159 against a scripted Bridge, 17 against a second, real Bridge, 7 live. Two of the cases against the real Bridge found a fault first: Home kept the last queue counts once the queue emptied, because the Bridge answers an empty queue with null. They passed after the fix, with Home's cases run again. Among them: every card, Getting started, Arrange Home across a restart, the mailbox's every outcome (no satellite session was opened), the welcome at the first start only, the banner's four states, People, About, the Satellite page, and a chat's key saved in and read back from a real Bridge.

  Not proven on the bench: the mailbox against a real satellite session (it bills), the mobile chart and a sealed SMS on the air (no SIM), and the node's own satellite modem over Bluetooth (0.13.0; the T-Beam with the RockBLOCK is out of range).

Install on a Mobian phone: wget https://github.com/meshsat/meshsat-linux/releases/download/v0.12.0/meshsat_0.12.0_arm64.deb && sudo apt install ./meshsat_0.12.0_arm64.deb (docs/INSTALL.md).