#67

Add manual recovery for original watch face values

OpenRayawawants to merge intofrom

Hi @pookjw, thanks for building HermesEnabler and for all the recent fixes and updates.

What happened on my watch

On my first install, I backed up MobileGestalt before enabling Hermès and Ultra Faces. The app later disappeared from my watch for reasons I couldn't identify. When I reinstalled, the original backup was gone, and the new initial backup captured both features already enabled. When I tried to turn them off, the app told me to restore from a backup. The only backup I had was the one that already contained the enabled values.

Related reports include #34, #58, and #26.

Proposed change

I'd like to propose a Restore Original Face Values button in Watch Faces for this case.

  1. The button checks the initial backup first, then other local snapshots from oldest to newest. It looks up DeviceBrand and main-screen-class separately. Each backup must match the current cache UUID and data length, and values matching the app's activation settings are skipped.
  2. For any unresolved field, it reuses the existing on-device checks on builds marked RecoveryVerified. It checks DeviceBrand against the device tree and main-screen-class against MainScreenStaticInfo. If either field can't be resolved, the operation stops before saving.
  3. Once both values are resolved, it updates the two slots and their corresponding CacheExtra entries in the current cache and saves once. The save path takes an automatic backup, checks for cache changes before writing, verifies the result, and attempts rollback if read-back verification fails. Existing backups are preserved.

Testing

Unsigned Release builds for the watch app and iPhone companion, the existing C and Python tests, and local recovery cases passed. The full reinstall-and-recovery flow still needs testing on a physical watch.

Thanks for taking a look. I'd appreciate your feedback on whether this approach fits the project.

Activity

3
pookjw9d ago

Thanks for working on this and sharing your experience.

I think restoring each value when its toggle is turned off would be clearer than adding a separate restore button. My intended order is to check the initial backup first, then use an independently verified system value, and finally look through other local backups when their values can be verified.

An older backup, or a value that differs from the activation value, does not necessarily contain the original value. This is especially important for main-screen-class, because an actual Ultra watch can originally use an Ultra class.

I’ve started implementing the toggle-based approach in a separate commit and credited you as a co-author. It restores initial overrides for additional capability keys and uses the existing native checks where available. Automatic recovery from other snapshots and independent verification for all keys still need more research and physical-device testing. ddf24b4c156004052aa905b3ba97d7a6817c7fdd

Rayawa9d ago

Thanks for looking into this and for crediting me as a co-author. I agree that we can’t simply turn everything off on a genuine Ultra, since the Ultra screen class may be its original value. The case I’d like to cover is when a user tries to turn off a toggle and the app asks for a backup they no longer have. If their only remaining backup already contains the enabled values, they’re stuck and can’t change the affected settings. In that situation, I think the app should give the user an explicit option to turn off the affected changes themselves.