hey guys, did anybody tryed with this?
howto:dji_configs [dji.retroroms.info]
I've heard that they've disabled configs in the newer versions of the firmware.
First, a bit of a backstory. I own an older Android device which doesn't support 5ghz wifi and an iOS device (iPad 4 3g, old model aswell) but it supports both 2.4ghz and 5ghz wifi.
On the Android device I was only able to use the 5ghz connection between the aircraft and the remote control since the phone had to be connected via the 2.4ghz frequency. With 5ghz on CE mode my range was limited to about 200m. There are some users which have reported problems with switching to 2.4ghz on the Android app. In my case, the switch seemed to work because once I've activated 2.4ghz in the app, I wasn't able to find my phantom access point. This was expected because the phone didn't support 5ghz anyway.
On my iOS device I'm able to use a 2.4ghz connection between the aircraft and the remote control. In CE mode the max distance was approx 720m, which seems a lot more than the expected 500m.
I believe it could have gone a bit further and cancel the RTH but I've stopped there.
Here's my experience with switching to FCC mode.
In order to switch to FCC mode I've followed the same steps mentioned by users in this thread.
On the Android Device:
1. Uninstalled the DJI Go app, removed the heremaps and dji folders from the phones storage.
2. Installed FakeGPS, configured it to a random location in the US.
3. Installed DJI Go, logged into the DJI account.
4. Closed the DJI Go app, started airplane mode (no wifi or mobile connection), made sure FakeGPS is still running, removed the credentials to my home access point so it doesn't auto-connect.
5. Started the remote control, while the airplane mode was still enabled - switched the phone wifi on, started the DJI Go app and connected
6. Started the aircraft, the wlan window appeared in the DJI go app, wifi restarted, FCC mode was successfully enabled since the 2.4 ghz mode had 11 channels available.
Nothing new so give all the thanks to the wonderful people in this thread who deserve the credit for figuring these steps out.
At this point I've closed everything and switched to the iOS device. I connected everything in the following order (RC turned on, iPad connected to the RC access point, aircraft started). Once connected, the iOS obviously found the drone in FCC mode and as far as I could tell, it remained in the FCC mode.
I never did anything to hide my GPS location on the iOS device. Even more, I made sure was near a window and I had some GPS signal on the iPad and on the aircraft.
The iOS app has switched back to CE mode only in one instance: while being in FCC mode, I switched the frequency from 5ghz to 2.4ghz. That disconnected the iPad from the RC and it automatically connected to my home wifi. Upon reconnecting to the RC access point, I was prompted with the wifi dialog.
So I went back to the Android device and this time I haven't uninstalled anything. Just started FakeGPS, stared airplane mode, started wifi, connected to the drone in the way mentioned in the steps above, bam, back to FCC mode.
Back on the iOS device I removed the home wifi so it doesn't auto-connect to it and started some tests. I haven't managed to bring the wlan toggle to CE mode. I tried to gain genuine GPS signal to both the iPad and the aircraft. I also tried to shut down the aircraft and let restart while everything else was connected in order to simulate a signal loss/reconnection and I wasn't propted with a wlan window at all.
I'm guessing that RTH should work without any problems since the GPS of the iPad wasn't tempered with at all. The location of the RC and the aircraft was accurate on the map while remaining in FCC mode and while reconnecting to the drone.
I will try to do a real flight test tomorrow and come back with the results.
I do realize that this is not helpful to many because I don't think everyone has Android and iOS devices lying around but I sure hope this helps in some way.