Uhoh, hating on the Tegra.
Actually, the more I learn about Android, the more I discover that "multitasking" is a myth. A few thoughts:
- First, how many Android apps are multi-thread capable? None, afaik (could definitely be wrong). That means that any given app presumably runs in ONE CORE.
OK, but then: I can run several apps simultaneously across different cores, right?
- Not exactly: it looks like the device RAM is the bottleneck. If Android runs out of RAM, it caches background apps--saving their state (e.g., gmail inbox and the message you were viewing 2 apps back)--and then restoring the app+state when you return to it. You have the illusion "it was still running." This happens to me on my Droid (OK, yeah...256MB RAM?) ALL THE TIME when I go back to my browser (it reloads the page!!!). Happens a lot with my gTab (500MB RAM) too.
There are some important exceptions: we can for example run a music player (which stays persistent) while browsing or reading mail. We hear the music (while offscreen) so it's obviously still running.
But then: LOTS of "apps" (actually, services/processes) run in the background, like location sensing, phone, push services, etc. Still, I wouldn't call *that* multitasking.
What's my point? I guess it's that: All those cores sound awesome, but multitasking on an Android device isn't quite the same as it is on a PC. (Sidenote: Nvidia is claiming that another advantage of Kal-El will be battery life. If so, then my analysis is not so relevant.)
-Matt