Re: WhoGo Maps
 

OK, that changes things. I'll have to look into how to get RAM consumption for WhoGo maps and monitor it for some time. While its simple with collectd for C++ programs, here we have python script which is probably not a single one running on device.

How long were the trips to trigger such crashes?

Re: WhoGo Maps
 

Not any more. I used to, but found very little use for it and did not bother reinstalling it after a system reset. I can kick off a terminal and run 'free' the next time. Right now it says total 828692, free 224012. With five apps open, including the terminal.

(Incidentally, WhoGo failed to start, even after closing all five. One Lipstick restart later, WhoGo started fine. 'free' now says 828692/189788.)

Re: WhoGo Maps
 

The triplength vary a lot. Something between 30 km an 200 km. I also had the feeling, It just happens, when there is some rerouting necessary. But can't guarantee that. Also I have the feeling, it doesn't really have to do, with the length of the trip, but more with the fact how long the app is running.

Re: WhoGo Maps
 

Hi Everyone,

Rinigus was kind enough to help me out with my voice navigation issue before recommending to post about the problem here.

For some reason, voice navigation only starts working after I press the re-route button several times. Sometimes it works when pressing it from the first time. Just in case somebody has difficulties getting the voice navigation to work, you can try your luck with the mentioned method.

Also I noticed that voice navigation had stopped working after my car paired with the phone via bluetooth. Unpairing the phone bought voice navigation back.

Keep up the good work.

Re: WhoGo Maps
 

I had a similar problem. It was the underlying cause of what I reported earlier.

The real reason is that my car is a bit slow at switching to sound input from Bluetooth. Merely being paired is not enough, there must be an actual sound stream coming from the paired device, only then will my car's stereo offer me the option to switch to it. So I have to start playing some music on the phone, switch the car's input to it, stop the music, start WhoGo... not ideal but it works.

Another option is to unpair but unfortunately it does not always work, voice is still muted. As if the phone thought it was still paired and tried to stream the voice through Bluetooth. I have not quite figured out what the pattern is. Closing and restarting WhoGo does not always help either. I will try your re-routing workaround the next time.

Re: WhoGo Maps
 

loving the app, itd be handy if theres a way to pick which speech engine to use if multiple are installed.

being able to have a route based on several drop offs would be handy :P

Re: WhoGo Maps
 

What is the current policy on translations? I would like to see my Russian localization (which is already in Transifex) released or at least available in a test build rpm.

Re: WhoGo Maps
 

It will be included in the next release.

I just don't include severely incomplete translations, which Russian has been before and I don't tend to make new releases on account of translation updates when there's a new major/minor release coming out soon anyway.

Re: WhoGo Maps
 

Rinigus, Otsaloma, you are my heroes.
I finally ditched android navigation completely thanks to WhoGo maps.

Are you aware that WhoGo is "competing" with the big ones now by offering similar feature set? :)
You even have all puzzle pieces in place to overtake them with an unprecedented killer feature.

One thing no mobile navigation can offer is what embedded car solutions are best known for.
Reliable data directly from the car!

There is OBDfish in Jolla Store and combining it with WhoGo would allow for nifty things like speed data without Gps reception (perfect for tunnels and such), fuel/reach calculation (will i maybe need to refuel if i speed or better go slow) or eyecandy like nice (optional) rpm graphs.
http://m.memegen.com/ygkxnf.jpg

Now that i compare WhoGo on (very) high level with all other solutions i know, 2 things are "missing" for me.

Firstly, the 1 second(?) position update is slammed into the users face as honestly as it can be. The other way around i would love to not see the absolute accurate position where i am now, it would be enough for me to know where i was 1 second ago and have a nice fluid transition to the next known point and possibly fluid transitions overall while navigating.

For the second i threw together some code to not sound completely demanding without delivering something :p

How do you think about a gauge display for the current speed? I always focus on gps-speed when evading speed traps with just that slight 2km/h over and would love to have some sort of (optional/settings) large speed display.
Here my mock-up and code that should work if you feed the right data and somehow update it every second. Also feel free to adapt and change what is necessary to look good on the actual map display.
The Font is Source Han Sans, you might want to change that to Source Sans Pro.
gauge-test-upload.zip

https://mosushi.de/misc/maemo/050.pnghttps://mosushi.de/misc/maemo/090.pnghttps://mosushi.de/misc/maemo/160.pnghttps://mosushi.de/misc/maemo/200.png

Re: WhoGo Maps
 

It's a known issue, it's probably possible to improve it.

https://github.com/otsaloma/whogo-maps/issues/34

I have probably already said no to giant speed meters a couple times, as it seems to me hijacking a general purpose map app for a niche purpose, regardless of whether there's an option to show or hide the meter. If there is some day a fancier navigation view separate from the normal map view (see e.g. Kanzi), then in such a context it could make more sense.

Re: WhoGo Maps
 

For the record, I am not a great fan either but for those who are, I see an opportunity for an overlay plugin ;)

Re: WhoGo Maps
 

