You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2023. It is now read-only.
We are looking into this. Initial testing seems to indicate the callbacks are triggered when a provider is disabled using the location system settings (toggling mode between high accuracy, battery saving, and device only) but not when enabled.
Also please be aware that LocationListener.onProviderDisabled() and LocationListener.onProviderDisabled() will soon be deprecated in favor of LocationAvailability.
These methods are called if the LocationListener has been registered with the location manager service using the requestLocationUpdates(String, long, float, LocationListener) method.
Lost registers its listeners with the LocationManager selectively based on the priority set when creating a location request.
For example if the priority is PRIORITY_BALANCED_POWER_ACCURACY then no listener will be set on the GPS provider and enabled/disabled callbacks will not be invoked for it. However callbacks will still be invoked for the network provider.
Documentation and demo app have been updated here #137.
The text was updated successfully, but these errors were encountered: