torlando-tech 41d2eb6e63 Track A.1: repoint microReticulum submodule at attermann upstream 0.3.0
Was: torlando-tech/microReticulum @ feat/t-deck @ ca355e5 (a torlando
fork with unrelated git history per pyxis_microReticulum_alignment_analysis).

Now: attermann/microReticulum @ tag 0.3.0 @ f8d91d1 (canonical upstream).

This commit is configuration-only — just the submodule pointer + URL.
Pyxis will not build yet because vanilla upstream doesn't ship the
fork's added subtrees (src/LXMF, src/BLE, src/Hardware/TDeck, src/UI,
src/Instrumentation, PSRAMAllocator/BytesPool/ObjectPool/FileStream/
FileSystem, Cryptography/{BZ2,Ratchet}, Utilities/Print,
SegmentAccumulator). Subsequent commits in this branch vendor those
into pyxis itself or carve them out into standalone libraries per
the alignment plan.
2026-05-04 18:00:45 -04:00
2026-02-07 11:49:21 -05:00
2026-03-04 14:12:36 -05:00

Pyxis logo

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)

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.

S
Description
No description provided
Readme GPL-3.0
234 MiB
Languages
C++ 47.9%
C 41.8%
Python 8.8%
mupad 1.4%
Shell 0.1%