How do I start my ride Now

Answered

Comments

27 comments

  • Avatar
    Raymond de Jager

    press the green bar displaying 'start a ride'. It will change to 'In ride'

     

    0
    Comment actions Permalink
  • Avatar
    Jeff Smith

    Gordon, 

     

    I have seen this too, and reported it as part of the ATG. The workaround that I have found is to either turn autopause off, or when I get the blank map double click the bottom right button and then close the Ride app and start again. That seems to work for me anyway, I hope it does for you ...

     

    Best regards, Jeff

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    This trek up the highest mountain in the Brecon Beacons, South Wales, UK. After this map on Thursday last nothing after the update, please HH send me the upday from June, then I can use my Karoo.  

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    I'm afraid your wrong Raymond De Jager, any ways I can't be bothered with trying o trying that way, it should work as it did a few weeks ago or better still three months ago. 

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    The upper was from Thursday, Wednesday I was Down hill riding at Bike Park Wales but Tuesday I rode the Port Tennant canal to Neath then after lunch I carried on up The Neath canal, as these screenshots of the recorded maps show.  As you can see my auto pause worked fine as I leave it on all the time.Starting from Swansea.

     Lunch plus the ride around the town.

    As you can it worked perfectly over the last few days until the new update this last Thursday.

    After this rubbish.

    0
    Comment actions Permalink
  • Avatar
    Jonathan Hill

    I just had the same thing.  Tried first ride on the latest update (270.3) this afternoon and had the blank screen.  Pressing buttons and trying the green bar at the top did nothing.  Only way to get it to work was to double click bottom right button and kill the ride app and then start the ride again.

    I don't understand that If it was reported by the ATG why was it not resolved before the latest release, or at least have some notes with the latest release for a workaround? It delayed my ride as i kept rebooting the Karoo until out of pure chance I killed the ride app to get it to work.

    0
    Comment actions Permalink
  • Avatar
    Nnovod

    If this was reported by ATG and nothing was done about it then I don't understand what ATG is about.  Has the software ever been changed between being sent to ATG and general release?  What is the purpose of ATG?

    0
    Comment actions Permalink
  • Avatar
    Gilles muoy

    A solution for the black screen issue was brought in the FB forum: simply swipe down and toggle the dark theme on/off. 

    I also noticed that this issue only happens if we start the ride app immediately after powering on the unit, if you wait a (couple) dozen seconds before firing the app, chances are you won't notice the issue anymore.

    regarding the new start sequence, I find it less confusing to use a long press on the ride app icon and use the top right physicak button to start recording the ride. This is a bit faster as it skips the "add route" dialogue and "start" button, and the physical button is actually easier to press than the green bar on top.

    2
    Comment actions Permalink
  • Avatar
    Ali

    This was reported by the ATG and although it could not be fixed before the release, it was helpful to catch this with the help of ATG users, the fix is being worked on. As a workaround, you may want to add the route after the ride starts or try toggling between the light theme and dark theme.

    0
    Comment actions Permalink
  • Avatar
    Nnovod

    Hi Ali,

    Thank you for the response.

    For such an important bug I think it's appropriate to delay the release and incorporate a fix before the entire user community has to deal with the problem.  If the ATG is simply used to find bugs a few days earlier there's really not much purpose to it.

    Regards,

    Nathaniel

    0
    Comment actions Permalink
  • Avatar
    Jeff Smith

    I think it is a difficult balancing act to decide on whether to hold a release.

    However, what would have been good, if the bug couldn't be fixed before release, would be to add it to the bug list / to be fixed list on the release notes, and to show the workaround.  That way, people are warned and have a way of easily dealing with it.

    2
    Comment actions Permalink
  • Avatar
    Nnovod

    Yes, it's a difficult balancing act, but it seems that the decision to plow forward with the release is always taken.  Battery life was made significantly worse by the monitoring during pauses - that's still not fixed.  The way to start a ride is now complex - the little green bar is still there.  Now starting a ride is even more complicated: 1)Say to start the ride.  2)Say again to start the ride.  3)Use the workaround to reset the themes to say you want to see your ride.

    It's making some nice additions look ugly and once these problems are introduced it can take a long time for them to be fixed.

    0
    Comment actions Permalink
  • Avatar
    Gilles muoy

    yup Jeff: a "known bugs" and "known workarounds" section would have saved a lot of trouble for this release...

    I couldn't help but notice though that a surprisingly high amount of users apparently didn't read the release notes from 2 weeks ago... I had to help a couple users on the FB forum who didn't notice the start sequence had changed and thought their unit didn't record due to a bug!

    something should be done in order to make such changes more obvious when they occur... maybe a popup on the website or something: people have a tendency to discard emails pretty fast (and that's when the email they gave Hammerhead is the one they use!)

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    Why cant HH send a text message on the Karoo?

    0
    Comment actions Permalink
  • Avatar
    Ali

    I  agree with you all that the known issues being worked on or reported should be highlighted with the release and as we cannot include everything on the blog, we had a discussion to update our forum on these. Let me know if that would be better and any suggestions from you guys will be further discussed tomorrow with the team.

    0
    Comment actions Permalink
  • Avatar
    Gilles muoy

    Notes on forums would obviously be a plus... but I feel that some users might miss them.

    That's basically why I think a popup or notification on dashboard (or on Karoo's screen as Gordon Davies suggests) could be a solution... even if that popup is just a link to a the release notes or a forums post...

    0
    Comment actions Permalink
  • Avatar
    Nnovod

    I think the release notes are the best place, but a one-time popup on the Karoo itself that outlines what has changed would be a big plus.

    Also, I still think that HH should be less hesitant to hold back a release (or at least individual features in the release) if there's a significant bug.  To me the battery consumption bug from a few releases ago and the latest blank screen problems merit waiting for fixes.

    Thanks,

    Nathaniel

    0
    Comment actions Permalink
  • Avatar
    Ody

    Hi Ali,

    Releasing an update with a "known bug" is a very unprofessional decision, specially a major issue like this. Either do not release the update or delay it until a fix is done. This has impacted and frustrated everyone.

    Of course, we will see a reply that you understand our frustration, but sending this out does not seem like you do.

    Since this is an urgent issue, I hope HH prioritize resolving and sending out a fix without waiting for the scheduled update.

    When are we going to be able to use the device straightforward without going through workarounds?

    0
    Comment actions Permalink
  • Avatar
    Gilles muoy

    I fear I have to agree with Ody here: even though the bi monthly updates are probably well received by some users who consider regular updates a good thing, what we actually get is a continuous stream of barely tested updates... at the end of the day, everyone is a beta tester...
    But what about those of us who would prefer to update only once they're sure we have a stable release without any bugs ?

    also, I really think beta testers should be able to interact in a dedicated part of the forum between one another. Some bugs are actually quite complex to identify and it'd be nice if we could share our findings and ask for other's help somewhere... that's not a public forum.

    right now, we are all beta testers and discussing the issues on facebook or on this very forum... great for transparency, but not sure if it's really in Hammerhead's interest really...

    0
    Comment actions Permalink
  • Avatar
    Nnovod

    Ody and Gilles, I agree.  For the blank screen bug in the latest update HH should seriously consider an immediate patch (without the addition of any other features).  Take a look at https://karoousers.org/viewtopic.php?f=2&t=411 to see the discussions this is generating.  It seems only a matter of time before everyone will hit this problem (see JohnJ80's comments in the thread).  In general it appears that the use of global memory in the code has always been a problem.  I've experienced problems as well that only seem possible if global/shared memory is getting corrupted.

    0
    Comment actions Permalink
  • Avatar
    Steve Hammatt

    I agree, this should have been in the release notes, and it makes a complete nonsense of the "Bug Fixes in progress" section that it wasn't there. Perhaps there should be a separate "Known Issues" section?

    I also agree that when an update is installed (or perhaps as part of the notification that a new update is available), the release notes should pop up on the Karoo itself.

     

    0
    Comment actions Permalink
  • Avatar
    Ali

    Thanks everyone for your input here. I will have the discussion today and pass it on to the team. Although, it might take some time for the software team to work on implementing these release notes on Karoo as it is their decision. However, from the communications point of view, I really like all your ideas and let's see what would be the best for everyone.

    Thanks once again.

    0
    Comment actions Permalink
  • Avatar
    Jeff Smith

    Steve's summary is how I feel too.

    The key thing here is to accurately describe what is known not to work, and (where possible) clearly describe the workaround.

    You need to get the basic information about known issues complete and clear, make sure that is in the release notes emailed to all owners and  on the web site, and then add the nice part of the release notes popping up on the Karoo itself when the software engineers have the time.

    Maintaining fully useful release notes isn't too hard to do, though it is tedious I know.

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    I find pressing the green bar is gets no action at all, please remove that, the button would be better if that worked strate away.

    0
    Comment actions Permalink
  • Avatar
    Gordon Davies

    Tried twice this morning, on a ride into town not recorded, so tried a new ride recording,  no mileage. It is just way to complicated  a start up.

    0
    Comment actions Permalink
  • Avatar
    Jeff Smith

    I agree.  I have said it before, the user interface design is very poor, inconsistent, and confusing.

    Life doesn't have to be this convoluted, even in 2018...

    0
    Comment actions Permalink
  • Avatar
    Brent T

    I searched the forums for this issue, not sure why I couldn't find anything until after I sent a message to support (just submitted), but I agree, to give a release with a known bug (especially this significant) does not do anything for HH credibility.  They have held releases before.   This bug is very very frustrating, I wish I knew of the them toggle to get the screen to display, that is at least a work around that is manageable.

    I also got a reply to another that the release notes cannot be all inclusive, I ask WHY?  The blog post announcing the new release should be shorter, but there should be an all inclusive patch and new feature list for each release.  We have found out about new functionality only when something doesn't work correctly, then the response "this is by design" or something.  Come on HH, stop keeping us in the dark.

    0
    Comment actions Permalink

Please sign in to leave a comment.