0.4.1

What's new in v0.4.1

• 🆕 Captain ↔ FO CDU swipe (PMDG 737 + 777) — swipe left on the CDU display to switch to the First Officer's CDU, swipe right to return to the Captain's. A green CAPT CDU / FO CDU label flashes so you always know which seat you're on. Screen, bezel annunciators (EXEC / MSG / OFST / FAIL / DSPY / CALL) and every key press all follow the selected side — the FO CDU is fully functional, not just a mirrored screen.
• 🆕 "CDU Side" setting — the app settings now have a Captain / First Officer selector. The saved side is applied on every connect, so a tablet set to First Officer always comes up on the FO CDU. Swiping remains a temporary override that never changes the saved setting.
• 🆕 Dual-tablet cockpits — two tablets can connect at the same time, one on the Captain CDU and one on the FO CDU, each fully independent. If you've been building a two-seat setup, this release is for you.
• ✨ Smarter "app outdated" check — the server now knows the minimum compatible app version per aircraft. Only the PMDG 737 and 777 apps need the 0.4.1 update; your FBW A320, Fenix A320 and iFly 737 MAX 0.4.0 apps remain fully compatible and won't be nagged.

⚠ One new setup line for the FO CDU: add EnableCDUBroadcast.1=1 to your PMDG aircraft's options.ini, next to the existing EnableCDUBroadcast.0=1 (full paths in the README). Without it, the FO screen stays blank after a swipe — the .0 line only broadcasts the Captain's CDU.

⚠ Upgrading? Only two APKs changed in this release: 737PMDG.apk and 777PMDG.apk (now versionName 0.4.1). Install them over the top of 0.4.0; if Android reports a package conflict, uninstall the old app first. The FBW A320, Fenix A320 and iFly 737 MAX apps are unchanged — keep your 0.4.0 installs. The server EXE is updated to 0.4.1 and works with all of them.

v0.4.0

What's new in v0.4.0

The headline of this release is iFly 737 MAX support as a brand-new app, and a rewritten Server Console that finally tells you, at a glance, exactly what's going on between MSFS, the server and your tablet. Plus a coordinated visual-polish round across all six Android apps — every CDU and MCDU now rendering closer to how it looks on the real flight deck.

• 🆕 iFly 737 MAX support — brand-new iFly737MAX.apk. Drives the iFly 737 MAX CDU end-to-end via the iFly Plugin's shared memory + WM_COPYDATA interface — no PMDG SDK setup, no SimBridge, no MobiFlight. Just install the iFly 737 MAX, make sure the iFly Plugin is enabled in MSFS Add-Ons, install the APK, and you're flying. All 5 LEDs (EXEC / MSG / FAIL / CALL / OFST) drive live from the plugin's shared memory. Works on MSFS 2020 AND MSFS 2024, supports all MAX variants (7 / 8 / 8200 / 9 / 10).
• 🆕 Automatic aircraft detection in MSFS — the server now identifies which aircraft you have loaded the moment you pick it in the MSFS profile menu, BEFORE you click Fly. Parallel SimConnect TITLE SimVar subscription (vanilla, no WASM) means changes are instant — same as MobiFlight does it. Five aircraft mapped: PMDG 777, PMDG 737NG, iFly 737 MAX, FlyByWire A320, Fenix A320.
• 🆕 New Server Console panel — a persistent black status panel sits next to the Connection Status card and surfaces non-scrolling state you'd otherwise lose to the activity log. Shows which aircraft is loaded, SDK health (PMDG broadcast / iFly shm / SimBridge / Fenix WS), aircraft-mismatch warnings (you opened the FBW app but loaded the 737), MSFS auto-exit countdown, outdated-Android-app warnings, and a sky-blue "✈ Blue Sky Captain" row when everything's healthy. Activity log still mirrors every transition with [OK] / [WARN] / [ERROR] / [INFO] tags so .log files you share for support carry the full story.
• 🆕 Tablet-side status overlays — when the server detects a known issue (PMDG SDK silent, SimBridge tray app not running, Fenix EFB not running, aircraft mismatch), the diagnosis appears as an amber overlay right on the tablet's CDU/MCDU screen. Long messages auto-shrink to fit any tablet width. No more "the tablet is blank, why?" confusion — the tablet itself tells you.
• 🆕 SimBridge 3-state startup check — distinguishes "package missing" / "package found but tray app not running on :8380" / "ready". The activity log message tells you exactly which step you're missing instead of a generic "found".
• 🆕 Server connection status shows MSFS version — "Connected MSFS 2020" / "Connected MSFS 2024" instead of bare "Connected", so the label always agrees with whichever SimConnect DLL the server is actually loaded against.
• ✨ Annunciator text glow — MSG / OFST / DSPY / FAIL / CALL now glow with a soft halo when lit (same colour as the label), mimicking how the real bezel annunciators look on the in-sim cockpit render. Applied across all six apps.
• ✨ EXEC LED rounded corners (PMDG + iFly) — the EXEC indicator above the EXEC button is now a rounded-corner rectangle in white, matching the in-sim render. 90% size of the bezel slot, sits properly inside the cutout.
• ✨ Pixel-detected button shapes from the bezel skin — no manual touch-area calibration needed any more on any of the six apps. The Calibrate button is gone from settings; defaults are baked from the cockpit-tablet sweeps. Press feedback uses a cockpit-feel fade-in/fade-out shadow tuned for rapid-press correctness.
• ✨ FAIL annunciator now red on iFly + FMC737 (was amber, both wrong vs the in-sim render).
• ✨ FM annunciator now white on FBW + Fenix (was amber).
• 🐞 Settings-save manual-IP reconnect bug fixed across the fleet — saving a manual IP in the in-app Settings now properly triggers a clean reconnect to the new IP without needing to close and reopen the app.
• 🐞 EXEC LED flicker on iFly fixed — surfaced during live testing, the legacy embedded led field in the per-tick screen_update was clobbering iFly's EXEC state every refresh. Now picks the right cached value per aircraft.
• 🪶 Launcher labels unified — PMDG737 / PMDG777 / PMDG777-Silence / iFly737MAX / FBWA320 / FenixA320 for consistent ordering on tablet home screens.

