Recent Posts

Pages: 1 [2] 3 4 ... 10
11
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
12
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
13
Versions / Re: [APP] - version 3.32.+ ( 31. 7. 2018 )
« Last post by menion on Yesterday at 09:05:55 »
@Andrew Heard
ah, here comes confusion. The red circle isn't clickable! It allows to drag & drop to create a new shaping point, but click do nothing! What happens to you is that click on this point, selected nearest trackpoint on track, so you had feel like you click on track.
I've anyway improved this now, and this red circle now offer information about this track segment with an option to recalculate it.

Problem with backup: hmm crash needs logs. Anyway problem with restoring, hard to say. App should check if config.cfg was changed and use it or overwrite based on this.

@freischneider
understand your point with dragging of trackpoints, but I still do nothe t like it. On smaller screen, you often drag map with fingers and with this feature, you will have to worry even more to not to drag part of existing route. Use long click > it's even faster (mainly with new Beta version).

@tapio
export me please your track to GPX, I'll check why this happen, thanks.

@alezy
thanks, should be fixed now. New Beta? Most probably today.

EDIT: Beta version is out!
14
Troubles & Questions / Re: Default set up - one click?
« Last post by alanmcd on Yesterday at 08:49:59 »
Thanks - these options get me closer
15
Troubles & Questions / Re: Navigation - 'null description'
« Last post by menion on Yesterday at 08:49:30 »
Alan, why don't you post a screenshot or at least write an error number?
What android device are you using (Android version)? Does it fail even if you compute route in Route planner?
16
Troubles & Questions / Re: Default set up - one click?
« Last post by balloni55 on Yesterday at 08:35:24 »
Hi Alan
i think some of your whishes can be done by using "presets"
http://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:presets&s[]=preset

BTW: 2+3, do once a long click on rotate button and select "rotate"

Wolfgang
17
Hi,
in der BETA Version gibt es eine  "Experimental" Einstellungen, wo du z.B. Sensordaten speichern kannst.
Ob das deinen Wunsch erfüllt kann ich nicht sagen, ein Versuch ist es bestimmt wert ;)
Behalte aber im Hinterkopf: Experimental ist ein Versuchsstadium, welches nicht unbedingt für immer verfügbar sein wird!
Gruß Wolfgang

18
Troubles & Questions / Default set up - one click?
« Last post by alanmcd on Yesterday at 04:59:35 »
I use locus the same way very often (most often). This is the setup/clicks
1. double tap for options
2. click rotate
3. click rotate again from popup
4. click locate
5. click +/- to get close to my desired zoom
6. click lock
7. click Lock the Zoom - this always moves the zoom away from the previous zoom, so
8. several (sometimes) clicks to re-adjust the zoom to my previous choice
9. sometimes the zoom does not actually zoom the map (vector zoom) it jumps into a raster view and I have to go in and out to get back the proper clarity.
10. click record
11. click dashboard (because it often seems to just disappear and not stay on)

In all it takes about 15 clicks or more to get my screen the way I want it.
Is there a way to get all this done in one click by setting default a view? Or at least a good part of it?
thanks
Alan
19
Troubles & Questions / Navigation - 'null description'
« Last post by alanmcd on Yesterday at 04:51:16 »
Hi,
I use BRouter because I am offline a lot. But even when I am on a main road, I often get a navigation failure with the error as an orange box with 'null description' and a number under it. I try over and over with no change. The nav fails to provide a route. If I move one some way and try again, it can work. Why do I get this error and how do I avoid it?
Alan
20
Is the GraphHopper offline routing "project" dead? None of the links on develar.org for any of the routing files work. Any other options for offline routing at this point besides BRouter?
Pages: 1 [2] 3 4 ... 10