Wahoo BOLT - Reboot and "lost ride" problem.

[Bob]

I wanted to post my exchange with Wahoo Customer Support - Which I find very responsive by-the-way.  In the past they replaced a Wahoo Bolt at no charge for me because the buttons were coming off and the battery was failing.  I think they mostly are helpful as possible, but I think this problem with Bolt rebooting is more common then they are thinking and they are failing to properly deal with it - WHICH is why I'm posting here.  I'm asking for your help!  :)

In this case,  the BOLT "rebooted" mid ride on a 400k.   Jack N. and I were doing the DCR 400k checkout, his unit, also a Bolt, rebooted also.  I thought my ride was lost actually because it started back again at "0.00" miles (at mile 170).  Fortunately, at the end of the 400k I was able to recover both the first and second halves of the ride, but that was using a RWGPS feature, the BOLT didn't put them together.

If you encounter this problem please respond, but also, please tell Wahoo about the problem too.  Perhaps they need more riders to chime in if it is something they can fix.

Bob

PS - if you have similar problem, contact support.wahoofitness.com.

----

MY EXCHANGE WITH WAHOO SUPPORT FOLLOWS:

Dear Wahoo Support -

My Wahoo Bolt rebooted in the middle of a 400K ride.  I have encountered this before on other long rides.  Fortunately I was able to recover the lost portion of the ride.  I know others that have had this problem, including the friend I was riding with on the 400k (he had the same thing happen but at a different point in the ride).

I'm glad I was able to save the lost portion, nevertheless, I'm hoping that you can debug this problem and escalate it up to the programmers.  To me this appears to be a software glitch.  I am using the latest firmware on the Wahoo.  The Bolt unit is less than a year old.  I have about 2 GIG of space available on the unit, so space seems a non-issue.

Thank you for your time.
-Bob
--

Bob-

I'd be curious if the issue re-surfaces after the most recent firmware update that you made. We aren't getting other reports of this with bolt users, so its possible it could be a one off.
 
Do you have a similar Ultra-Distance ride scheduled in the near future?
 
Certainly i'm happy to replace the unit, but given its battery life is normal, and everything else seems consistant with it, it doesn't look to be hardware failure related in nature.
 
Best,
 
Andy baker
Customer Support Lead.

-----

Andy -

I doubt replacing it will solve this problem.  I think it is a software glitch.  If you look at my history, assuming you have that available to you, I had this unit replaced in this past year.  I DO appreciate the Wahoo (mostly excellent) support, and that includes your attention to this matter (thanks).  I WOULD hope that this problem gets escalated to the programmers that can have a deeper understanding on how to fix it.

Perhaps I should post your message on a local rando forum (think, ultra cyclists).  I'd like to hear their feedback.  If my small sample set of 10 people serves me, I think it is likely a much larger problem than you possibly are able to know about.  Most of the riders that have told me about this just decide to live with the issue (that seems to include me) so maybe that is why you don't know about it enough.

Thanks,

Bob
--
--
Bob,
 
I assure you we take all inquiries of this nature seriously, and investigate them throughly.
 
I have already brought this to the attention of our team who have confirmed that this is not a historic issue suffered by bolts, and again I will reiterate that we are not seeing a preponderance of cases like this.
 
We are happy to investigate it further, but these investigations are driven by number of reports, and if you have friends experiencing the same issue, please have them write in to support.wahoofitness.com on a case by case basis.
 
Please let me know if I can assist you further, or if you would like to try a replacement unit.
 
Best,
 
Andy Baker
Customer Support Lead.

[Bill Gobie]

I used a Bolt for about five years with no problems. A little over a year ago I replaced it with a Roam, for the larger display. The Roam functioned flawlessly until after a firmware update in March of this year. 

In March it failed twice during a 300. At the first failure the screen went blank then displayed "Hello world". I don't recall if the unit restarted spontaneously or I restarted it. "Hello world" was displayed only briefly; it would be easy to miss if you are not looking at the device when it happens. This occurred somewhere around 200 km. It seemed to navigate correctly but at 280 km I realized it was no longer giving turn cues. (I was also running the RwGPS app on my phone for its spoken cues and I was listening to those.) I power cycled the Roam and was able to reload the route and it resumed navigating. But the ride track up to that point was lost.* 

