Messages

Hi Jan!

I am really sorry about the whole Garmin API-fiasco.
Got to say, on my FRN945 I am only using the app for quick course transfer from the phone, and love it!

Although I plan to upgrade to a Garmin Edge for my bike, and as I see it is not yet supported.
Is it still planned to be supported, or maybe the community can give some advice how to quickly copy courses from phone to a Garmin Edge 530?

Thanks! 

Will we get custom data screens?

Hey there!

Jan, have you considered apart from the customizable garmin data screens the possibility of including pedal cadence? It could be included instead of the avarage speed for example 

Because I understand that the custom screens are a much bigger effort to implement.

Thanks for your answer!

Edit: I forgot to ask, is this app open-source like the Sony Smartwatch 2 companion app was (I know that it was made by the Locus team)? Because if the source is public, I could squeeze the cadence into it 

Hey Jan!

I really like this activity app, I have used your implementation for Sony Smartwatch 2 and for Android Wear in the past, but this is the right way, I think. I am a proud owner of a Forerunner 645 Music for 3 whole days now, so this came just in time for me.

I would be glad too if the data screens would be customizable, but as a quick fix, if this bigger change requires more effort, it would be enough for me if I could see the current (pedal) cadence in the watch-side data screens.

Oh and also, if someone pairs the sensors with the phone app, and start recording there, do you plan to just mirror out the measured values to the phone data screens in the Garmin app? So no broadcasting or duality, only the already measured values would be indicated like with the distance for example.

Hi there!

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

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

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

Here is my screenshot with time on the x axis:



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

[Regarding heartrate from the watch:]

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!

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?

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

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:



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

Hi Milan!

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



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 

But anyway, thanks for everything, you are the best!

Hi Milan!

Did I see correctly, there is another new build?

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?

@Danjel:

Does the heart rate sometimes drops to zero on your side as well if you're using a dashboard? 

Hi!

I am sharing my dashboard which I use for cycling, you can see the current, average and maximal heart rate, current elevation , elevation gain and loss, slope degree, graph, current speed, avg speed and max speed, trip time, and distance.

Feel free to use it / alter it. 

Sneak peek:

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!