Two OMAP 3430 Phones: Nokia N900 and Motorola Droid
by Brian Klug on June 10, 2010 9:29 PM EST- Posted in
- Smartphones
- N900
- Maemo
- Motorola Droid
- Droid
- MeeGo
- Android
- Mobile
Maemo is Debian
That really brings us to what we haven't talked in depth about before; Maemo. Nokia's Maemo operating system started - as I mentioned earlier - as a tablet operating system for the N770, and saw updates for the N800, and N810. As it stands now, all three legacy internet tablets can run up thorough Maemo 4.1.
The N900, however, launched with and continues to exclusively run Maemo 5. The N900 we played with was flashed to PR 1.1, and recently Nokia released PR 1.2 - unfortunately just a few days after we had to part ways with our N900. PR 1.2 brings bugfixes and a few new features to the platform, including support for Skype and Google Talk video calling (which I'll get to in a moment), performance increases for the core OS and browser JavaScript engine, and Qt 4.6.2. The core of the Maemo OS remains largely the same however.
Maemo is derived from Debian and runs natively compiled code, uses GNOME for much of the UI, has an X-Window system, and uses BusyBox core utilities. For all intents and purposes, using Maemo is exactly like using almost any other computer running Debian. What other phone seriously ships with X Terminal installed and presented front and center in the launcher? It really is a bona-fide handheld computer by day, smartphone by night.
In Maemo 5, up at the top is the menu and status bar. This is a bit of a strange departure for earlier Maemo users who likely are used to the same bar being at the left. Regardless, tapping on the icon at top left from the desktop brings up the application launcher, which consists of a 5 by 3 grid of applications overlaid on a beautiful defocused version of your desktop. What's really impressive is how buttery smooth the transition from desktop to launcher is; no doubt a huge testament to some GPU acceleration on the OMAP 3430's PowerVR SGX.
Getting to the next page of apps is unfortunately not a scroll gesture away, instead, you have to tap more in the bottom right corner. This is something that has changed in PR 1.2 however, as 'more' has been removed in favor of touch scrolling, and apps can be rearranged.
This out-of-focus blur is a consistent UI element that acts as Maemo's way of establishing what many on the desktop would identify as window 'focus.' Of course, in this context, it's more likely to be applied to a menu or some launched property panel.
For example, tapping and holding for a copy/paste or save file command brings up a blurry background surrounding the new property window. It's impressive how smooth this transition is, I just can't stress it enough.
68 Comments
View All Comments
Wadzii22 - Friday, June 11, 2010 - link
Out of curiosity I ran linpack and Benchmark pi on my droid that's oc'd to 1ghzmy benchmark pi score was 1280 and linpack gives me 17.24 mflops
strikeback03 - Friday, June 11, 2010 - link
Did you run them stock? As those numbers seem to be a ~4x improvement over what is shown here, which seems odd given the ~2x increase in clockspeed.Wadzii22 - Wednesday, June 16, 2010 - link
with the phone completely stock my scores were basically the same as whats in the original article.jamyryals - Friday, June 11, 2010 - link
Please continue this type of in depth comparison with current and future hardware. PC hardware is all well and good, but it's all so fast now the mobile space is a much more interesting battle. Not to mention with how fast things are evolving there is the opportunity for a lot of content.Ratman6161 - Friday, June 11, 2010 - link
For eample, my droid purchased in early April came out of the box running at 600 MHz (though now it actually runs at up to 900 Mhz). My wife got hers in early June and hers is 600 MHz too and also came out of the box with Android 2.1 already on it.Wadzii22 - Friday, June 11, 2010 - link
For whatever reason, setcpu always sees a stock droid's max at 600, but they do run at 550. I just got a new one yesterday after bricking my old droid, it showed the same thing.CharonPDX - Friday, June 11, 2010 - link
Nokia was the originator of the "sell unsubsidized smartphones direct" model, years before Apple or Google. You could get a Nokia N80 at CompUSA completely unlocked for $800 in 2006, a year before the unsubsidized iPhone.Stas - Friday, June 11, 2010 - link
0.1 build with fixed WiFi and maps.LinPack - 12.2 (twelve point two)MFLOPS
Engadget.com loads in 20 sec (default browser)
'nuff said.
Stas - Friday, June 11, 2010 - link
forgot to mention. the CPU is at 800Mhz. I've had it up at 900Mhz with bare Android build (leaked 2.2) and the performance seems no different, but no numbers, sorry.milli - Saturday, June 12, 2010 - link
That's pretty wrong what you're saying there.Qualcomm didn't even license the A8 (nor will they ever).
What they did license is the ARMv7 instruction set (and that's a huge difference). With that they made a custom implementation of the ARMv7 architecture. (BTW Qualcomm already stated in 2005 that they're an architectural licensee for ARM’s ARMv7 instruction set)
There are many differences between Scorpion and A8.
I'll quote from a certain article since i can't say it better:
'Although Scorpion and Cortex-A8 have many similarities, based on the information released by Qualcomm, the two cores differ in a number of interesting ways. For example, while the Scorpion and Cortex-A8 NEON implementations execute the same SIMD-style instructions, Scorpion’s implementation can process128 bits of data in parallel, compared to 64 bits on Cortex-A8. Half of Scorpion’s SIMD data path can be shut down to conserve power. Scorpion’s pipeline is deeper: It has a 13-stage load/store pipeline and two integer pipelines—one of which is 10 stages and can perform simple arithmetic operations (such as adds and subtracts) while the other is 12 stages and can perform both simple and more complex arithmetic, like MACs. Scorpion also has a 23-stage floating-point/SIMD pipeline, and unlike on Cortex-A8, VFPv3 operations are pipelined. Scorpion uses a number of other microarchitectural tweaks that are intended to either boost speed or reduce power consumption. (Scorpion’s architects previously designed low-power, high-performance processors for IBM.) The core supports multiple clock and voltage domains to enable additional power savings."
"Qualcomm claims that Scorpion will have power consumption of roughly 200 mW at 600 MHz (this figure includes leakage current, though its contribution is typically minimal in low-power processes). In comparison, ARM reports on its website that a Cortex-A8 in a 65 nm LP process consumes .59 mW/MHz (excluding leakage), which translates into about 350 mW at 600 MHz."
With that said, i don't understand where the misconception about the Scorpion being an A8 started. Even Qualcomm states clearly on their own website that Scorpion is not licensed from ARM. They also state that they invested hundred of millions in creating their own core based on the ARMv7 instruction set.
I hope now all the staff from Anand will stop saying that there's an A8 inside of Snapdragon. Or maybe you should even clarify that with a small article.