<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The Future of Phones:  Unlocked</title>
	<atom:link href="http://blog.herlein.com/2010/01/the-future-of-phones-unlocked/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.herlein.com/2010/01/the-future-of-phones-unlocked/</link>
	<description>- the musings of Greg Herlein</description>
	<lastBuildDate>Fri, 11 Mar 2011 06:55:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Why the iPhone is doomed &#171; Chasing the Power Curve</title>
		<link>http://blog.herlein.com/2010/01/the-future-of-phones-unlocked/comment-page-1/#comment-61</link>
		<dc:creator>Why the iPhone is doomed &#171; Chasing the Power Curve</dc:creator>
		<pubDate>Tue, 19 Jan 2010 00:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.herlein.com/?p=171#comment-61</guid>
		<description>[...] The Future of Phones: Unlocked  [...]</description>
		<content:encoded><![CDATA[<p>[...] The Future of Phones: Unlocked  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://blog.herlein.com/2010/01/the-future-of-phones-unlocked/comment-page-1/#comment-60</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Fri, 15 Jan 2010 19:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.herlein.com/?p=171#comment-60</guid>
		<description>The process will not be a quick one, but they are heading in the right direction. The immediate problem is that the phone will NOT be compatible with the Verizon network. The Verizon version of the Nexus One will have a different radio:

http://www.google.com/support/android/bin/answer.py?hl=en&amp;answer=164772

Users will not be able to just switch back and forth with the current model, but will be able to travel better internationally.

I&#039;ll be interested to see if the Verizon version has a radio that supports t-mobile (or AT&amp;T); or if AT&amp;T, Verizon or Google roll out a compatible 3G network. For now, WiFi and Google Voice have more of an influence on portability (don&#039;t *need* any plan).

I don&#039;t expect the data or phone network to always be available; My current AT&amp;T phone network drops calls like crazy. What I hope though is that there is a good offline mode, especially for turn-by-turn directions.

It will all work out. They are in it for the long run.

For the record... I&#039;m buying one anyway.</description>
		<content:encoded><![CDATA[<p>The process will not be a quick one, but they are heading in the right direction. The immediate problem is that the phone will NOT be compatible with the Verizon network. The Verizon version of the Nexus One will have a different radio:</p>
<p><a href="http://www.google.com/support/android/bin/answer.py?hl=en&#038;answer=164772" rel="nofollow">http://www.google.com/support/android/bin/answer.py?hl=en&#038;answer=164772</a></p>
<p>Users will not be able to just switch back and forth with the current model, but will be able to travel better internationally.</p>
<p>I&#8217;ll be interested to see if the Verizon version has a radio that supports t-mobile (or AT&amp;T); or if AT&amp;T, Verizon or Google roll out a compatible 3G network. For now, WiFi and Google Voice have more of an influence on portability (don&#8217;t *need* any plan).</p>
<p>I don&#8217;t expect the data or phone network to always be available; My current AT&amp;T phone network drops calls like crazy. What I hope though is that there is a good offline mode, especially for turn-by-turn directions.</p>
<p>It will all work out. They are in it for the long run.</p>
<p>For the record&#8230; I&#8217;m buying one anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

