Continuous Press, Quick Intensity Adjustment [Feature Request]

[AldridgePrior]

Thread resurrection…

@Crownan

The point is, if I press and hold the intensity adjustment, as per the implemented feature request, it doesn’t stop when I release but lags and keeps adjusting for longer than required.

I’ve not used the Intensity adjustment feature for eons, but have begun doing so again the past couple of weeks while tacking a bit of Endurance onto the end of workouts. And what I’ve found is that the long-press adjustment is massively laggy causing it to then hugely overshoot, just as you wrote a year ago, rendering the feature largely unusable…

Could it be my device? Perhaps, but I’m running a Pixel 3a, so not the slowest device by far, and with no apps other than TR running; tried phone reboots and TR app re-installation, to no avail.

Prior to me contacting TR support, out of interest are others here using this long-press feature OK, without any lags/overshoots, at the end of their workouts? Or are the posts towards the end of this thread all commenting about laggy/overshooting behaviour the norm?

[tomclune]

Last year when I used it I found the lag went away when I got a new iPad. So it may well require peppy HW to be usable in practice.

[AldridgePrior]

@patrickhill

Has anyone noticed that intensity adjustment feature is snappy, quick, and useful in the beginning of a workout, but becomes super laggy and slow near the end (over 1 hour)?

For today’s workout I used the “continuous press” Intensity adjustment at the beginning of my workout and at the end…

It behaves just as you wrote back in January: function behaves correctly near the beginning of the workout, while it behaves horribly laggy/slow/overshooting by the end of the workour (eg. ~1 hr time).

I cannot think of anything other than a bug to explain that discrepancy in behaviour: if it works OK at the beginning it should also work OK 1 hr into a workout; device processing power alone doesn’t satisfactorily explain that change in behaviour. While device power might be an additional factor (in that very powerful devices may help mask the underlying problem) it looks pretty clear cut as a coding error.

Considering this was flagged up here well over a year ago, I’m surprised it’s not been fixed. Maybe nobody told TR support? That’s what I’ll be doing.

[mcneese.chad]

@AldridgePrior

Maybe nobody told TR support? That’s what I’ll be doing.

Thanks for doing this.

The forum can be useful for a range of items, but nothing beats contacting support directly when it comes to apparent bugs and such, IMO.

[SarahLaverty]

Hey @AldridgePrior!

@AldridgePrior

Could it be my device? Perhaps, but I’m running a Pixel 3a, so not the slowest device by far, and with no apps other than TR running; tried phone reboots and TR app re-installation, to no avail.

I don’t believe your device is the issue. It looks like you are on Android version 12.32 with your Pixel 3A which is above the required Android 7. You can find our minimum system requirements here.

These steps were a good idea, and the first I would suggest to an athlete running into an issue like this.

@AldridgePrior

function behaves correctly near the beginning of the workout, while it behaves horribly laggy/slow/overshooting by the end of the workour

We have a bug report open for this, so I will add your information to this report so that the team have more info to work with. Cheers for the info- it helps our developers!