Yeah, I figured it was! Is everyone experiencing this? I was a little put out by WeegieMac's dismissal of problems (including the crashing of settings) as "you've done something wrong", hence my slightly capsaicin-heavy response. I assume his does not crash when he follows my steps?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Install every Beta as New
- Thread starter Armen
- Start date
- Sort by reaction score
Yeah, I figured it was! Is everyone experiencing this? I was a little put out by WeegieMac's dismissal of problems (including the crashing of settings) as "you've done something wrong", hence my slightly capsaicin-heavy response. I assume his does not crash when he follows my steps?
I wish it did... while the video-recording-initiated-from-lockscreen bug is fixed, the Camera app still occasionally resprings the entire device immediately after taking a still. (It doesn't record the still. That is, it's gone forever.)
All this on an absolutely clean device w/o any third-party app or even iCloud set up. (It's my dev / camera iPhone5 not in daily regular use.)
Your comments in this thread are appropriate and well said.
I will add that a separation needs to be made between iOS 7 and apps. The settings bug described here should be reported to Apple and iOS 7's stability judged on that. I'm not sure how much Apple cares if Tap Tap Time waste crashes (well, I'm sure they care but it should be reported to the developer and they will work it out with Apple if an API is broken or missing or...).
So I agree with WeegieMac that there is something that person is doing that causes something to crash if it doesn't crash for the majority of other people. Or maybe it's isolated to a 4 or 4S or 5. A thoughtful person would restore as new and try to reproduce the problem before installing anything. Then install apps one by one to see when the problem occurs. If you get back to your phone fully loaded and configured how it was before and don't have the problem, then it was an issue with restoring an existing backup onto the phone.
That's what we're trying to do here... Find the problems and report to the responsible party. If not, good luck but don't come in and say how bad iOS 7 is when folks who follow a few simple guidelines are having a near GM experience. If everything worked then it would be released. And apps would still continue to crash until the developers update them.
Wow. /walloftext. Sorry.
Clean b3 install here (GSM iPhone 5). Absolutely no battery drain - as opposed to the b1->b2 OTA upgrade.
Upgrade install of Beta 1. Then OTA upgrade of Beta 2 and then 3. No battery drain here, either.
Then there's this guy who DID a clean install on his iPhone 5 and is seeing massive battery drain in Beta 3 that he wasn't seeing in Beta 2: https://forums.macrumors.com/threads/1607971/
Whether or not you do a clean install is not the issue.
Well, the situation is exactly the opposite here. I've done one OTA upgrade (b1 -> b2), which resulted in MAJOR battery drain. All other upgrades were clean (incl. the restore after some days of suffering from the OTA b2 battery drain) and showed no signs of power drain.
All this on an iPhone 5 without third party apps / iCloud (disabled during activation) / automatic background app upgrades (disabled manually in Settings).
Surely not. It's 100% CPU drain because of a stale process, which drains orders of magnitude more power than the natural differences between two batteries.
100% drain is pretty common with (in this regard) failed upgrades or just plain bugs remained in the OS and not spotted by Apple. The 6.1.3 (latest) iOS version of iPhone 3GS, for example, has the same problem (even) after a fresh, clean, no-backups-restored installs if you enable iCloud during setup. (I've documented this at https://forums.macrumors.com/threads/1586046/ , should you be interested.)
Yes, you're probably right. It could well be in one of Apple's core apps, meaning it doesn't matter what type of install you've done.