Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tapio

Pages: 1 [2] 3 4 ... 7
16
Was so ein Regen Tag alles gute hat. Jetzt endlich mal mit dem Tasker, autoinput und autovoice auseinandergesetzt. Dank google und sehr vielen Übersetzungen nun zum Ziel gekommen.

Habe es geschafft damit Tasker die Taste erkennt und autovoice auf Empfang schaltet. Dann spreche ich meine Befehle, diese erkennt autovoice und löst den Task aus um einen Punkt mit einem bestimmten Namen in Locus zu screiben. Es könnte aber auch jeder andere Befehl umgesetzt werden.
Habe ein Video aufgenommen wo man das sieht. Leider ohne Sprache, da sonst die google Spracherkenung nicht mehr funktioniert (das hat lange gedauert bis ich da drauf gekommen bin) Video und Erklärung folgt gleich
The following users thanked this post: tapio

17
Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 04, 2019, 06:24:21 »
Is there a change in action task track record stop with "autosave = on" and no name (don't know if this is relevant). It now gives a track save dialog, before it just silently stopped and saved the track.

Gesendet von meinem D5503 mit Tapatalk

The following users thanked this post: tapio

18
schau mal nach dem nächsten Update ob jetzt alles passt ;)
The following users thanked this post: tapio

19
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 30, 2019, 15:32:16 »
I fight with the custom setup of language since we changed app format (since 3.38 version). Still not perfectly solved ... little weird that with the latest two Beta versions, there was no change. Anyway, I'll test it rather once more, thanks @balloni55.

@tapio
problem with centering does not happen in Beta, right?

@Andrew Heard
Not sure if this is equivalent. Maybe consumption will be a little less than during movement. One thing is internal sensors (rotation, gravity etc.) and second thing is that equitation to compute GPS location often works on iteration method and when you do not move, location does not change => compute is faster => less consumed energy. Just guess.
The following users thanked this post: tapio

20
"style" (missing in your reference)
Thanks, added it
Anyway because MF project seems not to be dead like in times I started to write own modded version, I'll instead contribute changes back to the official version.
Good news :-)
BTW, are you planning to update the V4-maps engine to mapsforge 0.12.0? This finally adds curved path text rendering, which is great for street names:
https://github.com/mapsforge/mapsforge/pull/1112#issuecomment-477969418
The following users thanked this post: tapio

21
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 03, 2019, 10:40:26 »
Just want to say that applying presets to routing preferences, and resetting afterwards, is a stroke of genius. It's suddenly made presets really useful. Well done.

Sent from my moto g(6) plus using Tapatalk

I just wish it was possible to choose map in presets and not only the theme ........
The following users thanked this post: tapio

22
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 28, 2019, 07:32:59 »
@tapio
Now it works that right at the start of navigation, settings that are included in automatic preset are saved (made a backup) and at the moment you end navigation, old settings are restored.

@Žajdlík Josef
ah thanks, it seems to be small down-arrow that should be on the right side. I'll look at it.

@balloni55
it is possible (issue with the icon). Main start activity of Locus Map has changed in Beta so this switching cause this small mess.

Geocaching: 25kb looks still little hight to me, but as I wrote, maybe you have too much trackables in your inventory?
Favorite point ... I think that upload of draft and also offline logging does not support favorite points (on gc.com side). Hmm maybe I should add some note about this into app ... thanks.
The following users thanked this post: tapio

23
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 27, 2019, 12:38:06 »
Oki, it's there ... new Beta 3.39.3.4 ... hmm it's the incorrect name because it is already based on 3.39.4. Sorry, should be 3.39.4.1.

One nice additional feature from yesterday > new settings in navigation. Enjoy it ;).
The following users thanked this post: tapio

24
Ich habe jetzt mal Autohöfe, Rasthöfe, Picknickplätze und Parkplätze teils etwas bereinigt und vor allem nach UTF8 umgewandelt, damit die Umlaute nicht verkorksen.
Im Anhang ein zip mit den genannten als GPX. Klappt im Locus.
The following users thanked this post: tapio

25
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 24, 2019, 08:30:43 »


Awesome new Beta, because you seem to have fixed the text problem over more than one tile! Haven't seen any more broken text yet!
.3 beta no more broken text, I did not find one anymore.



Inviato dal mio SM-A520F utilizzando Tapatalk

The following users thanked this post: tapio

26
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 04, 2019, 15:23:37 »
@tapio
hmm using OAM for some days and did not yet notice any problems, but thanks, I'll be watching it.

Main menu: menu, as well as the whole layout of the main screen, is in process of a redesign for new Locus Map version. I'll keep in mind huge screens. Anyway recording panel will remain as is, so I've added two more possible number of items here.

@Mips
no, no change.

@Christian
And when you now insert description, after save it is still empty? Are there exact steps I may follow to simulate it?
The following users thanked this post: tapio

27
Hi tapio,

I am no Huawei user but I found this or this in Locus Helpdesk.

And you can check this page or this page.

c.s.g.
The following users thanked this post: tapio

28
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 03, 2019, 08:53:16 »
@tapio
hmm really weird. I do not see a problem in the app, but on a few places, I've set to completely "ignore case", so hopefully it will help here.

The system is pretty simple ... for every vector MapsForge map Locus finds, it replaces it's ending from ".osm.map" to ":osm.db" and search for this file. It does not matter what map version it is.

And complicated usage of POI.db? May only confirm. It is one of the top priorities to a more radical change in next months.

@michaelbechtold
nice. Just tested it and indeed, Arndt correctly returns required time parameters for segments between route waypoints!
The following users thanked this post: tapio

29
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 01, 2019, 22:55:11 »
Naming convention is: <country>.osm.map and ...osm.db
The following users thanked this post: tapio

30
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 01, 2019, 14:40:22 »
@tapio
I do not agree. Some value "30 s" has nothing to do in UI. Firstly, no one should be interested in such value. The app works or not, that's the point. I told you this to give a better overview of what happened under the hood. And secondly, I really plan to make this value more dynamic, so there won't be a single "30-sec" value.

POI database should work the same, no matter which map version you have. Do you have correct naming, same as your map?

@Graf Geo
does problem with recalculation in the field happen also when the screen is on? Because if you have Android 8.x, there is a possible problem on some devices in case, the screen is turned off.

@Mips
agree that fake GPS or any similar app is definitelly better and more robust system how to test. But, a lot more complicated (more steps).

Travel time: you mean travel time at bottom panel? In case of GraphHopper routing, times on route segments is estimated on their server. From my experience, they are usually quite precise.

In case of BRouter, there are no time and Locus Map know absolutely nothing about the route itself (surface, city/highway, ...). Just a routing type and is able to compute elevation. So app internally records your traveling speed during track recording or navigation for known activity and then use this average speed for a time estimate. Time is something like an "average" from the last 60 minutes. So these times are usually fine for a hike, where your speed is around the certain average value. In case of a bike, it may be worst mainly if you change a surface or bikes. In case of the car, these values are usually useless, mainly if you combine hour of a ride over the city and then you plan route over highway :). Hope my explanation is clear.
The following users thanked this post: tapio

Pages: 1 [2] 3 4 ... 7