Trek Central

Does a lot in one app, but the best part is being able to customize in great detail how my electric motor works, so I can turn it right down for long range and a slight boost, all the way up to the 300W juggernaut for steep hills. The map while riding works well, easy to pinch and rotate. And the database of rides is helpful. Thanks Trek for fixing all the bugs over the last few months.

I’ve had this bike for a little over a year and it has been fine, everything except this app. The developers should honestly be embarrassed. It was horrible before this update, now the bike doesn’t even connect to the app. It used to take anywhere from 2-5 minutes HOLDING COMPLETELY STILL for it to connect to the app. Even then, it would disconnect MID RIDE 25% of the time, it’s horrible. What’s worse, when the bike is attempting to connect, and you’re riding it, it stutter stops and sometimes turns off, which is incredibly dangerous. I’m writing this while waiting in a line, not 20 feet from my bike and it couldn’t find it anymore, so I don’t even know if it will work anymore. To the developers, maybe ride the bike to see how awful your app is, before patting yourself on the back. It’s been almost a year before this update rolled out, nothing between then and now, and nothing that was bad was fixed. You added nonsense to the app, only over complicating things. Fix the connection issues, the disconnection issues (basically the safety issues, which don’t exist on regular bikes). This app is pathetic.

I use the app with my ‘23 domane+. I actually like the app overall. But… While riding and switching assist levels, the app will just randomly shut down. It’s not consistent, about 10% of the time. When I restart, the current ride picks back up, with one major issue. It adds miles to the ride. I’ve had it add 1 mile, 5.2 miles, 10.7 miles…. It’s really random. The actual bike odometer does not get the miles added, just the current ride/trip odometer. This obviously then skews the other stats (avg speed, etc.) for the ride. Given you are interfacing with TQ, idk if the bug comes from TQ somehow on reconnect or if you have some major logic issue on your side when reconnecting. I have the latest version of the app, 2.5.