1)
@aeropic has a litchi licence (I don't). I saw on his Samsung that V4.14 had the issue and litchi not. May be he could make a try to confirm for V4.15 ?
2) the issue seems to be linked to the developper's account (not the drone) as the problem occurs on all of my drones (2 sparks and one mini)
As you can see into my log, the connection jumps several times to "NOT_REQUIRED" (which is the expected result for Europe) but the latest one gives "UNBOUND"
I did try an almost (not) working woraround :
- place a sheet of aluminium on top of the drone to prevent GPS fix
- launch the app
- cut the 4g data link on the phone
- remove the sheet of metal
if you are lucky, you can do it at the exact right moment to skip the latest DJI connection and prevent the "UNBOUND". But it is really a matter of chance and doesn't work most of the time...
In any case if you reopen the data link then the drone switchs to UNBOUND (if not already in the air)
Once you are in "UNBOUND" you MUST open the DJIFly original App to "clear a flag" to recover the NOT_REQUIRED configuration. A message in the DJI App says "device re initializes its parameters to comply with local regulations. Please wait and reconnect" or something like this.
Then (and only then) the V4.14 App may recover the NOT_REQUIRED config provided you are lucky enough with my not working trick above...
If you relaunch the DJI Fly App this message does not pop up. This means that :
- V4.14 somehow spoils a parameter into the remote controller
- this parameter can be reset by the official DJIFly app (or Litchi if
@aeropic can confirm)
- if not reset this parameter remains into its latest state (if you are UNBOUND you stay UNBOUND unless an "official app" removes this limitation)
All this is not tested on my app with V4.15 as it doesn't work with the latest lib... Only Erel's example works for the moment. (logs above are from this Erel's example V4.15)