859183 - [GPS] GPS engine still operate, when HERE Map Stop

Status: RESOLVED DUPLICATE of bug 871343

(Firefox OS Graveyard :: Gaia, defect)

Description

[leo.bugzilla.gecko]

When HERE Map start and stop, GPS Indicator is still remain on the top(also,GPS Engine operate).
It is off after about 1 minute from Here Map stop.
Is scenario normal case?

Comment 1

[leo.bugzilla.gecko]

This Case(when HEREMap stop, still GPS operate) is possible to cause power consumption claim.
Could your team be ready debug this issue?

Comment 2

[leo.bugzilla.gecko]

We don't have any comment for a week.
We hope we can look forward to hearing from your team soon.

Comment 3

[Lawrence Mandel [:lmandel] (use needinfo)]

This reads like a platform issue to me. Shouldn't the B2G platform enforce the release of GPS when an app terminates?

Comment 4

[leo.bugzilla.gecko]

Sorry about the confusion my question.
We just want to know that it is Normal scenario. 
- push the HOME button when HERE Map operating, background app still operate(also,GPS Engine operate).

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

Back over to b2g to determine if this is a platform issue.

Comment 6

[leo.bugzilla.gecko]

We want to answer this question.
Is this case Normal scenario? yes or no.
(Opush the HOME button when HERE Map operating, background app still operatealso,GPS Engine operate.)

Plz, Confirm this.
Thanks.

Comment 7

[Chris Lord [:cwiiis]]

I also see this issue and the increased battery drain. A work-around is to kill the app by long-pressing home and closing it from there, but this should not be necessary.

Nominating for v1.0.1 as I think this is something people will easily run into and has a very negative effect (your phone dies prematurely).

Comment 8

[Lawrence Mandel [:lmandel] (use needinfo)]

FWIW, to me this isn't a blocker. While this scenario is not ideal, as stated in comment 7, there is a simple workaround.

Comment 9

[Chris Lord [:cwiiis]]

(In reply to Lawrence Mandel [:lmandel] from comment #8)
> FWIW, to me this isn't a blocker. While this scenario is not ideal, as
> stated in comment 7, there is a simple workaround.

The work-around is simple, but not obvious or particularly discoverable - is this really something we want all users to have to do?

Comment 10

[Daniel Coloma:dcoloma]

Agree with comment 8, not a blocker for 1.0.1

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to Chris Lord [:cwiiis] from comment #9)
> 
> The work-around is simple, but not obvious or particularly discoverable - is
> this really something we want all users to have to do?

It's not something we want, but a fix will have to be driven into a future release.

Comment 12

[leo.bugzilla.gecko]

(In reply to [e-mail] from comment #11)
> (In reply to Chris Lord [:cwiiis] from comment #9)
> 
> The work-around is
> simple, but not obvious or particularly discoverable - is
> this really
> something we want all users to have to do?

It's not something we want, but
> a fix will have to be driven into a future release.

Thanks your decision.
We want know when receive fixed version.

Thanks