Jeff Brown ef3a823482 Fix bug where home presses were not poking user activity. ... We now poke user activity twice: once upon dequeueing an event for dispatch and then again just before we dispatch it. The second poke is to compensate for the fact that it can take a few seconds to identify the dispatch target (if the application is responding slowly) but we want to keep the display from going to sleep for X amount of time after the app gets a chance to actually receive the event. This mirrors pre-Gingerbread behavior. Removed some unnecessary code that filters user activity pokes when sending events to KeyGuard. We don't need this because KeyGuard already tells the power manager to disable user activity. Bug: 3101397 Change-Id: I8c3a77601fdef8f584e84cfdd11aa79da0ff51db		2010-10-18 14:50:13 -07:00
..
tests
Android.mk
EGLUtils.cpp
EventHub.cpp
EventRecurrence.cpp
FramebufferNativeWindow.cpp
GraphicBuffer.cpp
GraphicBufferAllocator.cpp
GraphicBufferMapper.cpp
GraphicLog.cpp
Input.cpp
InputDispatcher.cpp	Fix bug where home presses were not poking user activity.	2010-10-18 14:50:13 -07:00
InputManager.cpp
InputReader.cpp
InputTransport.cpp
IOverlay.cpp
KeyCharacterMap.cpp
KeyLayoutMap.cpp
KeyLayoutMap.h
MODULE_LICENSE_APACHE2
NOTICE
Overlay.cpp
PixelFormat.cpp
Rect.cpp
Region.cpp