Before I could get around to reporting that failure another firmware update occurred. Had others experienced a similar failure, prompting a rapid update? 

Irritatingly the updates are automatic. I would prefer to postpone updates until after brevet season. Now my Roam seems to be infested with dodgy firmware.

In April the unit refused to turn off. I searched the internet and learned you can force a reboot by holding the power button until it reboots. After the forced reboot I was able to turn it off.

Last weekend it refused to load routes. I was hours from home, starting a permanent. Power cycling and forced rebooting did not help. I tried to select routes with the companion app on my phone but the app reported the Roam was having a problem. Yeah, I knew that! The problem was not just with the route I was going to ride. It would not load any route. Sometimes when I attempted to load a route it would display, "poor gps". But the unit displayed my location correctly and recorded my track correctly. I tried loading the route several more times throughout the day without success. Again fortunately I was able to navigate with the RwGPS app on my phone, albeit with some backtracking when I could not hear cues. Once I got home and synced routes the Roam would load routes with no apparent problem.

Now I'm facing this weekend's 400 with an unreliable gps. The RwGPS phone app is not an ideal solution. I cannot always hear it. I do not have a good way to mount the phone to see it (on a laid-back recumbent), and I don't want to expose it to this weekend's likely rain. If I could read a cue sheet at night in the rain I would not be using a gps.

 *Losing the ride track was a near disaster because I was using EPP for that brevet -- the track replaced my brevet card. Fortunately I was also running the RwGPS app on my phone for the voice cues so I was able to use that track.

I haven't had the bandwidth to report this to Wahoo. 

Bill

--
You received this message because you are subscribed to the Google Groups "randon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to randon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/randon/2581056f-7111-426c-bc3f-6764fe5a8814n%40googlegroups.com.

[Peter J Leiss]

And this why we always carry a backup paper copy of the route. GPS is just another tool sometimes they break. 

Peter

Sent from my iPhone

On May 5, 2022, at 2:52 AM, Bill Gobie <gobie...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/randon/CA%2Bsg%3DPppA6yywKSD%2B2m5B9JssfjBN79uw8LWeFvb4S36aC4%3D9A%40mail.gmail.com.

[Bob]

Thanks for your response Bill.  I also got that similar "Hello World" message when it rebooted.  I was able to reload the route and continue but the mileage started back at 0.00.  Fortunately that was the case.    I think if the route could not reload I'd be switching to something else (although, I've been down the Garmin road and that had failures in the past!)  Maybe the newer units are better.  If you have experience with that I'd be thankful for any recommendations.

I also got the "would not turn off" issue and forced a reboot with the 10 second power button press.  I'm heading out on a big ride Sunday.  I will be using my phone as a backup device as you seem to have done.

If you have problems with your Wahoo that are similar do report it to Wahoo.  They are responsive but perhaps they are not likely to deal with the problem if enough riders don't let them know.

Bob

[Brett Sterling]

I don't have a Wahoo BOLT, but have used other Wahoo products.  My experience is somewhat the same, but also somewhat different.  I too have found them very responsive - i.e. they respond to my submission very quickly - but also not helpful - i.e. they indicate that they are logging the issue, but I have never seen it actually get to an engineering team to be addressed.

It was my experience with Wahoo customer support that made me decide to go with other brands for my cycling stuff (and I have been very happy with that decision - there are still customer focused products out there!).

Best of luck - I do hope you get this resolved soon!

Brett

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/34974834-15d1-413b-98ab-2e6459609fe6n%40googlegroups.com.

[Ronald Long]

