@iagouaros Try to disable rerouting feature and test. In past I opened a topic with Wahoo support and same as you I described them problems and uploaded screenshots but it came to nothing. After many months of investigation of this problem I found that rerouting causes all of it.
Hi @koval1021,
Thank you very much for the tip and for sharing your experience!
I will definitely try disabling rerouting on my local/familiar routes to see if it makes a difference. However, as a long-distance brevet rider, rerouting is a feature I genuinely need when navigating unfamiliar roads.
If rerouting is indeed the root cause, Wahoo should absolutely fix this algorithm in a software update. Isn’t there anyone from Wahoo monitoring these forums to address such critical cycling computer issues? A flagship device shouldn’t force users to disable essential features just to achieve acceptable battery life.
Thanks again for your help!
Yes, rerouting is very important feature especially for unfamiliar regions. Im also surprised that they haven’t fixed these problems for a long time.
I’ve recorded battery % used per hour over several months and found that loading a route to provide navigation increases battery discharge rate. This is fairly obvious as more processor activity needed. I also expect going ‘off route’ adds to processing load.
My rides are typically 30 to 60 mile, 4 hours to 6 hours (Roam 3 running during coffee/ lunch stops). I have a lot of sensors, radar. Live tracking etc. 95% rides are planned in Komoot with route guidance by voice.
I typically experience 3 to 4%/h, so this extrapolates to 25h run time. However, I’ve never tested for this duration !
I have a theory that route planning (Strava, Komoot etc) have a role to play. Internet / AI searches suggest different vector segment sizes, Komoot more efficient less resolution. Search recommended output from Strava using .FIT rather than .GPX.
This perhaps suggests that a very long route, with large .GPX file and frequent ‘off route’ excursions all add up to more battery drain.
However, there are some reports that when Wahoo replace a Roam 3/ Bolt 3 device, the problem is solved!
The really annoying aspect is the lack of explanation or guidance from Wahoo!
Hi,
Thank you for such a detailed breakdown and analysis!
While your theory regarding file formats, segment sizes, and processing load makes a lot of technical sense, my real-world experience strongly points to a hardware issue in my case rather than a route-file limitation:
Month 1 (September 2025): On a 12-hour brevet using a Komoot route file, active rerouting, and my full setup of sensors, I finished the ride with 55% battery remaining.
1 Year Later (September 2026): On a 13-hour ride using the exact same setup (Komoot route file, identical sensors, active rerouting, identical settings), the battery collapsed down to 8%, almost shutting down mid-ride.
Since both rides shared the exact same conditions, software environment (Komoot), and routing features, this massive drop from 55% to 8% over just one year proves that the device didn’t perform like this from the beginning. Something has clearly degraded or broken internally (likely power management or the thermal sensor issue I mentioned).
It’s just frustrating that Wahoo isn’t more transparent about these failures, especially when a simple warranty replacement seems to solve it for many users!
Thanks again for sharing your thoughts!
Hi everyone,
I wanted to update you all on my ongoing communication with Wahoo Support regarding the severe battery drain and high-temperature issue on my ELEMNT BOLT v3.
Wahoo Support (Jack) replied to my warranty claim stating that, based on the information provided so far, they suspect this behavior might be a software/firmware issue rather than a isolated hardware defect. They have asked me to enable device usage logs on my unit so they can collect data during rides and investigate the software activity causing the rapid discharge.
Here is how I responded to them:
Rerouting Bug Highlighted: I specifically informed Support about our discussion here on the forum, highlighting that many users are facing the exact same issue on both Bolt v3 and Roam 3 (referencing threads like “Elemnt Roam 3: battery life drastically reduced after update”). I explicitly pointed out our consensus: following a pre-loaded route with the Rerouting feature enabled appears to lock the processor into high usage, overheating the unit and causing rapid battery drain.
Brevet Season Ended: Since my official long-distance season has just ended for the year, my next multi-hour test rides will take place in the spring.
Warranty Protection: I agreed to assist their engineering team with log collection, provided they give written confirmation that my warranty coverage will remain fully intact and extended if necessary until a resolution is found.
I’m now waiting for Wahoo Support to send instructions for log collection and confirmation on the warranty terms.
I will keep this thread updated as soon as I hear back from their tech team or receive further insights on a firmware fix.
Thanks again to everyone who shared their experiences and findings regarding the rerouting feature!
@iagouaros I do Brevets as well and have had no issues with battery life. Several 100ks and 2 200ks this year and am following a route and also using rerouting as well. I have seen no overheating issues.
Perhaps the rerouting is contributing to your specific issue but I don’t think based on my experience that it is a universal issue.
Log file sounds interesting. A long time ago I commented about ‘trace code’ to help identify the problem. Sounds like there’s now a function in current firmware that can be turned on to enable logging Possibly identify software modules that are hogging the processor to localise root cause.
Positive sign that the problem is being investigated by Wahoo.
BTW. Whilst re-routing and route navigation could be battery drain culprit. Don’t forget another Roam 3 user found phone BT connectivity to increase power drain.
Hi everyone,
Just a quick follow-up on this: for anyone still struggling with battery drain, I strongly recommend opening a ticket with Wahoo Support and asking them to enable device logging on your account as well. The more of us collecting and sending data, the faster they will pinpoint the root cause.
Also, regarding the discussion on what triggers the battery drain: in my specific case during those long brevet rides, my phone was NOT connected via Bluetooth at all. However, I was following a pre-loaded route with the Rerouting feature active.
This seems to confirm that the issue isn’t strictly tied to phone connectivity, but rather to the navigation/rerouting processing cycle itself.
Let’s keep reporting our findings to Support so they get this sorted!