K2 Reboot Issue Status?

Answered

Comments

5 comments

  • Avatar
    Ali

    Hi Darrell, We do not consider the issue as fixed and it is still under investigation. Not all the root causes have not been identified, so we do not have a proper fix right now. As stated earlier, this is still the priority and set of people working and dedicated in identifying the problem. As soon as we find the problem, we will immediately push out the fix in a release.

    0
    Comment actions Permalink
  • Avatar
    Darrell McCombs

    Ali if HH considered this an important Priority you would pull developers/analysts from the New Features work and focus on this critical bug.  When HH does not put out any Reboot fix on a release, yet HH does put out numerous new features (of minor importance), it's clear that the Reboot fix is not a High Priority to HH.

    HH priorities are really screwed up.  I guess I need to sell my Karoo.  If HH doesn't consider basic reliability a crucial focus, then I don't want this rebooting POS on my bike.  Why should we have to play Reboot Roulette?  Why should we have to run our old garmin to be sure to get our rides recorded?  

     

    -1
    Comment actions Permalink
  • Avatar
    Anna Ronkainen

    My hunch would be that the number of users impacted by this is relatively small and the crash sounds like it is triggered by some unique combination of whatever that makes it difficult to reproduce for the developers. One way forward might be for HH to swap a couple of units for new ones to get some problematic specimens for closer examination...

    1
    Comment actions Permalink
  • Avatar
    M L

    Perhaps email the chipset manufacturer and complain on HH's behalf?

    -1
    Comment actions Permalink
  • Avatar
    Brett Mulqueen-Ducker

    Come on, some sort of update on this, as Darrell says it's not really a good solution to go and buy a Garmin until the issue is resolved?

    0
    Comment actions Permalink

Please sign in to leave a comment.