v0.4.1

Bug Fixes

Relay Node Tracking

• Missing relay nodes fixed: Relay observations were silently dropped when packets arrived before the DB finished loading candidates. Now creates placeholder entries for unknown relay bytes so no data is lost.
• Signal filter fallback: When all viable candidates were filtered out by RSSI signal matching, relay observations were discarded. Now falls back to any non-CLIENT_MUTE candidate.
• CLIENT_MUTE no longer hides relay rows: A CLIENT_MUTE node with high direct-packet score could become the "best" candidate for a relay byte, causing the entire row to be filtered out — even when a valid ROUTER candidate existed. Best candidate selection now excludes CLIENT_MUTE nodes.
• Detail dialog star fix: The winner star in the candidate detail dialog no longer goes to CLIENT_MUTE nodes. Non-muted candidates are sorted first, and the star is only awarded to the top non-muted candidate.

DB Role Parsing (from v0.4.0)

• Fixed protobuf enum name mismatch: TAK not ATAK, TAK_TRACKER not ATAK_TRACKER
• Added ROUTER_LATE and CLIENT_BASE roles
• CLIENT role (0) now stored so nodes show "Client" instead of "Unknown"

Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's New

Relay Nodes Tab

• New Relay tab (tab 7) showing nodes observed relaying traffic, ranked by relay count
• One row per relay byte with best-scoring candidate as the displayed identity
• Tap any row for a candidate detail dialog showing all candidates with scores, roles, hop distance, RSSI/SNR, and recency
• CLIENT_MUTE nodes excluded — nodes with role=1 can't relay and are filtered out
• Legacy relay footer — shows packet count (and RSSI/SNR when available) for relayed packets from older firmware without the relay_node field

Search / Filter Bar

• Compact search bar on all tabs except Summary, between the tab row and content
• Automatically clears when switching tabs
• Case-insensitive substring matching on relevant fields per tab:
  • Msgs: sender, recipient, message text, gateway
  • Gates: short name, long name, gateway ID, last-byte hex
  • Nodes: config key, short name, hex node ID
  • Pkts: sender, packet type, gateway, relay hex byte
  • TR: from/to names, route node names, gateway
  • Relay: node short name, relay byte hex

Bug Fixes

• Notification persistence: notifiedPacketIds saved to SharedPreferences — no more notification flood after app kill/restart
• DB role parsing fixed: now uses official Meshtastic protobuf enum names (TAK not ATAK, TAK_TRACKER not ATAK_TRACKER); added ROUTER_LATE and CLIENT_BASE roles
• CLIENT role (0) now stored: nodes with default CLIENT role show "Client" instead of "Unknown" in relay detail dialog
• Node role tracking: roles populated from both NODEINFO packets over MQTT and PostgreSQL role column at startup

Full Changelog: v0.3.0...v0.4.0

v0.3.0

What's new

Traceroutes tab (TR)

• New TR tab decodes TRACEROUTE_APP (portnum 70) packets and displays the full RF path through the mesh
• Each card shows the forward path with per-hop SNR values and, when available, the return path
• Multiple gateway observations of the same traceroute are grouped into a single card, with each gateway's RSSI/SNR listed in the footer
• Round-trip traceroutes are indicated with a ↔ badge

Bug fixes

• Settings back gesture — swiping back from the Settings screen now closes settings instead of exiting the app
• Notification blast on startup — messages received while the app was offline no longer fire a burst of notifications when the app reconnects; only genuinely new messages trigger alerts

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Full Changelog: v0.1.1...v0.2.0

v0.1.1

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: v0.0.1...v0.1.0

v0.0.1

Full Changelog: https://github.com/dblaber/meshtop-android/commits/v0.0.1