Log device bus for keyboard metrics
Since the same vendor ID could mean different vendors depending on whether the device is connected over bluetooth or USB, we require to know the device bus to disambiguate the vendor IDs. Also fixed some formatting issues. Bug: 308918242 Test: atest InputTests:KeyboardMetricsCollectorTests Test: atest ShortcutLoggingTests Change-Id: Id96d86242ab239c7df0efe74bf13fb97eb97f482
Loading
Please register or sign in to comment