Xiaomi 11 Lite 5g with Dronelink 4.7.0(266)
I have been testing the new version today. I did notice that with the new version the app crashes less, compared to previously but I did notice some new bugs.
I have been using the latest available beta 4.7.0 (266) on my Xiaomi 11 Lite 5g with android 13, security patches 2023-06-01
Issues I ran into:
1.Video feed freezes sometimes. Going back through the menu keeps showing the frozen video feed over the rest of the app. I have to close and reopen the app to resolve this.
2. I started my app with photo mode set to pro. This was my last setting I flown with in the DJI Fly app. I switched it to Auto in dronelink, and created a new orbit from the app. The app would then at the start of the orbit automatically go back to pro (and in my case overexpose the video). The previous version would keep the setting the same (auto).
3. App still crashes approx every 1-2mins even with the new SDK making it very unreliable still for mapping missions.
4. Creating missions manually from the app (function button - orbit, follow, etc) langs/freezes the app sometimes.
Comments
14 comments
I thought the latest was 267, it certainly is on MSDK4 drones and as far as I was aware both SDK's are running the same build #
Hm, strange. I did not receive an update message.
I will update my app and run it again, see if I run into the same issues.
I just did a new test run with 267, and it only crashes once now. I no longer had the frozen screens and the photo mode also did not seem to flip back.
Also seems I had less latency compared to 266.
Its quite windy outside right now, so I may have to wait until tomorrow to try some additional settings.
Hey Danny. Not sure about the other questions but lagging is usually a device performance issue. Only way to compare is to try another more recently released device. I checked the benchmarks on that device and it’s performance is very low. It may work for you but not run the best with DL which is a resources intense app. Just a suggestion.
Updated: Forgot to mention Version 4.7.1 (268) came out yesterday in my TestFlight app. Indicates “corrected several issues causing app crashes”
As I bought the exact same device, I can say that it is not a performance issue.
Right now I unfortunately see no big improvements- as long as te app crashes once on a hyperlapse mission, the result is unusable.
I started testing the Litchi beta and after the second beta update it works simply fine- no crashes or problems with our setup.
You only need to edit the mission on a "non-beta" device or pc and then load it in the beta app and run it there.
I would really be surprised if a Snapdragon 780G would not be enough to handle this app.
But I will install a screen overlay app to check its performance during next test. I doubt that this is related, especially since latency has never been an issue before with DL.
Interesting to read that the Litchi Beta is running stable. This means that the DJI SDK is no longer the cause of the crashes.
The DJI SDK works fine on older versions of Android, or apps that were built to target lower versions of the Android SDK. This is speculation, but it is possible that Litchi started with their existing code-base (which is ancient in software development years) and modified it to work with MSDKv5, leaving the Android API target to some number from the distant past. If so, it is conceivable that they are avoiding the crashes that other apps are experiencing (DL, MapsMadeEasy, etc), but downgrading DL to an ancient version of the Android API is not feasible because of the modern libraries, architectures, and code patterns that would have to be replaced or rewritten - just isn’t going to happen.
Ok Danny. It was just a thought and wasn’t about the crashes. It was regarding the freezing video and or the latency issues you said you were having. It may have been no issue before but possible it may be the type of mission your running. Some will use more resources like a large mapping missions especially if it’s a grid pattern. If it works then great but just pointing out the performance of that device. You can check Geekbench yourself which is a good way to get an idea of which devices are better at processing based on actual benchmarks. I must say I have never been rude to anyone so it wasn’t a jab at the device. DL is a resource intense app as mentioned in their help section. Enjoy…..
@Mike (Arizona Wyldwest) No offence taken, and I hope none was given. I was just surprised as my phone is not "that" old yet :-D
@Jim McAndrew I have no idea about the backend of the application, and I was only assuming - my apologies.
I am very happy with what Dronelink has to offer, and am more than happy to continue testing.
The app does seem to become more stable with every release. As Mike stated previously that 4.7.1 beta is soon to be released. I would be more then happy to see how this makes a difference.
I have created a test mapping, orbit recording and in place hoover with interval photo's and am planning to check for differences at every release.
Understood Danny. 4.7.1 (268) has been available in the Apple TestFlight app already. Not sure about Android but you may want to check the DL link to the APK and see what it is. I believe that device was released in March 2021 so just over two years so you would think it would work well but hard to say. There are soooo many manufacturers of devices which use Android OS and no way of knowing which perform better while using DL. Maybe I missed it but which drone are you using ?
The 268 for MSDK 4 is out, and is good with my Tab7 FE, so I'm sure the version for MSDK5 is on the Dronelink website
I am using the mini 3, with my android 13 phone, so I need to use the beta with my rc-n1 and MSDK 5.
I just installed the new releases 268 and will run a few new tests.
Alright I just completed a new test with the 4.7.1 (268) version.
A simple mapping crashed 4 times. 3x in the beginning (at 10-25% of the mapping mission while taking pictures, and one crash at the last waypoint before landing (I always add a waypoint after mapping in a clear path so I can better track the drone). I had no glitches on the camera anymore this time.
Simple waypoint mission taking photos went perfectly fine, very stable and no crashes. I ran this mission 3 times, all 3 times went great!
A dronie and orbit mission was also succesful without any issues.
What I did encounter was that when I landed in between 2 missions, for some reason my drone did not want to take off anymore with dronelink. It gave the message "unable to take off".
I closed dronelink, confirmed DJI Fly was not active, restarted Dronelink and got the same message.
I closed dronelink and started DJI Fly, and it did not give any error.
I then turned my controller and drone off, closed DJI Fly and did a clean boot:
Start drone, start controller, start dronelink and then it started working again.
Danny. Unable to take-off can be the speed mode switch not in P/ Normal position or possibly not enough satellites. Since it looks like there are plenty of satellites and I’m assuming it was in Normal mode since the other missions ran I’m guessing it’s more then likely the firmware. DL only reports the issue and has no control over it so it’s what I like to call the Technology age and nothing is perfect. Lol…. Shutting down everything like you did and starting it all fresh is the best way to correct the problem. If it does happen again you can try to take-off manually and let it hover then start the mission and see if it will run from there since the problem is with take-of command. Any mission can be ran without starting it from the ground as long as it is within the reference pin area. If it happened once I would not worry about it. Hope this helps. Enjoy…
This is an old posting but still applies.
https://support.dronelink.com/hc/en-us/community/posts/4403276271379-Unable-to-take-off
Please sign in to leave a comment.