| commit | 6fde6fdaeec8041a43e1ce246b282c55613302c5 | [log] [tgz] |
|---|---|---|
| author | Trevor Bunker <trevorbunker@google.com> | Mon Aug 29 16:51:44 2016 -0700 |
| committer | Trevor Bunker <trevorbunker@google.com> | Mon Aug 29 16:54:09 2016 -0700 |
| tree | 7781435032ee456d1eaa4a9591a9617684e6b807 | |
| parent | 53f371991d675d737c264f5a89fcfa963cc72d76 [diff] |
ams_tmd2772: adjust proximity thresholds A small number of devices were right on the boundary of the threshold, so it would lead to a state where the device got stuck at "near". The problem would have been solved with factory calibration, which was not performed. Bug: 29872242 Change-Id: I53e152d030b3d7e25de5bb88d80f4eac8da7e6cf