Locus Map - forum

Content & Tools => Add-ons => Wear for Locus Map => Topic started by: milan.cejnar on December 06, 2017, 19:50:53

Title: Wear for Locus Map beta testing
Post by: milan.cejnar on December 06, 2017, 19:50:53
Hello,
we have just released a beta version of Wear for Locus Map which is an add-on to Locus Map for your Android Wear watch and you are more than welcome to try it ;) Please see Wear for Locus Map on Google Play. (https://play.google.com/store/apps/details?id=com.asamm.locus.addon.wear)

The version is not a very polished yet and is released mainly for testing purposes. The application now supports

- Map screen with zoom controls and side navigation panel when navigation is active.
--- know issues - there are still some issues with rendering navigation track on the map, it is kind of huge compared to the rest of the map. And the navigation on the watch doesn't currently show usual question mark symbol when off track.

- Track recording
--- start/stop/pause/add waypoint controls + track recording profile select before the recording start
--- showing basic statistics of current recording

For Android Wear 1.x users
- install Wear for Locus Map on your mobile phone and wait a few minutes for your watch to synchronize. The application Locus Map should appear in your application menu.

For Android Wear 2.0 users
The add-on must be installed separately for your phone and watch because the add-on is not part of the Locus Map app itself so that we could keep the whole add-on independent/separated and mainly open-sourced. In order to install we recommend to
- install Wear for Locus Map on your mobile phone
- then install Wear for Locus Map on your Android Wear 2.0 from the watch Google Play. The application Locus Map should appear in your application menu.

Please share if you have any crashes, trouble with the communication between the device and the watch or generally any inconvenient behavior or user interface problems.
So enjoy the testing and thank you in advance for any feedback :)
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 06, 2017, 20:46:38

made a short test.
working good

but one question: when the backlight on the watch switch off the map is inverted. on the "versions" in the past the maps are shown normaly
was this intended ?
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 06, 2017, 21:52:34
Hello, thank you for such a quick feedback :)
Regarding the inverted map - yes it is intended, do you find it confusing?

When the backlight switches off the watch enters "ambient mode" and the controls should be disabled in this mode (i.e. zoom function of the map should not work in this mode). Same for track recording - screen goes black&white and controls disappear to let the user know, that the watch is in the ambient mode. The communication with the mobile phone stays on though and the screen refreshes regularly so there is still significant drain on battery even in this mode.

We could disable this feature but I think it is somehow customary to simplify the UI in ambient mode and go black&white or dark pallete when in this mode. But the whole point was for the app to be less confusing and let the user know of the switch to ambient so this feature is still up for a discussion.
Title: Re: Wear for Locus Map beta testing
Post by: Peter Jurík on December 06, 2017, 23:10:00
Casio WSD-F20 (Android 2.6.0.176354550)
Application is super.
Missing: settings and using hardware buttons for zoom in and zoom out.
Navigation by gpx from application.
I can't reach menu for tracking when I'm in map.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 07, 2017, 09:23:20
Hello Peter,
thanks for the tip to support HW buttons for zoom function, this feature is really not implemented yet.

Could you please explain what do you mean by that you are missing navigation by gpx from application? The watch should simply receive navigation information from the phone app, so if you set up your navigation in Locus Map you should also automatically see navigation information on the map screen on the watch.

And what is your problem with reaching the menu? Navigation drawer should open when you swipe downwards from the very top of the screen. It doesn't work on map screen?
Title: Re: Wear for Locus Map beta testing
Post by: Carsten54 on December 07, 2017, 19:34:49
Hi all

I can't see a map on the watch. I only see the start button and the statistics. I can start and stop the recording. One bigger problem: The button "add waypoint" shows the message "waypoint added". But the message is shown until the watch is restarted.
Sony Smartwatch Android Wear 1.5
OnePlus X Android 6.01
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 07, 2017, 19:39:14
Hello, thank you for such a quick feedback :)
Regarding the inverted map - yes it is intended, do you find it confusing?.

Today i made a 2 hour test

app is working really good, no restart or something. way better than the past

yeah, i find it confusing. on the data screens its okay but not necessary.
on the map screen a lot auf maps infos are hard to see with the invertmode, in the normal mode it is much better even when backlight is off (testet the old version).
also in this invertmap mode you get big white areas because the maps on the phone show wood. look a bit like broken display
the refreshing in ambient mode is ok. i don´t really see any different to the normal mode on the maps screen refreshing.
maybe a option to deactivate the invert map mode ?

Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 08, 2017, 07:18:49
Hello Carsten54,
waypoint message should not get stuck, definitely a bug. Thank you for reporting this, I will try to fix it in the next version.
Map is accessible form the navigation drawer which should pop up when you swipe downwards from the very top of the screen. The drawer also opens the first time you open the app, but I see this is also somewhat confusing :/
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 08, 2017, 07:37:48
Ok guys, I see there are some usability problems, so I would be really glad to know your opinion on

Or if you have some other idea on how you would like the app to behave then please let me also know :) Thank you

P.S. skwal thanks for the test. I definitely see your problems with inverted map.
Title: Re: Wear for Locus Map beta testing
Post by: Peter Jurík on December 08, 2017, 08:21:19
Hi milan.cejnar

Okey I found, how I can reach menu from map. Ok when I started navigation from  locus(mobile) I saw navigation points. Is it possible add suport for standalone application for navigation? Watch has gps and barometer.

I found problem in application :  when i'm in map and watch go to sleep after  wake up is map in same position mobile has changed position but watch not. I must click on zoom in/out and map  has refreshed and show correctly position.

For inspiration see ViewRanger watch app :) https://play.google.com/store/apps/details?id=com.augmentra.viewranger.android
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 08, 2017, 10:44:07

1. Inverted map in ambient mode - probably just get rid of it completely. Only the zoom buttons would hide and navigation bar would turn black&white to notify about ambient mode and map would stay the same?
3. Maybe with an improvement that the app would open to the last screen you have visited last time so that you wouldn't have to go through the main menu every time you open the app?


Both sounds good for me


The menu drawer on the top is a good thing in my mind.  you should make it more clear how it works in the app description.
on a round watch it isn´t that logical as on my square wtach
On the data screen is it possible to show the time and the % of the phone battery ?

Today i tested it 3 hours. No  errors or so
But one question
Autorotation: is it deactivated? tried different option (autorotation, screen on, etc) on the phone and different zoomleves on the watch, the watchmap never rotate
Title: Re: Wear for Locus Map beta testing
Post by: Carsten54 on December 08, 2017, 20:30:34
Map is accessible form the navigation drawer which should pop up when you swipe downwards from the very top of the screen. The drawer also opens the first time you open the app, but I see this is also somewhat confusing :/
Sorry   ::)
Thank you for the hint. So easy, but difficult to find.   ;)
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 10, 2017, 10:48:00
@Peter Jurík,
could you please describe the problem with the map getting stuck a bit more? From my testing I see that map either goes to ambient mode after a while and keeps receiving updates or, if ambient is disabled, the watch goes to sleep and then after wake up application starts again and returns to track recording screen by default (right now it should not remember that map was actually opened previously). Do you use ambient mode (darkened screen/inverted map) or does your watch really return to map screen after wake up automatically?
Standalone function will not be supported in this version. What would you expect from standalone application? Would basic track recording functionality be enough?

@skwal,
thank you for testing. The navigation drawer should really be more advertised, we will try to make it more clear that it is there.
Autorotation of the map is currently disabled for the watch, but thanks for lettting us know, that you would be interested in this feature.

@Carsten54,
you are welcome :) We will let the navigation drawer peek for a little while every time any screen is shown to remind users that it is there. Thinking of adding some kind of intro/tutorial screen in the future.
Title: Re: Wear for Locus Map beta testing
Post by: Peter Jurík on December 11, 2017, 21:45:14
@milan.cejnar

I have run Locus on mobile as service. Ambient mode in watch is disabled. When I run locus on watch after wake up point with my gps on same postion before sleep. I must zoom in/out app for refresh data.

Step for test:
1. Run mobile Locus as service home button and set to sleep
2.  Watch run to map
3. Watch going to sleep
4.  must go away from previous position
5.  after cca 10 minutes wake up watch
6. mobile is refresh application and maps, watch still on same position before sleep
When you needed , I should add video.

Feature:
1. recording to watch and sync locus it will be nice feature
2. upload route to watch and navigation by route , and warning when i'm off route will be very nice feature, caching maps around gpx for standalone using
3. show elevation and gps position will be fine not needed.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 12, 2017, 17:57:20
tested it agian for 3 hours

few minutes after the start my sony smartwatch restarts. i don´t know why, because of locus, maybe because it was so cold outside, i don´t know

an hour later the map on the watch was in the ambient mode but didn´t refresh since a few minutes
tapping on the screen did not work, menu drawer also don´t work
locus stayed in the mode with light off. think the app was frozen
swipe to the side to the watch menu, light goes on and everything incl locus worked again.
happend only on time
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 13, 2017, 08:18:14
@skwal
that is odd. And the map was in the ambient mode and zoom buttons were hidden? Because in ambient mode the touch screen should be disabled and the app should be woken up from the ambient first (by button/wrist gesture etc.) It would explain why application seemed unresponsive - swipe to dismiss the application should have not been working either though. Not receiving updates to the map is definitely a bug.

@Peter Jurík
thanks for a description of the problem, something is definitely wrong, will look into it.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 14, 2017, 15:47:52
@skwal
that is odd. And the map was in the ambient mode and zoom buttons were hidden? Because in ambient mode the touch screen should be disabled and the app should be woken up from the ambient first (by button/wrist gesture etc.) It would explain why application seemed unresponsive - swipe to dismiss the application should have not been working either though. Not receiving updates to the map is definitely a bug.

