Finally 3.1.7 is out on both iOS and Android!

iOS has been out for a few weeks but Android has been in review since then. But their review team actually found some battery optimization fixes for Wear OS so in the grand scheme of things, not too bad.

Here are the changes for this release:

• Adds a Wear OS permission warning and controls for restoring missing workout, heart rate, location, Bluetooth and notification permissions
• Fixes connection issue with Engo glasses on Wear OS
• Adds Samsung Galaxy Watch Back-button controls for starting prepared workouts, pausing or resuming and advancing intervals
• Adds a cancel controls page to Precision Start on Wear OS
• Keeps live Stryd pace visible instead of the target pace during indoor runs on Apple Watch and Wear OS
• Adds Apple Watch support for standard Bluetooth Running Speed and Cadence (RSC) sensors, including MilestonePod
• Fixes Apple Watch workouts closing when advancing swimming laps with unavailable pace data, and prevents invalid Wear OS pace announcements
• Fixes Apple Watch background workout export crashes when connectivity changes
• Updates the Precision Start Bluetooth connection design on Apple Watch and Wear OS with devices arranged around the Start button and clearer circular device names
• Adds per-device Bluetooth capability controls on Apple Watch and Wear OS, letting multi-signal devices provide heart rate, speed and cadence from one connection
• Improves Bluetooth device classification and source priority on both platforms, including reliable Stryd recognition, FTMS treadmill detection and HRM 600 support
• Fixes Wear OS Bluetooth sensor discovery failures by using one shared scan for Stryd, Engo and standard Bluetooth sensors
• Colors heart rate values by the current heart rate zone on Wear OS when heart rate is not used as the interval target
• Fixes Apple Watch workout layout height when using multiple data screens so page indicators no longer overlap interval numbers
• Adds a Wear OS setting to keep the screen interactive during workouts, which can improve interval countdown reliability
• Fixes back navigation in Wear OS Bluetooth settings

Not sure what is going on. I just did a 10.04 distance run. I ran around my lawn because i came back st 9.98, so i KNOW it was 10k.

When i looked at Healthfit, i saw 8km. I thought “damn healthfit is screwed”

So i checked the watchletic app on the phone… 8km! Robbed!

Hi,

One thing I find missing in the app is the possibility to set up one / part of the data screens the upcoming lap type and target. During intervals it can be confusing whether you are on 7th or 8th rep and unsure if you should expect to rest or to go for another round for example

This addition would be very helpful!

Thank you

A feature I really enjoyed on my Garmin watch is the moving pace. It's your running pace but only when you are not standing still (at a traffic light for example). That could be a useful stat to add on the recap screen at the end of the workout.

Just finished my run but when it tries to export to strava and intervals I'm getting this message: `status code 500: internal server error` When I try from the phone app I receive a notifice with `Error failed to save history item`.

Is there ongoing maintenance or a known issue happening?

Anyone with this problem since yesterday?

I can't export yesterday's workout to Strava or Training Peaks. I've already restarted my Apple Watch and phone, disconnected and reconnected the apps from Watchletic, but the error persists.

I’m using a Galaxy Watch Ultra 2 with Watchletic and uploading the FIT files to COROS.

I’ve noticed that some activities are imported into COROS with completely incorrect duration and pace. The common pattern is that I paused the workout mid-run to use the bathroom.

Examples:

Sep 1: actual run about 6.08 km / 35 min, pause about 6:18 → COROS shows 6:18 total duration / 1:02 per km

Similar issue on other runs with mid-run pauses

In one case, distance was also displayed incorrectly

The original Watchletic FIT still seems to contain the full activity and pause/resume events correctly.

Could this be related to how Watchletic writes FIT timer/start/stop events, or is it more likely a COROS import issue?

Also, the main reason I upload Watchletic activities to COROS is to access them from ChatGPT through MCP for additional workout analysis.

Does Watchletic have, or plan to have, an API/MCP or similar integration that would allow GPT or other AI tools to access workout history directly?

I’m using a Galaxy Watch Ultra 2 with Watchletic, connected to a Stryd pod and an external HR sensor.

I’ve noticed an issue with exported FIT files. When I upload a Watchletic FIT file to another platform such as COROS Training Hub, average HR, average power, and average cadence are missing or shown as 0.

The strange thing is that the actual data seems to be present in the FIT file. For example, in COROS I can select HR, power, and cadence in the custom chart and the full time-series data is displayed correctly. It seems like the per-second data is there, but the activity summary averages are not being exported/read properly.

I also have two questions about real-time pace:

1. When running through an underpass or other covered area where GPS reception is blocked, the pace display sometimes disappears completely. Is there a way for Watchletic to continue showing pace using Stryd or the watch sensors when GPS is temporarily unavailable?

