Break down input device usage by uid
When InputDispatcher notifies that there is an interaction between a device and UIDs, track the usage of the input device by UID. Since Dispatcher calls the policy from its own thread, we use an AtomicQueue to hold the requests until we process the usages again from the Reader thread. Bug: 275726706 Test: atest inputflinger_tests Test: statsd_testdrive Change-Id: Ic4aae4bce7d3779adf23309973b964461bd92e7e
Loading
Please register or sign in to comment