Thanks for all the additional info.
First let me repeat any info from previous posts in a single central post (since many of you are asking for specific parameters, etc), and make sure I didn’t miss any:
First general info:
- All flights done on Mavic Pro Firmware v01.03.0600 released April 11th
- All flights done with Android Device (Nexus 6P Running Android 7.1.2)
- I’ve done many flights with DJI Go 4 successfully, no issues there, drone behaves beautifully on Android device
- Drone Deploy app was latest version before flight #1, and there was an update on the android app before Flight 2, and I did install that update to Drone Deploy before that flight.
- I’m using a Kingston Digital 64GB microSDXC UHS-I Speed Class 3 card (U3 / V30 speed, benchmarked at nearly the advertised 90MB/s read speed, and 80MB/s write speed, this is far superior to the “standard class 10” listed commonly.) It shoots burst mode photos VERY fast, in full res, and can shoot 4K without any issues. The SD model choice is definitely not the cause of the issue.
- SD Card was formatted (by the mavic) before each flight using the DJI Go 4 app.
- For the record this is not a complaint about the mavic specifically. That’s just the drone I fly. It’s specifically an issue I’m only experiencing with the DroneDeploy app, when used on my mavic. The camera/gimbal, all work great. Drone performs like a champ, etc.
First flight (the one that prompted me to post this thread): Flight covered 9 Acres, was setup with 80% frontlap, and 80% sidelap, at 200 foot altitude. With “max speed” set to 25Mph (though it never made it this fast during the capture). And camera settings set to Auto. This one seemed to work, sidelap (course) seemed correct, but frontlap (frequency of shots) seemed to be about half (or less) than what it should be. As indicated in the image of my flight path I posted. This seems to correlate with the recent example posted by syamaphantom (thanks for a second example!). RTH was aweful as well, on RTH it was far from the home point, almost landed in some trees, had to manually take control with mode switch, and land safely.
Then the second flight attempt, done on reduced area, reduced to 3 Acres (just to get test done quick), still 200 feet altitude, increased Sidelap to 85% and frontlap to 95%. Speed the same, And I changed the camera to “Manual”. Before flight I opened up the DJI Go4 app, flew up to 200 feet, setup camera, verified by taking a bunch of rapid pics in succession. Worked fine, so I landed, and switched to Drone Deploy app, loaded new mission and took off. This time it took no pics… I waited several seconds, it didn’t take any. So out of curiosity, I pressed the camera shutter button on the RC, and it took a pic. Thought “maybe that would kickstart it” but it didn’t, several more secs go by with nothing. So took several pics rapidly using the shutter button manually (at the frequency I thought seemed reasonable) and they worked fine. But the app didn’t “auto-take” any pics. RTH was still bad, again WAY off, had to manually land (at least this time I was prepared for it).
Third flight, I recreated the same flight plan in Pix4D, 3 Acre area, 200 feet altitude, 80% sidelap and 80% frontlap. And similar speed limit. Also set to manual camera settings. Launched the mission with their app, and it took off and immediately began flying the course, and taking frequent photos (more along the lines of what I would expect, with the 80% overlap settings, a given feature was in at least 3-4 photos in each direction). It finished, and as a nice bonus it’s RTH actually landed successfully in the right spot, without requiring manual intervention.
Some other notes:
- I’ve flown several missions, never had an issue with it recording photos or video, also never had any real issues on Android other than the well known “force quit other apps before switching” issue. Which I’m well aware of, and did every time here. If you don’t do this, it simply will not connect.
- I’ve use Lichi a bunch too, and was able to do successful orbit missions, and pano shots with Lichi automating picture taking without any issues at all on same drone, same card.
I’m not saying that the software doesn’t work at all, that’s clearly not the case, many others are using it very successfully. However I am actually an experienced software developer, and computer engineer. I’m well aware of the fact that wierd bugs can creep into a system as a result of a combination of unexpected conditions/circumstances/variables. So I suspect this is what’s going on, perhaps it’s the combo of the Android version of the app, with the latest Mavic firmware, causing the problem? Perhaps it’s something wonky on my account? etc. Anyway, that’s why I’m looking into suggestions, and hopefully helping DD debug their software. BUT I can say that through process of elimination, out of 2 mapping apps tried (DD, and Pix4D) and 2 other control apps tried. (4 apps total) ALL 3 of the other apps had zero issues, capture photos just fine, and ONLY DD appears affected. This leads me to believe that while the issue may not be 100% the software, it at least involves some bug in the software, which is being brought to the surface by other factors.
This is re-enforced by the fact that the HUD display doesn’t even show the images being captured on the mavic (which other users have reported as a specific issue to the mavic) and the fact that it appears unstable (sometimes it simply won’t capture photos). I have no doubt it may be “more” stable on Apple, but that isn’t a testament that the app is fine, it’s simply a validation that the android version of the app needs further work for improved stability. If you only want to support Apple, don’t bother releasing an Android version. I’m a pure Android user, I have no intention of using an apple device. I’m well aware of the quirks, and I’m also well aware of how to work around 99% of them, so it doesn’t bother me. If the result is that I have to use another app which is proving more stable on Android, I’m happy to do that. But I’d like to try to figure the problem out (as it’s in my nature) and I hopefully can help DD in the process to improve their app.
As for the suggestions in the last several posts:
- Don’t intend to downgrade the firmware to test. Again other apps work great for this same task, only DD app is affected. Well aware that 0500 and 0550 version firmwares had major issues with API apps, and 0600 corrected them.
- I have reset calibration on both IMU and Compass to test. This was done about 1 week prior to the first flight, and after the suggestion to re-calibrate, I did it before the second flight.
- Camera settings in Go4 App are set to manual, with manual wb, and exposure. I set it up in Go4 ahead of time, verified it was good, then exited (And force quit) go4 app and launched DD, in the flight plan, it’s setup to NOT use automatic settings.
- Thank you for the offer for the iphone to test, that’s extremely generous. However as I said I’m a pretty purist Android user, and I’d rather “figure out the root cause” with Android, rather than just resign myself to using apple as it’s more stable (just my nature lol)
- chasemgray: I will try to create a new account, and attempt another mission this weekend if I get time. Will let you know how that goes. That said this is a fresh account, with no extra plugins enabled, or fancy settings changed. It’s pretty much “out of the box”. Either way, I agree, something could be corrupt, so I’ll test that and let you know.
I think the pics in most recent post by Syamaphantom are pretty clear, same flight, same app, same drone, same location, one has frequent photos, one does not. That’s pretty blatant indicator of some underlying problem (even if it’s an obscure bug that’s only triggering on 1% of users or something due to uncommon combination of factors)
Thanks again for all your suggestions/feedback
hopefully we can dig to the bottom of this.