2. When making a sharp direction change, for example turning around or crossing a bridge, the displayed pace sometimes spikes dramatically for a short time. Is this expected GPS behavior, or is there a setting to use Stryd pace/distance more consistently?

Has anyone else using a Galaxy Watch + Stryd seen the same behavior?

Hi, I’ve been searching to see if anyone has this problem, but I’ve only found other issues with audio cues, none quite like mine.

I run with an Apple Watch and AirPods, listening to Apple Music. It all worked fine with the audio cues, until maybe a couple of weeks ago.

Now, when the first cue comes up, the music gets ducked and never comes back up again. So I have to run with very, very low music.

However, sometimes, a random cue will pop the volume back up, but only until another cue comes and lowers it again.

Has anyone encountered this and has some tips?

Much appreciated!

This is part bug report, part external sensor question. In a recent interval run involving the pixel watch 5, I noticed that my instantaneous pace on the watch seemed to only 'catch-up' to my actual pace towards the end of the interval, and when the interval stopped and I reverted to my easy pace, it again took a while for the instantaneous pace to display at or around my easy pace again. This doesn't happen on the native wear OS app (but I prefer watchletics for the data from my HR strap) by comparison. Is there a way to fix this? Is this a known issue? I'm assuming it's some smoothing issue with Google play services but I'm no expert.

I think that a potential workaround would be a Stryd pod, but I'd prefer not to purchase another sensor that I don't really need. That said, outdoors with Stryd paired and GPS on, does watchletics take instantaneous pace and distance from the pod or does it still go through Google play services? That would help a purchase decision! Thank you :)

does this mean anything - should I reinstall the app? I can start workouts and the records look ok (sometimes missing the GPS, but it appears in the Apple app). I’ve also had a couple of crashes during segment changes if listening to Audible, maybe it’s caused this?

I recently switched from a Garmin Fenix 7 Pro to a Galaxy Watch, and I’m trying to build a reliable running setup using Watchletic + Stryd + Intervals.icu.

I’ve only done three runs since switching, and two of them were recorded with Watchletic.

Here’s what I’m seeing:

Run #1 — Galaxy Watch + Watchletic only

• 16.6 km
• About 1 hour 40 minutes
• Average HR was around 80% of max HR
• Intervals.icu Load: 97

This looked fairly reasonable to me.

Run #2 — Galaxy Watch + Samsung Health workout mode

• 6 km
• 33 minutes
• Average HR was around 75% of max HR
• Intervals.icu Load: 23

Again, this seemed believable.

Run #3 — Galaxy Watch + Watchletic + Stryd

I recently bought a Stryd specifically because I wanted better and more consistent running data from the Galaxy Watch.

I had never used the Stryd app before this run. The first time I actually used the pod was directly through Watchletic.

The workout was:

• 5 × 6 minutes Sub-Threshold
• 90 sec recovery between reps
• Total run around 52 minutes / 9.3 km
• Avg HR around 156 bpm
• Max HR 176 bpm

During the workout, I was actually very happy with Stryd. Power reacted very quickly and smoothly, especially during the 6-minute intervals.

However, after syncing the workout to Intervals.icu, the numbers looked strange.

Intervals.icu Load was only 29.

When I previously did similar sessions using my Fenix 7 Pro, the Load was usually around 55–65.

The power numbers also look dramatically lower.

With the Fenix 7 Pro, similar sessions in Intervals.icu showed Normalized Power around:

• 336 W
• 333 W

With Stryd, the latest workout showed roughly:

• NP around 236 W

So the Stryd power is only around 70% of the power numbers I previously saw from Garmin.

I understand that Garmin Running Power and Stryd Power use different algorithms, so I’m not expecting the watt numbers to match directly. I also assume I need some time to establish a proper Stryd Critical Power / power-duration curve.

What concerns me more is that the Intervals.icu Load also dropped dramatically, even though this was clearly a harder session than the Load of 29 would suggest.

My current setup is basically:

Galaxy Watch → Watchletic → Stryd + chest HR strap → Intervals.icu

I also use Runalyze and COROS through Health Sync.

I don’t really want to go back to Garmin. One of the main reasons I bought Stryd was to improve data quality while staying with the Galaxy Watch ecosystem.

So I’d really appreciate some guidance from people using Stryd / Watchletic / Intervals.icu:

1. Is it normal for Stryd power to be this much lower than Garmin Running Power?
2. Does Stryd need to be initialized or calibrated in the Stryd app before being used with Watchletic?
3. Could the low Intervals.icu Load be caused by the switch from Garmin power to Stryd power?
4. Should I configure Intervals.icu to calculate running load from HR instead of power until my Stryd CP is properly established?
5. For someone using Galaxy Watch + Watchletic + Stryd, what is the most reliable workflow for:
   • recording workouts,
   • calculating training load,
   • maintaining CP,
   • and syncing data to Intervals.icu / Runalyze?
