- Joined
- Sep 22, 2015
- Messages
- 93
- Reaction score
- 25
- Age
- 43
A device locked by a default is definately not what we paid for.
Geofence - an attempt for Your privacy
- Thread starter Kyokushin
- Start date
- Joined
- Sep 22, 2015
- Messages
- 93
- Reaction score
- 25
- Age
- 43
Not exactly. The main problem is - DJI can push new NFZ even to old system just by connection to the internet or by the app or f/w upgrade. In Geo you will be just able to unlock some zones over airports what You cannot unlock at now.
Only one method to keep current NFZ list is block access to DJI servers and stay on 1.5 f/w with 2.4.3 app for ever.... or change DJI course (however i think they are on their own and they dont care so much about what we thinking).
However, the new geofence, after critical reception of first beta approach, sounds promising - they change the most of server-sided authorisation zones to client-sided enchanced warning zones, so finally it looks like an old NFZ system, but with a possibility of unlock the most of current red area's over airports.
Last edited:
- Joined
- Dec 14, 2015
- Messages
- 44
- Reaction score
- 5
- Age
- 53
Not entirely true. 1.6 doesn't contain any of the GeoFencing code in it. I do not have to unlock anything before I fly. That all starts at 1.7. I have never updated to the latest Go software either. Problem solved.
- Joined
- Sep 22, 2015
- Messages
- 93
- Reaction score
- 25
- Age
- 43
No. It means 1.6 have geo-ready functionalities (and maybe some other, but only God knows what), and they could be activated remotely.
RC Groups - View Single Post - Dji geofence - beware of 1.7 beta - you will not be able to downgrade nfz
But, finally - the new version of Geo is not what i like, but it should be better than old NFZ system, because at end will unlock a zones what are already red-locked. In both cases you can disable communication with DJI if you do not want unlock zones over airports, and in both cases DJI can in any moment push NFS-red zones if communication is not locked.
In my opinion - the best way will be consider a number of blocked -red and server-sided authorisation zones in both system, choose better and then disable any communication with DJI, then wait and observe system on their map carefully before any server-side unlock, or any update of app/fw what will require communication.
RC Groups - View Single Post - Dji geofence - beware of 1.7 beta - you will not be able to downgrade nfz
But, finally - the new version of Geo is not what i like, but it should be better than old NFZ system, because at end will unlock a zones what are already red-locked. In both cases you can disable communication with DJI if you do not want unlock zones over airports, and in both cases DJI can in any moment push NFS-red zones if communication is not locked.
In my opinion - the best way will be consider a number of blocked -red and server-sided authorisation zones in both system, choose better and then disable any communication with DJI, then wait and observe system on their map carefully before any server-side unlock, or any update of app/fw what will require communication.
Last edited:
Similar threads
