Slashdot Mirror
Google Mobile Phones Debut in Feb?
SpinelessJelly writes "It appears that Google's Android, criticised by Microsoft as vaporware, has sprung to life. Prototype devices are circulating, software developers are experimenting with the SDK and PC-based Android emulator, and there are rumours of a show-stopping debut at February's Mobile World Congress event in Barcelona. Numerous examples of the Android GUI are also starting to leak out."
Try the development kit.
It comes with an Android emulator, and a few of the Google applications. Included is an address book, a dummy dialling application, a working Google Maps application, a working browser... and any other applications that Android developers decide to write for it.
The only thing that is missing is the phone hardware, but we've seen pictures and videos of phone hardware running this. I'm surprised the release is so far away considering the resources available and how complete everything seems to be.
OpenGL ES supports floating point or fixed point math. Using floating point is going to severely reduce your performance if you don't have a Floating Point Co-Processor. And fixed point math is incredibly inaccurate, leading to a lot of graphical glitches in pre-accelerator games. (And is *still* slower than pure integer computations.)
Doom was a 2.5D raycaster, not a true 3D engine. Quake is a better comparison. Quake did run on a 90MHz processor, but it also ran in 256 color mode with rather small textures. Model meshes consisted of a handful of polygons wrapped with a single (low-res) texture. Visibility and lighting were pre-calculated using a modified BSP Tree structure that took HOURS to generate.
Android phones lack such a luxury. Graphics will be produced real-time using high-color, high-resolution textures. Scaling, rotation, and lighting are expected to be smooth and responsive. Graphical output should be crisp with little to no blurring. (Poor rendering quality is VERY bad for on-screen text.) In these situations, a 200MHz processor becomes barely adequate. In fact, it still remains to be seen if it will be able to handle the load.
It's possible that the phone manufactures who use the 200MHz chip with no 3D accelerator will keep the graphical effects to a minimum. (Obviously, a non-rotated 2D image with GL_ORTHO is going to be WAY faster to render than a full-3D scene with rotation matrices.) But that would tend to put the phone at a disadvantage in the market. The hardware is powerful enough to demand a higher price, but doesn't appear to be a good value when stacked against other smart phones.
Javascript + Nintendo DSi = DSiCade
The Nintendo DS has two ARM cores paired with one 2D/3D accelerator core and one 2D accelerator core. This gives it two separate rendering pipelines with a maximum output of 120,000 triangles per second on the top screen and a touch-sensitive 2D framebuffer on the other. That's not really comparable with a single 200MHz ARM trying to perform OpenGL ES computations.
Javascript + Nintendo DSi = DSiCade
I tried Android out -- we banged out a personalized weather application (even without a GPS chip, Android is capable of triangulating satellites to get within 300m of the user's position, which is sufficient for weather applications). The whole process took under an hour and was easy as pie.. So, no it's not vaporware. The hardware may be still be a few months away, but the software is enough to create real-world, practical applications.
And yes, this big drab-looking device is dog ugly - but this isn't a slick made-for-media concept phone, it's merely a functional prototype on which the developers and engineers can tinker (and we all know that as rule, they're not big on elegant design).
RTFA!!