I've seen at least 4 users today post saying they would just set their phones down to idle and they'd come back to it and the screen wouldn't turn on.
Zmagik chime in I know you've been following along with me all day.
The answer to every unexpected behavior cannot be "its a beta".
I think it's a fair point to make, (the OP) This is precisely what a forum is all about. Yes, we know "it's a beta", but some of us actually like to discuss hiccups that occur from beta to beta. "It's a forum."
It most certainly can, when its beta.
It most certainly can, when its beta.
Pray tell, what do you think is going on? Is there a bug that's causing it? Yes? Who'd have thought it, a bug with beta software! What's the world coming to?
But he doesn't believe it's a beta problem...! "Sorry not buying that" is a stupid and arrogant response to a correct answer.
It may not be what he wanted to hear but at the end of the day it's beta software. There WILL BE bugs, bugs that were in one beta may not be in another beta and bugs that weren't in one beta may be in subsequent betas. This is how betas work. You are using the beta operating system to test for and report bugs, therefore, stop with the conspiracy theory crap and report the bugs to Apple.
I agree with everything you are saying. I'm just disappointed something so severe (although it hasnt spread like a plague) has shown up in a beta 3 (about halfway through development). That's all.
People need to calm the heck down and stop attacking me as if I'm anti-Apple. I'm pro Apple and just surprised QA didn't catch this.
Serious bugs can and do show up even late in the process. I am not one who has a problem with discussion bugs, but the attitude that it is unacceptable [for] a serious bug shows up this late is a bit unreasonable.
Here is why - often betas are on scheduled where on this date or that date is when the next beta is coming out and devs code toward that date. it is possible that in fixing one bug they realized they would have to rewrite a large chunk of code that might break other things. Often in those cases, you go on and do the rewrite in time for the next beta and deal with any new bugs that generate as a result in the next one. They may have already known before the beta went out about this bug but it was scheduled for the next beta to be fixed.
Something like this would be a serious bug and most likely one near the top of the list to work on next, but if introduced while fixing something else they wanted done in beta 3, there just may have not been the time to address this one in time to make it into beta 3 (or they didn't know they introcued it until beta 3 went out but I'm sure they know now).
Serious, even critical bugs can show up at any stage of the beta process. This is a serious one definitely but it showing up in beta 3 when it wasn't in beta 1 or 2 is the way things can do in the development process and shouldn't be unacceptable or disappointing... it is the way the process works.
Serious bugs can and do show up even late in the process. I am not one who has a problem with discussion bugs, but the attitude that it is unacceptable a serious bug shows up this late is a bit unreasonable.
Here is why - often betas are on scheduled where on this date or that date is when the next beta is coming out and devs code toward that date. it is possible that in fixing one bug they realized they would have to rewrite a large chunk of code that might break other things. Often in those cases, you go on and do the rewrite in time for the next beta and deal with any new bugs that generate as a result in the next one. They may have already known before the beta went out about this bug but it was scheduled for the next beta to be fixed.
Something like this would be a serious bug and most likely one near the top of the list to work on next, but if introduced while fixing something else they wanted done in beta 3, there just may have not been the time to address this one in time to make it into beta 3 (or they didn't know they introcued it until beta 3 went out but I'm sure they know now).
Serious, even critical bugs can show up at any stage of the beta process. This is a serious one definitely but it showing up in beta 3 when it wasn't in beta 1 or 2 is the way things can do in the development process and shouldn't be unacceptable or disappointing... it is the way the process works.
I just don't have the time, or the crayons to explain it to you.
No, because it's a rude and flippant response that doesn't add any value to the conversation.
And someone giving a response gets
"Sorry I'm not buying that" as a response isn't rude and flippant?
At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.
Fair enough
----------
Judging from the attitude you're giving me I figured you'd have plenty of Crayons laying around.
Too many edits kid, couldn't you make mind for a comeback that you had to edit it, hahahaha, plus your comeback is pathetic, I just told you I don't have any crayons to explain it to you, but I have some time now.
When someone tells you it's a beta problem, and you say, "I'm not buying that" then you my friend have no place in your own thread.
So quoting your previous childish comeback, "you should leave your own thread" hahaha
And someone giving a response gets
"Sorry I'm not buying that" as a response isn't rude and flippant?
At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.
The entire thread was just an observation I made about a new issue that has sprung up and my disappointment with how that got passed QA. As I'm typing this more and more people are experiencing the issue. I was being "laughed" at when I mentioned 3-4 people already have the issue and now that number has grown.
Also somewhere in the middle of this apparently Niki and I got into a e-sword fight.
It's not an issue as you're making it out to be at this point. It only becomes an issue, when iOS 7 is finally released to the public. If phones are still randomly going into DFU mode still, then you can complain.
As of right now, it's a Beta. Weird **** is going to happen. Each new Beta release things will be fixed, others broken. It's how it works. I have been a developer since iOS 5. I have never had my phone go into DFU mode randomly. Rebooting, crashing, acting wonky - yes.
As for the user that has an entire family with phones on iOS 6 going into DFU mode, go to Apple. There is obviously an isolated issue with your phones/software/update. It's not normal and random DFU mode is not something that has been "happening" since any iOS version.
Please stop acting like this is a final product. Asking why a beta is doing something is irrelevant. If you really want to know - become a developer (if you're not already) and look at the code to see what is going on. Also use the bug reporting feature. If you're not a developer and can't use any of those features, please stop bitching.
So am I wrong to assume every beta should be more stable than the previous? If so, then Ok. I guess things could get worse before they get better.![]()
And someone giving a response gets
"Sorry I'm not buying that" as a response isn't rude and flippant?
At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.