VivoActive clock screen coming up during onhold event

Former Member
Former Member
Is there a way to disable the clock screen from appearing during an onhold event?

Ie. press the screen for approx 1 second and the clock screen appears over of the current view, interfering with the event.

I've only seen it on the vivoactive.

It's breaking some functionality and would love if there were a way to disable it.

Thanks
Joel
  • Pressing the screen and seeing the clock is actually part of the design - that way you can see the time while in an event, or swipe and access things like the music control widget, virb widget, etc.

    If you don't want to see it, don't press the screen! On the va, the back button or start button will take you back to the activity right away, or it will time out and go back in a few seconds.

    If it's breaking something in your app, look at what you're doing for onHide() and onShow(). Things like getting a notification while running your app will also occur, so it's something you'll need to handle.

    My guess is you're doing something in onShow() you only want done once - but it gets called whenever your view is shown after it is hidden (like when the clock pops up with the press). In the simulator you can force onShow or onHide to test stuff..
  • Former Member
    Former Member over 10 years ago
    Hi Jim,

    I understand that the functionality is built-in, thanks. The OnShow/OnHide usage patterns are not the problem.

    I am using the OnHold and OnRelease methods within the InputDelegate. You would think that if they provided such methods they could work without interference.

    I have created a number picker functionality that if you hold the screen it will increment a little faster. Problem is that the clock turns up, then you have to close it, and the OnRelease event is missed so the incrementation continues as if you never let go of the screen.

    Anyway I've just added a method to cancel the hold after 1.5 seconds. Stupid workaround but what can you do.
  • Former Member
    Former Member over 10 years ago
    Double check your return value from the onHold event. Make sure you are returning 'true' to tell the system you used that event. If the VivoActive is still exiting to the clock when you do that, let me know and I will ask the VivoActive team about it. I'm not sure what the designed behavior is.