i can´t tell you
i was on the bike and it was in the evening. so the display was hard to read
but when in ambient mode the display can´t be woken up by tap my watch is most of the time not in ambient mode. the display is inverted but i can always wake my watch by tapping on it.
and am happy with that. my watch core is mounted on the bike, so no side button or a really tiny one and also gesture deactiveted

edit: small testride: the watch is in ambient mode, map inverted, zoom buttons hidden.
But i can wake it by tapping on the screen
Title: Re: Wear for Locus Map beta testing
Post by: skwal on December 15, 2017, 20:47:25

the crash of the watch at the first Start happend again today.

whats new in the new Version?
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 16, 2017, 19:55:41
@skwal I have sent you a PM regarding the bug

Anyway, new beta version doesn't really bring any new features, it's mostly some bug fixes and optimalizations and small UI changes. There will still be some issues until new version of Locus Map comes out. But all in all I would say the add-on is almost ready for release and we plan to keep working on it gradually adding new features and improvements in the next months.
Title: Re: Wear for Locus Map beta testing
Post by: Peter Jurík on December 21, 2017, 16:52:30
@milan

Hi,

Latest version is for me stable. I 'm using with sleep mode. When watch are woken up application is correctly showing my position.

I'm looking forward for zooming with hardware buttons and other features.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on December 22, 2017, 09:33:12
Hello guys,
I have just published version 1.0.0 of the add-on. Again no new features but this should be really stable release and is intended to be used with the last Locus Map v3.28.0.
We plan to start gradually adding some new features now that the add-on is (hopefully) stable enough.

Please if you will have any problems with the add-on and you use Locus Map v3.28.0 then I will be glad if you report it here or since it is no longer beta you can also report it as usual to our help desk help.locusmap.eu

If you really want some new feature and you will find the time please add it as usual as an idea to our help desk so that others could vote and we could see which features would be preferred.

Finally feel free to continue this thread or even start a new thread here at the forum if you have any general feedback and/or interesting topic regarding wear add-on which you would want to discuss :)

Hope you will find the add-on useful and will enjoy using it during your outdoor activities :)
Title: Re: Wear for Locus Map beta testing
Post by: mzperx on December 24, 2017, 15:59:09
Hi Milan,

thank you for this addon! Saturday I did a 3 hour workout with this addon and it worked fine. It was stable and fast. I used 1.5 hours with "display always on" mode and 1.5 hours with "display always on" disabled. In the first case the application consumed abut 10% battery and in the second case about 35%.
I have Nexus 5x with Android 8 and Samsung Gear Live with Android Wear 1.5.
One can use "always on" mode in workouts <3 hours and for longer workouts the "always on" mode should be disabled.
 
Some suggestions:
#Wet clothes can cause unexpected touches on the screen this is why better if you put recording controls to different page or combine the controls with unimportant statistical data in this case the user will not leave the screen here and it will not cause any unexpected touch a trouble with recording.
#Device and wear battery level indicators and/or alerts,
#configurable statistical data (what I want to see in the stat panel is depends on the workout),
#configurable ambient mode (invert mode on/off)
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 03, 2018, 19:23:29
Hi everybody,

Is this forum topic the best and only place for finding all useful info about the use of Locus with an Android wear watch ?

I have not yet such a watch, at this time, so I should be very interested to see a short list of the best suitable models for Locus, and pros/cons of each models...
Title: Re: Wear for Locus Map beta testing
Post by: mzperx on January 04, 2018, 10:29:37
@sbouju

I think there is no "the best suitable models for Locus". The addon can run on newer and on older devices too. I have Samsung Gear Live (it was released in 2014) and the addon works fine for me.
There is no special requirements for the watch because this addon is only a visual extension of the phone applicaton. It doesn't use any special hardware of the watch (eg. hearth rate/gps etc...) it shows only what the phone collected.
I suggest that you choose a watch what best fits your requirements (functionality/looks like etc...) and then you can ask it here may someone has experience with that watch with Locus.
The only thing what I would consider if bought a watch the hardware buttons. In my experience the touch screen is unusable when it raining. The actual addon doesn't support buttons but maybe it will in the future.
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 04, 2018, 11:50:45
>> I suggest that you choose a watch what best fits your requirements (functionality/looks like etc...) and then you can ask it here may someone has experience with that watch with Locus.

As an ex-Casio watches addict, but living now (and happy) with a (not-Android-wear) Garmin fenix 2, one I should consider attentively among some others is this under...

(https://i.ebayimg.com/images/g/PoUAAOSwMvtZRUC-/s-l400.jpg)

Anyway, see under a very satisfying LocusWrist solution ;)

(http://img110.xooimage.com/files/b/d/3/wechatimg62-53b6bd6.jpeg)
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on January 04, 2018, 12:29:21
I can confirm that all watches running Android Wear should be supported. The add-on is currently intended as a companion app to the Locus Map running on the phone so there are no special HW requirements for the watch. Support of HW buttons and "rotating side button" is planned.
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 05, 2018, 10:37:49
Tested yesterday in some physical stores around me: the main problem is that it is difficult to know if such or such "smart watch" they sell is working under Android Wear 2.0 or not... And vendors generally don't know!
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 07, 2018, 11:15:59
Does somebody knows if the Xiaomi Amazfit "Pace 2" and "Pace 2S" watches are (will be?) 100% OK for this purpose...?

(https://s18.postimg.org/imxpr6j51/Screen_Shot_2018-01-07_at_11.13.05.png) (https://postimg.org/image/imxpr6j51/)

(https://s18.postimg.org/a5y7gnbzp/Screen_Shot_2018-01-07_at_11.27.18.png) (https://postimg.org/image/a5y7gnbzp/)
Title: Re: Wear for Locus Map beta testing
Post by: skwal on January 07, 2018, 13:33:18
Does somebody knows if the Xiaomi Amazfit "Pace 2" and "Pace 2S" watches are (will be?) 100% OK for this purpose...?

(https://s18.postimg.org/imxpr6j51/Screen_Shot_2018-01-07_at_11.13.05.png) (https://postimg.org/image/imxpr6j51/)

(https://s18.postimg.org/a5y7gnbzp/Screen_Shot_2018-01-07_at_11.27.18.png) (https://postimg.org/image/a5y7gnbzp/)

just check for android wear. so No


Testet the newest versions many times: no crash at start and no other problems. just working.

My only whish: rotating map on the watch.
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 07, 2018, 13:52:56
>>just check for android wear. so No

Thanks...

And same thing with the Sony SmartWatch3 SWR50, I fear...



Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on January 08, 2018, 08:03:44
@sbouju
Sony SmartWatch3 is not Android Wear watch, but it might by supported by a different add-on which Menion made, but I would have to ask. Anyway we would like to concentrate our support to Android Wear for now, so for Locus I would recommend Android Wear instead.

Sorry, my mistake. Menion pointed out that Sony SmartWatch3 is running Android Wear actually. I checked our device compatibility list and Sony SmartWatch3 should be supported by the Wear for Locus Map add-on.

Maybe please start another topic here at the forum if you want to recommend some watch by other users.

You can find some AW watch here
https://www.android.com/wear/
or here
https://www.amazon.com/b?node=15203391011

Android Wear tends to be a bit more expensive than the watch you have posted unfortunately. Depending on your region, these AW watches might be quite affordable - Moto 360 2gen, LG Watch Sport, Huawei Watch 2, Asus ZenWatch 3 (not so much outdoor/fitness)
But there are many other, please see links above and feel free to start a new topic to get some more recommendations from other users.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on January 08, 2018, 22:42:41

i´m usung the sony sw3
working great. and you can get it really cheap when you buy used
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 11, 2018, 13:58:23
made a short test...

Made a short test too, with my fresh Sony SmartWatch3, so I just begin to discover this "Wear for Locus Map beta application", and Android Wear itself !   :)


(https://s14.postimg.org/3qx7fsfp9/2018-01-11_14.27.28.jpg) (https://postimg.org/image/3qx7fsfp9/)
Title: Re: Wear for Locus Map beta testing
Post by: strandedeuropean on January 12, 2018, 14:49:07
Hi there, first of all thanks for the addon, finally a reason for me to buy a smartwatch  ;)

My main use case for locusmap is mountain biking. What I heavily use is the Strava Heatmap Biking Map as an overlay to an offline map.

Sadly this overlay isn't working properly with the wear addon. The overlay disappears as soon the map get's refreshed (phone->watch) while the phone display is turned off.

Is that a bug or do I need to change some settings?

Phone: oneplus 5 with Android 8.0.0
Watch: Fossil Q Control
Title: Re: Wear for Locus Map beta testing
Post by: menion on January 12, 2018, 15:08:57
Hello,
this definitely looks like a problem in Locus Map itself, not an add-on. I'll check it, thanks.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on January 12, 2018, 22:31:34
Hello,
this definitely looks like a problem in Locus Map itself, not an add-on. I'll check it, thanks.

yes, the overlay in the app is also not correct
on some positions it shows the correct overlay, on other positons lines which are to thick to see anything and on other positions it shows nothing.

tested the wear app 18 hours this week. not only one problem.
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on January 24, 2018, 11:26:16
It's quite magic to can see the moving map of Locus map on such a small thing than a wrist watch :) But is it so useful, finally?

If I had to choose, I think I had probably prefered a repeater of the dashboard, may be... ;)
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on February 12, 2018, 14:35:35
All of a sudden, my interest in an Android wear watch is back.

However, can the little 4-element dashboards shown in the screenshots be custom configured?
I would like very different values to be displayed if..
.. running (dist, km-time avg, heartrate)
.. mountains (dist, altitude, ..)
.. skiing (dist, max-speed, altitude, alt-lost..)

And I wonder if having Bluetooth on at the Smartphone constantly will drain a lot battery.. (tracking a ski-day usually gets very close with battery anyways.. even if one will have a few less looks on the display thanks to the watch).
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on February 12, 2018, 16:36:34
Where can I see the screenshots you are speaking about...?
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on February 12, 2018, 19:25:26
There are a lot of screenshots in the Play Store app page:
 https://play.google.com/store/apps/details?id=com.asamm.locus.addon.wear
The third shows a 4-element-mini-dash..

You can also see some profile selection..
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on February 12, 2018, 19:42:09
Oh yes, OK, thank you !  :)

I may be wrong, but for me, this screen seems to be a simple "numeric snapshot" of a recorded track, far from a real time info as is what we can see in a dahboard data field.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on February 13, 2018, 08:01:51
@H Ifang
Hello, the 4-element mini dashboard is currently not configurable, but we plan to extend it and allow the configuration in the future.
The bluetooth energy requirements are actually not that bad depending on the usage and assuming your phone has Bluetooth 4.0 or newer. I would actually expect only a couple of percents of a phone battery used by bluetooth, but again it depends on your specific usage. Of course keeping Wear for Locus Map visible on the watch all the time will indeed keep communication between the phone and the watch on and with the screen also on, even if dimmed, will drain the watch battery quite fast. My personal opinion is that for hiking and/or running disabling the ambient mode (i.e. "always-on screen") might be preferable if you are concerned about battery life.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on February 13, 2018, 14:52:17
@Milan
Thanks for the reply - I am very much looking forward to that (configurable dashboard - hopefully multi-page to get more than 4 values).
For me it is at least as important as having a little look onto the map. Most time I have to open the phone is when I want to see certain dash info like speed (but km-time not km/h), how high am I and gain (mountains), was there a new max-speed (skiing), how much distance behind etc. This of course only makes sense if all available info from the phone can also be viewed on the watch.
At the moment when running I use the audio coach mostly, but that of course is not nearly as flexible as if you can have a look whenever you want to (and sometimes surroundings are so loud you miss the coach speaking).

As for the battery drain, sounds reasonable, we will see. At the moment I still have a S6 with first battery, certainly has seen better times. BT4 is available, sure.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on February 21, 2018, 18:12:48
I had a first ski day recently. For this activity (skiing) the map is not too very helpful. It simply is very small - but at least it was mostly too close (zoom) for me. Or is the default zoom according to what was last selected on the phone? Then I think it should not be the "same pixels" as on the phone, but about the same area covered (with less resolution) - so you have the same overview. But other people may think different, so it should be configurable.
Zooming out was quite tedious, often not recognized, or activating the wipe-down (maybe locate them left and right?) (I have a Fossil Q Explorist). And of course is not too fast - maybe the reason why the usual pinch-to-zoom is not supported?

More than the map I would have liked the dashboard - but as said would be interested in some more/other values like absolute altitude, max speed or (when wearing belt) HF rate.

So looking forward to tap more of the full potential soon  :)
Thanks for reading.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on March 16, 2018, 15:55:29
I tried to use it twice for running now.
Sorry to have to say that but.. current state is pure disaster, not usable.

Next to the info I am missing, the numbers are far too small to be easily read while running (if you do not have Eagle's eyes). My watch has not the biggest screen you can get, but definitely not a small one either. There is room to make them bigger, and alternatively one could only put 3 or 2 values on one page.

While in that economy mode (ambient or not ambient, I never got that) there seem to be extremely slow updates of the values shown - when "activating" the distance jumped by nearly a km. If the app goes into that mode, it should still be a bit more dynamic, at least if a recording is active.

But the real big problem is, that the track recording was constantly stopped, restarted or paused..
In the end, I had a lot of single track fragments and also missing track parts (and of course no usable track progress while running).
While the hardware might play a role in this, and my sleeves (and even my sweat), this definitely must be implemented in a much more robust way.
Perhaps the stop button should not wait to be canceled by another tap, but auto-canceled if a constant-tap is interrupted. The pause button needs the same.
Perhaps it would be a good idea to not put the buttons on a page with values you want to watch while running, but on a separate page only opened at begin and end - so they cannot get toggled by accident (as long as the page ist not opened by accident..)

Hope there will be considerable improvements, will not use again until then.

Sorry again, but that was my experience.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 16, 2018, 16:58:06
@H Ifang hello,
no reason to be sorry at all, on the contrary I am sorry for your bad experience and would like to thank you for your time writing this feedback.
Regarding accidental button presses with wet or sweated clothes, don't you also have this problem with other applications? For example Strava or Runtastic are also using normal buttons or press areas on their tracking screen. I must admit though that these buttons are often smaller or located near the bottom of the screen which might result in less "false" touches to the screen.
Fonts on the track recording screen might be a bit small at the moment, I can image that on smaller screens 2x2 layout might be too much. Noted.
Now concerning the ambient mode. The watch should actually get updates at the same period as in normal mode, communication is not throttled in anyway, at least not in the application itself. This seems more like and issue with the Phone and Wear for Locus Map phone application. Some power saving feature of the phone could be the problem. I will definitely try to look into it.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on March 19, 2018, 18:46:06
I am quite new to smartwatches / Android Wear and do not use another fitness/running app.
Some people may have less problems with that, others more, but there must be a mode as robust as possible for this, or it will never be usable for some people. And the easiest and maybe most effective solution might be to not have the buttons on screen most of the time.

The more info on one screen the better of course - and I think the space that is there should be used for the value to show, not labels and icons (at least optionally). Maybe a small icon, labels shown on tap, but usually one knows what is where very soon. Then the font can be much much bigger on a 2x2 field too!

Title: Re: Wear for Locus Map beta testing
Post by: Peter Jurík on March 21, 2018, 14:35:00
Casio WSD-F20 report

1. Zoom +/- with button works fine. Thank you.
2. Stable application is okey.
3. How does auto-rotate function work?
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 21, 2018, 15:49:49
@H Ifang
thank you for your ideas regarding UI/UX, you might be right with the less buttons on the screen, we will definitely try to think more about usability in the next versions.

@Peter Jurík
Hello, thank you very much for your quick report on new version. I am glad that it (hopefully) works smoothly and that watch buttons work fine.

Regarding auto-rotate function. It is mainly intended for use with navigation but can be used even without it. This function should rotate the map according to you "movement bearing". There is a small time lag between your actual bearing and displayed map rotation but it should be more or less similar. This function is effectively useless and might be a bit confusing when you just test it at home or just standing at one spot, because it needs some movement to lock your bearing or have the navigation enabled to at least use your expected route bearing/heading as your current bearing.
Title: Re: Wear for Locus Map beta testing
Post by: Wolli on March 21, 2018, 18:14:02
With today's UPDATE of wear for locus map [/ b] to 1.1.0 and locus map pro 3.30.2, my Sony Smartwatch 3 is not working anymore.
Error message on the smartwatch: "locus map has ended"
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 21, 2018, 19:20:07
@Wolli
Hello, I am very sory to hear that. I can't see any report about the error in our console yet. Please make sure your phone is connected to wifi or cellular data and try again and I should hopefully receive an error report which could help me fix it.
Other than that I have one report that Sony Smartwatch 3 is working with new version. So maybe you could try uninstall both device and watch part of the add-on and try to install it again if it helps. Sorry for the inconvenience.
Milan
Title: Re: Wear for Locus Map beta testing
Post by: Wolli on March 21, 2018, 20:45:53
Hello Milan
my mobil phone /samsung Galaxy S4, Android 5.01) is connectet with wlan.
I have deinstalled the android wear and the  wear for locus map. Then I installed android wear software and my Sony smartwatch 3 works well.
After this I installed the wear for locus maps software
On my phone locus maps works well.
When  I press on the watch the locus map icon, following message dispays:
"Locus Map wurde beendet" OK 
So the reinstalling of the softwares dos not help. What can I do now ?
Title: Re: Wear for Locus Map beta testing
Post by: Wolli on March 21, 2018, 20:56:25
Hello Milan
when i have not start the locus maps pro software on my phone I get on my sony smartwatch (buildNo M1D64T) the same message .  It seems that the locus map software dosen't send data to the watch
Title: Re: Wear for Locus Map beta testing
Post by: skwal on March 22, 2018, 00:17:52
With today's UPDATE of wear for locus map [/ b] to 1.1.0 and locus map pro 3.30.2, my Sony Smartwatch 3 is not working anymore.
Error message on the smartwatch: "locus map has ended"

same problem here
newest maps pro
sony sw3

at the very first start it worked. the watch made a reboot then no connection
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 22, 2018, 06:52:19
@Wolli @skwal
Ok, thank you for the report. So reinstall didn't help and there is a message that Locus Map has ended right after you start the application on the watch, right? Any similar message on the phone when you try to start the watch app - that Locus Map or Wear for Locus Map has ended?
Thanks
Title: Re: Wear for Locus Map beta testing
Post by: Wolli on March 22, 2018, 07:56:27
Hallo
ja, es gibt keine Nachricht  auf der Smartwatch wenn ich locus map pro starte .
Bei der Initialisierung von Lucus map werden im Initiallisierungsfenster alle
Andere Apps, z.B. outdooractive funktionieren auf der Smartwatch sehr gut.
Kann ich die beiden Vorgängerversionen (lucus map pro und wear für locus map)  herunter laden um zu testen ob es wirklich am Update liegt ?
Hier habe ich ein Video abgelegt:  http://wollisgeocaching.de/20180322074901.avi

Hello
yes, there is no message on the smartwatch when I start locus map pro.
When Lucus map is initialized, all of them are initialized in the initialization window
Other apps, e.g. outdooractive work very well on the watch.
Can I download the two previous versions (lucus map pro and wear for locus map) to test whether it is really on the update?
Here I have a video filed: http://wollisgeocaching.de/20180322074901.avi
Title: Re: Wear for Locus Map beta testing
Post by: skwal on March 22, 2018, 08:16:01

reinstall don´t help

i made i test
the watch isn´t connectet to the phone
when i start the wear app i get directky the locus has ended message on the watch.
so the problem is the wear app
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 22, 2018, 08:32:21
@Wolli
Danke für die Beschreibung des Problems und für das Video. Est ist nicht mehr nötig die Vorgängerversionen zu testen, weil Ich den Fehler in der neuen Version von Wear for Locus Map jetzt gefunden habe.
Ich werde den Fehler heute beheben, vielen Dank für die Hilfe!

@skwal
Bug found in the new version on Android Wear 1.x, working to fix this right now.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 22, 2018, 09:44:48
@Wolli @skwal
Really thanks for the help guys. The fix version 1.1.1 which should fix your problem is out now and should be available within a couple of hours on Google Play.
Please let me know if there are any other problems with this version or if it solved your problem.
Have a nice day
Title: Re: Wear for Locus Map beta testing
Post by: Wolli on March 22, 2018, 10:10:37
Hello Milan

Thanks for the very fast help. With the update locus map works again on my smartwatch.
Locus Map is a great software and the support is exceptionally good and very fast
Title: Re: Wear for Locus Map beta testing
Post by: skwal on March 22, 2018, 12:49:47
thanks, is working again.

one question, i don´t know how it was in the past

when im looking at the watch map and standing still i see a blue circle and a red cross
when im moving, i see a blue triangle and the red cross.


in locus i only see the blue circle and triangle.
is it possible to deactivate the red cross ?


edit: don´t know if you worked on it, cinema mode still not working
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 22, 2018, 14:00:20
@skwal
oh, sorry about the red cross, that should not be there when auto-centered. Should be fixed in about 2 weeks when new Locus Map version comes out.

The cinema mode is problematic, I can't reproduce the bug at all, might be specific for Sony SW3. I suspect it is again more of an Android Wear 1.x problem, but when tested on my old Moto 360 the cinema mode is working as expected - the screen just stays off until I press the power button again.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on March 26, 2018, 23:32:49
@skwal
oh, sorry about the red cross, that should not be there when auto-centered. Should be fixed in about 2 weeks when new Locus Map version comes out..

No Problem. But you did not say that is now possible to move the red cross over the map on the watch....  :)
made a 5hour test ride today, map always turns in the right direction


Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on March 27, 2018, 09:32:26
@skwal
Super, thanks for the test :) Glad to hear that the auto-rotation is usable and working.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on April 20, 2018, 10:58:25
Since beginning of April (wanted to try for a bike ride, might have occurred earlier but did not try) my Locus on watch does not connect to Locus on phone.

