tajniak81andClaude Opus 4.8
002e484d80
The About panel and home card showed 01.03.0800 on a Mavic Pro whose
firmware is 03.02.35.05, sometimes flipping from the correct value to
the wrong one seconds after connect.
Cause was the component-level fallback I added in ec4b1bc. It is not a
slower route to the same value: BaseComponent.getFirmwareVersion()
reports the component's OWN firmware, so the flight controller answers
01.03.0800 while the aircraft is 03.02.35.05. Because it resolves
quickly and getFirmwarePackageVersion() stays null for far longer than
assumed, the fallback consistently won the race, published a wrong
version, and — since the poll stopped once firmware was non-null — ended
the search for the real one.
Remove it. getFirmwarePackageVersion() is the only source for this
field, so the value can now only be the aircraft's or absent, and the
wrong version has no source in the codebase at all. The field stays
blank until the package version is readable, which is the pre-existing
behaviour and strictly better than showing something wrong.
Widen the poll window to 60s as a best-effort head start now that
nothing fills the gap early. It is not a guarantee: a Mavic Pro was
still null after a minute, and whenever the window expires first the
next connection event carries the version through connectionMap, as it
did before this feature existed.
Found by testing against a real Mavic Pro; two earlier attempts to fix
this by re-ordering the fallback were both disproved on the aircraft.
The serial number this feature added is verified working (08RDE1J00103H1).
This fix is not yet confirmed on hardware — the controller needed charging.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
DJI MSDK Sample (Flutter)
A sample app demonstrating how to drive the DJI Mobile SDK V4 from Flutter.
DJI does not ship an official Flutter SDK — the Mobile SDK is a native Android/iOS library. This project therefore puts a Flutter UI on top of a thin native Android (Kotlin) bridge that talks to the DJI MSDK over platform channels. It covers the core "sample app" flow: SDK registration, product connection, and live telemetry (battery, GPS, flight status).
Android only. The DJI MSDK V4 native libraries here are wired up for Android. iOS would need a parallel Swift/Obj-C bridge (and a Mac to build).
Architecture
┌────────────────────────┐ platform channels ┌─────────────────────────┐
│ Flutter (Dart) │ dji_msdk/methods (MethodChannel)│ Android (Kotlin) │
│ lib/main.dart │ ───────────────────────────────▶ │ DjiSdkBridge.kt │
│ lib/dji_service.dart │ dji_msdk/events (EventChannel) │ └─ DJI Mobile SDK V4 │
│ │ ◀─────────────────────────────── │ DjiApplication.kt │
└────────────────────────┘ └─────────────────────────┘
| File | Responsibility |
|---|---|
lib/dji_service.dart |
Dart wrapper over the method/event channels |
lib/main.dart |
UI: registration / connection / telemetry cards |
android/app/.../DjiApplication.kt |
Installs the Secneo Helper (required by MSDK V4) |
android/app/.../MainActivity.kt |
Hosts the bridge, requests runtime permissions |
android/app/.../DjiSdkBridge.kt |
Registration, product lifecycle, telemetry callbacks |
android/app/build.gradle |
DJI deps, native-lib packaging, multidex, ABI filters |
Prerequisites
- Flutter (stable) and Android SDK with a connected Android device (the DJI SDK does not work on emulators).
- A DJI drone + remote controller supported by MSDK V4 (Phantom 4, Mavic 2 / Air / Mini 1, Spark, Inspire 2, etc.). The RC connects to the phone over USB.
- A DJI App Key (see below).
Set your DJI App Key
SDK registration will fail without a valid App Key bound to this app's application id.
-
Sign in at https://developer.dji.com/user/apps/ and create a new app.
- Package name must be exactly:
com.dji.flutter.dji_msdk_sample - SDK: Mobile SDK
- Package name must be exactly:
-
Copy the generated App Key.
-
Paste it into
android/gradle.properties:DJI_API_KEY=your_real_app_key_hereThe key is injected into
AndroidManifest.xmlat build time via amanifestPlaceholder(com.dji.sdk.API_KEY).
Run
flutter pub get
flutter run # device must be plugged in
# or just build the APK:
flutter build apk --debug
Using the app
- Launch it and grant the location / phone / mic permissions it requests.
- Tap Register app — needs internet on first run; status turns green on success.
- Connect the drone's remote controller to the phone over USB and power on the aircraft. The app auto-starts a connection on successful registration; you can also tap Connect to product.
- Once an aircraft connects, the Telemetry card streams battery %, GPS satellite count, flight mode, altitude, and position.
Notes & gotchas
- MSDK V4 version is pinned to
4.18(com.dji:dji-sdk/dji-sdk-provided). android.enableJetifier=trueis required — the SDK still uses legacy support libraries.- The native
.sofiles are kept unstripped and de-duplicated via thepackaging { }block inandroid/app/build.gradle; onlyarmeabi-v7aandarm64-v8aABIs are bundled (the only ABIs DJI provides). - This sample uses the core SDK, not the DJI UX SDK (its native UI widgets don't embed cleanly in Flutter).