| d120254f5ec511f441e5d4e8942b16068294afad |
|
02-Oct-2015 |
Andrew de los Reyes <adlr@google.com> |
am c9b39239: am 6c51a07d: am de18f6c3: InputResampling: Don\'t extrapolate for very low frame rates.
* commit 'c9b392395f3eada767cf9d1dce1eb40930ca1b95':
InputResampling: Don't extrapolate for very low frame rates.
|
| de18f6c32add6fb22065807a00ddc88b363df527 |
|
02-Oct-2015 |
Andrew de los Reyes <adlr@google.com> |
InputResampling: Don't extrapolate for very low frame rates.
In very low framerate situations, extrapolation is generally going to
either cause no benefit or make a mistake. We can safely turn it off
with no user-visible negative impact.
BUG=https://buganizer.corp.google.com/u/0/issues/24550942
TEST=Scrolled very slowly and saw mispredictions on Angler. With change,
saw the log message that the mispredictions were suppressed.
Change-Id: Ic9747d3ff098d7918047ada2ed1c2d21282c65b0
/frameworks/native/libs/input/InputTransport.cpp
|
| 0ba3db9e91d683a75af244cccfa62c8778a4c62a |
|
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
am bffbd09f: Merge "Eliminate multiple benign overflow conditions."
* commit 'bffbd09f65d3bc594d844a185d75700e8b4789eb':
Eliminate multiple benign overflow conditions.
|
| 1faef80170b71ee4162dc910bfe1aea9d7181e58 |
|
22-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Eliminate multiple benign overflow conditions.
In InputTransport.cpp, there are multiple loops in which loop
termination occurs when the value becomes zero. These termination
conditions are all written value-- > 0, which, since value is
unsigned, result in an unsigned integer overflow when value is 0.
These loops were refactored to eliminate these conditions.
Bug: 24171356
Change-Id: Ie135c4306d1f2cef2778e295242305ed5139221a
/frameworks/native/libs/input/InputTransport.cpp
|
| 7b159c9a4f589da7fdab7c16f3aefea25e0e7e4f |
|
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Revert "Revert "Add new MotionEvent actions for button press and release.""
This reverts commit 70b41ef580644fd0fe6fa9b8ac7e4a745cfb6db3.
/frameworks/native/libs/input/InputTransport.cpp
|
| 70b41ef580644fd0fe6fa9b8ac7e4a745cfb6db3 |
|
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Revert "Add new MotionEvent actions for button press and release."
This reverts commit 48a8a0e4322969e1551536d6183af3a1faa2240b.
/frameworks/native/libs/input/InputTransport.cpp
|
| 48a8a0e4322969e1551536d6183af3a1faa2240b |
|
11-May-2015 |
Michael Wright <michaelwr@google.com> |
Add new MotionEvent actions for button press and release.
Introduce ACTION_BUTTON_PRESS and ACTION_BUTTON_RELEASE as actions to
signal a button press or release. If these actions happen
simulanteously with a DOWN or UP event then they're explicitly
ordered to happen after the DOWN or preceding the UP in order to send
them to the most recently targeted view.
Also, introduce new stylus button constants that differ from the
constants we use for mouse buttons.
Bug: 20704355
Change-Id: Ib960a5004db5429ad2fc8db020704773e2978327
/frameworks/native/libs/input/InputTransport.cpp
|
| 63ff3a84ae5f60fc427aed4f63364b50695266d9 |
|
10-Jun-2014 |
Michael Wright <michaelwr@google.com> |
Fixup more potential issues / warnings in string formats
Change-Id: I323e44f950b2e758dc9ff4510b2e13ca870eb849
/frameworks/native/libs/input/InputTransport.cpp
|
| d0a4a6234f3d97f5e7fb86b028d3ee79dd4e3fa6 |
|
10-Jun-2014 |
Michael Wright <michaelwr@google.com> |
Fix warning in logging string interpolation
Change-Id: I86623083f68664d31ea277958837a4c2985037b4
/frameworks/native/libs/input/InputTransport.cpp
|
| bc6001b026069714177526eb1120b0011d6f2a51 |
|
02-May-2014 |
Narayan Kamath <narayan@google.com> |
Change InputMessage.motion.pointerSize to a uint32_t.
This ensures it's the same size in both 32 and 64 bit
processes and also brings it in line with struct
MotionEntry.
Change-Id: I66bb8b8d8664763e7dcbd489686051f563d5e1dc
/frameworks/native/libs/input/InputTransport.cpp
|
| 872db4f11e407accccba9d37c335ef7e3597eba4 |
|
23-Apr-2014 |
Michael Wright <michaelwr@google.com> |
Move key attribute information out of native.
Native doesn't ever actually care about the attributes of keys, so
move all of it up into the managed layer and move all of the key
names down so they're defined once.
Change-Id: Ic8ded13ce050b2b98744735ff50d11e8d882d7d5
/frameworks/native/libs/input/InputTransport.cpp
|
| 3223217aed6dcfa55b5b952cd6be71f70e41ba63 |
|
21-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Only consume touches up until the frame time
When resampling is disabled, it's currently possible to consume
touches after the current frame time. This breaks some guarantees and
could cause unexpected behaviors.
Change-Id: I99908a2cac2df9f795dd4a07188b4451213cf3e4
/frameworks/native/libs/input/InputTransport.cpp
|
| ad526f8505efe2ccd800e4665864b10bdae31e29 |
|
11-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Eliminate latency when resampling is disabled
Since the latency was introduced to avoid egregious errors during
resampling, remove it when we aren't resampling.
Change-Id: Ia8e9a9afb1e16212fec81a8c9c661c598e1b0ebf
/frameworks/native/libs/input/InputTransport.cpp
|
| 5912f95d26f77d2b6df13e1f2672e48e3f9b871c |
|
02-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Move input library code from frameworks/base.
Change-Id: I4983db61b53e28479fc90d9211fafff68f7f49a6
/frameworks/native/libs/input/InputTransport.cpp
|