The watch is definitely connected: in Bluetooth settings it shows "connected", the crossed cloud-icon shows or not according to Internet connection on phone disabled or active, apps can be installed from watch's play store.

But when I start the Locus app on the watch, it shows up for a fraction of a second and then switches to message that watch and phone are not connected. I shall connect and try again. The refresh-button can be pressed as often as I want, does not change anything.

Locus main app had some updates since then, no difference.
Wear OS on the watch had an update meanwhile, no difference.
I uninstalled/reinstalled the app on the watch now, no difference.
I reinstalled the Wear for Locus on the phone too, no difference.

I wonder how to check if the phone part is "active"? Going into app details on the phone for "Wear for Locus", it shows no RAM usage, no battery usage. And the "force stop" button is not active, so does it run? If not, how to start - there is not even an icon for this "app" (more of a background service I guess - but how to check status of such ones - up and running? How about a little status widget?)

Thanks for reading.
Title: Re: Wear for Locus Map beta testing
Post by: Christian on April 20, 2018, 22:18:25
Hi guys,
I'm new to wearables but interested.Can someone please explain something to me?
: the clock must be connected to phone via bluetooth and uses the GPS of the phone? right?
: how many hours the battery of the phone (offlline mode, only GPS is on) and how many hours the battery of the clock will last? Any expierences here?
: is the clock able to "guidance" like on phone? is beeper supported?

Thank you. Any answer will be appreciated.
Christian
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on April 23, 2018, 08:42:46
@Christian
Hello, yes, currently with Wear for Locus Map the watch has to be connected to the phone to work and it uses the phone's GPS. But generally some other applications can also run without a phone possible with limited functionality synchronizing data later when the phone is available.
Expected battery life can vary greatly but basically the watch will be the issue not the phone. With "Screen always on" setting disabled on the watch Locus application will only connect and display data when the display is turned on. With this setting enabled the screen, although dimmed, will stay on and the application will stay connected which, depending on your watch, can drain the battery in a couple of hours. Generally Android Wear watch will probably not make it through more than 2-3 days without charging, even when they are just lying on the table with screen off. And even with light usage it is normal to charge AW watch every day.
Navigation directions are shown on the map screen, distance to point is drawn directly on the map. Beeper and/or vibration is not supported at the moment.
Title: Re: Wear for Locus Map beta testing
Post by: Christian on April 23, 2018, 15:28:20
Thank you Milan for your detailed answer helping a lot.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on May 04, 2018, 13:29:07
My problem (see 4 above) did not go away. After a phone reboot the Wear-for-Locus app/service now has an active "force stop" button in the app details, but that did not help either.

How can I debug this? Why does the Wear OS Locus app always say there is no connection?

(Wanted to use for a mountain hike, even as I guess an absolute altitude field is still missing?)

Update: I set back the watch to factory defaults and re-connected/installed everything. All other things looked identical before and after that, but finally Locus on the watch can be started again.

Had a short look into the code from github before, it was the "middle" connection error message, the one associated to the API not delivering any "node" with status "nearby" (just from what can be read there, do not know anything about it). As I said, any other locations told me "connected" (like the watch settings or the Wear OS app on the phone).
Somehow Wear OS seems not really stable..

Update2:
In the mountains, the map on the watch is very useful.
You can have a look at the track at any time, without getting/opening/unlocking the phone - also saving energy there probably (Bluetooth costs less than screen I guess).

Having the possibility to see the time on the map would be nice. So you do not always have to switch to the watch face for that (and then back). On the other hand, it is probably a good idea to not have the map open all the time - a Wear watch just does not have the endurance for a 8 hour activity.
And of course everything could be a bit smoother / faster / responsive - if it could.. Seems the hardware that is faster and needs less energy lies a few years in the future..

Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on June 05, 2018, 11:48:44
As for my problem with unwanted touch-events with sleeves and/or when sweating.. (also occurred in the mountains recently as soon as there was some rain and putting on a jacket) - there is one solution: display-lock (or to be precise touch-lock).

With the Bubble-app, you can have such a function (even if the app is quite huge / lots of functionality, nothing else of which I use): a long press on the main button locks display, another long press unlocks.
There is such an option in the Bubble config - and another option in advanced config to disable fallback to deactivate the lock by screen (not a good idea I think - but introduced because of the following problem: for a while the Google app, which is on that long-press by default, spoiled everything by putting a dialog in between to choose Google or Bubble - thus making it impossible to deactivate the lock again - but since Google app version 8.4 this is fixed).

Of course, it would be very nice, if Locus Wear app would support some button navigation then (I am sure any app can react to button events - if they exist - the Q Explorist has 3 buttons and the main button can be turned). Like:
- turning button to scroll between dashboard pages or zoom in/out in map view
- button 2 press to switch between map / dashboard
- button 3 to pause or stop/start (long press) in dashboard, jump to own location in map view

And of course I still hope to get some more dashboard values (if not configurable, then predefined) for different situations.

But I see there is not really much traffic here and you probably get the impression the Wear app is not really a very "hot" topic. And indeed: if not for Locus, I have not really a good use for the watch, that would justify the constant need to charge, be connected with phone and phone with mobile network. Thats only for people with lots of communication / notifications.. maybe not the biggest part of Locus users.
Anyways, thanks for maintaining the Wear app at least a bit.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on June 05, 2018, 15:49:34
@H Ifang Hello,
yes we have planned another update for the watch but there are some more important issues right now, so as you say, at least temporarily the wear development has lower priority but we still want to add some features to the wear add-on to make it truly helpful and usable.
I am glad the screen lock function helped you. It should be available by default in the top drop-down system menu, but personally I find it not very comfortable to use. But with wet display I guess there is no other choice then locking the touch.
As for HW button support it should already be implemented. The turning button should actually work exactly as you described. Other buttons function depends on your physical button configuration specific for your device type. Do turning button and other buttons do nothing for you?
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on June 06, 2018, 11:12:55
Oops - seems I not really tested that Sorry! (got the touch-lock usable just shortly before and no occasion for real use yet; yes I also found a lock-function in the standard system settings now, but indeed not very practical).

So yes, turning the button does scroll and zoom - nice. But the other buttons do the same (except some start/pause as it seems in dashboard). I would prefer one button to switch between map and dashboard. And another maybe toggle between current position (in map) and advance a bit in current direction or so - maybe to near the border of the map depending on current zoom level - just an idea. Given this, nearly all functions (except moving map freely) could be used completely touch-less, right?

In the system settings of Explorist, I only find the possibility to put apps to start on the additional buttons. So nothing configurable that could possibly have influence on button use in apps like Locus. The Wear OS itself does not use the buttons very well: turning the main button also scrolls through settings e.g., but nothing can be selected by button. So no button-only use possible there.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on June 07, 2018, 08:36:16
@H Ifang
Switching between screens or screen/menu on button click is a good idea. Moving the map forward on button click is a little bit more specific. Honestly ideal solution would be to make the buttons configurable, so that's probably something I would like to implement in the future.
Title: Re: Wear for Locus Map beta testing
Post by: skwal on June 14, 2018, 14:56:03
app on the phone  and the wear app is running.
i have finished the ride and close the phone app.

it say closed but it continues running  on the phone and gps drains the battery.

when i disconnect the watchbefore i close the app on the phone it is really closed.

possible to fix that?



the rest of the wear app still perfect. not one crash, use it 5 times a week. now with warmer temperature outside i get 10h displaying the map on my sony sw3
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on June 18, 2018, 12:47:47
@skwal Hello,
thanks for your feedback about usage and mainly battery life, 10 hours is an excellent result on SW3 I think.

I am not sure that I understand your problem with running app when you close Locus on the phone. Is Wear for Locus Map still running on the watch? Does Locus Map stop running eventually if you turn off Locus Map and then turn off Wear for Locus Map on the watch?
But I can confirm that if you turn off Locus Map on the phone while having Wear for Locus Map opened on the watch then Locus Map will just restart on the background because the watch still requests its services, that is the designed behavior.
Would you like maybe to have some dialog popup in the Locus Map saying that the watch is still connected and whether it should force kill the connection and then terminate Locus Map itself or something like that?
Title: Re: Wear for Locus Map beta testing
Post by: skwal on July 11, 2018, 13:48:29


Sorry for the later answer.

Quote
But I can confirm that if you turn off Locus Map on the phone while having Wear for Locus Map opened on the watch then Locus Map will just restart on the background because the watch still requests its services, that is the designed behavior.
that is what i was talking about. and i understand when locus on the phone restarts when it chrashed when it is connected to the watch
but its unpractical when you click the ok button on locus to confirm to close the app and forget the wtach and it just restarts and drain the phone battery.

Quote
Would you like maybe to have some dialog popup in the Locus Map saying that the watch is still connected and whether it should force kill the connection and then terminate Locus Map itself or something like that?
that sounds good
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 17, 2018, 11:14:15
Hello guys,
a new beta version 1.1.2 of Wear for Locus Map has just been released.

If someone here wishes to test it and is not yet registered as a beta tester you can opt-in to become one via this link. (https://play.google.com/apps/testing/com.asamm.locus.addon.wear)

The version fixes some problems with swiping/scrolling in the track recording dashboard and also adds:

- heart rate measurement (and online HRM synchronization with LM) during track recording
- configurable values/statistics in track recording dashboard
- custom waypoint naming when adding new waypoint

Any testing and feedback is very welcome :)

Have a nice day,
Milan
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 17, 2018, 14:44:28
Hello Guys,

i have install the new app wear for Locus. I activate the HRM to synchronize to Locus Map. I see the Heart Rate Sensor was active but on the Smartwatch the Data was not send and not visible. I have setup the Dashboard on Smartwatch and the Track Recording was without Heart Rate Measurement.

Best Regards
Danjel
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 17, 2018, 15:09:26
@Danjel Rojka
So HRM is not working? :/ Can you confirm that the service is running on the watch while track recording is active? (Permanent notification should be in your watch notification area saying that the HR is running due to track recording).
Do you use latest versions of Locus Map and Wear for Locus Map apps on the phone?
Could you try running some other heart rate measuring app at the same time to see that the HR is really recorded by the watch?
And by the way, what watch are you using?

Thanks,
Milan
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 17, 2018, 15:15:03
So HRM is not working? :/ Can you confirm that the service is running on the watch while track recording is active? YES

 (Permanent notification should be in your watch notification area saying that the HR is running due to track recording). YES

Do you use latest versions of Locus Map and Wear for Locus Map apps on the phone? Both is the latest Version. Locus Map 3.32.2 and Locus Wear Beta

Could you try running some other heart rate measuring app at the same time to see that the HR is really recorded by the watch? I have started the Polar App on the Watch and the Heart Rate was recorded and visible.

And by the way, what watch are you using? Polar M600 and the newest Wear OS
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on August 19, 2018, 17:40:32
OK, got the beta.
At first I always had bluetooth connection error messages. As not everyone has auto-updates active on the phone: it should be noted that next to the Locus app on the watch also the counterpart on the phone "Wear for Locus" needs a (probably beta) update. And I also had to kill Locus app on the phone to get the new version active, at least only after that everything worked on the watch (Wear OS 1.5 / Home app 2.15).

I did not yet try in a real activity, but from what I can see sitting on the couch, all interesting data can now be configured to the dashboard, and the 4 pages should be enough for all one needs. The one page with only two and thus slightly bigger fonts should be helpful for running / being able to read it while running.

I am just (really) missing one thing: you still cannot switch between map and dashboard using a button, a third button (if existing) that is. Without this, the app cannot be used touch-less. The third button is currently used redundantly in both dashboard (switching pages can also be done with rotating the main button) and map (zooming can be done with rotating) - provided the main button is rotatable of course.
And even if you prefer a button press over turning for switching pages, one direction is enough to easily reach the 4 pages (of course that does not apply to the zoom).
Any chance this can get configurable? (so the one single option in new configuration dialog is no longer that lonely ;) - btw. I wont use this, the Q Explorist does not have its own HR, so I hope the dashboard element will show HR from the phone as long as this option is unused.

Thanks for the update.
If I find new aspects in real use I will check back.

[Edit: of course in dashboard there _is_ only one button to switch pages, the other one is used for pause/start/stop - no idea why I always get confused with this. But it could be used to switch to map as main button rotation can switch dashboard pages, that stays the point.
HR from phone (from belt connected to phone) was shown correctly.
Energy value stays zero all the time (probably on the phone too where I do not have it in the dashboard). At the beginning I always had an energy value in my .tcx tracks, but since quite some time this field is no longer set there, probably the same thing. Dont know how it was calculated when it still was. ]
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 22, 2018, 19:03:56
Hello, I tried again and there is a connection between the clock and the smartphone. I start LocusWear and the setting for heart rate monitoring is activated. I start the track recording on the clock and I don't see a pulse on the individual dashboards on the clock. I can't see anything on the activated dashboard on my mobile phone either. If I take these off I can see that the sensor is active.
After that I started the Polar Trackrecording and after a short moment I get values in the Polar app on the clock. But still no values in LocusWear.

I hope you can find the error. Can I help you figure out the problem?

Title: Re: Wear for Locus Map beta testing
Post by: fera on August 23, 2018, 08:52:34
Hello there!

I tried the new Beta with Locus Map 3.32.2 like Danjel did, and I can confirm that the heart rate monitoring does not work yet unfortunately. The devices are: Xiaomi Mi A1 + Misfit Vapor

What I can see is that the sensor flashes constantly, so it is controlled, if I turn the heart rate monitoring off on the settings page in Wear for Locus Maps then the sensor stops flashing.
I have the heart rate view on the watch on the tracking screen and the value is on constant 0 BPM.

I do not have the Pro version of Locus Map yet.

I would be glad to be able to help, just tell me what report do you need.  :)
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 24, 2018, 13:27:07
Hello guys,
new beta is out. Thank you for all the feedback and testing you have done so far.
I have tried to fix the HRM issues but could not find any reason why it should not work at least according to the documentation and it unfortunately works flawlessly on my Huawei Watch 2. HRM works kind of unpredictably on old Moto 360 but then other apps seem to have trouble too so maybe it is some kind of device problem. Anyway I did some poking around the code, upgraded libraries etc. so please give it a one more try.

@fera @Danjel Rojka
Could you please try it once more with new beta? If things still don't work then please try to uninstall the Wear for Locus Map app, restarting the watch and then reinstalling the app. If it still does not work, could you please enable debug mode and check out HRM debug values? To enabled tap 6 times to the watch on the top of menu drawer (message shoud appear). Then you can choose new HRM(debug only) value in the dashboard (see the included printscreens).
It prints out following information codes
(accuracy):HR:last update before (s) / Locus HR value:last update before (s)
For HR to work the accuracy must be in range 0-3, HR value must be 25 or more and updates should keep coming every 1 - 2 seconds (so third value should be 0 - 2 s). Only after that the Locus HR value can be synchronized.

(https://s22.postimg.cc/ke60wu1t9/image.png) (https://postimg.cc/image/ke60wu1t9/)

@H Ifang
Thanks for lots of feedback and tips. Forgetting to update the device part of the add-on is inconvenient. It is unfortunately a property of Android, that the two application are not allowed to communicate when they have different versions. I will try to look into it if I could detect it somehow before attempting to communicate with the add-on itself.
Switching screens by a button is a good idea. I have implemented and tested this feature in the new beta but it is hardcoded to the long press of third user button (ie. 4 button watch configuration) and I now see you have "only" two user buttons and rotary button. Sorry for that, I will probably map it to the 2nd button long press action for the next release.
Anyway user configuration would be the best solution but don't know if such relatively complicated thing could be done on the watch or if it would require phone configuration UI (mapping actions to buttons for each screen on small watch screen could be very confusing and exhausting :/ )
Also button auto-configuration algorithm cannot detect if your watch has rotary input button yet, so for now the rotary input is set the same for everyone and user button detection does not reflect this so this is why you see duplicate actions on your buttons and rotary input and why this is somewhat confusing.
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on August 24, 2018, 17:47:02
Putting the map/dashboard switch on a button long-press sounds perfect, just did not think about that possibility. Looking forward to get it on lower button (button 3 / second user button as it seems to be called).
Short press -> scroll through dashboard, long press -> go to map (and back).

Btw. which watches have 4+ buttons? I have never seen one with more than 3.

When I wrote about configurable I just had in mind a simple switch to decide about button 3 to switch dashboard pages or between map/dashboard. Of course, a fully flexible user configuration about every detail of (e.g. button-)handling is always best, and everyone who really wants/needs something will gladly go through a bit of configuration, be it on the watch or the phone. But also of course thats nothing with a high prio, and at least for me with 3 buttons (altogether) there currently seems to be no further need for such a thing, if the above noted switching will be implemented. It might be more interesting then for people with only one or two buttons to decide themselves what to do with them.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 25, 2018, 13:33:43
Hello, Milan,

I uninstalled and restarted the app on the Watch. I did not uninstall the app on my smartphone but on my watch. Then reinstalled. Still no pulse display with values.

Then I activated the debug mode as shown by you and activated the heart rate (debug) in the dashboard.

He shows me the following values as in the screenshot.

That's all I know.

Danjel
(https://s15.postimg.cc/n783bb2x3/heartrate.jpg) (https://postimg.cc/image/n783bb2x3/)
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 25, 2018, 16:26:30
Hello, Milan,

the screenshot does not always show the 3rd value with 4 but it is as you describe at 1 or 2 and also the first value is usually at 3.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 25, 2018, 17:03:19
Hello Danjel,
thank you for the data, this is very helpful. Basically your screenshot says
2 = medium sensor accuracy (3 is the highest)
64 = your BPM
4 = last sensor reading before 4 seconds
The last two numbers mean that the value of 64 BPM was accepted for synchronization with Locus before 4 seconds.
I will have yet to prepare another debug version, I was focusing on the wrong area - I thought that the sensor reading was the problem but the synchronization seems to actually be the problem. I honestly don't understand where the problem could be, I also use this with Locus Map 3.32.2.

One thing though. Do you by any chance have other HRM devies configured in Locus Map via Ant or BT manager?

Thank you again and have a nice weekend
Milan
Title: Re: Wear for Locus Map beta testing
Post by: fera on August 26, 2018, 12:13:29
Hi Milan!

I tried out the new build as well, the HRM was still not shown in the dashboard so I enabled the debug mode.
According to the values seen there, the value gets updated in every 3, sometimes 4 seconds and it looks like it is accepted by Locus for syncing.

I got to say, I still use the free version of Locus Map, could that be a problem? Or I should be able to see HRM value on the watch dashboard without it?

Here are my screenshots, looking for the next build!  ;)

Keep up the good work, this is awesome!


(https://s8.postimg.cc/eyivfbjnl/wear_debug1.png) (https://postimg.cc/image/eyivfbjnl/)

(https://s8.postimg.cc/rpx1lu15d/wear_debug2.png) (https://postimg.cc/image/rpx1lu15d/)


Edit: I unistalled the app both from the watch and the phone, then installed it on the phone, then got the notification "Get Locus map on your watch" on my watch, and installed it by that.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 27, 2018, 08:16:43
Hello, Milan,
 I have configured another sensor. This is the Mio link I connected via Bluetooth. But I also deactivated Bluetooth in Locus for connection with Mio when I started recording. With no other result. And Mio wasn't activated and connected either.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 27, 2018, 11:55:39
@fera @Danjel Rojka
Thank you for your reports guys.
One other thing, can you also confirm, that you had a GPS signal while testing HRM? Menion pointed out, that without GPS signal track recording does not work properly and HRM stays at zero until GPS signal is acquired. This is unfortunately a limitation of Locus Map.

Also I have discussed other paired BT/ANT HRM devices and they should have no affect until they start to send some measured data, so other paired devices should not cause this.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 27, 2018, 12:40:05
Hello Milan,

On Saturday I tested the function outside and I had good GPS reception. I had the same issue.

Regards
Danjel
Title: Re: Wear for Locus Map beta testing
Post by: fera on August 28, 2018, 07:18:52
Hi Milan!

I checked as well, I had a strong GPS lock-on (green satellite icon), the issue is the same.

Could you confirm this question:
I got to say, I still use the free version of Locus Map, could that be a problem? Or I should be able to see HRM value on the watch dashboard without it?

Thanks  :)
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 28, 2018, 08:37:52
@fera @Danjel Rojka
Ok, thanks for confirmation, it is a mystery then :)
Last versions of both LM Pro and Free should be fine. We will work on the next update together with Menion to get some more logs out of LM to try to find the cause now that we know that watch sensor input is most probably not the issue.
Thank you for testing and patience, I will definitely let you know when the next version is out.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 29, 2018, 16:06:42
Hello,
another beta version 1.1.4 is out and we are still continuing our attempts to debug HRM feature.
This time is a bit more complex but it would really help us to find the problem since this time we are monitoring the data across wear&device addon and within Locus Map itself. So if you are willing to help please follow these steps:
1. Download and install this private Beta version of LM Free (https://drive.google.com/file/d/1Ff27RHvOojR4Us-9DkwMHTeQWUf0mfdQ/view?usp=sharing)
2. Update your Wear addon on both device and watch.
3. Make sure the Locus Map Pro is turned off completely (not running in the background) and then run LM Free beta version.
4. Again enable debug mode on the watch and start the track recording. Checkout HRM debug output - there is now a sixth (i.e. the last)value which indicates how many seconds have elapsed since the HR data was last sent to the phone. This last number should always be less than 6 seconds.
5. Make sure you have GPS fix and just let the track recording work while having the watch on your wrist for at least a minute or two. (Formally it is enough to wait just until the first debug value(accuracy) reaches 0 or more and the last value is less than 6 (seconds after last data sync) which should all happen within 5 to 15 seconds after recording start)
6. After your track recording is done and when you have the time, copy (and zip ideally) all the logs in folder \Locus\logs directly in your phone internal storage or SD card and send them to me via email at milan.cejnar@asamm.com or upload them to any cloud/storage you might be accustomed to use and share the link with me.

Any help is greatly appreciated and I hope this one will help us find the bug because there is probably not more logging that Menion and I could do :)

P.S.
@H Ifang
I am not sure if there are any 4 button Wear OS watch actually, but this configuration is formally supported by the OS so we support it as well. Anyway the screen switch should now be mapped to the 3rd button long press, please try if it works as expected.
Title: Re: Wear for Locus Map beta testing
Post by: fera on August 29, 2018, 20:51:30
Hi Milan!

I just recorded a track with the private build of LM Free like you asked in your latest post, see the attached zip file in the email I sent you.

What I find a bit strange is that only one txt was generated (by one recording) is this enough?

Also I checked the sixth data field in HRM debug stat, and it was always under 6, around 2 or 3, so I guess syncing works properly.

Thanks guys, looking forward to the root cause of this bug  :)
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on August 30, 2018, 01:50:33
As for button switch map/dashboard by button3-long-press: works!
Just two details that could be improved:
1. whenever you switch back to dashboard it starts with first page again, page where you left is not remembered (that is the same if switching is done using touchscreen)
2. following the switch after a long-press there always is a button3 short/normal press recognized, too - that means going to dashboard you always go to page 2 at the moment (and if last page would be remembered it would spoil that), or everytime going to map an unintended zoom-out follows. Should be possible to suppress that short-button-event.

But thanks again until here, it gets better and better.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 30, 2018, 10:08:19
@fera
Thank you very much for your log reports I think I have finally found the bug. I was sending the HRM data between phone add-on part and LM in an incorrect way which in some Android 8.0+ devices might result in the data being lost quietly within the Android OS never arriving to the LM.
Quite a dumb but hard to spot mistake to be honest so thank you guys a lot for testing and bearing with me :) Next update should hopefully solve the issue, I will let you know when it is out.

@H Ifang
Ok, thanks for the report. I will look into it, short button press should not be called after the long press. I haven't noticed the issue but I will try to simulate.
Track recording dashboard page should probably be remembered. Good point a bit tricky though because the watch app has no notion of track recording session but I think some reasonable implementation could be done.
Title: Re: Wear for Locus Map beta testing
Post by: fera on August 30, 2018, 14:20:14
I'm glad I could help!

Also I got to ask, since you were discussing button behaviour, is it possible to use the only button on my watch for anything in Locus Wear, or that is completely owned by the OS?  ::)

Now with a short press I get to the watchface/main screen, with a long press to the voice assistant.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 30, 2018, 14:53:50
@fera
well in theory I think it is possible to override that button but I think I have read in the documentation that you are just not supposed to even try that at anytime and under any circumstances.
I mean if an application got stuck, swipe-to-dismiss gesture would malfunction and the power button was overridden then you would have to probably wait until your watch shuts down by insufficient battery to be able to restart the watch.
So no unfortunately, this is something that will certainly not appear in our code.

P.S. That said the whole Wear add-on is currently open-sourced so practically anybody can hack whatever they want and run it on their watch :)
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on August 31, 2018, 10:45:56
Hello Milan, I didn't find the time to install the beta. Should I do this after the fact?
Or is the problem fixed?

regards
Danjel
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on August 31, 2018, 14:06:16
Hello guys,
the new and hopefully final beta version 1.1.5 of the add-on is out. HRM should be finally fixed. You can uninstall the LM Free beta version it should now work even with production LM Pro version 3.32.2.
This is also a release candidate version of the add-on so if no more serious bugs are discovered, this version will go public in the next week (after rebuilding with new translations and disabled debugging to save battery.)

And again let me thank you all for your help and suggestions!

@fera @Danjel Rojka
Please test HRM normally, no debugging hopefully needed this time :)

@H Ifang
I have implemented version mismatch detection between phone and watch part of the add-on as per your suggestion.
I have also tried to fix that fake short press detection during screen switch.
Dashboard screen position still not remembered, but marked to be implemented in the following version after this release (don't really have more time/budget to implement more features to this release, sorry :/ )
Title: Re: Wear for Locus Map beta testing
Post by: gumka on September 02, 2018, 16:06:16
Hello to everybody as this is my first post on this forum.

I'm Locus Map Pro user for long time. Recently I've bought smartwatch Ticwatch Pro and install Wear for Locus. However I can't get GPS position from GPS build in watch. Position is working only when I hold phone with GPS on, but that makes not much sense for having smartwatch;) I couldn't see also "Location" in Wear for Locus permissions, there are only "Sensors".
Is it possible to get position on smartwatch from build in GPS? If yes please guide me.
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 03, 2018, 10:24:12
Hi Milan!

Unfortunately I haven't had the time to thoroughly test the latest build, but I gave it a couple minutes already, and it looks good.

What is a bit strange for me is that the BPM value sometimes drops to zero on the watch dashboard before the next measurement and therefore the HRM value in LM on my phone drops to zero as well.

Is there maybe a way to indicate always the latest not zero readout value? Or should I use average? :)

