Commentary

Woman Sues Apple Over 3G iPhone Reception Issues

I am tempted to make all sorts of witty, snarky comments about this, but I'll try to stick to the facts. An Alabama woman has sued Apple, stating that the 3G iPhone -- which she can't use in her home because of the 3G reception issues -- doesn't live up to Apple's claims of "twice as fast." The lawsuit could go class action.

I am tempted to make all sorts of witty, snarky comments about this, but I'll try to stick to the facts. An Alabama woman has sued Apple, stating that the 3G iPhone -- which she can't use in her home because of the 3G reception issues -- doesn't live up to Apple's claims of "twice as fast." The lawsuit could go class action.Apple will ever be a target for lawsuits. In fact, it has been quiet on the Apple lawsuit front lately, so the news of this new lawsuit feels like it is overdue.

The details are these: Jessica Smith, a woman living in Birmingham, Ala., believed in Apple's "twice as fast, half the price" marketing claims. According to her, she has solid AT&T coverage in her home, yet she can only connect to AT&T's 3G network about 25% of the time. She also said that she has had a large number of dropped calls. The lawsuit specifically says that Apple isn't living up to its warranty that the phone will "perform adequately" on AT&T's 3G network.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

So what does Jessica Smith want? She wants Apple to "repair or replace all 'defective iPhone 3G' units, plus damages, interest on 'monetary relief,' and attorney's fees." She estimates that tens of thousands of users are affected by the 3G iPhone's reception problems, which could push the lawsuit to class action status.

Um. Yeah.

Apple CEO Steve Jobs has copped to the 3G iPhone's reception problems. Firmware updates 2.0.1 and 2.0.2 did not fix the issues, and el-Steve-o has promised that another update, timed for September, will resolve everything. Sorry, Steve, but I'll believe it when I see it.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links