SilenceArt

### 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. ### What it is, for newcomers A Windows server runs on the sim PC and connects to MSFS via SimConnect (PMDG), Win32 IPC + shared memory (iFly), proxies SimBridge (FBW A320), or proxies Fenix's GraphQL stream (Fenix A320). The server streams the CDU / MCDU screen over your local WiFi to the Android app, and key presses on the tablet go back to the sim in real time. Five separate APKs, one per aircraft — install only what you fly: - `737PMDG.apk` — PMDG 737 NGXu - `777PMDG.apk` — PMDG 777 - `iFly737MAX.apk` — iFly 737 MAX (7 / 8 / 8200 / 9 / 10) - `FBWA320.apk` — FlyByWire A32NX - `FenixA320.apk` — Fenix A320 v2 Native Android — not a web page, not a browser trick. Pixel-accurate skins, real touch calibration baked in, runs all the way back to Android 4.4. ### Install The `README!!!.txt` in the release archive has the full step-by-step install guide, split by sim version (MSFS 2020 vs 2024) and by aircraft. There are separate sections for PMDG users, iFly users, FBW users and Fenix users, so you only do the steps that apply to you. The MSFS 2024 PMDG paths in this release also list both filename variants (`737_Options.ini` / `737NG3_Options.ini`) — PMDG appears to have dropped the NG3 suffix on some MSFS 2024 builds, and the README tells you which to look for. ### Optional: auto-launch the server with MSFS If you haven't already enabled it from v0.3.0 — turn on the **"Close server when MSFS exits"** setting, then add a `<Launch.Addon>` block to your MSFS `exe.xml` pointing at `FlightPadFMCServer.exe`. The server will start when MSFS starts and quit when MSFS closes, no manual lifecycle. STEP 4 of the README has the exact paths and the snippet. ### Download - Release: https://silencediy.com/dl/dl1776106237549 - GitHub: https://github.com/diymarcus/FlightPadFMC - Discord: https://discord.gg/YVn92NGYpt - email: [email protected] ### Credits - **PMDG Simulations** — for the 737 NGXu + 777 add-ons and for shipping the PMDG SDK that makes external CDU clients possible - **iFly Simulations Software** — for the iFly 737 MAX and the iFly Plugin SDK - **FlyByWire SimBridge** — © FlyByWire Simulations — GPL-3.0 - **Fenix Simulations** — for the Fenix A320 v2 + the open GraphQL interface - **B612 Mono font** — SIL Open Font License — originally designed for aviation cockpit displays Big thanks to PMDG, iFly, the FlyByWire team and the Fenix team for the SDKs and open interfaces — they're what make this project possible. ### Feedback & bug reports If you run into anything strange, please open an issue on GitHub (or reply in this thread) — I read everything. Short excerpts from the server Activity Log and the Android app really help me track things down. Especially helpful for v0.4.0: - **iFly 737 MAX owners** — confirmation that the CDU drives correctly across the common FMS pages (INIT, RTE, LEGS, PROG, PERF), and that all 5 LEDs (EXEC / MSG / FAIL / CALL / OFST) light at the appropriate moments during a normal flight - **Anyone running MSFS 2024** — confirmation of the actual filename in your `pmdg-aircraft-738\work\` folder (`737_Options.ini` vs `737NG3_Options.ini`), and confirmation of the `exe.xml` path on your install (MS Store vs Steam) - **All users** — confirmation that the new Server Console "Aircraft" row updates immediately when you change aircraft in the MSFS profile menu (matching MobiFlight behaviour). And — if it doesn't classify your aircraft, please share the raw title shown in the "Unrecognised — ..." row so I can add it to the substring map for the next release. Happy flying! ✈️ — Marcus (SilenceDIY) https://silencediy.com

FlightPadFMC v0.3.0 — Fenix A320 support, full PMDG annunciators support. ### 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. ### What it is, for newcomers A Windows server runs on the sim PC and connects to MSFS via SimConnect (PMDG), proxies SimBridge (FBW A320), or proxies Fenix's GraphQL stream (Fenix A320). The server streams the CDU / MCDU screen over your local WiFi to the Android app, and key presses on the tablet go back to the sim in real time. Four separate APKs, one per aircraft — install only what you fly: - `737PMDG.apk` — PMDG 737 NGXu - `777PMDG.apk` — PMDG 777 - `FBWA320.apk` — FlyByWire A32NX - `FenixA320.apk` — Fenix A320 v2 Native Android — not a web page, not a browser trick. Pixel-accurate skins, real touch calibration, runs all the way back to Android 4.4. Download: https://silencediy.com/dl/dl1776106237549

