Messages

@lor74cas
Hello, I wrote you an email through help desk 2 weeks ago (I hope it got through to you?). But it might be a good idea to share it here for others as well.
I tried once more after your report and finally hopefully found the cause of the problem. It should be fixed in the current version of LM Pro and the LT service should wake up correctly after connectivity state change.

Regarding unlimited session timeout usability problems we will probably limit upper bound to some more sensible limit like 1 or 2 weeks, at least until more mature group management is in place.

And by the way, web is still not fixed the way we would like to. We unfortunately have to find somebody else to fix it, since our current contractor is apparently not up for the task.

@Andrew Heard
Hello and thank you for letting me know. So I have just double checked and your data are no longer in the DB but are still available through our web API. That means one of our caching layers have failed to evict the data after the internal timeout for some unknown reason. The fix is not trivial and I will not be able to fix this right away (I will create bug report though). That means, that unlimited session time option is buggy right now, in a way that old unwanted data from old devices or LM versions get stuck and the system was not designed to be able to remove them in any simple manner.
I am very sorry about this, we wanted to add the feature but did not think through all implications when using for long time in a single stable group.
In the meantime you could create a new group or set the group session timeout to some of the available limited values. Of course we still confirm with the GDPR regulations and I could delete your LT data if you requested but that would mean deleting all your groups and your internal LT profile as well, which would make the data inaccessible,  but that is probably not very helpful right now.

As for the locale, I must admit that there is something wrong there then. Our locales work ok and we expected that the front-end framework will handle locales correctly out of the box. I will have to report this to the company doing the front-end for us. Thank you.

@lor74cas
Hello, I did not want to bother you with the help desk unnecessarily. It is just that I kind of missed the problem previously and did not try to reproduce thoroughly which was my personal mistake. I am sorry about that. The help desk just helps me to organize problems better and resolve them separately, especially because there was a lot of confusion and various errors concerning the LT web.
Anyway I tried to replicate again while locking the phone during the connection loss and could finally reproduce with my Samsung phone. The fix should be out with the new app version in a few days.

@Andrew Heard
Hi, I have checked the backend database and I can see the problem regarding your two positions. One position was recorded by the Locus Map Free and the other one by the Locus Map Pro. They are technically two separate clients due to some implementation details even when running on the same phone and with the same account. Leaving the group LM Free should hide your old position. Alternatively I could delete both last recorded positions on the server if it bothers you.

Hello guys,
sorry for the delay and no news. We have problems with the company which should have made the fixes and update but they are communicating again and promised to fix couple of issues.

Please if you have any problem related to the core LT functionality which can be reproduced in Locus Map directly (ie. not just concerning the web page itself), report it as a bug on our help desk so that I could get more information like your LT group identification and your Locus account info and solve the problems one by one.

@Andrew Heard
As for seeing your position multiple times, are you really using the same Locus account and the same Android device? Has the device been factory reset or rooted in the meantime? Or was the subscription really the only thing that has changed? If that is the case I would like to know (by a private email or PM) the name of the group and your email address that is linked with your Locus account if possible, thank you.

@lor74cas
I could not reproduce the behaviour but I will have to look again if you could reproduce it consistently.
You are right that the expected behaviour of the LT should be to increase the error count when there is no connection during the expected position refresh. But at the moment the actual behaviour is to don't even try if there is no Internet connection so that is why the numbers do not increase at all and that is not necessarily a bug (depending on your expectation). Still the position should update as soon as you connect to the network regardless of the app state, that indeed seems like a bug if that happens.
Again if you could please create a problem in our help desk, linking this topic so that we could solve it separately as it does not seem to concern the new LT web page problems.

Thank you

@Andrew Heard Thank you for mentioning this, it is true that private groups can set the "time out" to longer time.
But @lor74cas is right, this seems like a bug and increasing the time limit will only mask the problem somehow. I will add to my live tracking issues to solve.

