Thank you!
For 1st point, it is not an expected behavior! Last activity should be save. I guess it was broken when I update. Graph display is also good suggestion
Let me see what’s happening
Which kind of workout is it when you find lack of information in TCX? I don’t remember well though, platform such as Strava creats speed information when tcx is imported.
Hi @Hagu ,
first of all, thanks for your great work! I’ve explored your app a little and it does look very nice. One thing that’s stopping me right now from using it is the BLE HRM sharing available in a preview firmware here: BLE Heart Rate Monitor Sharing for Pebble Time 2 by bekriebel · Pull Request #1598 · coredevices/PebbleOS · GitHub
I’m using that to record the run including HR data with Strava on my phone, but would really like to have a nice distance/pace/hr display on my wrist.
Unfortunally it seems the workout app itself has to trigger the HRM sharing and it’s not coupled to the “heavy HRM”. I don’t know whether it’s even possible before that feature hits the regular firmware release, but if you manage that to work with your app, you will certainly have a new loyal user
The workout (in all cases for me) is cycling. I import into GoldenCheetah on Linux. I’ve not tried any other tool however. I’ve always used GC, primarily with FIT files from my Garmin watch. I don’t have much (any) experience with TCX files.
In any case, it’s not a big deal because the GPX file has the distance and speed and that’s really all I want.
Thank you for your interest in this app
Once this PR is merged, it would be a great option if third-party apps—like this Iron—could trigger the workout state
When I had started to work on developing this app, PebbleOS did not allow 3rd party app to wake pebble workout app up.
If you don’t mind to import tcx file to Strava manually, you can see good workout status on your wrist now
That makes sense. For cycling, I deleted some information such as “Cadence”, because any BLE sensor was not supported by this app. That may cause lack of information.
I try to see something for next update
Android app is now updated.
Middle, bottom row and last workout should be saved Android app 2.0.1.
Also I think TCX file is getting better with be added distance information.
I’ve gave it another try today and unfortunately had the worst experience yet.
I started the run with on my smartwatch and so far so good, everything looked fine. After a few minutes I wanted to check my pace and read ~16:00. Wtf is that supposed to be? I checked distance which was showing ~0.5km when it should’ve been significantly more. I got my phone out and had a look on the iron android app and the map showed the correct GPS-Path but also the wrong distance. My hunch would be that it’s maybe showing miles instead of km, despite showing km as the unit?
I ran about 5km to the meeting point of my running club, accidentally hit the pause button when taking off my running backpack to put away my bluetooth-earplugs, but resumed it no problem. Had a ~9km run with them with no problem. Everything except the time and heartrate was useless because none of the numbers were right, but at least it kept recording that far (foreshadowing).
So I finished the round with my running club and was on my way home (with a detour to make it a half-marathon) I took off my backpack to get my bluetooth-earplugs out again and accidentally hit the pause button on the watch again. (Could’ve been a different button, too) But there was no resume this time. My watch was showing my stats of the current run with the time not progressing. There was a pause symbol in the top right, so it appeared to not be paused?
I tried to resume / pause a few time with no effect. So I got my phone out, switched to the iron app and was greeted by a blank home screen. (“READY TO START” 00:00 0.00 --:-- --)
At that point the watch display reset as well. It did not save anything, the run was just discarded/lost. I restarted it again with the same issue as before with none of the numbers making sense. When I got back I stopped it and managed to properly save that segment.
One more thing I noticed on a run last week, where I already tried using iron. The pace display seems to always display the pace for the full run, which is kind of pointless. A rolling average over the last like 1-5min makes a lot more sense. That run did apparently not save properly either. I neither could find it in the history, nor in the target folder for auto-exports.
So my feedback:
As it is right now, the app is unfortunately unusable for me. I would have been horribly frustrated if I didn’t have strava recording in parallel on my phone.
Hi Forsaken,
Thanks for the detailed and constructive report. It’s incredibly helpful.
Since you mentioned you’ve tried the app before and are currently on version 2.0.3, it’s entirely possible that I accidentally broke something in this recent update.
Regarding the app resetting to the “READY TO START” screen and the data loss: It is just one possibility, but from my experience during development, I suspect your phone’s Android OS might have killed the app’s background process to save battery while it was in your pocket.
This kind of task kill often happens if the app isn’t granted permission to run in the background. Just to be sure, could you check your Android OS permission settings? I’m attaching a screenshot—could you take a look and let me know how this specific setting is configured on your device? Also, to help me investigate further, could you let me know what phone model and Android version you are using?
For the distance and pace calculation issues, I will look into it. I’ve already noticed some discrepancies between the app’s calculations and the exported GPX files when uploaded to external platforms, so I will investigate what exactly is going wrong there.
Your idea of using a long-press for the pause button to prevent accidental presses is great. However, changing the interface takes some time, so I might not be able to implement it immediately, but I’ll definitely keep it on my list.
Since I develop this app in my spare time after my day job, I honestly can’t test every single scenario or catch every bug before a release. That’s why I really appreciate you taking the time to test the app multiple times and report these details. Thanks again for your feedback!
I think it is very unlikely, since the timing matched accidentally pressing buttons on my watch (during getting off/on my backpack) very tightly. The most probable thing imho is a button sequence that broke the android app (e.g. continue before the pause was processed or something like that)
Maybe just try spamming the buttons a bit and see if something breaks
I will still make that adjustment for future tests, to ensure battery optimizations are not the cause for any issues.
Here’s a little extra info. The second part, which I recorded after the crash actually shows the issue very well in the history. The total shows 3.26km, but the map preview above clearly shows at least 7km. According to the GPX file it’s actually 7.5km.
If you need the GPX file for debugging, feel free to hit me up.
Don’t worry, I’m a software dev myself, I understand. I appreciate the time and effort you put into this project.
Especially things like the long-press pause are not a priority. More on that topic:
It probably makes sense as an option instead of the standard. If the bottom button does anything “dangerous” (you did not reply on that and I have not tried to figure it out yet) that should hold to activate as well, if that option is enabled. Just making sure accidental short presses don’t mess up your run.
Thank you for your a comment so quickly, details .
I don’t have much time this weekend, but I just want let you know the job of down button when you are running. Down button switch the graph data, such as pace, distance, HR, CAL, steps. I hope I fix this app soon and you see the graph works
Ah, okay. That makes sense. Personally I’d rather have a second “number row” instead of the graph, being able to e.g. show pace + HR at the same time. While the graph looks nice, I don’t think it’s that useful.
Take your time and prioritize the essentials. Have a nice weekend 
Edit: One more thing, I already had Iron on unrestricted battery usage, so that was not the cause for the crash.
I do think you may have broken something in the latest update. I went out for a bike ride with a friend. After 8km of riding, the app on my watch indicated just over 1km whereas my mate’s watch (a Garmin) said 8 km! I thought maybe I had done something wrong so checked the Iron app on my phone: the map on the app clearly indicated 8 km or more had been travelled.
I started the recording again and the same thing happened: the summary was many kilometres less than the actual travelled distance.
Thanks.
Thank you for letting me know.
I submitted the new version that may be removed bug to Google Play, under reviewing now.(So sleepy 
)
I hope it works well
There may still be some bugs left, but a version with the distance calculation error fixed has been released on Google Play.
I learned the importance of testing before release…
Thanks. I’ll update and give feedback when I have a chance to try it out.
Hmmm…
first things first, I just did a run and on my watch during the run everything was very nice. Distances were looking good, the new pace display was very helpful, no glitches chefs kiss
I’d still have a few ideas, like for watch notifications you could add zones for heart rate / pace and have the watch notify you by vibration/sound when leaving those defined zones. But that’s luxury. I would really like the second number-row instead of a graph, but even that is very much a nice to have. The current state is well usable, if it works reliably (foreshadowing 
)
When I finished the run, I think I might have accidentally discarded the recording. It might be partially because I’m an old man now (a bit hyperbole, I’m 39, see also the “larger system font”-topic for other old men in the same boat) I can’t tell shit with the tiny button symbols. Like play and pause is easy enough, settings I get, too, but the others are too intricate and unclear for me to tell, especially after having just run for an hour.
If there’s a discard button right after stopping the recording I would really appreciate an extra confirmation screen before trashing an hour of running data (especially since that seems to be before the auto-export, which I’ve got enabled). Better still, I would much prefer not even having that button. If I want to delete it, I can still do it on the companion app after the fact.
Fortunately this old man was wise enough to still record with strava on my phone, which means I only lost the heartrate data.
Thanks a lot for your effort, I’m really impressed you already managed to include the extra pace options in the last update (I was only expecting a hotfix for the wrong distances) and I’m looking forward to where your app is going
Thank you for trying update and comment!
I was super busy but I will read your comment, and consider next step
But I have to mention something right now.
“Old man” is significantly hyperbole, because I will turn 39 next month 
Unfortunally I have another bit of bad news. I’ve tried to log an “other” session today (climbing) and had the companion app close on me again. I just checked battery saving setting and found one more option to set, but other apps like e.g. strava work fine without that extra permission/setting. It broke after about 90 minutes (1:38:02 according to the watch display) of recording and again discarded everything.
As of accidentally discarding the run, I’m very certain I did top button (pause) → middle button (stop) and then middle button again (whatever that symbol is). I just did a short test, which did indeed save it properly. So there might sill be an issue with that as well 
Quick post to confirm that the app seems to be working properly now. Distance and speed all seem to have been recorded properly over a 5 hour bike ride.
Thanks again! A very useful app.
Thank you for letting me know. It is possible that a bug occurs depending on the timing of the button presses; I have also experienced instances where the app’s status doesn’t change immediately after pressing a button. As you suggested, it might be best to save every workout once it is finished. However, changing that sequence requires some preparation. For the time being, I will focus on stabilizing the Android app itself. I also have ideas for changing the bottom display area, but like the button operations, that will require some preparatory work.
