I too have experienced the same problem. Before I go farther, I have done everything usually suggested...calibration, factory restore, DJIAssitant reload of firmware, with app alone (no remote), with remote alone (no app), etc.
Mine will track to about 8-9 meters using the proximity sensors (showing the sensor icon next to the altitude), and then, as the Spark rises, the app display will flicker back and forth between the real(?) altitude (without the proximity icon) and something like 8.5 meters (with the proximity icon). I noticed a couple behaviors that this results in...
- Like others, I can release the sticks and the Spark will continue to rise a the same rate for quite a while
- Conversely, the Spark will drop like a rock (possibly faster than it would with the stick all the way down, before the problem) when descending and releasing the sticks.
- At first, I thought the flight log showed the correct altitude, but then realized there was something fishy. It seems to only record altitude from the barometer, and doesn't show the proximity sensor altitude. I had one flight were the "flickering" between altitude sensors stopped at a fairly high altitude, showing only the proximity sensor at 8.5 meter, until it got close to landing. The last barometer reading was at 18 meters. The flight log showed I never went below 18 meters until landing. TO be clear, I took off and landed in the exact same spot.
I'm torn at what is causing this, as it seems better on some flights, and terrible on others. If I were to guess, I would say it is one of two things.
- The barometer chip/sensor is failing and the proximity sensor is basically used and reports it's max detection range (8 meters?)
- The proximity sensors are reporting something (falsely) that overrides the barometer reading
I did put a call in to DJI and they said to send it in, but I'm a curious person and really want to see if there is a solution without sending it in. This would save me, and possibly others, unnecessary time away from their favorite toy...errr...I mean drone.
BanditX2:
Can you confirm the Go4 App has definitely resolved the issue? I ask, because I've had a few (nearly) flawless flights (with regard to reported altitude), but many wacky ones before and after. I've also flown the drone with the remote only (visually, no app in the mix) and see the same "keeps ascending" behavior.
If it truly solved the problem, how did you "roll back"?