@lor74cas Might only be a bug on the web, will have to try with two phones. The live tracking not reporting any failed transmissions might not be a problem. If there is no connection available Locus will notice this and postpone the attempt until the connection is available. The same should apply with GPS I think, so there should be no attempts to send the position until GPS fix is available.
But I would expect that as soon as a GPS or a connection is available there should be an attempt to synchronize position immediately (if last scheduled attempt had already been missed). So this is definitely not intended behaviour.

Hello,
thank you for reporting this, it is definitely and unwanted behaviour. I will have to investigate how this could be fixed.
Best regards
Milan

Hello,
currently the Locus Map Watch add-on for Wear OS requires connection to the phone running Locus Map (all the data are evaluated and recorded there).

Supported values and statistics that can be shown by the add-on are:
- Track time & distance
- Speed - current, average, max
- Elevation uphill/downhill
- Distance uphill/downhill
- Altitude current, min, max
- Heart rate current, average, max
- Energy
- Cadence average, max
- Pace
- Watch battery & current time

Slope is currently not implemented, but could be added in the future. Heart rate has been reported as a bit buggy for some users if captured directly by the watch itself. External HR sensors like chest-strap should be fine.

Also as an another suggestion, you could possibly consider getting another second-hand or cheap Android phone just to use as a Bike Computer? We are currently working on ways to synchronize two or more instances of Locus Map running on multiple devices (will require Internet connection though), so that could make using LM on two phones more usable in the future.

@sbouju Hello,
we have had already some users with Android OS on their watch trying out the standard Locus Map and from what I could gather, the usability and user experience on the round display was pretty poor, even though the resolution was probably lower.
Improved usability on the Android OS devices with round displays would probably require not exactly trivial UI changes and it is not currently planned.

Hello guys,
thank you for all your feedback.
The issue with the connection is weird, but I am glad that reinstalling Locus Map has helped, even though I see how this can be very incovenient.
After that I am glad to hear that the connection is pretty stable. The next thing I will focus on is probably the map not updating fast enough after the display is shown, as I have also seen this couple of times.

[There are two main screens available:]

Hello,
this thread is for general feedback and testing of new versions of Locus Map Watch add-on for Samsung Gear and Galaxy Watch.

Currently only closed beta version for registered users is available and is distributed only using Galaxy Apps (on both phone and the watch because of Samsung limitations). Registered users should be able to install and transfer the add-on to their watch by opening this link directly on their phone (Galaxy Apps should capture the link and open add-ons store page)

The closed beta version should communicate with the latest Locus Map Free or Pro versions directly. When the official "public/open" beta comes out it will be only available for Locus Map Free (again due to some Samsung companion app policies, we will probably have to make separate Locus Map Pro Gear add-on even though both add-on versions will be practically identical).

The add-on requires Locus Map phone app to run, it is not (at least yet) stand-alone.

There are two main screens available:
- Map screen: features zoomable and scrollable map with autocenter/rotate function button.

- Track recording screen: Offers function to select one of your tracking profiles and start the track recording. Then there is multi-page dashboard when the recording is active. You can pause/resume/stop the recording or add waypoint. Dashboard values are configurable by long-pressing them directly and choosing a value from the displayed option list.


Not yet available features:
- navigation directions: partially implemented but not available. Navigation directions will be available directly on top of the map as an overlay when the navigation is active.
- heart rate measurement: something we would like to add, but the implementation has not even started yet.


Known (serious) bugs:
- screens might not display correctly or at all on Gear S2 (seems to be mostly the case right after installing the add-on. On second or third run the things seem to sort out themselves for some reason)

- the add-on refuses to connect to the phone if the phone is in "sleep"(i.e. has had the screen turned off for a while). Just turning on the phone screen makes the add-on suddenly reconnect. Confirmed with Samsung S7 (Android and Gear S3 - if you are also affected by this problem please let me know.


I don't have access to the latest Galaxy Watch so any kind feedback from that watch would be helpful.

Please share with me any bugs, crashes or any other feedback which would help me improve the app for you.

Thanks a lot and hope you will enjoy

Milan

@Condor
Online status is currently missing, we should definitely add it.

There are no audio/vibration notifications about unread messages, but we also plan to add these. But you should be able to at least see the number of unread messages in the notification area in Live Tracking notification description.

@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

@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.

@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.

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