This too bad… I was really hopeful we had it resolved. Maybe it could be related to power match, I am not sure if we have tested the timer with power match. Thanks for the detailed feedback, maybe it is performance hard to say. We will keep going until we get this resolved.
Ok we found a really slow Android device and it has serious timing problems so it seems that it performance related. This is great news meaning since we can see the problem we can fix it. Hopefully quickly.
Ok, it seems we have some performance improvments that make it work correctly on a 3-year old $89 Amazon Fire tablet running Android 5.1. Yesterday it had timing problems on this device and today it is working correctly at 1hr right now (should be 90m in 30-min from now). We should have a new build today that will hopefully put this issue to rest.
Ok version 1.8.8 submitted to Android store for beta users. It has a couple of small visual bugs that I don’t think anyone will find, but they are not very important. We will resolve those and then try to push this to all users.
If any beta users can test that it would be great. Hopefully today we will push it to production also.
I rode about 1.5 hours on 1.8.8 today. Didn’t notice any issues with the app. I didn’t have any issues while app was running in foreground before, so not sure if I would have seen anything different anyways.
I did catch a visual bug while the workout is paused, but couldn’t find any other issues (granted, I didn’t try and find many other bugs).
Basically, this is what the screen looks like while the workout is paused. If you tap on the screen to change the view, it will show either a little bit more of your workout. I think it just has something to do with the view area not resetting to the full workout view when a workout is paused. Should have taken more screenshots or a video… sorry about that
Yes this is bug in beta version that is fixed already in next beta version. Good to hear, thanks for feedback
I had a strange experience on the Android app on my phone today. It was a 90 minute workout, and at about the 1-hour point I flipped over to Audible (TD still running) for about 5 minutes. When I flipped back to TD, the interval time remaining had lagged behind. It seemed to be trying to catch up - it was running at maybe 2-3x normal speed. And after a minute or so, it did catch up and the app was tracking the workout normally.
Then a second strange thing happened - I received a phone call, which I dismissed. When I switched back to TD, it appeared to have reset my workout - it was back at the start of the workout with the Ride now button showing. I clicked Ride now, and then things went kind of crazy - zooming the workout chart in and out, pause/resume button alternating, as if the app were controlled by automated testing software. I restarted the app and the workout, and it appeared to be working, but it wasn’t controlling the trainer. I tried toggling erg/free ride but I was getting only around 50 watts from the trainer.
I’m not sure if this is related to the performance issues, but I would be happy to beta test.
Wow, that is the strangest combination I have heard of. Yes, regarding time catch up, this is how the app works. There is no such thing is accurate time for doing events like this, so you have to fake it and adjust and if it gets way off then we play catch up or make a large jump, usually the catch up is only milliseconds so you don’t notice but when it is way off you do. Other companies/products just have better (or more mature) code so you don’t notice.
Our new beta version has some performance enhancements and improvements to timing but we still have one more “killer performance” version that will be ready for beta next week.
The answering the phone is the strangest one, I can’t imagine what that is. You can join the beta group in the Google play store, just go to the bottom and it should let you join. I know the new beta is better than the current public release version.
You can also join the beta discussion group here.
I’m happy to report that the latest beta version (1.8.9) has finally and truly squashed the stretching time bug. Thanks Alex and crew!
Yeah!!! So happy to hear. One user still has a problem with it on a slow device but we think we will have that resolved in next version that will be much faster performance.
After the latest update I’m now seeing this. Last 15 min of the ride took much longer. I can provide details if needed. From trainingpeaks:
TD 1:28:10 TSS 77
Garmin Fenix 6 1:38.29 TSS 89
Garmin 520 1:38:23 TSS 89
Started in that order
App on iPad
I also saw this day before yesterday. Same setup
Thanks John, we will look at it and get it resolved ASAP (I hope).
John, we have tested with lots of devices and can not duplicate this. Can you provide more insights? Are I know you said iPad but which iPad? What trainer are you using, any other devices? What version of iOS? Are these using auto-extend? Did you do any merging of workouts? Can you send me a link ideally to your activity in trainer day or to the workout you did? Are you using power match? For example if you put it in the background for extended periods of time? It’s possible our app auto paused at some point but garmins did not? You could send me Garmin TCX (or fit file).
Below is using test mode in our app but we are getting the same thing connected to devices.
Thanks for the attention to this. I really enjoy the App. The problem grows with the length of ride. My energy goes in the opposite direction. The ride I just finished (details later) had the last 2 min last for 2 min 53 seconds.
- Stages SB-20 bike
- iPad is iPad mini 2; software version 12.5.3; 4G of 16G memory free
- Garmin 520 bike computer only recording sensors
- Garmin Fenix 6S Pro watch only recording sensors
- Version 2.1.10
- Enable Auto-Extend Cooldown enabled
- Auto Pause enabled
- Power Smoothing 0s
- Power Match enabled
- All other Options not enabled
- Always in foreground with no autopause
- All straight from the Library without merge and a few seconds auto-extend on Brad+1
- Townsend TD 1:30 Garmin 1:39:18
- Chea +1 TD 1:28:10 Garmin 1:38:23 (stopped before end of workout on TD)
- Brad +1 TD 1:15:23 Garmin 1:20:54
As I said it grows worse as the ride proceeds
- Chea +1 it was clearly slowing towards the end so I
- Took laps at interval starts with Garmin today on Brad +1
TD time TD Segment time Garmin Lap time
Files (first file is TD file from TrainingPeaks; second is from Garmin 520 or Garmin 520 via TrainingPeaks)
2021-07-05 13-42-06 - Day 19 - Townsend.tcx.gz
2021-07-07 13-35-20 - Day 20 - Chea +1.tcx.gz
2021-07-08 14-07-03 - Day 21 - Brad +1.tcx.gz
How do I get these files to you?
Great thanks for info. We will figure out the problem. It might be performance problem of iPad Mini but not sure (related to our app, maybe the performance is worse in latest version is why it is affecting you but previously our app auto-corrected itself, maybe this auto-correct stopped functioning correctly). I have an old iPad mini I can try.
email@example.com is best way.
I see your last workout
You like pain…
two more rides configured as above
Peti TD 1:00:00 Garmin 1:01:27
Diamante +1 TD 1:15:00 Garmin 1:24:10
so today I left everything the same and switched to Android Phone for TD configured the same as the iPad.
Sierra +1 TD 1:15:01 Garmin 1:15:01
So it is definitely the iPad mini 2
over the next few days I’ll experiment with the iPad config.