So there are a number of reasons for the break - greater processing capabilities of the OMAP3 platform (including support for hw acceleration of OpenGL, though this is something that might be possible for our OMAP2s with either some reverse engineering or some words in the right places, I am ever hopeful). This means that the new UI may be too much for our OMAP2 devices (though we should have a damn good try when it's finally released, closer to the device release date). ...