Thread: [SailfishOS] WhoGo Maps
View Single Post
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#140
Originally Posted by pichlo View Post
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.)

Is there anything I can do to try to help with debugging? Any special mode to trigger, logs to collect, that kind of thing?
Sounds like there is an instance of WhoGo maps that is still running after you closed it. The voice commands are routed through WhoGo maps, so it should be that. Since its Python app, its somewhat harder to debug. You would have to use ps in the terminal to see if there are multiple instances running. I have

Code:
> ps x | grep sailfish | grep -i who
12293 ?        Ssl    0:09 /usr/bin/sailfish-qml harbour-whogo-maps               
12558 ?        S      0:00 invoker --type=silica-qt5 --single-instance sailfish-qml harbour-whogo-maps
and nothing after closing WhoGo. Let's see what do you get when its still chatting on the background.
 

The Following 7 Users Say Thank You to rinigus For This Useful Post: