title: Google Play Service location API returns wrong location sometimes
body: <p>We have an app which captures user's location using Google Play Service Location API for each transactions like Geotag land, upon placing an order etc.</p>
  
  <p>After capturing these locations from mobile we'll sync it to server and show it in web dashboard.</p>
  
  <p>We have noticed in few cases transaction captured within few seconds have location results of varied distance.</p>
  
  <hr>
  
  <p><strong>Example</strong>: <br/>
  Location of the user will be in <br/><br/><strong>Mandsaur, Madhya Pradesh, India, Asia</strong><br/>  (Latitude - 24.057291, Longitude - 75.0970672, Captured date - <strong>2017-01-04 09:19:48</strong>). <br/><br/>
  But subsequent transactions will have location of <br/><br/>
  <strong>Paris</strong>  which is 6772 km away <br/>(Latitude - 48.8581074, Longitude - 2.3525187, Captured date - <strong>2017-01-04 09:20:01</strong>)</p>
  
  <hr>
  
  <p><em>sometimes its fetch wrong stated of <strong>india</strong> like user is from gujrat then location fetch of Bihar, Maharastra, Kuwait(out of india) its really headache for indian developer</em> </p>
  
  <hr>
  
  <p>As this is happening without user interference and no mock location apps installed in user's device.</p>
  
  <p>Can anyone explain why this happens and how could we avoid these scenarios?</p>
  
  <hr>
  
  <p><strong>NOTE:</strong><br/>
  <em>These transaction locations are captured usually at open fields with GPS turned on and set to High Accuracy mode</em></p>