This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

1030+ Bug lits

I've used the Edge 1030+ since Jan 2022 and here is the list of issues I run into on every ride (roadbike)

This is on the latest firmware and the screen fields are all the defaults Garmin built-ins

Bontrager IQ Light Control is the only extra app that is installed

All sensors are from Garmin apart from the SRAM Force/Quarc and all are connected using ANT+

1. Unit will randomly pause as I'm riding and speed will show 17-20mph and drop to 3 mph and go back up. GPS is set to use all satellites. Wheel is using Garmin's SpeedSensor 2

2. Power/Cadence will freeze/remain stuck at 70 pwr/ 60 cad despite changing the battery in the SRAM/Quarc meter.

3. Unit will never find the headlight/taillight (Ion Flare RT), until the unit is rebooted at-least once, after which it announces battery is critical on the lights despite being fully charged

Would it be possible for Garmin to actually fix these basic issues or hire more developers to do so for their flagship product ?

Repeatable issues on every build indicate a broken process control and this will create an inflection point where competitors like Hammerhead/Karoo 2 can move into the same space

As a longtime developer, the above is not exactly rocket science and I am willing to work with the dev team to narrow down any issues and see that they are resolved and supply any diagnostic information they would like.

Thank You.

0 Pete over 2 years ago in reply to cheracogoff

Nope. That is not an acceptable solution. If theres an error in your bank statement due to a bug would you like to reset and delete your bank account and start again ?

This is a fixed/static unit with known hardware and sensors and there should be less issues.

eg.The Bontrager light control widget only works after rebooting the system and on the first ride & never works after that. Why ? It's not rocket science to keep a state table with pointers and do a callback when an event is triggered (ie new ride started)

Maeve has reached out directly above (thank you) and I will enable diagnostics for the next couple of weeks and send it over and I hope this can be resolved.

0 cheracogoff over 2 years ago in reply to Pete

Garmin tech support will suggest a reset frequently. Garmins file structure is lacking in error checking and a reset corrects problems especially when there are multiple problems.
Since your computer has had problems so long, I would have thought that you would have contacted tech support. They probably would have exchanged it.

0 Pete over 2 years ago in reply to cheracogoff

The issue is intermittent after the last update which is why I don’t think it’s the hardware

if the file structure is an issue, switch to json, which is lightweight and serializable

0 yendorg over 2 years ago in reply to Pete

I purchased a new 1030+ last week and are having the same issues with sensor connection and drop out. My eTap AXS and Quarq power rarely auto connect and when I finally get them to connect they drop in and out every 10-20 secs. My Stages power on my other bike generally auto connects but also drops in and out, however not as frequent as the aforementioned. The only sensor that connects with any stability is my Wahoo Tickr HR. I have completed multiple resets and added and remove sensors a dozen times with no improvements. I'm running V6.4

My old 520 auto connects, within seconds of being turned on, to all of the above sensors and is rock solid, NEVER drops out!

0 Pete over 2 years ago in reply to yendorg

If you pre connect before you start a ride it will stay connected with off exceptions as mentioned above

if anyone can repeat my steps above for timer start and see if they can reproduce the bug where it suddenly starts a ride then please post as it will confirm the issue and give support some better data

0 mcinner1 over 2 years ago in reply to Pete

Pete said:
if anyone can repeat my steps above for timer start and see if they can reproduce the bug where it suddenly starts a ride then please post

This is less a bug than a problem with GPS.
If you do not use a speed sensor, or have not yet connected it, then the Edge takes the GPS signal for the speed display. If you do not have a good satfix, the GPS signal jumps several meters around. This in turn simulates a speed that then starts the activity, although you are standing.
I have therefore set the start of the activity to manual. You will get several warnings if you start without pressing start.

0 Pete over 2 years ago in reply to mcinner1

Without starting any ride and powering on the device and keeping the bike stationary or just holding the device in your hand

Settings -> Activity Profile -> <profile> -> Timer Start

Selecting any other mode like "auto" sometimes causes the whole screen to jump back to the profile & start a ride.

I was able to see this issue, but am having a hard time figuring out what sequence causes this bug as it's a difficult to replicate.

Try the above and keep a phone handy recording your key presses, if you are able to get it to glitch as above

0 Pete over 2 years ago in reply to Pete

Another bug.

1. Power on Edge 1030+ or simply plug one end of usb into a computer (mac in my case)

2. Plug other end into unit

3. It will randomly use the default bike profile and start a ride

4. Hit stop & discard ride & it will jump back & start a ride again

5. Stopping & discarding ride the 2nd time stops this from happening

* I am sitting in my office upstairs & the bike is on the wall in the garage downstairs & trying to get the unit to mount so I can send the Garmin folder over to QA

0 mcinner1 over 2 years ago in reply to Pete

Set

Settings -> Activity Profile -> <profile> -> Timer Start

to „manual“!

0 Pete over 2 years ago in reply to mcinner1

That also triggers the earlier "auto ride start" bug mentioned above

At the moment I have managed to download the Garmin folder which is 16gb (14gb compressed) and trying to upload it to Garmin. The unit is pretty sensitive to the type of usb cable being used.

There is no indication that the fileis being uploaded in Safari, so I am also dumping it on my google drive & will send the link to Maeve @ Garmin support

This has all the ride activity along with my detailed notes on the last 4 or 5 rides with debug logs enabled & should help them narrow down the issue

As a developer myself, I know how annoying it to get bug reports without being able to reproduce issues, so this is an attempt to do controlled experiments/rides to make it easier to fix all these issues.