Comment 17 for bug 1531167

This is driving me crazy:
- When I have the phone in my pocket, a message arrives and the screen turns on. If I happen to move after that (which I don't know because I usually keep it silenced all the time), my pants start to try weird pin combinations. All successful, so far. Which means that by the time I actually want to use the phone I have to wait until the pin screen is unlocked because I've had too many unsuccessful tries. Which is a *bummer* when I need to make an urgent phone call or need to take a look at the map to check if I should already turn or get off the bus (both happened to me) [which tempts me to open another bug report about "letting the user decide if they want to block the screen after too many unsuccessful tries"].

- In the rare cases when the phone isn't in my pocket, and I get a couple of notifs in a row (like, telegram msgs) sometimes the screen starts to flicker and turns on and off in a frantic way that's very disruptive. Which reminds me I usually want to have it in my pocket except... above :) And even after cleaning all the notifs the led stays on flickering... (some notification service bug I guess, if I get to reproduce it I'll report it). Can we set a timer for the first notification and don't act on successive notifs if they're less than X seconds apart from the first one? At least the time it takes to turn the screen up, play the sound, show the message on screen and turn it off again. I've tried messaging me and it play EVERY SOUND for each message. it ended delivering the last message (with its sound) 3 minutes after the last message I'd sent from another account.

I'm on arale rc-proposed.