Apple's silence

[PCboarder]

I dont think anyone said it was the end of the world but its just annoying to be on a important call and have your phone crap itself and go to sleep for no reason. Its annoying and it shouldnt happen.

But the point is that Apple is not acknowledging the problem like I said. Your right, they probably wont ever do that because they are apple but it would be a nice gesture to their loyal following.

And if they sold an iphone helmet that would deflect all these annoying problems with the OS, id wear it.

 

[chgojcs]

I dont think anyone said it was the end of the world but its just annoying to be on a important call and have your phone crap itself and go to sleep for no reason. Its annoying and it shouldnt happen.

But the point is that Apple is not acknowledging the problem like I said. Your right, they probably wont ever do that because they are apple but it would be a nice gesture to their loyal following.

And if they sold an iphone helmet that would deflect all these annoying problems with the OS, id wear it.

Jesus....
All I am saying is whining about it (which is what you're doing, because it makes you feel less helpless in lieu of the frustrating circumstances) is not going to fix anything.

And if you know your iPhone is buggy, and you miss an important call because of said bugginess, that's on you, not Apple.
Since the whole thing started last Thursday, I have been using my POS phone. I can't afford to miss those calls and I am not going to take the chance that Apple will get a fix out sonner rather than later.
S*** happens. Always have a plan B.
Anyone who uses technology for business and doesn't have some chain of redundancy and back up religiously, I feel no sympathy for.

Honestly, how many different threads do we need about how frustrating it is?

 

[NekoFever]

This bug has apparently been present in every beta version of 3.1, so it's not like it just slipped in unnoticed. 3.1 has clearly been rushed to get it out for the 9/9 event, and for that reason I think we have every right to be upset.

I can handle minor niggles and even the occasional crash because these things happen with computers, but something like this on a product like the iPhone is unacceptable. We're not talking minor slowdown or a small incompatibility; this is people's telephones becoming completely unusable at random intervals because of inadequate testing.

 

[chgojcs]

This bug has apparently been present in every beta version of 3.1, so it's not like it just slipped in unnoticed. 3.1 has clearly been rushed to get it out for the 9/9 event, and for that reason I think we have every right to be upset.

I can handle minor niggles and even the occasional crash because these things happen with computers, but something like this on a product like the iPhone is unacceptable. We're not talking minor slowdown or a small incompatibility; this is people's telephones becoming completely unusable at random intervals because of inadequate testing.

Yeah, we all have every reason to be upset.

But, good lord, how many different threads do people need to start saying how upsetting and frustrating it is?

We get it. We are all in the same boat.

Now, honestly, what else is there to do?
If you have an idea that will make Apple fix it in the next hour, please share.
Otherwise, we just wait.

 

[daflake]

Sadly my 3G was doing this on Beta 1 and got better during Beta 2 only to get worse in Beta 3. I figured that they would release another fix as I could sit there and watch memory max out. I was using Istat to reset the memory but that was pulled at Apple's request. Then they released 3.1 and it is still happening. I think that this one slipped on by and that 3.1 should have not been released until it was resolved.

 

[Shoesy]

Sadly my 3G was doing this on Beta 1 and got better during Beta 2 only to get worse in Beta 3. I figured that they would release another fix as I could sit there and watch memory max out. I was using Istat to reset the memory but that was pulled at Apple's request. Then they released 3.1 and it is still happening. I think that this one slipped on by and that 3.1 should have not been released until it was resolved.

Same same. My thoughts / experience exactly. To be honest I assumed that as soon as the public release came it would be all better. This bug has been hanging around longer than you might think.

 

[PCboarder]

Jesus....
All I am saying is whining about it (which is what you're doing, because it makes you feel less helpless in lieu of the frustrating circumstances) is not going to fix anything.

And if you know your iPhone is buggy, and you miss an important call because of said bugginess, that's on you, not Apple.
Since the whole thing started last Thursday, I have been using my POS phone. I can't afford to miss those calls and I am not going to take the chance that Apple will get a fix out sonner rather than later.
S*** happens. Always have a plan B.
Anyone who uses technology for business and doesn't have some chain of redundancy and back up religiously, I feel no sympathy for.

Honestly, how many different threads do we need about how frustrating it is?

Honestly it sounds like you are getting much more worked up over this thread than me over my phone haha

I use a landline for most important calls, but I would like to think that the iPhone can handle a call. (But I guess that makes me wrong and thats on me ) Unlike you this is my only GSM phone since I switched from Verizon.

As for all the threads, its a forum. People use them to talk about products, ok i lied people just use them to complain haha which is fine.

Dont read the threads if it pisses you off so much. I stopped reading all the MMS threads because its annoying to me. You should try it

 

[chgojcs]

Honestly it sounds like you are getting much more worked up over this thread than me over my phone haha

I use a landline for most important calls, but I would like to think that the iPhone can handle a call. (But I guess that makes me wrong and thats on me ) Unlike you this is my only GSM phone since I switched from Verizon.

As for all the threads, its a forum. People use them to talk about products, ok i lied people just use them to complain haha which is fine.

Dont read the threads if it pisses you off so much. I stopped reading all the MMS threads because its annoying to me. You should try it

Ha ha.
I'm not getting worked up at all. I just don't see the need to keep regurgitating the same point over and over again ad nauseum.

Maybe, instead of coming here, some of these whiny babies should send feedback to Apple. Apple doesn't hang out on Macrumors.com.
And yes, I'm sure people some have sent feedback, but I doubt it's the majority.

Crying about a problem over and over again doesn't actually get it fixed you know.
If a baby has a dirty diaper, crying doesn't make it go away, actually having some change the diaper does.

So please, stop crying. Apple will eventually change your diaper.

 

[PCboarder]

Well I know I have posted on the Apple Support board as well.

Dang it I thought If we got enough people to "whine" about the problem, Steve would come to my house and fix my phone...Good thing I have you around to correct me.

 

[newcronos]

Don't get me wrong, I agree with what you're saying. It would be irresponsible and stupid for geniuses to hand out their own advice.. but they could at least acknowledge the fact there might be a problem and just tell customers that they're sorry but they'll have to wait and see what Apple comes up with.

The problem is that it's not an Apple-approved answer for this situation.

 

[chgojcs]

Well I know I have posted on the Apple Support board as well.

Dang it I thought If we got enough people to "whine" about the problem, Steve would come to my house and fix my phone...Good thing I have you around to correct me.

Sure as heck seems that way.

And posting on the Apple support board is equally as pointless.

I'll refer you to the link to send feedback to Apple.
http://www.apple.com/feedback/iphone.html
You can do it.
I believe in you.

 

[creon]

3.1 has only brought 'snappiness' to my phone.

 

[PCboarder]

Sure as heck seems that way.

And posting on the Apple support board is equally as pointless.

I'll refer you to the link to send feedback to Apple.
http://www.apple.com/feedback/iphone.html
You can do it.
I believe in you.

Well by me saying I posted on the Apple support board also meant that I took the extra 13 seconds to copy my post into the feedback page. O but I thought I didnt have to outline every single detail because your obviously so much smarter than us normal iPhone users. haha man your a joke

 

[chgojcs]

Well by me saying I posted on the Apple support board also meant that I took the extra 13 seconds to copy my post into the feedback page. O but I thought I didnt have to outline every single detail because your obviously so much smarter than us normal iPhone users. haha man your a joke

your=possesive
you're=you are

And I don't claim to be smarter, just not going to piss and moan repeatedly about something when I know full well it won't do a lick of good.

 

[matttye]

Jesus....
All I am saying is whining about it (which is what you're doing, because it makes you feel less helpless in lieu of the frustrating circumstances) is not going to fix anything.

And if you know your iPhone is buggy, and you miss an important call because of said bugginess, that's on you, not Apple.
Since the whole thing started last Thursday, I have been using my POS phone. I can't afford to miss those calls and I am not going to take the chance that Apple will get a fix out sonner rather than later.
S*** happens. Always have a plan B.
Anyone who uses technology for business and doesn't have some chain of redundancy and back up religiously, I feel no sympathy for.

Honestly, how many different threads do we need about how frustrating it is?

No, it is not the fault of the user for missing calls because they don't have a backup phone. When you purchase an expensive, top of the line phone the one thing most people would expect it to do is make/receive telephone calls.

This crash is a problem that Apple needs to take responsibility for and sort out. I sent feedback to Apple long before I made this thread.

I don't know if you noticed but this is an Apple discussion website, and this is a topic discussing Apple!

The problem is that it's not an Apple-approved answer for this situation.

Common sense should prevail in some situations. If someone has already restored and had a replacement phone, and the problem isn't solved, then what happens next? They keep offering replacements? That is just going to annoy the customer.

 

[OllyW]

Lots of people are reporting their iPhones go into a permanent sleep state and need to be hard-reset. Whilst in this state if they call the iPhone it still rings according to the phone they are using, but the iPhone doesn't make any indication that there's a call.

Seems to affect 3G users mostly but there have been several 3GS reports too.

I had this happen to my 3G yesterday, I didn't know it was a widespread problem.

 

[VulchR]

Bad Apple

I love Apple products and always have.

However, this seems to be a genuine problem and the idea that iPhone owners should sit back passively and accept this failure as routine is nonsense. First, this is a problem with solely with Apple hardware and software. As the saying goes: "Live by a closed system, die by a closed system." Second, Apple has now taken steps to prevent rolling back updates, locking users into the faulty update. Third, since when is it excusable to release software without proper debugging, particularly when the users pay a premium? Fourth, many iPhone owners are on expensive contracts and therefore will lose service for which they have already paid. Moreover, some will have paid for replacement iPhones even though hardware was not to blame. Fifth, no doubt one of the main purposes of the update is to smack down jailbreaking - if any part of that effort contributed to these apparent problems, then Apple has some explaining to do to the vast majority of users who do not break their EULA.

And of course, there is the topic of this thread: Apple has not apologized, let alone acknowledged, the problem.

 

[ZipZap]

Ha ha.
I'm not getting worked up at all. I just don't see the need to keep regurgitating the same point over and over again ad nauseum.

Maybe, instead of coming here, some of these whiny babies should send feedback to Apple. Apple doesn't hang out on Macrumors.com.
And yes, I'm sure people some have sent feedback, but I doubt it's the majority.

Crying about a problem over and over again doesn't actually get it fixed you know.
If a baby has a dirty diaper, crying doesn't make it go away, actually having some change the diaper does.

So please, stop crying. Apple will eventually change your diaper.

Its sounds like you dont really want to be a part of this thread & topic ...so perhaps you should just stop reading and stop posting?

It would seem to me that the greater the volume of complaining the more likely it will be taken seriously.

In any case, this is a forum open to all topics, complaints and comments.

I love Apple products and always have.

However, this seems to be a genuine problem and the idea that iPhone owners should sit back passively and accept this failure as routine is nonsense. First, this is a problem with solely with Apple hardware and software. As the saying goes: "Live by a closed system, die by a closed system." Second, Apple has now taken steps to prevent rolling back updates, locking users into the faulty update. Third, since when is it excusable to release software without proper debugging, particularly when the users pay a premium? Fourth, many iPhone owners are on expensive contracts and therefore will lose service for which they have already paid. Moreover, some will have paid for replacement iPhones even though hardware was not to blame. Fifth, no doubt one of the main purposes of the update is to smack down jailbreaking - if any part of that effort contributed to these apparent problems, then Apple has some explaining to do to the vast majority of users who do not break their EULA.

And of course, there is the topic of this thread: Apple has not apologized, let alone acknowledged, the problem.

RIGHT ON THE MONEY!

It seems to me this release has been about testing the waters on jailbreak prevention and not about fixing systemic issues with the iphone. 3 Betas and this is the best Apple can release.

Who's been claiming their the best (best software, best hardware, more reliable).....hmmmm

So far over the lifetime of the iphone, I am not impressed with Apple. All that brainpower and their top priority is to stop the hacking.

 

[tremlock]

I think they're too busy dealing with the "does my silent switch seem a little loose?", or the "dude, i think my bezel is .0001 mm off, can i get a brand new phone? not one of them refurb deals"

 

[mstier09]

It seems to me this release has been about testing the waters on jailbreak prevention and not about fixing systemic issues with the iphone. 3 Betas and this is the best Apple can release.

This is my theory also, I think people might expect a new update to be a little unstable but since they aren't letting people downgrade the FW Apple is completely responsible for every complaint.

I understand they want to stop jailbreaking because it's easy to pirate apps once jaibroken, but it seems like this is more of a scorched earth tactic will ultimately prove ineffective and only serve to alienate people who trust Apple to put out good/stable products.

 

[VulchR]

I think they're too busy dealing with the "does my silent switch seem a little loose?", or the "dude, i think my bezel is .0001 mm off, can i get a brand new phone? not one of them refurb deals"

LOL. However, a certain amount of perfectionism is be expected when an iPhone costs more than most laptop computers (at least in the UK). If apple wants to lower consumer expectations, they should lower their prices.

 

[Rhosfelt]

Apple's business stance is and has always been to be quiet about bugs/problems. The only case of the admitting fault was the Mobile Me Disaster. Just sit tight 3.1.1 will be here soon enough.

 

[theviceofreason]

Your or you're, who cares, just relaaaaaaxxxxxx

your=possesive
you're=you are

*Possessive*. And while we're doing the smart-arse corrections:

Breathe, relax, wait, and make due.

That's *make do*.

Jesus....
All I am saying is whining about it (which is what you're doing, because it makes you feel less helpless in lieu of the frustrating circumstances) is not going to fix anything.

Not quite sure what "in lieu of" is standing in for here, as it were...

ad nauseum.

And *ad nauseam*.

Sorry to whine about these, just killing time while my phone resets.

 

[darngooddesign]

S*** happens. Buy a helmet.

What if s*** happens to that helmet?

 

[HitchHykr]

Jesus....
And if you know your iPhone is buggy, and you miss an important call because of said bugginess, that's on you, not Apple.
Since the whole thing started last Thursday, I have been using my POS phone. I can't afford to miss those calls and I am not going to take the chance that Apple will get a fix out sonner rather than later.
S*** happens. Always have a plan B.
Anyone who uses technology for business and doesn't have some chain of redundancy and back up religiously, I feel no sympathy for.
?

Are you serious when you say that iPhone users should carry two phones because the iPhone is unreliable? Maybe Apple should include that tidbit in their ads.

BTW, you get my nomination for fanboy of the year.