Show Posts

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


Messages - shushuk

Pages: [1] 2 3 4
1
Ich vermute, da reden wir aneinander vorbei bzw. versteht da einer etwas falsch.
Wenn Du das Smartphone in den Flugmodus setzt, ists vorbei mit Live Tracking.
Den Datenverbrauch minimierst du dann natürlich, ist klar  ;)


2
[DE] - deutschsprachiger Forumsbereich / Re: Buddy tracking
« on: April 05, 2017, 10:50:35 »
Ja, da schließe ich mich an. Ab dem Zeitpunkt des "Verfolgungsbeginns" wäre eine Verbindung der Übermittelten Punkte als Option super!!!

Ergänzung:
Vote here!!!
http://help.locusmap.eu/topic/snail-trail-for-live-tracking

4
Ohne dir jetzt eine konrete Antwort geben zu können (ich glaube aber, das wurde im Rahmen eines threads zum Thema live-tracking bereits mal behandelt und bewegt sich im sehr überschaubaren Bereich) gebe ich aber noch zu bedenken, dass Smartphones die unangenehme Eigenschaft haben, auch für andere Apps bei aktiver Datenübertragung Daten zu transferieren. Trotz Beendigung aller nichtbenötigten Apps, Mobiler Synch von Emails, etc. kommen so doch einige MB zusammen, die das live-tracking-Volumen bei meinen Tests deutlich überschritten haben. (Genaueres weiß ich nach Erhalt der nächsten Abrechnung... ;-) )
Nicht getestet habe ich dabei die Einschränkung der Hintergrunddaten, nämlich ob dies Auswirkungen auf die Nutzung von Locus hat.
Meine Tests haben bei aktiviertem internationalen Roaming im benachbarten Ausland stattgefunden. In diesem Zusammenhang habe ich übrigens doch Hoffnungen in die gelockerten Roaming-Regeln, die ab (Mitte?) Juni d.J. in Kraft teten sollen. Macht dann das Besorgen von prepaid data sims und das ständige Wechseln hoffentlich hinfällig...
Grüße
shushuk

5
Das Problem wurde mittlerweile gelöst, der Vollständigkeit halber hier der link zur locus-help Seite.

http://help.locusmap.eu/topic/live-tracking-entering-a-private-room-not-working

Danke, Menion!

6
Hallo,
Folgendes Problem:
Ich habe auf einem Handy Locus pro, für das Live Tracking eine Subscription, einen privaten Raum angelegt, den Key generiert. Weiters auf diesem Phone GPS und Tracking gestartet (beides grün)

Auf dem Handy meiner Frau ist Locus free installiert.
Für das private Buddy Tracking versuche ich nun dem generierten Raum beizutreten. Dazu gebe ich unter Räume-->Verwalten-->"+"-->"einen passwortgeschützten Raum hinzufügen" das PW ein und bestätige mit "Raum betreten". Es kommt die Meldung "Prozess erfolgreich". Allerdings ist in der Raumverwaltung weiterhin nur der "Public room" vorhanden.

Ist das ein Bug oder mach ich was falsch?
LG
shushuk

7
I also posted this topic as an idea at the Locus Help portal about a week ago. Here is the link:
http://help.locusmap.eu/topic/air-pressure-calibration

@Menion: Is this topic on your "radar"? Any comment on that would be appreciated....

Regards
shushuk

8
I also use brouter for MTB-Track planning. Although I don't need navigational instructions, I just follow tracks. That's fine for me.

shushuk

