It seems a production batch version had these issues. Glad to hear yours was resolved.I had the same issue. Completely resolved by getting a replacement from DJI
64GB model?I had the same issue. Completely resolved by getting a replacement from DJI
Well, there goes the theory that it is only the 64 GB versions. So far then, it seems like the Canadian DJI sourced ones are immune, such as the Adorama units in the U.S. and those bought in Canada.Nope. Creator combo.
Since I see you are in California, did you purchase from the DJI Canada web site and have it delivered to a Canadian address?Unfortunately mine was a non-creator combo one purchased in Canada as well, and it suffered from the obstacle avoidance issue. I've since sent it back to DJI for replacement.
Well, then maybe just the Creator Combos from DJI Canada are immune. The field of immunity keeps narrowing!Unfortunately mine was a non-creator combo one purchased in Canada as well, and it suffered from the obstacle avoidance issue. I've since sent it back to DJI for replacement.
I have the same issue with my Mavic 4 Pro Creator Combo. The drone was manufactured on 04/2025 and was bought from the DJI EU store. Currently I have an open case with the support and sent over 5GB of log data to them.I had the same issue. Completely resolved by getting a replacement from DJI
This worked for me!An update to my case, in case it might be helpful to anyone.
After contacting dji support, they suggested to send the unit back to them for inspection.
Before doing so, I thought to try one more time to self-calibrate the sensors.
DJI support suggested that I should perform a low-flight altitude on an area with obstacles and particular something above the aircraft, flying the aircraft on four directions for 2-3 minutes. This did not help at all as it kept detecting false obstacles.
What DID help and fixed the issue was this:
I went to an open area without obstacles (an empty football field) and performed a low altitude flight (2-3m over the ground), flying the Mavic 4 Pro in a cross-like pattern front/back/left/right with obstacle avoidance set to off (not bypass nor brake). The flight was less than 5 minutes (3-4 minutes) and after performing the cross-like flight pattern, I've landed and powered off the aircraft.
This was done 3 times in sequence.
After that, the sensors no longer detect false obstacles, the drone flights fine with either bypass or brake obstacle avoidance action and I can perform automated flights (Mastershots, Waypoints, etc) without issues on the same areas that previously was not possible (in these same areas, the Mavic 3 can do them without issues).
In any case, that's what I did and now the aircraft is working perfectly.
Hope this helps someone.
View attachment 184264
I had the same issue on the first two flights. I then flew random patterns at about 15' for ten minutes and the problem resolved. I don't think there's anything significant about the flight path or speed; the drone just needs a little flight time at low altitude to calibrate itself.Today, I am happily writing right after repeating Frontier’s procedure on a soccer field, with some trees at the boundaries, flying at 4 meters high and doing 4 repetitions of his patterns. It worked like a charm! Now it is flying OK with OA on.
Apparently the drone learns by itself, and I think that flying carefully in N mode and with OA set to off helps to feed its OA algorithm.
So:This worked for me!
I have had Mini 4 Pro and Mavic 3 Pro and never had these issues of false obstacles detections, as I was getting frustrated with this problem with my Mavic 4 Pro (non creator combo).
I bought it yesterday, experienced the problem, came to this forum and updated the firmware using DJI Assistant 2. (I have it already on 0200, but the software allowed me to install new firmware)
Today, I am happily writing right after repeating Frontier’s procedure on a soccer field, with some trees at the boundaries, flying at 4 meters high and doing 4 repetitions of his patterns. It worked like a charm! Now it is flying OK with OA on.
Apparently the drone learns by itself, and I think that flying carefully in N mode and with OA set to off helps to feed its OA algorithm.
Thanks again Frontier and all the people who have shared their experience on this forum!
Yes. That is the way it worked for me. I did not use S mode because on that mode you do not get the yellow or red warnings from OA.So:
In N mode, with anti-obstacle sensors active, and brake on off.
Interesting.
What speed did you keep? Thank you
Have you calibrated the drone? May resolve your issues.I'm plagued with this issue as well.
I just received my brand new Mavic 4 Pro Creator Combo into the USA from South Korea. Manufacture date 08/2025. And it says its a (KR) model, so I assume Korean.
(Stock it was on firmware .100, the issue occured and I updated it to .200 which did not help)
Figured I'd share some videos of the issue so people can see and compare with their own situations.
Here I am flying the drone steady, full stick to the right, ~150ft up, and the obstacle avoidance braking is just constantly firing and you can see the drone stop and start. Behind the wind noise you can hear the sensor beep.
Here are some other situations where you can see the controller screen. Again, steady movement, and way above any obstacles, but the sensors are going ballistic.
I tried some flying around in a park as advised, which potentially has stopped the issue from occurring when I fly to the left, but currently still happens when I fly to the right. Front and back have no issue.
I'll do some more tests to try and "train" the sensors, and report back if I have any success.
It's a known issue that's been resolved by many folks by flying the drone low to the ground for several minutes. Apparently, the OA system needs to train itself in order to work properly. It sounds like the OP has partially resolved the problem by doing that. Another flight may well finish the job.Have you calibrated the drone? May resolve your issues.
I'd do it all although start with compass. I had zero issues with my Mavic 4 Pro from the onset, close to the ground, high up, any height for the matter; perhaps I have one from a different production batch, from initial release however I'm purely speculating. Then again there have been several firmware updates, mine is updated to the latest and still fine.It's a known issue that's been resolved by many folks by flying the drone low to the ground for several minutes. Apparently, the OA system needs to train itself in order to work properly. It sounds like the OP has partially resolved the problem by doing that. Another flight may well finish the job.
What calibration might address an OA issue? Not the IMU, compass, gimbal, or controller calibration.
We use essential cookies to make this site work, and optional cookies to enhance your experience.