<?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: Apple has a PR nightmare brewing&#8230;</title>
	<atom:link href="http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/feed/" rel="self" type="application/rss+xml" />
	<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/</link>
	<description>Searching for world-changing technology</description>
	<lastBuildDate>Sat, 24 Mar 2012 05:14:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: tina</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-81791</link>
		<dc:creator>tina</dc:creator>
		<pubDate>Fri, 07 Dec 2007 18:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-81791</guid>
		<description>Cool post:) apple e aplle .</description>
		<content:encoded><![CDATA[<p>Cool post:) apple e aplle .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tina</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-211398</link>
		<dc:creator>tina</dc:creator>
		<pubDate>Fri, 07 Dec 2007 18:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-211398</guid>
		<description>Cool post:) apple e aplle .</description>
		<content:encoded><![CDATA[<p>Cool post:) apple e aplle .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grenzpfosten : Apple steuert in die iPhone Krise</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-81900</link>
		<dc:creator>Grenzpfosten : Apple steuert in die iPhone Krise</dc:creator>
		<pubDate>Thu, 08 Nov 2007 12:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-81900</guid>
		<description>[...] Robert Scoble hat die Twitterzonen und sonstigen Stellen lokalisiert, an denen sich User des iPhones &#252;ber die Schwierigkeiten mit dem angeblichen Killer-Phone berichten. Zeit f&#252;r Apple in diese Communities reinzugehen und die Probleme dort zu kommunizieren. Bin gespannt, ob die sowas machen.  Syndiziere Dich    Verfasst von Flo am Montag, Oktober 1, 2007, um 20:55, Veröffentlicht unter Online, PR. Alle Kommentare zu diesem Beitrag mit dem Kommentar RSS Feed verfolgen. Du kannst einen Kommentar verfassen oder einen Trackback von deinem Blog setzen. [...]</description>
		<content:encoded><![CDATA[<p>[...] Robert Scoble hat die Twitterzonen und sonstigen Stellen lokalisiert, an denen sich User des iPhones &#252;ber die Schwierigkeiten mit dem angeblichen Killer-Phone berichten. Zeit f&#252;r Apple in diese Communities reinzugehen und die Probleme dort zu kommunizieren. Bin gespannt, ob die sowas machen.  Syndiziere Dich    Verfasst von Flo am Montag, Oktober 1, 2007, um 20:55, Veröffentlicht unter Online, PR. Alle Kommentare zu diesem Beitrag mit dem Kommentar RSS Feed verfolgen. Du kannst einen Kommentar verfassen oder einen Trackback von deinem Blog setzen. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bbbent</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-81792</link>
		<dc:creator>Bbbent</dc:creator>
		<pubDate>Mon, 22 Oct 2007 17:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-81792</guid>
		<description>My update went fine.  For awhile.   I did the 1.1.1 update the day after it came out.  The only problems I had after that were a few freezes (resolved with a soft reset) and sometimes the party on the other end couldn&#039;t hear me talking on a phone call.

The phone is -not- unlocked, and as far as I know not modified. I only had two things that were possibly wierd. One is a single iToner ringtone.  The other is Beejive&#039;s Jivetalk.

As far as I know from my extensive research, iToner is not a hack in any way. At least not according to everything Ambrosia has written.  Being in the &#039;biz I know how these things go sometimes.

And Jivetalk is a straight AJAX web app.

So all was well. I was enjoying the 1.1.1 &#039;double-click to go to faves&#039; feature. Don&#039;t much care about the wifi itunes store access.

About two weeks after the update I started Safari and opened the Beejive Jivetalk URL to IM someone. And at that point the screen froze.

Ick.  Soft restore would reboot the phone and it was acting wierd.  Would boot to the UI, but sasn&#039;t responsive to any touches or the home button.  Wouldn&#039;t find the network.  Sometimes the time would be right, sometimes not. But the key thing here is that it wouldn&#039;t respond to any touches. That&#039;s not good.

Now, at this point I have to add that there is a tiny, tiny crack in teh lower left glass.  If you use your phone as an alarm clock keep it somehere you can&#039;t accidentally knock it down while you&#039;re sleeping. The crack is in the lower left corner of the glass, about 1/8&quot; in from teh corner, in the part of the glass directly to the left of the home button. In other words, NOT in the area of the touchscreen UI.

So, I get on the phone with support.  No dice on doing a restore. All restore attempts (on two machines, one mac, one PC) return &#039;error 1602&#039;.  Get a super-nice higher level support agent on the phone.  We do a few more restore attempts.  Nada. Finally we set up a a repair.

So I get a free loaner, which is appreciated, and off the phone goes for repair.

Well, back it comes. Unrepaired. Because of the glass crack (see my blog for the letter they sent). OK i understand that the repair center can&#039;t touch it.  I get that.

The problem is statement number 2 on their letter:
&quot;Due to unauthorized modifications... was inoperable&quot;.  And then they voided my warranty.

And there lies the problem.  Since then I have been able to force-restore and reinstall 1.1.1.  But nothing I do has been able to restore any touchscreen functionality.

So maybe the digitizer actually -is- broken.  But I still think (in my 13 years in software support) that it&#039;s a software problem.

So my 1.1.1 experience has been lame.  I&#039;ll be writing more about it on my blog.

And to counterpoint that, my wife&#039;s iPhone (which I updated 2 days after mine) has been flawless so far. So maybe itoner did have something to do with it. I just can&#039;t tell.  I have an appointment to talk to a genious tomorrow to get the straight scoop.  If Apple won&#039;t help me (and won&#039;t let me buy a $250 repair?) then I&#039;ll have no choice but to waste a lot more time and money and fix the glass myself and then turn to the hacking community for a software solution. That&#039;s not really what I want to do.. :(</description>
		<content:encoded><![CDATA[<p>My update went fine.  For awhile.   I did the 1.1.1 update the day after it came out.  The only problems I had after that were a few freezes (resolved with a soft reset) and sometimes the party on the other end couldn&#8217;t hear me talking on a phone call.</p>
<p>The phone is -not- unlocked, and as far as I know not modified. I only had two things that were possibly wierd. One is a single iToner ringtone.  The other is Beejive&#8217;s Jivetalk.</p>
<p>As far as I know from my extensive research, iToner is not a hack in any way. At least not according to everything Ambrosia has written.  Being in the &#8216;biz I know how these things go sometimes.</p>
<p>And Jivetalk is a straight AJAX web app.</p>
<p>So all was well. I was enjoying the 1.1.1 &#8216;double-click to go to faves&#8217; feature. Don&#8217;t much care about the wifi itunes store access.</p>
<p>About two weeks after the update I started Safari and opened the Beejive Jivetalk URL to IM someone. And at that point the screen froze.</p>
<p>Ick.  Soft restore would reboot the phone and it was acting wierd.  Would boot to the UI, but sasn&#8217;t responsive to any touches or the home button.  Wouldn&#8217;t find the network.  Sometimes the time would be right, sometimes not. But the key thing here is that it wouldn&#8217;t respond to any touches. That&#8217;s not good.</p>
<p>Now, at this point I have to add that there is a tiny, tiny crack in teh lower left glass.  If you use your phone as an alarm clock keep it somehere you can&#8217;t accidentally knock it down while you&#8217;re sleeping. The crack is in the lower left corner of the glass, about 1/8&#8243; in from teh corner, in the part of the glass directly to the left of the home button. In other words, NOT in the area of the touchscreen UI.</p>
<p>So, I get on the phone with support.  No dice on doing a restore. All restore attempts (on two machines, one mac, one PC) return &#8216;error 1602&#8242;.  Get a super-nice higher level support agent on the phone.  We do a few more restore attempts.  Nada. Finally we set up a a repair.</p>
<p>So I get a free loaner, which is appreciated, and off the phone goes for repair.</p>
<p>Well, back it comes. Unrepaired. Because of the glass crack (see my blog for the letter they sent). OK i understand that the repair center can&#8217;t touch it.  I get that.</p>
<p>The problem is statement number 2 on their letter:<br />
&#8220;Due to unauthorized modifications&#8230; was inoperable&#8221;.  And then they voided my warranty.</p>
<p>And there lies the problem.  Since then I have been able to force-restore and reinstall 1.1.1.  But nothing I do has been able to restore any touchscreen functionality.</p>
<p>So maybe the digitizer actually -is- broken.  But I still think (in my 13 years in software support) that it&#8217;s a software problem.</p>
<p>So my 1.1.1 experience has been lame.  I&#8217;ll be writing more about it on my blog.</p>
<p>And to counterpoint that, my wife&#8217;s iPhone (which I updated 2 days after mine) has been flawless so far. So maybe itoner did have something to do with it. I just can&#8217;t tell.  I have an appointment to talk to a genious tomorrow to get the straight scoop.  If Apple won&#8217;t help me (and won&#8217;t let me buy a $250 repair?) then I&#8217;ll have no choice but to waste a lot more time and money and fix the glass myself and then turn to the hacking community for a software solution. That&#8217;s not really what I want to do.. <img src='http://scobleizer.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bbbent</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-211399</link>
		<dc:creator>Bbbent</dc:creator>
		<pubDate>Mon, 22 Oct 2007 17:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-211399</guid>
		<description>My update went fine.  For awhile.   I did the 1.1.1 update the day after it came out.  The only problems I had after that were a few freezes (resolved with a soft reset) and sometimes the party on the other end couldn&#039;t hear me talking on a phone call.

The phone is -not- unlocked, and as far as I know not modified. I only had two things that were possibly wierd. One is a single iToner ringtone.  The other is Beejive&#039;s Jivetalk.

As far as I know from my extensive research, iToner is not a hack in any way. At least not according to everything Ambrosia has written.  Being in the &#039;biz I know how these things go sometimes.

And Jivetalk is a straight AJAX web app.

So all was well. I was enjoying the 1.1.1 &#039;double-click to go to faves&#039; feature. Don&#039;t much care about the wifi itunes store access.

About two weeks after the update I started Safari and opened the Beejive Jivetalk URL to IM someone. And at that point the screen froze.

Ick.  Soft restore would reboot the phone and it was acting wierd.  Would boot to the UI, but sasn&#039;t responsive to any touches or the home button.  Wouldn&#039;t find the network.  Sometimes the time would be right, sometimes not. But the key thing here is that it wouldn&#039;t respond to any touches. That&#039;s not good.

Now, at this point I have to add that there is a tiny, tiny crack in teh lower left glass.  If you use your phone as an alarm clock keep it somehere you can&#039;t accidentally knock it down while you&#039;re sleeping. The crack is in the lower left corner of the glass, about 1/8&quot; in from teh corner, in the part of the glass directly to the left of the home button. In other words, NOT in the area of the touchscreen UI.

So, I get on the phone with support.  No dice on doing a restore. All restore attempts (on two machines, one mac, one PC) return &#039;error 1602&#039;.  Get a super-nice higher level support agent on the phone.  We do a few more restore attempts.  Nada. Finally we set up a a repair.

So I get a free loaner, which is appreciated, and off the phone goes for repair.

Well, back it comes. Unrepaired. Because of the glass crack (see my blog for the letter they sent). OK i understand that the repair center can&#039;t touch it.  I get that.

The problem is statement number 2 on their letter:
&quot;Due to unauthorized modifications... was inoperable&quot;.  And then they voided my warranty.

And there lies the problem.  Since then I have been able to force-restore and reinstall 1.1.1.  But nothing I do has been able to restore any touchscreen functionality.

So maybe the digitizer actually -is- broken.  But I still think (in my 13 years in software support) that it&#039;s a software problem.

So my 1.1.1 experience has been lame.  I&#039;ll be writing more about it on my blog.

And to counterpoint that, my wife&#039;s iPhone (which I updated 2 days after mine) has been flawless so far. So maybe itoner did have something to do with it. I just can&#039;t tell.  I have an appointment to talk to a genious tomorrow to get the straight scoop.  If Apple won&#039;t help me (and won&#039;t let me buy a $250 repair?) then I&#039;ll have no choice but to waste a lot more time and money and fix the glass myself and then turn to the hacking community for a software solution. That&#039;s not really what I want to do.. :(</description>
		<content:encoded><![CDATA[<p>My update went fine.  For awhile.   I did the 1.1.1 update the day after it came out.  The only problems I had after that were a few freezes (resolved with a soft reset) and sometimes the party on the other end couldn&#8217;t hear me talking on a phone call.</p>
<p>The phone is -not- unlocked, and as far as I know not modified. I only had two things that were possibly wierd. One is a single iToner ringtone.  The other is Beejive&#8217;s Jivetalk.</p>
<p>As far as I know from my extensive research, iToner is not a hack in any way. At least not according to everything Ambrosia has written.  Being in the &#8216;biz I know how these things go sometimes.</p>
<p>And Jivetalk is a straight AJAX web app.</p>
<p>So all was well. I was enjoying the 1.1.1 &#8216;double-click to go to faves&#8217; feature. Don&#8217;t much care about the wifi itunes store access.</p>
<p>About two weeks after the update I started Safari and opened the Beejive Jivetalk URL to IM someone. And at that point the screen froze.</p>
<p>Ick.  Soft restore would reboot the phone and it was acting wierd.  Would boot to the UI, but sasn&#8217;t responsive to any touches or the home button.  Wouldn&#8217;t find the network.  Sometimes the time would be right, sometimes not. But the key thing here is that it wouldn&#8217;t respond to any touches. That&#8217;s not good.</p>
<p>Now, at this point I have to add that there is a tiny, tiny crack in teh lower left glass.  If you use your phone as an alarm clock keep it somehere you can&#8217;t accidentally knock it down while you&#8217;re sleeping. The crack is in the lower left corner of the glass, about 1/8&#8243; in from teh corner, in the part of the glass directly to the left of the home button. In other words, NOT in the area of the touchscreen UI.</p>
<p>So, I get on the phone with support.  No dice on doing a restore. All restore attempts (on two machines, one mac, one PC) return &#8216;error 1602&#8242;.  Get a super-nice higher level support agent on the phone.  We do a few more restore attempts.  Nada. Finally we set up a a repair.</p>
<p>So I get a free loaner, which is appreciated, and off the phone goes for repair.</p>
<p>Well, back it comes. Unrepaired. Because of the glass crack (see my blog for the letter they sent). OK i understand that the repair center can&#8217;t touch it.  I get that.</p>
<p>The problem is statement number 2 on their letter:<br />
&#8220;Due to unauthorized modifications&#8230; was inoperable&#8221;.  And then they voided my warranty.</p>
<p>And there lies the problem.  Since then I have been able to force-restore and reinstall 1.1.1.  But nothing I do has been able to restore any touchscreen functionality.</p>
<p>So maybe the digitizer actually -is- broken.  But I still think (in my 13 years in software support) that it&#8217;s a software problem.</p>
<p>So my 1.1.1 experience has been lame.  I&#8217;ll be writing more about it on my blog.</p>
<p>And to counterpoint that, my wife&#8217;s iPhone (which I updated 2 days after mine) has been flawless so far. So maybe itoner did have something to do with it. I just can&#8217;t tell.  I have an appointment to talk to a genious tomorrow to get the straight scoop.  If Apple won&#8217;t help me (and won&#8217;t let me buy a $250 repair?) then I&#8217;ll have no choice but to waste a lot more time and money and fix the glass myself and then turn to the hacking community for a software solution. That&#8217;s not really what I want to do.. <img src='http://scobleizer.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: podheadz -  the iphone unlocked</title>
		<link>http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/comment-page-6/#comment-81793</link>
		<dc:creator>podheadz -  the iphone unlocked</dc:creator>
		<pubDate>Thu, 04 Oct 2007 21:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://scobleizer.com/2007/09/27/apple-has-a-pr-nightmare-brewing/#comment-81793</guid>
		<description>&lt;strong&gt;iPhone unlocked&lt;/strong&gt;

Well, now that I can actually unlock it, Ill buy one</description>
		<content:encoded><![CDATA[<p><strong>iPhone unlocked</strong></p>
<p>Well, now that I can actually unlock it, Ill buy one</p>
]]></content:encoded>
	</item>
</channel>
</rss>

