IssueTracker

Can you provide the below requested information to better understand the issue:

We have tested with given below example we are not able to reproduce the issue.
https://github.com/googlesamples/android-play-location/tree/master/LocationUpdates

Please provide the sample application to demonstrate the issue.

Android build
Which Android build are you using? (e.g. KVT49L)

Device used
Which device did you use to reproduce this issue?

Please provide sample project  to reproduce the issue.  
Also mention the steps to be followed for reproducing the issue with the given sample project.

Expected output
What do you expect to occur?

Current output
What do you see instead?

The sample application is updating the app you tested with the code updates in this issue https://github.com/googlesamples/android-play-location/issues/151.  I will explicitly add the 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 10M even when device is reporting sub 10M accuracy.

We are not able to reproduce the issue

We have find the below coordinates
05-08 05:26:27.226 10630-10630/com.google.android.gms.location.sample.locationupdates I/System.out: latitude  12.9824637lang  77.6971695
05-08 05:26:37.293 10630-10630/com.google.android.gms.location.sample.locationupdates I/System.out: latitude  12.9824604lang  77.6971659
05-08 05:26:47.733 10630-10630/com.google.android.gms.location.sample.locationupdates I/System.out: latitude  12.9824616lang  77.6971672
05-08 05:26:57.755 10630-10630/com.google.android.gms.location.sample.locationupdates I/System.out: latitude  12.9824637lang  77.6971694
05-08 05:27:07.777 10630-10630/com.google.android.gms.location.sample.locationupdates I/System.out: latitude  12.9824639lang  77.6971695

From above lat lang the difference between each updates less then meter only

Please check the application and update the results which you observed.

The issue is with the result of calling `mCurrentLocation.getAccuracy()` as the result of that API call is never less than 10M even when the accuracy from `LocationManager` is less than 10M.  Are you updating the sample with the code I provided?  If so you should see that when your devices accuracy is < 10M the `mAccuracyTextView` never shows a value < 10M.