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.
@Dougal.Doughnut The “Warming Up Trainer” and “Loading Calendar” messages have always been in the app – not trying to use any smoke & mirrors here!
Here are a few things to check on your Android device to ensure you’re running at max performance (@mailman these tips may be helpful for your friend as well):
Make sure you have at least 2GB of free storage on your Android device (instructions on how to check this from Samsung here).
Close out all apps that may be open in the background.
Ensure that power saving mode is toggled off under your battery settings.
We also have a group of engineers dedicated to working on app performance issues on Android at the moment, so we hope to continue to release improvements to the Android app.
@Peter.V iOS issues seem to be different from the Android problems described in this thread, so our support team will reach out to you regarding iOS troubleshooting steps.
I have to say, I never saw the wording until the latest update either. I’ve watched that screen many times and since it took over 30 seconds each time, I had plenty of opportunity to see it. It was just the little red/black spinny wheel other than the oddity below.
About the only text I’ve ever seen prior to the latest update was something like “Updating app…” or similar content. And that happened nearly every time despite only seeming to be relevant on the first launch after an actual update. But I saw that repeatedly in my testing, so it was something that was consistent for whatever reason.
Perhaps it was always programmed to be there, but for some reason I never say it any of the prior versions.
One thing to check… the bluetooth accessories are all running on 2.4ghz. I recently had bt dropouts/instability on a new tablet and switching the wifi to a 5ghz channel appears to have fixed it. Is it possible in your troubleshooting your wifi setup changed?
@Dougal.Doughnut@mcneese.chad Whoops!! You’re right, those are new messages that appear – we got that mixed up on our end, sorry for the confusion on that point.
We checked in with engineering and those messages are meant to describe what’s happening in the loading process more accurately. This should help us determine which part of loading the TR app takes the most time to complete so we can focus our attention there for further improvements.
We are changing the phrase “Warming Up Trainer” to “Starting Sync” to better describe what’s happening in the background of that loading screen.
That said, @Dougal.Doughnut, we’re really struggling to help you out. A lot of your posts recently in this thread give the impression that you’re not really interested in trying to get to the bottom of the issue but rather criticize TR and spread negativity.
I understand this is a frustrating experience for you, but we’re still dedicated to getting these issues fixed. It would be really helpful for us, and anyone else experiencing problems, if you could work with us on what you’re experiencing so we can get these issues resolved rather than ignoring or entirely dismissing our suggestions.
I am running TR on a Google Pixel 4, Android 13. The app had gotten really slow over the last few months, similar to what others describe.
Yesterday signed up for the beta program. Today I got to use the beta for the first time.
I see significant improvement. Buttons are now responsive again and next page loads within a second or so. Initial startup still takes a bit of time (10 seconds(?), But down from 20-30 seconds.)
Great news on that. I also came to the forum looking for answers because the app has become very, very slow. 30s+ on opening until anything appears, very unresponsive UI in general, often taking 5-15 seconds for anything to happen when I click.
I wonder if UI responsiveness testing is part of the pipeline? Because then it should be relatively simple to figure out where things started going wrong.
I took a look into your account and noticed you were using the standard production app. While the production app is getting improvements rolled out to it, the TR Beta app is getting updates even sooner than the production app does. It would be worth downloading it and giving it a try to see if your app’s performance gets better!
Our developers have logging in the app that allows them to track where to improve app performance, so we’ll have more good stuff on the way!
This is just a heads-up that we’ve rolled out a few more updates to the Beta app that should help improve performance on Android mobile.
For anyone who might still be having issues, don’t hesitate to reach out on this thread. We’d be happy to help!
Again, 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.
As per Zach’s advice in the past, uninstalling the app and installing the freshest version definitely makes a big difference to performance.
I don’t know how many “updates” to just do before you should go through the uninstall cycle. It’s a bit of a nuisance as you have to log in etc, and it does the introduction, but it obviously clears a bunch of unneeded data .
The app is still not as fast as it used to be, but I think it is doing more things as well.
I’ll come back with another grumpy post if it drops back to routinely crashing mid workout - that’s worse than a go-slow…
I was having this for over the last year. Anything over an hour had a decent chance of dying. Even if it didn’t crash, the UI would lag more as it went on. Watching the interval clock it would skip seconds pretty regularly, especially around resistance changes. Finally bit the bullet and got a new tablet with more ram, which seemed to be limiting factor. Guessing as the workout data builds up in memory the tablet gets stuck in a memory garbage collection cycle, so the cpu spends more and more time on it. Eventually just can’t allocate a block of memory big enough so the app crashes.
I’m a little curious if my old tablet will be functional again after these perf improvements are completed.
.