Apple

[#1]

Seriously, im in downtown NYC, my iPhone is showing 5 bars of signal, but:
- i can't send/receive emails (says 'Can't connect to the mail server')
- none of sites in Safari open (would just take forever and then give you an error "Safari can't open the page. The error was: "Operation could not be completed.kCFErrorDomainCFNetwork error 302" ")

WHAT AM I PAYING MY $30 FOR?

• restarted / reseted / reflashed my iPhone a number of times
• called ATT iPhone support, which is now in Philippines, spent 30 minutes and understood that it's even worse then talking to Shaniquas in domestic CC
  
• anything else you may suggest??? other then joining that woman in lawsuit against Apple/ATT?
  

[#2]

I have almost the exact same issue (except I can send and receive emails).  Even with 5 bars of 3G, my browser will time out in almost every instance.  I took it to an AT&T store thinking it was an account issue but they suggested it go back to Apple for replacement.  I have an appointment with the genius bar on Wednesday and I'll see what he/she can do.

I suggest you do the same if you haven't already.  Get the phone checked out and exchanged if necessary.  If that doesn't work and you are still within your return date I'd take it back.  I don't think joining a lawsuit is necessary--simply return merchandise that is defective.

[#3]

3G in downtown Manhattan is unbelievably bad on weekdays. Reminds me of using an analog modem over a noisy line. Even Goggle's classic main page times out while loading. Edge, for what it is worth, seems to work better during the week (I've taken to simply disabling 3G altogether). On weekends 3G is usable, but forget about it on a weekday - completely useless. I'm disappointed but I can't say I'm all that surprised. And short of this becoming a massive political problem for them, I have no expectation that AT&T will take responsibility for the issue.

Here is the result of running a bandwidth test via CNET over 3G at 1pm this afternoon (30.4kbps) ...

http://reviews.cnet.com/7009-7254_7-0.html?CType=5733&ac=212&ISPID=404438&ISPNAME=&&kbps=30.4

[#4]

I'm also in lower Manhattan, and it's not quite as simple as just weekdays. It's a totally shifting terrain, perhaps due to concentrated usage during certain periods, or maintenance on the system, or something else.

Data just blows in Manhattan, and there's really nothing you can do except bear with it until things improve, which they likely will. By all means go to a "genius" and get the thing checked out, but I think the devices are probably pretty uniform.

Just FYI, for the first time in a month I left Manhattan last week and went all over Queens. This was the first time I tried the iPhone outside of Manhattan, and it flew! I covered a very wide area of Queens, and whenever I stopped to check, I had excellent signal and could get mail and visit sites quickly and without problems. When I got back to Manhattan, everything was as before.

So I'll hang on, on the assumption that what I saw in Queens is what they're going to try to achieve everywhere, however they have to do it.

DGI

[#5]

geniuses will not be able to help, I've read one guy's story where he had exchaned the iPhone and nothing changed. It's a software issue where Applehad released an update to help those unlucky 2% with defective chips , but made a mess with the rest. Just trying to figure how long it will take for em to understand this.

It was just fine during the first days. All started after 2.0.2...

[#6]

I was downtown last Sunday. Nothing. I restarted the iPhone. I had 2 bars of 3G. Still couldn't connect. Turned off 3g. Used Edge.

I live on LI. Mineola area. 3G worthless here too. One bar of service at home. Full bars on Edge. Internet will not even work on 3G. Times out.

So 3G is turned off all the time.

So as the others asked.

WHAT ARE WE PAYING THE EXTRA 10 DOLLARS A MONTH FOR ATT?

I don't see this as an Apple hardware issue. I see it totally as ATT network issue.

This is NY no less. Very disappointed in 3G.

[#7]

Then how do you explain the flood of identical complaints from countries around the world?????

---

mozart11 wrote:

I don't see this as an Apple hardware issue. I see it totally as ATT network issue.

---

[#8]

---

Jameson! wrote:
Then how do you explain the flood of identical complaints from countries around the world?????

---

Because when you look at profiles of the reports around the world you see that the failures share not only a common device, but other common characteristics as well, having to do with specific geographical and environmental conditions. That's something a lot of people are missing. IOW, it seems not to be something *necessarily* inherent in the device, but a combination of device performance and network performance. This is not conclusive - if anyone had the final word we'd know it. But you might find these articles worthwhile:

http://apple20.blogs.fortune.cnn.com/2008/08/25/mapping-the-iphone-3gs-dead-zones/

http://blog.wired.com/gadgets/2008/08/global-iphone-3.html

DGI

---

[#9]

Sorry Bud, but if I line up 10 different 3G phones and 9 work fine, while one has problems, I don't bother looking at common network characteristics around the entire globe, as a possible cause.   The problem still lies, in my view, with the single under-performing unit.   Nobody wants to believe that the "Great APPLE" may have blown this product release, but it sure looks like that's exactly what has happened here.

One device should not rule the network design.   The network should rule the device design.........  

I know that having over 3 million of them out in the hands of customers creates an enormous mess for APPLE and AT&T, but the problem just continues to grow.  At some point, APPLE is going to have to acknowledge the mess and set some realistic expectations on when and how the solution will be handled.   they sure aren't doing themselves any favors by handling it as they are today.........

---

mulciber wrote:

---

Jameson! wrote:
Then how do you explain the flood of identical complaints from countries around the world?????

---

Because when you look at profiles of the reports around the world you see that the failures share not only a common device, but other common characteristics as well, having to do with specific geographical and environmental conditions. That's something a lot of people are missing. IOW, it seems not to be something *necessarily* inherent in the device, but a combination of device performance and network performance. This is not conclusive - if anyone had the final word we'd know it. But you might find these articles worthwhile:

http://apple20.blogs.fortune.cnn.com/2008/08/25/mapping-the-iphone-3gs-dead-zones/

http://blog.wired.com/gadgets/2008/08/global-iphone-3.html

DGI

---

---

[#10]

Honestly, when you consider how many people are located in downtown New York (Manhattan), the sheer amount of cell phones in use daily, and all other variables (massive steel buildings, etc) it's not to hard to assume that the network is simple CLOGGED by the number of users.  It isn't a phone problem, it's an network overload problem.

And in a city with population density like New York's....I doubt there's an easy fix to that problem.