How in the world did you get 4.2 on the Wildfire? Root + custom ROM?
Yes root + custom rom. But it's a Wildfire ->S<- which was shipped with 2.3.5 and got updated once by HTC to 2.3.7. After no more updates I rooted it and flashed a 4.0 version. Now I'm at 4.2.1 but it's obviously tuned down in features, because the phone is hardly capable of running stuff like google now etc. and it's still running on a 2.6.35 kernel.
But I still like it, because it's so small :-)
Well it's quite easy to write a scheduler for a predefined set of background processes and a maximum of 1 active foreground tasks ;-)
With android you can have the same experience, but your phone has to be quite powerful. For example on my Samsung Galaxy Nexus (which is quite powerful) with android 4.2 I have never experienced any noticeable lag. On the other hand there is my HTC Wildfire S which is also running 4.2 but as soon as there is more then one process activley using the cpu there's a noticeable lag.
I think you know that ios isn't that simple (plus, I think, there is an api for background tasks but, I'd imagine, they get evicted at the drop of a hat). OSX gets great latency out of the box (apparently not as good as RT linux, but RT linux is hardly stock).
Linux probably needs something completely different from CFS, something much more interactive. I know that some changes are either coming (or are in the current rcs) like the bouncing elephant outlier (which I'm surprised even existed since we've had affinity for ages) and the AutoNUMA stuff (hoping "node" will refer to cores as much as sockets).
I've played around with android enough to know that unless you get something like a 10GHz xeon you aren't going to see improvements in lag once you are running 4.1+ (even my old Nexus S runs with similar to indentical lag as my N4...it's just not a hardware issue, aside from the absurd device I posited). The problems come down to:1)touch events aren't priortized enough, 2)android takes too long to perform certain draws (an intel engineer wrote a whitepaper where he gave some data about this). The first thing can be helped by an RT kernel, the second can as well IF drawing is prioritized thus not interrupted except by another touch event.
Originally Posted by Akka
A realtime kernel to get smooth animation. That sounds as a bad solution long term...
Why? The RT guys seem to think they will eventually achieve performance parity with mainline, and in some cases even faster (networking, I think, was the target there). Besides, I don't recall ever seeing the throughput delta of coop and RT.
Originally Posted by Sonadow
My family owns an iPhone 4 and a Galaxy Note 2. And when I compare the animations between all 3 devices, my Lumia 520 with Windows Phone 8 really looks (to me) to have the least lag, and is even more fluid than the iPhone 4 in the interface animation.
Love the Note 2's huge display though. Too bad it's too big to stuff in my pocket.
For well used devices, you might be right. I don't own any i or win devices so I am going by using them in stores, and friends/relatives devices.
In those cases, ios always wins in terms of following my finger. Place your finger over a specific character in the browser, for instance, and see how much it moves when you scroll up and down. First move slowly, but constantly, then later use acceleration in both directions. IOS simply reacts faster than any of the others. Windows and Android are ROUGHLY equivalent, with windows looking to be a bit more responsive in my view.
BTW, I'm not talking about smoothness, only responsiveness.
I don't agree with your statement that Nokia is dying. Nokia still covers huge market to beat its competitors and have great potential to introduce unique stuff and innovative products in current market.