Showing posts with label Nexus One. Show all posts
Showing posts with label Nexus One. Show all posts

Google Phone press conference January 5!

Looks like the Google Nexus One speculation is drawing to a close, with the news that Google are hosting an exclusive “Android press gathering” on January 5th. While the Nexus One is not specifically mentioned in the invitation, it seems likely to be the main focus at the event.



“With the launch of the first Android-powered device just over a year ago,” Google’s invite reads, “we’ve seen how a powerful, open platform can spur mobile product innovation. And this is just the beginning of what’s possible.” The all-morning event kicks off with a press conference and presentation, before an opportunity to try out the new device.

We’ve already heard from earlier on today that T-Mobile USA are preparing to support the Nexus One – aka the Google Phone – as the US carrier, though the hardware itself will be supported by Google and HTC. The search giant are expected to sell the Nexus One exclusively through their site online.

Google Nexus One sold directly and only by Google, officially supported by T-Mobile

Interesting. It looks like Google won’t be entirely shaking up any wireless industries at the present time, but it will be pushing forward with its own “flagship” device by selling it directly to consumers. While our connect’s internal T-Mobile photo is rather small, we’ve broken down the text for you:

Google, with support from T-Mobile, is scheduled to launch a new Android device in early January. The Google Android phone will be sold directly by Google via the Web.

Support for the device including troubleshooting and exchanges will be managed by Google and HTC. T-Mobile will offer service support including billing, coverage, features, and rate plans. Additional details Streamline content regarding the launch of Google’s Android phone will be coming in early January.

So… Google is simply selling the phone directly for now, as rumored, and T-Mobile will “officially” support it, even though they practically do the same for any unlocked handset on their network. Google and HTC will be fielding support calls from users, and I’m not quite sure how I feel about that. Unless this is only the Android Development 3 phone. But it’s not just that. And T-Mobile could possibly subsidize it in or around March. Ok, bye.

Google Nexus One specs leak; Initial sales invite-only



Full specifications and some launch news tidbits for the Google Nexus One have emerged, and according to Engadget’s source the first devices – from Google at least – will be offered by invitation only. The first batch are likely going to developers, similar to how Google offered previous dev handsets, but those sales will be followed up by general T-Mobile USA availability. The Nexus One will have a Qualcomm 1GHz QSD8250 processor, UMTS/HSPA 900/1700/2100 (i.e. only EDGE max on AT&T), WiFi a/b/g/n and a 3.7-inch WVGA AMOLED display.

The whole handset measures 119 x 59.8 x 11.5 mm and weighs 130g with the standard 1,400mAh battery. It has 512MB each of flash and RAM, comes with a 4GB microSD card and is compatible with up to 32GB microSDs. Along with the WiFi a/b/g/n there’s Bluetooth 2.1+EDR, A-GPS, various sensors, active noise cancellation with a second microphone and a three-color clickable trackball. OS is Android 2.1 and there’s a 5-megapixel autofocus camera with LED flash.

Meanwhile, the French have managed to acquire a pre-release Nexus One and shoot the slightly blurry 5 minute video you can see below. Journal du Geek commenter Bruce confirms that there’s no Flash support in the Nexus One browser and – as we already knew – no multitouch support, but that the whole thing is “very very very smooth”; more of his photos here.http://www.bheller.com/old/images/NexusGoogleAndroid/







Twitter Captures A Nexus One Unboxing And Another Video



A number of pictures have hit the web now showing the Nexus One, aka the Google Phone, in the flesh. But there haven’t been too many showing its packaging, and it getting unboxed. Today, some Twitpics shared by one user show those. As a bonus, he also shows off a bit of its HTC-innards, and even shared a nice little video of the device in action.

The Nexus One is expected to be released early next year sold both unlocked from Google and in partnership with at least one major carrier. Plenty of Googlers already have the device and have been going around all over the country showing it off. There was previously a video of it booting up, but apparently Google made the YouTube user take it down.





Google Nexus One T-Mobile 3G confirmed; EDGE only on AT&T ; lacks multitouch

The Google Nexus One hands-on reports continue to trickle in, and after Peek CEO Amol Sarva’s reasonably glowing feedback earlier in the week, now it’s tnkgrl who has spent some time playing with the Android 2.1 smartphone. No photos – they weren’t allowed – but plenty of interesting news, including confirmation that the Nexus One only supports T-Mobile USA 3G; you’ll be limited to EDGE on AT&T. Contrasting with earlier speculation that Google might be looking to bypass carrier-voice altogether and instead use VoIP over data, tnkgrl found that voice calls are routed in the regular way.

Elsewhere there’s both a microUSB port and a number of gold connections on the bottom of the handset, which are presumably for docking with Google Nexus One accessories like a car kit.

The unit tnkgrl played with had a 4GB microSD card preinstalled – it’s unclear if that’ll be standard or not – together with a 1,400mAh battery and an 854 x 480 touchscreen which “appears to be OLED”.

The whole thing is described as “super snappy” and faster, in her opinion, than the DROID, as well as extremely thin and “nicer looking in person than in pictures”. Multitouch fans will be disappointed to hear that there’s no support for multi-finger gestures in either the browser or Google Maps, though.'

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.

Why Google Needs Its Own Phone

Someone has to stand up to the carriers.

By now, you've heard the hubbub. Google is preparing its own smartphone to challenge Apple, Palm, Research In Motion, and -- oh, the horror! -- Motorola, a partner with Google. The new Nexus One, as it's known, is presumably slated to be sold through Google's web site, beginning in January.

Verizon executives probably hated this idea when they first heard it. Why? Control. Google plans to relinquish none, according to reports published by The Wall Street Journal. This won't be Droid 2.0.

Carriers just aren't part of the plan, though T-Mobile subscribers may get a discount on the Nexus One if The Big G and Deutsche Telekom reach an accord. The two companies are negotiating now, the Journal reports.

No other handset maker has shown this kind of guts -- or stupidity, if you think Google has gone mentally AWOL -- not even Apple. AT&T has long had a say in how and when the iPhone gets tethering, a technology for connecting a cell phone to a computer to enable wireless Web access.

By going it alone, Google is reframing the argument over who controls the content that appears on a smartphone. Traditionally, that's been carriers. Apple has made progress with the App Store but apparently not enough for Google's taste.

And that's as it should be. Google, fundamentally, is an ad server. It can't allow a private network to stiff-arm software that will help it to collect data from Android handsets. To do so would be to waste the $750 million it spent for mobile ad market AdMob.

Carriers don't mind Google right now. The Droid is a hit. But just as Apple had its own finger-pointing fracas with Ma Bell, Google could suffer a spat with Verizon or T-Mobile over Android apps that pull unwanted data from their networks. That's a problem. Google isn't ever likely to approve of a model that allows carriers to dictate terms. The Big G thrives on unrestricted usage of its services; it's how its advertising engine gets smarter.

Google needs its own phone. Not because the other handset makers are a threat, but because it can't depend on the carriers.

But that's my take. Now it's your turn. Is Google's Nexus One the telecom equivalent of a thrown gauntlet? Please vote in the poll below. You can also sound off in the comments box at the bottom.

Peek CEO gets Google Nexus One hands-on; price speculation increases

Bored of the Google Nexus One yet? Details – and hands-on reports – keep filtering through, and while much of it is still speculation we’re gradually building up a picture of what Google may have in mind. Peek’s Amol Sarva is the latest to play with the Android 2.1 smartphone, and while he’s reasonably impressed with the hardware – he describes the Nexus One as “definitely nice” – he still reckons it’s a pretty mainstream iPhone clone.



Meanwhile, elsewhere there’s talk of a January 5th release date and possible sub-$200 or even sub-$100 pricing for the handset. Earlier this week Reuters quoted “a source familiar with the matter” for the early January launch, with the handset tipped to be on sale through the Google website. However we’re more interested in the possible pricing, and whether the search giant will be selling the Nexus One unlocked and contract-free, or subsidizing it.

Tipsters – anonymous and otherwise – are going wild with speculation, with our old friend Charbax saying Google will offer the Nexus One for $199 or $99 with a rebate; however he also claims the device will use 3G for VoIP on either T-Mobile or AT&T, which is at odds with the FCC report that indicated the Nexus One would be T-Mobile 3G compatible only. Over at AndroidAndMe their source is saying $199 too, with a CDMA version waiting in the wings [via Gear Diary].

All well and good, but certainly nothing approaching conclusive. The prospect of a data-only SIM and contract is interesting, with VoIP and Google Voice used for all the talk and SMS functionality users expect, but given the Google Voice app already available in the Android Market, that doesn’t necessarily distinguish the Nexus One from other devices using the platform. As Amol Sarva says, “I’m not sure there’s anything to go gaga over when comparing it to some of the T-Mobile touchscreens out there.”

10 Points About the Nexus One Google Phone

EWEEK has read some of the 1,400-plus Nexus One reports and cherry picked some points and for you to enjoy and debate here. Will it be sold online, unlocked and subsidized by Google or with a two-year contract from T-Mobile, or both? Is Google risking alienating its current Android partners Motorola, Samsung, Verizon Wireless and Sprint? Questions and theories abound, with few concrete answers.

News Analysis: This Nexus One Google Phone story is getting out of hand. It's reminiscient of satirical movies such as the Scary Movie series, Not Another Teen Movie and others that make fun of sorry slasher and other B-movie fare for teens.

Coverage is getting downright metaphysical. People are writing pieces that underline what is known, what may be known, and what we don't know, scrambling for stakes in the Google News cluster, which Dec. 15 listed a staggering 1,400-plus pieces on the latest Android smartphone.

This Nexus One device has been given to Google employees to test before an alleged January release. The HTC-made device has no physical keyboard, is super fast, powered by Android 2.1, which is powered by a Qualcomm Snapdragon processor. There are proximity and ambient light sensors, and accelerometer: magnetic compass: Wi-fi radio and a noise cancellation chipset.

There is text to speech flavor, dual microphones, and the device runs on GSM, which makes it a candidate for T-Mobile and AT&T's networks in the U.S., and plenty of vendors overseas. The Federal Communications Commission has blessed it and Google has registered Nexus One as a trademark Dec. 10, according to Engadget.

The device will be unlocked, but supposedly supported by T-Mobile, and possibly sold by Google itself online and possibly through Best Buy. Barring subsidies from either T-Mobile or Google, the smartphone could cost $500, pricing it out of range of all but the geekiest of geeks and Google fans.

What do the media and blogosphere have to say about all of this? You just read some of it above. Google is mum beyond a blog post acknowledging that a new device exists and has been given to Google employees to test. EWEEK has read many of the reports and cherry picked some points and rumors for you to enjoy here.

1. Nexus One Named For Blade Runner Robots

Daring Fireball noted the name Nexus One appears to be a nod to the line of replicant cyborgs from late sci-fi author Philip K. Dicks "Do Androids Dream of Electric Sheep," upon which the 1982 film Blade Runner was based. The New York Times went deeper, speaking to Dick's daughter, who claimed Google did not consult her family about using the Nexus One name. I smell a handsome payout in the Dick family's future. One other note: Things didn't turn out so well for the replicants. Superstitious, anyone?

2. Google Already Sells Phones

Technically, this is true. CNET is correct in pointing out that Android developers have been able to buy unlocked versions of the G1 and the T-Mobile MyTouch3G for $399. EWEEK covered this a year ago here.

3. The Nexus One is Just Another Android Phone

Slate.com's Farhad Manjoo noted: "For the Google Phone to be truly stellar, Google would have to imbue it with exclusive features—violating the core Google principle of platform independence. I just don't see that happening; it's not in the company's DNA to make software that works on one device alone." So every phone will be a Google Phone. That may be the single best argument against a Google Phone boasting exclusivity.

4. Unlocked, or Locked With T-Mobile?

Indeed, while the blogosphere was in a tizzy over an unlocked GSM device in the Nexus One, Reuters claims T-Mobile will subsidize the phone cost provided customers agree to a two-year contract. Alternatively, we suppose, one could buy it from Google for $500 or whatever the at-cost production value is. Pick your poison. Pay upfront for no lock-in, or pick T-Mobile, which is starving for more customers. Such is the state of the wireless business in the U.S.

5. Android for All

Then you have Android and Me, which reports that the Nexus One will be an affordable $199, subsidized by Google. What's the catch? The smartphone will require a Google account, so Google will be basically buying new mobile users. Google officials have made a big deal about mobile searches increasing 30 percent in recent quarters. Imagine what a Google phone would do for that number.

6. Nexus One For Consumers? You Must Be Crazy

Industry analyst Jack Gold has a markedly different theory: "Despite the widespread conjecture of the past few days, it is highly unlikely that this phone will ever be offered to the general consumer, let alone sold by Google directly to end users." Gold sees the Nexus One as a test bed for several thousand Google workers and developers. "Testing is the path that Google has chosen for this device, and not the path of competing with its customers." The company wouldn't alienate Motorola, Samsung and the carriers.

7. Then Again

With Apple's iPhone dominating the smartphone space, Google may believe that it must roll out and subsidize the Nexus One -- a drastic, bold move by any measure -- to gain serious headway in the mobile market. It's not so much about the devices as it is about the mobile searches and the ads Google wants to show along with THEM. Sure, Google serves ads on Google searches executed through the iPhone now, but who is to say Apple won't shut Google out for a better deal with Bing?

8. So What?

The Wall Street Journal doesn't believe Google needs its own special phone to succeed in mobile, noting (paywall): "Mobile apps are taking the place of Web sites. While there clearly will be a place for search in helping people find apps, Web-surfing behavior will change on mobile. But Google became the dominant player in Web search without designing computers. It is unclear why it needs to sell mobile phones to dominate mobile search." One can't help but think Google and its supporters might argue the alternative

9. Meet The New SAAS -- Smartphones as A Service

More broadly, Google wants to uproot the current wireless phone market. Google wants to flip the mobile carrier and distribution market upside-down, becoming the place you go to search for and buy a mobile phone -- before you even pick a carrier, number, voice and data plans, or extras, according to this piece in Business Insider, which spells out how this purchase process would work. It's a must read, and, while BI is identifying the business model, eWEEK hereby claims the smartphone-as-a-service (SAAS) moniker.

10. Bonus Point (Cold Water)

With all that's been speculated, from pros to cons of the device, doesn't the timing of all of this seem a bit off? Why would Google seed the Nexus One with employees, then turn around and mass sell it to consumers in January. How much testing could employees possibly do for Google in a few weeks or a month before the search engine is allegedly supposed to turn around and start selling this to the mass market? Seems sketchy, unless of course the only thing that's been completely misreported is the January timeline.

Nexus One finally caught on video alongside its packaging



Frankly, we're surprised it took this long, but lo and behold, here we are with the first video of the Nexus One we've seen. It's just the all-too-brief and familiar boot animation, but thenexusone.com promises this is just one of many videos to come, and with any luck, a nicer video camera can be found in the interim. Also on hand is a few snapshots of the casing it came with -- don't read too much into that, however, as even the developer-only Google Ion had fancy packaging.

A Google Phone could be the death of Android



Without a doubt, the big buzz since the weekend has been over the "Google Phone," an HTC-built device called the Nexus One handed out to Google employees last week in what Google describes as a "mobile lab." Confirmed to be running Android 2.1, the Nexus One has once again raised the idea of Google selling unlocked devices directly to consumers. (Google has been selling unlocked HTC Android phones for some time, but only to developers.)

It would be a strange turnabout if Mountain View made this move, directly going in the face of previous assurances that Google had no plans to compete directly with Android hardware manufacturers. What's more, there are a lot of unanswered questions here.

The first question: How would Google bring an unlocked phone to market? There are really only three ways to sell phones. The first is to license spectrum from a carrier and become a mobile virtual network operator or MVNO -- a business model that time has proven to be a failure. The second, of course, is to partner with carriers and offer phones at discounted prices through carrier subsidies, which is more or less the case with every successful device on the US market today. The final model is to sell unlocked devices at full retail price that can be used by consumers on the network of the their choice. This is allegedly the model Google will be using to sell the Nexus One.

Selling unlocked devices sans carrier is a lousy business model in the States, however. There's no mass market for unlocked phones in the US -- just ask Nokia how hard it is to sell a high end phone with no carrier subsidy or support. Either Google would need to take a huge loss on every device to achieve a consumer-friendly price point, or hope to convince consumers to pay full price for an unsubsidized device -- even though Eric Schmidt in the past has argued phone prices need to trend to zero through full subsidies. What's more, an unlocked device will at least get you onto T-Mobile and AT&T's EDGE networks, but Verizon and Sprint both require phones that are approved for network use and can easily be locked out.

There's something even more fundamental that struck me as I listened to the "Google Phone" chatter, and that's the basic challenge of licensing to competitors. One reason Microsoft is successful in the PC industry is that it's never built PCs. Licensing to folks you compete with doesn't work: either your licensees do better than you do, in which case why bother, or you do better than your licensees, in which case your licensees wise up and go elsewhere. Apple's tried this twice: first with the Newton, where Apple did better than the licensees, and second with Classic Mac OS, where licensees like Power Computing did better than Apple -- eventually driving Cupertino to give up on the licensing idea entirely. Palm tried it, and it eventually had to split up into Palm and Palm Source. Nokia tried it with S60. The whole point of the Open Handset Alliance is to create a partner ecosystem of handsets and other devices, and a "Google Phone" that undercuts both carriers and licenses might well be the death of Android in the marketplace.

There might be a strategy here that allows for this to happen -- I can even think of one or two -- but until someone can give me a ten-word answer to how Mountain View can manage to build an ecosystem while trying to compete with it, I will remain skeptical that the Google Phone ever comes to market.

Google Nexus One's Hardware Components: Looking Good



Thesearethedroids.com has a running list of the hardware components in the Nexus One, gleaned from the Android 2.1 ROM. Read onward for lengthy and confusing chipset names!

* Proximity Sensor/Light Sensor: Capella CM3602 per sensors.mahimahi.so in Nexus One ROM Dump.
* Accelerometer: BMA150 3-axis Accelerometer per sensors.mahimahi.so in Nexus One ROM Dump.
* Magnetic Compass: AK8973 3-axis Magnetic field sensor/AK8973 Orientation sensor per sensors.mahimahi.so in Nexus One ROM Dump.
* Wifi Radio / Bluetooth / FM: BCM4329 in lib/modules
* In libaudio.so I found "Routing audio to Speakerphone with back mic" reference.
* In libaudio.so I found "Stereo FM speaker" also referenced.
* Audience A1026 Noise Canceling Chip – No link but here is the A1024 found in libaudio.so

Google’s Nexus One to be sold starting January 5?

I’m sure you’ve already noticed how everyone’s talking about the Google Phone aka Nexus One these last few days. We’ve already heard that the smartphone might be available starting January 2010, and it looks like it will happen very early in January.


According to a brief report found at Reuters, a source familiar with the matter says that the Nexus One may be on sale directly from Google (most probably unlocked) as soon as January 5. Unfortunately, there’s no word yet on the smartphone’s price.

The same source mentions that T-Mobile USA will also offer the Nexus One (on contract) – this kind of confirming the previously-heard rumors.

Of course, we can’t be sure of anything until Google officially announces the Nexus One – let’s hope it won’t be long until this happens.

Whether or not Google plans to offer its own Android 2.1 handset outside the US is still a mystery for now.

Manufactured by HTC, the Nexus One reportedly features a 3.7 inch WVGA display, a new UI with 3D elements, a 5MP camera and lots of Google services (including Google Navigation and Google Goggles).

Android 2.1's boot animation for the Nexus One reminds us of... something



Red, green, blue, yellow. They aren't just four of the bestest shades in Roy G. Biv -- to anyone with a computer and a soul, that particular color combo is permanently etched in the brain as the unchanging constituents of the Windows logo in its many, many forms over the years; Google's logo happens to use them, true, but so far, Android's been green to the bone. Anyhow, you may have already noticed that some of the shots of the Nexus One clearly show a boot screen with a cross pattern colored thusly, and it turns out there's an Android 2.1 dump floating around that's got the animation on board. Of course, dumped ROMs have a tendency to get pulled apart like a turkey at Thanksgiving dinner in a matter of mere hours, and the animation's already found its way onto YouTube. Just because it's in a hacked Flan ROM doesn't mean you should expect to see it on every Android phone under the sun next year -- the animation portrays a nexus, of sorts, which would fit in nicely with a phone of the same name.

Seriously though, check out the wait cursor in Windows Mobile 6.5 for comparison



And yes, we know you can only combine colors so many ways -- we doubt there was any intentional inspiration here -- but regardless, we're chalking it up as a cute homage to a platform Android hopes to destroy.

Google Nexus One photos confirm Android 2.1 & T-Mobile support

The tubes through which the internet flow were bursting with Google Nexus One speculation this weekend, with the prospect of an “official” Google Phone driving many Android geeks to madness. A leaked photo over the weekend confirmed that the Nexus One appeared to be based on the same HTC device we knew as the HTC Dream, and now Engadget have come up with a few new images themselves. The Nexus One in their shots is devoid of HTC logos and runs Android 2.1.



According to their source, the Google Nexus One has more homescreen panes on offer and new 3D elements to the app tray, while an overnight firmware update now adds the handset name to the device’s status page. Google have also added a webOS-style card preview of open applications, rather than the current dumb app switcher, and both Google Maps Navigation and Google Goggles are preinstalled.

The supplied documentation, meanwhile, points to a questions page at google.com/phone/support, not currently active, while the photos show both T-Mobile as the carrier currently in use and WiFi as being active. Apparently the tape on the back of the handset is covering a QR code. Speculation is currently leaning toward this being a developers’ device, in the same manner as the Google Dev Phone 1 and the Google Ion, offering Android coders higher-specification hardware to keep up with the latest range of devices using the platform.











More - HTC-made Google Nexus One certified by FCC


The “Google phone,” HTC’s Nexus One, was approved this morning by the U.S. Federal Communications Commission as model number PB99100.

The trio of filings (first, second, third) confirm a few technical details, such as microSD expansion, 802.11b/g Wi-Fi and Bluetooth 2.1 + EDR.



The report also raises new questions about the device’s potential carrier landing spot, with support for quad-band GSM/GPRS/EDGE with UMTS/HSUPA on 850/1700/1900 frequencies.

Translation: Hello T-Mobile, and perhaps AT&T, too.

The Google Phone: what we know... and what we don't



There's been an immense amount of crosstalk, speculation, and just plain noise over the past 48 hours about a device allegedly called the Nexus One, or as it's more commonly known: the Google Phone. We've heard all sorts of reports about the HTC-made device, and figured it might be helpful to put together a little roundup about what we know -- and don't -- on one of the potentially more exciting devices we've seen recently. Read on for an exploration of what this device could mean, as well as a little editorial perspective on some of those "confirmed" stories of the day!

Update: Peter Kafka over at All Things Digital says that T-Mobile is now on-board to sell this device as an unsubsidized, unlocked phone through its retail channels (he claims the big G first went to Verizon, but was turned down). That doesn't really make a lot of sense if the phone does indeed work on both T-Mobile and AT&T 3G networks. We can't see what's in it for T-Mobile in that scenario, unless this were 3G only on its network, like... previous Google dev phones. We can't help but feel there's a crucial piece of this puzzle still missing -- here's hoping we get that info soon.

The phone doesn't really have an official name, though it's obviously being referred to as the Google Phone, and both its user agent string (browser identifier) and EXIF data on pictures taken on the device identify it as the "Nexus One," which we take to be a code name for the phone (it's also a reference to a line of replicants in the film Blade Runner). Some shots identify the device as "Phone 88," apparently an earlier code name. It is highly unlikely it will be released to the public as the Nexus One, in our opinion.
The phone was given to Google employees at an all-hands meeting on Friday, December 10th. The story broke when a number of Googlers tweeted about the phone.
Google posted on its blog that it was experimenting with "eating its own dogfood" on the Android front by giving employees "around the globe" a device to test. There have been zero -- zero -- official statements about Google selling the device to retailers or directly to consumers. There is a Wall Street Journal article which claims that this is the strategy Google is headed in, but the post contains a number of poorly sourced and suspect facts, so we say take it with a major grain of salt. Other reports say "what if" and "could." That doesn't make it so. As of right now, the only way to get this phone is to work for Google.
The phone itself appears to be the HTC Dragon / Passion (with at least the specs of the Bravo, which looks to be a variant of the other models). All are Snapdragon-based phones with a 3.7-inch AMOLED displays, 5 megapixel cameras, and no physical keyboards.
There have been rumors (or fact, as stated in the aforementioned WSJ report) that this phone runs a "real" or different version of Android. Based on the pictures we've seen, this is inaccurate. It appears to run a version of Android that looks nearly identical to the version currently found on the Droid (2.0.1) -- Google's latest, most official device. The version number we've heard is Android 2.1, which would not be a drastic departure from 2.0.
There are rumors that if sold, the device will be available unlocked and able to function on both AT&T and T-Mobile 3G bands. A source tells us that they have spoken with someone with first-hand knowledge, and this is the case, despite earlier rumors that it would only function using T-Mobile's 3G network.

And now, some philosophical perspective on what this device could mean, depending on how it ends up coming to market.


As we said, there is currently a theory floating around that the Google Phone will be sold directly by Google to consumers, or by the company to retailers and carriers. If that is the case, it should cause a real splintering of the Open Handset Alliance, and could also be a sign that Google is moving away from its "all in" mentality demonstrated at the birth of Android. Positioning itself as the purveyor of the "real" Google Phone, while controlling distribution of both hardware and software for that device could be hugely disruptive to its current strategy of 'one platform, many devices' (clearly taken from the Windows Mobile handbook). A move to full control over its ecosystem and hardware in this way certainly calls to mind something closer to Apple's strategy, though it is still confusing as to why Google would make this move given the relative success and growth of Android worldwide. Our guess would be the pressures to homogenize the experience and give developers a single path to app creation may now seem more logical to the company; it's worked beautifully for their biggest rival.


What everyone seems to be ignoring is the fact that Google has created two other "Google Phones" in the past; the Dev Phone 1 (shock, an unlocked phone that Google sold online!), and the Ion. Both were "Google" phones, both were given out to employees early on, and both were built by HTC. They also both went on to become "with Google" devices, and it's entirely possible that the Nexus One is the next generation of those phones. Given the fact that there is currently no developer device with specs similar to Android's current high water mark (the Droid), seeing a new dev phone with a faster CPU, newer version of Android, and higher resolution screen actually makes perfect sense. If we were the betting type, we'd say you were going to see this phone come to market much in the way the myTouch and G1 did -- as official, Google branded devices. Google Phones, if you will.

Regardless, all we know of this phone and Google's strategy behind it has been built largely atop rumors. The phone clearly exists, and some employees clearly have it, but as to what the long term positioning will be, Google has been 100 percent silent -- a point to note when reading articles claiming that this device is "confirmed" as being sold by Google. There is no evidence of that. For now, stay tuned -- we'll have more info as we get it!

Google Phone Nexus One makes first Twitter appearance?


Look familiar? For a story that broke on Twitter it's only fitting that the first reported picture of the mythical, magical "Google Phone" (AKA, Nexus One) would appear there as well. The tweeted image above appears courtesy of one Cory O'Brien, an account manager at a San Francisco Bay Area marketing agency that does not list Google as a client. That note of caution aside, the image above is an exact match to that leaked HTC Passion / Bravo image from October, only this time lacking the HTC logo on the top-side bezel. Besides the pic, O'Brien tweets that the "Google Phone = iPhone + a little extra screen and a scroll wheel. Great touch screen, and Android." Granted, none of this is confirmed yet, but with Google releasing so many of the devices as part of its "mobile lab" concept, well, we expect to see plenty more sightings in the run up to the rumored January launch.

Update: A quick search for "nexus one" on Google's Picasa photo service reveals several pictures taken with a camera pegged as the HTC Nexus One in the EXIF data. The very first of these geotagged 2592×1944 pixel (that's a 5 megapixel sensor folks, hardly "weirdly large" as described by TechCrunch) images were taken by user Bradley (who just happens to be a Picasa friend to Sergey... hint) in the SF Bay Area on November 27th. A few are clearly lit by an onboard flash as well. In fact, many of the pics appear to be taken from within Google's offices and at Google sponsored events. The quality is not exactly spectacular and that won't likely change in the final product because even Google's bound by the laws of physics when it comes to tiny cellphone sensors.

Update 2: The device seems to have been around earlier with an EXIF identifier of "Phone88." Fortunately, Google's own employees have uploaded pics of the device, by the device, for us to marvel at -- so meta. Check the gallery for the images or a quickie close-up posted after the break.


powered by Blogger | WordPress by Newwpthemes | Converted by BloggerTheme