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.


Topics - shushuk

Pages: [1]
1
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

2
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

3
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

4
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

5
Hallo zusammen,

seit dem letzten Update werden mir bei manueller Planung von Tracks in Locus (Quelle zur Routenberechnung = BRouter) "Zwischenziele" als Icons angezeigt (in der Karte und im Diagramm). Nämlich genau dort, wo ich zur Planung einen Punkt erzeuge.
Ich finde die Option einfach nicht, um das auszublenden bzw. gar nicht als Punkt zu erstellen.Ich möchte nach Speicherung des Tracks einfach nur den Track sehen.
Ist sicher nur eine Kleinigkeit, aber ich finds nicht....... :-\

Danke für Eure Hilfe!
shushuk

6
Hallo,

Beim Eintragen von Höhendaten aufgezeichneter Tracks werden teils utopische Werte berechnet.
Hab mir dann mal das Profil anzeigen lassen und festgestellt, dass die Höhendaten stellenweise extreme Ausreißer haben (-30.000m und mehr).
Die Höhendaten hab ich für die offline-Verwendung downgeloaded. Das ist schon eine Weile her.

In der Hoffnung, dass hier Bereinigungen/Korrekturen stattgefunden haben, folgende Frage: kann man für bereits downgeloadede Bereiche einen erneuten download erzwingen? Oder gibt es alternative Quellen und wie bekommt man die nach Locus?

Als Beispiel folgende Koordinaten:
N 46.32924  E 013.12046  -->  -32.768m
N 46.33279  E 013.12668  -->  238m (korrekt)

Danke und Grüße
shushuk


7
Hi

I store my finished recorded tracks in an appropriate folder, called “Recorded”. For this folder I have defined a track style, which is blue.
During the recording of a track the defined colour is red. So I can distinguish between an old recorded track (which I perhaps follow) and the actual track.

After finishing the recording of the new track I store this track in the folder “Recorded”. But the style remains the same, the colour still is red.

Is there an option to switch the style to the folder-definition automatically when such a folder-style is defined and a track is saved to this folder?

Regards
shushuk

8
Hi everybody,
I would like to move a topic already discussed in german forum (but not solved) here. Thanks to user 0709 so far !!!

Short description:
I am using Locus Pro 3.2.3 on a Motorola Defy (Stock Rom) and would like to use the feature display activation by gesture control. Anzeige-->Display(de)Aktivierung (in german version) is ON with the gesture control option set.

Proximity sensor is working (tested with the app Proximity Sensor Finder). At least it switches between 3 and 100 cm (nothing inbetween)

Does anybody else have had this problem and found a solution?
Should I wait for next official version with an (hopefully) updated gesture control feature?

Thanks for any help
shushuk

9
Hallo,
ich verwende Locus Pro 3.2.3 auf einem Defy.
Beim Mountainbiken möchte ich bei einer laufenden Trackaufzeichnung mittels Näherungssensor mein Display wieder aktivieren.
Ich habe die entsprechende Einstellung unter Anzeige --> Display(de)Aktivierung --> Aktivierung EIN (mit der entsprechenden Option für den Näherungssensor) gesetzt.
Nur leider tut sich nichts beim Wachteln vor dem Gerät.... (hoffentlich schaut mir dabei keiner zu! :-)  )

Hat jemand eine Idee?

Danke und Grüße
shushuk

10
Troubles & Questions / Locus Pro crashes during start-routine
« on: July 10, 2013, 08:17:00 »
Hi,
I hope someone can help me: I use Locus Pro very frequently but am unable to start it anymore...

I installed 2.13.1, I think it worked for some times normally (But I am not sure about that, because I rarely used it the last few days).

2 days ago it started to crash again and again when I try to start locus. Mostly the following happens:
During start routine between 60-70% („Vorheriger Status“ – „Tracks“ (I use the german version)), it takes abnormally long, then at 80% at „Initialisierung…Online-Karten - Kartenelemente  it crashes.

In rare cases the start routine finishes (still after abnormally long 60-70%), but at first action it crashes.

I created a Catlog File as described and sent it per mail.

Do I have access to recorded tracks on my sd-card? Mayby one of the last tracks is broken somehow?!?
Or is there a Maximum size for tracks-db?


However, I definitely need locus on Saturday for several days (Mountainbike-tour in the alps)!!!!
I have an older Version of Locus Free installed but don't want to mess up database-versions.

I use an unrooted Defy with Android 2.2.2

Thanx for any assistance!!!
shushuk

11
Troubles & Questions / Remove onboard calibratet maps
« on: May 11, 2013, 14:27:03 »
Hi,
I don't find this in locus:
I made a simple test calibrating a photo on board. How can i remove this 'overlay'(?) again? Only way i found is deleting the kmz file in the 'mapitems' folder. Is there a better solution?
Thanx for help
Shushuk

12
Hi,
I really appreciate the edit-function to get rid of some errors when recording a track. Sometimes (when I forget to pause the recording while I enter a building) a location is recorded thousands of km away.
So some of my bike-trips have around 15.000 km :-)
After correction of the track by using the new edit-feature the short summary in the tracklist (duration | km) under the trackname still shows the old (wrong) km, while the 'information'-window shows the correct one.
How can I update the summary?

And something else:
the track-length in the track list is shown in km up to a certain date (about dec. 2011 in my list). After that the length is shown in metres in the format 123456m. A '.' would be very helpful --> 123.456m or otherwise the 'old' km-value like 123.5km (for me the better solution). (Where) can I configure this?!

I really use this app a lot - for me the perfect assistant for hiking an biking!!!
cheers
shushuk

13
Troubles & Questions / Locus Shop not working
« on: June 01, 2012, 12:01:41 »
Hi,
I get an Error when selecting Locus Shop from the main menu. The error is not specified an further (in german; "Fehler: Unerwartetes Problem!..."
Locus (Pro) Version 2.4.0
Android Version 2.1
Smartphone: Motorola Defy

I would have liked to check the download fee for OSM-Cyclo Maps.

Cheers,
shushuk

14
Troubles & Questions / OCM-maps not accessible
« on: July 19, 2011, 08:23:35 »
Hi,
the online OCM (= OSM Cyclo) maps have not not been accessible within locus the last days. I get "Zugriff verweigert" (german version) when trying to download tiles.
Is this a permanent problem, do I have to change any settings?

Thanks for help,
shushuk

15
Troubles & Questions / External Bluetooth GPS
« on: May 12, 2011, 10:55:24 »
Hi together,
I am new to this forum, using the free version of Locus (1.7.4) at the moment for testing purposes, comparing it to Orux and ape@map on a Motorola Defy.

I would like to know whether you have actual information on the troubles using an external bluetooth gps mouse without third-party-tools as 'Bluetooth-GPS'.
I have read the threads on this issue and still don't know whether this is a priority topic and has a chance to get solved soon.
Using an external mouse is my standard way of using these apps to preserve battery. When using the Locus-internal Bluetooth-GPS-Option I don't get a fix at all.

Another question (maybe in the wrong forum, but hopefully I get some honest answers ;-) ): Is there a difference between the mentiond apps above regarding battery consumption when recording a track, assuming 'equal' conditions (recording intervals, display-usage, etc...).

Thanx for any Information
shushuk

Pages: [1]