Android Phone Tips

Android Phone Tips
Forumers at XDA-Developers Forum have overclocked the Motorola Xoom to an amazing 1.5 GHz. The Xoom, by default is already considered fast with a dual-core Nvidia Tegra 2 chip running at 1 GHz. I have successfully brought the Tegra 2 in the Xoom to 1.5GHz. A few kernel modifications make the dual core chip in the Xoom even more powerful than the recently announced Tegra 2 3D! 

If you’re not familiar with this tablet, it features a 10.1-inch capacitive touchscreen display with 1280 x 800 resolution, an NVIDIA Tegra 2 dual-core processor clocked at 1GHz, 1GB of DDR2 RAM, 32GB of built-in storage, a microSD slot for additional storage, an accelerometer, digital compass, proximity sensor, ambient light sensor, gyroscope and a barometer. 

On the camera front we’ve got both a 5-megapixel rear facing camera with auto focus, 4x digital zoom, 720p video capture and dual LED flash and a  2-megapixel front facing camera for video conference calls. Now it's facing a tougher review: how well does it meet the HTML5 specification, and how does its CSS3 and Javascript support match up?

Nada. Clearly, shipping "with support for" is different from shipping "with". Other tests suggest that the Xoom supports HTML5 features including SVG, inline SVG and CSS3 3-D transformations. Not present: WebGL, Web Sockets, Web Workers. 

The processing power is very hefty - the Xoom, with a dual-core Nvidia Tegra 2 processor is miles ahead of the iPad and Samsung Galaxy Tab in Javascript performance. Bansod points out that CSS3 animations were "almost completely broken"

"We often found even for the most basic animations the browser skipped frames, incorrectly rendered elements, or didn't run the animation to completion. If Animations were simply slow, that would be one thing, but the Xoom CSS3 Animation support faces basic correctness issues. "For anything but the most basic CSS transitions and animations the Xoom does not make the grade."

HTML5 audio worked ("although we find that sometimes the audio plays even after we left the page or even closed the browser") but HTML5 video didn't work at all. The message to HTML5 developers: "wait for the inevitable patches". We had issues where the browser either hung or crashed. We had issues where media playback failed or performed incorrectly. 
By. Android Phone Tips

Friday, March 4, 2011 | 0 comments | Labels: , ,


Post a Comment