BTW: I also have the problem that (nearly) nobody is interested in, what I think, my suggestion for a better app-handling for MTB-users regarding air pressure sensor. So I'm also a bit frustrated at the moment.... :'(

9
But I personally prefer calibration according SRTM data because this is not too bad in most cases (I know there are examples with quite high difference compared to actual altitude) and works everywhere I start track recording.

So the "Automatic" Setting is perfect for you.
But it's not useful if you want to focus on air pressure sensor, as I do.

And for me this seems to work because I checked some tracks starting from my house and they all start with 473m which is the SRTM value Locus reports for this location. I have no calibration data entered myself.
I checked it again today, first value was 276m (instead of 450) today, rising as gps-signal got better. So nearly 200m uphill without moving... SRTM value also available for my Location.

Thinking about it I would even recommend not only to automatically calibrate the altitude at the beginning of a track-recording but even at activating of GPS, when AltitudeManager-->AirPressure-->Altitude[value] is set!
It's up to the user which settings and sensors to choose, but if you want to use the air-pressure-sensor and you want to calibrate altitude to a known value, it should be done by the app without additional clicks.


shushuk

10
I did a little test today. Setting as recommended:
Pressure-Sensor = on (of course)
Pressure = Automatic

SRTM data is stored on my device for this spesific area.

I started Locus and track recording (via widget). Altitude obviousely was driven from GPS-data (it was different from SRTM value which is shown in map-center...) and far too low. (~360m instead of 450)
Immediately, as GPS-Signal got better, altitude began to rise. After about 30seconds I had an (GPS-)altitude of ~400m.
Therefore I made about 40m uphill, which is Nonsens as I didn't move uphill.
I stopped the test, because this setting is not useful for me.

Then I manually calibrated the altitude to the desired 450m, started a track recording again and everything was perfect. Altitude changes were realistic, just as I expected them.

Only thing is that I would have to do this Manual calibration every time Prior to track recording!

An automatic calibration to the specified value would make an air-pressure-sensor much more usefull!
No GPS-data, no SRTM-data, just the most reliable air-pressure data at track recording...

shushuk

11
Altitude Manager --> Pressure --> Automatic uses GPS-Data to calibrate the altitude, which can be quite wrong as we know. It also does some recalibration every 2 hours.
No, I would like to use my known altitude when starting a track recording.

Current Situation:
Altitude Manager --> Settings --> Pressure Sensor = on
Altitude Manager --> Pressure --> Altitude = 452m (= my known altitude)

After confirmation of the settings the altitude is calibrated to 452m. OK
I start a track recording (in this case immediately after setting the value), the altitude starts at 452m. OK

When stopping the record there are two possibilities:
a. My training was a round trip and I finish at the starting point again, but altitude is not 452 any more but let's say 464m (due to pressure changes f.e.).
b. my training finishes at another point (let's say 680m), transportation back home by car or train

In both cases a track record the next day would start at a wrong value. I would have to start altitude manager again, calibrate the altitude to 452m and start recording.

A setting would be great where you could tell Locus to make an automatic calibration  to the altitude value in altitude manager every time you start a track recording!

Hope I could make my point,
cheers,
shushuk

12
Hi,
I have already posted this question in the german section, but maybe I get more response here.

I have a Smartphone with a barometric sensor and would like to use it for altitude measurement on MTB-tours.

As most of the tours start at home and therefore at the same altitude it would be great to have an automatic calibration of the altitude on the specified value ("Höhen Manager" (Hight Manager?) --> "Luftdruck" (Air Pressure?)) when starting to record a track!
As I understand it I have to calibrate the altitude manually every time in advance an then start the record.
Is this correct?!

Cheers
shushuk

13
Hallo!

Im Höhenmanager / Luftdruck kann man ja die Höhe zur Kalibrierung des Barometers eintragen. Ist es möglich, dass Locus bei Start einer Aufzeichnung automatisch die Kalibrierung vornimmt und bei der eingetragenen Höhe startet?

Bsp aus dem Mountainbiken:
Die meisten Touren starten von daheim bei immer gleicher Starthöhe. Die wäre im Höhenmanager eingetragen. Bei Aufzeichnungsstart würde die Höhenberechnung jedes mal automatisch auf diese kalibriert.
Geht das?

Bei einem anderen Startpunkt und bekannter Höhe müsste man natürlich vorher in den Höhenmanager (in der rechten Leiste schnell erreichbar) und die Starthöhe eintragen. Dann Start der Aufzeichnung.
Aber bei immer gleichem Startpunkt würde man sich dieses Prozedere sparen, was sehr komfortabel wäre.

LG
shushuk

14
With Android 6.0 Marshmallow ante portas: Is there anything to be considered in this regard?

Thanks for showing me the procedure... I will try that.
shushuk

15
Hi!

My Sony Z1 compact was stolen... >:( The phone was rooted, Android 4.4.
Quite a short time before it was stolen I inserted a new SD-card, and kept the old one as a backup. As far as I can remember I installed Locus on the SD-Card completely.

I now have ordered a Z3c (Android 5.x). If possible I try to avoid a root of the device. Therefore I consider a "splitted Installation" where the app is located on the internal Memory and maps on the sd-card.

Question: Do I have any Chance to recover my track recordings from the old sd-card? I have quite a lot of records which I don't want to loose... Which way should I choose?

Thanks for your help,
shushuk

Pages: [1] 2 3 4