[Bug]: Server operator/SMP server settings revert after any configuration change

Is there an existing issue for this?

• I have searched the existing issues

Platform

Android

OS version

GrapheneOS (latest)

App version

6.4.10

Current Behavior

When I disable preset server operators (SimpleX Chat, Flux) or toggle off "Use for new connections" on preset SMP servers, the changes do not persist. The settings revert to
their previous state after:

• Leaving the Network & servers settings screen and returning
• Restarting the app
• Updating the app to a new version

I run my own self-hosted SMP server on a private mesh network (Headscale/Tailscale) and want to use ONLY that server — no preset servers. But every time I configure this, the
preset operators/servers re-enable themselves. The same applies to toggling individual preset SMP servers off — they re-enable on next visit to settings.

This makes it impossible to reliably run a self-hosted-only SimpleX setup on mobile.

Expected Behavior

When I disable a preset server operator or toggle off "Use for new connections" for preset SMP servers, that setting should persist across:

• Navigation away from and back to the settings screen
• App restarts
• App updates

If I configure only my own SMP server, preset servers should stay disabled permanently until I explicitly re-enable them.

Steps To Reproduce

1. Open SimpleX Chat → Settings → Network & servers
2. Under "Server operators", disable "SimpleX Chat" and "Flux" (toggle off "Use for new connections")
3. Under "SMP servers", add your own self-hosted SMP server (e.g. on a private mesh)
4. Verify preset servers show as disabled
5. Navigate back to main chat screen
6. Return to Settings → Network & servers → Server operators
7. Observe: preset operators are re-enabled, preset SMP servers are back to active

Relevant log output

No error messages shown — settings silently revert without user feedback.

Start at Settings → Network & servers and trace how server-operator and SMP-server toggles are loaded and saved. Reproduce the issue on Android, then verify that disabled preset entries remain disabled after leaving and reopening the screen, restarting the app, and updating it.