Purpose
This is a concrete, experimental watchOS 26 contribution for the Apple-original Hermès face goal. Upstream HermesEnabler2 1.6.1 did not enable Hermès on my stock non-Hermès Apple Watch Series 6. Rather than claiming a new MobileGestalt bypass, this PR provides a separate opt-in way to render Apple's installed, genuine NanoTimeKit Hermès FaceViews inside the watch app.
Important: This is an in-app native viewer, NOT an Apple system ClockFace / Face Gallery unlock. The existing protected-system-cache issue is not resolved by this change.
Changes
- Adds Original Hermès (App Only) to Watch Faces and the MG Backup screen; the viewer remains accessible even when the MG backup cannot be made.
- Loads six Apple-original face types using system-installed FaceBundles and native
NTKFace/NTKFaceViewclasses: Circulaire (Poodle), Hermès (Zeus Analog), Radial (Bellona), Circuit H (Hades), Lucky Horse (Secretariat), and Faubourg Party (Hermes2025). - Uses a temporary app-process-only
CLKDevice.collectionTypeselection (restored using@finally). Never writes to the system MobileGestalt plist, the system face collection, or the first-party ClockFace process. - Requires the exact expected Apple face/view class and a live window attachment before reporting success. No screenshots, hand-drawn hands, reconstructed face artwork, or substitute renderers.
- Wires real reduced-luminance signals to the original Apple native tritium controller, without custom animations. This does not guarantee first-party AOD fidelity.
- Adds a simulator-only DEBUG smoke hook (
--native-smoke-index 0...5), plus reproducible verification notes inResearch/WatchFaces/WatchOS26OriginalNativeViewer.md.
Verified results
- Base: upstream 1.6.1, commit
a4feb9071. - Xcode 27.3: watchOS device SDK build passes with signing disabled.
- Xcode 27.3: watchOS simulator SDK build passes with signing disabled.
- Separate watchOS 26.5 Apple Watch Series 6 (Watch6,2) simulator: six independent app launches. Every native mount reports success after checking real window attachment, and each face's actual rendered Apple-native pixels was visually verified in a local simulator screenshot.
- Separate physical-watch research: a different experimental app (not this integrated patch) has successfully shown all six original Apple FaceViews on a stock Series 6 Cellular (Watch6,4), watchOS 26.6 / 23U67. This integrated PR app has not yet been installed or tested on that physical watch.
Physical watchOS 26.6 failure evidence that motivated this
On the Series 6 above, unchanged upstream 1.6.1 built, signed with a recognized App Group, installed and launched. However, the Hermès toggle showed “Could Not Change Setting” and remained off. Fresh diagnostic logs of 129 escape attempts showed zero usable sandbox tokens, including the actual class13-bad-query attempt. consume=-5 in the app's log means no token obtained; it is the app's fallback value, not the result of calling sandbox_extension_consume. No system MobileGestalt write was made.
Related reports, including #7 and #90, indicate other watchOS 26 devices may return a system-group token with different flags but still receive EPERM for MG writes. Token acquisition alone is not permission to modify protected system cache.
Limitations / next steps
- Not a system unlock: does not change the real ClockFace, Apple Face Gallery, system face switching or system persistence.
- The upper-right watchOS app time overlay remains visible in simulator screenshots; this patch doesn't claim to hide it.
- Third-party renderer authorization still limits some original Apple WidgetKit complications. Native AOD state transitions are present but identical first-party wrist-down/raise timing is not established.
- Private framework APIs are unstable; currently limited to watchOS 26, failing closed if native components are missing.
- No Apple frameworks/binaries, extracted face images, raw MG backup, provisioning profiles, watch IDs, private device logs or user-specific face configurations are committed.
Draft for upstream review: I can help with follow-up changes and additional physical-watch testing, but I want to distinguish verified Apple-original rendering from the still-blocked first-party system face unlock.
Activity
5I thought about this too, but I was thinking of running Carousel separately, like Procursus does. I didn't know it could be this simple.
And this isn't just for watchOS 26! It should work on most watchOS versions, even after Apple patches worse_query. I think this is worth developing further.
I’ve been testing on a Series 7 (Watch6,7), watchOS 26.6.1 (23U95), using a locally modified build of 1.6.1 (a4feb9071).
Reading MobileGestalt and making a backup work. The backup is 13,202 bytes, parses correctly, and its hash matches the transfer manifest. Opening the cache for writing still returns EPERM.
As shared in #90, four class-13 exact-file tests gave us two tokens that we could consume, but neither allowed a writable file descriptor. Both tokens were released and the cache stayed unchanged.
Since then, we’ve also tried a class-2 RENAME_SWAP check. It failed at the dummy-file control: watchOS refused to swap the app’s own Caches directory with a symlink to a dummy file inside the app’s container. We got the same EPERM result three times, so the test stopped before making any query targeting MobileGestalt. The app’s cache directory was confirmed in place afterward.
Here are the relevant anonymized log lines:
MG initial backup created: initial (13202 bytes)
MG write-access probe: denied errno=1 (Operation not permitted); no bytes written
FILE-PROBE END trials=4 consumed-tokens=2 writable-descriptors=0 content=UNCHANGED
SWAP-PROBE stage=dummy-control exchange=NO errno=1
SWAP-PROBE app-cache-restored=YES
SWAP-PROBE END control=FAIL finished=NO consumed-tokens=0 writable-descriptors=0 app-cache-restored=YES content=UNCHANGEDSo far, we haven’t obtained write access on this watch, and these tests left MobileGestalt unchanged. The swap result only covers this particular control; it doesn’t rule out every class-2 approach.
This pull request is a draft
Merging is unavailable until it is marked ready for review.
I think it should be a separate app. Interesting.