IssueTracker

The `FusedLocationProviderClient` never reports an accuracy less than 3m?

Reproducible steps are provided in the Location samples on GitHub, see issue https://github.com/googlesamples/android-play-location/issues/151.  

I will explicitly add reproducible code here:

Update res/layout/main_activity.xml with the following:
<!-- Add TextView UI (new line 98-104) -->
<TextView
            android:id="@+id/accuracy_text"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_marginLeft="@dimen/small_margin"
            android:layout_marginStart="@dimen/small_margin"
            android:textSize="@dimen/default_text_size" />

Update MainActivity.java with the following:
// add widget (new line 143)
private TextView mAccuracyTextView;

// add label (new line 148)
private String mAccuracyLabel;

// locate UI widget (new line 174)
mAccuracyTextView = (TextView) findViewById(R.id.accuracy_text);

// set label (new line 180)
mAccuracyLabel = "Accuracy";

// set value of the UI field (new line 409/410)
mAccuracyTextView.setText(String.format(Locale.ENGLISH, "%s: %f", mAccuracyLabel,
                    mCurrentLocation.getAccuracy()));

Run the updated app.  Expected output is the accuracy in the app to match the accuracy reported by device.  

Android Build: Tested on 3 devices with the following build numbers:
- OPM2.171019.029
- NRD90M.T710XXU2DRB1
- M4B302

Devices:
- Pixel 2 XL
- Samsung Galaxy Tab S2
- Nexus 5

Expected output
Accuracy in updated sample app should match device accuracy

Current Output
App never shows accuracy below 3M even when device is reporting sub 3M accuracy.

The issue is with the result of calling `mCurrentLocation.getAccuracy()` as the result of that API call is never less than 3M even when the accuracy from `LocationManager` is less than 3M.  The current accuracy reported is a fix from https://issuetracker.google.com/79189573 Location.getAccuracy() never reporting accuracy better than 3M when using FusedLocationProviderClient, but we consider this still a bug in that accuracy reported should not be limited to 3M.


Also add the following details:
- Devices: Nexus 5, Pixel 2 XL, Samsung Galaxy Tab S2
- Google Play Services client library version: 11+
- Google Play Services version on the device: 12.5.29,
- Android SDK Version: 6.0.1, 7.0, 8.1.0, 9.0
- Was this working correctly on a previous version of Google Play Services?
N/A