Comment 20 for bug 1531167

so the complaint in comment #17 sounds to be the arale specific issue of sending repeat key events

for the other generic issue of proximity staying active - we are going to change policy to be a single trigger, e.g. once display turns on during an event, the display will remain on even if proximity is covered.

and unfortunately, we don't own the prox/display drivers - we don't want to get in the biz of tinker with every soc/device driver set, rather have a stack on top that can best accommodates many devices

so, the single trigger should help the queuing issue. however, it's a little concerning that your description indicates, the display is turning on in your pocket?