Messages

31

Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )

« on: October 01, 2018, 09:09:06 »

@lor74cas
hmm no back button? One of the most used buttons on Android?? How he control other apps, no problems??
I'm really not sure how useful such a button may be to others ... sounds to me as really useless :/. If he have enabled fullscreen mode (he probably has) then he may also swipe from left to open main menu. Then it's almost no extra work for this one-time task I think. Sorry, I've convinced myself, that such button really does not make sense .

Yes fullscreen mode covers the virtual back button, ok I'll tell him to use swipe method I hope he will be more confortable with it.

32

Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )

« on: September 29, 2018, 17:23:16 »

Is it possible to add the exit button as one of the selectable option for the panels?
A fried has a phone without back fisical button and to exit needs always to open the main menu.

Inviato dal mio SM-A520F utilizzando Tapatalk

33

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: September 25, 2018, 19:57:49 »

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

34

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« 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

35

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: September 19, 2018, 18:44:14 »

@Ž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

36

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« 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

37

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« 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

Inviato dal mio SM-A520F utilizzando Tapatalk

38

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 18, 2018, 22:44:18 »

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 🤤

Inviato dal mio SM-A520F utilizzando Tapatalk

39

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 18, 2018, 07:58:14 »

@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

40

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 14, 2018, 12:28:08 »

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

41

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 07, 2018, 20:06:04 »

One click on plus sign in LT frozen ️

Inviato dal mio SM-A520F utilizzando Tapatalk

42

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 06, 2018, 17:56:22 »

@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):

Code: [Select]

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.

43

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 06, 2018, 10:59:18 »

@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)

44

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« on: August 06, 2018, 07:30:32 »

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.

Inviato dal mio SM-A520F utilizzando Tapatalk

45

Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )

« 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