Recent content by zbooy

I've got the same problem with my Samsung A53, both on Android 12 and after the upgrade to v13. I believe it's a long-standing DJI Fly bug.

Sorry mate, you got the wrong one :-D This is Kościuszko Mound, not Krak's (which you can see on the attached photo). Yeah, we got at least four of them over here in Kraków :-D

I believe I had an incident like this about a year ago with a Mini 2 (the same controller!). It was scary but after landing and turning everything off and on again the problem never came back.

Nope, it's the build number (as the previous one was 1386).

I have just done some flying and 1410 seems stable enough. And the compass works just fine :)

I have just noticed that an updated APK is available for download at the usual location. Hopefully it fixes the compass indicator bug from 1386.

Yup, it's the same with my Mini 2.

Here you are: fc_log.zip Let us all know if it is useful for anything.

I have noticed that the DJI Fly got more sluggish and lagging after the last upgrade. (I'm flying the Mini 2, BTW.) When checking the SD card after a maybe 15-minute flight I found 2 large log files in the /Misc subdir: fc_log.log 512 MB camera_log.log 100 MB The card was freshly formatted just...

You get small changes in status display at the bottom of the screen; it now shows white balance in K.

I just turn the Mini 2 around manually, use the M camera mode, convert DNGs to 16-bit TIFFs and stitch them in PTGui Pro,

Because the panorama is stitched by the app, not the drone. BTW, the DJI Fly app uses only quarter-resolution (2000x1500 px) images, so you are much better off grabbing original DNGs and stitching them yourself.

I have had it happen to me a few times. Now I just don't bother with the automatic mode and just shoot a sphere manually.

Mine is about 1400 grams.