title: Location.getTime() always returns timestamp without milliseconds
body: <p>I'm tracking GPS locations with <code>LocationManager.requestLocationUpdates()</code> using <code>LocationManager.GPS_PROVIDER</code> and registering a <code>LocationListener</code>.</p>
  
  <p><strong>My Problem:</strong></p>
  
  <p>All tested devices (Sony neo, Sony active, Moto G) produce <code>Location</code> objects which do not have fractions of a second in their <code>getTime()</code>:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;trkpt ...&gt;&lt;time&gt;2014-05-24T10:24:59.000Z&lt;/time&gt;&lt;/trkpt&gt;
  &lt;trkpt ...&gt;&lt;time&gt;2014-05-24T10:25:00.000Z&lt;/time&gt;&lt;/trkpt&gt;
  &lt;trkpt ...&gt;&lt;time&gt;2014-05-24T10:25:01.000Z&lt;/time&gt;&lt;/trkpt&gt;
  &lt;trkpt ...&gt;&lt;time&gt;2014-05-24T10:25:02.000Z&lt;/time&gt;&lt;/trkpt&gt;
  &lt;trkpt ...&gt;&lt;time&gt;2014-05-24T10:25:03.000Z&lt;/time&gt;&lt;/trkpt&gt;
  </code></pre>
  
  <p>As I'm calculating speed, incline and merge with barometic altitude, 1s (1000ms) resolution is way too imprecise. And I do not believe, that the fixes are all <em>exactly</em> at <code>.000</code>.</p>
  
  <p><strong>My question:</strong></p>
  
  <p>Is is better to take <code>System.currentTimeMillis()</code> as the timestamp for my track-points, or is the GPS fix generally far behind "real time" and the calculated positions are actually those from the past (several seconds behind)?</p>
  
  <p>Remarks:</p>
  
  <ul>
  <li>I know speed calculation is not precise and quite complex when using GPS data</li>
  <li>This is not a duplicate of <a href="https://stackoverflow.com/questions/22841421/">Matching Location.getTime() milliseconds to NMEA sentences</a> </li>
  </ul>