Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - milan.cejnar

#1
Currently trying out a Galaxy watch, after some pause and an Android wear watch before.
After some times running and once skiing I can say: Locus app works (Thanks!)

Of course, there are various details that could be improved from my perspective.

I am missing the heart-rate field in dashboard (showing the values of hr-belt connected with the phone) - should that not be one of the first values to think of? Of course, it would be very nice, if the watch's builtin HR sensor could be used too.

Clock (current time) would also be an interesting field for dashboard - not having to switch to watch time display and back. Sometimes on screen activation the current time is overlayed at the top for a very short time - did not find out when and why it does or not.

Not very nice is the fact that it always takes a moment until values refresh - so at first you always see the old values from previous/last time screen was active. I would prefer to spend that little extra energy to also update in the background - or at least refresh-before-show!

A pity it cannot be operated with buttons. But probably the Galaxy buttons are quite specific in what they are meant for by Samsung? At least, the screen seems a bit less sensible regarding unwanted touchscreen events than the Fossil Q Explorist I used to have.

But I cannot see much sense in the little start/switch screen. You press the back-button to get there and then need to touch to go to either map or dashboard. Usually you will go there to switch. Why not directly switch with that button - and exit with a double-button-press (or if not allowed other way around). Then at least one could use the watch with gloves only using buttons and the rotatable bezel (with both dashboard and map).

Perhaps you can consider. Thanks.

The following users thanked this post: milan.cejnar
#2
Hi Milan.
Thanks for your reply.

Seems everything is in except of "slope" .

Already any ideas, when it could be possible implemented?


Thanks for your suggestion, but using another phone does not solve me y issue:
I would like to have a device , which has a display permanently on.
Just like a standard old fashion bike computer.

So my optimum would be:
- a small smart phone with
- ANT+ sensors connected, with
- huge battery power
- ruining Locus with
- display always on in bright mode
- for several hours
- waterproof

But I did not found anything like this jet. 8)


So, a simple smart watch with the Locus Wear App connected to my  Nokia, will maybe a possible compromise.


The following users thanked this post: milan.cejnar
#3
Thanks Milan! The second method works! All good so far!
Will continue testing...
Cheers big.

Gesendet von meinem SM-N930F mit Tapatalk

The following users thanked this post: milan.cejnar
#4
Thank you for this answer !  :)

Quote from: milan.cejnar on October 18, 2018, 16:04:05
... 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.
The following users thanked this post: milan.cejnar
#5
Hallo,
ich bin jetzt im Urlaub und melde mich in der letzten Septemberwoche wieder.
Fritz
The following users thanked this post: milan.cejnar
#6
Locus Map Watch / Re: Wear for Locus Map beta testing
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ɷµ#¯ ` ` ` ` `
...'''''''™''''™'''™''''™™ ... ... ` ` ` ` ` ` ` ` ` ` ` ` ... ... ` ` `
` ... ` ` ` ` ` ` ` ` ... ` ... ` ` ` ` ` ` ` ` ` ` ` ... ` ` ` ` `.
The following users thanked this post: milan.cejnar
#7
Quote from: milan.cejnar on August 30, 2018, 15:08:33...
Add-on "Wear for Locus Map"
...Crowdin
...

Gern gescheh'n
You're welcome!
The following users thanked this post: milan.cejnar
#8
Good day alklecks,
this is little un-usuall use case. Sensors in watches usually (for now "always" as I know) does not use common communication with a phone like do any specialized "heart rate monitors" or "barometric sensors". So it is little complicated to send such data from watches to the mobile device (Locus).
So for now, this is not planned.
The following users thanked this post: milan.cejnar
#9
I have found that putting my phone in airplane mode more than makes up for running the GPS. I also set Locus to shut off the GPS when the screen is asleep. I wake it up every 15 minutes or so to verify position and heading and then put it back in my pocket. I will typically have 75% battery at the end of a full day hike.
The following users thanked this post: milan.cejnar
#10
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..

The following users thanked this post: milan.cejnar
#11
Quote from: 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..

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


The following users thanked this post: milan.cejnar
#12
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
The following users thanked this post: milan.cejnar
#13
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
The following users thanked this post: milan.cejnar
#14
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
The following users thanked this post: milan.cejnar
#15
Casio WSD-F20 report

1. Zoom +/- with button works fine. Thank you.
2. Stable application is okey.
3. How does auto-rotate function work?
The following users thanked this post: milan.cejnar