| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Ignore the closing MotionEvent of swipe gestures for falsing | András Kurucz | 2023-03-03 | 1 | -1/+1 |
| | | | | | | | | | | | | | The ZigZagClassifier falsly reports some swipes as false touches. The reason for that is in our touch event stream. The closing ACTION_UP event of a swipe might be a bit offseted from the previous ACTION_MOVE event and sometimes it is just enough to push us over the allowed tolerance. In this fix we drop the gesture closing ACTION_UP event if it is close in time to a previous ACTION_MOVE event. Fixes: 236197248 Test: atest swipe notifications on the LS and observe the FalsingManager logs Test: atest SystemUI:com.android.systemui.classifier Change-Id: I33093ff77fd23a2913bd3adfd79a15e3ae66b316 | ||||
| * | Fix unbounded MotionEvent growth in Falsing | Dave Mankoff | 2021-03-04 | 1 | -12/+0 |
| | | | | | | | | | | | | | | | | | | We were keeping an unbounded list of MotionEvents inside of the FalsingManager. Generally, this list should have shrunk itself periodically, but in practice it only shrank itself when someone double taps a notification. Meanwhile, we weren't even using the data in the list! With this change, we only keep the current and prior list of MotionEvents - the ones we actually use. The list of historical events is removed, so the leak goes with it. Fixes: 177329773 Test: atest SystemUITests && manual Change-Id: If8bfeea944850d972434915018b5bbfb3acb80e4 | ||||
| * | Add Tests for the BrightLineFalsingManager. | Dave Mankoff | 2020-12-01 | 1 | -0/+254 |
| Sets up some more dagger injection and removes all the "new Classifier(...)" from its constructor, allowing them to come from outside. Bug: 172655679 Test: atest SystemUITests Change-Id: I916de7d5ee60ec2183c6401ec222867fc5eff823 | |||||
 |
index : frameworks_base.git | |
| frameworks_base |
| summaryrefslogtreecommitdiff |