Allegedly leaked Nexus One purchase page answers, raises questions (update: we’ve got the terms of sale)

So apparently the cats over at Gizmodo have gotten their hands on leaked pics of the Nexus One‘s landing and purchase page. First, the meat. According to the pages, the phone will be available in two ways: as a $529.99 unsubsidized and unlocked device, and as a $179.99 T-Mobile device locked to a two year contract. Sound familiar? It should, because it’s exactly the same story as every other phone available on the market right now. Additionally, the pics seem to suggest that there will only be one plan available should you get the device on contract — 500 minutes of talk time, unlimited text, data, and mobile to mobile for $79.99 — which happens to exactly equal what you’d pay for a T-Mobile Even More 500 plan with unlimited smartphone data and unlimited messaging, so that means there’s no bogus premium here. Furthermore, Giz claims that if you cancel your contract within 120 days you have to pay a $350 fee (a la Verizon) or return the phone to Google, and any existing customer that wishes to buy the phone has to switch to the Nexus One plan.

One thing that caught our eye is a mention of personalization — you’ll be able to get the phone engraved, something that we’ve been able to independently confirm through another tipster of ours. It looks like you can do two lines of text on a metallic bar on the back of the device… just don’t expect to return it if you do (seriously, it says right in the terms of service that you’re married to that thing if you get it etched).

To be perfectly honest, it’s hard to say if this is the real deal or not. We don’t get why Google would want to lock you into a single plan, nor do we fully understand why you would need to activate your phone via the website (as shown in the grab). Of course, the big G sometimes works in mysterious ways — perhaps they’re going for a little Apple magic here with restrictive plans and draconian ideas about how you can use the phone. It wouldn’t be surprising given the timing of the company’s little event next week. Don’t worry, all will be revealed soon enough.

Update: Well what do you know. We’ve just been hit with a few photos of our own, apparently straight from HTC training materials, according to a tipster. And what else? Oh yes — a PDF of the terms of sale, which you can download and view right here.

Allegedly leaked Nexus One purchase page answers, raises questions (update: we’ve got the terms of sale) originally appeared on Engadget on Tue, 29 Dec 2009 21:02:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceGizmodo, Terms of sale (PDF)  | Email this | Comments

Leaked Nexus One Documents: $530 Unlocked, $180 With T-Mobile

A tipster just sent in these Nexus One screenshots that supposedly confirms two things: that Google will sell it unlocked and unsubsidized for $530, and that Google will sell it by themselves. Plus, some other very interesting details. UPDATE

Some of the most important bits of info we extracted (assuming the tipster is accurate, and it seems like he is). Oh, and take a look at our hands on with the device in case you haven’t familiarized yourself with it yet.

• Yeah, it’s $530 unsubsidized. Google’s not going to be selling the phone at cost, like so many people considered. They’re not going to save us from the “making money off of hardware” culture we’ve got right now, so this is basically just another Android handset, albeit a really good one
• If you want it subsidized, you’ll have to sign up for a 2 year mandatory contract and pay $180 for the phone
• There’s only one rate plan: $39.99 Even More + Text + Web for $79.99 total
• Existing customers cannot keep their plan if they want a subsidized phone; they have to change to the one plan, and this only applies to accounts with one single line
• If that doesn’t fly with you, you have to buy the $530 unlocked version—this actually might save you money over two years if you already have a cheap plan
• Family plans, Flexpay, SmartAccess and KidConnect subscribers must buy the phone unlocked and unsubsidized for $530
• You can only buy five Nexus One phones per Google account
• There is language in the agreement of shipping outside the US
• Google will sell it at google.com/phone, which explains what they were doing with that page a few weeks ago
• Google will still call it the Nexus One apparently, and not the Google Phone

And here is a big one:
• If you cancel your plan before 120 days, you have to pay the subsidy difference between what you paid and the unsubsidized price, so $350 in this case. Or you can return the phone to Google. You also authorize them to charge this directly to your credit card.

One weirdness in the Terms of Sale that we quickly glanced through was that Google made sure you acknowledged that the manufacturer is HTC, and not Google.

UPDATE: TmoNews is citing sources who claim that Google will begin taking orders on January 5th at 9am

T-Mobile makes internal mention of Nexus One (sort of) for ‘early January’ release

It manages to never actually call out the device by name, but T-Mobile’s thrown up some internal verbiage mentioning that “Google… is scheduled to launch a new Android device in early January.” That would line up with information we’d previously received reporting to some sort of January 5 launch, and we can only assume they’re talking about the Nexus One here — though the name could still change by the time this hits retail channels. Interestingly, T-Mobile calls out that Google and HTC will be directly responsible for support on the handset, bypassing T-Mobile for everything other than wireless service — the great “dumb pipe” dream, realized. Stay tuned, because it looks like this is all about to get real.

T-Mobile makes internal mention of Nexus One (sort of) for ‘early January’ release originally appeared on Engadget on Tue, 29 Dec 2009 11:18:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceTmoNews  | Email this | Comments

Android 2.0 officially coming to T-Mobile G1?

We don’t know where this is coming from so take it with a grain of salt, but rumor has it from AndroidSPIN that the progenitor Android device, the T-Mobile G1, is destined to officially get an over-the-air update for an Eclair build, Android 2-point-something. Hey T-Mo, we know the holidays are pretty much over, but could you validate these whispers for us? Thanks!

[Thanks to everyone who sent this in]

Android 2.0 officially coming to T-Mobile G1? originally appeared on Engadget on Sat, 26 Dec 2009 21:59:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceAndroidSPIN  | Email this | Comments

Google Nexus One Hands On

Thanks to a clandestine meeting with a source, I got a chance to play with and try out the Nexus One. It’s basically, from my time with it, Google’s Droid killer. It’s thin, it’s fast, it’s better in every way.

My source was very firm about no photography, and I didn’t want to jeopardize anything on my source’s end, so there are no photos, hence these photos are ones we’ve already shown you. But, based on all the leaked shots this week, plus the very pretty and very clear one last week from Boy Genius, everyone knows what the phone looks like already. Hell, there’s even a complete UI walkthrough today that’s on YouTube. So I’m going to focus on the experience, and how it compares to the Droid and the iPhone 3GS.

How it feels

The Nexus One is slightly thinner than the iPhone 3GS, and slightly lighter. No hard specs were thrown around, unfortunately, since Google didn’t even let people who they gave the phone to know that. The back is definitely not cheap and plasticky, like the iPhone’s backing, and feels like some sort of rubbery material. So, not smooth like the iPhone, but not as rubbery as the Droid. It’s halfway in-between.

You can call the design the antithesis of the Droid: smooth, curved, and light, instead of hard, square and pointy. It feels long and silky and natural in your hand—even more so than the iPhone 3GS. There are also three gold contacts on the bottom designed for future docking (possibly charging?) use, but there aren’t any accessories available for the phone now. It plugs in via microUSB at the moment.

That screen is damn good

Even though the screen is the same size and same resolution as the Droid, it’s noticeably better. The colors are much more vibrant and the blacks are blacker, as evidenced by putting both side by side and hitting up various websites and loading various games. The pinks on Perez Hilton and the blues on Gizmodo just popped a lot more on the N1, and made the Droid (which was actually considered to have a great screen) seem washed out. The same feeling carries over when you compare the Nexus with the iPhone 3GS. And it’s pretty damn bright, compared to the other two phones.

This is probably the best screen we’ve seen on a smartphone so far. Probably.

Why is it so fast?

Google just gave Motorola (and Verizon) a swift shot to the TSTS, because the Nexus One is astonishingly faster than the Droid. The speed dominance was most evident when we compared the loading of webpages, but even when you’re just scrolling around, launching apps and moving about the OS, you could tell that there’s a beefier brain inside the N1. I don’t know the specs for sure, but there’s talk of a 1GHz processor being inside, which would push it quite a ways above the 550MHz Arm A8 in Motorola’s newest toy.

When comparing the three phones in loading a webpage over Wi-Fi, the Nexus One loaded first, the iPhone 3GS came in a few seconds later, and the Droid came in a little while after that. This was constant throughout many webpage loads, so it’s indicative of something going on inside with the hardware.

I ran all three through a Javascript benchmark engine for some quantifiable numbers, and while the results were similar between the Nexus One and the iPhone 3GS, the Droid still came up at about 60% of the other two. Surprisingly enough, Mobile Safari on the iPhone scored better on the Javscript benches than the Nexus did, even though the Nexus was able to pull down and render actual web pages faster. Note that I didn’t list actual numbers here, for privacy reasons.

That crazy video background

You’ve no doubt heard about the animated video backgrounds, but they’re actually more than just animations: you can interact with them.

The default background is the square/8-bit like one shown above, where lines of colored squares come in from different sides of the screen. What’s neat (even if it is superfluous and battery draining) is that you can tap anywhere on the desktop in a blank space and trigger dots to spread out from your tap. Basically, press anywhere to cause blocks to fly outwards. The same thing happens in the “water” background, except instead of blocks, you cause ripples in the water.

What’s also neat are the two virtual sound meters, which act as a visualizer for whatever music you’re currently playing on your phone. There’s one analog one that looks like one of the old ones with a red needle, and a “digital” one that looks similar to ones you see elsewhere. Sorta neat in itself, but it shows that the interactive backgrounds can actually interact with apps, as long as one knows the other’s APIs.

Other bits

The 5-megapixel camera is nice, and the flash works well enough for a flash on a phone, but it’s not spectacular, as seen by early photos taken and uploaded online by Googlers. There is autofocus, and you activate it with the trackball on the face of the phone. There is no tap-to-focus as see on the iPhone 3GS.

There’s no multitouch in the browser or in the map, but I think at this point that’s more of a legal consideration than a technical one, since many phones that run Android have the capability of supporting multitouch on a hardware level.

Playing back music over the speakers sounded decent, but not great. It’s definitely in need of a dock—like all smartphones—if you want to listen to music for a sustained period.

I didn’t get a chance to call on it, because I wanted to keep this as anonymous as possible, and didn’t want any sort of way to trace when I used the phone. From what other people say in their time with it, it functions fine as a phone, and should work as normally as other Android phones in the SMS/MMS department.

So what’s this all mean?

If Google’s planning on releasing this phone as their official Google phone, it’ll certify them as the premium Android phone brand out there right now. Even though it doesn’t have a hardware keyboard, it basically beats the hell out of the Droid in every single task that we threw at it. And face it, some people didn’t like the Droid’s keyboard because it was too flush and the keys were too unseparated with each other. N1’s onscreen keyboard felt fine, and the speedy processor made sure that each key was interpreted well.

But in the end, it’s still an Android phone. If you want Android phones, this is the one to get, provided Google goes ahead with the rumored plans of either selling it themselves or partnering with T-Mobile in a more traditional role. Droid, shmoid; Nexus is the one you’re looking for.

Image courtesy anonymous tipster

T-Mobile bringing HTC HD2 to the States? All .nbh files point to ‘yes’

You know those times when you’re sifting through an undercooked ROM, dumping .nbh files right and left, asking yourself: “is this even worth it?” Well, the folks at WMExperts can answer with a resounding fist pump after digging up references to T-Mobile US in an HTC HD2 prerelease ROM that was recently leaked their way. At this point we’re looking at a new 2.01 version of the HD2 software in the T-Mobile version, a big jump from the 1.61 seen in previous leaks, which maybe will smooth over some of those performance woes we experienced with the device. WMExperts also claims a March 2010 release date, which seems a while to wait, but somebody told us once about “good things” coming to “waiters” or something like that, so we’re cautiously optimistic.

[Thanks to everyone who sent this in]

T-Mobile bringing HTC HD2 to the States? All .nbh files point to ‘yes’ originally appeared on Engadget on Fri, 18 Dec 2009 18:19:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceWMExperts  | Email this | Comments

Google’s Nexus One lacks multitouch

Our buddy Tnkgrl just had a sit down with Google and HTC’s lovedroid, the Nexus One. She “wasn’t allowed” to take pictures or video but she came away with plenty of detail. The biggest point of clarification might not be what’s included in the handset, but what’s missing: multitouch. She confirms, “no multitouch support in the browser or in Google Maps,” just like Verizon’s Droid (but available on its European Milestone brother). The unit she tested included a 4GB microSD card, 1400mAh battery, worked on T-Mobile’s 3G only (AT&T is limited to EDGE data), and was “super snappy! Faster than the Droid.” She also noted “gold contacts” along the bottom edge presumably for a docking port thus jibing with whispers of a Nexus One Car Dock accessory. Now hit the read link for all the details if you still have the strength.

P.S. We should probably clarify that while the Google Apps tested don’t respond to multitouch, the OS and hardware are presumably multitouch capable. See our previous exhaustive analysis of this topic if you’re wondering why.

Google’s Nexus One lacks multitouch originally appeared on Engadget on Fri, 18 Dec 2009 04:19:00 EST. Please see our terms for use of feeds.

Permalink   |  sourcetnkgrl mobile  | Email this | Comments

How Carriers and Phone Makers Are Strangling Android (And How Google Could Save It)

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!

Google Phone Coming in January, Unlocked, Thinner Than iPhone

google phone nexus one htc

At last, the Googlephone has appeared. Forget the Droid, the G1 and all those other Android wannabees. Google will begin to sell its own reference Android 2.1 handset, designed by Google, made by hardware partner HTC, and called the Nexus One. The phone will be sold online by Google itself.

The Nexus One will, crucially, be sold unlocked, giving Google complete control over the hardware and software with no pesky carrier interference. Even the iPhone, which has had almost unprecedented autonomy in its functionality is still constrained by carriers: AT&T’s anti-tethering paranoia is a good example.

Although not yet officially announced, Google has coyly admitted that the phone is real and will be on sale early in the new year. In fact, it has provided the handset to its employees in order to test it out in the wild. The Google Mobile Blog explains, somewhat cryptically:

We recently came up with the concept of a mobile lab, which is a device that combines innovative hardware from a partner with software that runs on Android to experiment with new mobile features and capabilities, and we shared this device with Google employees across the globe. This means they get to test out a new technology and help improve it.

Unfortunately, because dogfooding is a process exclusively for Google employees, we cannot share specific product details. We hope to share more after our dogfood diet.

The phone is already in use. Nerdy John Gruber of Daring Fireball found this user agent string in his site’s logs:

Mozilla/5.0 (Linux; U; Android 2.1; en-us; Nexus One Build/ERD56C) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17

It makes sense to identify yourself as Mobile Safari, if only to get proper mobile Webkit pages served to you.

Characteristically, and in contrast to Apple’s secrecy, photos of the Googlephone are already being posted openly by Googlers, or being handed to their friends. The picture above, posted on Twitpic by blogger Cory O’Brien, shows the handset (taken on an iPhone and with a BlackBerry in the background). According to O’Brien, “Google Phone = iPhone + a little extra screen and a scroll wheel. Great touch screen, and Android.”

The hardware specs are also leaking. Erick Schonfeld at TechCrunch says that the Nexus will run on Qualcomm’s speedy Snapdragon chip, sport an OLED display, be thinner than the iPhone (with no physical keyboard) and feature two microphones along with a “weirdly large” camera.

Those hoping to get an iPhone-caliber phone on Verizon are out of luck. The Nexus will be a GSM phone, which means T-Mobile and AT&T in the United States. Worse, if you do opt for AT&T, your data connection could be EDGE-only. Gruber again, from Twitter: “The bummer I’m hearing about Nexus One: it’s GSM and unlocked, but on T-Mobile’s 3G band, so it works on AT&T but EDGE-only.”

According to the Media Memo blog at the Wall Street Journal, the choice to use GSM was prompted by Verizon’s refusal to carry the Nexus. Verizon already sells the Android-based Droid, but this odd decision looks like a repeat of the one made when the carrier turned down the iPhone.

This may turn out to be a Zune-like move, where Microsoft alienated hardware makers by ignoring PlaysForSure in favor of its own new DRM scheme. Or the Nexus could be a light that burns twice as bright as all the existing confusion of Android handsets combined, thus building a brand that can rival the iPhone. Either way, we won’t have to wait for long to see. The Nexus should be on sale in early January, and if these last two days are any indication, then Googlers will have “leaked” all the hardware and software well before the launch.

An Android dogfood diet for the holidays [Google Mobile Blog]

Photo: Cory O’Brien


The 30 Essential Android Apps

In a year, Android’s gone from shaky upstart to mobile juggernaut. And nowhere is that more apparent than the apps—the Marketplace is positively bursting, with over 14,000 apps. Here are the ones you need, the essentials.

If you want them all on one page, click here.

If we’ve missed anything or you’ve got a superior alternative, let us know in the comments, since you vastly outnumber us. By ‘us’ I mean me.