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

Well, that was an adventure in pain....

Got the 1030 this morning. Good timing it appeared to be as the GPS and altimeter on my 1000 seems to have crapped out.

Started the setup process following the prompts and things seemed promising. Got half-way through the phone/1030 setup and the connect app on the phone hung up. Hung up the phone so well, it froze the full screen. Even the on display time of day froze!

Finally after 4 or 5 tries (deleting the blue tooth devices, unloading the Garmin connect app), I was almost able to get it set up until the Garmin app hung up again when getting my profile info. The Garmin app is really brutal and needs to be looked at by a qualified Apple app developer. They are doing something wrong since this is a simple question and answer situation and the phone case is burning up! They are doing something really stupid in the app to cause the battery to drain really quickly and to cause it to heat up.

Next problem was adding sensors. It found the speed sensor twice and interestingly named it twice (not sure what happened there since I only named the sensor once). Then it wouldn't find the Di2 at all. Five minutes of trying to get it to find is five minutes of time I am never getting back. Finally, I used the e-tube app to update the Di2 firmware just in case it was that. Eventually, and for reasons I do not know why, I was able to find the Di2 and get it paired with the 1030.

What should have taken at most 20 minutes became 90 minutes. Hopefully the rest of the setup doesn't go totally sideways.
  • I have had some hang ups lately in GCM as well but I chalked mine up to running the beta version.
  • I had major problems when first pairing my spd/cadence sensor (Bontrager Duotrap S). At first it seemed simple (like my other Garmins) and I saw "Duotrap S Sensor" pop up. Great, selected... off I go. Well, my first ride out there not only was no cadence, but no speed, no distance or any other speed related data such as ascent, grade, etc.

    When home, I removed the sensor and tried again. Same result. Attempt #3: I let the scanning go on for about five minutes and now tnarrow 19100wo sensors appeared: 1) the original "Duotrap S Sensor" and 2) 123456 Sensor (numbers representing device ID). Hmm. So this time I selected just the sensor ID and bingo --- all my speed/distance data came back as well as the cadence.

    Can anyone offer an explanation for this, or why there were two sensors displayed?
  • Dual sensors one is Bluetooth and the other is ant+ the one that lists the name is the Bluetooth connection.
  • Is it a dual protocol sensor, ANT and BLE? If so you might be seeing it appear twice, once under each protocol.
  • Well, that is the question. Why did I only see the two sensors just the one time? And why the lack of speed/distance data?