Locus Map - forum

Development => Android versions => Locus Classic (LM Free, LM Pro) => Topic started by: Menion on July 31, 2018, 13:19:59

Title: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on July 31, 2018, 13:19:59
Important links
- blog post (http://www.locusmap.eu/news-version-3-32-0) about major version
- list of news (http://help.locusmap.eu/announcement/version-3-32-31-7-2018) of public versions

Versions
31. 7. 2018 - Locus 3.32.0
4. 8. 2018 - Locus 3.32.1
6. 8. 2018 - Locus 3.32.2
7. 8. 2018 - Locus 3.32.2.1 - BETA
17. 8. 2018 - Locus 3.32.2.2 - BETA
31. 8. 2018 - Locus 3.32.2.3 - BETA
7. 9. 2018 - Locus 3.32.2.5 - BETA
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 01, 2018, 10:21:35
Hi Menion, the new time estimation in route planner. It is very conservative. In flat areas it assumes I walk < 3km/h,which is way too slow. I use brouter. Can I configure it? Thx

It detected, after a second start, a change in the file system, but I did not change anything. I just confirmed, it works, but makes me nervous.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: chrobak.truhlik on August 01, 2018, 11:10:12
I can confirm the same thing as a tapio . Every second start of the app i see "it a change in the file system", but I did not change anything. I just confirmed, it works. Android 7.1.1
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: zossebart on August 01, 2018, 11:21:43
I think for the ETA to work correctly with Brouter, we need a new version of Brouter app, right? The commits for Locus ETA on Brouter github are from 8th of july, but no official version with the changes is available. Do we have to ask Arndt for a new version?

Gesendet von meinem D5503 mit Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on August 01, 2018, 13:03:02
QuoteClick on "download" button does not work on your Android 6.x? Hmmm, have to try it, thanks

with PRO V3.31on same device it work well
now with V 3.32.0  FREE as well as PRO i can´t download needed BRouter data :-[ with both of my devices
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 01, 2018, 21:04:23
Where is the confirmation for 'quit Locus' gone??? The new green toast 'tap twice to quit' is not enough.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 02, 2018, 17:43:22
This year, I have feeling that I only solve problems, interesting and little frustrating. We tested new login system that is provided by Google itself for almost two months, even published Free version week ago, just for sure, but still some weird problems appear and we are with Petr second day try to find any working solution for something, that clearly does not work on Google server, stupid ... so sorry to you, affected by problems with login to Store :(.

To problems (thanks for reports!)

@tapio
time estimates will be improved in next version. Expect better times when using online GraphHopper. In case of BRouter, times will be based on your own movement for certain activity (mainly time spend in navigation with certain routing).

@balloni55
clickable buttons in toasts will be fixed in next version, finally. I had to change this system and use special new component which should allow displaying really clickable buttons on all devices.

@Christian
why you need this confirmation dialog? We removed it as non-standard, useless feature. Does it have any possitive effect on usage of app for You?

New version? Most probably tomorrow ... little risky before the weekend, hope it will be better than this one!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: TimoG on August 02, 2018, 18:39:50
A new BUG:

Can't create geocache waypoint.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 02, 2018, 19:44:10
Should be solved: http://help.locusmap.eu/topic/impossible-to-add-waypoint-to-geocache-anymore , thanks
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Henk van der Spek on August 02, 2018, 19:51:59
Quote from: menion on August 02, 2018, 17:43:22
......

@Christian
why you need this confirmation dialog? We removed it as non-standard, useless feature. Does it have any possitive effect on usage of app for You?

......

In 3.31.3 it still functions but now I understand that is because the setting (was under Miscellenaneous) was not "resetted".
I am going to miss that one since I often use the back button of the phone instead of the left arrow in the topbar. (As does my wife).
The confirm option (with a cancel button) often prevented the accidental closure of Locus for us. Since guiding and navigation are not saved upon closure of the APP it is a real step back for us.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 02, 2018, 21:45:03
Hmm and you press "back button" so frequently when you return to map screen, that you press it even two twice more (necessary to close the app) then you wanted?
I have to say that rarely when in hurry, I also close app itself, but when within 1 or 2 secs I again tap on icon of the app, it continues without problem.

Also (and mainly) in case, some service is running ( like recording, navigation, etc.) , dialog still appear!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Henk van der Spek on August 02, 2018, 22:12:12
Good to read this! Thanks you. If you add Guiding to this group of services that notify me before closing Locus, I will sleep even better.  :) (and upgrade after the next hiking holiday).

Verstuurd vanaf mijn Armor_2 met Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Viajero Perdido on August 02, 2018, 22:12:57
I don't mind the lack of a confirmation on exit (never used it, if it was available), but could understand why some people might like it.

But no big deal for me.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 02, 2018, 22:48:02
Quote from: menion on August 02, 2018, 17:43:22@Christian
why you need this confirmation dialog? We removed it as non-standard, useless feature. Does it have any possitive effect on usage of app for You?
The dialog prevented unwanted exit by tapping back buttons by accident with wet fingers, gloves or when out of breath and have shaking fingers. To have to restart Locus in the wild when i only wanted to have a look on the map is a real PITA and should not happen at all.
I could not find any user request to remove this nor a poll either.
The confirmation dialog is an essential thing in Locus like running as a service imho. So please bring it back.
Thank you for understanding.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on August 03, 2018, 03:59:37
+1
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Bucky Kid on August 03, 2018, 11:16:27
Hi, I notice some trouble with 3.32.0.
It seems not remembering properly the location of data folder root. After initial scanning it offers me available locations where I confirm the first (/sdcard/Locus/) and tick the box to don't ask again, however on other run it scans and asks again.
Now I'm back to Locus 3.31.1 and it handles storage location correctly.

Another minor dislike on new version is the missing confirmation on exit. Double tap back button can easily mismatch with long tap which is preset for forced close and loss of unsaved data.

________________________
Sent from my phone using Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: locus.sv@heime.org on August 03, 2018, 11:42:36
Bucky Kid: How do you roll back to 3.31.1 version?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Stargaterunner on August 03, 2018, 11:47:54
Download V3.31.3 See here:
http://help.locusmap.eu/topic/locus-store-not-working-with-google-account#comment-61170
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Bucky Kid on August 03, 2018, 11:48:40
Quote from: locus.sv@heime.org on August 03, 2018, 11:42:36
Bucky Kid: How do you roll back to 3.31.1 version?
I have backup in Titanium Backup
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: tramp20 on August 04, 2018, 12:48:02
Quote from: Bucky Kid on August 03, 2018, 11:16:27

It seems not remembering properly the location of data folder root. After initial scanning it offers me available locations where I confirm the first (/sdcard/Locus/) and tick the box to don't ask again, however on other run it scans and asks again.

I just wanted to write this bug here too:-)
I have this on 3 smartphones almost on every start of pro and free since the latest version.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 04, 2018, 12:59:54
Yes, the filesystem message makes me very nervous, I don't want to spend time setting anything up again.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 04, 2018, 16:35:47
Hello guys,
new version 3.32.1 was a while ago published on Google Play. Hope this issue is fixed.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: tramp20 on August 04, 2018, 16:42:02
Thank you, file system is fixed.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 04, 2018, 16:48:57
17km in 6 hrs is still unrealistic ETA. Thx for the update btw.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 04, 2018, 17:05:41
"Filesystem is fixed", perfect!

Times in planner: please, as first step, suggest to use GraphHopper and in this case, also suggest to check values on their web site if they are correct in Locus: https://graphhopper.com/maps/
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: JoxM on August 04, 2018, 17:32:51
Latest version not tested yet, but I would like to have this confirmation button back, too.
Today I was out looking for some caches and it happened twice that I existed the app while going back a little bit too fast. Very annoying...
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 04, 2018, 17:36:16
From: 51.351619,7.699465
To: 51.344583,7.740034

Graphhopper: 42m
Loc/Graphhopper: 1h14

Edit: Maybe hiking profile = walking profile.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Henk van der Spek on August 04, 2018, 18:40:23
Locus + Brouter: 1h14 incl. 10 m rest. So, netto 1h04m. Not too bad I think.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: TimoG on August 04, 2018, 20:40:37
BUG geocache waypoint:

New geocache waypoints can now be created. However, the changes (such as name or icon) are not immediately displayed. You you have to close the cache first and then call it again.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on August 05, 2018, 02:50:37
Test of Locus Pro+BRouter Route Planner ETA: quite good result in my first test. Well done @menion.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 05, 2018, 07:36:29
Quote from: Andrew Heard on August 05, 2018, 02:50:37Test of Locus Pro+BRouter Route Planner ETA: quite good result in my first test. Well done @menion.
Du you have an example? What brf files do you use, maybe you can upload one? I get good results for 90 year old people. 3 km/h in flat areas. Is the ETA depending from something inside the brouter brf files maybe?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 05, 2018, 08:33:52
I cannot save tracks from route planner any more. Buttons at the bottom are missing. In fullscreen mode, old story.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 05, 2018, 08:37:48
@tapio
I'll check your different web vs Locus ETA, thanks.

ETA times computed by BRouter are currently completely computed by Locus itself. If you, for example, pick "bike" as routing profile, Locus has internally stored your average speed for bike activities (navigation, track recording) and use this average speed. This avg. speed is computed from last cca 1-2 hours of this activity. It will be quite precise if you still move on the same terrain & same speed. Otherwise, it may take a while till your speed adapts to new conditions. Consider as first test version ... :).
In the case of GraphHopper ... these values are completely computed on the web server of GraphHopper. Here I can imagine to use also your average speed and compare it to expected values and modify it the little bit as well. This later.

@TimoG
thanks, I'll check it
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 05, 2018, 10:09:43
Ok. Average speed from my tracks is not perfect. I was in the mountains recently, with very low average speeds, because we had at max. 1400m elevation change per day and 1-2 km/h speed at times.

I think you just let us define climbing/descending/flat speeds. You already know the different ETA formulas, because it always has been in the track options... Thanks for your hard work!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on August 05, 2018, 12:13:20
Hi Menione. If I use a Brouter with my own routing profile in the Route Planner, is the route time not counted? It would agree that Locus calculates value-based activity. But with his own routing profile he probably does not know what activity to use. Personally, I do not mind, it's just a question.

CZ: Ahoj Menione. Pokud v plánovači tras použiji Brouter s vlastním routovacím profilem, tak se čas trasy nespočítá? Souhlasilo by to s tím, že si Locus vypočítává hodnotu na základě aktivity. Jenže s vlastním routovacím profilem asi neví jakou aktivitu použít. Osobně mi to nevadí, je to jen dotaz.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 05, 2018, 13:17:15
A good time for reminding of poutnikls ETA calc proposal: http://forum.locusmap.eu/index.php?topic=5176.msg45502#msg45502
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 05, 2018, 21:44:36
Not a bug report just for information about power saving mode of my device.
Today I tested the battery saving mode on the a5 2017 Samsung.  Mid power saving mode with locus excluded from it I recorded a track.
Locus was working correctly but it did not had any response from gps, I could fix a point only when watching the map so not in background. I disabled power savings without stopping the recording and all went ok.

I think in this mid power saving mode only the foreground app have access to gps.
Now I know it I will not use it anymore.
Power saving not Locus

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on August 06, 2018, 02:02:55
Quote from: tapio on August 05, 2018, 07:36:29
Du you have an example? What brf files do you use, maybe you can upload one? I get good results for 90 year old people. 3 km/h in flat areas. Is the ETA depending from something inside the brouter brf files maybe?
@tapio - example in Australia so may not be of use to you? "ordinary" downloaded BRF file. I can send track GPX & link to BRF if useful? Saving tracks - no problems for me. I have no idea how ETA is calculated, maybe based on selected profile - it seems quite good (PS. @Menion earlier reply confirms my experience).
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on August 06, 2018, 02:09:00
Quote from: lor74cas on August 05, 2018, 21:44:36
Not a bug report just for information about power saving mode of my device.
Today I tested the battery saving mode on the a5 2017 Samsung
@lor74cas - thanks for report - I have just bought this phone so am hoping no power saving problems with Locus.
I note has inbuilt barometer - do you find the ascent measurement more accurate than a phone without inbuilt barometer?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 06, 2018, 07:30:32
Quote from: Andrew Heard on August 06, 2018, 02:09:00
Quote from: lor74cas on August 05, 2018, 21:44:36
Not a bug report just for information about power saving mode of my device.
Today I tested the battery saving mode on the a5 2017 Samsung
@lor74cas - thanks for report - I have just bought this phone so am hoping no power saving problems with Locus.
I note has inbuilt barometer - do you find the ascent measurement more accurate than a phone without inbuilt barometer?
I use light filter in combination with automatic gps calibration with good results. I also use hgt files with 1 arc accuracy.

Compared to the old s5 mini it's really more accurate, but elevation seem to not be exact science: every device, every app can give you different values, now I'm happy to have values near to what expected when planning my trips.(https://uploads.tapatalk-cdn.com/20180806/8ec38a242c2283b798c277afb8394515.jpg)

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 06, 2018, 09:18:45
@tapio
setup of "climbing/descending/flat speeds" is overkill, nothing like this will happen. I'm sure I'll be able to improve the algorithm to be clever enough even without these parameters.
Anyway thanks for pointing to poutnik's algorithm, I'll definitely read it once more.

@Žajdlík Josef
every BRouter profile is based on either car, bike or foot. Generally, every routing profile in every router belongs to one of these three categories. So no matter what custom profile you use, it will always be in one of three groups.

@lor74cas
battery saving mode is always ... "wrong" for GPS usage

Anyway I'll always suprised that my overcomplicated altitude system return quite good elevation values. Nice :)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 06, 2018, 10:59:18
Quote from: menion on August 06, 2018, 09:18:45
@lor74cas
battery saving mode is always ... "wrong" for GPS usage
Anyway I'll always suprised that my overcomplicated altitude system return quite good elevation values. Nice :)
I think your system of high complexity is used by the sapcex project, you have to try to ask them for money or a tesla in exchange for your code. ;)
I think the altitude manager needs some simplification once we find the way we have the best results.
We have these use cases:
A) no srtm - no baro> ok user do you want to download the srtm data to improve the altitude data? Yes (B) - No ok good luck I hope you are running by the sea, do not bother me for inaccurate elevation data :)

