Messages

Thanks for a file, unfortunately I see no problem on own device. May you please send this crash report once more and into comment write your nickname so I'll be able to find it, thanks!

Crash report with log and lor74cas in text field sent

Inviato dal mio SM-G800F utilizzando Tapatalk

track from garmin forerunner, fit file converted in gpx with gpsbabel.
Other gpx file converted from fit to gpx with sporttracks same issue.
The import with previous version was ok, with the same files, some days ago I imported without problems.

Hello,
I cannot import in Locus gpx files created with 2 different software.
Never ending analysis ...

Then crash.
Crash reported with log

Inviato dal mio SM-G800F utilizzando Tapatalk

Thanks guys for a testing, really useful, thanks!!

So new version published as Beta version on Google Play right now. There are some minor improvements, nothing serious. I would like to publish this version at start of next week as final public version, so feel free to report anything you consider as bug ... + small Christmas gift to @balloni55 because I appreciate he care about my spend, not wasted, time .

Hello,
Crash detected switching from 2d to 3d skyplot on last beta.
Android 4.4.2
Restored 2d works fine.
Sorry I have no time for better testing

Inviato dal mio SM-G800F utilizzando Tapatalk

You can install a android emulator like bluestacks on your PC,  install locus, provide a mock location and done. Tested last week.

Inviato dal mio SM-G800F utilizzando Tapatalk

For global info: http://www.locusmap.eu/everything-you-always-wanted-to-know-about-elevation-in-locus-but-were-afraid-to-ask/

I do not have a pressure sensor so when I found that altitude data of the recorded track with just gps are crazy I tried to solve.

First you need a good accuracy of recorded track points:
settings -> track rec -> choose your profile settings --> requested accuracy set a strict value (for me 30mt)

Second you can have better SRTM values using HGT files with 1" arc insted of 3"
http://help.locusmap.eu/topic/hgt-elevation-data-display-if-both-1%E2%80%9D-and-3%E2%80%9D-resolution-hgt-files-are-present-in-the-srtm-directory
http://www.viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org1.htm
http://www.viewfinderpanoramas.org/dem3.html

and if you want a costant application of srtm data and bypass the "fill data.." after track recorded use this:
in settings -> gps and position -> altitude manager -> settings -> srtm data -> replace gps values

Does this stuff you are telling me apply to me since I have a baro sensor or just to someone who is using a device WITHOUT a baro sensor? I hate to just start changing values i do not understand if it is going to make it worse for my particular phone. With a baro sensor do I still want to bypass the fill data and replace gps track values or is this just what you did because of the device you were using with no baro sensor?

You started this topic with a question about elevation gain, not about pressure sensor settings, after some posts we now know that your device has the pressure sensor.
Before this we also talk about SRTM.
If someone else in future will read this topic will find something usefull about elevation gain becouse the post title is ELEVATION GAIN.

If you wonder if "this stuff" is about pressure sensor, read carefully what I wrote "I do not have a pressure sensor", nothing in my post is about pressure sensor.

And if you "hate to just start changing values i do not understand ..." you can start study how things work, you didn't know to use side panel, you didn't know that "Elevation gain = elevation (uphill)" now you know becouse someone used his time to answer you even if this things are explained in the documentation and in other posts.

Now I can answer your questions:
1) No
2) This is just what I do because my device has no pressure sensor.

P.S.
Strava does not have the truth, no software and no device has the truth.
Put the same track gpx file into 3 different account with different algorithms you'll obtain 3 different altitude gain.
I use Locus on two phones (no baro) and a garmin forerunner and you'll see that the 3 tracks have differences not only about the altitude gain.
I agree with michaelbechtold "Elevation collected from GPS in mobile devices is like rolling the dice around the true curve."
So you need to study wich way is better for you/your device/your habits/place of use.

Regards

For global info: http://www.locusmap.eu/everything-you-always-wanted-to-know-about-elevation-in-locus-but-were-afraid-to-ask/

I do not have a pressure sensor so when I found that altitude data of the recorded track with just gps are crazy I tried to solve.

First you need a good accuracy of recorded track points:
settings -> track rec -> choose your profile settings --> requested accuracy set a strict value (for me 30mt)

Second you can have better SRTM values using HGT files with 1" arc insted of 3"
http://help.locusmap.eu/topic/hgt-elevation-data-display-if-both-1%E2%80%9D-and-3%E2%80%9D-resolution-hgt-files-are-present-in-the-srtm-directory
http://www.viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org1.htm
http://www.viewfinderpanoramas.org/dem3.html

and if you want a costant application of srtm data and bypass the "fill data.." after track recorded use this:
in settings -> gps and position -> altitude manager -> settings -> srtm data -> replace gps values

@gynta and Kompass map (799 LoCoins)
- more info please
- screenshot
- the name of map
- why are not Kompass maps "detailed"? Some real experiences?
- the text "Detailed" is adopted form official Kompass product description

I used komass maps but I prefer Tabacco on paper are 1:25.000 no experience on digital version

Inviato dal mio SM-G800F utilizzando Tapatalk

As other wrote I like the actual Quick measurement, no timer just disappear with the next touch of the screen.

A little bug:
With calibrated image disabled if I search for some caches and in the pop up menu I select show them on map both caches and disabled image appear on the map.


Inviato dal mio SM-G800F utilizzando Tapatalk

Wanted to try the new "measurement with two fingers" but nothing happend. Whats wrong?

http://help.locusmap.eu/topic/measuring-distances-with-two-fingers-on-the-screen

Settings -> Maps -> Map Objects -> Quick Measurement. (Enable)
photo
0709
2 days ago

Inviato dal mio SM-G800F utilizzando Tapatalk

Hello
In map items I found a double voice in menu one in English and one in Italian.
The Italian one is enabled the English disabled but the line is visible on the map.


Inviato dal mio SM-G800F utilizzando Tapatalk

"Settings" button on track record widget changed to icon of current profile

if profile is changed via widget or direct in settings the widget icon isn´t refreched.
It´s refreched on next track record start

The same for me, the refresh of the icon needs a fresh start of locus (if already in memory the widget doesn't refresh) or track rec.

Inviato dal mio SM-G800F utilizzando Tapatalk

V 3.18.9.6
if i tap near the left side of the screen while 2 finger measure, measurement freeze. Reset can be done with a new two finger touch inside the screen
https://www.dropbox.com/s/z603p9tevsxkdl2/2finger.mp4?dl=0

Confirmed
I think that when you touch the left side of the screen the activation of side panel casue the issue.

Inviato dal mio SM-G800F utilizzando Tapatalk

settings/maps/maps objects/Quick measurement
and additional setting in config.cfg see code in #290

Thank you,
I have the altitude value back.
I don't know why the "line below info" is disabled in the last beta, and I do not understand why the two fingers measurement is disabled by default.
But the important is to have both back

Inviato dal mio SM-G800F utilizzando Tapatalk

Hello,
In New beta 3.18.9.5 the two fingers measurement doesn't show altitude value.

Inviato dal mio SM-G800F utilizzando Tapatalk