Horrible performance on Galaxy Tab S5e and Tab S8. Very slow to respond to clicks and now unable to pair the power meter. Was working great until a couple weeks ago. Wasting so much time pre workout just to try and get the app to work.
Did all the basic troubleshooting and OS is up to date. Actually regret reinstalling the app since now I can’t get it to recognize my power meter on the S8.
The TR beta app with the fix for Android is currently under review for release.
For anyone still experiencing a slow app at the moment, please email support@trainerroad.com and we can send you a development build of the TR app in the meantime while the review for the beta app is completed.
@Velog8or if you haven’t reached out to TR Support already, shoot them an email and they’ll hook you up!
The Beta App that should help alleviate slowness in the TR Android app is now live!
This beta build should be faster than the current production app that’s out at the moment. Our engineers mentioned that there will be more performance updates for the Android app on the way!
Feel free to let me or TR Support know if you need a hand getting the beta app installed or if you have any other questions.
OK, I saw the note about the new beta release moments ago, and did some quick testing:
39 seconds total to launch TR and get to the main screen, with Refresh wheel icon still spinning.
about 1 minute total until the “Refresh” icon stops spinning.
Changes between the Calendar & Career pages take over 5 seconds each.
Changes to other pages (Devices, Workouts, etc.) are 1-2 seconds.
I updated to the new 07/21/2023 beta, then rebooted my phone:
25 seconds to launch TR and get to the main screen, with Refresh wheel icon still spinning.
1 minute total until the “Refresh” icon stops spinning.
Changes between the Calendar & Career pages take over 5 seconds each.
Changes to other pages (Devices, Workouts, etc.) are 1-2 seconds.
So the initial launch time drops significantly from 39 seconds to 25 seconds on my Galaxy S9, which is great.
But the “Refresh” and other page changes seems to be unchanged.
I don’t know if the refresh operation causes any part of the related slow page swaps, Career to Calendar and back specifically, but it gives the appearance that the app is still not ready despite being “loaded”.
34% reduction for initial time to open is clearly better in my case. Sure, I’d love it to be faster and hope they still aim to improve, but this is progress and I am happy to have it for now.
ETA for reference, open times for other apps on this phone.
I am on the iOS (iPhone) beta. The problems I experience are:
the app is crashing. I navigated between the career and calendar pages 5-10 times without waiting for the refreshes to complete, and at some point the app just closes. Could it be that you are starting new background tasks for each page switch without cancelling the old ones? And then you run out of resources or do a change in the background which causes the other thread to crash?
the UI becomes unresponsive or blocked. I can click on a workout or some other item, but there is no response. I was able to reproduce this by 1) opening the app, 2) going to the Calendar, 3) opening and closing a calendar item 14 times. This suggest that there is some kind of resource leak happening each time you do this action. Note that the calendar refresh was spinning in the background the whole time.
Could the problem be two things: 1) slower response times for your APIs and 2) resource leaks causing multiple refreshes to run in parallel. Because of the slower response times the resource leaks (that might not be new) are more frequently becoming a problem as the background jobs are easily created faster than they are completed?
In my case it is the calendar that takes forever (50-60 sec). It looks like it downloads the the whole calendar instead of just a part of it. This is strange, because when you scroll the calendar it will show “pull to load more…”
I also see that if I scroll back to end of 2022 my activities (iPhone) does not show any graphs.
App crashing had become significantly better, but following the latest update I had two crashes. A major positive was the app waited to see if I wanted to resume which both sped up getting back in, and meant I didn’t have to go delete the part ride from Strava/Garmin.
Has there been a backlog or blockage or something on the server end in the last 24 hours?
I have a friend that is trialling TR after my recommendation and he’s been having a really average experience. He’s on mid volume and all his workouts are ~45min long. I tried to have a look on his phone yesterday to see whether it was a settings thing/to do with his plan builder inputs, but his iPhone app wouldn’t load all the pages properly.
Hey everyone, I’ve got some good news! We’ve made further updates to our Android Beta App, which should help to speed things up even more than the one released last week. To get access to the Beta app, you’ll first need to follow the link below.
From there, you can select Android and enter your email address. We’ll then send you further directions as to how to find the Beta app in the Google Play Store.
If anyone has basic questions about our Beta Programs, you can check out our FAQs Support article below, and as always, feel free to reach out to support@trainerroad.com for more assistance.
@mailman sorry to hear that you still had a couple of crashes after the last update. Give this new version a shot to see if it helps. As for your friend on iOS, I don’t think that we’ve had any issues that would cause this in the last 24 hours. Could you have them reach out to support? Then we can take a closer look at their account and figure out the issue.
@Dougal.Doughnut, give this a try to see if it helps to get things running smoothly for you. If you’re still having issues, I’d like to take a deeper look at your account. We need to put these types of changes into Beta first in order to get some data back regarding how things are working for a number of our athletes before pushing the changes into production.
Thanks Eddie, I’ve just downloaded the latest Beta to the phone. Hopefully the tablet downloads it and is stable. It’s weird as it had been fine recently again.
As for my friend, I’ve suggested he contact support, I don’t know if he will though.
For him I have been trying to click the training plan link, and on his phone it goes blank, to add to the confusion mine goes to a spinning wheel too.
Hard to trouble shoot his training plan and whether it’s simple input stuff or not.
I updated to the new 07/27/2023 beta, opened the app just to get past the initial update info screen and closed it. Then I rebooted my phone and recorded the following:
About 20 seconds to launch TR and get to the main screen (tested 3 times).
Change between Career and Calendar page take about 2-3 seconds each time.
Changes to other pages (Devices, Workouts, etc.) are 1-2 seconds.
A bit more improvement for main open (20s vs 25s on the prior beta), but still slow compared to other apps on this phone.
A quick recap of my recent experiences with the iOS-app.
In the month of July, I had an awesome 6 days cycling vacation in Wales (which I planned in the TR calendar as an A event). Before this trip, everything went smooth in the TR app. But afterwards, the app took forever syncing my ride data (because of the six added outdoor rides?) (and crashing on multiple occasions). Starting a workout was a real pain in the …
I reached out to TR support (who were quick to respond, I must say!). At first the usual suggestions : check wifi connection, delete and reinstall the app, … None of which helped. They even suggested to delete my outdoor July-rides (my A-event), which I wasn’t inclined to do. I mean : the solution should never be to delete rides, right?
I managed to find a somewhat workable solution : first sync the data on the TR-app on my Macbook, delete an reinstall the app on my iPhone. At first the iOS-app crashed again, but less so.
A couple of days ago, TR support contacted me with the news that an app update was released. I updated the app to the latest version.
Hooray, the app was quick to respond and didn’t crash anymore. But my enthusiasm quickly went away : suddenly the connection with my Garmin Fenix watch (which I use for HR-reading) didn’t work properly anymore. The connection ‘dropped’ constantly. The app even tried to make a connection with a Tickr, which I don’t even use anymore and is lying somewhere collecting dust! Result : a workout with a completely messed up HR-reading…
Another suggestion from TR support : try the beta version…
We did a slightly tweaked version of the Wales section of the GB Divide and rode from Bristol to Liverpool. We’re a bunch of slightly elderly riders (50+), so we didn’t go bikepacking but stayed in hotels along the way.