Related
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

Bug on climb pro

Roberto Ena
over 3 years ago

Hi

when using climb pro, very often the "remaining ascend" freezes. This happens mostly (probably always) on imported gpx tracks.

If I stop/restart the navigation, maybe to a slightly different route, what happens is that the new route shows on the map, but the "climb pro" window retains the old route climbs (still frozen)

I have to switch off the device (and loose the activity)

Any suggestion?

I have version 4.10: I will update the device, but only if this is a known bug that has been fixed.

Thank you

EDIT: I'm attaching images showing the issue. It was a video but my language was not very polite so I'm attaching just two frames.

Here the display correctly says "26 km to destination" (I just loaded a new destination)

But here the climb pro is still stucked on the previous climb (and says "next climb 34 km", that is beyond the end of the current navigation, which is impossible).

  • 0 over 3 years ago in reply to Roberto Ena

    If the device determines you are not following the loaded track, it pauses some stuff (like virtual partner and distance to end).

    Aweatherall indicated that Climbpro is based on the track.

    So, if you aren't following the track, it wouldn't be surprising if other stuff didn't work correctly.

    ====================================

    The 1030+ does determine the climbs for Climbpro for routes it calculates (when you aren't using a track file).

    I sort of doubt it keeps recomputing them when you go off course (it would be too slow).

    ====================================

    It appears other people aren't experiencing the same sort of issues.

    If that's the case, the issue might be with the user not the device.

    Don't make this more complicated that it needs to be.

    Do what other people do.

    Use a better/appropriate track.

  • 0 over 3 years ago in reply to dpawlyk
    dpawlyk said:
    Use a better/appropriate track.

    If you don't want to be constructive there is no need to follow this topic.

    As I explained, the issue is trying to set a different destination while off track.


    It has **nothing** to do with the resolution of the track.

    You are focusing on the wrong side of the problem again.

    The problem is the device partially freezing.

    What I was supposed to do? Going down 200 meters to follow the proper track to make my 1030 happy?

    If I'll be in the same situation I won't have any other option that to switch to onboard navigation.

    Is my Garmin supposed to freeze again?

  • 0 over 3 years ago in reply to Roberto Ena
    Roberto Ena said:
    If you don't want to be constructive there is no need to follow this topic.

    Some of your problems are related to using an inappropriate track.

    Roberto Ena said:
    The problem is the device partially freezing.

    The device shouldn't freeze. 

    Roberto Ena said:
    What I was supposed to do? Going down 200 meters to follow the proper track to make my 1030 happy?

    It's not likely the freezing will be fixed anytime soon (if ever). So, one thing you can't really do is rely on that being fixed. You are mostly stuck with trying to avoid the problem with the device as it is.

  • 0 over 3 years ago in reply to dpawlyk
    dpawlyk said:
    Some of your problems are related to using an inappropriate track.

    No. The track quality does not matter at all when you are not following it.

    dpawlyk said:
    The device shouldn't freeze. 

    It did, and I am happy I recorded a video, otherwise I suspect someone would not have believed me.

    dpawlyk said:
    It's not likely the freezing will be fixed anytime soon (if ever). So, one thing you can't really do is rely on that being fixed. You are mostly stuck with trying to avoid the problem with the device as it is.

    Maybe. It depends on Garmin. BTW do you own the same unit?

  • 0 over 3 years ago in reply to dpawlyk

    The 1030+ does determine the climbs for Climbpro for routes it calculates (when you aren't using a track file).

    I  doubt it keeps recomputing them when you go off course (it would be too slow).

  • 0 over 3 years ago in reply to Roberto Ena
    Roberto Ena said:
    Maybe. It depends on Garmin. BTW do you own the same unit?

    Based on experience, it takes a while for things to be fixed.

    I'm waiting on a bug to be fixed in IQ I reported months ago.

    Yes, I have a 1030+.

  • 0 over 3 years ago in reply to dpawlyk

    How do I report a bug?

  • 0 over 3 years ago in reply to Roberto Ena

    You call them up. Though, you got aweatherall to report it for you.

    My bug was in IQ. There's a forum to report bugs for that.

    ========================

    I reported 3 IQ bugs:

    • July 2020. It's status is still "ticket created". This bug was introduced in later firmware. I had to modify my IQ widget to provide a work-around for it.
    • Oct 2020. It's status is still "ticket created".
    • Dec 2020. It's status is still "ticket created". This bug was introduced in later firmware. Lots of people reported this bug. I had to modify my IQ app to avoid it.

    Based on experience, I'm confident in saying problems aren't generally fixed very quickly.

    Garmin has gotten better recently (it seems).

  • 0 over 3 years ago in reply to Roberto Ena
    Roberto Ena said:
    No. The track quality does not matter at all when you are not following it.

    If you weren't following it, why are you showing it?

    If you have an active track, the devices kind of expect you are going to return to it when you go off course from it.

    Things like distance to end and virtual partner are paused when you go off course.

    So, even if you are not following it, the loaded track is involved.

  • 0 over 3 years ago in reply to dpawlyk
    dpawlyk said:
    If you weren't following it, why are you showing it?

    I was not physically following it, but the track was loaded and it was the last track that navigation was active on (until when, I don't know).

    I hope this clarifies.