question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`double_tap` as a card-level action does not work on Android

See original GitHub issue

Checklist:

  • I updated to the latest version available
  • I cleared the cache of my browser

Release with the issue: Double tap doesn’t perform action fullscreen on android Fully Kiosk when it’s used with different provider but frigate-jsmpeg.

Last working release (if known):

Browser and Operating System:

  • Fully Kiosk 1.45-play
  • Galaxy Tab A7 (SM-T500)
  • Android Version 11 (SDK 30)

Description of problem:

Double tap action on card in Fully Kiosk Browser doesn’t perform fullscreen action when it’s used with different provider but frigate-jsmpeg. It performs fast forward or backward depends on area of touch.

Yaml config:

type: custom:frigate-card
cameras:
  - camera_entity: camera.garage
live:
  actions:
    double_tap_action:
      action: custom:frigate-card-action
      frigate_card_action: fullscreen
  controls:
    thumbnails: {}
    next_previous:
      style: none

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
dermotduffycommented, Feb 9, 2022

Investigated this some more. All 3 providers work reliably for me on Chrome, Firefox and Safari on desktop. On Android, only JSMPEG works with double_tap – this seems to be because the Android HTML5 video player (which is used for both frigate and webrtc providers) appears to swallow the double tap interaction to rewind & fast forward.

I cannot find a way to stop Android doing this.

Workaround suggestions:

  • Use hold instead of double_tap (appears to work on all platforms).
  • Use a menu or picture element icon instead of double_tap.
0reactions
grimmalduscommented, Feb 10, 2022

Workaround suggestions:

  • Use hold instead of double_tap (appears to work on all platforms).
  • Use a menu or picture element icon instead of double_tap.

Yea I think I have to will implement these workarounds didn’t know about the hold maybe that will do the thing. I think since there is no fix for it now it can be closed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

DoubleTap in android [duplicate] - Stack Overflow
I found a fix to be able to pass the context. Add this to the onCreate(): final Context context = getApplicationContext(); Then pass...
Read more >
Pixel 7 Pro Double Tap stopped working : r/android_beta
Pixel 7 Pro Double Tap stopped working. I have the "Gestures - Double Tab back" of my P7P set-up to open the camera...
Read more >
Here's how to add Android 11's double-tap gesture to any phone
To set it up, open the Settings app and find the System section. Then select gestures and choose your Quick Tap preference.
Read more >
How to Set up Android 12's Double-Tap Gesture - Lifewire
Open the Settings app. · Tap System. · Select Gestures. · Tap Quick Tap (or Quick tap to start actions on Android 13)....
Read more >
Double tap on back of device gesture from Android 12 port ...
Tap, Tap is a port of the double tap on back of device gesture from Pixels running Android 12 to any Android 7.0+...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found