Interesting. I started a ride on Tuesday - a 200k, but not from the official start point. Got to the official start at 125km, saved and ended that ride, and loaded the RWGPS route. It would show my position on the map, but didn't load the route, and wouldn't navigate (and, yes, I foolishly didn't have a usable backup.).

I assumed I had done something wrong, but it is sounding suspiciously similar to some of the problems described above.

[mi...@demarcoip.com]

Bob - Exact same thing happened to me with my four year old Elemnt on the non-preride version of the DCR 400K. Computer disconnected from my HR strap at Mile 130, intermittent data from my pedals at Mile 173, and then a full failure at Mile 175. Took me thirty minutes of smashing the power button to get it turned on and the ride restored.

I had the ridewithgps file downloaded to my phone and the bone conduction headset (two thumbs up!) ready to give me alternative instructions, but luckily I was able to follow other riders during that 30 minute period. (Also had the PDF cue sheets saved to my phone as my 2nd backup item, but have zero interest in reading a cue sheet to do a ride.)

Taking your advice and pinging Wahoo to share the issue with them. I still absolutely love my Wahoo bike computer and definitely won't be switching to a Garmin, Karoo, or whatever. I know one extreme Rando rider (aka the loony quintuple K-Hound) who saves every ride in ~200K chunks and then stitches them together after the ride. Since he has vastly more super long ride experience than most of us, perhaps he's onto something till this bug gets fixed.

Mimo DeMarco - RUSA #12711

[Narayan Krishnamoorthy]

This isn't recent, but I've had this happen on a 1000K - when I kept the Bolt running for about 64 hours+; around 920K I looked down to see the Bolt showing "Recovering ride...". That took a mighty long time and I got no turn by turn directions during that time. After it finished rebooting (I don't remember if I did it myself or automatically), I reloaded the course and continued on (at km 930). It was 2 different rides at that point, and I used rwgps to put them together. Hadn't heard of it dying on a 400K. That seems awfully too quick ;)

https://ridewithgps.com/trips/46049809 (if you look, there is a straight line between km 927 and 930. But the "recovering ride" showed up several kilometers before that, which means the Bolt kept recording data as it was recovering the ride).

Hope that helps.

Narayan

[Bill Gobie]

On Thu, May 5, 2022 at 11:03 AM Ronald Long <ronal...@gmail.com> wrote:

Interesting. I started a ride on Tuesday - a 200k, but not from the official start point. Got to the official start at 125km, saved and ended that ride, and loaded the RWGPS route.

It is not necessary to "save and end" and start recording a second track, if that is what you did. From the map page press Route, then End. The unit will ask, "End Route? Your workout will continue to record." Answer yes. Then reload the route and continue on your way. Your ride will be recorded in a single track.

Bill

[Ronald Long]

Thanks! Never ceases to amaze me what a small slice of the functionality of the many devices I own I'm actually aware of.

[William Beck]

My Wahoo ROAM actually restarted THREE times during the DCR 400K for which Bob did the checkout ride. Each time it had to spend several minutes "recovering ride," during which time it did not record and could not be used for navigation. The second time, it awakened in a state with "Poor GPS" and therefore wouldn't navigate. I had to manually turn it off and back on, wait for it to again recover the ride, and fortunately it came back with the GPS working and I could navigate. In the end, the entire ride was recorded except for about 6 miles that was missed during the periods that it was recovering.

I contacted Wahoo and they said that problem is often fixed by replacing the unit. I responded that's OK, but pointed out the other people who had the same problem, suggesting that it is a firmware, rather than hardware, problem. I also pointed out that, along with excellent integration with RWGPS, the main strength of Wahoo was their reliability compared to Garmin, and that they seem to have thrown that reputation away by these kinds of problems.

They are fixing other problems though. My ROAM had stopped properly displaying the phone battery status, which they said was a known problem. After the update that I downloaded this morning, the phone battery status display works again.

Bill Beck

[Bill Gobie]

On Thu, May 5, 2022 at 12:23 PM William Beck <william...@gmail.com> wrote:

 After the update that I downloaded this morning, the phone battery status display works again.

My Roam reports "up to date." Splitting routes into 200k chunks seems prudent. Good luck.

Bill 

[Bob]

Thanks to all that responded with similar problems.  Bill, Bill, Narayan, Mimo and the several others that emailed privately. 

I think some of you had said, and I will ask again, please contact  support.wahoofitness.com and submit a ticket.  The guy told me "they don't find anyone else with this problem" which is total BS to me.  They just don't have many users that ride above 200k that use their devices!

I think they mostly cater to the 99% of users that are not Rando's or Ultra Cyclists right?   That doesn't mean their units don't have a problem.  And they told some of you the same that I heard - "We can replace it for you"!  Which is ridiculous I think.

I use my phone as backup to the Wahoo unfortunately.  I guess it comes to that sometimes.  But the process of saving every 200k might be a good workaround.

Bob

[Greg Goebel]

I had similar experience with my ELEMNT during two recent 600km brevets. Below is exchange with WAHOO Tech Support.

Bottom Line: "Not enough "free space!"

John G (Wahoo Fitness Support)

May 6, 2022, 12:15 AM EDT

Hi Gregory,
 
Thanks for reaching out to Wahoo Support. I'm sorry that you are experiencing this issue. 
 
This issue may be occurring on your ELEMNT device because of a lack of free space. We recommend having at least 1GB of free space for the best performance.
 
Please see the below support articles which will walk you through how to connected your device to WiFi, and manage the maps to free up space. These maps are always available for re-download in the future, should you need them.
 
https://support.wahoofitness.com/hc/en-us/articles/115000638644-Connecting-ELEMNT-BOLT-ROAM-to-WiFi

https://wahoofitness.yonyx.com/y/conversation/?id=0861dff0-53dd-11e8-8f6c-bc764e10d166
 
Additionally, we generally recommend breaking up large route files into smaller sections for the most consistent and best results.
 
If the issue persists after following these steps, please let us know.
 
Kind regards,

John G
Customer Support Specialist
Wahoo Fitness
www.wahoofitness.com

Gregory Goebel

May 5, 2022, 12:30 AM EDT

Hello,

I have ridden two 600km rides over the past two weekends and my Wahoo Elemnt has crashed, i.e. restarted and recovered ride, after ~15 hours of being powered on during each ride. I start re-charging the unit at approximately 8 hours into the rides because the battery only lasts 10-11 hours (backlight=off, route/map=active.)

The unit has 733MB of free space and is at version WF48-14713.

Is there anything I can do to keep the Elemnt from crashing and losing miles?

Greg Goebel

RUSA 12470

[Bob]

I think perhaps they say free space is the issue.  I think this is just their go-to reason.  My communication with them addressed that.  I have 1.4 Gig of free space and the unit still crashed in similar fashion. 

As mentioned before, it may be wise to just stop the ride at about 200K.  Restart (at 0.0 miles in other words) and then reload the route,  you are then following the route after riding 200k or so of it.  At the end of your ride just paste the two halves of the ride together.  I did that in RWGPS easily.

Bob

[Mark]

Not everyone who has problems is on brevets!  My wife and I are on a bike tour in Europe and traveling by ourselves on a tandem.  Our average ride length per day is 45 miles.

On two separate days we have had problems with our Wahoo Roam unit’s GPS not working.  It simply froze up and didn’t show movement, although the workout time continued to work.  I have managed to get it to work by first resetting it to the factory settings and rebooting it, then the second time letting it run out of power and die, then rebooting.  It still occasionally shows “poor gps” as it starts.

I have an old garmin and my iPhone that I have used as a backup—not the greatest solution but ok.  

Mark W

Sent from my iPhone

On May 8, 2022, at 2:16 AM, Bob <robert...@gmail.com> wrote:

I think perhaps they say free space is the issue.  I think this is just their go-to reason.  My communication with them addressed that.  I have 1.4 Gig of free space and the unit still crashed in similar fashion. 

--
You received this message because you are subscribed to the Google Groups "randon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to randon+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/9396b915-9735-41a8-8c89-23018702e48en%40googlegroups.com.

[Eric Norris]

Reading this as a former Wahoo Elemnt user. I had the same issue with the unit freaking out after about 400Km. When I took it to PBP in 2015, I split the ride into three parts, ending and restarting each time at Loudeac and at the finish.

The first time I experienced this with the Elemnt was particularly problematic, as it locked up 400Km into a 600Km brevet. It took a while to figure out how to reset the darn thing to keep me going for the last 1/3 of the ride.

I use a Hammerhead Karoo now, which has its own quirks but doesn’t shut down on long rides.

--Eric Norris
campyo...@me.com
Insta: @CampyOnlyGuy
YouTube: YouTube.com/CampyOnlyGuy 

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/A6E86AA1-8F47-4A56-A9F1-51B19FE59B3F%40yahoo.com.

[Charles Coldwell]

I hit this bug while riding a 300K yesterday on an Elemnt BOLT. I looked down and my head unit was displaying the message "Restoring Ride xx%" where xx ran from 0-99. After restoring the ride it picked up again where I left off although I had to reload the route. I didn't stop to wait for it to reload, so there's a bit of a gap in the data, you can see it between 305 and 306 km (about 189.5 miles) here

https://ridewithgps.com/trips/89534955

The route should follow Harvard Road/Warner Road/East Bare Hill Road/Brown Road but has been replaced by a straight line.

The ride is a bit longer than 300K because per my tradition I ride to the start and (slowly) home from the finish.

--
You received this message because you are subscribed to the Google Groups "randon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to randon+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/randon/9396b915-9735-41a8-8c89-23018702e48en%40googlegroups.com.

--

Charles M. Coldwell, W1CMC
Belmont, Massachusetts, New England
"Turn on, log in, tune out"

[William Beck]

Wahoo insists that they want to replace my ROAM to fix the resetting problem. I'm not convinced that will work since so many others have the same problem, but figure I'll at least get a new unit with a fresh battery. I'm not sure why they're pushing a solution that costs them money unless a) they have a reason to believe that there actually IS a hardware problem, or b) they're about to release a new ROAM2 and want to get rid of the old ones. They wanted to wait until they received my old one before shipping a new one, but I didn't want to be without a unit for that long. So they had me order a new one from the web site, and will refund that payment after they receive the old one.

