I'm wondering for the fused location, does any of the above use a combination of gps + wifi network together? what is the difference in terms of provider (does any of it uses the gps)? from what i see in the documentation the difference is only distance
I've previously worked with LocationManager and used NETWORK_PROVIDER and GPS_PROVIDER together to get a combination of those two provider.
Typically uses a combination of Wi-Fi and cell information to compute device location. PRIORITY_LOW_POWER largely relies on cell towers and avoids GPS and Wi-Fi inputs, providing coarse (city-level) accuracy with minimal battery drain. PRIORITY_NO_POWER receives locations passively from other apps for which location has already been computed.
PRIORITY_BALANCED_POWER_ACCURACY provides accurate location while optimizing for power. Very rarely uses GPS. Typically uses a combination of Wi-Fi and cell information to compute device location.
Used with setPriority(int) to request the best accuracy possible with zero additional power consumption. No locations will be returned unless a different client has requested location updates in which case this request will act as a passive listener to those locations.
the smallest displacement in meters the user must move between location updates. Sets whether the client wants the locations services to wait a few seconds for accurate locations initially, when accurate locations could not be computed on the device immediately after PRIORITY_HIGH_ACCURACY request is made.
The new fused location providers take a slightly different approach compared to previous methods. Developers now choose how much battery power is used to calculate a location instead of which device components are used to calculate it. It uses any available combination of GPS, Wi-Fi, mobile networks, and onboard sensors to calculate the location.
The LocationRequest
priority settings are now:
PRIORITY_NO_POWER
(passively listens for location updates from other clients)PRIORITY_LOW_POWER
(~10km "city" accuracy)PRIORITY_BALANCED_POWER_ACCURACY
(~100m "block" accuracy)PRIORITY_HIGH_ACCURACY
(accurate as possible at the expense of battery life)Google describes the LocationRequest
class here: https://developers.google.com/android/reference/com/google/android/gms/location/LocationRequest
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