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.

Messages - H Ifang

Pages: [1]
Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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..

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

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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!

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« on: February 13, 2018, 14:52:17 »
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.

Wear for Locus Map / Re: Wear for Locus Map beta testing
« on: February 12, 2018, 19:25:26 »
There are a lot of screenshots in the Play Store app page:
The third shows a 4-element-mini-dash..

You can also see some profile selection..

Wear for Locus Map / Re: Wear for Locus Map beta testing
« 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).

Pages: [1]