============================================================= CHANGELOG ============================================================= 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). Download V0.2.15: https://silencediy.com/dl/dl1776106237549

================================================================================ FlightPadFMC — Native Android FMC / MCDU for PMDG 737, PMDG 777 & FlyByWire A320 Version 0.2.1 By SilenceDIY (Marcus) https://github.com/diymarcus/FlightPadFMC ================================================================================ DESCRIPTION ----------- FlightPadFMC turns your Android tablet or phone into a fully functional CDU / MCDU for the PMDG 737, PMDG 777 and FlyByWire A320 in Microsoft Flight Simulator 2020 and 2024. Unlike web-based solutions, this is a true native Android app — faster, smoother and more responsive. The CDU / MCDU skins are pixel-accurate, touch input is calibrated, and the display updates live over your local WiFi. Three separate Android apps are provided, one per aircraft type: - 737PMDG.apk — PMDG 737 NGXu (700 / 800 / 900) - 777PMDG.apk — PMDG 777-300ER / 777F - FBWA320.apk — FlyByWire A32NX (via SimBridge) One Windows server acts as the bridge between MSFS and the Android apps. The same server handles all three aircraft — simply launch the matching app on your tablet and the server figures out the rest. Supported platforms: - Microsoft Flight Simulator 2020 (SimConnect v11) - Microsoft Flight Simulator 2024 (SimConnect v12) - Android 4.4 through Android 14 (single APK per aircraft) - Windows 10 / 11, 64-bit (server app) HOW IT WORKS ------------ PMDG 737 / 777: MSFS + PMDG Aircraft | SimConnect + MobiFlight WASM | FlightPadFMC Server (FlightPadFMCServer.exe) | WiFi / LAN (WebSocket) | FlightPadFMC App (Android) FlyByWire A320: MSFS + FlyByWire A32NX | FlyByWire SimBridge | FlightPadFMC Server <-- proxies SimBridge | WiFi / LAN (WebSocket) | FBWA320 App (Android) The server connects to MSFS via SimConnect (PMDG) or proxies SimBridge (FlyByWire), reads the CDU / MCDU screen data, and streams it to the Android app over your local network. Key presses are sent back to the server and forwarded to the aircraft in real time. REQUIREMENTS ------------ General (all users): - Microsoft Flight Simulator 2020 OR 2024 - Windows 10 / 11, 64-bit - Android device on the same WiFi / LAN as the PC - Android 4.4 or newer For PMDG 737 / 777: - PMDG 737 NGXu or PMDG 777 add-on - PMDG SDK enabled in the aircraft options (Step 1) - MobiFlight WASM Module installed in the Community folder (Step 2) For FlyByWire A320: - FlyByWire A32NX (free, from flightsim.to or FBW installer) - FlyByWire SimBridge running on the same PC (Step 3) INSTALLATION — STEP BY STEP ---------------------------- This is an Alpha release. Bug reports and feedback are very welcome — they help me track down the last rough edges before a proper 1.0. STEP 1 — Enable the PMDG SDK (skip if you only use the A320) --------------------------------------------------------------- The PMDG SDK must be enabled so external tools (like FlightPadFMC) can read the CDU data. You need to edit a small .ini file once per aircraft per sim. In every case: - Open the file in a text editor (Notepad works). - Add or edit the [SDK] section so it contains: [SDK] EnableDataBroadcast=1 EnableCDUBroadcast.0=1 - Save the file. IMPORTANT: make sure there is a blank line / trailing newline at the end — PMDG has been known to discard the [SDK] section if the file does not end cleanly. - Restart MSFS if it was already running. - Load the aircraft fully, past "ready to fly", at least once. The file is regenerated by PMDG on first load, so if it does not exist yet, fly the aircraft once and it will appear. --------------------------------------------------------------- MSFS 2020 --------------------------------------------------------------- PMDG 737 (MSFS 2020, MS Store): %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ packages\pmdg-aircraft-738\work\737NG3_Options.ini PMDG 737 (MSFS 2020, Steam): %APPDATA%\Microsoft Flight Simulator\Packages\pmdg-aircraft-738\work\ 737NG3_Options.ini PMDG 777 (MSFS 2020, MS Store): %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ packages\pmdg-aircraft-77w\work\777_Options.ini PMDG 777 (MSFS 2020, Steam): %APPDATA%\Microsoft Flight Simulator\Packages\pmdg-aircraft-77w\work\ 777_Options.ini --------------------------------------------------------------- MSFS 2024 --------------------------------------------------------------- MSFS 2024 stores PMDG options under a different root than 2020 — look in the "Limitless" package, inside a WASM\MSFS2024 subfolder. PMDG 737 (MSFS 2024, MS Store): %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\ WASM\MSFS2024\pmdg-aircraft-738\work\737NG3_Options.ini PMDG 737 (MSFS 2024, Steam): %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\ pmdg-aircraft-738\work\737NG3_Options.ini PMDG 777 (MSFS 2024, MS Store): %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\ WASM\MSFS2024\pmdg-aircraft-77w\work\777_Options.ini PMDG 777 (MSFS 2024, Steam): %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\ pmdg-aircraft-77w\work\777_Options.ini The folder name may show up as "pmdg-aircraft-737" or "pmdg-aircraft-777" instead of "738" / "77w" depending on which PMDG build you own. If you don't see the exact folder above, look for any folder starting with "pmdg-aircraft-73" (for the 737) or "pmdg-aircraft-77" (for the 777) in the same parent directory — that's the one to edit. STEP 2 — Install the MobiFlight WASM Module (skip if you only use the A320) ----------------------------------------------------------------------------- The MobiFlight WASM Module (a.k.a. "mobiflight-event-module" / "EVENT MODULE") runs inside MSFS and exposes aircraft L-variables that FlightPadFMC needs for the PMDG 737 EXEC LED. The install procedure is different between MSFS 2020 and MSFS 2024 — follow the section that matches your sim. --------------------------------------------------------------- MSFS 2020 — manual copy into Community folder --------------------------------------------------------------- 1. Download the module from: https://github.com/MobiFlight/MobiFlight-WASM-Module Or use the "mobiflight-event-module" folder included in the "Community" archive shipped with FlightPadFMC. 2. Copy the "mobiflight-event-module" folder into your MSFS 2020 Community folder: MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\ LocalCache\Packages\Community\ Steam: %APPDATA%\Microsoft Flight Simulator\Packages\Community\ 3. Restart MSFS 2020. --------------------------------------------------------------- MSFS 2024 — enable through the in-sim Marketplace --------------------------------------------------------------- MSFS 2024 does not use a manual Community folder for most add-ons. The MobiFlight WASM module is published as a free Marketplace item ("EVENT MODULE") and only needs to be enabled: 1. Launch MSFS 2024. 2. Open Marketplace -> My Library -> Community. 3. Find the entry named "EVENT MODULE" (this is the MobiFlight WASM module — same module as MSFS 2020, just delivered via Marketplace). If you don't see it in "My Library", download it once from the Marketplace first (it is free). It should then appear under "My Library". 4. Click Enable on the EVENT MODULE entry. 5. Restart MSFS 2024 so the WASM module is loaded. --------------------------------------------------------------- NOTE: The FlightPadFMC server automatically checks whether the module is installed when a PMDG 737 connects, and will log a red error in the server Activity Log if it is missing or not enabled. If you see that error, return to this step. NOTE: If you already use MobiFlight for other purposes, the WASM module is most likely already installed — no extra action needed. STEP 3 — Install FlyByWire SimBridge (skip if you only use the 737 / 777) --------------------------------------------------------------------------- The A320 support proxies the MCDU through FlyByWire's own SimBridge tool. SimBridge is free and maintained by the FlyByWire team, and it is installed through the FlyByWire A32NX installer — you do not need a separate download. 1. Launch the FlyByWire Installer (the same tool you used to install the A32NX itself). If you don't have it yet: https://flybywiresim.com/download/ 2. In the installer, open the A32NX section and start the setup / update flow. During setup you will be offered a list of optional components — tick "SimBridge" (or "Install SimBridge") and let the installer finish. 3. Launch SimBridge. It runs as a small tray app on the PC. You can start it in any of these ways (pick whichever is easiest): - From the Start menu shortcut created by the FBW installer. - Let the FBW installer start it for you at the end of setup. - Directly from the Community folder: <Community>\flybywire-externaltools-simbridge\fbw-simbridge.exe (this is the exact executable — you can pin it to the taskbar or make a desktop shortcut for one-click launch). 4. Load the A32NX in MSFS. SimBridge must be running before you connect the FBWA320 Android app, otherwise the app will just sit at "Waiting for server...". The FlightPadFMC server Activity Log will also tell you if SimBridge is missing or not reachable. More info: https://docs.flybywiresim.com/tools/simbridge/ STEP 4 — Run the FlightPadFMC Server ------------------------------------ 1. Extract the FlightPadFMC server folder anywhere on your PC. 2. Inside that folder you will find two SimConnect subfolders: dist\SDK2020\SimConnect.dll <-- for MSFS 2020 dist\SDK2024\SimConnect.dll <-- for MSFS 2024 Both DLLs ship with the release — no manual copy needed. 3. Run FlightPadFMCServer.exe. 4. In the server: File -> Settings, set "MSFS Version" to 2020 or 2024 to match your installation, then restart the server. 5. Start MSFS and load your aircraft. The server will show: - MSFS: Connected / Not connected - Android: which FMC app is connected - Server: WebSocket running / stopped 6. Allow the server through Windows Firewall when prompted. If the firewall blocks the server, the Android apps will never see it on the LAN. Activity Log, port setting and About window are available from the menu. Closing the window minimises the server to the system tray. STEP 5 — Install the Android App(s) ----------------------------------- Three APKs are provided, one per aircraft. Install only the one(s) you fly: 737PMDG.apk — for PMDG 737 NGXu 777PMDG.apk — for PMDG 777 FBWA320.apk — for FlyByWire A32NX To install: 1. IMPORTANT — If you already have an older version of the same FlightPadFMC app installed, uninstall it first (Android Settings > Apps > 737FMCPad / 777FMCPad / FBWA320 > Uninstall). Installing a new APK on top of an old one can fail with a "package conflict" / "app not installed" error because the signing keys between builds may differ. Uninstalling the old version first avoids this. 2. Copy the APK to your Android device. 3. Enable "Install from unknown sources" in Android Settings > Security (or "Install unknown apps" on newer Android versions). 4. Tap the APK file to install. The apps work on Android 4.4 through Android 14. The only permission used is local network access. In-app settings: Tap the gear icon on the CDU / MCDU skin to open the in-app Settings dialog. From here you can: - Switch connection mode between Auto (mDNS auto-discovery) and Manual (type the server IP yourself) - Enter the server IP and port manually if auto-discovery does not find the server on your network - Toggle click sound and haptic feedback If the app sits on "Waiting for server..." or "No IP — tap gear to configure", open Settings, switch to Manual mode, and enter the IP address shown in the server window title bar (default port 8765). Auto mode works on most home networks, but some routers block mDNS — in that case Manual mode is the reliable fallback. STEP 6 — Connect ---------------- 1. Make sure the PC and the Android device are on the same WiFi / LAN. 2. Launch the matching app on your tablet: - 737PMDG -> PMDG 737 loaded - 777PMDG -> PMDG 777 loaded - FBWA320 -> A32NX loaded + SimBridge running 3. The app auto-discovers the server via mDNS. No IP entry needed in most home networks. 4. If auto-discovery fails: open the in-app Settings, switch mode to "Manual", and type the server IP shown in the server window title bar. Default port is 8765. Once connected, the CDU / MCDU screen appears and updates live. The server also fires a fake MENU key on connect, so the display is never blank. USAGE TIPS ---------- - Tap the gear icon on the skin to open in-app Settings. - Tap the X icon to cleanly close the app. - If the server restarts, the app reconnects automatically (5 fast retries, then a 30-second slow retry until it comes back). - Pressing Home / switching apps disconnects the Android side cleanly; returning to the app reconnects automatically. - The server tray icon turns green when an Android app is connected. TROUBLESHOOTING --------------- EXEC LED not working (PMDG 737): - Make sure the MobiFlight WASM Module is in the Community folder. - Restart MSFS after installing the WASM module. - Check the server Activity Log for "MF LVar switch_6042_73X" messages. CDU / MCDU screen not showing: - PMDG: verify PMDG SDK is enabled (Step 1) and MSFS was restarted. - A320: verify SimBridge is running (launch the SimBridge tray app — see Step 3). The server Activity Log will show SimBridge retry messages if it cannot reach it. - Make sure you launched the correct app for the aircraft you loaded. - In the server, check that "MSFS Version" matches your installation (2020 vs 2024). App not connecting: - PC and Android on the same WiFi network? - Windows Firewall allowing FlightPadFMCServer.exe on private networks? - Default port 8765 not already used by another app? - Try "Manual" mode in the app and enter the server IP by hand. Keys not registering: - PMDG: PMDG SDK must be enabled. Also make sure the aircraft has been fully loaded past "ready to fly" at least once after enabling the SDK. - A320: SimBridge must be running before you press any key. Sound is quiet or inconsistent on newer Android: - Update to v0.2.1 — sound output was reworked in this release and now follows the media volume slider cleanly on Android 12+. KNOWN LIMITATIONS ----------------- The following items are known and are NOT bugs in FlightPadFMC — they are limitations of the upstream data sources we depend on. They will be addressed in future releases as the underlying tools gain the necessary features, or as FlightPadFMC adds support for aircraft that do expose the missing data. FBWA320 — MCDU annunciator LEDs stay dark The 5 annunciator indicators at the top of the A320 MCDU skin (FM1, IND, RDY, --, FM2) are drawn on the app but remain off under all conditions, including after triggering FMGC failures from the FlyByWire flyPad Failures menu. Reason: the FlyByWire A32NX does not simulate the MCDU annunciator panel state in the in-sim MCDU gauge either, so FlyByWire SimBridge has no data to forward. This was verified on a live A32NX by triggering FMGC1 failures and observing that the annunciators never lit up on the real cockpit MCDU in the sim — it is an FBW limitation, not a FlightPadFMC bug. Planned to light up in a future release once Fenix A320 support is added, since Fenix exposes all annunciators as L:Variables. FBWA320 — certain MCDU pages may show placeholder characters On some MCDU pages where the FBW HTML MCDU gauge uses special cockpit glyphs (empty data-entry boxes, custom symbols), the Android app may render a plain character or a small placeholder square instead of the intended glyph. This is because FlyByWire's in-sim MCDU uses a custom font with remapped codepoints that B612 Mono (the aviation font used by FlightPadFMC) does not have a matching glyph for. Functionality is not affected — only the visual appearance of that specific character. A character translation table (translateFbwChar() in MainActivity.java) is already in place for known remaps and will be extended in future updates as more are identified. FBWA320 — not all MCDU pages fully verified FlightPadFMC v0.2.1 is the first release with FlyByWire A320 support. The common MCDU pages (MCDU MENU, INIT A/B, F-PLN, PROG, PERF) have been tested, but the A32NX MCDU has many less frequently used pages that have not yet been exercised in a live flight. If you see an alignment, color, or rendering issue on a specific page, please report it — the fix is usually one line once the broken data is captured from the server log. FMC777 / FMC737 — only EXEC LED is currently implemented The real PMDG 737 NGXu and 777 CDUs have several annunciator lights next to the display (EXEC, MSG, CALL, FAIL, OFST, DSPY on the 737 / EXEC, CALL, FAIL, MSG, OFST on the 777). FlightPadFMC v0.2.1 currently only drives the EXEC LED on both aircraft — all other annunciators are drawn on the skin but remain off. The underlying data is available via the PMDG SDK and MobiFlight L:Variables, so this is a FlightPadFMC-side limitation, not a data source limitation. Additional annunciators will be added in a future release. Most common operational use of the PMDG CDU does not depend on the missing annunciators — MSG in particular is the one most users will notice is not lighting during normal flight. OPEN SOURCE CREDITS ------------------- MobiFlight WASM Module Copyright (c) 2021 Sebastian Moebius, MobiFlight MIT License — https://github.com/MobiFlight/MobiFlight-WASM-Module FlyByWire SimBridge Copyright (c) FlyByWire Simulations GPL-3.0 — https://github.com/flybywiresim/simbridge B612 Mono font SIL Open Font License — designed for aviation cockpit displays ================================================================================ CHANGELOG ================================================================================ 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 ================================================================================ ROADMAP — What's next ================================================================================ The next two aircraft targeted for FlightPadFMC support are both fully researched, SDK paths are already scoped out, and they will be added as new Android apps in upcoming releases: Fenix A320 ---------- - MCDU screen via the Fenix GraphQL interface - Subscribes to aircraft.mcdu1.display / aircraft.mcdu2.display - Full color + size tag support (white, green, cyan, magenta, amber, red, small / large) and all Airbus special glyphs - Key input via MobiFlight WASM L-variables (S_CDU1_KEY_*) - LEDs: FAIL, IND, FM, FM1, FM2, MENU, RDY (all exposed) iFly 737 MAX ------------ - CDU screen via Windows shared memory (iFly737MAX_SDK_FileMappingObject) - Full 14x24 character grid with per-cell color + small-font flags - Key input via WM_COPYDATA messages to the iFly Plugin window - LEDs: EXEC, MSG, FAIL, CALL, OFST - Works on MSFS 2020 AND MSFS 2024 - Supports all MAX variants (7 / 8 / 8200 / 9 / 10) Other items on the longer-term roadmap: - Single Android app with automatic skin-switch between aircraft - PFD / MFD secondary display app - Second CDU support (Captain + F/O simultaneously) - iOS port (community contribution welcome) Download: V0.2.1 https://www.silencediy.com/?sdm_process_download=1&download_id=2054