Bill Beck

[Georgi Stoychev]

Bob, 

Thanks for the suggestion on opening a ticket with Wahoo to bring awareness to this problem. Besides that, I have been in love with my unit. My other issue is the temperature increasing at times when plugged to a power bank, it will spike to above 90 F and i have to disconnect it for a moment :)

While crossing the US last year, I had numerous issues with freezing. Luckily, the directions were straight forward so I kept pedaling while waiting for the device to reboot after holding the power button like everyone else and re load the route. Sadly, if the file is very large , it takes forever to load. I was saving it after each day and started fresh so in case a restart is needed , it will not take as long. My device was already replaced as well and the problem is not solved. None of the firmware updates seem to be addressing this issue as mentioned above. I like the idea of freeing some space on the unit  so it can move a little faster. 

Ive also had an issue where the zoom function will stop working until you scroll through the pages and attempt it again. I am not sure why I am still using it with all these issues :) When its working , it is a great little unit and the battery life is great at 1600mAh MaH battery, my small 5000 Mah power bank can literally charge it  3 times and get 1.5 days of life ( except when the screen light is on at night )

IF you were recording and experienced an error, the actual ride file can still be located on the device storage when plugged to a PC

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/e6fc4be7-f974-4abf-a583-83819eb05eecn%40googlegroups.com.

