v0.5.1 — Native FCC-Extender shortcut
v0.5.1 — Native yellow-button shortcut to FCC-Extender
Polish release on top of v0.5.0. The companion-plugin integration is now bidirectional and natively owned on each side.
Added
- Yellow-button shortcut from the Settings screen straight into the FCC-Extender's own settings screen. The button appears only when the companion plugin is detected (same opkg-status check that powers the existing "FCC-Extender: installed (v...)" presence indicator); on every other box it stays out of the action map entirely so any host-skin yellow binding is untouched.
- This is the native replacement for the runtime monkey-patch that the FCC-Extender plugin used to inject into
FBCChannelSpeedChangeSetup.__init__in earlier releases. Each plugin now owns its own settings surface; the FCC-Extender's matching v0.2 release drops its monkey-patch in the same cycle.
Changed
_classify_fccextender_contentis now a thin wrapper around a new low-level_parse_fccextender_statushelper that returns a(state, version)tuple. The boolean detector used by the new button gate and the existing label formatter share one parser. No behaviour change to the presence-indicator label.
Tests
- 6 new cases pin the parser and the boolean detector contracts (
FccExtenderParserTests+FccExtenderInstalledDetectorTests). All existing label tests stay green. 130 / 130 total.
Notes
- No new C-binding surface, no new
recordServiceorprepare()call shapes. Pure UI / presence-detection work. - Field-verified 2026-06-22 against the FCC-Extender rc2 (v0.2) on the GigaBlue UHD Quad 4K Pro: yellow button appears, opens the FCC-Extender settings, both plugins coexist without crashes.
- On boxes without the FCC-Extender installed the new code path is dormant - no UI change, no startup cost.
Full v0.5.0 release notes (which introduce the underlying public api, EXTERNAL slot, TTL safety net and presence indicator): https://github.com/empyfi/FBC-ChannelSpeedChange/releases/tag/v0.5.0.