Most GPS receivers output a position that is valid at the second
boundry.
On Mar 17, 2:54 pm, Yossi wrote:
> Hi,
>
> According to the decumentation, android.location.Location.getTime()
> returns the fix time in milliseconds. however I keep getting the time
> rounded to seconds (e.g. no milliseco
Plus, getSpeed() often returns 0, even when it shouldn't.
-Jon
On Mar 18, 8:37 am, Yossi wrote:
> I'm calculating the average speed of several points so I need to have
> the accurate total distance and time.
>
> On Mar 18, 2:32 pm, Neil wrote:
>
> > If you want the speed call getSpeed().
>
> >
I'm calculating the average speed of several points so I need to have
the accurate total distance and time.
On Mar 18, 2:32 pm, Neil wrote:
> If you want the speed call getSpeed().
>
> On Mar 18, 12:21 pm, Yossi wrote:
>
>
>
> > thanks, I also don't want fixes more then every few seconds but to
If you want the speed call getSpeed().
On Mar 18, 12:21 pm, Yossi wrote:
> thanks, I also don't want fixes more then every few seconds but to
> calculate the accurate speed/pace I would expect milliseconds
> accuracy.
>
> On Mar 18, 12:07 am, Dianne Hackborn wrote:
>
> > It just says the units
thanks, I also don't want fixes more then every few seconds but to
calculate the accurate speed/pace I would expect milliseconds
accuracy.
On Mar 18, 12:07 am, Dianne Hackborn wrote:
> It just says the units are in milliseconds; it doesn't say anything about
> the accuracy. I certainly wouldn't
It just says the units are in milliseconds; it doesn't say anything about
the accuracy. I certainly wouldn't expect (nor probably want) fixes more
than every second. :}
On Tue, Mar 17, 2009 at 2:54 PM, Yossi wrote:
>
> Hi,
>
> According to the decumentation, android.location.Location.getTime()
6 matches
Mail list logo
