Well, we're talking about the chip throughput, running tests that are likely to be native code on both platforms. I would be shocked if these numbers would be that hugely affected by kernel module optimization. I suppose anything is possible, though I'm not going to hold my breath.

Assuming that the T20 just isn't up to snuff:

The iPad2 will lead this generation of devices in performance (GPU). The two major Android players, Samsung and Motorola were likely considering their bottom line over this crucial part, and it will cost them a year for the all-important gamer demographic. Apple will wipe then floor with them.

I'm actually quite disappointed with Samsung. I was surprised when I learned that the Tegra 2 (last years SoC) was to be in the tablet, but figured that internally, they had considered the SoC options. Of the options are the Scorpion w/ Adreno 220, and Samsung's own Exynos 4210 w/ Mali 400MP. These designs (this year's SoC -- with the possible exception of the 220, for lack of specs) compete on paper with the A5's SGX543.

Samsung seems to have made a really bad decision. In fact, the Galaxy S2 should outperform the Tab10.1 by a healthy margin. Sad.

If it is just a case of software optimization (which I doubt), then I'll eat my hat!

Samsung Mobile now has an official Galaxy Tab 10.1 site!

http://galaxytab.samsungmobile.com/

What's interesting is that the site is devoid of flash, unlike the first Tab micro-site.

Not much, but it's something!

The Galaxy Tab, may not be able to compete with the GPU performance of the iPad2, but it still looks like a very compelling purchase for many individuals that don't fixate around specs -- or games.

http://www.engadget.com/2011/03/14/s...-look-all-tha/
(as linked before)

However, Google should consider improving on what exists than hunting newer features for Honeycomb tablets.

For example:
1) Continuing to modularize certain APIs out of the Android OS distribution. This will make it easier to 'push' updates. Which leads to:

2) Consider using Dalvik for developer libs (increased portability) and not just app code. Dalvik has come a long way in terms of performance (computational and memory) and it will likely make a fine substitute for otherwise compiled APIs that require OS bundling.

3) Improving on existing features rather than constantly adding new features. Certain bug-fixes can be applied to greatly improve the UX as well as enhancements to usability and speed.

4) A binary testing mechanism to ensure proper functioning prior to integration on a new system. Somewhat of a novel concept, but it would protect users from a failed automated update, and provide Google feedback to further improve support of a particular system, or pass that information on to the vendor.

5) Store multiple versions of core libs on drive (if it's not done already), with a rich manifest describing the particulars of the lib. This will allow a good mix of homebrew and external APIs for developers to use. If coded in Java, the benefit would be a lib almost 'guaranteed' to work on multiple platforms.

6) Provide a mechanism for community developers to easily 'try' OS code on their systems in a protected way for increased community interaction with bug-fixing. Empowered, the community would lend a great hand in improving the overall stability of devices across the spectrum, and be encouraged to try new APIs.

7) Allow the storage of libs in the Android Marketplace in a hidden form (non-purchasable). Apps would thus be able to list their dependencies, and dependency chains could be resolved via Google's services. The download would be 'apt-get' like, only with static APKs rather than expandable debs. Similarly the lib would be subject to the same access permissions as with applications.

8) Provide access to vendors to upload things like binary kernels, modules, and native libs to the market in a hidden form (if it's not done already). This will remove the difficulty of pushing updates and will not require special software outside of that which ships with Android.

With these inclusions, Android could see seamless updates not only to apps, but core OS functionality. Instead of requiring that vendor's update the OSs, Android could receive timely updates and all devices could slide between OS releases. This provides more of an opportunity to fix bugs, as well as to distribute APIs and even to try new features!

The manifest features, testing and versioning ensure that current software will not break in the event of an update, even a significant one.

It seems that the next version of Angry Birds will launch exclusively via Amazon's app store!


http://www.androidcentral.com/angry-...roid-app-store
http://www.rovio.com/index.php?mact=...t01returnid=58

Expect it to find its way to the App Market shortly thereafter.

The Android app count continues to rise at a breakneck pace!


http://www.androidcentral.com/appbra...-android-stats

Interestingly, this statistic visualized by AppBrain (Google Market curator) differentiates between regular apps and 'low quality' apps.

It is nice to know that there are 90K good apps, and the rate of good apps seems to be growing faster than the low-quality apps.

As an aside, I've now installed CyanogenMod 7 on two Motorola Droids (RC2 on mine and my brother's) and on the Nook Color (R17 nightly) and.. cripes! The battery life! Oh my God.

On the Droid... For one--battery life is far.. FAR.. FAAAAR better now. Where I used to be able to maaaaybe stretch my Motorola Droid out to a bout two days of normal use before it would finally completely run out and turn off, I recently decided not to try charging and see how long it lasts. I'm already on day two and it's still well over 70%. What... the.. hell?? I'm really, really loving this on a phone!

On the Nook Color, Cyanogen Mod 7 R17 completely changed the otherwise dinky, crippled feeling Nook Android experience to a real and proper TABLET experience! It runs GREAT on there, generally pretty fluid and about the only problem I'm noticing so far: 1) bluetooth isn't working--period. I think I remember reading that it's a known problem. 2) video playing is broken. This, to me, is devastating--especially since my mother uses this Nook for her podcasts (audio and video). I got around this by installing Rockplayer but.. you know.. Rockplayer. Blech (audio syncing issues, overlayed logo, etc.). Anyway, it appears they're aware of the issue and supposedly fixing that soon too. Outside of those two issues--it's an incredibly excellent experience. Even the emmc is available as storage space! The significant thing about the Bluetooth issue, to me, is that if they fix it and it works--BAM! Suddenly you have a 7-inch tablet that supports BLUETOOTH MOUSE AND KEYBOARD! ...and CHEAP, too!

Given all of this.. I'm that much more excited to see what they can do with the Galaxy Tab, assuming they manage to make an easy and reliable install method.

Woah! That's really great news. There's something to be said about a battery that you don't even have to *think* about. It's like a weight gets lifted off of your shoulders while you're using the device, and the battery becomes an afterthought.

Having dealt with notebooks/netbooks, I can comfortably say that the notebooks with sub-par battery performance always have you looking at the clock with a type of 'time anxiety' added to the mobile experience, and the need to carry around a charger wherever you go, selectively choose places with outlets for extended periods, and hunt for outlets in new locations. It really, really cripples the user experience!

It's nice to know that Gingerbread has stepped up the battery performance in a very big way.

I wish Google would apply polish like this to other areas of the OS that are functional, but could be stellar with the correct attention.

It seems as though Google Maps is heavily used by mobile users.

At SXSW, Google mentioned that some 150Mil users are using the service!


http://www.droiddog.com/android-blog...-maps-at-sxsw/

I fully expect that Tab users are driving the charge!

Other claims include:

• 12M driven miles
• 2 years saved in due to traffic avoidance

Android owner? Generally up to no good? Craving access to restricted spaces?

There's now a 'solution' for brute forcing "IP-based Cardkey security locks".
http://www.androidcentral.com/androi...security-locks

Those crazy kids with the cellphones! God luv em'!

In other news: CardKey should be ashamed of itself...