{"push_id":952249598,"size":3,"distinct_size":3,"ref":"refs/heads/bacon-par-6.0","head":"f83ba3bcfb048473e30958417d44253653412dd2","before":"c020322ba3117c9927083c8a3f3c2c7b5986d19f","commits":[{"sha":"9d153fd84744f915991b8dc0b74679f2ece659cf","author":{"email":"60c6d277a8bd81de7fdde19201bf9c58a3df08f4@derhofbauer.at","name":"Alexander Hofbauer"},"message":"Dispatch keys to a device specific key handler\n\nInjects a device key handler into the input path to handle additional\nkeys (as found on some docks with a hardware keyboard).\n\nConfigurable via overlay settings config_deviceKeyHandlerLib and\nconfig_deviceKeyHandlerClass.\n\nChange-Id: I6678c89c7530fdb1d4d516ba4f1d2c9e30ce79a4\n\nDeviceKeyHandle: The device should consume only known keys\n\nWhen the device receive the key, only should consume it if the device\nknow about the key. Otherwise, the key must be handle by the active app.\nAlso make mDeviceKeyHandler private (is not useful outside this class)\n\nChange-Id: I4b9ea57b802e8c8c88c8b93a63d510f5952b0700\nSigned-off-by: Jorge Ruesga <jorge@ruesga.com>\n\nDeviceKeyHandler : Allow handling keyevents while screen off\n\nSome devices require the keyevents to be processed while the screen\nis off, this patchset addresses that by moving the filter up in the call\nhierarchy.\n\nChange-Id: If71beecc81aa5e453dcd08aba72b7bea5c210590\nSigned-off-by: Louis Popi <theh2o64@gmail.com>","distinct":true,"url":"https://api.github.com/repos/AOSParadox/android_frameworks_base/commits/9d153fd84744f915991b8dc0b74679f2ece659cf"},{"sha":"289d780c82f04b77031aa15c4d3d43f9b4c01cea","author":{"email":"4bceda912b479e46f041c22bcc2c9ed75fe8d5cc@web.de","name":"Danny Baumann"},"message":"Add PowerManager integration for button and keyboard backlight.\n\nAllows setting button and keyboard backlight brightness as well as\nbutton timeout.\n\nChange-Id: I550cccafc0a8f90d6347de9261adb26b75955cc4\nSigned-off-by: Louis Popi <theh2o64@gmail.com>","distinct":true,"url":"https://api.github.com/repos/AOSParadox/android_frameworks_base/commits/289d780c82f04b77031aa15c4d3d43f9b4c01cea"},{"sha":"f83ba3bcfb048473e30958417d44253653412dd2","author":{"email":"98c2d5a1e48c998bd9ba9dbc53d6857beae1c9bd@tjwendt.de","name":"Timo Wendt"},"message":"Runtime toggle of navbar\n\nThis adds the framework support for enabling the Navigation bar\non devices with hardware keys. It is toggled from Settings, and\ndepends on device-specific support for the KeyDisabler hardware\ncontrol\n\nChange-Id: I88fecb2ca1e8613591c327a93f53909b00239cd8\n\nwm: Nullify hardkey function assignments if enabling the navbar\n\nThis caused erroneous (and sometimes duplicate) events being generated\ndue to the regular key function assignments. The navbar does its\nown action management, so don't try to derive from the actions\nusually present in hard keys.\n\nChange-Id: I82866e24547f8145cac4f07820ae90aacce09281\n\nUpdate DEV_FORCE_SHOW_NAVBAR constant.\n\nChange-Id: Ie5b4317162c514d22276956f81007e064a3d0f32\n\nSettings: Move DEV_FORCE_SHOW_NAVBAR load to loadSecureSettings.\n\nChange-Id: I6ac53b8c9f7fce6f9ca6b4ad7bf31a1c1e896863\nSigned-off-by: Louis Popi <theh2o64@gmail.com>","distinct":true,"url":"https://api.github.com/repos/AOSParadox/android_frameworks_base/commits/f83ba3bcfb048473e30958417d44253653412dd2"}]}