<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>owngadget.com&#187; Nexus One</title>
	<atom:link href="http://owngadget.com/tag/nexus-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://owngadget.com</link>
	<description>Tech News and Reviews</description>
	<lastBuildDate>Wed, 21 Dec 2011 10:13:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Nexus One sees red, nearly doubles battery life?</title>
		<link>http://owngadget.com/2010/07/06/nexus-one-sees-red-nearly-doubles-battery-life/</link>
		<comments>http://owngadget.com/2010/07/06/nexus-one-sees-red-nearly-doubles-battery-life/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 03:18:57 +0000</pubDate>
		<dc:creator>Raymond.J</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=3006</guid>
		<description><![CDATA[These five Nexus One smartphones may seem to have defects, but there&#8217;s actually nothing wrong with their AMOLED screens &#8212; the funky colors are an attempt to improve battery life by turning off unnecessary sub-pixel LEDs. Hooking up his handset to an industrial power meter, Android engineer Jeff Sharkey discovered a blood-red screen drew 42]]></description>
			<content:encoded><![CDATA[<div><a href="http://www.engadget.com/2010/07/03/nexus-one-sees-red-nearly-doubles-battery-life-video/"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/07/7-3-10-nexusonenightvision600.jpg" border="0" alt="" hspace="4" vspace="4" /></a></div>
<p>These five <a href="http://www.engadget.com/tag/NexusOne/">Nexus One</a> smartphones may seem to have defects, but there&#8217;s actually nothing  wrong with their <a href="http://www.engadget.com/tag/AMOLEDscreens/">AMOLED  screens</a> &#8212; the funky colors are an attempt to improve battery life  by turning off unnecessary sub-pixel LEDs. Hooking up his handset to an  industrial power meter, Android engineer Jeff Sharkey discovered a  blood-red screen drew 42 percent less current than full color &#8212; the  least of any combination by far &#8212; purportedly doubling the effective  battery life of the phone. While you&#8217;re probably not going to be able to  test the requisite software patch for yourself unless you&#8217;re mildly  familiar with Google code, you&#8217;ll find a video of the crimson wonder  after the break to fuel your dreams of a eyestrain-free astronomy cheat  sheet&#8230; and Android bullfighting, of course.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/07/06/nexus-one-sees-red-nearly-doubles-battery-life/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTC EVO 4G, Nexus One, and Droid face off on the charted field of battle</title>
		<link>http://owngadget.com/2010/03/24/htc-evo-4g-nexus-one-and-droid-face-off-on-the-charted-field-of-battle/</link>
		<comments>http://owngadget.com/2010/03/24/htc-evo-4g-nexus-one-and-droid-face-off-on-the-charted-field-of-battle/#comments</comments>
		<pubDate>Wed, 24 Mar 2010 09:47:38 +0000</pubDate>
		<dc:creator>Raymond.J</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[DROID]]></category>
		<category><![CDATA[HTC EVO 4G]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=2450</guid>
		<description><![CDATA[HTC EVO 4G Google Nexus One Motorola Droid Android OS 2.1 with Sense UI 2.1 2.01 Carrier Sprint All2 Verizon Wireless Network technology 1x / EV-DO Rev. A / WiMAX Various (including 3G) 1x / EV-DO Rev. A Processor 1GHz Snapdragon 1GHz Snapdragon 550MHz TI OMAP 3430 RAM 512MB 512MB 256MB Screen size 4.3-inch 3.7-inch]]></description>
			<content:encoded><![CDATA[<table border="0" cellspacing="4" cellpadding="4">
<tbody>
<tr>
<td width="25%" align="center" valign="bottom"><strong><a href="http://www.engadget.com/tag/evo"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/03/evo-4g-rm-eng_124x200.jpg" border="0" alt="" hspace="4" vspace="4" /></a><br /> HTC EVO 4G</strong></td>
<td width="25%" align="center" valign="bottom"><strong><a href="http://www.engadget.com/tag/nexusone"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/03/n1-small-rm-eng_118x195.jpg" border="0" alt="" hspace="4" vspace="4" /></a><br /> Google Nexus One</strong><strong><br /> </strong></td>
<td width="25%" align="center" valign="bottom"><strong><a href="http://www.engadget.com/droid"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/03/droid-small-rm-eng_101x190.jpg" border="0" alt="" hspace="4" vspace="4" /></a><br /> Motorola Droid</strong></td>
</tr>
</tbody>
</table>
<table border="1px solid black" cellspacing="4" cellpadding="4" frame="HSIDES" rules="ROWS">
<tbody>
<tr>
<td width="25%" valign="top">Android OS</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">2.1 with <a href="http://www.engadget.com/tag/senseui">Sense  UI</a></td>
<td width="25%" valign="top" bgcolor="#ffffff">2.1</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">2.0<sup>1</sup></td>
</tr>
<tr>
<td width="25%" valign="top">Carrier</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Sprint</td>
<td width="25%" valign="top" bgcolor="#ffffff">All<sup>2</sup></td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Verizon Wireless</td>
</tr>
<tr>
<td width="25%" valign="top">Network technology</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1x / EV-DO Rev. A / WiMAX</td>
<td width="25%" valign="top" bgcolor="#ffffff">Various (including 3G)</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1x / EV-DO Rev. A</td>
</tr>
<tr>
<td width="25%" valign="top">Processor</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1GHz Snapdragon</td>
<td width="25%" valign="top" bgcolor="#ffffff">1GHz Snapdragon</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">550MHz TI OMAP 3430</td>
</tr>
<tr>
<td width="25%" valign="top">RAM</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">512MB</td>
<td width="25%" valign="top" bgcolor="#ffffff">512MB</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">256MB</td>
</tr>
<tr>
<td width="25%" valign="top">Screen size</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">4.3-inch</td>
<td width="25%" valign="top" bgcolor="#ffffff">3.7-inch</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">3.7-inch</td>
</tr>
<tr>
<td width="25%" valign="top">Resolution</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">800 x 480</td>
<td width="25%" valign="top" bgcolor="#ffffff">800 x 480</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">854 x 480</td>
</tr>
<tr>
<td width="25%" valign="top">Touch</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Capacitive multitouch</td>
<td width="25%" valign="top" bgcolor="#ffffff">Capacitive multitouch</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Capacitive multitouch</td>
</tr>
<tr>
<td width="25%" valign="top">Physical keyboard</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">&#8211;</td>
<td width="25%" valign="top" bgcolor="#ffffff">&#8211;</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Slide-out landscape QWERTY</td>
</tr>
<tr>
<td width="25%" valign="top">Internal storage</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1GB</td>
<td width="25%" valign="top" bgcolor="#ffffff">512MB</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">512MB</td>
</tr>
<tr>
<td width="25%" valign="top">Expandable storage</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">microSD</td>
<td width="25%" valign="top" bgcolor="#ffffff">microSD</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">microSD</td>
</tr>
<tr>
<td width="25%" valign="top">Rear camera</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">8MP w/ LED flash</td>
<td width="25%" valign="top" bgcolor="#ffffff">5MP w/ LED flash</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">5MP w/ LED flash</td>
</tr>
<tr>
<td width="25%" valign="top">Video recording</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1280 x 720</td>
<td width="25%" valign="top" bgcolor="#ffffff">720 x 480</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">720 x 480</td>
</tr>
<tr>
<td width="25%" valign="top">Front camera</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1.3MP</td>
<td width="25%" valign="top" bgcolor="#ffffff">&#8211;</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">&#8211;</td>
</tr>
<tr>
<td width="25%" valign="top">Battery</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1500mAh</td>
<td width="25%" valign="top" bgcolor="#ffffff">1400mAh</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">1400mAh</td>
</tr>
<tr>
<td width="25%" valign="top">WiFi</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">802.11b/g</td>
<td width="25%" valign="top" bgcolor="#ffffff">802.11b/g</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">802.11b/g</td>
</tr>
<tr>
<td width="25%" valign="top">HDMI out</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Yes</td>
<td width="25%" valign="top" bgcolor="#ffffff">&#8211;</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">&#8211;</td>
</tr>
<tr>
<td width="25%" valign="top">Kickstand</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">Yes</td>
<td width="25%" valign="top" bgcolor="#ffffff">&#8211;</td>
<td width="25%" align="center" valign="top" bgcolor="#eeeeee">&#8211;</td>
</tr>
</tbody>
</table>
<p> <script type="text/javascript">// <![CDATA[// <![CDATA[
 digg_url = 'http://digg.com/hardware/HTC_EVO_4G_Nexus_One_and_Droid_face_off_at_Engadget'; 
// ]]&gt;</script><script src="http://digg.com/tools/diggthis.js"></script> As you&#8217;ve probably noticed, we have something of a <a href="http://www.engadget.com/2010/02/15/windows-phone-7-series-faces-off-against-its-windows-mobile-past/">propensity  for charts</a> &#8212; hey, organization is key to a well-balanced life,  right? Since we last tackled an Android device faceoff, the sheer number  of competitors has branched out far and wide, but despite the <a href="http://www.engadget.com/2010/03/05/entelligence-will-android-fragmentation-destroy-the-platform/">propagation  / fragmentation</a>, including today&#8217;s unveiling of the <a href="http://www.engadget.com/2010/03/23/htc-evo-4g-is-sprints-android-powered-knight-in-superphone-armo/">HTC  EVO 4G</a>, three clear frontrunners have taken most of the spotlight  for being the pinnacle of the Android experience: the aforementioned,  HTC / Google&#8217;s <a href="http://www.engadget.com/tag/NexusOne/">Nexus One</a>,  and the <a href="http://www.engadget.com/tag/MotorolaDroid/">Motorola  Droid</a>. Here, the latter device is looking a bit long in the tooth,  but that physical QWERTY keyboard and its volcanic rise to prominence  gives it some strong staying power. Cold, hard data isn&#8217;t going to tell  the full story, but until you can get to try each of these yourself &#8212;  all <a href="http://www.engadget.com/photos/htc-evo-4g-vs-iphone-vs-nexus-one-0/">at  the same time</a>, if you&#8217;re lucky &#8212; it&#8217;s a great place to start.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/03/24/htc-evo-4g-nexus-one-and-droid-face-off-on-the-charted-field-of-battle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How would you change Google&#8217;s Nexus One?</title>
		<link>http://owngadget.com/2010/03/01/how-would-you-change-googles-nexus-one/</link>
		<comments>http://owngadget.com/2010/03/01/how-would-you-change-googles-nexus-one/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 07:35:18 +0000</pubDate>
		<dc:creator>Raymond.J</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=2086</guid>
		<description><![CDATA[It hasn&#8217;t quite been out (in public hands, anyway) for two months, but Google&#8217;s Nexus One has managed to grab the world&#8217;s attention and focus it squarely on Android. Specs wise, it&#8217;s not the superphone that many had expected, but it&#8217;s certainly delightful in its own right. For those who have sprung for one, we&#8217;re]]></description>
			<content:encoded><![CDATA[<div><img src="http://www.blogcdn.com/www.engadget.com/media/2010/02/nexus-one-handson.jpg" border="1" alt="" hspace="4" vspace="4" /></div>
<p>It hasn&#8217;t quite been out (in <a href="http://www.engadget.com/2010/01/02/exclusive-google-nexus-one-hands-on-video-and-first-impressio/">public hands</a>, anyway) for two months, but Google&#8217;s <a href="http://www.engadget.com/2010/01/04/nexus-one-review/">Nexus One</a> has managed to grab the world&#8217;s attention and focus it squarely on Android. Specs wise, it&#8217;s not the superphone that many had expected, but it&#8217;s certainly delightful in its own right. For those who have sprung for one, we&#8217;re bubbling over in anticipation to hear how you&#8217;d change it. Would you have snuck an overclocked processor in there? Would you have ditched the trackball for a sensor pad? Do you wish it were available on more carriers? Is the call quality up to snuff? Look &#8212; there&#8217;s a better-than-decent chance that you threw down some serious bills on this, so don&#8217;t hold back. The Nexus Two just won&#8217;t be the same without your pair of pennies.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/03/01/how-would-you-change-googles-nexus-one/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Nexus One censors your voice-to-text input, we #### you not</title>
		<link>http://owngadget.com/2010/01/25/googles-nexus-one-censors-your-voice-to-text-input-we-you-not/</link>
		<comments>http://owngadget.com/2010/01/25/googles-nexus-one-censors-your-voice-to-text-input-we-you-not/#comments</comments>
		<pubDate>Mon, 25 Jan 2010 09:07:47 +0000</pubDate>
		<dc:creator>Raymond.J</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1829</guid>
		<description><![CDATA[It&#8217;d be kinda funny if someone was live-bleeping your profanity, right? Sure, but five minutes later you&#8217;d sober up to regret and lingering annoyance. Turns out the Nexus One does it for real, courtesy of Google&#8217;s speech-to-text engine &#8212; it replaces notorious curses like the F and S words with a &#8216;####,&#8217; which is a]]></description>
			<content:encoded><![CDATA[<div><a href="http://news.cnet.com/8301-17852_3-10440115-71.html"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/01/nexus-one-censorshpi-rm-eng.jpg" border="1" alt="" hspace="4" vspace="4" /></a></div>
<p>It&#8217;d be kinda funny if someone was live-bleeping your profanity, right? Sure, but five minutes later you&#8217;d sober up to regret and lingering annoyance. Turns out the <a href="http://www.engadget.com/tag/nexus+one">Nexus One</a> does it for real, courtesy of Google&#8217;s speech-to-text engine &#8212; it replaces notorious curses like the F and S words with a &#8216;####,&#8217; which is a more dramatic take on the <a href="http://ww.engadget.com/tag/zune+hd">Zune HD</a>&#8216;s now-obsolete <a href="http://www.engadget.com/tag/censorship%2Czune">Twitter censorship</a>. As silly as this sounds, Google has come up with a good reason:</p>
<blockquote><p>We filter potentially offensive or inappropriate results because we want to avoid situations whereby we might misrecognize a spoken query and return profanity when, in fact, the user said something completely innocent.</p></blockquote>
<p> Kudos for caring, but it wouldn&#8217;t hurt to have an on / off option either &#8212; after all, it&#8217;s not like we&#8217;re asking for <a href="http://www.engadget.com/2010/01/19/editorial-googles-multitouch-dilemma/">pinch-to-zoom</a> here, and we&#8217;ll promise to use a swear jar.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/01/25/googles-nexus-one-censors-your-voice-to-text-input-we-you-not/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nexus One review</title>
		<link>http://owngadget.com/2010/01/06/nexus-one-review/</link>
		<comments>http://owngadget.com/2010/01/06/nexus-one-review/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 14:50:29 +0000</pubDate>
		<dc:creator>Arlene.L</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1397</guid>
		<description><![CDATA[// The Nexus One. In the modern climate of hyped (and over-hyped) smartphone launches, Google&#8217;s official entry into the phone-sales game has excelled in a department where many find difficulty: generating legitimate excitement. Of course, long before the name Nexus One or the recent bounty of pictures and details existed, the very concept of a]]></description>
			<content:encoded><![CDATA[<div><img src="http://www.blogcdn.com/www.engadget.com/media/2010/01/eng_nexus_60012.jpg" border="1" alt="" hspace="4" vspace="4" /></div>
<p><script type="text/javascript">// <![CDATA[// <![CDATA[
 digg_url = 'http://digg.com/gadgets/Nexus_One_review_Engadget'; 
// ]]&gt;</script><script src="http://digg.com/api/diggthis.js"></script>The Nexus One. In the modern climate of hyped (and over-hyped) smartphone launches, Google&#8217;s official entry into the phone-sales game has excelled in a department where many find difficulty: generating legitimate excitement. Of course, long before the name Nexus One or the recent bounty of pictures and details existed, the very concept of a &#8220;Google Phone&#8221; had been ingrained in the public conscience, predating even the <a href="http://www.engadget.com/tag/OpenHandsetAlliance/">Open Handset Alliance</a> and Android itself; the company dabbled in the concept of direct sales through its offering of the Android Dev Phones 1 and 2 (alias Ion), but this time, it&#8217;s a public retail ordeal, not a couple of one-off developer specials. The genuine-article Google Phone is finally here &#8212; for better or worse.<span id="more-1397"></span></p>
<p> The device, a Snapdragon-powered, HTC-built phone looks &#8212; on paper, at least &#8212; like the ultimate Android handset, combining a newly tweaked and tightened user interface with killer industrial design. A sleek, streamlined phone that can easily go toe-to-toe with the iPhone 3GSs, Pres, and Droids of the world, powered by the latest version of Android (2.1 &#8220;Flan,&#8221; if you&#8217;re counting), and hand-retooled by Google. But is it all it&#8217;s cracked up to be? Can the Nexus One possibly live up to the hype ascribed to it? And more importantly, is the appearance of the phone the death knell for the OHA and a sign of the coming Android autocracy? In our exclusive review of the Nexus One, we&#8217;ll answer all those pressing questions and more&#8230; so read on for the full scoop!</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/01/06/nexus-one-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Nexus One is official</title>
		<link>http://owngadget.com/2010/01/06/googles-nexus-one-is-official/</link>
		<comments>http://owngadget.com/2010/01/06/googles-nexus-one-is-official/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 13:47:28 +0000</pubDate>
		<dc:creator>Arlene.L</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1368</guid>
		<description><![CDATA[// We know, you&#8217;re so surprised. Google&#8217;s finally confirmed the Nexus One. We&#8217;ve naturally heard all about the phone already from dubious sources, and even reviewed the purported device, but now that they&#8217;ve got one in hand up on a stage, we suppose we&#8217;ll have to set aside all of our doubts. So, the nitty]]></description>
			<content:encoded><![CDATA[<div><a href="http://www.google.com/phone"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/01/nexus-one-event-0023-rm-eng.jpg" border="0" alt="" hspace="4" vspace="4" width="600" height="398" /></a></div>
<p><script type="text/javascript">// <![CDATA[// <![CDATA[
 digg_url = 'http://digg.com/tech_news/Google_s_Nexus_One_is_official_Engadget'; 
// ]]&gt;</script><script src="http://digg.com/tools/diggthis.js"></script> We know, you&#8217;re so surprised. Google&#8217;s <a href="http://www.engadget.com/2010/01/05/live-from-googles-android-press-conference/">finally confirmed</a> the <a href="http://www.engadget.com/tag/NexusOne/">Nexus One</a>. We&#8217;ve naturally heard all about the phone already from <em>dubious</em> sources, and even <a href="http://www.engadget.com/2010/01/04/nexus-one-review/">reviewed</a> the purported device, but now that they&#8217;ve got one in hand up on a stage, we suppose we&#8217;ll have to set aside all of our doubts. So, the nitty gritty: 3.7-inch AMOLED display, 1GHz Snapdragon processor, compass, GPS, accelerometer, light and proximity sensor, 5 megapixel camera with LED flash, 3.5mm headphone jack, and a multicolored LED under the trackball. There are also two mics onboard, one on the bottom and one on the back, for the purpose of noise cancellation à la Motorola&#8217;s CrystalTalk, and the phone is naturally running the brand new <a href="http://www.engadget.com/2010/01/05/android-2-1-gets-real-on-the-wings-of-the-nexus-one/">Android 2.1</a>. The phone is actually HTC branded, unlike the pre-release versions we&#8217;ve seen, and can be custom engraved with two lines of text at the time of order, for that extra personal touch (there&#8217;s a picture of the phone&#8217;s back after the break). The phone is available today off contract with a T-Mobile compatible radio for $529 unlocked, shipping to the US, UK, Singapore and Hong Kong, or with a two year T-Mobile US contract for $179 (both with free overnight shipping in the US). Most surprisingly, the phone is also <a href="http://www.engadget.com/2010/01/05/verizon-getting-the-nexus-one-in-spring-2010/">headed to Verizon this Spring</a>, and Vodafone will score the device eventually as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/01/06/googles-nexus-one-is-official/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Nexus One support page goes live, quickly dies again</title>
		<link>http://owngadget.com/2010/01/05/google-nexus-one-support-page-goes-live-quickly-dies-again/</link>
		<comments>http://owngadget.com/2010/01/05/google-nexus-one-support-page-goes-live-quickly-dies-again/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 02:51:42 +0000</pubDate>
		<dc:creator>Arlene.L</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1264</guid>
		<description><![CDATA[Wondering how to activate your shiny new Nexus One? Curious how to get started with the thing, or how to use the 3D gallery? Oh, wait, you don&#8217;t have yours yet? Oops. Google seems to have posted its support page for the phone a little early, a little site that went live for just a]]></description>
			<content:encoded><![CDATA[<div><a href="https://www.google.com/phone/support"><img src="http://www.blogcdn.com/www.engadget.com/media/2010/01/nexus-20100104-600-2.jpg" border="0" alt="Google Nexus One support page goes live, quickly dies again" hspace="4" vspace="4" /></a></div>
<div>Wondering how to activate your shiny new <a href="http://www.engadget.com/tag/nexusone">Nexus One</a>? Curious how to get started with the thing, or how to use the 3D gallery? Oh, wait, you don&#8217;t have yours yet? Oops. Google seems to have posted its support page for the phone a little early, a little site that went live for just a few minutes &#8212; just long enough for us to click through a little, read that <a href="http://www.engadget.com/2009/12/29/allegedly-leaked-nexus-one-purchase-page-answers-raises-questio/">Terms of Service</a> that was leaked to us last week, and watch a few videos. The first one that came up is actually the walkthrough for Android 2.0, curiously, but the other videos showed 3D photo gallery and some other goodies. Now they show nothing, though, having been set private and the pages removed. Surely they&#8217;ll be up again soon, with the device getting <a href="http://www.engadget.com/2009/12/29/google-announces-android-press-conference-for-january-5th/">announced tomorrow</a>, and while we&#8217;re still not sure exactly when you&#8217;ll be able to get your own, you&#8217;re always welcome to <a href="http://www.engadget.com/2010/01/02/exclusive-google-nexus-one-hands-on-video-and-first-impressio/">enjoy our hands-on impressions</a>.</div>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2010/01/05/google-nexus-one-support-page-goes-live-quickly-dies-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nexus One trounces 3D benchmark, gets caught in high-res photoshoot</title>
		<link>http://owngadget.com/2009/12/31/nexus-one-trounces-3d-benchmark-gets-caught-in-high-res-photoshoot/</link>
		<comments>http://owngadget.com/2009/12/31/nexus-one-trounces-3d-benchmark-gets-caught-in-high-res-photoshoot/#comments</comments>
		<pubDate>Thu, 31 Dec 2009 08:20:59 +0000</pubDate>
		<dc:creator>Arlene.L</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1239</guid>
		<description><![CDATA[Just when you thought you&#8217;d seen it all with Nexus One, along comes an old friend with some higher resolution shots of the handset (hooray!) and a pretty impressive 3D benchmark test using Qualcomm&#8217;s Neocore. Video&#8217;s after the break &#8211;that Snapdragon chip outputs a mean framerate, no?]]></description>
			<content:encoded><![CDATA[<div><img src="http://www.blogcdn.com/www.engadget.com/media/2009/12/nexus-one-3d-rm-eng.jpg" border="1" alt="" hspace="4" vspace="4" /></div>
<p>Just when you thought you&#8217;d seen it all with Nexus One, along comes an <a href="http://www.engadget.com/2009/12/22/google-nexus-one-stands-with-iphone-and-hero-interface-gets-a-5/">old friend</a> with some higher resolution shots of the handset (hooray!) and a pretty impressive 3D benchmark test using Qualcomm&#8217;s Neocore. Video&#8217;s after the break &#8211;that Snapdragon chip outputs a mean framerate, no?</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2009/12/31/nexus-one-trounces-3d-benchmark-gets-caught-in-high-res-photoshoot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Nexus One lacks multitouch</title>
		<link>http://owngadget.com/2009/12/19/googles-nexus-one-lacks-multitouch/</link>
		<comments>http://owngadget.com/2009/12/19/googles-nexus-one-lacks-multitouch/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 15:04:44 +0000</pubDate>
		<dc:creator>Raymond.J</dc:creator>
				<category><![CDATA[Cellphones]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Nexus One]]></category>

		<guid isPermaLink="false">http://owngadget.com/?p=1146</guid>
		<description><![CDATA[Our buddy Tnkgrl just had a sit down with Google and HTC&#8217;s lovedroid, the Nexus One. She &#8220;wasn&#8217;t allowed&#8221; to take pictures or video but she came away with plenty of detail. The biggest point of clarification might not be what&#8217;s included in the handset, but what&#8217;s missing: multitouch. She confirms, &#8220;no multitouch support in]]></description>
			<content:encoded><![CDATA[<div><a href="http://tnkgrl.wordpress.com/2009/12/18/exclusive-hands-on-with-the-google-nexus-one/"><img src="http://www.blogcdn.com/www.engadget.com/media/2009/12/12-15-09googlephoneen.jpg" border="1" alt="" hspace="4" vspace="4" /></a></div>
<p>Our buddy Tnkgrl just had a sit down with Google and HTC&#8217;s lovedroid, the Nexus One. She &#8220;wasn&#8217;t allowed&#8221; to take pictures or video but she came away with plenty of detail. The biggest point of clarification might not be what&#8217;s included in the handset, but what&#8217;s <em>missing</em>: multitouch. She confirms, &#8220;no multitouch support in the browser or in Google Maps,&#8221; just like Verizon&#8217;s Droid (but available on its European <a href="http://www.engadget.com/tag/milestone">Milestone</a> brother). The unit she tested included a 4GB microSD card, 1400mAh battery, worked on T-Mobile&#8217;s 3G only (AT&amp;T is limited to EDGE data), and was &#8220;super snappy! Faster than the Droid.&#8221; She also noted &#8220;gold contacts&#8221; 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>
<p> P.S. We should probably clarify that while the Google Apps tested don&#8217;t respond to multitouch, the OS and hardware are presumably multitouch capable. See our previous <a href="http://www.engadget.com/2009/11/04/some-more-perspective-on-the-droid-and-multitouch/">exhaustive analysis</a> of this topic if you&#8217;re wondering why.</p>
]]></content:encoded>
			<wfw:commentRss>http://owngadget.com/2009/12/19/googles-nexus-one-lacks-multitouch/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

