Active Topics
-
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 1 day, 15 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 2 days, 12 hrs ago - more...
| The Following 5 Users Say Thank You to rinigus For This Useful Post: | ||
 |
|
2018-08-28
, 12:33
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#52
|
Thanks, rinigus, that really helped. Searching for the same address that had been giving me crashes all morning now takes about 40 seconds. Search and route to the same address 50 seconds. With OSM Scout used for everything. Tried a different destination, similar results. Thank you, I am happy again!
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
| The Following 6 Users Say Thank You to pichlo For This Useful Post: | ||
|
|
2018-08-28
, 13:40
|
|
Posts: 248 |
Thanked: 1,142 times |
Joined on Dec 2014
@ Earth
|
#53
|
Originally Posted by rinigus
We need somebody to hack something along these lines using a canbus connector (PiCAN, etc.) :-P
The alternative would be to switch to car's speedometer, compass, and from these try to predict the motion.
Originally Posted by DrYak
And I've forgotten to give my positive feed-back about the experience.
2. Foreign-language street names :
The protuguese-speaking region (with the names badly garbled by the text-to-speech) I was visiting was Madeira, a volcanic Island (with very steep terrain)
Compared to the experience with a commercial GPS system (Tomtom), using Pure's WhoGo predecessor had a few very positive outstanding points :
- thanks to using OpenStreetmaps data, a lot of the streets on the map had the correct metadata regarding practicability/speed limitations, meaning that the whole software stack was always able to advise the best route.
Meanwhile, the commercial data used by Tomtom was lacking (despite having the latest map update installed), most of the street where "just" edges between two nodes on the map with not enough meta data. That meant that sometime, in the steep terrain, instead of advising to stay on the main road that goes up in twists, the tomtom would advise to cut short through some tiny barely driveable path.
No such problem with WhoGo.
- the spoken routing instuctions by valhalla makes a bit more sense : when on a mountain main road that slowly climbs in twists, often they are side paths leading to houses.
On lots of satnavs (including the above mentioned Tomtom), the driving instruction would be something like "at the intersection, turn right", as if at a crossing between two main roads. (that happens even in regions where the map data is more complete).
On pure maps, the instruction is a bit more logica similar to "turn right to remain on {main street name}" (making it clear that you follow the main road on it twist and avoid taking a small side path).
TL;DR: the current opensource native stack on Sailfish, thanks to Pure/WhoGo, OSM Scout, and the various libraries behind is actually a very smooth experience that's rather competitive with some commercial offering.
Kudos to all people involved in it.
|
|
2018-08-28
, 14:05
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#54
|
Originally Posted by DrYak
I can confirm, I noticed that too driving on English country roads. I found that a very nice feature.
On lots of satnavs (including the above mentioned Tomtom), the driving instruction would be something like "at the intersection, turn right", as if at a crossing between two main roads. (that happens even in regions where the map data is more complete).
On pure maps, the instruction is a bit more logical similar to "turn right to remain on {main street name}" (making it clear that you follow the main road on it twist and avoid taking a small side path).
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
| The Following 5 Users Say Thank You to pichlo For This Useful Post: | ||
|
|
2018-08-28
, 14:11
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#55
|
Originally Posted by pichlo
That is thanks to Mapzen work on Valhalla
I can confirm, I noticed that too driving on English country roads. I found that a very nice feature.
| The Following 9 Users Say Thank You to rinigus For This Useful Post: | ||
 |
