EdisonW1979
First Officer
Flight distance : 1535679 ft
Canada
Offline
|
hallmark007 Posted at 2018-7-7 11:50
https://forum.dji.com/forum.php?mod=redirect&goto=findpost&ptid=139147&pid=1386009&fromuid=260008
I refer you to this post, and when you read it go down and read your next post, you clearly say this is a 0400 problem, yet if you read this thread you will realize that this problem has been reported long before 0400 and so this problem would have to go down as an inherent problem. Yes it affected you in 0400, but from you have been saying and continuing to say it would make no sense to return to a bad FW IE 0300 as you are continually saying here that bad FW can show up at any time. So I would have thought you would have realized this. But you seem to want your cake and eat it.
Pal,
There have been COUNTLESS others here who have posted with issues, reporting problems relating to BOTH the 0400 MA firmware and the GO 4 app with builds started at 4.2.14 onwards.
I've also now seen videos posted by pilots disproving your FUD, and your "knowledge" is heavily in question.
There have also been other IT people chime in to confirm that bunk firmware can manifest problems only with certain MA's due to manufacturing differences from different component supply vendors, a fact you casually love to ignore.
You blowing your idiot trumpet insinuating that the problems don't re-occur after re-flashing the FW via DJI Assistant 2 1.2.4 is another slap in the face to owners who have done so, and after a few flights, have re-experienced the problems, which also goes to show you have no clue what you're talking about.
For the pilots for whom that process worked, and stuck, I say congratulations and happy safe flying, and enjoy your MA!
For those who DO HAVE CONTINUED PROBLEMS, stop trying to put us down as if we don't know what we're talking about, especially those who live and breathe IT and know a LOT more about electronic equipment and software troubleshooting than someone like you who just pretends to know anything.
You've been exposed here MANY times over the last few weeks as someone who will casually puts down owners because it suits your fancy, not giving any respect to their issues, which are not made up or imaginary, which I find monumentally disrespectful.
And just to prove a point... In the world of software development, a few lines of code could've been written into the MA FW dating back to 0200 that could've caused similar issues as we're experiencing now with 0400, but only manifested itself on a tiny fraction on units. Now, as more code got written and/or changed with 0300 and later 0400, that original problem can get multiplied dramatically, hence why the significant uptick in issues in 0400 that were previously experienced by only a small percentage of owners using in earlier builds of the firmware.
So yes, 0400 IS a cause of the problems, even if the bad code was already present in 0200, and later brought to the surface much more due to code changes and inadvertent mistakes made by the DJI developers.
And BTW, I "rubbished" the 0400 FW for the MP/MPP because DJI again tried to pull the "cannot downgrade" card. However if you'll note in the thread where I posted that, I retracted that statement, as it would appear, for now, DJI is still allowing pilots to downgrade if necessary, and thus far, 0400 on the MP/MPP is working splendidly, so there doesn't seem to be a need to downgrade.
It is always wise to hold off on upgrading to new FW on any electronic product to see what issues manifest themselves after launching to the public, so this, coupled with the fact their change log was against very skimpy on details, prompted a cautionary warning, which, again, I retracted publicly. Might want to double-check before you try and smear someone before checking if anything has since changed. |
|