Top drop-down menu horrible rips and lagging - can't it be fixed?

Comments

13 comments

  • Avatar
    Gregory Gregory

    I confirm. It is very irritating how badly the menu expansion from the top bar works, but also the change of screens of this menu. Usually I am not able to expand it the first time. Also, the screen that appears, after some time, seems to be random, and not the one that was last. Usually I am interested in the screen with backlight and the screen with light support. They are not next to each other and I have to scroll sideways, which also works poorly.

    1
    Comment actions Permalink
  • Avatar
    Chase Pinkerton

    It is super laggy. I usually just use the two two buttons to bring it down since scrolling has almost never worked for me 

    1
    Comment actions Permalink
  • Avatar
    James Parker

    I agree also, the swipe down is extremely poorly implemented and often I swipe again because I think the first swipe has not registered, only for the menu to appear as I am doing it and then a button is inadvertently pressed. Its a horrible process.

    1
    Comment actions Permalink
  • Avatar
    James Parker

    Any idea when this will be fixed. It’s very irritating. I tested today by swiping down multiple times and I would say the menu only appeared 75% of the time and on some occasions the screen registered a touch elsewhere without displaying the menu. Sometimes it’s just slow and other time it doesn’t appear at all.

    2
    Comment actions Permalink
  • Avatar
    Gregory Gregory

    As you can see, no one from HH has responded yet. They probably don't see any problem with it. But once they see it, they will promise to solve the problem as soon as possible, e.g. as soon as changing the radar alarm sound :)

    0
    Comment actions Permalink
  • Avatar
    Thomas Gruber

    I've never (not even on my iPhone or iPad) had a drop-down menu that works perfectly when you swipe down (or left or right). Especially in less than ideal conditions (like when riding a bike). So I always use the buttons on my Karoo (also to change pages there) and that works well for me. Yes, sometimes it lags a bit, but a one second delay isn't the world to me. And I'm always wrong about the left and right buttons, but that's my own confusion.

    Also, since there have been few replies on this topic in the last two months, it could be that this is not a big deal for most users (if at all).

     

    0
    Comment actions Permalink
  • Avatar
    Gregory Gregory

    Strange, I don't have a problem with the top-down menu on any Android phone. And it's necessary for certain things. For example, every time I start riding, I change the radar light mode to auto off because it doesn't start in the last state it was working in, nor is there an option to remember the state in the profile (why do I need a light in the forest?). If I want to manually change the backlight brightness level, I also have to do it every time from the top menu, because it always starts in auto mode. I often turn off the navigation when I'm close to home, because I know how to ride, and it beeps at me unnecessarily - I use the top menu again.

    Why don't people write? There are a few stubborn people who write :), the rest probably have already despaired when they see these topic markings - solved, planned.

    0
    Comment actions Permalink
  • Avatar
    LKerch

    The top-down menu works fine for me. It does take me a more intentional swipe than the casual flips moving between profile pages.  But after coming off the long winter season wearing gloves, I've gotten in the habit of using the buttons to access the top-down so I don't even think about it anymore.

    0
    Comment actions Permalink
  • Avatar
    Gregory Gregory

    I suggest a simple way to improve the slide-out of the top menu and bottom drawers.

    In the data screen mode and the screen with the map locked (lock closed), the gesture of swiping from top to bottom, from bottom to top across the entire screen is not currently used. The device only detects swiping directly from the edge. While riding, there may be problems with hitting the edge of the screen with your finger. Maybe the gesture is imprecise and that's why people try several times. I think that the gesture of swiping across the entire screen should be used because it is not used now. Only when someone unlocks the map (lock open), swiping across the entire screen should apply only to the map as it is now.

    1
    Comment actions Permalink
  • Avatar
    Mitja Bonca

    The top down menu is specially extremely laggy, when opening it for the very 1st time after reboot. Later on its better, but still not smooth.

    Video: https://www.youtube.com/shorts/ALKJP8hT3DA 

    --

    It would also be good to make it work like on Samsung S20 onwards (not sure for other Andorid phones), so no matter where on the screen (vertically) you swipe down, it opens the top down menu. Now you have to swipe from the very top, else it doesn't open.

    PLEASE, can that be fixed? Thx in advance.

    1
    Comment actions Permalink
  • Avatar
    Mitja Bonca

    I think the swipe-down-menu seems to be working better, smoother. But there is still some lagging when swiping it down for the 1st time after boot.

     

    And would be cool to consider if possible to implement what I said at the end of my previous post; about swiping down anywhere on the screen, not just from the very top (same as in smart phones) in order to open the drop-down-menu.

    1
    Comment actions Permalink
  • Avatar
    Tiago Miranda

    If drop-down-menu and changing pages using buttons works smooth without lags, why with touch gestures it becomes laggy? I think it can be related from capacitive detection and device response programing...hammerhead could turn it more sensitive? At least, they should come here to show us their point of view and answer!

    0
    Comment actions Permalink
  • Avatar
    Aishwarya

    Hi everyone, thanks for sharing your feedback on the top drop-down menu. 

    All of your comments and suggestions have been shared with our product teams for review. The current display sensitivity behaviour was designed to reduce accidental inputs while riding, but we understand that this experience may not work equally well for all riders and conditions. While I can’t share a specific timeline or confirm upcoming changes, please know that your feedback is noted and our team will consider this in future enhancements.

    Thanks again for taking the time to share your experiences.

    1
    Comment actions Permalink

Please sign in to leave a comment.