B) srtm - no baro> altitude assisted by srtm by default (I do not know which filter is the best solution)

C) no srtm - baro> ok user do you want to download the srtm data to improve the altitude data? Yes now (D) - No ok I hope you are by the sea, where you can calibrate your baro at 0 mt or do not bother me for inaccurate elevation data :)

D) srtm - baro> srtm and active baro in car with light filter

Any other configuration in an advanced menu (manual offset, geoid, nmea, calibration ...), is just my opinion, but emerges from the face of the frightened users I saw while watching the altitude manager (wife, friends, colleagues)

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on August 06, 2018, 11:52:28
Quote from: menion on August 06, 2018, 09:18:45
@tapio
every BRouter profile is based on either car, bike or foot. Generally, every routing profile in every router belongs to one of these three categories. So no matter what custom profile you use, it will always be in one of three groups.

So it might be a problem maybe that my profile is older. The time on the route is empty. As I wrote, I personally do not mind, but if you want to explore it for other users, then I attach the SCR and also the used profile.
profil: https://drive.google.com/open?id=0B2JefmdshiwpaUxZaExseXhZOEE

CZ: Tak to by mohl být problém možná v tom, že ten můj profil je staršího data. Čas na trase mám totiž prázdný. Jak jsem psal, osobně mi to nevadí, ale pokud bys to chtěl prozkoumat kvůli jiným uživatelům, tak přikládám SCR a taky ten použitý profil.
(https://s15.postimg.cc/8mx7q0n6v/Screenshot_20180806-112737_Locus_Map.jpg) (https://postimg.cc/image/8mx7q0n6v/)

(https://s15.postimg.cc/3o9pbhr3r/Screenshot_20180806-112745_Locus_Map.jpg) (https://postimg.cc/image/3o9pbhr3r/)

(https://s15.postimg.cc/9p7e8klfr/Screenshot_20180806-112753_Locus_Map.jpg) (https://postimg.cc/image/9p7e8klfr/)

(https://s15.postimg.cc/4dshnv72v/Screenshot_20180806-112810_Locus_Map.jpg) (https://postimg.cc/image/4dshnv72v/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Condor on August 06, 2018, 15:37:41
Return home from vacation and trip ...
Somewhere in the middle I gave up an online log ...
Today, for more than 7 hours, I have been posting logs, posting more. It's all there is. . . .
I have to control 140 logs that have passed and which are not. Skips the TB log, the attached photo of 400 has passed about 300. So all logs go through a manual check. Add Missing ... Can not insert in order. So the gallery is in the wrong order. Chronology is in. . . .
Patience comes to me ...
Locus does not report a bug! Do not send TB and from 15 photos go 10 and no announcement! Terribly bad.
Locus became totally unreliable.
(3.31.3)

The new version did not have the courage to risk the route.

P.S.:
The only thing I can think of ...
Either I go back to some version of 2014-15.
Or it is time to think (Menion) or it could be possible to generate a functional "Lite" version of Locus.
Only maps, points, navigation, geocaching.

Without trainers, sensors, bicycles, Fitnes, LT, chat, health records, Boats, planes, heart transplants .... and I do not know what's all in Locus.

Yes I understand ... Locus is a multifunctional application.
But if the base function is not working reliably, it is unusable for a large group of people and we will have to look for a reliable alternative application.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 06, 2018, 16:15:41
Quote from: menion on August 06, 2018, 09:18:45
@tapio
setup of "climbing/descending/flat speeds" is overkill
OK! Hey, Locus already does calculate decent ETAs internally for the temporary track... and also offers it in route planner (Menu -> Travel time) - There is "Bergwandern (mountain hiking)" which would be more appropriate for me for display in the bottom bar.

BTW as you probably know, Germany has a norm for this (DIN 33466):

Up: <u> meters
Down: <d> meters
Horizontal: <h> meters

Conservative assumption - the hiker walks per hour:
300m up
500m down
4km horizontal

Calculation:
a = u/300 + d/500
b = h/4
c = greater value of a and b
d = smaller value of a and b

Walking time: (0.5*c + d) hours
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 06, 2018, 17:56:22
Quote from: tapio on August 06, 2018, 16:15:41
Quote from: menion on August 06, 2018, 09:18:45
@tapio
setup of "climbing/descending/flat speeds" is overkill
OK! Hey, Locus already does calculate decent ETAs internally for the temporary track... and also offers it in route planner (Menu -> Travel time) - There is "Bergwandern (mountain hiking)" which would be more appropriate for me for display in the bottom bar.

BTW as you probably know, Germany has a norm for this (DIN 33466):

Up: <u> meters
Down: <d> meters
Horizontal: <h> meters

Conservative assumption - the hiker walks per hour:
300m up
500m down
4km horizontal

Calculation:
a = u/300 + d/500
b = h/4
c = greater value of a and b
d = smaller value of a and b

Walking time: (0.5*c + d) hours


Interesting algorithm, I tried to insert my current trailrunning data and return a satisfactory ETA. Maybe the fatigue factor is missing, as the number of kilometers increases or the difference in height takes over the fatigue that makes slowing down, while the proposed formula is linear, the reality is a curve.
Obviously you have to compare similar data to get reliable results, you can not enter a time on 100 meters to look for time in the marathon.
However, it has a very good approximation to reality, thanks.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 06, 2018, 18:29:19
Tapio was faster then me. The hint for the DIN in Germany and for the original Swiss Standard is here on the right place. Thank you for this.
I have a huge database with all my activities including times and elevation, distances etc. And also a simple tool in Excel to calculate the needed time based on the DIN Standard. Computing the average of the appropriate values of my tracks from my db leads always to wrong values, only the values computed from the DIN are right.
The ETA value in Route Planner are always empty in my case because mostly i use a mix of profiles and sometimes the designed tracks are from Brouter Web or i use profile "hiking beta" oder another custom profile template for mountain biking. So no information about the used profiles are available / reliable and the ETA function are not available to me :(

I want Locus to be the "Swiss knife" for my purposes = all-in-one tool. The ETA / needed time is one of the key features i need for planning my routes. Just now i do this within an Excel sheet (and link / compare the values with the time between Sunrise / Sunset <- this idea is free of charge for menion). I would like to have this stuff inside Locus and in a way that work (from within the first track). So @menion, please check the Standard and check your algorithm. Please give us the overkill of "setup of climbing/descending/flat speeds" because it is the only way to get reliable values. Thank you.

For those who are interested in the meantime in calculation. xls or online (https://www.ksuppan.at/cms/bergtouren/bergtouren-nuetzliche-infos/128-gehzeit-bereichnen.html)
I adapted the values in the xls sheet for biking, trail running a.s.o. Works fine.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 06, 2018, 18:35:40
Quote from: lor74cas on August 06, 2018, 17:56:22
Interesting algorithm, I tried to insert my current trailrunning data and return a satisfactory ETA. Maybe the fatigue factor is missing, as the number of kilometers increases or the difference in height takes over the fatigue that makes slowing down, while the proposed formula is linear, the reality is a curve.
Obviously you have to compare similar data to get reliable results, you can not enter a time on 100 meters to look for time in the marathon.
However, it has a very good approximation to reality, thanks.
You can use the swiss formula and you will geht mor accurate values.
t_t0 = {L · [C0 + (C1 · S) + (C2 · S2) + (C3 · S3) + (C4 · S4) + (C5 · S5) + (C6 · S6) + (C7 · S7) + (C8 · S8) + (C9 · S9) + (C10 · S10) + (C11 · S11) + (C12 · S12) + (C13 · S13) + (C14 · S14) + (C15 · S15)]} / 1000
(L = Horizontaldistanz; S = Steigung; C = Konstante)
Source (https://www.bergwelten.com/a/berg-know-how-wie-lange-geht-s-noch)
And you can insert conditions of the pathes into the formula also / or use different values for running and trailrunning and alpin trail running...
End of OT.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 06, 2018, 19:19:40
I've read about the swiss formula; looks like we need a realistic example here. I've searched quite a lot and did not find what those magic constants are.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Condor on August 06, 2018, 19:30:03
3.32.1
What about this?
Next we will not get ....
(https://s22.postimg.cc/bih27mm4d/Screenshot_20180806-192520.png) (https://postimg.cc/image/bih27mm4d/)

Other...

Sign in via email? Wich one? What?
Any registration for Locus? Or google mail? Or?
Facebook I do not use.

After 9 hours of work to repair what Locus has corrupted. I do not have a mood for this fact.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 06, 2018, 21:04:18
Quote from: tapio on August 05, 2018, 08:33:52
I cannot save tracks from route planner any more. Buttons at the bottom are missing. In fullscreen mode, old story.
I need to bring the keyboard (SwiftKey) up, then the buttons appear.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 06, 2018, 21:27:45
Quote from: tapio on August 06, 2018, 19:19:40
I've read about the swiss formula; looks like we need a realistic example here. I've searched quite a lot and did not find what those magic constants are.
http://www.wandern.ch/download.php?id=265_984bc5d8 (http://www.wandern.ch/download.php?id=265_984bc5d8)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: TimoG on August 06, 2018, 22:40:49
Thanks for the new version.

BUG geocache waypoint:
New geocache waypoints can now be created and are immediately displayed.

But if I change for example the coordinates I first have to close the cache and call it again to see the changes....
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: locus.sv@heime.org on August 07, 2018, 08:01:10
Quote from: Condor on August 06, 2018, 15:37:41
Or it is time to think (Menion) or it could be possible to generate a functional "Lite" version of Locus.
Only maps, points, navigation, geocaching.

Without trainers, sensors, bicycles, Fitnes, LT, chat, health records, Boats, planes, heart transplants .... and I do not know what's all in Locus.



Hehe, I know several people who won't touch Locus Map because of its complexity. A geocaching Lite version could be a solution for them, but personally, I like a lot of functions. But they have to work. Not able to add waypoints last week was very frustrating.

I also want to see a rock solid and reliable Locus Map. I do all my logging with GSAK as I don't thrust anything else at the moment. My wife is doing all logging with Locus Map and she experience strange error messages popping up from Locus that an error happened and "something" is stored for offline logging. But when we afterwards search, we cannot find anything stored for offline logging and everything seems to be correctly sent to the online api at groundspeak. Or so it seems :-)
The first thing I wish is more meaningful error messages when something goes wrong. A small popup which last half a second before it goes away is not user friendly and it does not say anything abot what is wrong, only that "something" happened.


And I find betatesting Locus Map is extremely difficult. Personally, I am testing on my live geocaching data. I don't want anything to go wrong with that. I don't want to come home from a trip and "test" 20 or 30 geocache find logs and 100-150 TB logs and experience a lot of trouble. So I mostly use GSAK for this as I know it works.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 07, 2018, 10:53:39
Many feedbacks, thanks.

I'll definitely look at ETA times and do some login behind to improve computed values. I'm currently communicating with Arndt and it looks like BRouter will compute ETA time also. So both GraphHopper and BRouter should return computed ETA times and the app should only modify these values little bit based on previous user activities. This is doable I believe.

Swiss or German (DIN 33466) method may be then used for the manual draw or in cases of some manual edit.

@tapio
issue in fullscreen: as wrote = long story. Try 3.32.2 or don't use full-screen

@TimoG
ah, thanks, have to check it

@Condor
I've already wrote excuses in different topic. Till now, I was not able to simulate any issues you wrote, sorry.

Problem with login: http://help.locusmap.eu/topic/locus-store-not-working-with-google-account#comment-61298

The light version of an app? No chance, sorry.

Method for testing Geocaching API  - Locus Map BETA needed:
(Beta will be published today)
- enable experimental settings: long click on the main menu
- in experimental settings (settings screen at the bottom), enable
- since now, Locus will communicate with staging server: http://staging.geocaching.com/ (it is a copy of original server for testing purpose).
Feel free to play & test as you wish :)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: locus.sv@heime.org on August 07, 2018, 11:51:47
Quote from: menion on August 07, 2018, 10:53:39

- since now, Locus will communicate with staging server: http://staging.geocaching.com/ (it is a copy of original server for testing purpose).
Feel free to play & test as you wish :)


Can you explain what that means for me? Can I log found, dnf and whatever as much as I want on a cache without this affecting my profile on the "real" server and without cacheowner getting any emails and so on?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 07, 2018, 12:14:20
Exactly. This staging server is from time to time completely cleared and data from the original server are copied here.
Anyway, you may do whatever wants here.
Not sure if this is allowed to publish to users (access to this server), but because we need to solve some GC troubles, I consider this as best method how to allow you to play with GC API without worry.
Also in geocaching tools in app, at the top, you will see a note that "Staging server is active", just to be sure you enabled this correctly.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: locus.sv@heime.org on August 07, 2018, 12:46:10
Quote from: menion on August 07, 2018, 10:53:39
Method for testing Geocaching API  - Locus Map BETA needed:
(Beta will be published today)
- enable experimental settings: long click on the main menu



Is these experimental settings only available in the beta. I am not able to activate it in the non-beta version and I am not sure I long press the correct menu item.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 07, 2018, 12:59:46
Quote from: menion on August 07, 2018, 10:53:39So both GraphHopper and BRouter should return computed ETA times and the app should only modify these values little bit based on previous user activities.
I'm not sure about "the app should only modify these values little bit".  There is no absolute truth in calculated ETAs, looking at the users tracks will not help, our actions may be too versatile. You add unnecessary complexity.

Quote from: menion on August 07, 2018, 10:53:39The light version of an app? No chance, sorry.
Here I fully agree. It would be something else. People can already have something else. Locus is complex, has to be learnt no matter what. But we want it. We want the features it has.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 07, 2018, 15:24:35
Quote from: tapio on August 07, 2018, 12:59:46
Quote from: menion on August 07, 2018, 10:53:39So both GraphHopper and BRouter should return computed ETA times and the app should only modify these values little bit based on previous user activities.
I'm not sure about "the app should only modify these values little bit".  There is no absolute truth in calculated ETAs, looking at the users tracks will not help, our actions may be too versatile. You add unnecessary complexity.
+1
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 07, 2018, 20:06:04
One click on plus sign in LT frozen

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on August 08, 2018, 05:42:27
I noticed this below yesterday on long bike ride - I must admit the phone is quite sick & being replaced; however the "last GPS fix" kept ticking over each second suggesting the phone was hearing something, however the rest of the screen suggests the other half of the phone brain had gone to sleep
(https://s22.postimg.cc/e7r2i5z0d/Window_20180808-133859.jpg) (https://postimg.cc/image/e7r2i5z0d/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: dribagnac on August 09, 2018, 15:15:13
Thanks a lot for this new update.
Just a comment about the new calculated time displayed on the lower bar of the Route Planner : it is rather wrong (too small). Same comment for the time computed on Travel Time (Route Menu) which is rather too high.

For example time compute with this GPX (with BRouter) : 02:29:26
Travel Time : 4:16 of movement + 1:30 of rest

GPX to download : https://www.visugpx.com/download.php?id=qi8JmTQxH4
With this GPX loaded on Swisstopo :
03:36

Load the GPX (drag and drop) on http://map.geo.admin.ch
Click on the track and "Display profile"

With my own experience (I am a mountain leader), Swisstopo is the most accurate time calculation.

Yours,

Daniel Ribagnac


(https://s15.postimg.cc/lb3nxvc6v/screenshot-map.geo.admin.ch-2018-08-09-15-13-26.png) (https://postimg.cc/image/lb3nxvc6v/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Mek on August 12, 2018, 17:54:26
Hello,
since this version I noticed that my recorded tracks exported in format "KML/KMZ" are always exported as KMZ. They were exported as KML before. I cannot find out how to get Locus to export to KML, no matter what I do. I have other software that expects format to be KML, not KMZ. Now, I know that KMZ is just a zipped KML, but how many users don't?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 13, 2018, 10:11:02
Crash since a few versions ago.

- Display like 20+ tracks
- Enter whatever track details screen
- Crash

Anyone else? Maybe because I have older hardware, a Sony Z1?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: c.s.g. on August 13, 2018, 15:42:06
Hi tapio,

just tested it on my Samsung Galaxy Note 4, Android Stock ROM 6.0.1 and Locus Pro 3.32.2:

I have a folder containing 28 tracks. Maximum 50 Km length.
All shown on map (LoMaps and OpenAndroMaps).
No problem selecting the detail screen via map or track menu.

Mayby my 28 tracks are to short to make Locus Pro crash.

Repeated the test with all stored tracks (96) in different folders on my phone.
Maximum 50 Km length.
All shown on map (LoMaps and OpenAndroMaps).
No problem selecting the detail screen of one track via map or track menu too.

c.s.g.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 13, 2018, 19:25:16
Thanks! I've found out: Locus does not like my Vista hcx tracks any more, crashes on any of them. Anyone having old, imported Garmin tracks in Locus? Will try to find out more...
I'm under the impression it happens on imported gpx files. My workflow is to import and correct elevation data on import.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: milan.cejnar on August 14, 2018, 11:45:55
Hello guys,
has anyone tried out the new Live tracking configuration/profile setup wizard that is started when you click on plus icon on the main live tracking screen? The setup wizard is currently only available in beta but I would like to know if you have any comments or feedback about this new LT profile setup style. Is it an improvement or an even bigger mess than before? :)

@lor74cas
Are you using beta? Which Android version do you use? Is Locus Map like completely frozen? Any chance of getting a bug report when this happens? :) Thanks
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 14, 2018, 12:28:08
Quote from: milan.cejnar on August 14, 2018, 11:45:55
Hello guys,
has anyone tried out the new Live tracking configuration/profile setup wizard that is started when you click on plus icon on the main live tracking screen? The setup wizard is currently only available in beta but I would like to know if you have any comments or feedback about this new LT profile setup style. Is it an improvement or an even bigger mess than before? :)

@lor74cas
Are you using beta? Which Android version do you use? Is Locus Map like completely frozen? Any chance of getting a bug report when this happens? :) Thanks

I can create the debug report with developer option tell me where I have to send it
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: milan.cejnar on August 14, 2018, 15:51:24
@lor74cas
Hello, I've sent you my email via PM. Alternatively you could submit a new ticket at our Locus help desk and attach the file there. Thank you.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 14, 2018, 17:02:55
Hi guys,

@tapio
what about saving the track from route planner in fullscreen mode in the latest version? Better?

Crash with some tracks? If reproducible, send me GPX track to test please, thanks.

@Andrew Heard
interesting screen with "no satellites". Were coordinates changing? Does this happen to you more often?

@Mek
if you have packed KML exports, you have to uncheck "Export attachments" checkbox. It will be renamed in next version to "Incl. description &amp; attachments" with small hint under "question" icon with text: "Add icons, generated descriptions and attachments and...\n - KML - pack into a KMZ\n - GPX - export to a subfolder". Hope this helps.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 14, 2018, 19:34:50
Quote from: menion on August 14, 2018, 17:02:55
@tapio
what about saving the track from route planner in fullscreen mode in the latest version? Better?
Yes, buttons are there, looks like solved.

Will send gpx if definitely reproducible.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 14, 2018, 19:45:15
Quote from: menion on August 14, 2018, 17:02:55
Hi guys,

@tapio Crash with some tracks? If reproducible, send me GPX track to test please, thanks.
My Garmin imports now crash reliably. But when I export and re-import, they work. Will need to look for the source gpx files.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: LocusUser#1 on August 14, 2018, 19:47:46
Quote from: lor74cas on August 07, 2018, 20:06:04
One click on plus sign in LT frozen

+1
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on August 14, 2018, 20:11:34
It's something completely different. Locus crashes depending on the group and folder name.

Group: 3. Test Test
Folder in that group: Unsorted

Tap any track, crash.

Rename group to "3TestTest": no crash.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 15, 2018, 19:01:24
@tapio
trying to rename group/folder based on your infromation, but no success. Crash log or share of your track database is needed here, thanks.

@Condor , @locus.sv@heime.org
you are for now only two who reported to me any troubles with current geocaching system. Unfortunately, without some exact reproducible steps or logs with error, that will lead to the problem, I have nothing to fix (all works for me as I tried). Why there are now such problems? Do not know. UI has changed, but functions that communicate with Groundspeak server are still same. A lot of major changes are happening on Groundspeak server now, but I cannot blame them without a proof.
So give me one major problem we may start with, together with some steps to simulate. Thanks.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 17, 2018, 16:41:03
Aaaand new Beta version 3.32.2.2 before weekend.
Except bunch of fixes, I spend most of time on tunning of computed calories. Those of you who use and check these values, please check also some older tracks you rode and let me know how does it match to your expectations, other web services etc. Feedback is more then welcome (and if you attach your track as well, it will be ideal).
And wish you a nice weekend!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on August 18, 2018, 02:06:07
@menion 3.32.2.2 beta: minor suggestion & not directly related to beta, but when I go to LoStore & tap Download (icon) for an existing map then tap DOWNLOAD button there is no feedback the download has commenced (or not) until I return to the main screen & see the notifications. On 1st attempt I thought maybe I didn't tap the button, so tapped the DOWNLOAD button a 2nd time, and hence two notifications of download.

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 18, 2018, 07:58:14
Quote from: milan.cejnar on August 14, 2018, 15:51:24
@lor74cas
Hello, I've sent you my email via PM. Alternatively you could submit a new ticket at our Locus help desk and attach the file there. Thank you.
In today last beta now works

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Christian on August 18, 2018, 13:47:31
Is the 'confirmation on exit' back in the Beta?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 18, 2018, 22:44:18
Quote from: menion on August 17, 2018, 16:41:03
Aaaand new Beta version 3.32.2.2 before weekend.
Except bunch of fixes, I spend most of time on tunning of computed calories. Those of you who use and check these values, please check also some older tracks you rode and let me know how does it match to your expectations, other web services etc. Feedback is more then welcome (and if you attach your track as well, it will be ideal).
And wish you a nice weekend!
Locus last beta vs Garmin forerunner 235 with HR monitor and Garmin Connect

2 activities: a walk and a run
Screenshot attached
Seems locus doesn't want that I eat ice creams this evening it's always lower in energy consumption than Garmin 🤤(https://uploads.tapatalk-cdn.com/20180818/a989171758bd83133e5fc3917e4803b5.jpg)(https://uploads.tapatalk-cdn.com/20180818/fd38d3b466c8ff7e0b0fe5e4a0d666b7.jpg)(https://uploads.tapatalk-cdn.com/20180818/dbc304588199d91127914c2da4eaeba6.jpg)(https://uploads.tapatalk-cdn.com/20180818/dd02e7fa38b23ab374cda4a0f390e08f.jpg)

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 22, 2018, 17:11:44
In red too close the numbers of altitude
In yellow too thin the grid lines to be useful(https://uploads.tapatalk-cdn.com/20180822/28999546d2943c22771fe3f91ca9c785.jpg)

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on August 22, 2018, 17:14:28
Today while recording with beta I searched for some caches locus did it but switched to pro version recording the track with both versions. Two is better than nothing

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Mek on August 29, 2018, 14:10:02
Quote from: menion on August 14, 2018, 17:02:55
@Mek
if you have packed KML exports, you have to uncheck "Export attachments" checkbox. It will be renamed in next version to "Incl. description &amp; attachments" with small hint under "question" icon with text: "Add icons, generated descriptions and attachments and...\n - KML - pack into a KMZ\n - GPX - export to a subfolder". Hope this helps.
Thanks, yes, it helps. Now the track is exported in KML unless I check the "Include icons and attachments" checkbox. But I was surprised that this track does not include the generated description either, why not? Previously it was there. Only if I export it as KMZ and unpack it in my computer, the doc.kmz file inside contains generated description. Is it possible to export as KMZ only if there really are any icons and attachments (and so multiple files, which must be packed)?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on August 30, 2018, 07:19:38
Please verify. When I create a new profile profile in the PRO version and assign a pre-created folder to save, the selected folder is not saved. See Scr.
In the BETA version, the save works.

CZ: Prosím o prověření. Když ve verzi PRO vytvořím nový profil záznamu a přiřadím mu předem vytvořenou složku k ukládání, neuloží se vybraná složka. Viz scr.
Ve verzi BETA uložení funguje.


(https://s15.postimg.cc/9untyjign/Screenshot_20180830-071017_Locus_Map.jpg) (https://postimg.cc/image/9untyjign/)

(https://s15.postimg.cc/w6lmrxpaf/Screenshot_20180830-071050_Locus_Map.jpg) (https://postimg.cc/image/w6lmrxpaf/)

(https://s15.postimg.cc/5yai2kcwn/Screenshot_20180830-071101_Locus_Map.jpg) (https://postimg.cc/image/5yai2kcwn/)

(https://s15.postimg.cc/gl4b7yq6v/Screenshot_20180830-071132_Locus_Map.jpg) (https://postimg.cc/image/gl4b7yq6v/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 30, 2018, 09:50:54
@Mek
I believe there are needs to export content without any extra information (like for OSM editor for example). The generated description is mainly used for Google Earth or similar apps, where you expect just to show track without any post-modifications.

Anyway, what you wrote is correct. Only if you check "Incl. description & attachments", Locus creates "big" export with all possible data at once. In the case of KML, it also packs into KMZ. Why is this problem for you? Most of apps should be able to handle KMZ correctly.

Why I did this? Previously there were two settings: "pack to KMZ" and "export generated description" and maybe also "export attachments"? (not sure now). Anyway, maybe the reason of "generated desc." caused confusion and repeated questions on the help desk. So this is simplification which places all into single settings.

@Žajdlík Josef
as you noticed, the issue is already fixed in Beta. Thanks for confirmation
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: john_percy on August 30, 2018, 14:15:07
"Personal details" setting asks for my height in yards. I don't know of any country that measures personal height in yards. For both Imperial (UK) and US (Queen Anne) measures, feet and inches would be best.

Sent from my XT1039 using Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on August 31, 2018, 10:44:20
in Beta and PRO
funktion twice different icon?

(https://s8.postimg.cc/nz27uzc9d/doppelt.jpg) (https://postimg.cc/image/nz27uzc9d/)

missing icon


(https://s8.postimg.cc/v2a3an7f5/fehlt.jpg) (https://postimg.cc/image/v2a3an7f5/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on August 31, 2018, 11:02:18
@john_percy
ah good point, thanks. Locus now set up this field based on "distance" unit. I'll change it to "altitude" unit.

@balloni55
seems you forget on the reason of this ;)
Points > open "points" tab of the data manager
Tracks > open "tracks" tab of the data manager
Data > open the latest tab of the data manager

Reason? Not everyone needs points or tracks directly, so "data" button is most useful for top/right function panel. On the second case, "Data" is a complicated word for new users so "points" and "tracks" directly in the main menu are a lot better!

And missing button ... well, 7 functions available in your case. Or you miss any specific button there?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on August 31, 2018, 12:51:18
QuoteReason? Not everyone needs points or tracks directly,
Thanks, understand ;)
QuoteOr you miss any specific button there?
sorry my fault :'(
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on August 31, 2018, 19:43:25
BETA 3.22.2.4 new export. When automated export to Cater, Locus reports an error. The export went well, see. SCR. So far only once, it can be a coincidence. I will continue to test.

CZ: BETA 3.22.2.4 nový export. Při automatrickém exportu do Stravy hlásí Locus chybu. Přitom export proběhl v pořádku, viz. SCR. Zatím vyzkoušeno jen jednou, může to být náhoda. Budu testovat i nadále.

(https://s15.postimg.cc/4oo63sak7/Screenshot_20180831-190145_Locus_Map.jpg) (https://postimg.cc/image/4oo63sak7/)

(https://s15.postimg.cc/3z5drfhqf/Screenshot_20180831-190223_Strava.jpg) (https://postimg.cc/image/3z5drfhqf/)

EDIT 2.9.2018
The route was again legally exported today with a green window of successful export. Yet, again, the manager reported a failed export report.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 02, 2018, 22:45:10
Thanks Josef, I see same problem now on own device. Will fix it.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 07, 2018, 21:08:26
*** Beta version 3.32.2.5 ***
- news after start, but main work was done on improving Route planner if few ways (more in news). Let me know (best in mentioned topic in news). Thanks and have a nice weekend!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: erfi on September 07, 2018, 22:35:51
Beta version 3.32.2.5:
Tested with SGS8 (Android 8.0.0) and HTC One S (Android 4.1.1)
It's great! Is it possible to change the name into the selfmaked profilname?

(https://s22.postimg.cc/qsf03xdzx/Route_Planner.jpg) (https://postimg.cc/image/qsf03xdzx/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 07, 2018, 22:41:45
Conversion of the route works well. But I use modified profiles with my own names. However, these names will not appear in the recalculation, instead of the original name. It's just a little thing.
(https://s15.postimg.cc/wx5q0vlg7/IMG_20180907_223409.jpg) (https://postimg.cc/image/wx5q0vlg7/)

(https://s15.postimg.cc/i176ta2br/IMG_20180907_223500.jpg) (https://postimg.cc/image/i176ta2br/)

(https://s15.postimg.cc/q6p8renzr/IMG_20180907_223532.jpg) (https://postimg.cc/image/q6p8renzr/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 08, 2018, 12:29:55
Hmm profile with car and label "chůze mokro" (wet walk in English). Because of this, app may report incorrect times because consider your navigation style as "car" and not as "walk". I know ... custom BRouter profiles. Maybe it also time to do something with it ...

Anyway issue You and @erfi reported: thanks, it will be possible, I'll look at it.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 08, 2018, 14:27:32
In the new Beta version of the route export, it works well. I just think it's a double report. The green window first flashes: The process is successful. Then there is a report about successful export in the manager, which I also have to manually remove. It is not useless?

I apologize for the non-standard profile assignment. As you write, it's a habit. Unforgettable times do not mind me, I do not see any, just a dash. This will definitely be the result of my own older Brouter profiles, which, however, are tuned exactly to my needs. I can estimate the time on my way alone.

CZ: V nové verzi Beta zobrazení exportu trasy funguje dobře. Jen mi přijde, že je to zdvojené hlášení. Napřed blikne zelené okýnko: Proces úspěšný. Pak ještě hlášení o úspěšném exportu v manažeru, které navíc musím ručně odstranit. Není to zbytečné?

Za nestandardní přiřazení profilů se omlouvám. Jak píšeš, jde o zvyk. Nespávné časy mi nijak nevadí, nezobrazují se mi totiž žádné, jen pomlčka. To bude určitě důsledek vlastních starších Brouter profilů, které mám ovšem odladěny přesně dle svých potřeb. Čas na cestě si dokážu odhadnout sám.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on September 12, 2018, 21:12:34
V 3.32.2.7
bigger GPS circles??
(https://s8.postimg.cc/gu6rfef7l/GPS.jpg) (https://postimg.cc/image/gu6rfef7l/)

in Beta and Pro:
challenging time forecast ;) uphill and downhill identically forecast
(https://s8.postimg.cc/3rb4w5za9/time.jpg) (https://postimg.cc/image/3rb4w5za9/)
profil icon perfect !!! :D
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 13, 2018, 01:04:17
Ah circles ... an unwanted side effect of larger circles with profiles in route planner. Thanks, will fix it.

And times, well ... :). Hopefully, there is always space for improvements!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 13, 2018, 09:18:00
3.32.2.7 Route Planner - a joy to use - well done @Menion. New track point icon - nice.

Bug (maybe) - when a Navigation (small blue) point is selected then deleted by tap of Bin icon the small blue icon on the map remains and needs repainting without any point? If I tap this small blue point it is described as a track point?

Suggestion - when a track point is selected display the GPS location in same way (bottom line) as a Via point, and thus allow this point to be moved by tapping the Circle/ Dot icon. This avoids having to drag the track point icon which only works over the visible screen distance, and I have sometimes found quite error prone - tap then immediate drag.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 13, 2018, 16:58:39
"Nice", glad to hear it :). I also think that now is work with planner again a little easier.

Bug: will check it, consider as fixed.

Suggestion: coordinates are now visible for shaping points (green triangle) and via points (blue square) that define the shape of the route. For other points, it does not make sense, because moving of navigation point or a single trackpoint just break computed route. Or did I understand incorrectly?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 14, 2018, 08:04:40
Quote from: menion on September 13, 2018, 16:58:39
For other points, it does not make sense, because moving of navigation point or a single trackpoint just break computed route. Or did I understand incorrectly?
At present I can tap/drag the trackpoint to a new location to force a route recalculation. That is as long as the new location is on the visible map otherwise I have to zoom out/ in. I can be tedious. So my suggestion is that when you tap the trackpoint and the new bottom dialog is displayed, why not allow the position to be changed as well. This would simply be a superset of existing tap/drag functionality but with ability to move the point with all the standard means - exact lat/lon, existing point, select on map etc. For me it makes total sense & seems like the one last remaining part of route planning to improve.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: freischneider on September 14, 2018, 09:19:37
For others, I can simply pull the track or route (google Maps on PC). I click the route anywhere. Then I draw the line where I want. And already a new route is calculated. You could then create a shaping point on the spot. Can you do something like that?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 14, 2018, 10:14:24
Notes to Event Manager. I apologize, I will continue to write Czech, my English is no longer enough.

Měl bych dva podněty k Manažeru událostí.
1) Navrhuji přesunout do něj i hlášení při automatickém uložení trasy. Je to takové nesourodé, když hlášení o uložení je v notifikacích a hlášení o exportu v Manažeru.
2) Pokud se využívá Locus k záznamu několikrát za den, hlášení o exportu docela zahlcují Manažer. Jedna možnost by byla položky seskupovat, viz scr1. Navrhuji ale spíš doplnit Manažer o hamburger menu s položkou Nastavení. V ní by pak byla možnost zatrhnout zobrazování jednotlivých položek. Viz SRC2. Třeba oznámení o úspěšném exportu do Stravy je zbytečné pokud ji máte nainstalovanou, stejně z ní hned přijde notifikace o nové trase.

(https://s15.postimg.cc/o8ph2fzh3/scr1.jpg) (https://postimg.cc/image/o8ph2fzh3/)

(https://s15.postimg.cc/8agrcaxjb/scr2.jpg) (https://postimg.cc/image/8agrcaxjb/)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 14, 2018, 15:14:10
@Andrew Heard
but as I wrote: you cannot move with a single trackpoint! You can move only with three type of points:
- red circle: middle point in the segment used for quick and easy creating of another shaping points
- green triangle: shaping point
- blue square: via point
So about which point we talk here? Moving directly with trackpoints is not acceptable: you never may be sure, which point you are moving with and also there are other options how to add a point in the middle of the track on exact place.

@freischneider
I just tried google maps on PC and to be true, I do not know about which feature you talk, because to me it looks like there is nothing special compare to what Locus Map do in Route planner.

@Žajdlík Josef
thanks for idea. Agree it may grow ... I have one more idea in the head. Agree it needs some improvement. I'll look at it ...
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: freischneider on September 14, 2018, 17:31:10
I have taken it with the phone times.
1. Set start and destination
2. Calculate route
3. Route (blue line) change the course (see video)[/b
click blue line
put her in a new position
google recalculates the route

Video: https://www.dropbox.com/s/3mzgwme0mpi2cjz/2018-09-14%2015.58.43.mp4?dl=0
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: freischneider on September 14, 2018, 17:38:22
It could look like this in locus.
click route long
Route can be moved to another street.
Calculation with a new course
or
click route long
a shaping point will be created at this point
and this can be moved to a new street
Calculation with a new course

So I can calculate a route quickly. Enter start and finish, calculate, make small changes. For example, I would like to take the path at the edge of the forest and not over the field.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on September 14, 2018, 21:23:52
Hello menion
Beta:
FC while click on label to open GC-listing, but only on some caches ?!
e.g.
https://coord.info/GC7XD59
https://coord.info/GC1M66M
https://coord.info/GC67CFN

bug report send per mail
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 14, 2018, 21:52:53
@freischneider
understand, thanks for an explanation. What you want is already possible with middle "red circle" point in every segment. So just drag and drop it to the new location. Or you may alternatively add point (detour) by long click on the place which you want to pass.

@balloni55
thanks. Log received, issue found!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 15, 2018, 03:32:43
Quote from: freischneider on September 14, 2018, 09:19:37
For others, I can simply pull the track or route (google Maps on PC). I click the route anywhere. Then I draw the line where I want. And already a new route is calculated. You could then create a shaping point on the spot. Can you do something like that?
@freischneider - is that a suggestion for me? The Route Planner already allows a tap/drag (or swipe) of a Track/ Shaping/ Via point to force the route through a new point. If you are zoomed out the new point may be quite inaccurate as it doesn't snap to nearby road; or desired road may not even be visible at current zoom level.

I'm just suggesting an alternative which seems entirely consistent with point selection in other parts of Locus. Tap on track point - the bottom dialog is displayed similar to Shaping or Via point:
(https://s33.postimg.cc/lwcn5l3nv/map.jpg) (https://postimg.cc/image/lwcn5l3nv/)

then tap on Circle icon to access other point selection methods:
(https://s33.postimg.cc/zd9loh14r/select.jpg) (https://postimg.cc/image/zd9loh14r/)

For short distance a swipe of the point to a nearby position may be OK but sometimes one of these other existing methods (My Points/ Coordinate/ Search) may be more convenient.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 15, 2018, 03:39:24
Quote from: Žajdlík Josef on September 14, 2018, 10:14:24
Notes to Event Manager. I apologize, I will continue to write Czech, my English is no longer enough.
@Žajdlík Josef - I think your English is very impressive. In any language specific thread (not a mixture of languages) it is nice not to have to translate from one language to another if possible so please persist if can please.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 15, 2018, 03:51:40
Quote from: menion on September 14, 2018, 15:14:10
@Andrew Heard
but as I wrote: you cannot move with a single trackpoint! You can move only with three type of points:
- red circle: middle point in the segment used for quick and easy creating of another shaping points
- green triangle: shaping point
- blue square: via point
So about which point we talk here? Moving directly with trackpoints is not acceptable: you never may be sure, which point you are moving with and also there are other options how to add a point in the middle of the track on exact place.
@menion - sorry for this ongoing confusion - a picture is sometimes worth a thousand words so below is simple route with start/ finish Shaping point, and Track point:
(https://s33.postimg.cc/k5tm3utrv/Window_20180915-114328.jpg) (https://postimg.cc/image/k5tm3utrv/)

If I tap the cyclist icon the bottom dialog shows this point is a Track point and can be converted to a Shaping, Via, or Navigation point. No problems. I am also able to swipe (tap/ drag) this Track point to any new location on the visible map (with magnifying glass) although as I explained in the post to @freischneider this can be problematic if the zoom is low or the map distance is large. So I can't see why it is not consistent to allow this Track point to be moved to any new location using the other selection methods.

I agree a new point can be added via the menu; and this will have the desired outcome too. But I explain this UX to another user thus: tap on red, green or blue icon then choose new location, but don't tap on the cyclist icon, you can only choose a new location for this point from the menu sorry.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 15, 2018, 07:47:31
I have just installed Locus Pro 3.32.2 & beta 3.32.2.7 onto a new 7.1 tablet. I did a backup from phone to ZIP file which was copied across & then restored. For some reason it took many many restarts before correct Presets were displayed, and config.cfg setting dev_gui_main_rescale_value was used. Changing the Backup folder from default /Locus/Backups to /Downloads/Locus would each time cause a crash.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: freischneider on September 16, 2018, 11:11:28
@menion, Andrew Heard
I know that with the red dot.
But at a long distance 40 km. Only 2 points (start, finish) If there is 1 red point.
If I zoom in to change details on the track, I may not even see it.
So I have to zoom out to see him. But then I do not see details anymore
So it would be more comfortable if I could just pull the route.lang drücken auf Route.
long press on route.
Pull to new place
Let go and then there is a shaping point
This can then possibly change to a via point.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Tapio on September 16, 2018, 12:08:40
In all my latest recorded tracks, I have extreme ascend/descend values, >400% at times. Elevation values are by srtm here, they replace gps values. I did not change it. This makes the graph unusable. Anyone else?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 17, 2018, 02:13:23
Quote from: freischneider on September 16, 2018, 11:11:28
@menion, Andrew Heard
I know that with the red dot.
But at a long distance 40 km. Only 2 points (start, finish) If there is 1 red point.
If I zoom in to change details on the track, I may not even see it.
So I have to zoom out to see him. But then I do not see details anymore
So it would be more comfortable if I could just pull the route.lang drücken auf Route.
long press on route.
Pull to new place
Let go and then there is a shaping point
This can then possibly change to a via point.
@freischneider - I think you are suggesting allow swipe of route, not just at the mid-point icon but anywhere along the route - nice idea, I agree
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 17, 2018, 02:15:32
Quote from: tapio on September 16, 2018, 12:08:40
In all my latest recorded tracks, I have extreme ascend/descend values, >400% at times. Elevation values are by srtm here, they replace gps values. I did not change it. This makes the graph unusable. Anyone else?
@tapio - yes I had same experience one month ago - see ongoing discussion here (http://help.locusmap.eu/topic/limit-gradient-scale-in-chart-to-something-reasonable-instead-of-autoscaling-to-silly-values#comment-22072).
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: alezy on September 17, 2018, 11:27:19
@menion, in last beta I've got FC when tapping on "Map Items" button
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 18, 2018, 09:05:55
@Andrew Heard
ah, here comes confusion. The red circle isn't clickable! It allows to drag & drop to create a new shaping point, but click do nothing! What happens to you is that click on this point, selected nearest trackpoint on track, so you had feel like you click on track.
I've anyway improved this now, and this red circle now offer information about this track segment with an option to recalculate it.

Problem with backup: hmm crash needs logs. Anyway problem with restoring, hard to say. App should check if config.cfg was changed and use it or overwrite based on this.

@freischneider
understand your point with dragging of trackpoints, but I still do nothe t like it. On smaller screen, you often drag map with fingers and with this feature, you will have to worry even more to not to drag part of existing route. Use long click > it's even faster (mainly with new Beta version).

@tapio
export me please your track to GPX, I'll check why this happen, thanks.

@alezy
thanks, should be fixed now. New Beta? Most probably today.

EDIT: Beta version is out!
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: balloni55 on September 18, 2018, 20:50:51
V 3.32.2.8
routeplanner:
- click on "shaping triangle" or "via square" or "segment circle" of planned route
- next click top left in "bottom window" triangle, square or circle > point detail window opens, why?
- it seams that this point is stored inside point folder, but if i click on horizontal arrow i didn´t find this point there
- if you click on bottom left button "show on map" or click the "mini map" my planned route is gone and only this temporary point is visible

Experimental:
i can´t switch off "Allow login over Play Service"
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 19, 2018, 01:58:23
V 3.32.2.8: @menion - the Route Planner just gets better & better. The latest changes are very impressive.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 19, 2018, 07:24:36
In 3.32.2.8: as Andrew writes, the new planner is very good. I just have one comment. When I change the shaping point to a transit, I have no option to confirm the name. With the back button, changes are canceled, so the only confirmation option is a click on the map screen. I do not think this is a procedure that would follow other Locus control.

CZ: V 3.32.2.8: jak píše Andrew, nový plánovač je moc dobrý. Měl bych jen jednu připomínku. Když změním tvarovací bod na průjezdní, nemám žádnou možnost potvrdit název. Tlačítkem zpět se změny zruší, takže jediná možnost potvrzení je klik do obrazovky s mapou. Myslím, že to není postup, který by navazoval na jiné ovládání Locusu.
(https://i.postimg.cc/JymXgkVd/Screenshot_20180919-071732_Locus_Map.jpg) (https://postimg.cc/JymXgkVd)
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 19, 2018, 16:01:19
@balloni55
Hmm, you are right. Reason for this was mainly "street view". I wanted to offer point screen with its bottom panel to give access to extra functions available there, mainly to Street view. But it should be a lot better, to put this function directly into "three dots" bottom menu of clicked shaping/via/etc point. This will solve also issue with the click on the map in the point detail etc. Thanks.

"Allow login over Play Service" switch? Why can't? This option is not visible? Btw. if this setting is disabled, most probably on your device isn't Google Play services installed at all, is it possible? You may check it by the number of options in "login" to Store. In case of "Google/Facebook/Email" => Google Play services are installed. If only "Email" is available, they aren't installed.

@Andrew Heard
thanks :)

@Žajdlík Josef
changes should not be lost after you press the back button. Anyway, any better solution? I want to get rid of confirmation buttons as much as possible.

@0709
thanks, I'll try it.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 19, 2018, 18:40:17
Quote from: menion on September 19, 2018, 16:01:19
@Žajdlík Josef
changes should not be lost after you press the back button. Anyway, any better solution? I want to get rid of confirmation buttons as much as possible.

I guess yes, in the case of a mistake, the point can be easily changed to shape. Or use the Enter key. The first click moves the cursor into the "description" field. The second click will confirm and exit the dialog. Now the second click moves the cursor to the next line in the "description" field. At the same time, I would still have the option of ending by clicking on the map.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on September 19, 2018, 18:44:14
Quote from: Žajdlík Josef on September 19, 2018, 18:40:17
Quote from: menion on September 19, 2018, 16:01:19
@Žajdlík Josef
changes should not be lost after you press the back button. Anyway, any better solution? I want to get rid of confirmation buttons as much as possible.

I guess yes, in the case of a mistake, the point can be easily changed to shape. Or use the Enter key. The first click moves the cursor into the "description" field. The second click will confirm and exit the dialog. Now the second click moves the cursor to the next line in the "description" field. At the same time, I would still have the option of ending by clicking on the map.
+1

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 20, 2018, 08:52:20
First observed in 3.22.2.7 or 3.22.2.8: track > INFORMATION tab displayed > tap Export > export dialog is displayed > tap EXPORT > tap CLOSE > same export dialog is again displayed - why? Previously after an export the track INFORMATION tab was again displayed, and would seem a more useful workflow. I don't think many users would want to export same track multiple times in a row. Can the previous behavior be restored?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 21, 2018, 13:54:27
@Žajdlík Josef, @lor74cas
understand, but to be true, I also do not like this option. Closing dialog by "enter" button on keyboard is also not obvious. Will have to wait on my "muse" with the useful idea :).

@Andrew Heard
ah thanks, side effect, fixed.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 22, 2018, 01:39:24
@menion new 3.33.0RC1 on Android 7.1.1 tablet. Android location disabled (in home). Always crashing. Eg menu > About > About > back > crash. Track list > back > crash. GPS > off > back > crash. But not menu > About > back. It seems always when Back button is tapped. If I just leave the app idle it does not crash. If I zoom/ pan map the app does not crash. I have never seen behavior like this before.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: T-mo on September 22, 2018, 12:04:36
menion, nice to see the last improvements

3.33.0RC1
route planner (example-scenario with at least 3 shaping points)

- click on any  'Shaping point':
    - labels next to 'change to' always have no.1..might be confusing
    - choosing blue icon to change to 'via point' > opens dialog 'Icon & name'..the already given blue std-icon is not given..I choose to press the return-key as I don't want to input anything or as I'm confused (maybe) > all is fine, back in the route-planner. Click on the same point which I changed to 'Via point': no text 'Via point' next the Point-Icon (Description)

- clicking Point 2 'Shaping Point'
> Selection-dialog: Part 1 of route, Part 2 of route, Shaping point, etc...
    - 'selection 'Part 1 of route' selects the last trackpoint, seems so
    - 'selection 'Part 2 of route' selects the next trackpoint, seems so
   ..in both cases the parts are completely selected and highlighted, but the pop-up is about the trackpoint

- clicking a Part of a route near the rose/pink Part/Segment-Profile-icon
  - counting of 'Route segments' starts with 0..intended?
  - I would mean 'Parts' and 'Segments' of a route to be the same thing, reg. word-description and by highlighting..but it is handled diffently. Maybe this is sort of artificial complexity and there should only be 1 thing for the same?

- by mistake I choosed the wrong routing-engine or maybe I want to switch to compare the results..recalculation tells me that this is only possible with the used engine (and profiles)..as the used profiles might be engine-special this makes sense. Any way to re-define/-choose profiles for each segments or reuse the whole point-list while planning?

questions:
- waypoints are direction-descriptions (and only this), trackpoints are only internal points ('Part of Route' gives me e.g. Trackpoint 52, and by selection on the part here and there I can try to hit Trackpoint 51..48..)
- I guess you reduced the trackpoint-pop-up in the routeplanner to reduce complexity, because at regular tracks I can jump to the next trackpoint or before AFAIR..

wishes:
- a list of all used Shaping/Via-points and the dot-menu for point-changing next to all of them, and the ability to add or remove points. Maybe placed between 'chart' and 'waypoints' @Route-Stats. This might be the ability to work on compact list-views instead of map only (visual-only).
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: LocusUser#1 on September 22, 2018, 13:34:46
Here are my findings in 3.33.0 RC1

1. When I load a track into the route planner, the icon in the red dot always shows a car, even if the track was previously created as hiking.
(https://i.postimg.cc/vxQr55RC/image.jpg) (https://postimg.cc/vxQr55RC)

2. The thumbnails in the track list are broken again.
(https://i.postimg.cc/jDQRFfBM/image.jpg) (https://postimg.cc/jDQRFfBM)

3. The start point icon is not always displayed correctly.
(https://i.postimg.cc/CBb7GFRn/image.jpg) (https://postimg.cc/CBb7GFRn)

4. The symbol of a waypoint is not displayed, instead only a blue dot is displayed.

5. FC when i make this: More functions > Share > Share screen > CANCEL
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on September 22, 2018, 17:36:39
3.33.0 RC1 Livetracking one touch to start to have a crash

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 23, 2018, 16:23:00
@Andrew Heard
thanks for the send log, it helped! (crashes should be solved)

@T-mo
very nice feedback, thank you!

- first three paragraph: improved/changed
- problem with selecting different router: may you write me step-by-step what you did? I'm unable to simulate any problem
- in Route planner was never possible to move between trackpoints. It was always possible only in "Track editor". Here it partially makes sense, but still not too much :).
- wish: an interesting idea. I have one idea (integration of something like "Navigate to" into Route planner"), so it will be close to what you want.

@LocusUser#1
1. ah issue, fixed thanks
2. nice, fixed
3. hmm start point without background? Any steps to reproduce?
4. again, any steps? For me, all via points created in Route planner are displayed correctly
5. thanks, fixed

@lor74cas
thanks, most probably connected to crashed of Andrew and LocusUser. Check please next version and if the issue will be still there, better step-by-step will be needed.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: erfi on September 23, 2018, 16:32:22
@menion:
Quote4. The symbol of a waypoint is not displayed, instead only a blue dot is displayed.
Look also at here: http://help.locusmap.eu/topic/waypoints-not-shown-consistently-in-rc1
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 24, 2018, 09:20:13
Quote from: menion on September 23, 2018, 16:23:00
@Andrew Heard
thanks for the send log, it helped! (crashes should be solved)
@menion - thanks - I just installed RC1 on Android 8 phone (previously v7 tablet), and it too crashes for same reasons. Strange that no one else has reported this problem - what is special about my tablet & phone?
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 24, 2018, 09:37:04
Thanks guys ... new BETA RC2, give it a try.

And Andrew ... special, maybe Dashboard, do not exactly know, but I believe it will work now :).
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Žajdlík Josef on September 24, 2018, 14:21:56
On android 8, I had the same problems with the crash of the app as Andrew. The new Beta RC2 has resolved these crashes.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: erfi on September 24, 2018, 19:54:45
Version 3.33.0 RC2: Problem with Track editor,
look also here: http://help.locusmap.eu/topic/insertedit-trackpoint-not-wot-working-in-track-editor
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Andrew Heard on September 25, 2018, 06:01:11
Version 3.33.0 RC2: working for me on Android 7.1 & 8. Thanks @menion. Yes, I had custom dashboard.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 25, 2018, 09:51:15
Perfect. Track editor fixed and seems there is no other serious problem. We will test it as much as possible during today in our team and most probably, tomorrow publish new final version.
Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: lor74cas on September 25, 2018, 19:57:49
Quote from: lor74cas on September 22, 2018, 17:36:39
3.33.0 RC1 Livetracking one touch to start to have a crash

Inviato dal mio SM-A520F utilizzando Tapatalk
Fixed

Inviato dal mio SM-A520F utilizzando Tapatalk

Title: Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
Post by: Menion on September 26, 2018, 21:52:59
Most probably the longest time between releases, somewhere around 7 weeks. Well, summer holidays have negative effect :). Anyway, hope that new version brings some useful news to you and thanks for help!