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

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

2
Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )
« on: October 11, 2018, 08:37:08 »
Hello Gynta,
thank you for spotting the issue with LT statusbar, looks really odd. I will be fixing this promptly.

Have a nice day,
Milan

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

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

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

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

7
[DE] - deutschsprachiger Forumsbereich / Re: Ist Locus nachtaktiv?
« on: September 09, 2018, 08:51:50 »
@alter Rentner1

Hallo,
können Sie mir bitte mehr über das Problem sagen? Locus Map sollte im Hintergrund nichts im Internet tun, aber wir hatten ein paar Berichte über verdächtige Datenverbrauch, also vielleicht ist es eine Art seltsamer Bug.

Zuerst entschuldigen Sie mich, aber ich kann die Tabelle nicht wirklich verstehen, was ist Ko Einheit? Über wie viele Megabytes oder Gigabytes der Daten sprechen wir?
Haben Sie Locus als Service option aktiviert?
Haben Sie Live Tracking verwendet?
Verwenden Sie Offline- oder Online-Karten?

Vielen Dank,
Milan

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

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

10
@gynta
Das war super schnell. Vielen Dank!

11
Hallo,
nutzt hier jemand das Add-on "Wear for Locus Map"? Wir planen ein neues Update mit neuen Features und es würde uns wirklich helfen, wenn jemand neue Texte in Crowdin ins Deutsche übersetzen könnte.
Also, wenn Sie Zeit haben und mit diesem Add-on helfen wollen, bitte helfen Sie :) Es wäre sehr geschätzt.

Danke, Milan

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

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

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

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

Pages: [1] 2 3 4