Lines Matching refs:FalsingManager

12 The `FalsingManager` tracks all touch interactions happening on a phone's lock screen.
15 minimum, inform the `FalsingManager` of what touches are on touch targets vs not (things that may be
16  intentional). If you do not tell the `FalsingManager`, it will assume touches on your feature are
21 `FalsingManager`, however more granular tracking will result in better results
24 You can _act_ on the results of the `FalsingManager`. Instead of only telling
25 the `FalsingManager` that touch events were on touch targets, you can further use the
33 2. The `FalsingManager` makes a note of all of the `MotionEvents`.
37       the `FalsingManager`.
43     * If the `FalsingManager` says it looks good, respond to the touch.
44 4. The `FalsingManager` checks to see if anyone queried about the gesture. If not, mark it as 
47 There is also an event fired by the `FalsingManager` that can be listened to by anyone, that 
48 indicates that the the `FalsingManager` believes the phone is actively being pocket-dialed. When
54 The `FalsingManager` maintains a recent history of false analyses. Using
61 Changes in belief may influence internal heurstics within the `FalsingManager`,
68 The methods below inform the `FalsingManager` that a tap is occurring within an expected touch 
73 `FalsingManager#isSimpleTape()`. This method
76 you probably want `FalsingManager#isFalseTap` method for most cases.
78 `FalsingManager#isFalseTap(@Penalty int penalty)`. This
79 method tells the `FalsingManager` that you want to thoroughly validate a single tap. It
87     the tap is **accepted**. This works exactly like `FalsingManager#isFalseDoubleTap`.
99 The `@FalsingManager.Penalty` values are fairly straightforward, but note that you
108 `FalsingManager#isFalseDoubleTap()`. This method tells the `FalsingManager` that
112 Note that `FalsingManager#isFalseTap(boolean robustCheck, double falsePenalty)`
118 `FalsingManager#isFalseTouch(@Classifier.InteractionType int interactionType)`.
127 `FalsingCollector#avoidGesture()`. Tell the `FalsingManager` to pretend like the
133 forcefully telling the `FalsingManager` to wholly pretend the gesture never
136 FalsingManager. Falsing works better the more behavior it is told about.
140 Please try to call the `FalsingManager` only once per gesture. Wait until you
141 are ready to act on the owner's action, and then query the `FalsingManager`. The `FalsingManager`
145 The `FalsingManager` does not update its belief in pocket-dialing until after a gesture completes.
151 accordingly. Figure out which `FalsingManager` method you need to call first, rather than relying
152 on multiple calls to the `FalsingManager` to act as a sieve.
191 method allows you to directly change the `FalsingManager`'s belief in the state
201 value of `0` would make no change in the `FalsingManager` and should be avoided
206 avoid recording those gestures in the `FalsingManager`, but we have the pattern input update
207 the `FalsingManager` directly in some cases. If the owner simply taps on the pattern input, we 
217 Again, useful on password inputs where the FalsingManager is avoiding recording
223 If the `FalsingManager`'s belief in falsing crosses some internally defined
229 `FalsingManager#addFalsingBeliefListener(FalsingBeliefListener listener)`.