| f8c4add85188a90940d9d7045ab4c945375fcff2 |
|
08-Jun-2017 |
Selim Cinek <cinek@google.com> |
Fixed an issue where the notification could stay userlocked
When collapsing the shade while draging down (using fingerprint)
notifications would stay userlocked and would appear in a small
height instead of their regular size.
Test: runtest -x packages/SystemUI/tests/src/com/android/systemui/statusbar/phone/StatusBarWindowViewTest.java
Change-Id: Ibd97a6ce063bc2fcd76f11e010e781a61bd76b5f
Fixes: 36469584
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| e549a8d62108c7c7dabedbf4e77b9a653781723b |
|
15-May-2017 |
Jorim Jaggi <jjaggi@google.com> |
Optimize latency when unlocking phone
Latency when unlocking the phone regressed a bit for two reasons:
- For lockscreen -> app we now have to create a full starting
window containing the snapshot, while previously this was just
showing a surface.
- For lockscreen -> home, we can't use the saved surface anymore
because currently we don't support snapshotting translucent
activities. However, in the long term, we want home screen to be
more involved into transitions anyways, so we'll have to wait for
the first frame draw anyways.
However, crystal ball trainee developer Jorim added some
artificial latency in this transition 3 years ago, because he knew
that it is going to be an issue at some point so we have some
headroom to improve! Genius! On a more serious note, it was because
he didn't understand how to read systraces with binders involved (to
be fair, there was also no binder tracing).
Now, we can completely fix the introduces latencies above by
removing this latency of 100ms, and we are 30-70ms better than
before! However, this requires a lot of discipline in SystemUI.
Currently, the callback to dismiss Keyguard takes around 30ms. By
moving all non-essential binder calls of the main thread or to the
next frame, we bring this down to 5ms, such that window animation
and Keyguard animation starts about at the same time.
Test: Take systrace, unlock phone...profit!
Fixes: 38294347
Change-Id: I481fe4ecf358ed09f7142dd9e7ecd290b53c500c
Merged-In: I3ea672bc2eca47221bc6c9f3d7c56b6899df207d
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 8e291a5d3f6f90072ed91887359567d5640f6170 |
|
10-Dec-2016 |
Adrian Roos <roosa@google.com> |
FalsingLog: Fix false positive Log.wtfs
Fixes a frequent case where we do not get notified immediately of the
screen turning on and log a WTF as a result when a touch makes it
through to the lockscreen.
Change-Id: I5437aa0283d78624ffb3a43404e7248b7e91372c
Fixes: 32575746
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 9f0b002ecfe68508354f9c023a09cf360666df9e |
|
10-Nov-2016 |
Adrian Roos <roosa@google.com> |
Lockscreen: Restrict double taps to prevent falsing
Further restricts the second tap on ActivateableNotificationView
such that it must occur no further than 0.2in from the first tap.
Bug: 32766052
Change-Id: I033c1abc64c815d519153ced23ac9751471b1d05
Test: Tap notification on lockscreen. Verify that second touch is only accepted near the first tap
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 7bb38a941b056e8e7cb41151d927313ec6c138d5 |
|
21-Jul-2016 |
Adrian Roos <roosa@google.com> |
HIC: Add report facility for overzealous anti-falsing
Bug: 27405075
Change-Id: I15e5d601af3c7cc067371bbe51c873d2ce15ec83
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| ca664b93b91ee4c29b22e914c01411c241f5068e |
|
18-Apr-2016 |
Adrian Roos <roosa@google.com> |
Disable anti-falsing logic with touch exploration
Change-Id: Ide1992f11ace9c2604f68fe3c9277c3e20ecb71a
Fixes: 28140321
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 3021f44d9ebe43e5083abd83799e8eb9a67a3a57 |
|
08-Apr-2016 |
Adrian Roos <roosa@google.com> |
Fix early session termination in FalsingManager
Now we properly wait until the status has changed
from Keyguard to Shade.
Bug: 27754935
Change-Id: I1b09130965a196ec20f6982d1ac3e4d1d2b2e2a3
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 6a04cb1efc4a6cfd6733d92c0c7efca5f9082e5d |
|
15-Mar-2016 |
Adrian Roos <roosa@google.com> |
Prevent Log.wtf crash in benign case
Fixes a crash that happens when you turn of the screen
while moving the finger. Some touches still come in even
when the screen went to sleep. No need to get upset over
those.
Bug: 27595423
Change-Id: If75ae3b6c2c83a87f38daaf8777f89d8c74a9cd1
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 401caaedd871894620accc1d14592c08095b5523 |
|
04-Mar-2016 |
Adrian Roos <roosa@google.com> |
Fix bug and add logging in FalsingManager
Fixes bug that lead FalsingManager to be incorrect
about the screen on state.
Makes it a fatal error to query whether a touch is
falsing outside of an active session.
Prevents touch collection and logging on the locked
shade which needs no anti-falsing.
Bug: 27227578
Change-Id: I8e330ad28636156a952e61b8fe6a3d201f82e624
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| c5584ceaad422c96f978132aee4d21ee1f61fc7d |
|
24-Feb-2016 |
Adrian Roos <roosa@google.com> |
Fix anti falsing detection
The falsing detection stopped listening for touches
when the lockscreen showed without turning the screen off.
This happens e.g. when SystemUI crashes, when switching users,
when ending lock-to-task.
As a result, the falsing detection usually got stuck on a bad
value and without further touches continued preventing all input.
Bug: 27227578
Change-Id: I6717c04b0271e4d2578b88fc584b6ad46492e497
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 6dc59b48c040cf6871d7ff6d8e5242b1a5ddd032 |
|
23-Sep-2015 |
Blazej Magnowski <johnasselta@google.com> |
Integration into other unlock mechanisms
Replaces all the older falsing thresholds unless the
HumanInteractionClassifier is disabled.
Change-Id: Idfc3cb1b6bc0bbdbc792cd75499f0c3b4f1b7142
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 9f01c5bfa5c1c63e350808c154adfc2953949b15 |
|
18-Sep-2015 |
Blazej Magnowski <johnasselta@google.com> |
Add HistoryEvaluator
Adds the possibility to store the evaluations for previous strokes and gestures.
Also and enables to take the history into account when classifying current
interatcions.
Change-Id: Ia8fa54a00daa80b4e5aebf11b11b568ed23165d4
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|
| 0e2ffbd48bbedf47deb7f6aed96bd07e2fc96f53 |
|
10-Sep-2015 |
Blazej Magnowski <johnasselta@google.com> |
Add FalsingManager and Classifier to SystemUI
Adds the possibility to analyze and classify touch and sensor events as
human or false touches.
Change-Id: I5079c02406d532fea38ca2d302e8606effae0696
/frameworks/base/packages/SystemUI/src/com/android/systemui/classifier/FalsingManager.java
|