Beta 4.6.0 keeps crashing on Samsung S22 Ultra and Tab S8 Ultra
Hi, firstly I am loving the overall product and the planning elements on my desktop are brilliant and easy to use.
I have had a few issues both prior to flying and during flying when it comes to using my phone/tablet.
Firstly, without flying, i can typically view a saved plan, but when i come to edit it, the app will crash and needs to restart manually, sometimes i get a message saying after crash try clearing cache, I've tried clearing, and also tried not clearing. Continues to happen, there is no pattern.
Then today I went to do my first flight with it, a small project requiring about 388 photos using the standard grid map. Flying conditions were ideal, no wind, clear skies, excellent gps lock. I used the tablet first, connected ok, mission started perfectly, and drone took off, clibmed to correct altitude and made its way to the first map point, it took about 7 photos (roughly the point at which it needed to turn back on itself), then app would crash and UI drops out. The drone stayed stilll but when i relauched the app, the display was showing it was on manual flight mode. I had to reload the mission and it told me that a mission was in progress but there was no option to resume, so had to cancel and restart, It did this exactly the same 2 more times, then i switched to my phone, and exactly the same thing happened, at same point.
There is no geological or mechanical assets at this site, nothing that could interfere, was flying at 60m so well within range.
Having read some reviews Im assuming that since the S21 was known to be buggy, it may be a continuation from that?
Have looked for some crash logs but cant find any.
Any help please?
Comments
8 comments
Funnily enough ive tested it (without flight) on an older Samsung A70 and doesnt crash, so will try flying it with the a70 and report back. Forgot to say above, the drone is DJI Mini 3 Pro
Hi Jonathan. Are you using the current version build, (259). If not always keep version up to date especially with Beta as it is always evolving. Regarding the app crashing. You may need to force close the app before trying again. It may have still been running in background. Once forced closed go to your missions tab and select that mission which will indicate with a blue color and select to complete it. Any mission which was partially flown can be resumed at a later time or day so you don’t need to redo the entire mission. Great feature. If app keeps having issues closing then it may be the deceive and DL may need to see what they can do.
Hi yes it's built 259.
I've just got back from testing it in field with the A70 and it worked much better, got to 49% before it crashed, but as you say, I was able to resume missing, to be fair I didn't know where that option was when first happened with S22 but still with s22 it kept crashing at about 2%. So definitely got further with a70.
With the a70 it did crash twice but much later on and I was able to resume both times, however it needed to autoland to swap battery and I couldn't get it to take off again, said unable to take off.m, and Sat's locks dropped to between 2 and 3, so I'm assuming it was crashing because of poor gps, and then wouldn't launch again.
But the s22 is absolutely more buggy
Glad to know its not just me, I fear the S22 and Tab S8 will be a nonstarter given the issues with the S21 etc.
In my case, i know from the UAV forecast that at that time of day the sat lock would drop to poor, but i just needed to check to see if A70 worked better and it did. I will probably have to restart the entire mission because when i go back the light will be very different.
Also assuming the poor GPS caused the crashes, because when it RTH for fresh battery it was at least 2m off the landing pad!
The ability to resume a mission is fantastic. I’ve tested several times a long time ago just to see how it worked a day later and no issues. At least if there is an issue you can go back another day or at a time when it’s convenient once you got it working and finish. Unfortunately with Beta it’s trial and error. That’s why it is important to post problems so DL can get it fixed which overall they do an amazing job. As far as Satellites, if you have enough it will work and it should have nothing to do with the app crashes. Losing 2 or 3 won’t make a difference as long as you have enough like 10 or more. You may try powering off drone only again and then power back on to see if it will work. Sometimes just cycling the drone off and then on again may work. Battery swaps usually work without issues but if it does not resume then just exit plan and then go to the mission tab and resume the mission from there. Enjoy
Probably an incorrect assumption. The reason why it works better on the A70 is probably because it is running an older version of Android which is closer to the version that the DJI Remote Controller run, which is what MSDKv5 was designed for:
https://support.dronelink.com/hc/en-us/community/posts/16409496589331/comments/16410305783571
I'm having very similar issues with an Asus Zenfone 8 and android 13 on mini 3 pro. To fly a 25 minutes mission I'll need to restart the mission 12 or 15 times and require 2 batteries.
I could not find a way to get logs or some crash report and share somewhere with the developers.
I'm also wondering if there is any way to make sure the checkpoints to resume mission are fairly close sometimes i need to fly back a long way to resume mission.
Definitely helped using an android.11 device
Please sign in to leave a comment.