or Connect
AppleInsider › Forums › Mobile › iPhone › iPhone 5s has 2% app crash rate; crashes half as likely on iPhone 5 & 5c
New Posts  All Forums:Forum Nav:

iPhone 5s has 2% app crash rate; crashes half as likely on iPhone 5 & 5c

post #1 of 94
Thread Starter 
Apple's new 64-bit iOS 7 and A7 processor found in the iPhone 5s apparently have a few bugs that still need to be ironed out, as a new study reveals that applications are twice as likely to crash on the iPhone 5s than they are on the 32-bit iPhone 5.

iPhone 5s


The data collected by Crittercism, and shared on Friday by AllThingsD, reveals that applications running on the iPhone 5s have a crash rate of about 2 percent. In contrast, last year's iPhone 5 and this year's iPhone 5c, which run the same CPU and 32-bit version of iOS 7, see an application crash rate of just under 1 percent.

A representative for Crittercism suggests that crashes are more likely to occur on the iPhone 5s because developers were unable to check compatibility with the latest iPhone and its new 64-bit A7 processor ahead of its launch. Testing for iOS 7 on 32-bit chips has been possible since the first beta was released at Apple's annual Worldwide Developers Conference in June.

Despite lingering issues, the bug tracking company said Apple has still done a good job of transitioning to a new 64-bit version of its mobile operating system in a way that is largely seamless to end users. Such problems are inevitable with the release of any new hardware or software, they said.



The data on iPhone 5s crashes comes as some users have reported seeing Windows-style "Blue Screen of Death" reboots on Apple's latest handset. The issue seems to be triggered by using the multitasking feature of iOS 7, which can be accessed by double-tapping the home button.

Apple has already released two minor updates for iOS 7 to address bugs. The first was a day-one update available for new iPhone 5s and iPhone 5c buyers, while iOS 7.0.2 arrived in late September to fix a lockscreen passcode bug.

The company has promised to soon release another update to iOS 7 to address issues with its iMessage service, as well as iPad supervision profiles. Apple is said to have provided select partners with an early version of iOS 7.0.3 earlier this month.
post #2 of 94
Haven't seen a problem with the iPhone5S yet. Must not be running apps which are not handled appropriately.
post #3 of 94
Of course there are bugs but I can't say it's a huge issue or a deal breaker. I've had exactly one non-repeateadable blue screen.
post #4 of 94

"Despite lingering issues, the bug tracking company said Apple has still done a good job of transitioning to a new 64-bit version of its mobile operating system in a way that is largely seamless to end users. Such problems are inevitable with the release of any new hardware or software, they said."

 

Yet the report reads like yet another "Apple is doomed" screed and will be picked up and spread like gonorrhea on a Thai cruise ship by the anti-Apple tech media. I can just see the headlines on Computerworld, C|net,  Forbes, MacRumors, AppleInsider... oh wait.

post #5 of 94
Quote:
Originally Posted by AppleInsider View Post

Apple's new 64-bit iOS 7 and A7 processor found in the iPhone 5s apparently have a few bugs that still need to be ironed out, as a new study reveals that applications are twice as likely to crash on the iPhone 5s than they are on the 32-bit iPhone 5..

Based on the tiny number of people who report their bugs to this company.

While it's likely that there will be more bugs on the 5S than on the 5C, I doubt if this company has any real evidence to back up their 'twice as likely" or "2%" claims.
"I'm way over my head when it comes to technical issues like this"
Gatorguy 5/31/13
Reply
"I'm way over my head when it comes to technical issues like this"
Gatorguy 5/31/13
Reply
post #6 of 94
No problems here. My 5s running 7.02 has been more rock solid with apps (and I have about 200 apps on my phone), and I have hammered this past week. I cant say I've had one app crash yet.

It seems more stable even than my 5 running 6.1.4 (possibly because some of the apps have been updated for iOS 7 compatibility and that makes them less stable).