@mosen, gauge looking good. Not sure where to fit it though.

There was discussion over here about specific car navigation view. I could work on it when I get there - I am also using navigation mainly in the car and would love to get the corresponding mode available. Right now I am busy with the geocoder, though.

RE OBD: I remember when activating Jolla Store account there were some specific conditions regarding car interfaces and apps. If my memory serves me right, there were some specific restrictions regarding such apps. I suspect it has something to do with Qt and its use in cars. Assuming that it is just limitation of the store and not general for Qt, would be great to get the car speed via QtLocation API. I wonder if it has been done already.

Actually, I have somewhat WhoGo Maps related question: has anyone seen something similar for desktop Linux? We have modRana, but that's without Mapbox GL support (yet). Anything else, supporting geocoding, Mapbox GL, routing / navigation? When I looked for it, I couldn't find anything except few demos with rather limited functionality.

Re: WhoGo Maps
 

https://wiki.gnome.org/Apps/Maps

I don't use it myself though, I don't see much point in a desktop app for maps, especially online.

Re: WhoGo Maps
 

Just a "short" answer. Been travelling again...

I had to think into why you all read the proposed gauge is somehow ment to be big. Then i realised the giant 600px screenshots (for testing purpous in qmlscene on my 4k screen) and me not giving a mock-up of the whole screen placement might have lead you into that, sorry.

The gauge is kept simple and readability optimizes for the exact reason so it can be displayed rather tiny! I was thinking about the same height as the other lower items (menu+compass). That would not be wider than the current "n km/h" then also, but much more readable imho.

This post will be followed up by some clarifying screenshots as soon as i am back on my workstation.
Also i realize the background circle do not fit the overall ui, Thatmight get an update.

Thank you for taking my proposal serious anyway :)
I did not know gauges where already discussed.

Re: WhoGo Maps
 

Actually, I like the gauge & I'd like to add it to modRana. :)

There is are already dedicated info display pages in modRana,
so it could be put there as a dedicated speed-gauge page.

As for displaying it on the map, there is already the compass widget
in the upper left corner, scale bar in upper right and the bottom corners
are occupied by buttons.

But I guess I could add a setting to configure what should be shown in the upper
corners - compass/scale bar or the speed gauge. Should not be that hard.

And sorry for thread hijacking & we can certainly move further discussion
about this to the modRana thread. :)

Re: WhoGo Maps
 

So I've tried to play with mosens speed gauge (thanks! :) ), but the included shaders don't compile for some reason. I've posted the error log into the modRana thread to avoid any further hijacking of this thread. :)

Re: WhoGo Maps
 

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?

Re: WhoGo Maps
 

Did not happen to me (on Jolla C).

But must say I do not use navigation that much. Will try this afternoon again (and only reply if I smell something suspicious)...

nope, nothing wrong here

Re: WhoGo Maps
 

@pichlo: Check with Lighthouse if whoGo or OSM Scout Server is still running.

Re: WhoGo Maps
 

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

and nothing after closing WhoGo. Let's see what do you get when its still chatting on the background.

Re: WhoGo Maps
 

Happened again today. Twice. WhoGo is currently closed, yet flashing GPS icon in the status bar and trying to start a new instance shuts it down instantly.

EDIT:
Killing processes 1796 and 1883 sorted it out, but the first time it happened today I did not have time for such experiments. Life is too short, a reboot was quicker.

Re: WhoGo Maps
 

I have the same issue, but since many Versions. Even in Poor Maps i had this issue already.. :/

Re: WhoGo Maps
 

So, it looks like we need app killer for it. Or a one-liner to run from terminal / shellex

While I do wonder where does it lock itself.

Re: WhoGo Maps
 

I've been thinking about a one-liner too. Something along the lines of...
(Caveat: not tried yet.)

Re: WhoGo Maps
 

As it is python why not add (for Jolla1 users only ;)) something like pichlos one-liner wrapped in an 'os.system(...)' call on closing the window of WhoGo?
(not the nice way of closing a program but hey ... :D)

Maybe you could try different positions in py code and narrow down that occurence? I am sure pichlo would be happy to be guinea pig :rolleyes:

Re: WhoGo Maps
 

Yeah, kill as a way of ending the program is surely not the best. I would suggest to file it as an issue for now under https://github.com/otsaloma/whogo-maps/issues and fill in as much info as possible (update if you get anything extra). Then it will be possible to pick it up when time permits. (I started to work on a new aspect of navigation and will be focusing on that for some time => would prefer to focus on it).

Re: WhoGo Maps
 

I don't expect to investigate these Jolla 1 problems, but if someone wishes to do so, look at Application.quit, e.g. add print statements to see if one of those lines hangs. Try "raise SystemExit(1)" if needed to force a quit.

https://github.com/otsaloma/whogo-ma...ication.py#L54

Re: WhoGo Maps
 

Well for me and two other users from my family it's not only a J1 Problem, we have this issue on the Xperia X aswell. So i think it's a common issue not limited to a specific platform.