--

Georgi Stoychev

[William Beck]

In case anyone is interested in the continuing saga, Wahoo seems to think that hardware replacement is the solution. When I told the guy at Wahoo that I had low confidence in that working because of all the other people with the same problem, he said "This replacement will solve the issue." Unfortunately, the replacement unit I received has a problem of its own. With the unit off, but connected to the charger, it displays a battery symbol with four bars to indicate the charge state. When fully charged, all four bars are supposed to be solid. But on my replacement unit, the 4th bar continues to blink forever. If you turn the unit on, you see that it is 100% charged, but you can't tell that without turning it on. So it looks like I will have to order ANOTHER replacement.

Bill Beck

[fint...@gmail.com]

Hi All,

Sad to say, you're not alone. Here in Ireland over the last few weeks we have had issues with Wahoo devices rebooting mid ride on 300 and 400km cycles. Tickets were opened and like previous posts we were told to free up space. Last weekend on a 400km, 3 out of 7 Bolts had rapid battery drainage, mine went from 100% to 0% after 6.5 hours. Along with the battery drainage the others rebooted, some twice on the ride. 
Initially with my ticket I was told " This is something that we have never seen before with our Elemnt Bolts". I went back with other ticket numbers that were opened and they just said they would let the software team know. They are currently keeping my ticket open to see if it re-occurs.

Regards,

Fintan Brewster

[William Beck]

Wahoo says that the blinking 4th battery bar, even when fully charged, is a known issue with the "new" ROAMs. They are working to fix it (all bars solid when fully charged) in an update. It's actually reassuring that the new ROAMs are physically different than the old ones since it makes it more plausible that the new ones will actually fix the rest problem. The blinking 4th bar is a minor issue to have until the update.

