You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Like for the sensitivites, provide something like:
The text was updated successfully, but these errors were encountered: