Settings gains a Maintenance section: LED reset, macro/event clears, restart#24
Merged
Conversation
…restart Owner request plus the escape hatches the group-logging cycle showed we need: - Reset LED — stop playback and clear patterns immediately. The footer points at the real fix when the light returns after a disconnect: an on-board event is re-arming it. - Clear Macros — erases all on-boot macros, with the confirm warning that this includes the identity-broadcast macro (the app re-applies it automatically on the next connect via the existing gate). - Clear Events & Timers — removes ALL on-board bindings, the manual way out of a lingering recording-heartbeat disconnect event (the documented edge when a different phone collects a heartbeat-armed board and can't know the event ids). - Restart Board — new SDK MetaWearDevice.restart(): reboot WITHOUT erasing (logs and macros survive; volatile state — timers, events, a wedged NAND housekeeping pass — clears). Same intentional- disconnect suppression and MMS ResetAfterGC-no-op fallback as factoryReset, without the erase steps. The unwedge we kept wishing for during the GC saga, now one tap. All destructive actions confirm via centered alerts per the app convention; failures surface in a dedicated alert. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Owner request (items 1–2) plus the escape hatches the group-logging debugging cycle showed we genuinely need (items 3–4):
MetaWearDevice.restart(): reboot without erasing — logs and macros survive, volatile state (including a wedged NAND housekeeping pass) clears. Same intentional-disconnect handling as factory reset, minus the erase. The unwedge we kept wanting during the GC saga.Centered confirm alerts per app convention; failures surface in their own alert. Full app suite + 1058 SPM tests green.
🤖 Generated with Claude Code