Bill Beck

[Charlie Martin]

Late to the party, but I'm finally caught up on this thread. Good and interesting discussion here.

TL;DR here's what's served me well in the past:

• Save your current recording every ~200K, 12 hours, or some other regular benchmark. I've never had problems with recordings of these lengths. Pick an interval that you're comfortable with, keeping in mind the unit becomes more unstable the longer it's in use, and also the amount of time it takes to recover your ride is proportional to the duration of the current recording.
• After you save your recording, restart your device before starting a new recording! This is necessary in order to make the device stable again!
• If your unit does crash on you, save your recording as soon as your unit finishes recovering your ride. It's still unstable and will likely crash again before long if you carry on like nothing happened. It's incredibly frustrating waiting 10 minutes for your ride to recover, only to wait another 10 minutes when the unit crashes again shortly after it revives. Once you save your recording, restart your device! Otherwise it's still unstable and will keep on crashing.
• If you're hesitant about this process because you want a single recording, it's dead easy to combine the individual pieces together. Your Wahoo produces .fit files that you can stitch together using a variety of free tools on the Internet. My favorite is fitfiletools. You can get the files directly from your Wahoo, or you can download them from Strava (open activity, click the 3-dot menu, and then choose "Export Original"; alternatively, take your activity URL and append "/export_original" to the end).

Wahoo's main selling point to me over Garmin was its reliability. My Strava feed would regularly show people's rides getting lost due to Garmin crashes. I still see it happening. Over any other feature, preserving my ride data is the most important to me. From what I've seen lately Wahoo hasn't been doing as well on that front. I have had several Wahoo crashes on longer rides in the past across multiple Bolt units, but I've never actually lost any ride data. Lately I've heard of people losing their data as well. I've never had a crash when I preemptively applied the workarounds in my TL;DR, so I've been happy to continue living with the Wahoo. I am unsure whether any of the issues in this thread are brand new and might indicate different or more severe problems with the units.

I didn't own a dedicated GPS unit or start doing "long" rides until 2018, but I've experienced crashes with the Bolt as far back as 2018. In my experience it's not so much the distance that predicts when the device becomes unstable, but rather the length of time it's been recording. My first crashes were during Everestings where you don't tend to cover huge distances, but the rides can still manage to take a long time. I eventually had issues on SR600's and then on shorter rides like like flat 400K's. Anything up to 300K has generally been safe for me unless it's been a particularly slow ride for whatever reason.

I have owned 2 Wahoo devices, and I've had the same crashing behavior on both of them. Unless Wahoo claims to know the actual cause of the crashing, I think they're grasping at straws when claiming that replacing the unit will resolve the issue. It's hard to verify or refute a possible fix for a problem that happens in extreme circumstances. I think it's far more likely that they didn't design their units with ultra endurance cycling in mind, and all of our crashes seem like outliers to them. For me it's become an expectation and I have learned to build my workflows around it. If I hit a control 200K-300K into a brevet, you can expect I'll be saving my recording and restarting my device!

It sounds like randonneurs haven't made sufficient noise for Wahoo to see this as more than a transient issue. Time to start filing bugs I guess.

- Charlie

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/06a18cc0-9692-482b-80df-f1e6d4d51186n%40googlegroups.com.

[Eric Keller]

On Tue, May 17, 2022 at 12:23 PM Charlie Martin
<charlie....@gmail.com> wrote:
> Wahoo's main selling point to me over Garmin was its reliability. My Strava feed would regularly show people's rides getting lost due to Garmin crashes. I still see it happening. Over any other feature, preserving my ride data is the most important to me.

I'm probably due for an unpleasant surprise, but my Garmin 830 has
never let me down and has great battery life. I thought doing all of
PBP on one ride might not be a good idea, so I reloaded in Brest.
Having said that, there are tons of earlier garmin devices still in
use, and they all seem to have problems. And I know there are some
830's that have given people trouble, but so far I think that's just a
few bad examples. Before I got rid of it, my 800 got an update that
made it so the inevitable crash happened at 550km instead of 250km.
That was much appreciated.

I have nothing but praise for Wahoo for forcing Garmin to take their
bike devices seriously.
Eric Keller
Boalsburg, Pennsylvania

[fint...@gmail.com]

