So Wi-Fi is not active during the ride. You can see the Wi-Fi icon in the status bar when it’s connected or trying to connect. If you do see it during a ride that would be a bug you should report.
I have problems occasionally where I have to restart my Pixel 9 to make live track work, and maybe something similar is causing your BT battery drain, might be worth trying.
Richie, last ride I experienced first time live track failure but thought it was a phone problem. Had to restart phone and also email a new livetrack URL, continued working after that. Diffrent message to network coverage loss.
My latency problem last year I suspect due to phone having ‘optimised’ BT app power mode. Later in ride causing phone BT app to cause delayed ACK’s / replies to Roam data polling. Roam probably doing many comms retries, loading CPU and subsequently not servicing other functions. Poor allocation of real time multi tasking resources? Clearly, intense CPU activity increases consumption.
All speculation because Wahoo support simply ask stupid questions rather than engaging in meaningful technical analysis and discussion!
I’ve now done a number of rides and it’s clear that a Bluetooth connection to the phone triggers high power usage. Just connecting once after booting up the head unit is enough. It doesn’t help if I stop the Wahoo app or disable Bluetooth on the phone later on.
So that means common use cases like picking a track from within the app are affected, I cannot really use live track, and so on.
I’ll open a new support request, let’s see what they will say.
I got my new Roam 3 about a week ago. I’ve immediately noticed poor battery life, much worse than my older Bolt V2. Yesterday I did a 5 hours and 20 minutes ride, and the battery went from 100% to 19%. Backlight turned completely off, navigation on, connected sensors: HR, Radar (Garmin), SRAM power meter, SRAM Force shifters. I checked and the software version is WH49-302543. I’m starting to regret my purchase.
Noticed the same issue on an 8hr ride yesterday. First ride with a route loaded on a 2 week old Bolt 3. All other rides on it were just my usual park laps so never needed a route for those. Battery drops were never an issue in the handful of rides I did before yesterday’s long one.
On this ride, was connected to the Wahoo app, but after noticing the battery drop, turned off backlight, set the brightness to auto, turned off Live Track AND “forgot” my Garmin Varia sensor in hopes of saving more battery. No dice. Dropped from 100% to 7% in 6 hours — had to plug it in for a few minutes at a cafe to make sure I found my way home.
After my mid ride charge to 40%, I turned the Bluetooth on my iPhone off as well, but it continued to drop until I ended my ride at home, all the way to 8% after 2 hours.
I’ve emailed Wahoo Support, but this seems like a software issue that’s yet to be solved. Does anyone have any insight besides what’s been contributed on this thread?
Need info/a potential fix urgently for a multi-day tour I have coming up at the end of the next week…or do I need to pony up for a Garmin head unit?
As a short term fix I suggest you use a battery power bank and USB-C lead.
I ride on busy roads with a flashing front light, a safety measure. I have a Towild CL1200 and a CL1600 (from AliExpress and Amazon). These lights are great and have bidirectional charge port. Recently, I forgot to charge Roam 3 before ride, connected light to Roam 3. Got home after 5h ride with Roam 3 100% charge.
Probably going to have to do that since there’s no concrete fix from Wahoo as far as a software update goes…battery packs are just going to add more weight to my pack now.
That is not normal. I have done over 10 hours with plenty of charge left on the roam and a radar, power meter, speed sensor and HRM connected. I always run on auto setting for backlight. Reach out to support.
Some USB leads, particulary longer ones >2m exhibit high resistance. Also some chargers may output less than 5V DC since they too have higher resistance and poor regulation. However, with either lead or charger problem then Roam / Bolt , from a battery low condition, would not charge at all, i.e. won’t display Wahoo/ charging when connected to charge lead.
If the Roam / Bolt displays 100% and you let charging continue for another 45min, then it should be fully charged.
Given over 100 posts, I’ve noticed a trend that extreme battery discharge reports are being raised on product recently purchased. Users like me with a Roam 3 purchased May 2025 only have a lesser battery operation time when running Auto Max backlight.
Out of interest, did the Wahoo support desk provide their name?
Hrm, power meter, navigation, di2, app connected, location sharing on. I turned on radar in second half. Brightness set to auto.
My roam3 barely held, it finished with 4-5% battery. So 95% in 10h of running time. I did not turn it off in any stage, it was still on during breaks (that were between 10-100mins)
When i was on 9% and around 30k to go, i turned off the navigation in order to hold on for the whole ride.
Im rather not commeting this further. Unit was bought in september 2025
It happened to me 2nd time (once before ‘battery update’ and once now - rides more than 10h barely being finished)
Wahoo support is still playing dumb in my case, too. It turned out that my hunch with the Bluetooth connection is probably wrong. I’ve now had it happen without phone connection, too. It’s simply random, sometimes battery life is OK, other times it’s horrible. I cannot rely on the unit at all!
Maybe I’ll go through with a replacement for shits and giggles, even though I don’t expect it to fix anything. After all, Wahoo support told me it is “all they can offer”.
Worth taking a chance that a replacement will solve the problem. However, I’m sure I read another post on this thread where problem continued.
Whilst you ruled out BTLE/phone, some other process must be consuming battery. Given not all Roam 3 users have this problem, the variable has to be configuration, options, sensor combination etc.
Wahoo is either evading a known problem (too difficult to fix) or can’t identify or repeat the problem.
Assuming they can’t identify, a proficient developer would create a version of soft/firmware with trace code to log process activity in order to identify abnormal process load.
You and other users with this problem are Wahoo’s asset for testing and improving. My solution would involve sending users with the problem (or everyone, through normal updates) a version of code with 'trace code ’ and then review log files when user reports a problem. Plenty of storage on Roam 3 to do this.
‘Trace’ is an additional process, for example to log ‘real time’ runtime of each process, or log battery % against time, log comms errors etc
I have the same problem with roam3 purchased a month ago and I reckon I figured how to stop it.
I was at a ~18h race and decided to replace my trusty bolt v2 with the roam3. Bolt consistently got to 13-15h.
Race day and in 1h45 the battery was down to 68% from 100. Panic. Device gets hot when it is bugged. Turn off bt in phone, keeps draining. Restart device while bt is ON in phone same problem. But if I restart the device with the phone’s BT off and load route directly on the device drain stops. Managed to finish event with 20%
Powermeter, HRM and di2 connected.
I have encountered the problem very frequently. And have confirmed the workaround to be consistent.
The device definitely gets warm when bugged, no one else felt that?