Pike
cb6a9d38e6
refresh() previously opened + parsed each conversation's newest message file (load_message_metadata) on every list refresh, which dominated list-load time on SPI LittleFS. It now reads the per-conversation last-message preview + timestamp from the store's in-memory index (O(1), zero I/O) and falls back to load_message_metadata only when the index has no cached preview — the first refresh after a firmware upgrade or after a corrupt-tail drop — then writes the preview back through so the fallback happens at most once per conversation per firmware generation. The write-through is skipped when drops were queued (the drained deletes move the tail, so a preview written for the old tail would be stale for one refresh). Host benchmark (x86 + POSIX fs, 24 msgs/conv): the per-conversation store-load work drops from ~0.149ms (9 convs) / ~0.342ms (20 convs) to ~0.002ms / ~0.005ms, and the cold-boot path (store reconstructed from disk) matches the warm path because the preview now persists in the index. Bumps the microLXMF pin to c8d3156 (feat/conversation-preview-cache) in platformio.ini, the release audit, and the native reference test. Adds tests/microlxmf/bench_conversation_list_load.cpp (baseline vs index warm/cold) and the bench target in tests/microlxmf/CMakeLists.txt.
Pyxis
An LXMF and LXST client firmware for T-Deck, built on a highly modified fork of microReticulum
Very much WIP, don't expect stability :)
Features
Reticulum transport over:
- RNode-compatible LoRa
- AutoInterface (local wifi)
- TCP Client
- BLE Interface (barely working if at all)
Other features:
- GPS-synced time
- One really annoying beep when you get a new message (user toggle)
- View the announce stream
- Choose a propagation node (and sync with it) (fixed in v0.2.1)
- Set auto announce timer
- Light up keyboard (user toggle)
Will crash in about 5 minutes of normal use (sorry)I had 5d uptime on v0.2.0 with BLE disabled- Make LXST voice calls (codec2 only, quality sounds horrible coming out the other end in Columba, needs work)
Flashing
The easiest way to get Pyxis running is the web flasher, which downloads release firmware from this repository's releases and verifies each image's SHA-256 digest against the release metadata.
For esptool (or any other tool that writes raw flash), each release also publishes a merged binary (pyxis-<tag>-merged.bin) that contains the bootloader, partition table, OTA selector, and application at their fixed offsets. Provision a T-Deck Plus (8 MB flash) with:
esptool.py --chip esp32s3 erase_flash
esptool.py --chip esp32s3 write_flash 0x0 pyxis-<tag>-merged.bin
Merged binaries are for first install / provisioning. Flashing one overwrites every flash region, including NVS (settings, identity) and the LittleFS partition (messages, paths, maps). To update an existing device without losing data, flash firmware.bin to 0x10000 only, or use the Columba-compatible pyxis-<tag>.pyxis.zip update package.
Why "Pyxis"
Pyxis, latin for "compass," is a constellation in the southern sky depicting a mariner's compass. Small but essential, the compass ensures every message finds its destination - even when the path is uncertain.