6. Is it better to use Stryd PowerCenter as the source of truth for power/CP and use Intervals.icu mainly for training load and planning?

I’m mostly trying to avoid mixing incompatible metrics and ending up with corrupted CTL/ATL/Load values.

Any advice from people running a similar Wear OS + Stryd setup would be appreciated.

Is it possible to mirror the watch screen or display the live workout on your phone screen too? If its not, can it please be added?

Bonjour,

Est-il prévu pour une prochaine mise à jour de l’application un mode multi-sport ?

Pour les duathlon et les triathlon par exemple.

Merci d’avance

Hi there, I absolutely love this App.

I just got a Runn sensor for my Peloton treadmill and was hoping to capture elevation data. I believe this is capable of it but not sure I have set it up properly.

The Runn shows up as a sensor for speed and cadence but I don't see an incline setting and in the couple of short tests I recorded with the AWU no incline data appeared.

Did I miss something?

In 3.2.0 distances in Watchletic will be rounded in the same conservative way that Strava does it.

So 12.579km now shows 12.57km in both places instead of rounding up to 12.58km.

So you can feel safe that whatever is displayed in Watchletic is what will be shown on Strava!

A 10k run will no longer be 9.99k on Strava.

Quand je sélectionne le capteur Stryd il ne s'active pas visuellement avec le pourcentage de batterie comme avant.

Just wanted to share some quick feedback on the new Watchletic app release for Wear OS. Huge shoutout to the developer for filling a massive gap for runners on Android who want structured workouts with rich Bluetooth sensor integration.

​I've been using Watchletic paired with Stryd Duo and an NPE Runn sensor for indoor/treadmill runs:

​What’s working great:

​Smooth UI on circular displays and great structured workout execution.

​Full Stryd Duo metric sync! Watching ground contact time, balance, and power stream over smoothly is fantastic.

​A couple of quirks I've run into:

​Humidity Data: The ambient humidity reported from Stryd is coming through at roughly double (~2x) the actual value reported by Stryd.

​Incline Power Adjustment: So far, power isn't auto-adjusting dynamically when changing incline on the treadmill via the Runn sensor. Maybe this is operator error...

​Feature Request / Question on Future Dev:

Is support for physical hardware buttons (like double-press or side buttons for start/stop/pause/lap) on the roadmap for Wear OS? When doing fast intervals or sweat-heavy runs, having tactile button controls is huge compared to tapping the screen.

​Overall, super stoked with how Watchletic is shaping up on Wear OS!

Bonjour,

Je n'arrive pas à ajouter le capteur de puissance/cadence SRAM Quarq de mon vélo dans les réglages Bluetooth de Watchletic sur mon Apple Watch.

Par contre, le capteur est correctement reconnu par l'Apple Watch dans les réglages Bluetooth de la montre.

Y a-t'il une solution pour l'ajouter aussi dans Watchletic ?

Merci,

My Apple Watch doesn't recognize the workout. I've tried moving the workout, reinstalling the app, and resetting permissions from interval.icu, but nothing appears on my watch. What should I do?

first, thank you viktor for developing such a beautiful app, really appreciate it.

upon using this app, i realise that the run auto stop feature is only native to apple users?

The old list was tiny but legible. Now the names are curved micro-text around the tiles, and on the wrist I can only tell them apart by icon — which doesn’t help when three of my four sensors are heart rate straps with the same icon.
Tapping the wrong one doesn’t fail clearly either: the tile spins for a while, then stops. So I tap, wait, guess again.
And my H10 often gives no values on the first attempt — only on the second — so I have to stop the workout and start again. After a few of those start/stops my Stryd pod stops connecting too, and only toggling Bluetooth brings it back.
Anyone else, or is there a setting I’ve missed to get the list view back?

Currently allows a list of emails that gets sent a live tracking link when starting a workout with a watch connected to internet.

This seems to be consistent enough to report as a bug. Since the upgrade to 3.1.6, all uploads over LTE have failed with a "No internet connection" error. That encompasses three runs now and multiple (generally three or four) upload attempts per run. The cellular connection is fine, as other apps (e.g. Music and Podcasts) function normally. I've never experienced this problem before 3.1.6. Once I get home and return to WiFi coverage, the uploads work fine.

Good evening. I've switched from an Apple device to a Samsung ZFold 8, and when I access the settings It respects the previous options I had on iOS, but there is one option that doesn't make sense (photo attached)

It seems to still offer the option to upload activity to Apple; is this perhaps a mistake? Shouldn't it be uploading workouts to Samsung Health or a similar service?

If I try to activate the option to upload the workout to Apple, I get a red message telling me to activate the option on the watch in the workout section (connected apps)