Re: This was the problem with my last Windows Mobile phone
To be honest, all problems that even modern PC's have been able to replicate if you slag them hard enough with things to do.
I work in schools and still hear the occasional keyboard "beep beep beep beep" as some computer has 90 copies of Word loaded on it because the kids are leaning on the keyboard, then it gets a full keyboard buffer and doesn't know what to do with it, and the replay of the keyboard buffer after it catches up still affects just about every PC in the world.
The problem is not the exhibited behaviour, but the cause. The only way to have that be a problem (and not have the keyboard / touchscreen input buffers just keep up in real-time) is to have a vastly overworked processor that just can't get round to processing input in time. With MS, I'm not really surprised, they've never really taken the "embedded" space seriously in terms of programming and just try to shoehorn portions of the desktop product into a smaller, powerful device (even the XBox was just a mid-range PC in a box).
There is no magic solution to the input problem that others are using. You can either buffer input, or throw it away, and if you buffer it you have to have a limit before you start throwing away. And getting to the point that you are throwing away input means the machine is just trying to do too much and can't get around to dealing with that input. The problem lies in not checking input often enough, with enough priority, and at the expense of other processes. Something that a lot of programs and OS get right is to just give user input the absolute top priority possible - there's nothing so frustrating as a small pause between input actions and their response. I want the computer to start deleting the damn files I told it to, or move the cursor across the screen smoothly AT THE EXPENSE of the background process actually removing those files from disk. That's how it should always work. If I can't get to the damn icon in the first place, it doesn't matter how multitasking the OS is or how fast it deletes those files, I still suffer a drop in productivity where I could be giving the computer MORE instructions that it can perform for me.
But if you program without consideration of user input, if you don't prioritise it but prioritise other uncertain benchmarks, or if your processor is just THAT damn busy, you end up with those problems. Optimise, rethink, upgrade. And the third option is REALLY expensive if you're building a phone. Methinks they just couldn't get the software down to the point where it didn't bring the whole processor to a grinding halt and have "forgotten" how to optimise things for low-end systems, as a company.