The firmware's dialog threads spend their init and shutdown time waiting
on module loading and I/O, so threads of any priority run meanwhile, and
a caller always sees SHUTDOWN after ShutdownStart (utility/dialog/priority,
even at priority 111). With savedata's short delays we only ate CPU at the
dialog's better priority, so a worse-priority caller saw NONE straight away.
Freak Out waits for SHUTDOWN after closing its savedata dialog, and spun
forever at "Please press START".
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Henrik RydgårdandClaude Opus 5.5
6b7eef1caa