<?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: A quick Thought About iPhone Issues</title> <atom:link href="http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/feed/" rel="self" type="application/rss+xml" /><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/</link> <description>Everyone can understand technology; sometimes it just takes a little translating.</description> <lastBuildDate>Tue, 14 Feb 2012 21:16:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: oops46</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-39030</link> <dc:creator>oops46</dc:creator> <pubDate>Sat, 16 Aug 2008 05:28:33 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-39030</guid> <description>I know it’s not their standard M.O., but it sure couldn’t hurt…
No it surely wouldn&#039;t. The battery on the 3G is utterly terrible! I have 3G turned off, browsing for WiFi networks turned off and still, the battery life is abismal. This is the same way I ran iPhone1 and have never experienced these problems before, even on that model.
Perhaps Apple doesn&#039;t communicate very well but it is an insult to one&#039;s intelligence when AT&amp;T says everything is fine.</description> <content:encoded><![CDATA[<p>I know it’s not their standard M.O., but it sure couldn’t hurt…</p><p>No it surely wouldn&#8217;t. The battery on the 3G is utterly terrible! I have 3G turned off, browsing for WiFi networks turned off and still, the battery life is abismal. This is the same way I ran iPhone1 and have never experienced these problems before, even on that model.<br
/> Perhaps Apple doesn&#8217;t communicate very well but it is an insult to one&#8217;s intelligence when AT&amp;T says everything is fine.</p> ]]></content:encoded> </item> <item><title>By: Christopher Spera</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38997</link> <dc:creator>Christopher Spera</dc:creator> <pubDate>Thu, 14 Aug 2008 19:33:13 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38997</guid> <description>This wasn&#039;t so much a rant as it was a plea for communication. There&#039;s been so much press about what is going on with the iPhone 3G, and not all of it has been positive.
I think the best way to combat bad press is with good, solid communication right from the source. It can&#039;t make Apple look bad. They&#039;ve already taken (and continue to take) the hit for MobileMe problems.  Why not just fess up and say, &quot;we&#039;re working on the reception problems?&quot; It might go a long way to making them look good.
I know it&#039;s not their standard M.O., but it sure couldn&#039;t hurt...</description> <content:encoded><![CDATA[<p>This wasn&#8217;t so much a rant as it was a plea for communication. There&#8217;s been so much press about what is going on with the iPhone 3G, and not all of it has been positive.</p><p>I think the best way to combat bad press is with good, solid communication right from the source. It can&#8217;t make Apple look bad. They&#8217;ve already taken (and continue to take) the hit for MobileMe problems.  Why not just fess up and say, &#8220;we&#8217;re working on the reception problems?&#8221; It might go a long way to making them look good.</p><p>I know it&#8217;s not their standard M.O., but it sure couldn&#8217;t hurt&#8230;</p> ]]></content:encoded> </item> <item><title>By: Chris Spera</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-109297</link> <dc:creator>Chris Spera</dc:creator> <pubDate>Thu, 14 Aug 2008 18:52:31 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-109297</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;A Quick Thought About iPhone Issues - Apple needs to step up to the plate... http://ping.fm/4oZmp&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span
class="topsy_trackback_comment"><span
class="topsy_twitter_username"><span
class="topsy_trackback_content">A Quick Thought About iPhone Issues &#8211; Apple needs to step up to the plate&#8230; <a
href="http://ping.fm/4oZmp" rel="nofollow">http://ping.fm/4oZmp</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Christopher Gavula</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38993</link> <dc:creator>Christopher Gavula</dc:creator> <pubDate>Thu, 14 Aug 2008 17:04:12 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38993</guid> <description>I don&#039;t agree with the idea that they weren&#039;t forced to relase the iPhone 2.0/3G.   Not entirely, anyway.  I think there WAS a LOT of pressure to get the iPhone 3G out along with Enxhange support.  It started the day the original iPhone was released.  All anyone seemed to be able to talk about was the lack of 3G and the lack of Exchange support.
I dont think Apple HAS to come out and say anything, necessarily.  It would be nice, yes, but that&#039;s not how they have ever operated.  The difference here, and the reason they don&#039;t have to say anything, is that you KNOW, based on their past history, that they are pretty likely to fix it.  With WM devices you were never sure and odds were about even that you&#039;d never see a fix to a given problem - you just had to wait for the next device and buy it when it came out.  With Apple we had 4 updates in 9 months to the original iPhone, and now with the 3G and the 2.x OS we&#039;ve already seen one fix within the first month.  Because you are pretty sure that they will fix it there&#039;s LESS of a need for them to talk about it.
But it sure would be nice if they did.</description> <content:encoded><![CDATA[<p>I don&#8217;t agree with the idea that they weren&#8217;t forced to relase the iPhone 2.0/3G.   Not entirely, anyway.  I think there WAS a LOT of pressure to get the iPhone 3G out along with Enxhange support.  It started the day the original iPhone was released.  All anyone seemed to be able to talk about was the lack of 3G and the lack of Exchange support.</p><p>I dont think Apple HAS to come out and say anything, necessarily.  It would be nice, yes, but that&#8217;s not how they have ever operated.  The difference here, and the reason they don&#8217;t have to say anything, is that you KNOW, based on their past history, that they are pretty likely to fix it.  With WM devices you were never sure and odds were about even that you&#8217;d never see a fix to a given problem &#8211; you just had to wait for the next device and buy it when it came out.  With Apple we had 4 updates in 9 months to the original iPhone, and now with the 3G and the 2.x OS we&#8217;ve already seen one fix within the first month.  Because you are pretty sure that they will fix it there&#8217;s LESS of a need for them to talk about it.</p><p>But it sure would be nice if they did.</p> ]]></content:encoded> </item> <item><title>By: Brandon (aka netsyd)</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38990</link> <dc:creator>Brandon (aka netsyd)</dc:creator> <pubDate>Thu, 14 Aug 2008 15:26:48 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38990</guid> <description>@reidme - agreed. They likely did feel some false sense of infallibility - but at the same time they set the deadlines themselves. They weren&#039;t forced to release mobileme when they did, and they weren&#039;t forced into iPhone 2.0 - they did that to themselves.
Now they need to work on being open and honest... I don&#039;t think anyone is asking for them to come out and say yes, we know there&#039;s a problem and here&#039;s the fix, but I do think they need to at least acknowledge the issue and tell us they&#039;re working on it.
Its like the Macbook WiFi dropping issue. That went on forever without a single word of acknowledgement from Apple. You knew they were working on it just because there was so many patches to the chipset and the OS, but they never once said anything about it.</description> <content:encoded><![CDATA[<p>@reidme &#8211; agreed. They likely did feel some false sense of infallibility &#8211; but at the same time they set the deadlines themselves. They weren&#8217;t forced to release mobileme when they did, and they weren&#8217;t forced into iPhone 2.0 &#8211; they did that to themselves.</p><p>Now they need to work on being open and honest&#8230; I don&#8217;t think anyone is asking for them to come out and say yes, we know there&#8217;s a problem and here&#8217;s the fix, but I do think they need to at least acknowledge the issue and tell us they&#8217;re working on it.</p><p>Its like the Macbook WiFi dropping issue. That went on forever without a single word of acknowledgement from Apple. You knew they were working on it just because there was so many patches to the chipset and the OS, but they never once said anything about it.</p> ]]></content:encoded> </item> <item><title>By: reidme</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38989</link> <dc:creator>reidme</dc:creator> <pubDate>Thu, 14 Aug 2008 15:01:32 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38989</guid> <description>Is there an echo in here?</description> <content:encoded><![CDATA[<p>Is there an echo in here?</p> ]]></content:encoded> </item> <item><title>By: reidme</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38988</link> <dc:creator>reidme</dc:creator> <pubDate>Thu, 14 Aug 2008 15:00:44 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38988</guid> <description>I think part of the reason for Apple&#039;s past success has been been because they didn&#039;t give in to pressure from customers, retailers, etc and only would release products when they were &quot;ready for prime time.&quot;  In the case of the iPhone 3G and MobileMe I think they dropped the ball because they did feel rushed to market.  Their string of recent successes may have given them a false sense of infallibility.</description> <content:encoded><![CDATA[<p>I think part of the reason for Apple&#8217;s past success has been been because they didn&#8217;t give in to pressure from customers, retailers, etc and only would release products when they were &#8220;ready for prime time.&#8221;  In the case of the iPhone 3G and MobileMe I think they dropped the ball because they did feel rushed to market.  Their string of recent successes may have given them a false sense of infallibility.</p> ]]></content:encoded> </item> <item><title>By: Michael Anderson</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38979</link> <dc:creator>Michael Anderson</dc:creator> <pubDate>Thu, 14 Aug 2008 13:48:58 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38979</guid> <description>This is sadly the way Apple has functioned *forever* ... they clamp on rumor sites, don&#039;t readily discuss issues, and are just generally very tight lipped about everything.
I have an iPod Touch 32GB, and when I updated to 2.0 firmware I watched my battery life go down drastically.  I now micromanage my WiFi setup (one of my office areas has no WiFi and it sucks down the battery!) in order to get reasonable battery life.  With WiFi I get only a few hours, but with WIFi off I still get better than 25 hours!</description> <content:encoded><![CDATA[<p>This is sadly the way Apple has functioned *forever* &#8230; they clamp on rumor sites, don&#8217;t readily discuss issues, and are just generally very tight lipped about everything.</p><p>I have an iPod Touch 32GB, and when I updated to 2.0 firmware I watched my battery life go down drastically.  I now micromanage my WiFi setup (one of my office areas has no WiFi and it sucks down the battery!) in order to get reasonable battery life.  With WiFi I get only a few hours, but with WIFi off I still get better than 25 hours!</p> ]]></content:encoded> </item> <item><title>By: Brandon (aka netsyd)</title><link>http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38977</link> <dc:creator>Brandon (aka netsyd)</dc:creator> <pubDate>Thu, 14 Aug 2008 13:22:18 +0000</pubDate> <guid
isPermaLink="false">http://www.geardiary.com/2008/08/14/a-quick-thought-about-iphone-issues/#comment-38977</guid> <description>What would I do? The same thing you&#039;re doing - making sure the issue stays in the front of people&#039;s minds. I&#039;ve made posts about it at JAMM and JAiB as well as using Twitter to make my voice heard. I personally could care less if its Apple, AT&amp;T or the chipset ... something is broken in a bad way (I use EDGE on my 3G by choice) and there&#039;s no way that should have to continue. This isn&#039;t as bad as the MobileFailMe debacle but its still not up to Apple quality standards.</description> <content:encoded><![CDATA[<p>What would I do? The same thing you&#8217;re doing &#8211; making sure the issue stays in the front of people&#8217;s minds. I&#8217;ve made posts about it at JAMM and JAiB as well as using Twitter to make my voice heard. I personally could care less if its Apple, AT&amp;T or the chipset &#8230; something is broken in a bad way (I use EDGE on my 3G by choice) and there&#8217;s no way that should have to continue. This isn&#8217;t as bad as the MobileFailMe debacle but its still not up to Apple quality standards.</p> ]]></content:encoded> </item> </channel> </rss>
