A mode is temporary; the stored setting is not

Entering some mode — a shared session, a call, a low-power state — often requires a feature to stop. The one-line way to do that is to write the stored preference off and write it back on the way out. Do not: the way out is not guaranteed to run. A crash, a task kill, a battery death, an unhandled exception in the teardown — any of them leaves the user's real setting silently rewritten, with no event they could connect it to.

Give the component a second, in-memory line instead, and let the two compose: