v0.3.0

What's new in v0.3.0

The headline of this release is the brand-new Fenix A320 v2 app plus full PMDG bezel annunciators on both the 737 NG3 and 777 — all driven directly from the PMDG SDK. The MobiFlight WASM module that was needed for the 737 EXEC LED in v0.2.x is now an obsolete dependency you can stop worrying about.

• 🆕 Fenix A320 v2 support — brand-new FenixA320.apk, proxies Fenix's built-in GraphQL stream on port 8083. No SimBridge, no MobiFlight, no extra installer — just install the APK, launch Fenix, and the MCDU + annunciator strip drives live from the sim. Live annunciators (FM1 / IND / RDY / FM / FM2 + FAIL + MCDU MENU) verified end-to-end against the in-sim Fenix MCDU.
• 🆕 PMDG 737 NG3 bezel annunciators end-to-end — MSG / OFST / CALL / FAIL drawn on the keypad bezel alongside the existing EXEC LED, same pipeline as the 777 annunciators. All five LEDs read directly from the PMDG NG3 SDK. Captain CDU only.
• 🆕 Server auto-close when MSFS exits — opt-in setting, ~10 second debounce. File → Settings → "Close server when MSFS exits". When MSFS closes, the server cleanly quits ~10 seconds later. If MSFS reconnects within the window (a hiccup, a quick restart), the server stays alive. Default OFF so nothing changes for existing users.
• 🆕 Optional auto-launch with MSFS via exe.xml — pair this with the new auto-close setting and the server lifecycle follows MSFS perfectly: starts when MSFS starts, quits when MSFS closes. The README has the full install snippet for MSFS 2020 + 2024, MS Store + Steam.
• 🆕 Fresh-client annunciator state replay — any annunciator already lit when the Android app connects (notably the PMDG NG3 cold-and-dark MSG light) appears immediately. Earlier versions only sent state on transitions, so an already-on annunciator could stay invisibly off on the client until something happened to toggle it.
• ✅ MobiFlight WASM module no longer required for any aircraft. The 737 EXEC LED now reads via the PMDG NG3 SDK alongside the rest of the bezel annunciators. If you have MobiFlight installed for other purposes, leave it — FlightPadFMC simply doesn't read from it anymore. The bundled Community/mobiflight-event-module/ folder is no longer included in the archive.
• 🪶 Quieter activity log — three high-frequency per-tick CDU-area dispatch DEBUG lines removed. State changes (EXEC LED on/off, MSG ANNUN on/off, etc.) still log at INFO so you keep the operational signal.

⚠ Upgrading from v0.2.x? Uninstall the old Android app first (Android Settings → Apps → 737PMDG / 777PMDG / FBWA320 / FenixA320 → Uninstall) before installing the new APK. Installing a new APK on top of an older signed build can fail with a "package conflict" / "app not installed" error because the signing keys may differ between builds. The server's settings.ini carries over automatically and picks up the new keys.