ferraript

I figured out I was idiot because I hadn't noticed that in DJI GO sources, timestamp is appended to that address and so entire address to my file was invalid...

hi @TadbirPaydar thanks, well, until I try it in the field, it's too early to say maybe all of this is useless I'm using DJI GO 2.4.3 with link to...

I don't use newer versions of DJI GO, because they are more complicated and they contain things I don't need / I don't like I don't use dex2jar + JD-GUI,...

yeah, it's complicated like hell :D just another reason for not using firmwares with GEO

I can assure you that all versions of DJI GO have NFZ, even DJI GO's predecessor, DJI Pilot, has NFZ so I'm afraid it's the same story with firmwares

by the way, today I finally took my downgraded P3A outside to test my NFZ hack in DJI GO result is: it's not working AC wasn't able to penetrate border...

>In my voyages through firmware, I wasn't able to find a list on NFZ areas @mefistotelis: I found it!!! in P3S_FW_V01.07.0060_mi01.bin, at address 0x0A1620, there is `85B0E6022F0F44017908` 85B0E602, in Little-endian,...

>Each entry looks like actually, it's written in bin file too: `----lat------lon-----radi-con-cla-id----sta-----end--` and it fits: 4-byte latitude 4-byte longitude 2-byte radius 2-byte country_code 1-byte class 2-byte area_id 1-byte begin_at 1-byte...

that's not clear at the moment today I was out at our airport to test my latest DJI GO hack this time I really deleted all real references to airport's...

I took 48.672901, tried to convert it into float, double, signed int (multiplied by 1000000) and I looked for the corresponding HEX value with both possibilities, that it could be...