TripStatisticsService does not always exit

As of this fix:
http://bazaar.launchpad.net/~opensatnav-admins/opensatnav/release-1.0/revision/151
The TripStatistics service will shut down when OSN is not in the foreground.

This is a suboptimal solution. If you are on a walk with you osn running and
you care about statistics, and then someone calls you, you will loose your
trip distance, time etc.
droidguy

On Jun 20, 2010 1:45 AM, "Kieran Fleming" <email address hidden> wrote:

As of this fix:
http://bazaar.launchpad.net/~opensatnav-admins/opensatnav/release-1.0/revision/151
The TripStatistics service will shut down when OSN is not in the foreground.

** Changed in: opensatnav
      Status: Confirmed => Fix Committed

--
TripStatisticsService does not always exit
https://bugs.launchpad.net/bugs/584439
You received ...
Status in OpenSatNav: Fix Committed

Bug description:
If OpenSatNav is not closed using the 'back' button the service stays
running. As ...

That's a fair point. What about if the service keeps running but lets go of the GPS?

If trip stats service stops using GPS, the trip while the user is on the
phone, or uses any application other than OSN, this section of the trip is
ignored. I'd prefer to notify the user that the service is still running by
posting a message to the status bar. But this takes more work, right?

droidguy

On Sun, Jun 20, 2010 at 10:55 AM, Kieran Fleming
<email address hidden>wrote:

> That's a fair point. What about if the service keeps running but lets go
> of the GPS?
>
> --
> TripStatisticsService does not always exit
> https://bugs.launchpad.net/bugs/584439
> You received this bug notification because you are a member of
> OpenSatNav Admins, which is the registrant for OpenSatNav.
>
> Status in OpenSatNav: Fix Committed
>
> Bug description:
> If OpenSatNav is not closed using the 'back' button the service stays
> running. As the service uses GPS this ends up draining the battery very
> quickly!
> We should either close down the service when the program isn't on screen or
> notify the user that the program is still running by posting a message to
> the status bar.
>
>
>

--
Stan Berka
(h) 503 977-3813
(c) 503 997-0062