Is your Android device not quite top of the line? I read recently that Rovio felt that they'd aimed a bit high with their required specs, and that they would focus on increasing performance on mid-range devices in the near future.
In fact, my EUR0.02 is that native-inclusive apps (just like any Java apps which rely on native libraries) are worse, in my opinion, because it limits the number of platforms that one can execute the apps upon. And as a huge Linux fan, current Mac user, and user of x64 Windows at work, I can assure you that I get left out in the cold a LOT.
It's one level of bad to tie your app only to Windows, which coincidentally includes 90% (last metric I heard) of the world. It's another thing entirely to say, "oh, sorry, your Android isn't the same as my Android: too bad for you."
1 = unzip -l AngryBirds_1.3.5.apk|grep -i \\.so
That's interesting - are you sure about that? There's a big difference between a static translation JIT and the more modern and memory-intensive progressively-optimizing JIT's that are used outside mobile. My understanding was that Dalvik's JIT was a one-time-only translater. Its difficult to find any comprehensive benchmarks of the 2.2 JIT - there are plenty of benchmarks showing the 2.1 interpreter eating CPU cycles compared to native code (think 20-to-1), and Google themselves claimed that the 2.2 JIT would mean a 2-5x improvement in CPU efficiency, but I'm still waiting for a set of comprehensive cross-platform benchmarks.
So presuming that you're talking about the "Full" version, and considering that there is no lite version, I'm curious how such a difference of perceptions could possibly be.