<?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: Straight from AT&amp;T: We&#8217;re working on reception problems, but it&#8217;s your fault</title>
	<atom:link href="http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/</link>
	<description>Gadgets, gear and computer hardware.</description>
	<lastBuildDate>Mon, 09 Nov 2009 23:53:09 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Petwonemeveme</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-940606</link>
		<dc:creator>Petwonemeveme</dc:creator>
		<pubDate>Tue, 21 Oct 2008 11:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-940606</guid>
		<description>Good day! &lt;a href=&quot;http://www.citeulike.org/profile/apekoff&quot; rel=&quot;nofollow&quot;&gt;purim 2008&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Good day! <a href="http://www.citeulike.org/profile/apekoff" rel="nofollow">purim 2008</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wack</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850484</link>
		<dc:creator>wack</dc:creator>
		<pubDate>Thu, 28 Aug 2008 20:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850484</guid>
		<description>Would that also explain super slow data speed?

I don&#039;t see why but maybe someone has an explanation?</description>
		<content:encoded><![CDATA[<p>Would that also explain super slow data speed?</p>
<p>I don&#8217;t see why but maybe someone has an explanation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rener</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850282</link>
		<dc:creator>rener</dc:creator>
		<pubDate>Thu, 28 Aug 2008 18:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850282</guid>
		<description>No worries, it&#039;s who DailyTech is linking to when they talk about the source of the info...

(In the sentence &quot;With such a hazy picture, a new inside source from AT&amp;T steps in to try to *clarify exactly what the fix did*.&quot;</description>
		<content:encoded><![CDATA[<p>No worries, it&#8217;s who DailyTech is linking to when they talk about the source of the info&#8230;</p>
<p>(In the sentence &#8220;With such a hazy picture, a new inside source from AT&amp;T steps in to try to *clarify exactly what the fix did*.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Biggs</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850254</link>
		<dc:creator>John Biggs</dc:creator>
		<pubDate>Thu, 28 Aug 2008 18:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850254</guid>
		<description>Sorry. didn&#039;t see that story.</description>
		<content:encoded><![CDATA[<p>Sorry. didn&#8217;t see that story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rener</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850237</link>
		<dc:creator>rener</dc:creator>
		<pubDate>Thu, 28 Aug 2008 18:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850237</guid>
		<description>Ron is correct. Roughly Drafted is the source of this info, and rather than linking to a site that links to them, why not just give them the credit directly?

http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/</description>
		<content:encoded><![CDATA[<p>Ron is correct. Roughly Drafted is the source of this info, and rather than linking to a site that links to them, why not just give them the credit directly?</p>
<p><a href="http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/" rel="nofollow">http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850126</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Thu, 28 Aug 2008 17:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850126</guid>
		<description>You all should read http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/#more-2230 and you will get a very good explaination on what the issue was (transmitter power) and the solution (receiver asking only for what it needs).</description>
		<content:encoded><![CDATA[<p>You all should read <a href="http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/#more-2230" rel="nofollow">http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/#more-2230</a> and you will get a very good explaination on what the issue was (transmitter power) and the solution (receiver asking only for what it needs).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Frommer</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850049</link>
		<dc:creator>Dan Frommer</dc:creator>
		<pubDate>Thu, 28 Aug 2008 16:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850049</guid>
		<description>&quot;The result is a net effect: if everyone upgraded, we’d all be OK. But since folks are slow to update, the problem persists. The only way to fix this once and for all would be to push an over the air update to the phones, something I’m not sure Apple can or will do.&quot;

They tried. AT&amp;T sent out a bulk text -- I got it, at least -- noting that an &quot;important&quot; software update was on iTunes, and that I should download it.</description>
		<content:encoded><![CDATA[<p>&#8220;The result is a net effect: if everyone upgraded, we’d all be OK. But since folks are slow to update, the problem persists. The only way to fix this once and for all would be to push an over the air update to the phones, something I’m not sure Apple can or will do.&#8221;</p>
<p>They tried. AT&amp;T sent out a bulk text &#8212; I got it, at least &#8212; noting that an &#8220;important&#8221; software update was on iTunes, and that I should download it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cody B</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-850003</link>
		<dc:creator>Cody B</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-850003</guid>
		<description>Wow I just reread my comment then the article again.  It makes even less sense to me now.  

&quot;Too many phones ask for too much power at once, the transmitter starts shutting down, resulting in dropped calls.&quot;

I know a guy that has the iPhone connection issue.  When it happens, other AT&amp;T phones stay connected, which would mean the cell is still running.  That would mean that the iPhones have dedicated transmitters?  Or do they really mean some sort of UMTS v-lan variation.  I somewhat doubt that, but I could be wrong.</description>
		<content:encoded><![CDATA[<p>Wow I just reread my comment then the article again.  It makes even less sense to me now.  </p>
<p>&#8220;Too many phones ask for too much power at once, the transmitter starts shutting down, resulting in dropped calls.&#8221;</p>
<p>I know a guy that has the iPhone connection issue.  When it happens, other AT&amp;T phones stay connected, which would mean the cell is still running.  That would mean that the iPhones have dedicated transmitters?  Or do they really mean some sort of UMTS v-lan variation.  I somewhat doubt that, but I could be wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cody B</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-849983</link>
		<dc:creator>Cody B</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-849983</guid>
		<description>What is this &quot;power&quot; they speak of?  CPU, energy, bandwidth, and or &#039;the force?&quot;

UMTS is a standard network technology.  The iPhone shouldn&#039;t be much different than any other device using the technology.  That why I&#039;m interested in this &quot;power&quot; they are referencing.  I&#039;m guessing, but taking too much CPU &quot;power&quot; per connection would make some sense.  Overloading the cell might cause it to reset.  But saying that the iPhone connection, using the international network standard, takes more power than any other device just sounds like a joke to me.  Any thoughts?</description>
		<content:encoded><![CDATA[<p>What is this &#8220;power&#8221; they speak of?  CPU, energy, bandwidth, and or &#8216;the force?&#8221;</p>
<p>UMTS is a standard network technology.  The iPhone shouldn&#8217;t be much different than any other device using the technology.  That why I&#8217;m interested in this &#8220;power&#8221; they are referencing.  I&#8217;m guessing, but taking too much CPU &#8220;power&#8221; per connection would make some sense.  Overloading the cell might cause it to reset.  But saying that the iPhone connection, using the international network standard, takes more power than any other device just sounds like a joke to me.  Any thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken @ T-mobile</title>
		<link>http://www.crunchgear.com/2008/08/28/straight-from-att-were-working-on-reception-problems-but-its-your-fault/comment-page-1/#comment-849963</link>
		<dc:creator>Ken @ T-mobile</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.crunchgear.com/?p=37656#comment-849963</guid>
		<description>LOL!!</description>
		<content:encoded><![CDATA[<p>LOL!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
