Migrate to LocationManagerCompat + LocationRequestCompat

[LukasPaczos]

Capturing from this bug report, there's a bug in Android 12 where FUSED location provider is returned instead of GPS one when trying to get LocationManager's best available location provider which leads to a significant degradation in location updates quality. This situation takes place in the LocationEngineProvider when the app does not have Google Play Location Service dependency available. There's a bug fix on the way that should've reached 100% deployment on March 7 but for any devices affected and without the update there's a workaround of migrating to the compat location APIs which should theoretically resolve the issue.

Migrating to the compat lib should be a good step for us regardless, so we might want to pick it up as soon as possible to prevent additional exposure to this issue.

cc @mapbox/core-telemetry @mapbox/navigation-android

[VysotskiVadim]

Is there any suggested workarounds for those who experience issue with getting location on Android 12 without GP? mapbox/mapbox-navigation-android-examples#80

[tarigo]

I think we can bump LocationCompat in MME if the issue with lStar is solved (latest androidx core require compileSdk 31).

[Abram4]

Hi team,

I believe I have another customer experiencing this issue. Do we have any steps I can share with them on the workaround that we found for this?

[LukasPaczos]

This change has not been implemented in the Mapbox stack @Abram4, a workaround would be using a custom implementation of the LocationEngine interface which is wired to the LocationManagerCompat by a customer that sees an impact of this Android bug.