OK, let me try to explain what I did today.
1. FW is 1.3.20+
2. DJI Go app ver 3.1.23 - can't roll it back because that resource file thing.
3. Starded FakeGPSapp with MOCK location enabled - somewhere in the US of A
5. Allowed DJIGo app to find location through my phone GPS
6. Turned ON RC
7. Linked my phone to RC and started DJIGo app. In camera mode, map location was exactly how I put it in FakeGPS app (if DJIGo app is not allowed to find location, it will locate itself to last remembered location, or no location at all - no map background, so it HAS TO BE allowed at this time).
8. Turned ON my copter (with aluminum foil covered GPS antenna). As soon as connection to RC was established, system warned me that region has changed and it will switch WiFi settings accordingly. NOTE: it was considered as RC-Drone WiFi setting, not RC-phone one. It was obvious because WiFi link RC-phone was never interrupted (fact). At that point I changed DJI location setting to "ASK".
9. Finally I had 27 dBm output power (FCC mode). It was so obvious - even through the walls of my house it was clearly noticeable change.
But... (there is always some BUT around
)
10. As soon as drone picked up position through his own GPS, new home point was prompted (even my FakeGPS app was still running) and map jumped to my real location. Few second after, system recognized new region and demanded WiFi change (no Cancel option, just OK). At that point, what ever I do it was not possible to convince that sucker he is wrong.
I didn't try to take off before that message (rainy day), maybe it wouldn't popup while flying (security reasons?). But anyway, it is a short time window to take off (not more that 10 sec).
I think there is nothing we can do on DJIGo app side except specific instruction to drone software to ignore mode change (something like .DJI.configs files made for ForceFCC and 32ch extension). But those config files don't work for P3SE unfortunately.
Maybe to downgrade to previous FW version (the very first one?).