|
2018-08-28
, 19:44
|
|
Posts: 304 |
Thanked: 1,246 times |
Joined on Aug 2015
|
#56
|
@pichlo, @rinigus, WRT issues when searching a location and crashes / presumed OOM situations (as described by @pichlo):
As I had issues with the location search using OSM Scout Server (online services were always working fine) in the past (with Poor Maps / WhoGo Maps), I was eagerly reading this conversation and spontaneously tried to reproduce the experience.
While my use cases and usage is lighter than @pichlo's, my configuration is a bit "heavier":
For me the only sore point on Jolla 1 phones is the stability of the TTS navigation (as discussed on Github and TMO).
Last edited by olf; 2018-08-28 at 20:41.
As I had issues with the location search using OSM Scout Server (online services were always working fine) in the past (with Poor Maps / WhoGo Maps), I was eagerly reading this conversation and spontaneously tried to reproduce the experience.
While my use cases and usage is lighter than @pichlo's, my configuration is a bit "heavier":
- Jolla 1, SFOS 2.1.4, OSM Scout Server 1.9.1-1.76.1, recent Pure Maps
- Maps: OSM Scout Car Day English (vector)
- Navigation: Valhalla, 128 MByte cache (default)
- TTS engine: picotts
- Maps downloaded: NL, BE, LU, various DE states
- Search: Geocoder-NLP
- NLP languages: de, en, fr, lb, nl
- AlienDalvik is running, including two Android background tasks
- I have not experienced crashes of Pure / WhoGo / Poor Maps or OSM Scout Server, as @Fellfrosch already indicated.
When I drive the Jolla 1 phone ("sbj") into an OOM situation, e.g. by starting a fat Android app (Firefox works well) while using Pure / WhoGo / Poor Maps with OSM Scout Server, SailfishOS handles this as usual: UIs (OS & apps) become very unresponsive and SFOS regularly states "App XYZ is not responding. [Wait | Close]". - With above configuration and no other apps started, System Monitor shows ca. 630 MByte RAM and ca. 180 MB Swap used when browsing maps, searching for locations etc. in Pure Maps with OSM Scout Server (might be even less on a freshly rebooted device, it had an uptime of 4 days while testing).
That is absolutely fine, Firefox alone consumes about the same amount of memory and one can still run a few smaller apps (regardless, if native or Android ones) concurrently. - In the past, location searches with libosmcout worked fine, albeit really slow (usually >> 1 minute), while I had trouble using Geocoder-NLP (not: "Valhalla") for location searches (except when submitting the full, comma separated, simple format: <House number>, <Street>, <City>), regularly running into "No results" (which rather looked like timeouts) after more than a minute of searching.
@rinigus made me aware, that I still had "loading of libpostal on each call" switched on from past tests; switching it off made Geocoder-NLP's (not: "Valhalla's") location search consistently returning 25 really good matches within 30 to 40 seconds (as @rinigus expected). Aforementioned RAM usage does not significantly change, while doing this.
For me the only sore point on Jolla 1 phones is the stability of the TTS navigation (as discussed on Github and TMO).
Last edited by olf; 2018-08-28 at 20:41.
| The Following 8 Users Say Thank You to olf For This Useful Post: | ||
|
|
2018-08-28
, 20:04
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#57
|
Originally Posted by olf
@olf: thank you for detailed report! Just a small correction - OSM Scout Server uses GeocoderNLP or libosmscout for search. Valhalla uses the coordinates returned by the geocoder - this is done automatically for you in Poor/WhoGo/Pure Maps before calculation of the route.
In the past, location searches with libosmcout worked fine, albeit really slow (usually >> 1 minute), while I had trouble using Valhalla for location searches (except when submitting the full, comma separated, simple format: <House number>, <Street>, <City>), regularly running into "No results" (which rather looked like timeouts) after more than a minute of searching.
@rinigus made me aware, that I still had "loading of libpostal on each call" switched on from past tests; switching it off made Valhalla's location search consistently returning 25 really good matches within 30 to 40 seconds (as @rinigus expected). Aforementioned RAM usage does not significantly change, while doing this.
| The Following 6 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2018-08-28
, 20:51
|
|
Posts: 6,445 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#58
|
This is all really interesting. One question, why is search so slow? As mentioned before, search alone ~40s, search+route ~50s. I tried route only, to a point on the map, it took ~7s. I would expect a search to be virtually instantaneous and routing to take some time. It seems to be the other way around.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
 |
|
2018-08-28
, 21:02
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#59
|
Originally Posted by rinigus
Some pages back (or was it in OSM thread?) i suggested to look into OBDfish for reliable speed data when gps is not available. It would be so cool if pure maps could pick up some data from a running obd fish instance and do magic no nav app has done so far(?).
The alternative would be to switch to car's speedometer, compass, and from these try to predict the motion. I think that could come one day to Qt, if it hasn't done yet, but for the car industry mainly.
So, unfortunately, its a bit too far at foreseeable future.
Taking exits in tunnels is much more complicated though, i concour.
Sadly the turn indicator is not hooked to any ECU even in modern cars, so it is not accessible via obd2.
But it is mostly not necessary because i rarely remember having to take multiple exits in one continuous tunnel.
The most common situation are tunnels with some exits that leave out of the tunnel so the the signal would be picked up again when leaving and then correct the displayed position.
Most vital is the info when to exit/turn for the first time.
If you don't mind, i would love to ship an obdfish compatible ELM bt adapter to your door if you do not already have one. Just pm an adress in that case, i would direct an aliexpress shipment to you.
Another completely different thing that came up during my drive from frankfurt to cologne today.
Why does no nav app display the distance to a speed limit?
For "fuel conservation" it is quite nice to know there will be a speed limit around the corner and it thus makes no sense to give full throttle for an overtake you will not finish. Or going fast and not having to waste precious brakes but gently roll out to allowed limit some hundret meters earlier (e.g.).
I checked in all common android apps, no one is doing it. I would love to see info about speed limits ~1km before reaching them. Or depending on speed, some sane amount of seconds before.
Thanks for your verbosity! This is an awesome thread to follow.
__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
| The Following 7 Users Say Thank You to mosen For This Useful Post: | ||
 |
|
2018-08-28
, 21:10
|
|
Posts: 173 |
Thanked: 512 times |
Joined on Jul 2018
@ Guatemala
|
#60
|
over RAM everything is going slow, SWAP is just to keep alive the task.
what happen with ZRAM is this available to jolla p1? if yes this will help with poor RAM.
Last edited by carlosgonz; 2018-08-28 at 23:22.
what happen with ZRAM is this available to jolla p1? if yes this will help with poor RAM.
__________________
Nokia N95 / Nokia N900 / Nokia N9 / Nokia N8 / Jolla 1 / Jolla C / Xperia X / Xperia 10 II / PinePhone / Librem 5
TI Chronos
Nokia N95 / Nokia N900 / Nokia N9 / Nokia N8 / Jolla 1 / Jolla C / Xperia X / Xperia 10 II / PinePhone / Librem 5
TI Chronos
Last edited by carlosgonz; 2018-08-28 at 23:22.
* start OSM Scout Server
* get into its Settings. Choose there GeocoderNLP settings (button towards the bottom)
* in GeocoderNLP, enable the loading of libpostal on each call.
In theory, it should increase search time. But in your case, I have no clue how it will work. Your search times are already too long, but let's test this case.