Re: WhoGo Maps
 

Thanks otsaloma.

If this is really just a J1 problem I can understand. I guess some race condition on older (bit slower) problem someshere?

I had a brief look at the quit(s) and I would start my simple plain ' print "Something" ' statement begore and after line
self._worker_thread.join()
in poor/voice.py even I do not see.why it should not join...
(not knowing how task_queues are handled in python)

Have fun, pichlo ;)

Re: WhoGo Maps
 

@pichlo and @jayki:

As a follow up: its Python 3, so you would have to use
syntax. Add it in between each command in quit. To see the print outs, run it in the terminal:
or, if you wish to clone it into your home dir (probably a better solution), you could run it by
If its regular for you, should be easy to catch it. Good luck!

Re: WhoGo Maps
 

Here's a possible fix. Try if that works. You can just edit that small change into the installed file under /usr/share/harbour-whogo-maps.

https://github.com/otsaloma/whogo-ma...92b6aa005ee8fa

Re: WhoGo Maps
 

I had some problems with cut. I could not convince it to use multiple spaces as a single delimiter. So I had to expand the line a bit but it seems to work now:
It is tested and it works (yes, I had to trigger the issue again to test it but that part was easy).

What it does:

• ps aux lists the running processes;
• The first grep filters out only those processes with "whogo" anywhere in the command line that started it - be it in the name or arguments;
• The second grep eliminates the grep process itself from the results;
• The third grep is only useful if you use the attached script - it eliminates the grep script itself from the results;
• sed merges multiple spaces into a single space;
• cut splits each line of output into fields, using a space as a delimiter and letting only the second field (the one containing the process ID, or PID) through;
• xargs collects the output (which by now is a few lines, each containing just the PID of a WhoGo process) into an argument list for the kill command.

I am attaching the line as a script. Copy it into /home/nemo, remove the .txt extension (I had to add it to pacify the TMO uploader) and run from the command line like this:
Or add the execute permission and run it like this:

Re: WhoGo Maps
 

Oops, I was too slow. Or you were too fast. After all, you said you were not going to waste spend time on this in the near future ;)

Thanks, I will give it a try and let you know.

Re: WhoGo Maps
 

Not sure if this is related, but I've been recently experiencing something similar (GPS icon in my status bar with no GPS application currently running, but only after having used one). Thing is, it happened when using Here WeGo (the android app installed from the official Jolla store a.k.a. harbour, not any of the available android stores). I'm using an Xperia X with official Sailfish X license, latest OS installed.

Maybe there is something system related triggering this, and it is not a WhoGo specific issue?

Re: WhoGo Maps
 

I don't know what the 'invoker' process is responsible for, but going by the name I'm assuming it isn't the one hanging in the background, so in that case I think you've just created a very complicated way of doing:
Props regardless!

Re: WhoGo Maps
 

Oh. I had not tried pkill. I tried killall which of course did not work.

While on the topic of trying... sorry otsaloma, your one-line fix on github did not do the trick :( Same issue again on my drive home from work. About 40 minutes, including a fuel stop.

Oh, and for some reason my script did not work either. The same command executed directly from Terminal did. Curiouser and curiouser.

Re: WhoGo Maps
 

I have been working on incorporation of map matching info and navigation screen for driving by car. I am quite sure the same can be used for cycling as well.

As mentioned earlier, map matching, in addition to snapping position to the road network, gives current speed limit, street name, direction. While current implementation of hooking map matching is rather primitive and only good for testing it, I have been rather pleased with the results. Snapping to the road works quite well, speed limits in many places (NB! not all) are accurate, street names are well detected.

I looked around on how this info can be shown and tried to piece something together, as shown on attached screenshot. Here, menu button is replaced with speed/time to destination/distance to destination. That rectangle if clickable, as the one above. On top, the current road or street is shown, if detected. The map was blown up by using scaling 2x in the preferences and was rather nice to use while driving (normally I use it at 1x).

As you can see, I miss proper speed limit sign (anyone to chip in?). Right now its just shown in red. The other elements were shifted out of the way, for testing the other elements. While driving, I was missing ETA, would like to add it (top right?). North arrow and scale were actually useful to have, so would like to keep them too. As for fancy speed widget, not sure where (or if) to fit it.

All in all, its early days and with this work I mainly wanted to get the feedback and ideas/schemes on how to proceed. Then we would have to figure out how to integrate different modes of operation into WhoGo Maps, but that would be easier if there is a working prototype.

I am planning to work on map matching further and expose it properly. After that, would like to come back and work on the car navigation mode.

Re: WhoGo Maps
 

look like landcape mode will more afected on visibilty.

Re: WhoGo Maps
 

Forgot to mention it - I am sure we will have to design separate landscape and portrait modes. I am used to portrait now, so started there.

Re: WhoGo Maps
 

If feasible, I would let the user decide if showing the scale and the north arrow; they may be useful to some and not to someone else.
(What's the C symbol? Copyright? )
Good job!