Common Paradox Tech Blog

In a very special episode of Remainders, we’ve got: A Verizon-iPhone quote from somebody who would actually know something (Verizon exec!), the anti-COFEE tool DECAF revealed as a hoax, Xperia X10 at the FCC, and (no lie) Three Walrus Moon.

Verizon iPhone Rumor From a Non-Analyst (Whaa?)

Analysts can blah blah blah about the Verizon iPhone all they want, but we ain’t buying it until we see some hard proof. Now, Verizon’s CTO made a statement that looks as if it’s that proof we’ve been wanting:

“We have put things in place already,” Melone reportedly said. “We are prepared to support that traffic.”

Ah. Well, it’s not exactly a confirmation that Verizon’s getting the iPhone. It actually seems like another dig at AT&T’s network problems—he’s just saying that if a huge blockbuster handset like the iPhone were to come in 2010, Verizon’s network could handle that kind of traffic. So, Remaindersed. [AppleInsider]

COFEE-Beating DECAF Software Revealed as Hoax

DECAF, which supposedly disabled Microsoft’s COFEE forensics tool, has been revealed as an elaborate hoax by its creators. Looks like it was created to draw attention to the fact that COFEE is actually not as effective a tool as they’d like—in fact, the hoaxers view COFEE as vastly inferior to properly trained forensics experts. So, we, like everybody else, got duped. Seems to us that software that actually could defeat COFEE would be make a stronger statement than a hoax, but we’ll never know now. [Seattle P-I]

Sony Ericsson’s Xperia X10 Android Phone Hits FCC

This one’s simple: FCC posts are boring. They rarely give us new information, and the FCC photographers are notoriously artless. But the Xperia X10 is an exciting gadget, with its flashy Android skin, and it looks like we’ve got confirmation that the X10 should hit either T-Mobile or be sold unlocked, due to the support of the EDGE 850/1900 spectrum. More details as we hear more about the phone’s eventual release. [Engadget]

Jesus Diaz Has Odd(ly Hilarious) Taste in T-Shirts

Three Wolf Moon is cliche. But our own Jesus Diaz has moved beyond the internet sensation to its logical sequel: Three Walrus Moon. Really, this t-shirt was just delivered to our HQ today, addressed to Jesus, and he’s been elusive about offering official comment. All we can say is: Watch out, ladies.

In a very special episode of Remainders, we’ve got: A Verizon-iPhone quote from somebody who would actually know something (Verizon exec!), the anti-COFEE tool DECAF revealed as a hoax, Xperia X10 at the FCC, and (no lie) Three Walrus Moon.

Verizon iPhone Rumor From a Non-Analyst (Whaa?)

Analysts can blah blah blah about the Verizon iPhone all they want, but we ain’t buying it until we see some hard proof. Now, Verizon’s CTO made a statement that looks as if it’s that proof we’ve been wanting:

“We have put things in place already,” Melone reportedly said. “We are prepared to support that traffic.”

Ah. Well, it’s not exactly a confirmation that Verizon’s getting the iPhone. It actually seems like another dig at AT&T’s network problems—he’s just saying that if a huge blockbuster handset like the iPhone were to come in 2010, Verizon’s network could handle that kind of traffic. So, Remaindersed. [AppleInsider]

COFEE-Beating DECAF Software Revealed as Hoax

DECAF, which supposedly disabled Microsoft’s COFEE forensics tool, has been revealed as an elaborate hoax by its creators. Looks like it was created to draw attention to the fact that COFEE is actually not as effective a tool as they’d like—in fact, the hoaxers view COFEE as vastly inferior to properly trained forensics experts. So, we, like everybody else, got duped. Seems to us that software that actually could defeat COFEE would be make a stronger statement than a hoax, but we’ll never know now. [Seattle P-I]

Sony Ericsson’s Xperia X10 Android Phone Hits FCC

This one’s simple: FCC posts are boring. They rarely give us new information, and the FCC photographers are notoriously artless. But the Xperia X10 is an exciting gadget, with its flashy Android skin, and it looks like we’ve got confirmation that the X10 should hit either T-Mobile or be sold unlocked, due to the support of the EDGE 850/1900 spectrum. More details as we hear more about the phone’s eventual release. [Engadget]

Jesus Diaz Has Odd(ly Hilarious) Taste in T-Shirts

