It's not self-evident. There are serious jank problems while scrolling, 10-second latency problems navigating trivial apps like Settings, and nagging battery-drain problems with Android. These are the main problems the platform has.
Utter bollocks. And even if it were true (and it isn't) it does not mean the kernel is to blame so your point would still be bollocks.
Memory use isn't one of the problems: the standard phone went from 0.5GByte to 2GByte RAM a couple years ago without any significant change in app functionality, and the K release used less memory than the J release so general platform bloat is actually going backwards: the stack's memory tax is therefore less than a quarter of the standard platform size and not a big deal for emulation.
Utter bollocks again. Android has increased memory generally so more apps stay resident in memory. The less memory, the more likely it would be to purge apps. In other words it makes use of the memory for stuff.
Performance probably isn't a problem wrt the emulation because the performance problems are not flat-out CPU bound work nor mean-latency problems: doubling the mean latency would not be a big deal because android has such huge tail-latency problems. And doubling mean latency in return for cutting max latency is exactly what hard-realtime kernels like Neutrino are made for. Whether they can do this through the android stack is doubtful because the latency is probably coming from java crappo, but who knows. Anyway it's not self-evident that emulation will cause a memory problem for Android, nor that it will cause a performance/battery problem.
Utter bollocks because it presupposes your other bollocks and makes no sense in any event. The point I was making was that to emulate Android, a Black Berry device has the memory pressure of two runtimes in memory at once (the native one) and the emulated one (plus shims). It obviously impacts on memory and performance.
Emulation and battery-drain problems aren't related because they're caused by poor scheduling, bugs, held "wake locks", etc. Part of the area where bugs can exist will be replaced, so if QNX is higher-quality than Android in this replaced area it will win the battery game.
It's true that a misbehaved app can drain battery but normal drain is caused by the screen, radio and general activity. And in any event it's largely an irrelevance what kernel is underneath because an app can misbehave over any kernel. And modern kernels are wasting CPU / battery unless something above is telling them to.