Parameter Load Issue When Loading on Android QGC (APK) with MAVLink Routing

[Spar-b]

Expected Behavior

Parameters load on startup less than 20 seconds

Current Behavior

Parameter load process stalls at ~40% for more than a minute.

Steps to Reproduce:

1. Download or build a QGC APK. Tested with:
   • Latest daily builds
   • Stable versions 4.4.3, 4.4.2, 4.3.4, 4.3.3, 4.4.0
2. Connect to the vehicle via Ethernet using UDP (with MAVLink routing).
3. Observe the parameter load process.

System Information

• Operating System: Android 15
• Architecture: x86_64, arm64_v8a
• QGC Versions Tested: 4.4.3, 4.4.2, 4.3.4, 4.3.3, 4.4.0
• QGC Build Types: Daily, stable, self-built
• Flight Controller: FMU-v6X with companion computer and MAVLink routing
• Autopilot Firmware: PX4 v1.15.2
• Connection Type: UDP (in all test cases)
• mavlink-routerd: v4

Detailed Description

When using QGroundControl (QGC) on Android (APK), the parameter loading process stalls at ~40% for over a minute before eventually completing. This significantly delays startup and causes unreliable operation.

• Packet loss is consistently around 80%, whether parameters load successfully (e.g., on AppImage) or not (on Android APK).
• The same QGC version (self-built or official) loads parameters in ~3 seconds when run as an AppImage on a Linux machine.
• If the flight controller (FC) is connected directly to the Android device via Wi-Fi or Ethernet (without MAVLink routing), parameters load correctly, despite the same ~80% packet loss.
• In some cases, the system worked even with 85% packet loss, which seems unexpected.
• All connections use UDP in every scenario.

Additional Details

• Issue occurs only on Android APK builds when using MAVLink routing over UDP.
• AppImage builds on Linux work flawlessly under the same conditions, despite the same packet loss (~80%).
• Direct Ethernet or Wi-Fi connection to the FC (without routing) works fine even on Android APK, also with ~80% loss.

Potential Causes

This issue might have something to do with mavlink router, or more specifically with the differences in it's interaction with different platforms