Three Wolf Moon is cliche. But our own Jesus Diaz has moved beyond the internet sensation to its logical sequel: Three Walrus Moon. Really, this t-shirt was just delivered to our HQ today, addressed to Jesus, and he’s been elusive about offering official comment. All we can say is: Watch out, ladies.

Mobile tech blogger Tnkgrl had a few minutes with the new Google Nexus One phone. Her full report gives some new insight into the much talked about device, and also confirms some things we’ve heard before. She was not allowed to take any new photos, but we’ve all seen the phone by now.

First off, there is no multitouch in the browser or maps applications. We can assume it has the same multitouch APIs as the Motorola Droid has. The Android 2.1 interface has five home screen panes instead of the three seen on previous builds of stock Android. Any Android user will tell you that’s a welcome improvement. We can pretty well tell from this that the rumors about the “Google Phone” running the “real” Android were wrong. This clearly seems to be an evolution of the existing platform. The interface is also quite snappy, being described as “Faster than the Droid”

On the hardware front, the device is rocking a 3.5 or 3.7 inch OLED display of the same resolution as the Droid. Overall, the phone apparently looks very nice and is thinner than you might expect. The GSM radio is for T-Mobile 3G bands. It runs EDGE only on the AT&T network. HTC has finally moved to MicroUSB for the data/charging port. There are also some gold contacts on the bottom of the handset, these may be for a dock of some sort. Based on what you’ve heard so far, Is this a revolution or just another phone?

Another personal encounter with the Nexus One is recorded in history forever, and while Tnkgrl wasn’t allowed to exercise her camera finger, she’s written on her blog that it’s “extremely thin,” but more importantly, there’s a severe lack of multitouch…UPDATE

While she concedes that it’s “much nicer looking in person,” the lack of multitouch in the browser and Maps is a bummer. Here’s what she noticed when having a fondle with the Nexus One:

- It’s much nicer looking in person than in pictures
– There’s a 4 GB micro-SD card installed
– The battery capacity is 1400 mAh
– The screen appears to be OLED (same size/resolution as the Motorola Droid)
– 3G works on T-Mobile USA
– I can confirm that there’s no 3G on AT&T (EGDE only)
– It’s definitely unlocked
– It’s super snappy! Faster than the Droid…
– There’s no multitouch support in the browser or in Google Maps
– There’s no dedicated camera key, but it’s the same camera interface as the Droid
– The trackball can be used to focus (like on other HTC devices)
– Low-light performance is decent, but the flash is weak
– Calls are routed the normal way, not using data (VoIP), and sound fine
– The home screen is divided into 5 panes (like the Sense interface on the HTC Hero)
– It’s using a micro-USB connector for data/power
– There are some gold contacts at the bottom edge, for a dock perhaps?
– Did I mention it’s fast?

The lack of a camera button disturbs me, but other than that, it sounds like a fairly ho-hum Android phone. [Tnkgrl via Engadget]

UPDATE: Alright commenters, you have your wish. Tnkgrl only said there’s no multitouch support “in the browser or in Google Maps,” which still doesn’t eliminate the option of multitouch in other areas of the phone. And of course, it’s still just early days yet—there’s no reason to believe that Tnkgrl got her hands on a final production unit.

Do you remember Google’s Android mobile OS a year ago? Back then, it was just launching its app store and releasing the first phone powered by Android, the T-Mobile G1.

Fast-forward to today. Two days ago, Android surpassed 20,000 apps. Not only that, but the Droid by Google, Verizon, and Motorola has made a big impression. Oh, and don’t forget about the Nexus One, aka the much-hyped Google Phone.

It’s been quite an interesting year for the Google-made smartphone OS, but analytics firm comScore released some new numbers today that really illustrate just how far it has come.

Android: Still Small But Growing Fast

Let’s start with the most important number: market share. Android may be on the rise, but it isn’t anywhere near its main competitors. According to comScore, the Google OS doubled its market share in the past year. However, that only amounts to 3.5% of the market in October 2009. By comparison, Windows Mobile, the iPhone, the BlackBerry, and Symbian own magnitudes more of the market.

Still, look at the rate of growth from February to October, and it’s clear that Android is the fastest-growing mobile OS around:

The more telling stats are the ones that tell us what is going to happen over the next few months. Android is now recognized by 37% of mobile users, up from 22% in August. The reason, according to comScore? One hell of a memorable advertising campaign for the Verizon Droid.