P.S.: I will test it in greater depth today or tomorrow. ;)
Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on September 04, 2018, 02:36:31
Nice to hear there would be another fix ready, however I currently dont get it on the watch.

No problem with Locus probably, just Wear OS (again) got into some strange state. I put on WiFi and Bluetooth on the phone, Bluetooth on the watch, but it shows on the watch that it is not connected in Bluetooth settings, and crossed cloud symbol. Turning off/on Bluetooth did not help on both sides, even re-connecting. Wear App on the phone shows connection, it can do a screenshot or error report, so somehow the connection is there. But no connection in play store to get updates.
If someone has an idea what I could try else.. I currently dont plan to again completely reset the watch and start everything from scratch. That Wear OS really is still not very mature..
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 06, 2018, 09:13:29
Hi Milan!

I have spent more time with the beta, and got to say, it is working stable, however the problem which I mentioned in my previous post still persists:

"What is a bit strange for me is that the BPM value sometimes drops to zero on the watch dashboard before the next measurement and therefore the HRM value in LM on my phone drops to zero as well.
Is there maybe a way to indicate always the latest not zero readout value? Or should I use average? :)"
I guess this happens maybe because the LM Pro requests the HR more frequently than the add-on can provide? Could this be somehow fixed?

Thanks again! :)
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 06, 2018, 09:23:10
I can report that Wear Locus works without problems.
The heart rate was reproduced by Wear Locus without any problems. And I was able to finish my run successfully with the lap announcement and the heart rate message every 3min.
At the same time I started the Polar App on the Smartwatch and started the recording there. Both ran parallel and had no problems.

