# Sessions from watch truncated or corrupted while transfered to phone

**URL:** https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548
**Category:** Support
**Tags:** session
**Created:** [September 29, 2026, 6:16pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548 "2026-09-29T18:16:23Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Ciprian](https://forum.windsporttracker.com/letter_avatar_proxy/v4/letter/c/848f3c/32.png) [@Ciprian](https://forum.windsporttracker.com/u/Ciprian)
#### Post date: [September 29, 2026, 6:16pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548/1 "2026-09-29T18:16:23Z")

</div>

Hi.

I am using windsport tracker for my windsurf sessions.

I have the following setup:

- Samsung S24 ultra running updated stock Android
- Samsung Watch ultra

Sessions are recorded by the watch that i carry on the water. The phone remains in the car. At the end of the day, i enable wifi, bluetooth and 5G on the phone and transfer the sessions.

This was working fine until the latest september update of the WST on the phone.

After update, i see the following behavior:

- Sessions remain on the watch (they use to dissapear from the watch after update)
- some sessions are truncated on the phone; see session 9/29/2026 16:06 ; this session is 8.4km-51min on phone and 28.98km-2h11min on watch
- Sessions are corrupted on phone: session 9/29/2026 13:48 appears as "session too short) on phone and 24km-1h41m on watch

I see similar problems with my 9/27 and 9/28 sessions.

I have attached relevant phone and warch screenshots.

 ![63376](https://forum.windsporttracker.com/uploads/default/original/1X/2f64573e23921c998b581fb152cf6712ad0bbb72.jpeg)

 ![63377](https://forum.windsporttracker.com/uploads/default/original/1X/1af18a0f8d7aed18194b61980b8c5b93ec89426f.jpeg)

 ![63379](https://forum.windsporttracker.com/uploads/default/original/1X/7f33b7007acb5063da600db96c79f3c260e584cc.jpeg)

 ![63380](https://forum.windsporttracker.com/uploads/default/original/1X/e3101baa7d120610db9f1c5614613b178b2cd588.jpeg)

My sessions from august look fine.

Please help with sessions recovery

Thank you,

Ciprian.

---

<div class="post-metadata">

### Author: ![WST](https://forum.windsporttracker.com/user_avatar/forum.windsporttracker.com/wst/32/228_2.png) [@WST](https://forum.windsporttracker.com/u/WST)
#### Post date: [September 29, 2026, 6:34pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548/2 "2026-09-29T18:34:04Z")

</div>

Hi,

thank you for the detailed report and the screenshots, and I’m sorry for the trouble this has caused. Losing session data is exactly what should never happen, and in this case it’s on us.

**What happened:**  
Samsung watches use a very aggressive battery-saving mechanism. The app has a safety feature that makes sure a session isn’t lost if the battery runs out during recording. On Samsung watches specifically, this feature interacted badly with the battery-saving mechanism: at some point during the session, the app stopped writing recorded data, even though the session itself kept running.

That’s why the summary on the watch (e.g. 28.98 km / 2h11) looks correct, while the phone only receives the data recorded up to the point where the issue occurred. Depending on when that happened, the session on the phone is truncated (your 16:06 session) or so short that it’s flagged as “session too short” (your 13:48 session).

**The fix:**  
This is fixed in version **2.1.0 of the watch app** , released today (29.09.2026). We’ve also added further safeguards to reduce the risk of data loss going forward.

Please update the watch app to 2.1.0 before your next session. Again, sorry for the lost sessions, and thanks for reporting it so thoroughly.

---

<div class="post-metadata">

### Author: ![Ciprian](https://forum.windsporttracker.com/letter_avatar_proxy/v4/letter/c/848f3c/32.png) [@Ciprian](https://forum.windsporttracker.com/u/Ciprian)
#### Post date: [September 29, 2026, 8:19pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548/3 "2026-09-29T20:19:21Z")

</div>

You mean that my 27 28 and 29 september 2026 where I see this problem are all lost?

I can see the summary correclty on the watch.

Isn’t there any way to export them raw frm the watch in order to recover?

I really care about having this sessions logged, thus i use the payed version of the tracking app.

Thanks,

---

<div class="post-metadata">

### Author: ![WST](https://forum.windsporttracker.com/user_avatar/forum.windsporttracker.com/wst/32/228_2.png) [@WST](https://forum.windsporttracker.com/u/WST)
#### Post date: [September 29, 2026, 9:03pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548/4 "2026-09-29T21:03:53Z")

</div>

unfortunately yes, the missing parts of those sessions can’t be recovered. What you see on the watch is only the session summary, which is calculated and displayed live during the session. The actual track data stopped being saved at the point where the issue occurred, so it was shown on the watch but never stored. A raw export wouldn’t contain it either. The parts that did make it to your phone are valid and stay in your log.

Why this wasn’t caught earlier: the issue only affects Samsung watches, and it is triggered at a more or less random point during a session. A pure functional test on a Samsung watch passes, because nothing goes wrong until the bug kicks in. My own sessions are recorded with a Pixel Watch, which isn’t affected. So I only found out through user reports like yours. Once I could reproduce it, the fix itself was quick, but Google’s review and release process for Wear OS updates takes at least a week, which is why version 2.1.0 only became available today. On top of that, the automatic updater on the watch often takes a few more days to install updates in the background, which is why today’s session was still affected.

To make sure you’re on the fixed version right away, open the Play Store on your watch and update Windsport Tracker manually. You should see version 2.1.0.

I know losing these sessions is annoying, especially since you rely on having every session logged. I’m sorry about that. I’ve sent you a private message.

---

<div class="post-metadata">

### Author: ![WST](https://forum.windsporttracker.com/user_avatar/forum.windsporttracker.com/wst/32/228_2.png) [@WST](https://forum.windsporttracker.com/u/WST)
#### Post date: [September 29, 2026, 9:13pm UTC](https://forum.windsporttracker.com/t/sessions-from-watch-truncated-or-corrupted-while-transfered-to-phone/548/5 "2026-09-29T21:13:38Z")

</div>

One more thing for everyone affected by this issue:

I’ll try to create import files for the affected sessions, based on the values shown on the watch. These files will only contain date, duration and distance, so there won’t be a track, maneuvers or speed values. After importing, you can add notes and equipment as usual, so the sessions will at least show up in your history and statistics.

If you’d like this, send me a private message with screenshots of the session summaries from your watch (date, duration, distance).
