After some digging, I've found that com.android.server.accessibility.AccessibiliityManagerService is where KeyEvents are sent, and the AccessibilityInputFilter class is what handles the KeyEvent filtering. It doesn't appear that Accessibility itself is handling these events, so it's likely that the service providing these events simply does not pass along certain events,
On Sunday, July 13, 2014 10:05:14 AM UTC-4, Tom wrote: > > Android API 18 introduced the onKey method AccessibilityService along > with the necessary flags to enable filtering KeyEvents. What system > service/ method deals with the delivery of these events, and *is it > possible to register for key events when the screen is off*? > > I've noticed that hardware button events are not passed to > AccessibilityService when the screen is off, which I'm guessing has to do > with the dangers of overriding this behavior and preventing the device from > unlocking. However, I'm interested in handling hardware buttons for the > camera/ volume/ events other than the power button. Is this possible at > present, or is such a feature being considered? If not, perhaps > AccessibilityServiceInfo could include a list of KeyEvents the service > wants to register for when the screen is off and have the service only send > those? > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
