Skip to content

Conversation

@weebl2000
Copy link

Specifically, when auto-add is off and a new contact is discovered this currently triggers a write. That write has no effect, other than reducing flash life and causing more potential corruption.

@weebl2000 weebl2000 changed the base branch from main to dev January 10, 2026 15:54
Previously, on any new contact discovered we would try to write the
contacts again. If auto add isn't on, nothing has changed.

This can cause corruption by triggering more writes and also reduces
flash life.
@weebl2000 weebl2000 force-pushed the dont-save-autoadd-off branch from 1b7db1a to 8fc8bf9 Compare January 10, 2026 16:23
@oltaco
Copy link
Contributor

oltaco commented Jan 12, 2026

Nice work!

@ripplebiz
Copy link
Collaborator

@oltaco Do you know if this change still makes senses after your PR (now merged) ?

@oltaco
Copy link
Contributor

oltaco commented Jan 16, 2026

@oltaco Do you know if this change still makes senses after your PR (now merged) ?

The idea is still sound but the code will need to be tweaked. I have another PR which I will submit in the next hour that makes another small change to the onAdvertRecv() logic and I will add a change to that so that we only schedule the lazy write when the contacts file has actually changed 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants