So far, the OP has started 3 threads, reporting so-called "bugs" in the iPhone4. The first was closed down by the moderators and the second is going the same way! Now we have this one!!
They all describe what happens when, as he says, "I try things in conjunction with other things being open and mix-and-match different combinations of screen taps and app loads and closes" (!). With respect, what he describes are not "bugs" in the accepted interpretation of the definition. They are malfunctions resulting from input to the 'phone which were never envisaged or designed for.
As he says "You all just use it "as intended" like opening apps, closing them, checking email,etc all the obvious things." Well, of course we do!!! That's what we bought our iPhones for - to use them as intended!!!.
Anything, if not used for the purpose it was designed for is going to do strange things. Imagine driving a car at say 50 mph and you ram it into reverse gear..... That action will certainly make the car behave in a very strange way and it certainly won't do the gearbox any good! Why? because cars are not designed to be driven that way! It's certainly not a "bug".
I suggest CjayC resets his phone back to as it was when it was purchased, forgets about being an R&D expert and just uses and enjoys his iPhone as intended.
While I respect your opinion on the matter, I have to say I whole heartedly disagree. I also don't think your car analogy makes much sense here. A bug, by definition, is an unexpected "event" that occurs when a certain condition is met... which is repeatable. Putting a gearbox in reverse at 50mph and blowing the transmission is not an unexpected result... nor is it repeatable. That's more akin to using your iPhone under water, which is not it's intended function... ending with an expected result of the phone dying.
There are lot's of ways things are "not used as intended" and in turn, creates a bug. How else do you think most security hacks on browsers, servers, etc are achieved? Do you think the malicious hacker was using it as intended? Just because he wasn't, doesn't mean it's not a bug. When you play a game and do something unintended and out of the ordinary that "bugs" out the system to give you an unfair advantage... that's a bug.
I think it is you who does not understand the definition of the word bug. Yes, maybe CJayC worded it a little wrong by saying you guys are using it as "intended". I don't think that is what he was trying to say. I'm sure he meant that you guys probably don't go beyond a certain routine when using the phone. I know I don't. That doesn't mean that when certain conditions are met, the phone will not wig out. In fact, this is how some jailbreaks are achieved. They attack a bug that creates a security hole.
The only difference is the severity of the bug. If it's something that is difficult to reproduce, then yes, it's not really important or pertinent to fix right away(or at all). If it's something that is easy enough to reproduce that someone may randomly trigger the bug from daily use... then it will only help us all if these bugs are ousted before the next iOS update.
To be clear, I'll try to make an example:
even if "sliding the volume to exactly 33%, then exiting and double clicking home to pick your ipod app, then selecting a song but not playing it, then pressing the lock button, then receiving a call" is the exact trigger of a "bug", it's still a valid use case and CAN/WILL happen eventually. You can argue all you want that the exact example given is not how the phone is intended to be used... but that would just be denying that there is an issue in the software.
