Recent Posts

Pages: [1] 2 3 ... 10
1
Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« Last post by Žajdlík Josef on Today at 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.

2
Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« Last post by Andrew Heard on Today at 01:58:23 »
V 3.32.2.8: @menion - the Route Planner just gets better & better. The latest changes are very impressive.
3
Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« Last post by balloni55 on Yesterday at 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"
4
[DE] - deutschsprachiger Forumsbereich / Re: Fieldnotes Pro
« Last post by balloni55 on Yesterday at 19:40:03 »
Hallo Ray,
hab dir leider keine Lösung, bei mir klappt das.
Frage:
es gibt eine 2. Möglichkeit das Listing aus FN anzuzeigen
im Fenster wo du den Log schreibst rechts oben den 3-Punkte Button > Listing anzeigen
gehts damit?
Wolfgang
5
[DE] - deutschsprachiger Forumsbereich / Fieldnotes Pro
« Last post by raydavids on Yesterday at 19:22:57 »
Hallo!
Ich hätte mal wieder eine Frage bzw. Hilfe bzgl. Fieldnotes Pro. Wenn ich länger auf einen Log klicke kommt doch anschließend eine Mehrfachauswahl... u.a. Listing anzeigen. Leider passiert bei mir nichts wenn ich mir das Listing anzeigen lassen will. Hat jemand einen Tipp? Vielen Dank im Voraus. Gruß Ray
6
I have also the problem, that  both Locus-addons (GSAK database and (!!! ) the GeoGet database) are not working anymore. After an Android update 8.0 the waypoints are not displayed in the livemap. The same database is correct displayed on an older Android version (6.0).

As workaround I import the caches from the database.


Gesendet von meinem ONEPLUS A3003 mit Tapatalk

7
Wear for Locus Map / Re: Wear for Locus Map beta testing
« Last post by Marie Zemanova on Yesterday at 13:55:15 »
If I understand correctly, when you start SGT the Locus add-on is running on the watch as well at the same time? Which one stayed in the foreground?
Yes, both are running at the same time. And for me, neither has to run in the foreground, it is working even if both apps are in background and the watch is completely dimmed. It doesn't make any difference which app is started first and which second. As soon as both are running, I get the HR without any problems in Locus.

What I am suggesting is that SGT is doing something different and is for some reason is better at getting the sensor to work and to keep it working.

Locus is without any problems reading the heart rate from the sensor if the sensor is already running. But (at least on my watch) the Locus wear app is unable to start the sensor and to keep it at work. It needs SGT to do it instead.

The first experience I had was somewhat better - Locus was able to start the sensor when the app was in foreground and not dimmed but as soon as the watch screen dimmed (with Locus still in foreground), it couldn't keep the HR sensor at work. At least that is my current interpretation of the problem.

You could try this for yourself and it might be good to have another confirmation: Install the SGT tracker app, get it working on the watch and run Locus at the same time. If my reasoning is correct, you would then get constant HR readings as well, no zero values.
8
Wear for Locus Map / Re: Wear for Locus Map beta testing
« Last post by fera on Yesterday at 13:29:11 »
Regarding heartrate from the watch:
The Locus app was on the watch in foreground, on screen. I have disabled any power saving feature I found/I could access. Unfortunatelly, I cannot fine tune it the same way as the phone.
Locus was running fine, but the HR was not read (this time, on its own it didn't get even single reading). As soon as I started SGT on the watch, Locus on the phone started to display HR, the recording includes both HR and cadence from ANT+ sensor without a problem and without a single glitch anywhere.

Majka, help me clarify something :)

If I understand correctly, when you start SGT the Locus add-on is running on the watch as well at the same time? Which one stayed in the foreground?

Did this help the HR readings if you haven't used an ANT+ cadence sensor as well?
My question is, do you suggest that SGT somehow "pushes" the readings to the LM on the phone?

Thanks!
9
Wear for Locus Map / Re: Wear for Locus Map beta testing
« Last post by Marie Zemanova on Yesterday at 11:48:19 »
I am using MIUI 8.5 and can confirm that without disabling battery optimizations Locus Map quickly loses GPS in the background or gets terminated. Wear add-on surprisingly runs even without disabling optimizations at least on my phone.
I have found ton of messages regarding problems with bluetooth on MIUI. It does work for some versions - somewhere in the 8.5 range :) - but the next few up have the problem. It is not limited to the WearOS devices, it is a general BT problem, people cannot connect to car devices as well. I would say, somebody has probably forgotten to get the BT connection an exception from optimisation in system in these versions.
I didn't find anything about possible solutions.
What I am doing seems to be working, I have confirmed it again today: Unless I lock the WearOS app in the memory, it just looks like everything is running fine - but the BT won't either connect at all, or the WearOS app is "saying" it is connected, but the connection is not really running stable (for example no screenshot possible, etc.). Locus on Wear is getting the "not connected" message at the same time.

Since my first message, there was update of system/wear os app/google play services on the watch as well, and since then I cannot get single reading of HR from Locus on Wear by itself, where the previous version got the values at least if Locus was in foreground and not dimmed. Might be some optimisation somewhere in the updates.

Majka
10
Wear for Locus Map / Re: Wear for Locus Map beta testing
« Last post by milan.cejnar on Yesterday at 11:15:53 »
Hello Majka,
I am using MIUI 8.5 and can confirm that without disabling battery optimizations Locus Map quickly loses GPS in the background or gets terminated. Wear add-on surprisingly runs even without disabling optimizations at least on my phone. I might try to update my MIUI and see if it gets worse in the newer versions. But disabling the optimizations is basically required for Xiaomi devices in order for GPS to run correctly in background, seems there is no way around that unfortunately.

As for the watch it is really a mystery. I do not understand why would your watch just kill the foreground Locus HRM service. When I prepare the next beta I will try to show popup toast messages on service start and stop and also reenable HRM debugging so that we could see if HRM sensor is really not feeding any data for you even with the app in the foreground.

Best Regards
Milan
Pages: [1] 2 3 ... 10