help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SDK 5.0 intermittent non response to touch

‎11-08-2020 07:03

‎11-08-2020 07:03

Is there anything in SDK 5.0 that can stop a touch zone to not respond?

 

Sometimes it works, others it doesn't.

Author | ch, passion for improvement.

Best Answer
0 Votes
1 REPLY 1

‎11-09-2020 04:49

‎11-09-2020 04:49

Is there a recognised way to define touch zones, that would give it higher priority for a response? This applies only to Sense and Versa 3. Prior models don't suffer from this problem.


Incidentally I found an interesting condition to the non response to touch.


If you swipe right and then left again the screen becomes receptive to the touch.


Could the OS 5.0 be overly sensitive, looking for this motion thereby disabling the touch [ONCLICK] detection?


It would explain why it doesn't happen in OS 4.2.


Is there a way to disable the right swipe? May be that would resolve it before the next update to the OS.

Author | ch, passion for improvement.

Best Answer
0 Votes