Remaining Incompatibilites with Mini 3 Pro and new Android MSDK V5.5.0
Hello.
Now that the new M-SDK Android MSDK V5.5.0 has been release as of July 18, 2023, (https://developer.dji.com/doc/mobile-sdk-tutorial/en/), what incompatibilities still exist in Dronelink app - specifically for the DJI Mini 3 and Mini 3 Pro? Are there still incompatibilities / features to be ironed out in a future release? If so can we get some insight into the Release roadmap and the timeframe?
Many thanks!
Daniel
Comments
16 comments
DJI mini 4 won't be included for some time going off previous DJI releases, is normally about a year after drone release, and in some cases like the mini 2 se it doesn't ever happen
LOL. I meant to go back and correct that to Mini 3, but forgot. So I'll correct it now.
Reading various threads on here connected with MSDK 5.5 there are still lots of problems that DJI need to sort
This is the definitive thread: https://support.dronelink.com/hc/en-us/community/posts/16409496589331/comments/16410305783571
Thanks Jim, I'll switch over to that thread. To be clear though, these issues only pertain to the Mini 3 series and / or Android 13 correct? Or do we know if it affects other DJI products (like the Air2s)?
Daniel Snyder, anything that uses MSDK4, such as A2S Mini2 etc is fine, these problems only pertain to the Mini3 etc that use MSDK5
Beta testers to confirm that.
I notified Dev@DJI.COM about the remaining incompatibilities with the Mini 2 Pro, but they stated there is no incompatibility with MSDK 5.5 / Android 13 for the release. What exactly should I tell them to help Dronelink here?
We are already in direct communication with DJI and have sent specific error logs. If you are wanting to add your voice you can just tell them that you are still experiencing issues even after their fixes so the work is not complete.
Done, I sent this off to their Dev Support:
Here is the DJI Developer response (Crashes Intermittent??):
Dear Client
Thank you for contacting DJI.
We have been communicating with Dronelink regarding the crash issues some users are experiencing on RC-N1. Since the crashes are intermittent, we are actively seeking an effective solution. If a fix has been found, we will inform Dronelink.
Kindly Regards,
FYI - The latest today from DJI Developers:
Maybe something more needs to be given beyond crash logs?
We appreciate your dilligence Daniel, but poking both of us probably isn’t going to speed things up. When it comes to random, intermittent crashes on large code bases, the only path forward is a long and tedious process of elimination, followed by the construction of an example app that we can send to DJI that has the minimum amount of code that still causes the problem and also reliably reproduces the issue, even if it does take minutes or hours to happen. This is the process we are already doing and it just takes time, especially in this case since each test cycle takes anywhere from 5 to 30 minutes for the crash to present.
If Dji is not able to solve, I am wondering who can.
When I was software developer, years ago, we were used to "instrument" the code to record what is happening in case of spurious.
Maybe things have changed since that time ...
Stéphane GARNIER u might rethink the whining of yours. Obviously there's at least three instances with possible anomalies here.
1. DJI MSDK
2. DJI Dronelink
3. The way your phone manufacturer has implemented the Android codebase including libs etc etc. It seems obvious that the third point is varying between brands like Samsung, Xiaomi, Motorola, Google etc. Especially Samsung is known for odd implementations including multiple sets of proprietary hw.
That makes it virtually impossible to track bugs thoroughly. Ok?
But why not download the other two beta candidates such as Rainbow & Litchi? I'm running all three with different outcome, thus all based on MSDKv5.
Agree.
Things are more and more complex.
Some say it is working with litchi.
I don´t know because I don´t use.
Even if it is really comparable as the features are not the same.
That said I rely on DL to provide the solution.
Please sign in to leave a comment.