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.
Apps on iPhone 5s Reportedly Crashing Twice as Often as on iPhone 5c and iPhone 5
- Thread starter MacRumors
- Start date
- Sort by reaction score
Reduce motion being "off" could exacerbate certain things related to video memory and other bugs that aren't necessarily app dependent*, but for the purposes of this article, the other things you mentioned wouldn't likely do anything to solve the general system and apps to be prone to crashing.
That being said, I always disable Bluetooth on phones since I have no reason to leave it on, and I'm all for conserving battery life.
*Anyone who has tried to use a system or run a game with an unsupported video card and/or reverse-engineered video card drivers know how seemingly random errors and crashes can crop up out of nowhere know what this is like. (WINE+older games, I'm looking at you).
Initially I thought he was a Samsung troll. But now I think he's (somewhat justifiably) flaming iOS 7. Not all of us are enamored with iOS 7. I agree with others that iOS 7 feels rushed & needs to bake a little more...perhaps until it morphs into iOS 8 next year.
IMHO, getting rid of the skeuomorphism was nice, but they went way off the rails in the opposite direction of stark simplicity.
If you divide the speed increase by the number of crashes you get the inverse Crash-to-speed (CTS) ratio, a very useful benchmarking heuristic.
I can't say I agree with that necessarily. There is no way for the end user to know what sort of calls are being made by the application that is crashing. It's entirely possible that some background process is trying to reference something at the same time the current app is and a crash occurs. I have not developed apps for the iPhone, so I honestly have no idea.
Twice the amount of crash still is 3x times less than regular plain old Android.
I'm the joyous owner of a iPhone 5 and an Nexus 7 and god the Nexus is awful by any standard. The iphone barely ever crash (don't remember the last time) so my guess is 0 x 2 = 0.1
That's what many iPhone users believe (is it because of those "feel good" commercials?) but this is factually incorrect. Android apps were about on par (depending on OS version) with iOS6 according to Crittercism so now (with iOS7/iPhone 5S) the frequency of crashes on Android is twice lower.
To be fair, half of active Android users are on a 2 year old OS or older, so developers have had a bit more time to work out the bugs.
To be fair, half of active Android users are on a 2 year old OS or older, so developers have had a bit more time to work out the bugs.
That's irrelevant because Crittercism provides crash data separately for all Android versions. According to them "overall Android apps that use Crittercism have a 1.76% crash rate ... compared to Android Jelly Bean apps, which have a 1.5% crash". So it's actually a reverse trend for Android - fewer crashes on newer OS versions.
And how does Jelly Bean compare to the iOS version released around the same time?
About the same (slightly higher). That's what their report said. However, switch from iOS6 to iOS7/iPhone 5S is not a typical scenario. One should not expect this to happen for example when KitKat gets released.
Where did this "Crittercism" got their data?
This is stupid, developers don't write drivers for iOS, Apple does.
Also, developers don't change their code to "insert processor here", because they can't, they write in ObjC and that's all they got.
This is stupid, developers don't write drivers for iOS, Apple does.
Also, developers don't change their code to "insert processor here", because they can't, they write in ObjC and that's all they got.
Initially I thought he was a Samsung troll. But now I think he's (somewhat justifiably) flaming iOS 7. Not all of us are enamored with iOS 7. I agree with others that iOS 7 feels rushed & needs to bake a little more...perhaps until it morphs into iOS 8 next year.
IMHO, getting rid of the skeuomorphism was nice, but they went way off the rails in the opposite direction of stark simplicity.
Well you can thank the Android droolers for running their loud mouths so much that Apple decided to go their way and design iOS with those people's demands in mind.
How is 30%+ (depending on Android OS version) more crashes "about on par" or "about the same (slightly higher)"?
Not sure what you are getting at here. The increase in crashes is related to the hardware, not a new OS version. I would certainly expect an increase in crashing the first few weeks on the first 64-bit Android device.
Twice the speed, hence it crushes with increased speed also. Sounds logical.
The question is: can it be used to jailbreak?
The question is: can it be used to jailbreak?
Not at all related. Nice try.
I might have missed the proof point. But has it been determined specifically that it's a hardware issue? Because there are other Apple devices affected by issues with iO7 and crashing apps/reboots.
Well, there is the title of the thread... "Apps on iPhone 5s Reportedly Crashing Twice as Often as on iPhone 5c and iPhone 5." And then the OP provides more details.
Should have waited for the.6, as the 64bit processor is still premature there are bound to be these hiccups. I am still happy with my 5 iOS 7 is working flawlessly with little or no app crashes to report here.
Yeah, but if you also put a dress and a pair of high heels on that pig, you have a date to the prom.
Try turning on Reduce Motion in the Accessibility section. That fixed my issues with the Blue Screen.
This is a bit of a pointless debate to have here... but... as an experienced C# developer you know there are plenty of ways to write code with C# (and Java) that will crash an app as hard as accessing a dangling pointer. Not to mention Objective-C has crash-preventing features of its own that C# doesn't. E.g., sending a message to nil has nice well-defined non-crashing behavior while the equivalent in C# will crash the app. Likewise, it's not quite right to imply Objective-C isn't a modern language. It has its clunky old bits. But it has dazzling new parts too, like ARC that supplies a better solution to memory management than the GC that C# and Java have. But these details aside, from the macro view we know Objective-C is a good language for developing stable software...because so much of it has been developed. E.g., crash rates for iOS devices before the 5S were just under 1% according to the story. Lilo77 (a consistent Apple critic) here is quoting a 1.76% overall rate from the same source for Android for which Java is predominently used. So Objective-C based mobile apps have historically done better than Java-based ones and even on a bad day, like today, they are comperable. Overall Objective-C seems to have proven to be easier to develop stable apps for, notwithstanding recent 64-bit issues. They are possibly temporary, though we don't know yet. (I don't have any illusions that Objective-C is the perfect programming language, but it definitely has its points. Also, just as important, more so actually, the frameworks that comprise the iOS SDK are excellent.)
Going to 64 bit, I would expect Java based apps, which are the overwhelming majority of Android apps, to be pretty solid.
It's a lot easier to validate the code of a single virtual machine, than hundreds of thousands of native apps.