diff options
| author | Philip Milne <pmilne@google.com> | 2013-04-23 14:31:23 -0700 |
|---|---|---|
| committer | Philip Milne <pmilne@google.com> | 2013-04-23 15:28:18 -0700 |
| commit | 3c647d23e5e00b5663f344b7c3f0ab38d74cf720 (patch) | |
| tree | a35aef11a61302ef6241593c115339cae1f4203e /core/java/android/view/DisplayEventReceiver.java | |
| parent | 22a3344cda1a3dcf4f719e0685c5d06155922c29 (diff) | |
| download | frameworks_base-3c647d23e5e00b5663f344b7c3f0ab38d74cf720.zip frameworks_base-3c647d23e5e00b5663f344b7c3f0ab38d74cf720.tar.gz frameworks_base-3c647d23e5e00b5663f344b7c3f0ab38d74cf720.tar.bz2 | |
Fix for bug 8578258.
The fix in:
https://googleplex-android-review.googlesource.com/#/c/300346/
worked but the constant used had an extra trailing zero - which was confusing
and put a 1 in the 'flag' space of the measurement spec.
The intended number was:
0x00800000
Unfortunately, this intended constant doesn't fix this bug.
The constant submitted in this fix is:
0x00010000
which is outside the 'flag' space of measurement specs and appears to steer clear of overflow
problems in the scenario of this bug.
As suggested in the submission above, it would be preferable to rework of the RTL code to avoid
the use of such a constant as it seems very unlikely indeed that any choice of integer can
avoid problems in all cases.
Change-Id: I0c6744257ef2aebe8dbc8c041a447f9b90ee4b84
Diffstat (limited to 'core/java/android/view/DisplayEventReceiver.java')
0 files changed, 0 insertions, 0 deletions