I returned to roam 3 after some time with Karoo, but didn’t ride long enough to be bothered…but finally Karoo 3 battery isn’t so bad 
No, I haven’t returned it yet. I guess I still like the overall user experience too much for that.
I think dinpin has the right hunch and I’m still testing: as soon as the Roam tries to connect to the phone (if the phone’s Bluetooth interface is enabled that’s enough) it may trigger increased power consumption, even if the Wahoo app is not running at all. I now did some rides and always made sure to disable Bluetooth on my phone before I turned on the head unit and power usage always was normal.
Of course, the same still applies: if this isn’t a fluke it’s a clear software problem and Wahoo needs to investigate and fix it. If they actually listen they should have all the data that they need for quite some time already. I’ll watch the firmware updates for some time, if they don’t address this soon I’ll try to return the unit for sure.
Any chance you have a different phone to try. Just a possibility phone is somehow forcing Classic BT comms or other comms issue?
Ok here is my experience and observations with this problem.
Device: Roam V3
For the first time I noticed that in January 26.
Doesn’t matter if my device is connected to phone or not. This bug happens very often ONLY when I follow the route. Never happen during ride without loaded route. It starts to happen when wahoo is auto-paused or paused manually during stops.
What happens exactly? Roam starts to drain battery very fast. Device is overheated and shows outside temperature over 10C more than actually is.
I think from software perspective - there are multiple errors and something is looped. This causes processor to overheat then temp shows incorrect values then battery drains fast.
Temporary fix: When bug occurs I restart my device during traning. Roam recovers ride, everything back to normal and I continue my ride. But still it may happen again.
Route import and navigation impact on processor workload is plausible. I noted about 1.5%/h less drain when not riding with nav guidance.
I always plan rides with Komoot, as a cloud linked app and have no drain problem. Always possible that something in the imported gpx from other route planning app is the trigger?
Yeah, nope. That’s not it either. Last weekend I did two rides on Saturday. First ride was fine (the expected 5% per hour), second ride dropped from 80% to 20% over the course of five hours, even though I boosted the unit by about 7% in a mid-ride break with a powerbank. In both cases I disabled Bluetooth on my phone before the ride and in both cases I was following a track synchronized from Strava.
Edit: and yup, the reported temperature was much higher than air temperature, so it’s definitely high power consumption and not a flaky battery.
Hi all,
I was reading through this thread as a recent Roam 3 purchaser (mid July 2026 from Lordgun) and wanted to share some of my recent findings.
Yesterday I completed a ride of 8h:31m and an elapsed time of 10h:13min. The Roam finished the ride showing 73% battery life.
The Roam was on the entire time with auto paused trigger for coffee stops and lunch breaks.
Following some of the advice here I turned off wifi, I disabled blue booth before turning on the device, and I had back light off (which was fine even when riding through a thunderstorm). I was following a loaded route and had a heart rate monitor paired.
Needless to say I’m pleased with the battery life though I can appreciate I ride with far less sensors than the average rider here.
Hope this is useful.
You achieved 2.6%/h which far exceeds Wahoo performance claim.
I average around 4%/h with phone BT operating, Wahoo App and live tracking. My phone WiFi always running for automatic reconnection with pre-associated access points, but no hotspot enabled.
You mentioned WiFi (phone) turned off. We’re told that Roam 3 doesn’t enable its WiFi (for large file/firmware update) during an active ride.
My Roam 3 connects to my home WiFi, I can see a brief connection from MAC address that begins b4:6f:2d:16 etc when, under Roam 3 settings, I check for firmware update.
I’ve often wondered if users with rapid drain are coupling to a WiFi hotspot on phone and somehow Roam 3 WiFi gets enabled during a ride?
Roam 3 ride total duration 3h 44min, started with battery fully carged 100%, end of ride 96%.
This ride battery left on charge for an hour after reaching 100%. Ride with cadence, Tickr heart, wheel rotation sensor, Varia RCT715 camera Radar, Creo 2 ebike and SRAM etap gears and wahoo App running live tracking on Samsung S20fe. Backlight set to Auto.
This ride I hadn’t loaded a pre-planned route, so no navigation guidance but GNSS still active to record the route.
Significant observations:
Remained 100% for 1.5h from start.
Drain much lower without navigation, when I have voice guidance enabled.
I have radar bleeps turned on loud and a lot of activations.
Ii’ve never had a 20h ride but it seems possible battery would last
That’s an interesting observation. Wonder how much routing adds to the drain, separate from any speaker stuff.
Hi Richie,
Several rides now and %/h about 50% with no route navigation. Voice turn by turn instructions probably about the same drain as bleeps. Either voice or bleep will only be a small part of drain.
Navigation and re-routing will be processor intensive.
However, even when riding with navigation our battery drain significantly less than the massive drain reported by some users.
I use Komoot for planning, maybe different planning tools have an impact. Differemces in GPX files generated??
PS. Just Wiki researched this point. Strava high density, Komoot has agressive smoothing. GPX XML schema the same but waypoint density could differ significantly, especially longer routes. Would be interesting to compare GPX output file size from each route planner. Wiki comments number of waypoint vectors explains difference in predicted distance!
PPS. Further research and overload of GPX imported from Strava is a known issue. Apparently solution is to set Strava output to Wahoo as .FIT file. Maybe worth a try to see if it solves battery drain?
Has anyone found a solution? I’m at my wit’s end. I bought a Roam V3 to replace my V1, and the battery life has been incredibly inconsistent. I tried to troubleshoot with Wahoo support but they were not helpful, suggesting I connect fewer devices (I only had 3 devices connected) or not use navigation, LOL. After spending over a month going back and forth with Wahoo, they sent me a replacement V3. Took it on a ride this weekend and…as I expected, it drained from 100% to 50% after an elapsed time of 6:50 minutes. The fast draining started after I stopped at a cafe and it auto-paused. I was briefly far away from the Wahoo. During the ride, I had Backlight off and only connected to 2 bluetooth devices (HR and Power meter). I was using navigation from a route synced through Strava.
Halfway through the ride I noticed my phone battery was almost dead, too, and I couldn’t get the Wahoo app to connect to my Wahoo to turn off GPS re-routing. Putting my phone in airplane mode seemed to slow down the battery drain, so I am curious if the theory of something to do with bluetooth is causing the drain.
Once I got home, I had to completely restart the Wahoo in order to connect it to the Wahoo app and sync my ride. My phone is an iPhone 12 mini running iOS 26.6.
For contrast, I ended up using my roam v1 for a double century because I knew I could trust the battery. Elapsed time of 13 hours and 30 minutes and I ended the ride at over 50% battery life (backlight off, navigation on, 3 bluetooth devices connected).
I’ve had ONE ride with the v3 where the battery worked as advertised (4% per hour)–started at 100% and was down to 63% after 9 hours of being on. The only thing I can think of that was different about this ride was that I had driven to the start of the ride and turned my wahoo on outside of any home Wifi. Looking back, I was also using a route from RidewithGPS for that ride, too.
I’m really frustrated that Wahoo hasn’t been able to provide any meaningful troubleshooting support. I will continue to troubleshoot by trying Ride with GPS routes vs. Strava, as well as bluetooth, but curious if anyone else has figured out a reliable solution.
Nope, still the same issue on my new Bolt v3. What seems to slow the drain is what someone else detailed on this forum earlier — turn your phone’s Bluetooth off, and then turn on the Wahoo unit, while leaving Bluetooth off for your entire ride. Still drains at an alarming clip though, but better than nothing. Personally, I’m going to be getting a Garmin unit, since Wahoo seems to have no proposed fix for this obvious issue that multiple users are experiencing.
Just a thought. You mentioned phone and Roam 3 far apart at a cafe. BTLE will increase Tx power when weak Rx from other device detected, affecting phone and Roam 3 battery drain. Maybe continues in high pwer when they get near again?
At cafe stops, I always take Roam and phone in my helmet for security! Ok, do get a few squeaks from Roam but I don’t care about odd looks 
Another thought, are your Strava routes transfered as .FIT. Apparently, smaller output file compared to .GPX, less waypoint vectors, less processing. I use Komoot apparwntly less waypoints cpared to Strava.
Notes from my most recent ride: I used a RideWithGps route. Started ride at 50% battery when turned on. Elapsed time: 2 hours 02 min. Moving time: 1 hour 25 minutes. Ending battery: 41%.
Backlight was off. Auto rotate and reroute on. Wahoo wifi was turned off. I was connected to my power meter and HR. I noticed when I flipped through the screen that the Wahoo was “searching” for the power meter on my other bike, even though I was away from home. Hm. Didn’t pay attention to whether I had the wahoo app open or not.
In the 10 minutes of getting home, stopping & uploading my ride, and writing this, my Wahoo dropped to 39%. That’s right, it dropped 3% in 10 minutes by just being on. It was still connected to my HR monitor and when I looked at the pages, it was searching for both my power meters.
After this ride, I’m not convinced it’s a RidewithGPS or Strava issue. I feel like it’s definitely something to do with bluetooth, where there’s some software error for constant searching for bluetooth devices. On my V1, I can walk away from the device no problem at a cafe for hours and it’ll only lose 1 or 2%, and I have the V1 paired with devices on multiple bikes.
Is there anything we can do to adjust bluetooth settings or is this a Wahoo bug?
If the excessive power drain is due to BT or Ant+ datacoms, I think sensor polling and transfer unlikely the culprit. BTLE allows short data packet size amd that’s all that is needed for power, heartrate etc.
The small battery in the sensors last years and generally no upload from Roam 3, just a poll to request data.
The transfer of larger data is only possible with the connected phone and Wahoo App, or direct to WiFi.
On Android, through developer options, it is possible to enable 'Log BT HCI traffic data". I’ve tried but couldn’t find the file btsnoop_hci.log file.
Has anyone on this Forum done this?
After some tests I can confirm that for me Rerouting is the main problem here. Rerouting causes all those overheating problems = battery drain. With this feature disabled I don’t have any problems. Developers should focus on rerouting feature and check for infinite looping that causes processor to overheat and battery drain.
Be wary of quickly jumping to conclusions about the cause of high power consumption. In my experience it’s just random and does not have a specific cause. A few rides are not enough to confirm anything.
FWIW, Wahoo has now replaced my device and the new one seems fine, but I’ve only done a couple of rides, it’s too soon to say that the problem is fixed for good.
Hi everyone,
I wanted to share an issue I’ve been facing with my ELEMNT BOLT v3 (purchased about a year ago) to see if others are experiencing the same hardware/software defect, and to document the actions I’ve taken so far.
As a long-distance / randonneur cyclist, battery reliability is critical for me. Here is what happened:
-
Initial Performance: On September 20, 2025, during a 12-hour brevet ride, the device finished with 55% battery remaining using my standard paired sensors (Radar, HR, Speed, Cadence). I was extremely happy with its performance.
-
Current Issue: Over the past few months, the battery life has collapsed. On a recent 13-hour ride with identical settings, the battery dropped down to 7–9%. On previous rides (e.g., May 31, 2026), I was forced to charge it mid-ride with a power bank to avoid a shutdown.
-
Faulty Thermal Sensor: During these battery drain episodes, the internal temperature reading is constantly reported at ~35°C, even though the actual ambient outdoor temperature is around 20°C. The device seems to suffer from abnormal thermal readings, which trigger excessive power draw.
Troubleshooting Actions Taken So Far:
-
Battery Calibration: Performed a full cycle (fully drained the battery until shutdown, then charged it uninterrupted to 100%). Result: No improvement.
-
Settings Check: Verified that backlight is on Auto, dark mode is off, and no unnecessary phone apps or background processes are running.
-
Comparison Test: Compared the drain rate side-by-side with my Wahoo TRACKR RADAR (which started at 100% at the same time). After the ride, the RADAR was at 62% while the BOLT v3 collapsed to 7%. (I also still own a 7-year-old BOLT v1, which amazingly still lasts 13 hours without issue!).
Current Status: I have submitted a support ticket to Wahoo Support (including device serial number photos and battery comparison screenshots) requesting a warranty replacement (RMA), as this appears to be a clear hardware defect regarding the power management circuit or thermal sensor.
Has anyone else noticed a direct link between false high-temperature readings and rapid battery depletion on the v3?
Thanks!
The temperature sensor is internal and I suspect the elevated reading probably actual internal temp. Most probable scenario is some software process causing hardware (processor, RAM etc) to work harder. Affected components run hotter, drain power and cause self heating.
As yet, this battery drain issue remains a mystery affecting some users but not others.
Suggest you get Wahoo to replace.