Menu
I have a navigation app that used geofences(Creating and Monitoring Geofences).
Google says (Background Location Limits):
The average responsiveness for a geofencing event is every couple of minutes or so.
On previous Android versions was no delay. But on Android O, the app shows a delay of ~4-5 minutes after leaving a geofence(approximately 50% of cases). Tested on ODP2
Has anybody faced a similar problem?
647
App developers can use native Android and iOS location detection to power their location-based experiences and engagement. However, native geofencing technology can only deliver accuracy of around 100-200 meters. For context, that's about the length of a soccer field.
Most smart devices allow you to set them up to function so that they trigger automatically via a wonky-sounding technology called geofencing. That simply means enabling your smart devices to automatically activate when you leave home or return—an event that is (usually) determined by the location of your smartphone.
For best results, the minimum radius of the geofence should be set between 100 - 150 meters.
Test entering a geofence by creating a geofence region that includes your current physical location, so you're already inside the geofence and the “geofence entered” event is triggered immediately. This works great for the entered event but doesn't work for all geofencing scenarios.
Google added new paragraph to Create and monitor geofences doc
Alerts can be late. The geofence service doesn't continuously query for location, so expect some latency when receiving alerts. Usually the latency is less than 2 minutes, even less when the device has been moving. If Background Location Limits are in effect, the latency is about 2-3 minutes on average. If the device has been stationary for a significant period of time, the latency may increase (up to 6 minutes).
87
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
