Current, Here map Scenario is as the following So, We concerned power consumption issue. step1> execute HERE Map App step2> press home button -> HERE Map App performs long-running operations in the background and does not provide a user interface. step3> It can cause Power Consumption issue. We think that this issue is very critical and fixed. So, We propose this scenario as like Google Map. case_1> Here Map : Map Mode step1> execute HERE Map App - Map Mode step2> press home button step3> stop GPS engine : HERE Map App doesn't perform long-running operations in the background case_2> Here Map : Navigation mode step1> execute HERE Map App - Navigation Mode step2> press home button step3> runnning GPS engine for navigation guide(same current scenario) Could you modify Here map like above scenario? And let me know target date if possible. Thanks

ni? reporter. how do you tell that Nokia Map is doing something in the background after pressing home? can you describe more on this? thanks

When the Heremap become to be the background by press home key, it dese not turn off GPS. If user forgets the hidden Heremap running, the battery is consumed very quickly. so we consider Heremap removing from device. We suggest that Nokia modify their Heremap so that it turn off GPS when it’s be the background except navigating.

Can you give us an idea of the user impact? How much battery is lost, over how long? We can't base blocking on hypothetical user impact and correctness.

When the Here Map become to be the background by press home key, power consumption is 135.4mA. When the Here Map forcibly Stop by long press home key, power consumption is 3.8mA theoretically calculated, Here map in the cabkground 1540mAh / 135.4mA = 11.4 hour Here map forcibly Stop 1540mAh / 3.8mA = 405.3 hour Thanks

NI reporter - Leo, is this "running a navigation app in the background" part of your test cases for power consumption and it must be passed? We understand the impact is large given comment 5 but this can likely be corrected through application update in the future, should this be considered release blocking?

There are two possible fixes here. We can forcefully stop an app from tracking the current location when it goes to the background, or we can ask the partner to fix Here Map to stop tracking when the application goes into the background and we are not trying to do something like navigation. The former has the disadvantage that it will make it impossible to do navigation while in the background. The latter has the disadvantage that it won't fix similar apps doing the same.

