Recent content by simcab

I had the same bad experience twice. The first one I overcomed, the second one I was near to landing and the stick range was insufficient to compensate, no time to switch "p" I try landing but a soft impact toward a wall was inevitable! No damage, but WHY?

Light was pretty good and the collision with the wall was almost frontal. At the same angle the drone refused to go at 1 meter!

Today some of very strange and bad happened. I was in a narrow street with poor or none gps signal in tripod mode. I was 1 meter height hovering, looking for the best surface for landing (after flying smoothly). The M2P suddenly started drifting toward a wall, tripod mode was insufficient to...

This way they would disrupt the mavic pro market.

The main purpose of manual atti is to recover a fly away...

I'm afraid that when you hit pause the mavic attempts to hover in place, but if the (two) compass(es) are both wrong by more than 90... and you are in gps mode.... you have a fly away IN PAUSE!

When I update I blow to the bell of the AC to keep it a bit cooler elsewhere sometime the update fails.

Pay attention: precision landing is aitomatically enabled if vision is active AND you takeoff vertically for 10 meters or so.

I had 2 "app disconnected" experiences in 120 flights. Both times I recovered using the RC. In my opinion the guilty was the saturation of 2 gigabytes of the app video cache. What do you think?

If you take videos a copy is left on the mass storage of the cellphone or tablet. You need storage space for this.

I experienced an updating stuck (86%), the RC was really hot. I restarted the update blowing in the RC cooling grid. The update was ok. I do not know if this is only a coincidence.

Of course the specific device can be critical, I have a Galaxy S5

I had several app crashes (nearly 1/flight) but now I am happy!! No crash in 30 flights. Recipe: - close all applications - verify 2GBytes system space free - airplane mode

Are you sure that you do not have storage or memory issues? It seems to me (in my case) that the problem is related to storage occupation >90%

Which Android do you have? Do you have USB debug active?