Wear for Locus Map beta testing

[fera]

Hi there!

I've just given Majka's SGT-workaround a try, and I got to say it's working like a charm!
As soon as I started SGT on my watch, I got stable HR reading with no droppings at all, although neither the Locus Wear app, nor the SGT app was running in the foreground, I saw my watchface the whole time.

So I think Majka is completely right, somehow SGT "forces" the HRM sensor's SW-side in a stronger way than the locus add-on and that way the readouts are always executed, regardless of the watches' state. (During testing my display was off, until I raised my hand, but it did not matter for Locus, the measurements were always made)

Also I noticed a significantly more severe battery drain on both my watch and phone when SGT was running along with the locus add-on, so it would be really great if this workaround was not necessary 

Here is my screenshot with time on the x axis:



Oh and yes, the zero values on the plot were present until I started SGT.

[Marie Zemanova]

Also I noticed a significantly more severe battery drain on both my watch and phone when SGT was running along with the locus add-on, so it would be really great if this workaround was not necessary 

I wouldn't expect much lower battery drain from dropping the SGT should it not be necessary.

The main difference in battery consumption on the watch is because Locus alone doesn't get the HR sensor working. On the phone, there might be slightly more battery drain if the SGT app on phone is running as well. Additional difference would be that probably more communication is happening over BT when the HR is working fine as well.

[Danjel Rojka]

Another thing, would it be possible to set and save the dashboards depending on the activity? Further it is only possible to set the dashboards when the recording is running. It is not possible to set the dashboards before.

[milan.cejnar]

@Danjel Rojka
Hello, sorry I have forgotten to answer your last question. Dashboard presets depending on the selected track recording profile is a good idea and it could be really useful. It is not planned at the moment (I will be focusing mainly on communication issues in the next update) but some time later I think this could be doable.
Dashboard configuration without (i.e. before) active track recording would be a nice to have feature but I think it is not exactly a deal breaker. I will definitely keep this in mind though.


Anyway, for you all guys, there is a new 1.1.7 version for the watch (phone version remained at 1.1.6). There are only minor fixes i.e. there was a problem with opening the menu on some older watches and some crashes or weird behavior during track recording start. I also added "wake lock" to the track recording service on the watch so now the service should really be running in the background reliably but it will not probably solve issues with HRM caused by communication problems.
So maybe just try the new version out and see if it helped in any way or if it is the same. Any other feedback or reports of problems are also very welcome

Also sorry that there is once again kind of less activity with the Wear add-on but I am pretty busy with writing a new Locus add-on for Samsung Gear/Galaxy Watch at the moment. We are hoping that we will be able to unify parts of the Gear and Wear add-ons later so both add-ons could benefit from the development.

Have a nice weekend!

[sbouju]

Hi everybody!
Can (or could be) "Wear for Locus" be installed on a secondary standard Android "slave" machine, instead on an "wearable" one?

[milan.cejnar]

@sbouju Hi,
Wear OS and Android are practically identical and share a lot of APIs, but generally the answer is no because the Wear OS part is also using some features and components that are not present in normal Android. Significant parts of the code from the add-on could be reused to make such "slave" add-on for normal Android but it is unfortunately not that trivial and the Wear add-on cannot be installed to Android OS as is.
The Wear for Locus Map add-on's code is open-sourced so anyone could try to hack the existing code and port it to make a new Android add-on. But neither Menion nor I plan to make such an add-on in any foreseeable future unfortunately.

Btw. I am curious what your use case would be - could you please send me a PM? Is it because of Android OS watch or for some other reason?

[sbouju]

Thank you for this answer ! 

... I am curious what your use case would be...

For example, I can think of a master full Locus working on a large tablet, well protected in a bag, and a slave one with less possibilities, working on a rugged, waterproof, etc., a little unit I can wear like a watch on my wrist, like are the Unihertz "Jelly Pro" and (soon available) "Atom".

Similary, I am a very old user of the "qtVlm" program, a powerfull marine navigation application working on all plateforms, and which is going to work very soon with such another extension ("qtVlm Companion"), installable indifferently on a Android wear unit or on a more  "classic" smartphone, assuming (for example) the main program is working on a PC inside the boat.

[Peter Jurík]

Hi Milan,

are you planning to release new version for android wear  standalone app or always it will be depend on mobile?

[milan.cejnar]

@Peter Jurík
Hello, at the moment we are not planning on adding stand-alone functionality for Wear OS platfrom.

[sbouju]

Hi,
Is there somewhere a specific and complete documentation about all can be done with the couple LocusMap - Wear for Locus ?

Edit: found this: https://docs.locusmap.eu/doku.php?id=manual:user_guide:add-ons:wearforlocus

[menion]

Hi, probably the wrong topic? Here it is focused on "Wear" watches, so the author of "Garmin" addon is definitely not watching this topic.

[sbouju]

Oooops...!
Sorry, Menion, I had even not seen my mistake, thank for your answer and for the notification system 
I shall try to clear have cleared my above message, as it relate a disapeared problem...