(In reply to Andreas Gal :gal from comment #7) > There are two possible fixes here. We can forcefully stop an app from > tracking the current location when it goes to the background, or we can ask > the partner to fix Here Map to stop tracking when the application goes into > the background and we are not trying to do something like navigation. The > former has the disadvantage that it will make it impossible to do navigation > while in the background. The latter has the disadvantage that it won't fix > similar apps doing the same. Is there a third option where we could require a special permission to allow for background usage of gps, so that apps can request that if they need it, but current apps that don't request it won't get it?

comment 8: thats exactly what dougt and I were discussing this morning. Someone should grab this bug.

This is blocking issue. So, must fix it. We propose this scenario as like Google Map. When use Map mode, press home key -> Stop GPS. When use Navigation mode , press home key -> Ongoing GPS. Thanks

I thought a bit more about this. Is fixing Maps off the table? Location applications should turn off the gps when it isn't needed. I would hope that the software that comes bundled on the FFos are good examples of location usage. :) I do not like having another permission. Determining if we should cancel Watch() based on a new permission will not work in this case. The HERE application provide both navigation mode AND map mode as a single application (i think!). We would have to separate their application into two parts -- a mapping mode application and a navigation mode application. (Maybe I am using a different here build) My suggestion is that we shouldn't try to guess intent based on a permission. I do not think we should be inventing things here. We should just fix Maps. I could be convinced otherwise.

Talking to Nokia about the issue here is an option. Thomas - Can you notify the Nokia team about this bug in their app and solution proposed in https://bugzilla.mozilla.org/show_bug.cgi?id=871343#c7?

Michael, Sandeep - can we get a battery consumption perf target set for v1.1 expectations to base a blocking decision on here?

I mentioned this to Nokia, and they may be able to come up with a hack where they stop watching GPS when the application goes into the background, unless GPS is being used to give directions.

Lucas (comment #13): We are in the process of defining our targets for V1.2 (based on reference devices & product specs etc). I believe this case does not need that version of full blown spec for a blocking decision, as the comment #5 is the exact data we need. Typically, the "idle" current drain on device needs to be under 5mA (which is what we would accomplish if we fix the map issue, as shown in comment #5 above). I agree with fixing the maps app, as this is cleaner that way. There will be still some "off the web" (or mktplace) 3rd party apps that can cause this but there is enough user awareness these days that "some" apps can drain lot of battery. Typically that gets called out in user comments for that app. I would focus on our preloaded apps for now.

(In reply to Donovan Preston from comment #14) > I mentioned this to Nokia, and they may be able to come up with a hack where > they stop watching GPS when the application goes into the background, unless > GPS is being used to give directions. This seems like the most promising approach considering the schedule. Can they provide us with a confidence level and ETA for a fix?

leo+ for fixing the Maps app (comment 11), which makes this POVB.

(In reply to Alex Keybl [:akeybl] from comment #17) > leo+ for fixing the Maps app (comment 11), which makes this POVB. This is not how we track preinstalled app issues. Clearing flags.

Donovan, Can you reply to Lucas' comment #16? Any update from Nokia on what they can and plan to do about this issue? (In reply to Lucas Adamski [:ladamski] (plz needinfo) from comment #16) > (In reply to Donovan Preston from comment #14) > > I mentioned this to Nokia, and they may be able to come up with a hack where > > they stop watching GPS when the application goes into the background, unless > > GPS is being used to give directions. > > This seems like the most promising approach considering the schedule. Can > they provide us with a confidence level and ETA for a fix?

Let me redirect this request to one of the Nokia contacts.

Hi Lucas, we're planning to take a look (and most probably will be able to fix this issue) next week. Leo

Dear Mozilla Team Could you let me know fix schedule about this issue? We have to be concerned about this issue and receive patch ASAP. Thanks

ziel.leo@googlemail.com, any update? Please let me know how I can help!

Hello, we're are already looking into this issue. As far as I understood we can use the page visibility API https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/Using_the_Page_Visibility_API Approximate ETA of the fix should be by the end of the next week. Leo

Yes, the page visibility api should be perfect for this. Thanks for looking at it!

Thank you for fix this bug. I have a question. We wonder if it is fixed. Could you let me know what is fixed scenario? previously proposed fix..is that right? When press home button on operating Here Map, mapping mode -> GPS engine off navigation mode -> still GPS engine on (In reply to ZieL from comment #24) > Hello, we're are already looking into this issue. As far as I understood we > can use the page visibility API > https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/ > Using_the_Page_Visibility_API Approximate ETA of the fix should be by the > end of the next week. Leo

Hi, all. Could you let me know when do we get the patch? We have not received yet.

Hi, Sorry for the delay. Yes the fixed scenario is right: When press home button on operating Here Map, mapping mode -> GPS engine off navigation mode -> still GPS engine on We have now a fix in place. But would need to test the app next week. We'll try to release at Wednsday. Leo (In reply to leo.bugzilla.gecko from comment #26) > Thank you for fix this bug. > > I have a question. > We wonder if it is fixed. > Could you let me know what is fixed scenario? > > previously proposed fix..is that right? > > When press home button on operating Here Map, > mapping mode -> GPS engine off > navigation mode -> still GPS engine on > > > > (In reply to ZieL from comment #24) > > Hello, > > we're are already looking into this issue. As far as I understood we > > can use the page visibility API > > https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/ > > Using_the_Page_Visibility_API > > Approximate ETA of the fix should be by the > > end of the next week. > > > Leo

Could you let me know fix complete? We are anxiously awaiting. Thanks (In reply to ZieL from comment #28) > Hi, Sorry for the delay. Yes the fixed scenario is right: When press home > button on operating Here Map, mapping mode -> GPS engine off navigation mode > -> still GPS engine on We have now a fix in place. But would need to test > the app next week. We'll try to release at Wednsday. Leo (In reply to > leo.bugzilla.gecko from comment #26) > Thank you for fix this bug. > > I > have a question. > We wonder if it is fixed. > Could you let me know what > is fixed scenario? > > previously proposed fix..is that right? > > When > press home button on operating Here Map, > mapping mode -> GPS engine off > > navigation mode -> still GPS engine on > > > > (In reply to ZieL from > comment #24) > > Hello, > > we're are already looking into this issue. As > far as I understood we > > can use the page visibility API > > > https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/ > > > Using_the_Page_Visibility_API > > Approximate ETA of the fix should be by > the > > end of the next week. > > > Leo

Hi, The app with the fix was yesterday pushed to the market place and is currently in the review process. The version to check is 1.8.67. Leo (In reply to leo.bugzilla.gecko from comment #29) > Could you let me know fix complete? > We are anxiously awaiting. > > Thanks > > (In reply to ZieL from comment #28) > > Hi, > > Sorry for the delay. > > Yes the fixed scenario is right: > > When press home > > button on operating Here Map, > mapping mode -> GPS engine off > navigation mode > > -> still GPS engine on > > We have now a fix in place. But would need to test > > the app next week. We'll try to release at Wednsday. > > > Leo > > > (In reply to > > leo.bugzilla.gecko from comment #26) > > Thank you for fix this bug. > > > > I > > have a question. > > We wonder if it is fixed. > > Could you let me know what > > is fixed scenario? > > > > previously proposed fix..is that right? > > > > When > > press home button on operating Here Map, > > mapping mode -> GPS engine off > > > > navigation mode -> still GPS engine on > > > > > > > > (In reply to ZieL from > > comment #24) > > > Hello, > > > > we're are already looking into this issue. As > > far as I understood we > > > can use the page visibility API > > > > > https://developer.mozilla.org/en-US/docs/Web/Guide/User_experience/ > > > > > Using_the_Page_Visibility_API > > > > Approximate ETA of the fix should be by > > the > > > end of the next week. > > > > > > Leo

I checked the marketplace but the version is 1.8.61. How can I get the latest version(1.8.67)?

It seems that version 1.8.67 is still in the review process. Could you directly provide me Here Map version 1.8.67 ?

Could we get a latest version for HERE Maps? This bug was fixed at 1.8.61.

Can you seed up the review process? Otherwise we could send the package direclty to Donovan. He is our contact. Leo

I will lean on the marketplace review team to speed up the process.

Thank you ZieL and Donovan. We hope to get the latest version(1.8.67) by tomorrow for leo test version. Please request it to review team.

The 1.8.67 version is now available in the marketplace.

Now I connect to marketplace. But the version is 1.8.61 Could you check it?

It's probably cached, either in your browser or on a distributed cache network somewhere. Try clearing your browser cache, and if that doesn't work try again in a little while. When I refresh the page I see the new version.

Can this be closed as fixed now that we have the latest version with the fix to this bug included?

We check the 1.8.67 version, when here map start and position fix, go to background and GPS stop. But when here map start and searching satellite, go to background and don't stop. sometimes, if gps engine have turn off, even if it is not turned off. It is that we thought difference expected scenario. please check this. Thanks

Thx, we're looking into it. Leo

Hello, we've fixed the second reported issue happening while waiting for the gps fix. The version of the app containing this fix is 1.8.69. Yesterday the app was pushed to the marketplace. Please verify the fix and close this bug. Thx, Leo

Version 1.8.69 · Nokia · submitted July 8, 2013 · is now Fully Reviewed Donovan, can you confirm if the battery drain issue is resolved and close this bug if it is?

The OEM is the one that has the equipment to test the battery drain, they should test it and close it.

Leo, can you confirm if this is fixed?

I have installed 1.8.69 on my Unagi (master eng build I just did). The GPS activity icon is still in the top bar when the application is in the background. Not sure if that is an issue, but I would assume it actually tells is the GPS is being polled / running.

Hi Hubert, the gps icon stays indeed visible if the app is in the background but it's grayed out. If the app is running the gps activity icon is bright. I assume it's an indicator that the gps is not active anymore. Before the fix the icon stayed bright even if the app was in the background. Leo

The GPS icon stays white. It doesn't change colour. And the battery drained fast.

Gps activity icon is grayed out if the app is in the background

Hi Hubert, I've just checked 1.8.69 on Unagi 1.1.0.0-prerelease Build Id 20130719070225 Git commit ce5a75acd4ad6... Works as expected (see two attachments). Please let me know the device model and fxos version of the phone you've tested on. Thx, Leo

That was on Inari, master (I built it myself on the 23rd) Gecko 3bcb2143f6460fe67aa91322862f37bdc5fdfa92 Gaia bcc157b46e364856cdbc1eaa0ce159f2e10df1d6 Maybe it is a bug in master instead.

This also happen on Keon with Nightly build Build ID 20130725024045

Hubert, this seems like a regression in master; I just tested on Unagi with a 1.1 nightly build from 7/25 and the gps icon became grayed out as expected when maps went into the background. I also tested on Keon with a 1.1 nightly build from 7/24. It worked as expected.

I filed bug 871343 for the regression.

Sorry I meant bug 898240

(In reply to Donovan Preston from comment #46) > Leo, can you confirm if this is fixed? Yes, We confirm this. Sorry, answer is delayed. Thanks