The latest update from Wahoo to an open ticket that one of our members got.

"We have identified the issue here and linked it to a few other users experiencing the same behaviour.  As a result we have opened an internal ticket with our developers to fix this.  Since we have an open ticket with our development team, all customer service tickets related to the issue (including this one) will be marked as “On-Hold” and merged with the developer ticket to be monitored internally. This process allows us to send automatic notifications to you via email when changes are complete. Full release notes are posted on https://support.wahoofitness.com"

No indication of a time frame for a solution.

Fintan

[Bob]

Now that is nice to hear!  

Underscoring the importance of letting Wahoo know about the problem.  Thank you to all that contacted Wahoo and opened a ticket, please do so if you haven't already.

In the meantime I am incorporating Charlie Martin's strategy of saving the ride after a certain amount of time or distance.  It is easy to combine the rides together at the end.

Perhaps unrelated, I have also noticed a quicker draining of the battery lately.  I looked down on the last 200k I did, it was down to 10% (I started fully charged) by mile 100.  I'm betting this is due to their more recent "FIRMWARE UPDATE".   That is unusual.  I hooked it up to the dynamo charger and made up the difference, but I was surprised.  Normally a full charge will take me far past a normal 200k.

Bob

[Charles Coldwell]

In 2019, I did all of PBP as one continuous ride on my Wahoo Elemnt Bolt, charging it from a generator hub via a Sinewave Cycles Beacon headlight. I did not have any problems with it then nor until the 300K two weeks ago. That makes me suspect that one of their updates introduced a regression.

--

You received this message because you are subscribed to the Google Groups "randon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to randon+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/04d77039-f181-4d1d-ab94-d95fdd75d607n%40googlegroups.com.

[blue...@gmail.com]

I'm adding a data point to this discussion of Wahoo BOLTs freezing and rebooting on long brevets.  I also have the original BOLT and it choked on a 300k ride this weekend.  It was the 3rd time this year for me - all on 300k+ rides - but not happening on every 300k+ ride.  I have not had this problem with my BOLT until earlier this year - adding some weight to the theory its software related.  Here is Wahoo's reply from support:

"This is an issue we are aware of and we have opened an internal ticket with our development team to investigate and resolve the problem.

 
Since we have an open ticket with our development team, all customer service tickets related to the issue (including this one) will be marked as “On-Hold” and merged with the developer ticket to be monitored internally. This process allows us to send automatic notifications to you via email when changes are complete. Full release notes are posted on https://support.wahoofitness.com
 

Be sure to keep your app and device up-to-date to receive the fix, when available."

While this doesn't solve the problem - the efforts to open support tickets has gotten their attention.  I also note they don't say its a hardware specific issue, which might mean there is a fix possible.

Kevin Smith - RUSA 12995

[Ted Shwartz]

Perhaps this might be of help

Sometimes my Garmin Edge would flake out on long rides, which tended to take place in summer. My theory was “heat stroke”. My solution was to shut off, or cover with shade, when stopping at controls. It seems to work

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/fb6e6ddb-6dfe-4a38-b200-2f8dc48bb7a4n%40googlegroups.com.

[Bill Gobie]

My experience with my Roam Tuesday pre-riding a 600: I broke the route into three 200 km sub-routes which some have indicated avoids problems. The unit installed a firmware update when I synced routes before the ride. At the end of the first 200 km I stopped recording and power cycled the Roam. Instead of restarting, the five LEDs at the top of the device started blinking, #s 1, 3, 5 flashing together alternating with 2 & 4. I was able to force reset by holding down the power button. I let it stay off for several minutes and also unplugged my Sinewave Revolution from it. Then it restarted and seemed to navigate the second sub-route correctly.... 

Exactly 100 km into the second sub-route I noticed the speed field was showing "--". (The view of the sky was wide open, this was unlikely a poor gps fix episode.) After a couple of minutes it became clear the distance to next cue was not updating. The device allowed me to stop recording. I turned it off, unplugged the Sinewave, and let it rest for several minutes. After restarting I was able to reload the route and it navigated the remaining forty or so km to the overnight.

Bill

To view this discussion on the web visit https://groups.google.com/d/msgid/randon/8448D135-EB04-4177-B0FF-73880439E97C%40gmail.com.