Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If every single person who downloaded 3.1 had problems, maybe they would take it down. I have not had a single problem and in fact, my iPhone battery has been lasting about three days now since I upgraded. Much better than all the other updates.

3 days? Haha, someone barely uses the iPhone. iPod only? hahaha
 
- 3.1 sucks for me and my 3g.
- 50M google hits for "iphone 3.1 bugs" in the last 24 hours
- Apple support is very snotty (almost a case study in how not to speak with a customer); won't acknowledge a problem, but will send box/label for a refurb phone.
- 3g software issues are not new; happened last year after launch, but was resolved with a subsequent firmware update.
-It'd be nice if the phone was trouble free for at least the life of the 2yr ATT contract.
-sigh; like it when works, pissed when it doesn't
 
I feel the same way man, i havent had a problem and its all because of the settings i use for my phone. Everyones settings are different which is why everyone has their own usage numbers and no one can even come close to it. Besides that hows the ipod touch? I heard something floating around here that the new ipod touch has 3.1.1? I'm thinking of switching back to a blackberry and getting an ipod nano because of the camera feature as well as getting rid of the thing that runs my life. In a marketing sense, its understandable why they didnt give the ipod touch the camera it would hurt at&t and apples iphone sales.

</rant>

If you really must know, I actually returned my iPod touch (both of them) because I didn't like the screen. Read the whole story here.

Here's a summary:

Bought go-phone
Bought 64GB iPod touch
Didn't like the screen
Bought another one
Returned the first one
Didn't like the second screen
Put the go-phone sim in my iPhone 3G
Reverted back to 2.2.1
Bought a 13" MacBook Pro
Didn't like the screen on it
Traded with my brother for his Unibody MacBook

Now I'm happy again.
 
So its clear that 3.1 is a major problem.. All you have to do is read the forums here or even on the Apple boards... Wouldn't it be better to just take it down?

But then they'd just be admitting to it, and this is Apple we are talking about. This is a company that outright lies; liars generally don't fess up to much.
 
- 3.1 sucks for me and my 3g.
- 50M google hits for "iphone 3.1 bugs" in the last 24 hours
- Apple support is very snotty (almost a case study in how not to speak with a customer); won't acknowledge a problem, but will send box/label for a refurb phone.
- 3g software issues are not new; happened last year after launch, but was resolved with a subsequent firmware update.
-It'd be nice if the phone was trouble free for at least the life of the 2yr ATT contract.
-sigh; like it when works, pissed when it doesn't

And just what do you think Apple support can do for you?
--> If it's something specific to your environment (i.e. it's not reproducible on other iPhones), what exactly are they supposed to do beyond having your restore the iPhone and then replacing the iPhone?
--> If it's a bug, the support engineer on the line with you is not going to be able to (and in fact probably does not have the knowledge nor access to) modify the source code, build you a hotfix on-the-spot, and e-mail it out. All they can do is pass along the data they gather to their development team and wait for the next release.

Software is NEVER perfect. There are always more environmental variables, more use cases, more complex scenarios. Just like any software vendor, Apple does alphas, betas, and then releases. When issue come up "in the wild" they work to isolate and identify them, and then fix them in the next release. It's a standard software development lifecycle.

Go back to your hamburger phone on a landline, why don't you?

ux_a06090800ux0069_ux_c.jpg
 
Yea, no sorry...3.1 fails for me. Strange shut down issues, and not to mention the incredibly inconvenient intermittent total loss of data/cellular connection on a daily basis that is only remedied by rebooting (accompanied by that strange shut down issue I mentioned), and apparently that issue is seeing a lot of attention here as well as on Apple's own forums. I personally know 3 other people with iPhone 3GS's that are experiencing the same issue....in addition to a good number of others on various forums.

hitcomputer.gif
help.gif
iono.gif
 
Apple's always been like that party guest who breaks a glass and pretends like nothing happened.
Instead of admitting it, they hope you don't notice and just sneak a new one in at the next party.
 
No issues on my 3GS. I use about half of my battery every day with two push email accounts and location services on, plus the various things I use it for throughout the day (iPod, Safari, Pandora).
 
And just what do you think Apple support can do for you?
--> If it's something specific to your environment (i.e. it's not reproducible on other iPhones), what exactly are they supposed to do beyond having your restore the iPhone and then replacing the iPhone?
--> If it's a bug, the support engineer on the line with you is not going to be able to (and in fact probably does not have the knowledge nor access to) modify the source code, build you a hotfix on-the-spot, and e-mail it out. All they can do is pass along the data they gather to their development team and wait for the next release.

Software is NEVER perfect. There are always more environmental variables, more use cases, more complex scenarios. Just like any software vendor, Apple does alphas, betas, and then releases. When issue come up "in the wild" they work to isolate and identify them, and then fix them in the next release. It's a standard software development lifecycle.

Go back to your hamburger phone on a landline, why don't you?

Apple fan boys are so clever. I forgot you need to talk in sweet, hushed tones, or else risk bruising their sensitive souls.
 
It'd be interesting to see what set up people have got to see if there's any correlation between 3G/3GS, what you're syncing with etc and whether you have any problems or not.

I have a 3G and a 2007 MBP running 10.6 but haven't taken the plunge and upgraded to 3.1 yet. I don't have any problems at the moment and I'd like to keep it that way!
 
Actually I was told by a rep today that 1/3 of all the customer service calls they have been receiving since 3.1 release has been 3.1 problems, and this was AppleCare in general, not specifically AppleCare for iPhone.

The issues seem to be isolated to 3G's not 3GS's.

3.1 is a free update that most regular users have updated to, aside from Jailbreakers, Unlockers, and a few geeks on the MacRumors forums that is. The fact that 1/3 of calls are about 3.1 speaks more about it being a good update than a bad update.
 
i had some problems and restored as new from itunes. doing it from the iphone is flaky and caused problems.

now 3.1 is great, battery life is awesome once you stop fetching email every 15 minutes.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.