The study also explored which phone consumers intend to buy in the next few months. comScore surveyed 2,300 people to answer this question. While the winner was BlackBerry with a whopping 49% across five devices, Android make a strong showing with 17%, led primarily by the Verizon Droid. 20% of individuals plan to buy an iPhone 3GS or 3G.

While BlackBerry is still king and the iPhone is still sexy, the Android platform is so hot right now that it could burn right through steel. The Nexus One and a wave of new Android smartphones coming out in 2010 will only serve to create an even bigger frenzy.

Is 2010 the year of Android? We want to know what you think in the comments.

Reviews: Android, Google

Tags: ComScore, Google, Google Android, iphone, Mobile 2.0, smartphone

According to Reuters, Google will have two versions of the Nexus One—one unlocked and one on a service contract with T-Mobile. The phone could be available directly from Google as early as January 5th.

They already had the January 5th date a few days ago, so this second confirmation of the same date might make it a bit more legit.

“In the long term Google will become a seller and get commission from operators,” the source said, adding that other operators are expected to follow T-Mobile’s lead eventually and agree to Google’s terms.

Reuters also quotes Baird Research analyst Will Power on how Google’s choice to market their own phone shakes up the smartphone market, but mostly screws other Android makers:

“We expect the launch of a new competitive device to be directionally negative for most of the existing smart phone markers, including Apple, Research in Motion, Nokia Oyg, HTC, Motorola Inc, Palm Inc, Samsung and others, while perhaps most negative for the existing Android partners.”

If Google’s choice to go the traditional route with carriers is true, it would, of course, dash any possibility that they might be giving this thing away for free. Let’s just hope the unlocked version comes cheap. [Reuters]

These leaks supposedly show AT&T’s very first Android phone, either called Backflip or Enzo. Aside from the odd backwards hinge, it looks mostly like a smaller, crappier Cliq—not exactly what we expected, given their stance on Android.

This phone is smaller than the Cliq, with only a 3.1-inch, 320×480 resolution, a 528MHz Qualcomm proc, and 512MB of ROM and 256MB of RAM. It’ll bring the expected array of connections (Wi-Fi, GPS, Bluetooth), along with the same Blur brand of Android initiated by the Cliq, but those specs are pretty standard—downright unimpressive, really. The only interesting part is the unusual keyboard, which flips out backwards so the keyboard is exposed even when the handset is closed. That keyboard, by the way, is a full QWERTY with what appears to be an optical trackpad.

gawkerGallery(5428380,4,”);

AT&T is the last of the major carriers to bring an Android phone to market, and if this is indeed their first one, we’ve got to admit to being puzzled. Each of the other carriers’ first Android phones were the top of the line at the time (G1 on T-Mobile, HTC Hero on Sprint, and Droid on Verizon), so we’re really wondering why AT&T would launch Android with such a, well, lackluster-looking device. Of course, this is all total speculation, so we’ll reserve judgment, but it’s definitely something to ponder. [Phandroid via Electronista]

It looks like AT&T could finally be getting its first Android powered handset. While this may be good news for those on the network that have been hankering for some Android, there are some odd things going on here. The Motorola Backflip/Enzo (name still in question) eschews the hinge mechanism we’re all familiar with. It’s basically backwards so that when closed, the back of the phone has the keyboard exposed.

The phone runs on Motorola’s MotoBlur implementation of Android 1.5 similar to the T-Mobile CLIQ. The phone will have a 3.1 inch capacitive display, Wi-Fi, 5MP camera, and that same old Qualcomm 528Mhz CPU. The camera is at one end of the keyboard and faces the user when the phone is open. There’s also apparently a touchpad on the back of the phone (opposite the keyboard) that can be used for no-look scrolling.

The Backflip/Enzo takes the inadvisable step of ditching all the Google applications except for Maps. That’s right; this Android phone looks like it will ship with no Gmail, Gtalk, or even Google Search. There is a Yahoo search widget in place of the standard Google one. In an almost complete disconnect from reality, a Google login is still required to use the phone. It’s also loaded down with the usual AT&T software. No word on pricing or release date yet.

So, can an Android phone succeed without all those Google apps? Check out more pics here.

The Google Phone could be a ploy to upset the wireless industry, or it could be an expensive niche device. Either way, it’d be a bid to take Android back from the companies that seem hell-bent on destroying it.