⚠ Upgrading from v0.3.x? Uninstall the old Android apps first (Android Settings → Apps → 737PMDG / 777PMDG / FBWA320 / FenixA320 → Uninstall) before installing the v0.4.0 APKs. Installing a new APK on top of an older signed build can fail with a "package conflict" / "app not installed" error. The server's settings.ini carries over automatically. The new iFly737MAX APK is a fresh install — no old version to remove for that one.

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.

v0.2.15

Version 0.2.15 — April 2026

BUG FIXES:

• Fixed reconnect race condition where a stale WebSocket disconnect could
  clobber the active aircraft state, causing all CDU keys to be silently
  dropped until the user manually minimized and reopened the Android app.
  Server now tracks all connected clients and only resets state when the
  last client disconnects.
• Fixed Android apps silently reconnecting to the server while minimized.
  The WiFi NetworkCallback was not unregistered in onPause, so WiFi state
  changes could trigger startConnectionProcess() in the background. Now
  properly unregistered on pause, re-registered on resume. All 3 apps fixed.
• Fixed PMDG 737 DEP ARR button not working — Android app sent "DEP" but
  server expected "DEP ARR". Added alias in the server key map.
• mDNS auto-discovery timeout increased from 5 seconds to 15 seconds —
  Android NsdManager warm-up + router multicast propagation often took
  longer than 5 seconds, causing auto-discovery to always time out and
  fall back to manual IP entry.
• Removed dead [UI] section from server settings (start_minimized,
  window_width, window_height were never read by any code).

CHANGES:

• Server version bumped to 0.2.15.

v0.2.1

Version 0.2.1 — April 2026

NEW:

• FlyByWire A32NX support via new FBWA320 Android app
  • Server proxies FlyByWire SimBridge to the app
  • mDNS auto-discovery like the PMDG apps
  • All MCDU keys mapped, 5 annunciator LEDs (FM1, IND, RDY, FM2)
• MSFS 2024 fully supported
  • Server ships with both SimConnect DLLs (SDK2020 / SDK2024)
  • New "MSFS Version" setting in server Settings
• Clickable "SilenceDIY.com" link in server header
• Server About window updated for A320 + MSFS 2024

IMPROVEMENTS:

• New Photoshop-drawn skins for all three apps, freshly calibrated
• Settings / Close icons now drawn on the skin itself — no Android system
  drawables required
• Sound output reworked for Android 12+ — fixes quiet / inconsistent click
  volume on newer phones, now follows the media volume slider
  (SoundPool streams = 1, trimmed 80 ms click WAV, USAGE_MEDIA routing)
• APK output filenames are now 737PMDG.apk / 777PMDG.apk / FBWA320.apk
  (no more generic app-debug.apk)
• Server fires a fake MENU keypress 100 ms after any app connects, so the
  screen is never blank when connecting to a static page (PMDG + A320)
• FBWA320: multi-color + multi-alignment MCDU rendering — green flight
  levels, small labels, {right}-aligned text all render correctly
• FBWA320: corrected SimBridge line array order [left, right, center]
  — fixes right-side text appearing in the center column

BUG FIXES:

• FBWA320 MCDU alignment swap (right vs center columns)
• FBWA320 multi-color text (previously single dominant color per row)
• Calibration positions for all three apps re-baked against the new skins

777FMC+737FMC+Server

Version 0.2.0