Well, certain applications, like emulators, don't rely on Dalvik VM... and I'm sure many 3D applications that rely on certain GPU-specific codes wouldn't run.
apps that use the c++ based NDK wont work. but that is not most of them
Well, certain applications, like emulators, don't rely on Dalvik VM... and I'm sure many 3D applications that rely on certain GPU-specific codes wouldn't run.
I'll use a simple example: try to play a Tegra 2-specific game without Chainfire's wrapper.
As above.
OpenGL ES is the library, but that doesn't mean everything is supported equally.
It's like saying Intel GMA 950 should be able to run all DX9 games without bugs...
I'll use a simple example: try to play a Tegra 2-specific game without Chainfire's wrapper.
As above.
OpenGL ES is the library, but that doesn't mean everything is supported equally.
It's like saying Intel GMA 950 should be able to run all DX9 games without bugs...
Actually many of them should work. After all Android apps are written in java so the underlying architecture doesn't really matter provided the dalvik vm has been ported to it. Some apps do make use of native code but they should be in the minority.
apps that use the c++ based NDK wont work. but that is not most of them
Artificially restricting a game to a single gpu has nothing to do with gpu specific code.
We have never seen this gpu in a Android device before so dismissing it as buggy is premature and unfounded. After all a year ago many people thought the Mali 400 was going to be underwhelming.
right, driver issue, not the OS' fault, and not the fault of it being MIPS not ARM