Moving beyond what I think we all agree regarding GEO, I'll put my horns on.
My P4P is what some of you who seemingly don't understand the firmware would call "hacked". In fact, it is no more "hacked" than adjusting the amount of breaking in the GO 4 app. I made the change, (it's called a parameter) in the DJI Assistant software before DJI figured out that we could do that.
Many are too fearful to take this step for mostly reasons that don't hold up for me, but everyone has to decide for themselves. I'll leave you with a couple of points to ponder. Although I know for many it's easier just to go with the flow. I do get that.
1. DJI makes it absolutely clear that the operator of their equipment is solely responsible for how it's used.
2. Even if DJI didn't make this clear, the operator would still be solely responsible for it's use. Unless, there was a defect in the hardware of software that DJI negligently knew about but ignored.
3. The firmware, that some hold up as the holy grail not to be messed with, is not certified to any standard. NO ONE, not even DJI, states that it is perfect. If fact many versions have come and gone with serious flaws. But I degrees.
4. Joe Ernster, who is our local insurance expert, has stated that "modification" of the firmware beyond what DJI "wants" has never even been a question in a claim.
Somewhere along the line, folks got it into their head that DJI is some sort of authority of right and wrong. That's simply not true. In fact, because of the "hacking community" it was discovered that DJI was illegally using Open Source software toolkits without abiding by the licensing. For those of you that have been RCing for a long time, I find it incredibly difficult to understand how you got to this point, but whatever. If you have programmed numerous flight controllers over the years, how do you all of a sudden think that changing a parameter in DJI's flight controller is somehow bad or illegal? You own the equipment and you're not rewriting the code, you're just changing a value in the existing code. You're not changing any flight algorithms or anything, lol !
I've seen the same people that would change a value in their digital camera's firmware in order to open up RAW settings balk at changing a value in their drone's firmware to allow them to take off in an area that DJI said they can't. I don't get it.
IF the FAA tells me that DJI is the authority and whatever they say goes, then I will not touch the firmware.
IF my insurance company tells me that DJI is the authority and their parameter settings cannot be changed by the user, then I will not touch the FW.
IF there is a legal precedent set that if the owner of the equipment changes a FW parameter then no matter the cause of an incident they well be held negligent, then I will not touch the FW.
I think it will be a long time with FW far more vetted than DJI's current FW before any of the about comes to pass. But I'll be watching.
Ok, horns put away now!