mirror of
https://github.com/torlando-tech/pyxis.git
synced 2026-08-06 02:39:32 +00:00
torlando-agent[bot]andClaude Opus 4.8
f0a78f70e1
The offset was computed as unix_ms - millis() (32-bit) but ltime() adds it to a 64-bit (high32<<32|low32) counter. Once high32 != 0 (a millis() rollover, or an erratic screen-off/wake tripping ltime()'s roll-over check) OS::time() was wrong by high32*49.7 days -- surfacing as garbage "Nw ago" timestamps in the conversation list. Compute the offset from OS::ltime()-getTimeOffset() at both the GPS and NTP sync sites; add a diagnostic logging OS::time() after each sync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UWZuYkHBRqNb6BZHV8sTG5
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.