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

Make polling intervall configurable #12

Open
kuleszdl opened this issue Nov 19, 2014 · 2 comments
Open

Make polling intervall configurable #12

kuleszdl opened this issue Nov 19, 2014 · 2 comments

Comments

@kuleszdl
Copy link
Contributor

Like for the sensitivites, provide something like:

  • very often (most secure but highest battery drain)
  • often
  • ...
  • very rarely (less secure butlow battery drain)
  • custom
@SyntaxBlitz
Copy link
Owner

The biggest problem here is that polling does not directly correspond to security. Lower polling rates will sometimes trigger and sometimes won't, depending on the phase of the polling and the precise moment that the pluck takes place. This will probably just lead users to use lower thresholds when the polling rate is low to compensate for that, but this would probably lead to frustration if normal-usage jolts end up in phase with the polls.

Older versions of the OS only have four polling rates: SENSOR_DELAY_NORMAL (5 times/sec), SENSOR_DELAY_UI (16.7 times/sec), SENSOR_DELAY_GAME (50 times/sec), and SENSOR_DELAY_FASTEST (as quickly as the phone will allow). Right now, I'm using SENSOR_DELAY_UI, and it seems to work ok. SENSOR_DELAY_NORMAL is just about completely too slow, and SENSOR_DELAY_GAME's battery drain is insane (especially while #3 is a problem).

Starting in OS 11 (the minimum supported currently is 9), this is configurable down to the approximate microsecond; I need to figure out a good way to show the correct options to the user.

Still, I don't think the range should be too widely configurable, otherwise users will set their thresholds unsatisfactorily. If anything, this should be an advanced setting.

@kuleszdl
Copy link
Contributor Author

Okay I see. Well then I would suggest to still make this configurable, but with some "DANGEROUS" hint and an extra popup. So people who want can still do it, but others will stay away from setting this.

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

2 participants