mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-09-14 15:16:40 +00:00
docs(release-notes): add contacts-flush fix, Sats field, popup marquee fix
Three v1.27 changes this cycle weren't reflected yet: the low-battery/ reboot contacts-persistence fix (matching the settings one already documented), the Clock page's new Sats field, and the Path/Relayed by popup's marquee glitch + slowness fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -12,12 +12,15 @@
|
||||
- **A brand-new (or factory-reset) device now shows every Home page by default**, instead of a curated 5-page carousel (Clock, Tools, Shutdown, Favourites, Map) that made the rest opt-in only. Existing devices' own saved Home Pages selection is untouched.
|
||||
- **Repeater builds now default to a 6-minute local advert interval** (was 2 minutes) — quieter out of the box for a unit sitting on a desk or freshly deployed. Change it anytime under Settings › Radio.
|
||||
- **The lock screen now shows a title bar** (status icons and battery, node name deliberately left off so a locked device doesn't announce whose it is) and its clock is left-aligned instead of centred. Contributed by @3urobeat.
|
||||
- **The Clock page's data fields gain a `Sats` option** — GPS satellite count, or `--` without a fix.
|
||||
|
||||
### Fixes
|
||||
|
||||
- **Changing a setting and then rebooting or powering off without first backing out of that screen could silently lose the change** — most commonly hit via the low-battery auto-shutdown, which can fire mid-edit regardless of which screen is open. Every settings screen already saved correctly on its own Back/Cancel path, but the actual reboot/power-off code itself never flushed anything on its own. It now does, unconditionally, on every real shutdown/reboot path (including the phone app's and the serial CLI's reboot commands) — a deliberate factory reset is the one reboot that still wipes settings, as intended.
|
||||
- **A low-battery auto-shutdown (or long-press power-off) could lose recently learned contacts** — new contacts, path updates, favourites — leaving only Public channels behind after the device came back up. Contact writes are deliberately debounced to spare the flash, and under regular mesh traffic that debounce timer can stay pending for the device's whole uptime; the low-battery/power-off path never flushed it before shutting down. Every shutdown, power-off and reboot path (device menu, phone app, serial CLI) now flushes it first, the same as the settings fix above.
|
||||
- **A device with its own working clock (a board with a real RTC, or the browser demo) could have its time dragged backwards on boot** by a contact's older saved timestamp, instead of that timestamp only ever being used as a floor when the clock had no better source. Fixed so an already-correct clock is never rolled back.
|
||||
- **Diagnostics › Live always showed "N/A" for Heap free / Stack free on ESP32 boards** (Heltec V3/V4 and others) — those stats only had an implementation for nRF52. Now reported correctly on ESP32 too.
|
||||
- **Hovering a "Path" / "Relayed by" repeater name too long to fit could look stuck — a letter or two in, then crawling, before snapping back to the start.** Its marquee shared the same single animation slot as the row underneath it (by design, only one thing animates at a time) but both could end up drawing "selected" in the same frame, each resetting the other's state every redraw. The popup's own faster redraw request was also being silently discarded by its callers, capping the actual redraw rate far below what the animation needed. Both fixed.
|
||||
|
||||
- **Remote Bot's channel auto-replies showed up in the device's own history as if someone else had sent them, labelled with the device's own name.** The reply was stored with the device's node name as the sender prefix instead of the `"Me: "` convention the history view uses to tell an outgoing post apart from an incoming one, so the bubble rendered left-anchored like an incoming message. Now framed the same way an on-device or app-originated channel post is.
|
||||
- **A room server could end up pinned to the Favourites Dial and then never be removed.** The pin picker's "recent conversations" tier didn't filter by contact type, and room posts share the DM history, so a room could appear there; opening it from the dial then skipped the login handshake, and Unpin only existed in the chat contact list, which rooms never appear in. Rooms are now pinned deliberately (and open correctly), and any tile can be unpinned from the dial itself.
|
||||
|
||||
Reference in New Issue
Block a user