================================================================================ Udated to Version 0.2.0 FlightPadFMC — Native Android FMC for PMDG 737 & 777 By SilenceDIY (Marcus) ================================================================================ DESCRIPTION ----------- FlightPadFMC turns your Android tablet into a fully functional CDU (FMC) for PMDG aircraft in Microsoft Flight Simulator 2020. Unlike web-based solutions, this is a true native Android app — faster, smoother, and more responsive. The CDU skin is pixel-accurate, touch input is calibrated. Supported aircraft: - PMDG 737 NGXu (737-700 / 737-800/ 737-900) - PMDG 777X Supported platforms: - MSFS 2020 (MSFS 2024 compatible — same SimConnect API) - Android 4.4 and above (one APK for all Android versions) - Windows 10 / 11 (server app) HOW IT WORKS ------------ MSFS 2020 + PMDG Aircraft | SimConnect SDK | FlightPadFMC Server (Windows .exe) | WiFi / LAN (WebSocket) | FlightPadFMC App (Android tablet) The Windows server connects to MSFS via SimConnect, reads the CDU screen data state from PMDG, and streams it to the Android app over your local WiFi network. Key presses from the tablet are sent back to the server and forwarded to PMDG in real time. REQUIREMENTS ------------ - Microsoft Flight Simulator 2020/2024 (On Test) - PMDG 737 NGXu or PMDG 777X add-on - PMDG SDK enabled in aircraft options (see below) - MobiFlight WASM Module installed in MSFS Community folder - Android tablet (any size, Android 4.4+) - Both PC and tablet on the same WiFi / LAN network - Windows 10 or 11 (64-bit) INSTALLATION — STEP BY STEP Keep in mind that this is an Alpha version. I would greatly appreciate any bug reports or feedback you can provide to help improve the app! ---------------------------- STEP 1 — Enable PMDG SDK The PMDG SDK must be enabled to allow external tools to read CDU data. For PMDG 737: Open this file in a text editor: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ packages\pmdg-aircraft-738\work\737NG3_Options.ini Add or edit the [SDK] section: [SDK] EnableDataBroadcast=1 EnableCDUBroadcast.0=1 For PMDG 777: Open this file in a text editor: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ packages\pmdg-aircraft-77w\work\777_Options.ini Add or edit the [SDK] section: [SDK] EnableDataBroadcast=1 EnableCDUBroadcast.0=1 Save the file and restart MSFS if it was running. NOTE: If you use the Microsoft Store version of MSFS, the path above is correct. For Steam version, the path is: %APPDATA%\Microsoft Flight Simulator\Packages\... STEP 2 — Install MobiFlight WASM Module MSFS and provides access to aircraft L-variables. 1. Download MobiFlight WASM Module from: https://github.com/MobiFlight/MobiFlight-WASM-Module Or the mobiflight-event-module you can find in archive/Community 2. Copy the "mobiflight-event-module" folder into your MSFS Community folder. Your Community folder is typically: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ packages\Community\ 3. Restart MSFS after installing. NOTE: The MobiFlight WASM Module is a free, open-source project. If you already have MobiFlight installed for other purposes, the WASM module is already present — no extra steps needed. STEP 3 — Install SimConnect DLL The server requires SimConnect.dll to communicate with MSFS. The server will automatically search for SimConnect.dll in these locations: 1. Same folder as FlightPadFMC_Server.exe (recommended) The easiest approach: copy SimConnect.dll next to FlightPadFMC_Server.exe. You can find SimConnect.dll in your MSFS SDK installation, or download it from the MSFS Developer Mode tools. STEP 4 — Run the Server 1. Extract the FlightPadFMC server folder to any location on your PC. 2. Run FlightPadFMCServer.exe 3. Start MSFS and load a PMDG aircraft. 4. The server status will show "MSFS Connected" when ready. 5.Ensure you Allow Access through your firewall. If the firewall is not configured correctly, the Android app will be unable to communicate with the server. The server shows: - MSFS status (connected / not connected) - Android status (which app is connected) - Server status (WebSocket running) - Activity log Settings (port, log level) are available from the menu bar. The server minimizes to the system tray when closed. STEP 5 — Install Android App Two separate APKs are provided — one for 737, one for 777. 737FMCPad.apk — for PMDG 737 NGXu 777FMCPad.apk — for PMDG 777X To install: 1. Copy the APK to your Android tablet. 2. Enable "Install from unknown sources" in Android Settings > Security. 3. Tap the APK file to install. The app works on Android 4.4 through Android 14. No special permissions needed beyond local network access. STEP 6 — Connect 1. Make sure your PC and tablet are on the same WiFi network. 2. Open the FlightPadFMC app on your tablet. 3. The app will auto-discover the server via mDNS (no IP needed in most cases). 4. If auto-discovery fails, open Settings in the app and enter the server IP manually. The server IP is shown in the server window title bar. Once connected, the CDU screen will appear and update in real time. USAGE TIPS ---------- - Tap the FMC position button (top-left) to switch between LEFT / CENTER / RIGHT CDU positions. (Not yet implemented) - Tap the gear icon to open Settings. - Tap the X button to close the app cleanly. - If the server is restarted, the app will reconnect automatically. - If the app is minimized (home button), it disconnects. Return to the app to reconnect automatically. TROUBLESHOOTING --------------- EXEC LED not working: - Make sure MobiFlight WASM Module is installed in the Community folder. - Restart MSFS after installing the WASM module. - Check the server Activity Log for "MF LVar switch_6042_73X" messages. CDU screen not showing / wrong aircraft: - Check that PMDG SDK is enabled (Step 1). - Make sure the correct APK is installed for your aircraft (737 or 777). - The server detects aircraft from the Android app's identify message — make sure you opened the correct app. App not connecting: - Check that PC and tablet are on the same WiFi network. - Try entering the server IP manually in the app Settings. - Check Windows Firewall — allow FlightPadFMCServer.exe on private networks. - Default port is 8765. Change in server Settings if needed. Keys not registering in PMDG: - Make sure PMDG SDK is enabled (Step 1). OPEN SOURCE CREDITS ------------------- MobiFlight WASM Module Copyright (c) 2021 Sebastian Moebius, MobiFlight MIT License — https://github.com/MobiFlight/MobiFlight-WASM-Module ================================================================================ CHANGELOG ================================================================================ Version 0.2.0 — April 2026 --------------------------- NEW FEATURES: + EXEC LED for PMDG 737 — via MobiFlight WASM L-variable (switch_6042_73X) + EXEC LED for PMDG 777 — live via SimConnect (CDU data area) IMPROVEMENTS: + Key input speed: 600ms → 200ms delay between keys (discovered PMDG requires proper press+release mouse event cycle) + CLR button fixed on both 737 and 777 — now correctly deletes one character per tap without clearing the entire scratchpad after 2 seconds (used PMDG's K:ROTOR_BRAKE press/release events from HubHop database) + MSFS disconnect now detected immediately when MSFS closes + Android apps: fixed ghost "Android connected" status after app close + Android apps: app now fully disconnects when minimized (home button) and reconnects automatically when returned to foreground + Android apps: after 5 failed connection attempts, switches to slow retry mode (every 30 seconds) instead of stopping — always reconnects when server becomes available again + Server version bump to 0.2.0 BUG FIXES: - Fixed stale WebSocket callbacks causing ghost reconnects on server (737 app) - Fixed missing exec_led message handler in 737 app - Fixed CLR confirmation dialog race condition on app close (737 app) - Fixed SimConnect_CallDispatch not checking return value on MSFS disconnect Version 0.1.0 — March 2026 --------------------------- Initial release. + PMDG 777 CDU screen live on Android tablet + PMDG 737 CDU screen live on Android tablet + Full key input (all CDU buttons) for 737 and 777 + Auto-discovery via mDNS (no manual IP needed on most networks) + Manual IP fallback with retry + WiFi auto-reconnect + Modern server GUI with connection status indicators + System tray support + Activity log with filter + Touch calibration system + Sound and haptic feedback + Works on Android 4.4 through Android 14 ================================================================================ SUPPORT & FEEDBACK ================================================================================ I hope you enjoy using this as much as I enjoyed building it. If you encounter any issues or have suggestions for new features. Compatibility Note: Tested exclusively on MSFS 2020. Support for MSFS 2024 (Under Test).Focus is currently on the PMDG 777/737. and other aircraft (Airbus/FBW/etc.) is planned for future updates once the core version is stable. GitHub: https://github.com/diymarcus/FlightPadFMC Website: silencediy.com ================================================================================ Download: V0.2.0 https://www.silencediy.com/?sdm_process_download=1&download_id=2054 P.S. Captains, this has already been downloaded hundreds of times. Could I please get some feedback? I especially need someone to test it in MSFS 2024, as it have been tested in MSFS 2020 only. Many thanks!