ˊ ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'F'¯'''''L ` ` ` ` ` ` ` ` ` ` ` `
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'[``…'¾`` ``` ``` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'[```…ʹ[` ` ` ` ``` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `#````ˆ[```` ``` ``` ``` ``
` ` ` ` ` ` ` ` ` ` ` ` ` ` `'#``…``'[`… ` ` ` ` ` ` ` ` `
` ` ` ` ` ` ` ` ` ` ` ` ` ` #…`````'F`` ` ` ` `` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ƒ¯```````'[__` ` ` ` ` ` ` ``` ``
` ` ` ` ` ` ` ` ` ` ` ` ƒ¯````````ʹ¯¯¯¯''''''''''''¯¯¯¯¯¯™[ `
gµµµµµµµµµµµµµµ_µ™`````````````````````````'# `
'₫₫₫₫₫₫₫₫₫₫₫₫₫F¯…`````````````````````` ` ²q[¯ ` `
ʹ₫₫₫₫₫₫₫₫₫₫₫₫¾````````````````````````````ʹ} … `
›₫₫₫₫₫₫₫₫₫₫₫₫#`````````````````````````__µr… ` `
³₫₫₫₫₫₫₫₫₫₫₫₫₫…`````````````````````````¯[ … ` `
`₫₫₫₫₫₫₫₫₫₫₫₫$``````````````````````````_F … ` `
`]₫₫₫₫₫₫₫₫₫₫₫#````````````````````````ʹ''''[… … ` `
`'₫₫₫₫₫₫₫F''''']₫#___`````````````````````` '# … ` `
…₫₫₫₫₫₫₫bµ₫₫₫₫$¯''''¹uuuuuɷuɷuɷuɷuɷuɷµ#¯ ` ` ` ` `
…'''''''™''''™'''™''''™™ … … ` ` ` ` ` ` ` ` ` ` ` ` … … ` ` `
` … ` ` ` ` ` ` ` ` … ` … ` ` ` ` ` ` ` ` ` ` ` … ` ` ` ` `.
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 06, 2018, 09:38:22
@Danjel:

Does the heart rate sometimes drops to zero on your side as well if you're using a dashboard?  :-\
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 06, 2018, 09:57:32
I couldn't tell because I wasn't looking at the dashboard all the time. I'll check it on the next run to see if it happens.

You mean the dashboard on the Smartwatch or on the smartphone?
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 06, 2018, 10:03:08
Actually, I mean both, I have encountered this behavior on both devices.
Are you aware of a setting to only show the latest nonzero value of sensor data?

I couldn't tell because I wasn't looking at the dashboard all the time. I'll check it on the next run to see if it happens.

You mean the dashboard on the Smartwatch or on the smartphone?
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 06, 2018, 10:05:37
No, I don't know.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on September 06, 2018, 10:39:07
Hello guys,
sorry I was off for a few days ...

@gumka
Hello and welcome to the forum. This topic is intended mainly for beta testers so if you continue using the Wear add-on you are very welcome to also test and post feedback on recent add-on beta version and propose new tips on how to improve the app.
Currently the add-on does not have the option to use watch GPS and is built more like a companion to the Locus Map running on the phone which uses its own GPS. The stand-alone add-on operation would be possible but that brings a whole lot of other problems to solve and logic to implement and it is not planned in the near future.

@H Ifang
I completely agree, Wear OS is much better than original Android Wear 1.x but there are still various bugs and quirks in the platform itself and with each watch possibly behaving slightly different than the other.
For these kind of connectivity problems try to clear data and cache for Google, Google Play Services, Wear OS app on the phone and maybe clear data of Google Play app on the watch. Hope it will start working soon without a need for factory reset.

@fera @Danjel
Thank you guys for testing, I am glad it is somehow better. I will release the application in this state to see how many people are affected by this problem. It could be also a problem with sensor accuracy but the more likely cause as have been suggested is that the watch is not fast enough in providing the data for Locus Map for some unknown reason.
I will try to improve this behavior in next version since I need to redo some communication logic anyway thanks to ever changing Google APIs...
You can also plot a HRM graph(y axis) in time or distance(x axis) in Locus Map in track details and post it here or send it to me via email so I could see how often these drops occur and how serious they are.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 06, 2018, 13:05:53
Hello Milan,

the interruption of the cardiac frequency has only one interruption in an hour.
At 54min 26sec to 54min 46sec

Otherwise, I have a continuous transmission.

Best Regards
Danjel Rojka
Title: Re: Wear for Locus Map beta testing
Post by: gumka on September 06, 2018, 20:20:08
@Milan

I forgot to mention that I was using beta version. Anyway thank you for clarifying regarding build in GPS. Just have to continue using Locus on mobile. Thanks
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 08, 2018, 11:30:23
Hi Milan!

Did I see correctly, there is another new build? :)
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on September 09, 2018, 09:20:24
@fera
Hi, yeah you are right but there is nothing new in it really at least not for you guys, it is just previous beta version with disabled debug mode and with some new translations added. I have released it to all the users so it is not beta anymore.

I will be rewriting some connection logic for the next release (though there will be probably no activity for a couple of weeks now after this release). I will also try to decrease latency of HRM synchronization in order to avoid those 0 BPM readings in between samples.

Anyway thank you guys for testing I really appreciate it and it has helped a lot. If you stumble across any problems in the latest stable version please let me know but it should work the same as the last version.
And I will definitely give you a heads-up the next time there is a new beta so we could improve the add-on even more.

Have a nice weekend
Milan
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 10, 2018, 11:56:42
Hi Milan!

Here is a distance/HRM graph of my latest cycle-ride:

(https://s22.postimg.cc/uu82wlr3x/Screenshot_20180910-083702_1.png) (https://postimg.cc/image/uu82wlr3x/)

As you can see, the 0 BPM drops are pretty frequent. I can provide you with a time/HRM graph as well.

If you cannot increase the synchronisation frequency between the add-on and the LM, what if you altered something in the code to show the latest nonzero value until the next valid sensor readout?

But it's just an idea  8)

But anyway, thanks for everything, you are the best!
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on September 10, 2018, 12:44:47
@fera
Hello,
wow, your measurement is pretty bad, I am sorry. I wonder why that is :/ Locus Map will have some increased tolerance (10 seconds delay) but we won't increase it any more because it would only cover up this buggy behavior and you would still be missing the real data.
I will try to switch to newer communication API and use more light-weight messages for HRM synchronization with hopefully lower overall latency in the next version, maybe it will help.
By the way do you have any battery optimizations enabled on your phone? If so, could you try to disable them for Locus Map, Wear for Locus Map and Wear OS apps and see if that helps or if it is the same?
Thanks!
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 11, 2018, 09:17:00
Hello, Milan,

today I could test the pulse measurement again in bicycle mode. I rode my bike for about 50min and only had a drop-out of 10 seconds. Otherwise the transmission worked perfectly.

Best Regards
Danjel Rojka
(https://s15.postimg.cc/wldpgqap3/Screenshot_20180911-091220.png) (https://postimg.cc/image/wldpgqap3/)
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 11, 2018, 09:58:59
Hello Milan!

I checked what you asked yesterday, and it turned out that all locus apps were battery optimised, so I switched everything that is locus-related to "not optimized" as well as the wear os itself and here is today's measurement:

(https://s22.postimg.cc/exetgh959/Screenshot_20180911-093012.png) (https://postimg.cc/image/exetgh959/)

As you can see, in the beginning it was stable and continous then just got stochastic completely. Is there maybe a log.txt I can provide you?

What am I doing wrong? LM Pro and Wear app is the latest one on Android 8.1 on Xiaomi Mi A1 with Misfit Vapor. Thanks :)
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 11, 2018, 10:40:03
@Milan
Continuing the message in the help topic (http://help.locusmap.eu/topic/using-heart-rate-sensor-of-the-smartwatch) about HR on Ticwatch E and Redmi Note 4x:

Bit more details
Ticwatch E: Wear version 2.8.2.183948193, rights given all except Storage (noticed just now)
Locus Map version 1.1.6

Redmi Note 4x: System MIUI 9 (9.3.22), Wear OS 2.15.0.207193535
Locus Map version 3.32.2, HR addon v. 1.0.7

Bit more for troubleshooting the HR reading:
On its own, Locus was running on the watch but the HR sensor was not, unless the app was on the screen in foreground and about 1 min after it went in background (the watch face dimmed). Locus was running without problems, simply tapping the watch to bring it in foreground again was enough to get again several HR readings. But as soon as the watch dimmed, the HR ran only for a few moments more.
While in background, Locus was only reading HR already provided by SGT, not initialising the reading. From the recording, the exact moment when I started SGT is very clear.


(https://s33.postimg.cc/p0npy24a3/image.png) (https://postimg.cc/image/p0npy24a3/)

The first hour was Locus only, the second with SGT and the third (roughly) when the connection dropped and Locus recorded from the phone only.

---
The connection problem seems to be constant and somewhat puzzling, wear os is saying "connected" but I have noticed that no app can use the BT connection, so it is not only Locus. All apps where they connect are connecting through WIFI.
The only thing I would like to change on Locus side is to break the HR reading if no connection is detected, so that the reset is not necessary.

I'll have to reset the watch and to delete the connection on phone again to hopefully bring the BT connection back.

Majka


Title: Re: Wear for Locus Map beta testing
Post by: H Ifang on September 11, 2018, 13:19:00
I was not able to reestablish connectivity by clearing data and cache of various apps / services as you suggested. While before that action Locus itself still worked with the old version, now it also has no more connection to the phone-counterpart.
The phone Wear OS app (of course, after deleting its data) does not know the watch any longer and it cannot be re-registered there too. So only possibility would be to do the watch reset / reinstallation as it seems.

I guess I will wait for next-gen now for that, sell the old one. As it happens snapdragon 3100 was presented today.
Lets see how fast new models are available, and for what prices..
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 11, 2018, 15:25:03
Am I the only one where it works reasonably well?

Best Regards
Danjel
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 12, 2018, 12:01:25
It is very highly possible, Danjel, I'm afraid so  :-\

But good for you :)

What OS are you using on what devices?

Am I the only one where it works reasonably well?

Best Regards
Danjel
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 12, 2018, 13:34:57
I use Nokia 7 Plus with Android 8.1 as Pure Android or Android One.

As Smartwatch I use the Polar M600 with current WearOS version. I can find out the exact version this evening.
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 12, 2018, 14:08:02
So we use the same wear version and Android One version (8.1), only difference is that you use it on a Nokia 7 and me on a Xiaomi Mi A1.

Puzzling... Maybe the watch hardware?
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 12, 2018, 14:18:58
Am I the only one where it works reasonably well?

I would expect people posting when they have problems, not when everything works as expected... Myself, I wouldn't be here except a short thank you, if there was nothing to troubleshoot.

To be clear, I am not complaining about Locus. The connection problems I have are Wear problems, it has nothing to do with Locus alone. It might be a combination of Wear and MIUI, I'll try to update to latest MIUI and / or LineageOS.

And I could live with the problem I had with HR on Wear (reading HR only when in foreground, but could be avoided if another app was initialising the readings). For me, using 3rd party app as workaround would be fine. I was getting everything I needed in Locus this way in real time and everything was in the track recorded.

But if something is not working exactly as expected, IMHO, best is to give very detailed feedback. The developer can ignore it when they want but nobody can expect them to test any combination of hardware and software.
And any workaround could help others with the same problem.

Majka
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 12, 2018, 16:24:43
I am always happy when I get positive feedback. This can narrow errors and exclude certain constellations.

Yesterday I had the problem that the connection or recording was not continuous. Presumably, this is due to the low battery level on the smartwatch.

But I have to verify that again.

I'll let you know.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on September 13, 2018, 16:19:51
Hello,
@H Ifang I see you too have a lot of "fun" with Wear OS platform :) I myself cannot copy my accounts to  Google Play on the watch so Google Play is not working for me at all. Clearing accounts & clearing caches on the phone & watch factory reset didn't help :( @Marie here also has some general Wear OS connectivity issues if I understand correctly. I really don't understand what is Google doing with the platform but it is not so great so far :/

@Marie
Thanks for a lot of info and nice graph to show what is going on. It seems you actually have 2 separate problems. The first one is a problem that fera and a also sometimes Danjel have which is that a lot of data is missing from the recording so the HRM is dropping to zero way too often. That is something I will try to fix.
The second problem seems to be that your watch is probably killing of the foreground HRM service when you exit the app. That is something I will check but honestly don't think I will be able to fix. The OS should not be killing off foreground services under normal circumstances and I am not sure why your watch is so mean to do that to the Locus app.
Definitely thanks for the feedback though and I will be glad if you help with beta testing later because your watch seems exceptionally buggy with our app :/

@Danjel @fera
Well the app and HRM is working for me as well, which is very unfortunate for a developer :) Though I can confirm that those drops to 0 BPM seem to be an issue with the app which I will be working on to fix it later. I will try to use more light-weight communication API from watch to the phone to send HRM

@fera
I am a bit surprised that the rest of the APP is working normally though without a lot of "connection lost" error screens in your case if HRM seems to be so unstable, really a mystery :/ Really weird that various phone/watch combinations behave so differently and definitely not helping with the debugging...

Anyway thank you for all the feedback I need to work on something else for a couple of weeks but I have been talking with Menion and fixing these Wear OS HRM issues is quite a high priority for us so I am hoping to return to working on Wear OS very soon and start releasing some experimental Beta versions with a bit different communications handling. Sorry for all the trouble in the meantime and I hope the rest of the add-on is working correctly for you.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 14, 2018, 09:19:29
I use Nokia 7 Plus with Android 8.1 as Pure Android or Android One.

As Smartwatch I use the Polar M600 with current WearOS version. I can find out the exact version this evening.

On Polar M600 is Wear OS 1.5
HomeApp 2.15
Android 8.0
Security Patche  from 5.August 2018

On the Smartwatch the power saving function is deactivated.
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 17, 2018, 21:59:56
... @Marie here also has some general Wear OS connectivity issues if I understand correctly. I really don't understand what is Google doing with the platform but it is not so great so far :/

@Marie
Thanks for a lot of info and nice graph to show what is going on. It seems you actually have 2 separate problems. The first one is a problem that fera and a also sometimes Danjel have which is that a lot of data is missing from the recording so the HRM is dropping to zero way too often. That is something I will try to fix.
The second problem seems to be that your watch is probably killing of the foreground HRM service when you exit the app. That is something I will check but honestly don't think I will be able to fix. The OS should not be killing off foreground services under normal circumstances and I am not sure why your watch is so mean to do that to the Locus app.
...

In the meantime, I did some changes on my phone and updated everything I could (system, google play services, Wear OS to latest version). The Wear OS (connection) problems might be solved - I need to check over a longer time then the single bug-free day I had.

The problem was there on MIUI9, and was slightly better on fresh install of MIUI10 (8.9.6, last weekly version from miui.cz) without any changes from standard settings. It still didn't work well enough and I got BT-disconnects quite often.

To troubleshoot the bluetooth connection, there are some changes needed in the system: both Locus and Wear OS need to have "power saving" disabled, additionally both need to be "locked in memory" and both run slightly better if "wakelock" is manually enabled in permissions (including allowing wakelock initialised from 3rd party apps). I suspect this would be true for all apps which have to run even in part in the background - for example the HR zones plugin. This seems to stabilize the Bluetooth connection so that no "lost connection" comes up. It did clear the problem when the watch couldn't be paired at all as well, no more "Airplane mode" on/off or resetting the phone and hoping for best to get it working since I set it up this way. It isn't enough to disable the power saving features, for some reason it needs the additional changes as well.

This might (but only might) be a solution even for MIUI9, but the settings (and switches) needed are hidden deeper im System and some might be inpossible to set without rooting. No idea, I won't be going back to this version.

With these settings, Locus is running stable on both phone and watch, the connection is solid and the recording can be initialised from phone or from watch, and closed from phone or watch as well.

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.

(https://i.postimg.cc/Z0HtfRzY/Screenshot_2018-09-17-21-15-12-558_menion.android.locus.pro.png) (https://postimg.cc/Z0HtfRzY)

I am ready to test any beta version for possible solution. But for me, this is working fine just as it is.
It just seems that Locus on Wear, at least on my watch, would need to push harder to get HR reading, it can at the moment only read the heartrate if it is already provided by something else. Just to be clear,  it does have the needed premission - this shows inside of the app on watch as well as in application info in system. I did look at permission of SGT - this has additionally "storage" and "GPS" permission on the watch.

Majka
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on September 18, 2018, 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
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 18, 2018, 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
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 18, 2018, 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!
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 18, 2018, 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.
Title: Re: Wear for Locus Map beta testing
Post by: fera on September 19, 2018, 14:53:59
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:

(https://i.postimg.cc/2VvhPzv3/Screenshot_20180918-185730.png) (https://postimg.cc/2VvhPzv3)

Oh and yes, the zero values on the plot were present until I started SGT.
Title: Re: Wear for Locus Map beta testing
Post by: Marie Zemanova on September 20, 2018, 12:17:11
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.
Title: Re: Wear for Locus Map beta testing
Post by: Danjel Rojka on September 21, 2018, 17:02:03
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.
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on October 12, 2018, 22:32:39
@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!
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on October 18, 2018, 15:14:50
Hi everybody! :)
Can (or could be) "Wear for Locus" be installed on a secondary standard Android "slave" machine, instead on an "wearable" one?
Title: Re: Wear for Locus Map beta testing
Post by: milan.cejnar on October 18, 2018, 16:04:05
@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?
Title: Re: Wear for Locus Map beta testing
Post by: sbouju on October 18, 2018, 16:26:01
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.