Im in the same boat about not wanting to send it out. I did some tests today, after reading others peoples suggestions but I'm SOL and have had it happen repeatedly on single battery.
Note the following, problem started around the time of firmware .550
- would only happen on rare occasion (i.e once ever 3-4 batteries).
- It has slowly gotten progressively worse (happening many times each battery now)
After reading others similar problem I decided to take to my testing field and see if I could trigger the issue and or remove it. I went out and purchased a fresh x1000 Lexar 32G SD card to rule out the slower sandisk ones I had been using.
New card, ran a Format using the DJI Go 4. (iPad version).
I Turned on Mavic, checked for updates, did a camera settings reset and did some flying. All seemed well first 15 minutes, and thought the camera reset did the trick, but then... tilt.. camera goes into reset cycle we all know about.
So, now ruling out the possible SD issue, and camera reset, I tried to see what might be a trigger for it, I tried several different resolutions, 4k 24/30 and 2.7 and did some more flying checking now for video length recording etc (after 5 mins? after 10?) I had some people note file size may been issue, but for me, this did not seem to be an issue.
On the events it happens, it returned the camera to a 4k setting, even though it was on a 2.7k etc (though funny enough, when I did a camera setting reset it defaults to 2.7k)
I was able to reproduce the gimbal reset several times when I did a small POI circle. While holding down the right throttle to increase speed in a anti-clockwise direction seemed to make it reset more frequently than clockwise direction. (It would happen in under 2 mins vs not seem to want to happen after 5).
I did notice as it resets the controller came up with "SD ERR" - all the settings off the camera switch to NA while it resets and restores. I managed to record the controller during several events so I could see if any other notifications came up, but thought I would post this for others if it helps ID the issue if it is in fact a bug with the firmware.
One thing is sure, Its getting a lot worse, so maybe it really is a fault in hardware/cable as previously mentioned. So I am left but to send it back