search

rinigus / pure-maps

Maps and navigation
https://rinigus.github.io/pure-maps/
GNU General Public License v3.0
251 stars 43 forks source link

Pure Maps does not close / finish navigation properly #31

Open rinigus opened 6 years ago

rinigus commented 6 years ago

From TMO, https://talk.maemo.org/showpost.php?p=1545876&postcount=137 and https://talk.maemo.org/showpost.php?p=1547761&postcount=77

An even stranger thing happened about an hour later, when WhoGo was safely closed - or so I thought. I unlocked the phone for some other, unrelated reason, and it started speaking navigation instructions. I started WhoGo but it shut down instantly. I eventually had to restart Lipstick from Sailfish Utilities.

This has recently become the norm. Every time I use WhoGo for navigation, no matter how short, it always ends up like this. There was not a single time when it did not. I tried ending the navigation and clearing the route and all map markers before I close the application, but that seems to make zero difference. The GPS icon in the status bar is flashing and the battery drains about 4x faster than you would expect. Usually, unless I trigger this issue and the phone stays silent, I also get voice prompts even though no application is open.

I also found that restarting Lipstick is not enough. Only a complete reboot is. A reboot or power cycle every time after navigation has now become part of the experience. (This is on J1, but I have noticed at least one other user reporting a similar experience on the X.)

Olf0 commented 6 years ago

I experienced this, too. The hint was, that other "memory hogs" (e.g. Firefox for Android) were unusable after a navigation with Pure Maps (having it closed before starting the other "big" app), unless the Jolla 1 was rebooted. Yes, a simple lipstick restart was not sufficient to resolve this (tried that first).

rinigus commented 6 years ago

One way to impose this is to:

Observe that Pure Maps will be not stopped until killall -SIGCONT harbour-osmscout-server is issued.

So, at least one of the reasons: enforce closing of all connections at stop

Olf0 commented 5 years ago

Mmmh, I observed this again with PureMaps 1.9.0 yesterday, but did not have the time to analyse what exactly happened. I may try to reproduce and analyse this at around Christmas.

rinigus commented 5 years ago

I presume that you use latest Mapbox GL QML plugin. If not, please check with it. On my device (onyx), I haven't seen it for a very long time.

Olf0 commented 5 years ago

I presume that you use latest Mapbox GL QML plugin.

That (yesterday) occurred with mapbox-gl-qml v1.3.2 from OpenRepos.

rinigus commented 5 years ago

Yep, that's the latest. So my SSL fix is in already.

rinigus commented 5 years ago

@Olf0 - I presume this test slipped the proposed timeslot?

Olf0 commented 5 years ago

Thanks for the trigger, as it did not occur anymore, I completely forgot about it.

So explicitly testing it now:

Summary: I have not experienced this anymore, plus I cannot reproduce it by testing (but note, that I never ran those tests before).

Thanks, I think this issue can be closed for good. :)

rinigus commented 5 years ago

Closing with pleasure and hoping it will not resurface :)

rinigus commented 5 years ago

Looks like it has resurfaced:

http://talk.maemo.org/showpost.php?p=1558002&postcount=737 http://talk.maemo.org/showpost.php?p=1558119&postcount=748

rinigus commented 4 years ago

Any new instances of that with the latest release?

Olf0 commented 4 years ago

I did not experience any since January 2019, as noted in my comment (2019-01-11) above. But as it is just us (two) discussing here and the recent reports were posted at TMO (although 3 months ago), I wonder if it makes more sense to ask there.