[Solved] - Timer Related Issues

Resolved Bugs and Issues
#1

A few different users have timing related issues. It seems to mostly affect older phones but some issues to new phones as well. We have thousands of app users and only a few issues reported but we want to be very proactive in improving the performance and timing issues that do occasionally occur.

Here are a few issues
One iPhone 6 user had 1 time issue related to time that seemed off
One Pixel Pro 6 user had an issue of it recording 2X the speed
One Keiser M3i user had issue when app went to background the cursor was not in sync with the target.

I am just going to merge all timing related issues to this thread.

2 Likes
#2

I also had the interval and total time off by 5 seconds twice.
Once the cursor was also kind of frozen but the intervals changed. It only happened once and I also fiddled with split screen too much.

#3

Oh thanks, yes I put this hear to hear from more people that might not normally speak up.

#4

As an additional data point, I have had this issue on an iPhone 8 (using a Keiser M3i converter).

Current work-around:

  1. restart the phone,
  2. only one other app in the background (for music)
  3. make sure to keep the TrainerDay app in the foreground

Restarting the phone seems to matter. Only doing steps 2 and 3 didn’t work for me. (Perhaps restarting shuts down some background processes?)

#5

Hey!
I have had a similar problem lately. After pausing the workout to take a phone call, I resumed, but the intervals started too early (watts increased, while they should not according to the display), then the clock ran too fast (approximately two seconds per second). Really weird!

I have attached two screenshots. The first shows the workout how it appeared during the session. Notice how weird the watt tracking line jumps around on the time axis:

workout_during
workout_during1024Ă—1757 211 KB

The second shows how the workout looks after finishing it in the desktop app. The watts are completely out of sync with the plan.

workout_final
workout_final1501Ă—481 55.5 KB

This is really broken for me. Haven’t used trainerday since.
I am running Android 9.

#6

That’s terrible. Thanks for sharing. We will definitely fix this. It’s so strange for 95+% of the people and 99% of their rides it works perfectly but one experience like this just destroys confidence. As mentioned this type of issue is mostly older devices but I know that does not matter to the person with the problem and we want to support older devices.

#7

Hi Alex,
Relatively new to the app. I did a 90min trainer session on Sunday and it was a difference of 11 minutes compare to my Garmin. I was using iphone 12 and with the latest IOS version.
What can I do to resolve this?

Thanks

#8

@alex I think there is more going on then performance issues of the devices. What comes back on regular bases is that some sort of interruption happened on the phone and then the app goes crazy. Might be a phone call, a social media message, or similar.

#9

For now a phone restart and limit background activities and putting the app in the background but we are working hard to resolve this right now and can hopefully have something to resolve it in the next week or so.

#10

Yes, I agree something strange. We will find it. Do you have any issues?

#11

Had this one a couple weeks ago:

#12

Oh yes, thanks for the reminder.

#13

Thanks for your work! If it works fine (as it has most of the time I used it) it is the best App out there, as it exactly fits my needs!

1 Like
#14

i had this issue last night: was controlling my tacx neo v1 from my iphone 13 pro. seen it a few times before but not this bad:

time was really dragging, every second was taking several seconds which was very painful on the harder intervals. then after an epic grind it went crazy fast for the rest of my ride. the final 5 min interval then 10 minute cooldown went by in one or two minutes.

looking at the graphs on strava it doesn’t show anything overly odd with the ride. says total ride time was the 2:10 tho i’m sure it was much longer. started at 9:55 but finished at 12:30. so workout actually took around 2:35.

#15

Sorry to hear. Crazy on 13 pro. We are working on multiple solutions to this right now. It’s something related to device performance, low battery is an example, but obviously it’s a problem that needs to be solved with our app.

#16

It would feel less bad if the .fit or .tcx that came out at the other end was based on reality. i.e if it used legit timestamps instead of the timewarped versions.

FWIW my phone sits on a charger while i ride, so it’s not low battery or in a power save mode. I often notice the last second of a ride often takes a long time, maybe related.

#17

That’s a good idea/point. We have like 20 phones and tablets on our team and we can never replicate this problem. If we could replicate it it would be so much easier to solve. We keep thinking we have solved it when we have not. I did not realize the files did not match reality but now that I think about it I completely know why. Yes we could do some post processing to inject the missing seconds.

#18

I’ve done quite a lot of hours riding with the app and other than the last second or two of rides i’ve only noticed it on a couple of other occasions, so not really surprising that it’s hard to replicate.

If you could use system timestamps instead of the “workout time” it might shed some light on things. esp when there is a big difference between the two. It was definitely weird seeing the last 15 minutes of that workout flying past in a couple of minutes. That happened other times i’ve noticed it too, like it wants to get the time back in sync all of a sudden.

Trainer Day is the activity I’ve been talking about btw, feel free to mess around with the data if it helps.

#19

So the way this works is we progress “1-second” at a time. Every time we move forward 1 second we check the elapsed time and make a micro adjustment in milliseconds to try to catch up or extend it. So we actually do what you are suggesting. What we believe the problem is that a persons system can’t do all the required processing in 1 second so even though we are trying to catch up we can’t. We are are fairly sure the re-drawing of the chart is the performance problem so right now we are changing chart drawing technologies to something more native to the device and faster. Hopefully this solves the problem. If it doesn’t the next step we realized we could do is if the system gets to a point that it can’t catch up we could just drop a second to catch back up. That is our new “revelation” to a sure fix.

Finally as you suggest we can record time stamp with each second and at the end do a clean up process to make sure the output file matches what you did.

That is a serious workout wow you are tough. :slight_smile:

This has now become our absolute top priority to fix before this winter and we are 100% sure we will fix it one way or the other.

#20

I do like to do some longer rides to catch up on movies, and I wonder if they are more likely to trigger this.

Not sure if it’s just the charting causing it to get behind in my case. My suspects are bluetooth being weird, or incoming notifications in the background causing the initial desync. Then I think once it gets out of sync it seems unable to recover.

The weird thing is for most of the ride it’s slowing me down, which makes me think that it thinks somehow i’ve gotten ahead of where I should be. Then the weird turbo speed bit at the end seems to indicate it can go a lot faster when it wants to.

How about checking the elapsed real time vs how long the interval has been running for and declaring time bankruptcy as soon as we hit the point where the interval should have finished. Or I guess conversly extend it if we get to the end of the interval but not enough real time has elapsed. Then at least if things get out of sync it’d only be for one interval of the workout but the overall interval and workout lengths would be correct.

Another option might be to stop redrawing the chart whenever we get out of sync until things are back on track.

I’m happy to run a debug build if that’d help track it down. Occasional whacky interval times are still better than my garmin crashing in the middle of a workout :stuck_out_tongue: