<?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: HTC Supersonic, First Wimax-enabled Smartphone</title>
	<atom:link href="http://www.goingwimax.com/htc-supersonic-first-wimax-enabled-smartphone-7751/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goingwimax.com/htc-supersonic-first-wimax-enabled-smartphone-7751/</link>
	<description>WiMAX news, wimax opinions, 4G conversations and more</description>
	<lastBuildDate>Tue, 07 Feb 2012 11:17:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Sprint Will Showcase Supersonic at CTIA Wireless 2010 &#124; Going Wimax</title>
		<link>http://www.goingwimax.com/htc-supersonic-first-wimax-enabled-smartphone-7751/comment-page-1/#comment-1775</link>
		<dc:creator>Sprint Will Showcase Supersonic at CTIA Wireless 2010 &#124; Going Wimax</dc:creator>
		<pubDate>Wed, 17 Mar 2010 20:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.goingwimax.com/?p=7751#comment-1775</guid>
		<description>[...] Wall Street Journal Report announced that Sprint will showcase the first WiMAX phone, the Supersonic from HTC. It be seen for the first time at CTIA Wireless 2010 next week in Las Vegas. It&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] Wall Street Journal Report announced that Sprint will showcase the first WiMAX phone, the Supersonic from HTC. It be seen for the first time at CTIA Wireless 2010 next week in Las Vegas. It&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason954</title>
		<link>http://www.goingwimax.com/htc-supersonic-first-wimax-enabled-smartphone-7751/comment-page-1/#comment-1639</link>
		<dc:creator>jason954</dc:creator>
		<pubDate>Fri, 05 Feb 2010 20:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.goingwimax.com/?p=7751#comment-1639</guid>
		<description>Are they crazy? No hardkey for AT LEAST Android &#039;menu&#039;? Does HTC even CONSIDER the consequences of eliminating hardkeys whose presence was just taken for granted by Android&#039;s designers as a fundamental &#039;given&#039;? Or do they live in a parallel universe where nobody carries phones in pockets (where having a phone&#039;s touchscreen &#039;go live&#039; is a very, VERY bad thing)? Please, for the love of ${deity}, HTC, if you HAVE to make &#039;menu&#039; virtual, at LEAST have the decency to ensure that pressing the &#039;menu&#039; spot twice won&#039;t defeat the keyguard (like it does on the CDMA Hero). Please. We&#039;re begging you.</description>
		<content:encoded><![CDATA[<p>Are they crazy? No hardkey for AT LEAST Android &#39;menu&#39;? Does HTC even CONSIDER the consequences of eliminating hardkeys whose presence was just taken for granted by Android&#39;s designers as a fundamental &#39;given&#39;? Or do they live in a parallel universe where nobody carries phones in pockets (where having a phone&#39;s touchscreen &#39;go live&#39; is a very, VERY bad thing)? Please, for the love of ${deity}, HTC, if you HAVE to make &#39;menu&#39; virtual, at LEAST have the decency to ensure that pressing the &#39;menu&#39; spot twice won&#39;t defeat the keyguard (like it does on the CDMA Hero). Please. We&#39;re begging you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<br />
<b>Warning</b>:  Unknown: failed to open stream: Permission denied in <b>Unknown</b> on line <b>0</b><br />
<br />
<b>Warning</b>:  Unknown: failed to open stream: Permission denied in <b>Unknown</b> on line <b>0</b><br />
<br />
<b>Fatal error</b>:  Unknown: Failed opening required '0ff' (include_path='.:/usr/lib/php:/tmp:/usr/local/lib/php:/root/ZendGdata-1.11.1/library') in <b>Unknown</b> on line <b>0</b><br />
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