Hi Captains! 👋 Many of you will remember the excellent Virtual FMC apps we had back in the Prepar3D days—my favorite for years. Since the move to MSFS 2020, several web-based CDU solutions have appeared. While they work well, I’ve always missed the responsiveness of a true native app. Web apps are convenient, but native apps are simply faster, smoother, and more reliable. So, I decided to build one myself! FlightPadFMC is a fully native Android application that turns your tablet into a PMDG 777/737 CDU. No browser, no complex web server, and zero lag. It’s a clean, high-performance experience designed to feel like the real hardware sitting on your flight deck. A Note on iOS: I know many would love an iOS version. Unfortunately, I don't own a Mac to build and sign iOS apps, so I cannot provide one at this time. However, I am releasing the project as Open Source on GitHub very soon. The core logic is clean and well-structured, so if anyone in the community has a Mac and the skills to port it, I would welcome the collaboration! ✈️ Features Real-Time CDU Display: Streams live data from the PMDG 777/737 via SimConnect, including all text, colors, and formatting. Full Tactical Input: Every LSK, function key, and alphanumeric button is fully supported. EXEC LED: Real-time annunciator support—the EXEC light glows green on your tablet exactly when it does in the cockpit. Physical Feedback: Optional button click sounds and haptic vibration for a tactile feel. Built for Stability: built-in crash logging for easy troubleshooting. 💻 Requirements Android App: Android 4.4 (KitKat) through Android 14+ (Tested on v4.4 and v12). WiFi connection to the same local network as your Sim PC. Windows Server: Windows 10/11. Microsoft Flight Simulator 2020. PMDG 777 or 737 (any variant). PMDG SDK Enabled: You must enable data broadcasting in your aircraft options files (see Setup below). ⚙️ How it Works MSFS + PMDG exports data via the SimConnect SDK. FlightPadFMC Server (Windows) reads the screen data and LED states. WebSocket Streaming sends that data over your home WiFi to your tablet. Button Presses on the tablet are sent back to the server and injected directly into the aircraft as PMDG SDK events. 🔧 Setup Instructions Keep in mind that this is an Alpha version. I would greatly appreciate any bug reports or feedback you can provide to help improve the app! IMPORTANT: Please read the Setup Instructions carefully to ensure a successful connection. 1. Enable the PMDG SDK You must tell the PMDG aircraft to share its data with external apps. Locate your 777_Options.ini and 737_Options.ini files. Typical path (MS Store): %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\pmdg-aircraft-77w\work\ Typical path (Steam): %APPDATA%\Microsoft Flight Simulator\Packages\pmdg-aircraft-77w\work\ Open the .ini file and ensure these lines are set under the [SDK] section: [SDK] EnableDataBroadcast=1 EnableCDUBroadcast.0=1 EnableCDUBroadcast.1=1 2. Run the Server Launch FlightPadFMC_Server.exe on your flight simulation PC. When prompted by Windows, ensure you Allow Access through your firewall. If the firewall is not configured correctly, the Android app will be unable to communicate with the server. Navigate to File > Settings to select your aircraft version (737 or 777). (And MSFS2020 or MSFS2024 This feature is currently in development and will be included in a future update.) 3. Install the App Install the APK on your Android tablet. Ensure the tablet and PC are on the same WiFi network. If the app does not connect automatically, go to Settings and manually enter the Server IP (the IP address of the PC where FlightPadFMC_Server.exe is running). Current support is limited to the Captain's (Left-side) CDU. Support for the Co-pilot and Center CDUs is planned for a future update. Important Connection Note: If you launch the Android app before starting the Windows server, the app will make 5 connection attempts before stopping. If it fails to connect, simply minimize the app and re-open it (or restart it) to trigger a new search for the server. If you switch from the PMDG 737 to the PMDG 777 (or vice versa), you must Force Stop the Android app in your device settings. This ensures the connection is completely reset for the new aircraft's data structure. In future releases, I plan to implement separate network ports for the 777 and 737 to prevent connection conflicts. 4. Fly! Launch the app on your tablet. Load your PMDG 777 or 737 in MSFS and enjoy your new physical CDU! Feedback & Support: I hope you enjoy using this as much as I enjoyed building it. If you encounter any issues or have suggestions for new features. Compatibility Note: Tested exclusively on MSFS 2020. Focus is currently on the PMDG 777/737. Support for MSFS 2024 and other aircraft (Airbus/FBW/etc.) is planned for future updates once the core version is stable. Known Issues: PMDG 737: The EXEC LED is currently non-functional. This is a known limitation and will be addressed in a future update. https://www.silencediy.com/?sdm_process_download=1&download_id=2054