Android’s most serious problem right now is fragmentation: with each new phone, it seems, comes a different version of the OS. In theory, these differences are superficial, and come down to handset manufacturers’ and carriers’ custom interfaces, which sit atop a mostly unchanged Android core. In practice, it’s much worse.

Just look at the current top tier of Android devices. The Motorola Droid runs Android 2.0. The HTC MyTouch 3G and G1 on T-Mobile run Android 1.6. The HTC Hero, a newer phone than the MyTouch and the G1, is still stuck on 1.5, along with the even newer Motorola Cliq, which shares one parent—Motorola—with the 2.0-loaded Droid. Why is this something to worry about? Remember Google Maps Navigation, the free turn-by-turn app for Android? It only works on Android 2.0 and 1.6. An app written by Google doesn’t even work on every new Google phone. Imagine how things are with third party apps. (Spoiler: it’s a shitshow.)

Google’s been fairly diligent about updating the free, open-source heart of Android moving forward at a steady pace, and supplying handset manufacturers with the tools they need to keep their handsets running the latest software. That said, Google still deserves some of the blame here. That their software updates include new, exclusive functionality is fine on its own. And yeah, their eagerness to allow for Android to be skinned and deeply customized by handset manufacturers is fine on its own—in fact, it’s implicit in the project’s open source ethos. But mixed together, these ambitions create a gurgling software slurry of incompatibility, user experience inconsistency and general frustration. (See: Samsung Behold II) So what happened?

The problem is in the model. Android updates seed out through carriers, over the air or with special installers. This is because the updates are their responsibility: once handset manufacturers (and carriers, through handset manufacturers) have built their own version of Android, they’ve effectively taken it out of the development stream. Updating it is their responsibility, which they have to choose to uphold. Or not! Who cares? The phones are already sold. And there’s very little to motivate a carrier or handset manufacturer to update their Android phones, because the consequences tend to fall on Google: If Android fragments, the App Market doesn’t work. The public sours. Android starts to suck. This is where the Nexus One comes in.

Sold without a carrier, software updates for the Nexus One will be in Google’s hands. They will be able to keep it up to date as Android develops, without having to depend on some other company—or companies—not to drop the ball. Users won’t have to bother learning Google’s esoteric dessert-themed version codenames, and life will be better. This approach to software updates already has a case study: the iPhone. There’s a good reason Apple didn’t entrust AT&T with keeping the iPhone up to date, and that they didn’t want the company that actually manufacturers the phone—Foxconn—to have any responsibility for its software. Smartphone software is finicky and complicated, and so is the experience of using it. It needs to be tightly controlled to remain consistent, and because apps are the most important part of a smartphone platform nowadays, consistency is life or death.

Without totally changing what the Android project is, Google can’t put an absolute stop to fragmentation. What they can do is provide an example of how an Android phone should be done. With the Nexus One, Google probably isn’t getting into the business of making hardware; they’re just trying, in their passive, Googly way, to regain control of a project that’s spiraling toward chaos.

Update: Some input from someone who works in a major carrier’s device development group:

There is TONS of incentive for carriers to update their
software. Take a look at Verizon hosting the only Android 2.0 device.
Are you going to tell me that Sprint and T-Mobile wouldn’t love to
have their Android devices on 2.0 yesterday?

The truth is, there’s very little incentive for the Handset maker to
provide an update. All those phones are already sold and in the
carrier’s inventory. Any investment in updating those models will
bring them no additional cash flow. However focusing on their next
model will.

He’s partly right: carriers have a motivation to keep their software up to date, in that they are the ones who have to deal most with customers. Handset manufacturers are the one’s with the least motivation, since their sale has already been made. But in branding a handset with their name, effectively selling it as their product, and assuming responsibility for seeding updates, a carrier becomes responsible for making sure their customers have up-to-date software, and exerting pressure on handset manufacturers is they don’t hold up their end. —Thanks, David!

Reuters is reporting that, according to an unnamed source, the Nexus One may be subsidized by T-Mobile. A site called Android and Me is claiming that T-Mobile will sell it for $199 with contract, starting on January 5.

A January release date sounds reasonable based on what we know about the phone so far, and the information gleaned from the FCC details also makes T-Mobile a potential carrier, should Google take that route. A $199 subsidized price seems like the standard we are seeing elsewhere.

What I really want to know is how much this thing will cost without a contract. [HTC Source via Android and Me via ABC—Thanks, Steven!]