Even infinity blade 3 loads without issue. The only issue I've had is the well known email POP 'bug' displaying tens of thousands of unread emails (all my other accounts support exchange server access which register the read and unread email count)
post #7 of 94
I had that BSOD on my 5s, it rebooted, and then did it again. That isn't good, but I'm sticking with it.
post #8 of 94

More crashes is newsworthy, despite desires that the news be suppressed.

 

And Apple made a mistake here, there's NO good reason to put a 64-bit processor in a mobile device yet.  Maybe in a few years when individual apps need more than 2GB RAM it'll make sense, but the iPhone 5s only has 1GB RAM, Apple rushed this to market, it gives the user NO advantages over a 32-bit chip, and the software wasn't ready for it yet.

 

Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

post #9 of 94

I've definitely seen more crashes with my 5s than I ever experienced with my 4s, and I'm not sure what's going on -- the phone will suddenly go to the white screen with the black Apple logo, as if it were rebooting, and then a few seconds later the lock screen shows. It's apparent that it wasn't actually a reboot though, because a) the Apple logo screen only shows for about 5 seconds, and b) I'm not forced to enter my password at the lock screen -- fingerprint scan still lets me in. The last time it happened was when I was trying to search for a song in the Music app.

 

This has probably happened about 2 times a week (so it's not terribly inconvenient or anything), and I'm a pretty heavy user. I figured it was more likely due to bugs in the newly revamped iOS rather than something to do with the 64-bit processor, but who knows.

post #10 of 94

Same here. I get the most crashes and restarts when I go to multi-task on the 5S. It happens once or twice a day. Not too big of a deal but a little annoying.

post #11 of 94

This is why I'm going to wait for the 128GB version. Hope it will be this year but I'm not going to rush to upgrade to a phone with the same storage that's presently inadequate for me and one that also happens to crash more!

post #12 of 94
Crittercism. Enough said. They trot out reports like this right when iOS is released and compare it to Android from last version and imply iOS crashes more. They did this back when iOS 5 came out and fandroids are STILL linking to that bogus study as proof that Android is more stable.
post #13 of 94

Well, that didn't take long. BIG HEADLINE at C|net...

 

Blue Screen of Death attacks some Phone 5S owners

 

"The infamous Blue Screen of Death seems to have expanded from Windows PCs to iPhones."

 

Apple Is Doomed!

post #14 of 94
I'm on the train so can't check Crittercism's site at length, but last time I did they only released ONE study when iOS 5 came out. AFAIK they have only now done two studies - iOS 5 release and iOS 7 release. They have never done a test 6 months later to see if the numbers have changed nor have they done a test after a new version of Android is released to see how their developers are doing.

Oh, and Google is an investor , BTW.
post #15 of 94
No blue screens yet with my 5S, but the camera/photos app has locked up a few times to where I have to remove it from memory and reload it...
post #16 of 94
My app kept crashing consistently, but looks like it was more of an iOS 7 issue.

Took a couple weeks of work to fix. Just got the green light. 1biggrin.gif
post #17 of 94
I have had a few crashes on my 5 that are a bit annoying but nothing major. My wife has the 5s and no issues to speak of. I would expect some turbulence as they navigate through this transition but will improve over time.
post #18 of 94

My daughter just got a new iPhone 5 because her old one was having problems and last night she said her phone froze 3 times in 1.5 hour time she is taking it back today only have 7 days of warranty left on it. She took it to Apple and they said it was the firmware so they updated it, I hope this solves the problem, as soon as her new iPhone 5s comes in I get her 5.


Edited by mwhiteco - 10/11/13 at 1:32pm
post #19 of 94
I've not noticed any dramatic increase in crashes between my 5s and the 5 but I was actually more problems given the newness of the 64 bit architecture. I noticed the resident Google shills/Apple haters here on the forum are crapping about Apple being doomed for going with 64 bit -sigh-
post #20 of 94
Quote:
Originally Posted by mwhiteco View Post

My daughter just got a new iPhone 5 because her old one was having problems and last night she said her phone froze 3 times in 1.5 hour time she is taking it back today only have 7 days of warranty left on it.

Are you certain it's the phone and not an app running on iOS 7?
post #21 of 94
I've had an app crash maybe four times. Always the same app, too: Numbers. It happens intermittently when I try to exit the app while it's still replicating updates to the cloud. If I slow down and let it finish replicating, it works fine.
post #22 of 94
OMG! How dare Apple release an industry changing chip and not have all of the bugs ironed out in 4 weeks /s
post #23 of 94

Developers need to update their apps, huh? How is this Apple’s fault?

post #24 of 94
Quote:
Originally Posted by akqies View Post


Are you certain it's the phone and not an app running on iOS 7?


I will tell her to remove all the apps and see if that helps. Thanks for your suggestion.

post #25 of 94
Quote:
Originally Posted by booboo View Post

I've had an app crash maybe four times. Always the same app, too: Numbers. It happens intermittently when I try to exit the app while it's still replicating updates to the cloud. If I slow down and let it finish replicating, it works fine.

 

Disabling Cloud syncing for iWork suite is supposed to help reduce crashes.

post #26 of 94
Quote:
Originally Posted by Tallest Skil View Post

Developers need to update their apps, huh? How is this Apple’s fault?

As shown. Apple's iWork apps also can result in a crash so it's not just 3rd-party developers.
post #27 of 94
Quote:
Originally Posted by mwhiteco View Post


I will tell her to remove all the apps and see if that helps. Thanks for your suggestion.

Don't be an ass.
post #28 of 94
I don't think that white screen Apple logo faux reboot thing is related to the processor. It happens on occasion with my iPhone 4 so it's likely the iOS 7 which I'm sure will be corrected.
post #29 of 94
Quote:
Originally Posted by DarkVader View Post
Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

Anybody should be called on their mistakes if they are significant (affects end users), and if they have a history on not correcting their mistakes. But ... Your assertion that iOS 7 is a "steaming pile of garbage", and that people buy iPhones because they are status symbols, is silly and founded only on prejudice. The fact that you have been an apple user since 1982 proves to me that you have become a grumpy curmudgeon. We have to call each other on this ageing tendency. RAGE against it!

post #30 of 94
Quote:
Originally Posted by DarkVader View Post
 

More crashes is newsworthy, despite fanboi desires that the news be suppressed.

 

And Apple made a mistake here, there's NO good reason to put a 64-bit processor in a mobile device yet.  Maybe in a few years when individual apps need more than 2GB RAM it'll make sense, but the iPhone 5s only has 1GB RAM, Apple rushed this to market, it gives the user NO advantages over a 32-bit chip, and the software wasn't ready for it yet.

 

Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

 

 

We all have our *anecdotal* opinions. Fact is, though, iOS 7 is brilliant, and is an entirely necessary move away from iOS 6, which looks just dated and wonky now. 

 

Additionally, Apple is often accused of not innovating (though, wrongly), but when they are actually the first to make an advance in specs you cry foul?

 

This issue is minor, obviously, and will be fixed in due course. If you're complaining about iOS crashes, just take Android for a lengthy (and very eye-opening) spin. Make sure your airbags are tuned on.    

 

At some point your product has to deliver in order to sell well, especially when it's a closed platform, and one that aint cheap, either. The iPhone consumer satisfaction reports are out there for everyone to see, and they speak plainly to the fact that the iOS user experience is simply superior, due in part to the way in which Apple handles their vertical business model and their user-centric philosophy. 

 

So no, no particularly salient Apple "mistakes" in this case, apart from an issue requiring a patch, *or* developer updates. And there ya have it.


Edited by Quadra 610 - 10/11/13 at 7:19am
post #31 of 94
Quote:
Originally Posted by DarkVader View Post
 

More crashes is newsworthy, despite fanboi desires that the news be suppressed.

 

And Apple made a mistake here, there's NO good reason to put a 64-bit processor in a mobile device yet.  Maybe in a few years when individual apps need more than 2GB RAM it'll make sense, but the iPhone 5s only has 1GB RAM, Apple rushed this to market, it gives the user NO advantages over a 32-bit chip, and the software wasn't ready for it yet.

 

Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

What are you talking about with the 64-bit processor being a waste? Read any article about the chip and tell me there's no advantage to it. Developer (specifically a new unreleased Infinity Blade app) and Apple apps (the Camera app more specifically) are able to perform so much better. That's half the reason why the camera is so much better, despite being the same megapixel count - it can process so much more, even faster than before. And finally, just read the comments retracted by Snapdragon saying that the 64-bit processor is a marketing gimmick.

 

The major reason for the higher amount of crashes is because there weren't/aren't many devices with the 64-bit processor for developers to test their apps against. So just chill.

post #32 of 94
We've had 2 gold 5Ss since Sept 27, and no crashes or hiccups at all. And I've only noticed one little quirk that I've not seen before. I'm pretty sure it's in iOS7 and not the 5S, but maybe.

Say I type some text in a message, hit return to give me a new line, and now I want to paste something at that spot. Tap and hold, right? Can't. I have to add at least one space on that line before I get a paste option to pop up.
post #33 of 94
I must have been lucky, no crash on my 5S as yet, though one or two older apps can behave oddly, though I have found workarounds.

All my devices so far (iPhone 4, 4S, 5S and iPad) have been fine and have no issues with iOS 7, no app crashes as yet either.

Would it be worth starting a list of apps that have been run prior to the crash to see if other users can corroborate? Otherwise it's just a case of I got a crash, and I got a crash and no established reasons why
post #34 of 94
Quote:
Originally Posted by DarkVader View Post
 

More crashes is newsworthy, despite fanboi desires that the news be suppressed.

 

And Apple made a mistake here, there's NO good reason to put a 64-bit processor in a mobile device yet.  Maybe in a few years when individual apps need more than 2GB RAM it'll make sense, but the iPhone 5s only has 1GB RAM, Apple rushed this to market, it gives the user NO advantages over a 32-bit chip, and the software wasn't ready for it yet.

 

Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

 

 

You must be living in a vacuum. The idiotic insinuation that a 64 bit processor was somehow a marketing move has been refuted by experts. The 64 bit processor has over twice the transistors, which are wider then the ones found in the 32 bit version. The result is the A7 can process information much faster, and it can process 64 bits of information without breaking the information down into 32 bits. 

 

I have never known Apple to include technology just for the sake of including it. The results speak for themselves, the chip is on average twice as fast while using less power. Are there some kinks? Maybe, but you can't resolve them without putting the product out on the market and figure out how all the various third party software effects the product. 

 

This move was smoother then Apple moving to Intell, and bringing out OSX for the first time. When Apple brought OSX initially, I would get the blue screen of death daily. Within a few months, it dropped significantly.  

 

To each there own, but I love iOS7. I find new things about it everyday. The attention to detail is great. Last night around 12:15 am, I asked Siri to remind me call somebody tomorrow around 11. Siri knew it was shortly after midnight and responded, "Just to be clear, do you want to be reminded later today, on October 11,  or tomorrow on October 12. Truth was I wanted to be reminded later today. 


Edited by TBell - 10/11/13 at 7:23am
post #35 of 94
Quote:
Originally Posted by EricTheHalfBee View Post

IOh, and Google is an investor , BTW.

Ding, ding, ding, ding. Follow the money.
Quote:
Originally Posted by DarkVader View Post

More crashes is newsworthy, despite fanboi desires that the news be suppressed.

Except that I don't see anyone suggesting that news be suppressed.

I do see a lot of people pointing out that it's not particularly meaningful, though.
"I'm way over my head when it comes to technical issues like this"
Gatorguy 5/31/13
Reply
"I'm way over my head when it comes to technical issues like this"
Gatorguy 5/31/13
Reply
post #36 of 94
Quote:
Originally Posted by paxman View Post

Anybody should be called on their mistakes if they are significant (affects end users), and if they have a history on not correcting their mistakes. But ... Your assertion that iOS 7 is a "steaming pile of garbage", and that people buy iPhones because they are status symbols, is silly and founded only on prejudice. The fact that you have been an apple user since 1982 proves to me that you have become a grumpy curmudgeon. We have to call each other on this ageing tendency. RAGE against it!
I'm always skeptical when people throw out the "I've been a loyal apple user since the very beginning" card. And also when they throw out hyperbolic statements like "steaming pile of garbage". I'm sorry if that were the case no one would be buying new iPhones or updating their existing phones. The best trolls are the ones that make it look like they're long time fans concerned about Apple's pending DOOM. 1rolleyes.gif
post #37 of 94
Quote:
Originally Posted by jinjo235 View Post
 

Same here. I get the most crashes and restarts when I go to multi-task on the 5S. It happens once or twice a day. Not too big of a deal but a little annoying.

It happens to me about 2 times a week on my 5S , up from about once a month or less on my 5.  Most crashes are in Safari or when starting a new app.  My last crash besides Safari was Waze. 

post #38 of 94
Quote:
Originally Posted by Wings View Post

We've had 2 gold 5Ss since Sept 27, and no crashes or hiccups at all. And I've only noticed one little quirk that I've not seen before. I'm pretty sure it's in iOS7 and not the 5S, but maybe.

Say I type some text in a message, hit return to give me a new line, and now I want to paste something at that spot. Tap and hold, right? Can't. I have to add at least one space on that line before I get a paste option to pop up.
I have the same problem. Must be iOS 7 bug.
post #39 of 94
Quote:
Originally Posted by BeltsBear View Post
 

It happens to me about 2 times a week on my 5S , up from about once a month or less on my 5.  Most crashes are in Safari or when starting a new app.  My last crash besides Safari was Waze. 

and almost all of my iOS7 on my 4s crashes are in Safari as well... 

post #40 of 94
Quote:
Originally Posted by DarkVader View Post

More crashes is newsworthy, despite fanboi desires that the news be suppressed.

And Apple made a mistake here, there's NO good reason to put a 64-bit processor in a mobile device yet.  Maybe in a few years when individual apps need more than 2GB RAM it'll make sense, but the iPhone 5s only has 1GB RAM, Apple rushed this to market, it gives the user NO advantages over a 32-bit chip, and the software wasn't ready for it yet.

Mix that with iOS 7 being a steaming pile of garbage, and you get a device that's selling well ONLY because it's a status symbol.  Look, I've been an Apple guy since 1982, but if we don't call Apple on their mistakes, we're only going to get junk.  And if Apple keeps pushing junk out for too long, Apple really will be dying. And NONE of us want that.

The reason is to allow the app developers time to get there. Start using it now. Start taking advantage. By 2015, every iOS device sold will be 64-bit, most apps (of value) will be supporting it, and android will still be all over the place.

Same with iOS 7. I think the new design language is to support various display sizes without degredation. Allow it to scale.
Quote:
Originally Posted by Wings View Post

We've had 2 gold 5Ss since Sept 27, and no crashes or hiccups at all. And I've only noticed one little quirk that I've not seen before. I'm pretty sure it's in iOS7 and not the 5S, but maybe.

Say I type some text in a message, hit return to give me a new line, and now I want to paste something at that spot. Tap and hold, right? Can't. I have to add at least one space on that line before I get a paste option to pop up.

I see the same copy/paste troubles on my 5 with iOS 7
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: iPhone
  • iPhone 5s has 2% app crash rate; crashes half as likely on iPhone 5 & 5c
AppleInsider › Forums › Mobile › iPhone › iPhone 5s has 2% app crash rate; crashes half as likely on iPhone 5 & 5c