Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demo code can't detect touch/tap/double-tap gestures with official Flick case #29

Open
srcshelton opened this issue Dec 29, 2017 · 6 comments

Comments

@srcshelton
Copy link

The official Flick case, used closed, increases the minimum separation between the Flick HAT and the user's finger, and so the demo code isn't able to detect touch, tap, or double-tap events.

It would be helpful to add an on-screen notice and a simple user-editable flag to the demo code to account for this separation and allow the demos to fully work when the official case is used.

@shawaj
Copy link
Member

shawaj commented Dec 29, 2017

Thanks for posting this :-)

We have actually been thinking about a way to solve this for a while. Think it may require a firmware update because actually the gesture detection is hard coded into the MGC3130 chip. I am not 100% sure whether you can alter how these function.

We will investigate. Adding in @francesco-vannini and @tvoverbeek to see if they have any wise ideas (they usually have more than me!!)

@checkerap
Copy link

any updates on this, it's been a year and I just picked up a new Flick board, same thing happens. tap, double tap are not working when the board is covered, tap it is somewhat works without a cover, double tap not that much, very unreliable/useless.

@shawaj
Copy link
Member

shawaj commented Dec 2, 2018

If you need to use specific functions more accurately, the best way is to build a custom GestIC firmware yourself, deactivating the gestures you don't need. This makes the ones you do need more accurate.

This is not a bug but just the nature of a chip like this.

@shawaj shawaj closed this as completed Dec 2, 2018
@tvoverbeek
Copy link
Collaborator

Just wondering if when using a 3B or 3B+ the on-board WiFi and Bluetooth disturb the electric field used by the Flick to detect gestures, taps, etc.

@shawaj
Copy link
Member

shawaj commented Dec 3, 2018

@tvoverbeek that could definitely occur but I'm not sure how much this would reduce sensitivity. But I'll reopen the issue and loop microchip in via email to see what they think.

The case can definitely reduce sensitivity though. I've also had a thought that maybe we can force the firmware to detect the tap gestures at a Z height other than 0 - or recalibrate the 0 position somehow. Will also discuss with microchip

@shawaj shawaj reopened this Dec 3, 2018
@checkerap
Copy link

@shawaj understand the limitations, I may have misread the ads, I thought all gestures except touch are "3d air-based". I was hopping to use the tap as an "enter/click" type event. would be great if the firmware can be adjusted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants