As many posts in this thread have said, this problem dates back at least to 9.2.1, if not older versions of iOS.
Funny how I heard just about no one mention it then around here and I'm here every day.
You do know 9.2.1 was out quite a long time.
I'd bet 99% of mentions of this problem existing in 9.2.1 occured after 9.3 was released.
So you're telling me this bug had the SAME amplitude yet Apple didn't do anything before; seems very doubtful.
So, that would mean that in fact, for most people (if not all of them), IOS 9.2.1 would be the solution.
They should try it if they find this intolerable and only then, if it doesn't work, complain that there is no solution.
And if you are one of those few having this issue in 9.2.1, when did it occur?
If it is THAT bothersome, then I'm sure that whenever it occurred,
anyone would have been compelled to roll back to the previous version...
Or are you merely creating a scenario here?
So, I'm going to say the exact same thing, roll back and see if this fixes things, then and only then complain.
All the over the top preening for every single issue is getting just too much.
[doublepost=1459314351][/doublepost]
There is so much wrong with this post I don't even know where to begin. But I will say this...until you take the time to develop even a cursory understanding of the issue, you should probably refrain from making arrogant and inaccurate comments like this.
Got decades of hardware, systems and software engineering behind me and seen "outrage" like yours against "the man" (sic) a countless times, so spare me the cliff notes.