Known Limitations — Framework Crate

Resolved issues and the limitations still open today, so you can judge fit before installing.

Resolved

Fan curve coordinates. Direct canvas drag editing keeps points stable and the cached rendering invalidates on content changes (v0.3.0).
USB-C vs USB-A classification. Ports that ever reported a Sink role stay classified as USB-C, so plugging a device into an expansion-card port no longer flips the type (v0.3.0).
Sleep/hibernate fan control. Resume resets the EC client and curve stepper, re-asserts fan duty every 30s, and a wall-clock jump fallback covers missed resume events (v0.3.0, hardened in v0.9.0).
MMIO mirror is read-only by design. The official Intel MCHBAR module exposes reads only, so Apply writes MSR 0x610; the mirror is still used for display and the effective min(MSR, MMIO) estimate. MSR writes are sufficient for the app's CPU power control.

AMD CPU Power writes are experimental. The RyzenSMU card reads STAPM/PPT Fast/PPT Slow/Tctl and can apply AC/Battery profiles, but writes stay disabled until “Enable experimental AMD writes” is checked. The maintainer has no AMD hardware, so command behavior per CPU generation still needs community verification.
Tested platform is narrow. Only Intel Core Ultra Series 1 (Meteor Lake) Framework laptops are tested; the Framework EC kernel driver must be installed.
Per-fan curves lack multi-fan verification. Covered by mocked unit tests only — no Framework 16 / Desktop hardware was available. Single-fan machines use the exact pre-existing code path.
Crash keeps the last state. Orderly quit restores firmware fan control and flushes the charge limit, but a crash or kill bypasses that path: the EC keeps the last written fan duty until sleep, reboot, or the next launch.
Logoff handover is unreliable. On some Windows 11 elevated setups the session-end broadcast never reaches the tray window, so manual/curve duty can persist after sign-out. Use Restore Auto & Exit before logging off when the fan is under manual/curve control.
HDMI/DP cards without DP-alt may be mislabeled. Port type is inferred from PD state; cards that omit DP-alt mode while drawing ~3–5 W can show the wrong label. Ports Debug Mode on the About page shows the raw role/watts; report a wrong label with the USB port report template.