This is my 3rd Phantom 4 from Best Buy now....the last one had an issue with the phone/tablet holder, now this brand new 3rd Phantom 4 is doing exactly what the first one did: It will not hover. The first time I powered it up after updatng firmware it kept saying No GPS, so I rebooted it and GPS didn't switch to No GPS so I took it out in front yard...Took off and went to about 6 feet in the air, and then it did exactly what the 1st one started to do 2nd week into using it. It will not hover. Hovered at 6 feet for about 1 second then sank to the ground while DJI Go was saying it was still at 6 feet. IMU is calibrated, compass....did't switch to NO GPS, just wont hover. The craft firmware is v01.02.0503, the DJI app says 3.0.1 for App, where the Version field is there is nothing it is blank, RC is 1.8.0....Please help I don't want to have to return my 3rd Phantom to Best Buy and say I want my money back.

After update did you do all the calibrations, if not then that would be a good place to start ?

Specifically the sensor calibration using DJI Assistant 2.

Aardvark Posted at 2016-11-4 17:41
After update did you do all the calibrations, if not then that would be a good place to start ?

yes I calibrated IMU and compass.

fansb1fe1104 Posted at 2016-11-4 21:42
yes I calibrated IMU and compass.

OK Calibrated the sensors using DJI Assistant 2, those are what lock its position in low level hover (below 30 feet).

Aardvark Posted at 2016-11-4 17:44
OK Calibrated the sensors using DJI Assistant 2, those are what lock its position in low level hov ...

My 1st Phantom 4 flew perfectly for about a week, then after a firmware update it started this problem. DJI told me to calibrate sensors, did it about 20 times, each time it said it had passed, but it wouldn't hover....So seeing that calibrating sensors did absolutely nothing for the 1st one I'm thinking how is it gonna help on this one with exact same problem....I'm starting to think its a firmware bug or something.

fansb1fe1104 Posted at 2016-11-4 17:48
My 1st Phantom 4 flew perfectly for about a week, then after a firmware update it started this pro ...

but maybe this one will calibrate and be fine, like most are.

worth the effort anyhow!

good luck!

kirk2579@aol.co Posted at 2016-11-4 17:59
but maybe this one will calibrate and be fine, like most are.

worth the effort anyhow!

I will try it on this one too and see what happens, not getting my hopes up this time though.

Just to get the obvious things out of the way, is the VPS  turned on in the settings?
Its not set to atti mode is it?
Also you said   "so I took it out in front yard" you didnt try calibration of compass inside did you?
Edited to add:
Hmmmm, wonder if BB gave you back the same drone you had first

fansf91a8d14 Posted at 2016-11-5 09:20
Just to get the obvious things out of the way, is the VPS  turned on in the settings?
Its not set to ...

Also, it is normal to show 'No GPS' while in a house, most GPS reception devices do not work indoors.

kirk2579@aol.co Posted at 2016-11-4 17:59
but maybe this one will calibrate and be fine, like most are.

worth the effort anyhow!

Exactly as I thought would happen...Sensor calibration completed, but it still won't hover, it sinks right back down to ground again.

fansb1fe1104 Posted at 2016-11-5 06:27
Exactly as I thought would happen...Sensor calibration completed, but it still won't hover, it sin ...

Have you already tried a factory reset through the Assistant 2 software? Do you have any brackets underneath the unit that could be blocking the sensors below? Could you happen to provide a short video of how it behaves?

fansb1fe1104 Posted at 2016-11-4 22:27
Exactly as I thought would happen...Sensor calibration completed, but it still won't hover, it sin ...

Are the VPS sensors turned on in DJI Go settings ?

Under 'Visual Navigation Settings' menu, 'Enable Visual Positioning' should be on when all is connected and powered up.

How long does it take to drop to ground ?

fansf91a8d14 Posted at 2016-11-4 18:20
Just to get the obvious things out of the way, is the VPS  turned on in the settings?
Its not set to ...

Yes the VPS is turned on, compass was calibrated outside, says GPS ready to go with green on  I sent my flight records to DJI, hopefully they can figure out a solution this time.

DJI-Jamie Posted at 2016-11-4 18:36
Have you already tried a factory reset through the Assistant 2 software? Do you have any brackets  ...

I tried a factory reset on the 1st Phantom 4 that I had the exact same problem with on the new one but it did not help. This video is  from the first Phantom with the exact same problem as on the new one.

Aardvark Posted at 2016-11-4 18:38
Are the VPS sensors turned on in DJI Go settings ?

Under 'Visual Navigation Settings' menu, 'Enabl ...

at about 6 feet off the ground it was on the ground in a few seconds....but still saying it was at a height of 6 feet

Have you got the props attached? ;)

Controller calibration too. Very very odd that you've had two with the same issue, maybe the comment about bb giving you there same one back is right.

calls4u2 Posted at 2016-11-4 22:10
Controller calibration too. Very very odd that you've had two with the same issue, maybe the comment ...

I had tried remote calibration and re-linking it.....tried pretty much everything that can be done, I heard back from DJI and they said "We are sorry to hear about the issue with your DJI Product. We recommend sending your product into our North American Support center, for diagnosis and repair"


Ummm nope going right back to Best Buy and  mostly likely get a full refund instead of exchanging it for a 4th one that probably won't work.

calls4u2 Posted at 2016-11-4 22:10
Controller calibration too. Very very odd that you've had two with the same issue, maybe the comment ...

The Customer Service person said to another employee to go put this in the defective place or something like that when I was exchanging it the first time. The 2nd one and the 3rd one were both pulled out of their locked case on the floor. Both of them were unopened boxes, and both said it needed update on firmware, so unless they somehow in one day set it back to factory on the firmware and then put it in a box with everything else brand new, then I doubt it was the same one.  When I was exchanging for the 3rd one today, there was another person who came in wanting to exchange theirs because it had a battery issue. That's when customer service rep said "maybe we got a bad batch" . How a whole bunch of defective ones would come in on one shipment to best buy seems pretty Ludacris, unless the whole batch was not made right at the factory and DJI has very poor quality control. If I exchange this one it will now be the 4th one in 3 days...Do I wait until best buy gets a new "batch" in or just get my money back?

fansb1fe1104 Posted at 2016-11-5 10:20
I had tried remote calibration and re-linking it.....tried pretty much everything that can be done ...

Could you happen to provide the ticket number from your correspondence with the Support team?

DJI-Jamie Posted at 2016-11-5 16:22
Could you happen to provide the ticket number from your correspondence with the Support team?

I didn't even bother with ticket number...I was just about to give up and return to best buy and get my money back....But since I really like the Phantom 4 when it works properly, I decided to try once more...I had been advised to do factory reset both times, but what nobody ever suggested was downgrading the firmware instead of factory reset, so after downgrading and then relinking my RC I took it out to try flying (ready to be let down once again) But no holy crap it is actually flying perfectly again. Have flown twice today both times it said I needed a firmware update, so I just pressed cancel on that and now both times its flying as I hoped it should. So glad I didn't take DJI's advice to send it to them.

Did you try a firmware refresh/factory reset and it didn't work ?

Aardvark Posted at 2016-11-5 18:30
Did you try a firmware refresh/factory reset and it didn't work ?

Yes I had originally refreshed the latest firmware that didn't work so tried the factory reset, neither worked, seems downgrading the firmware is what fixed it.