You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

💡 Did you know?

⏺ If you can't accept iCloud Terms and Conditions... Learn more >

⏺ If you don't see your iCloud notes in the Notes app... Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iPhone 5S Springboard Crashes

Im a owner of the 5S 16GB 7.0.2 from the release date. But from the release till now i experienced 2 random springboard crashes. Once when i opened the camera from lockscreen and once when i wanted to call someone from the ''recent'' list. The apple logo came up for 5 seconds and it went back to normal.


Is this just bad luck for 2 times or is this something to worry ?


Maybe someone can look to my Crash Report. Im not into that.


Thnx in advance.

iPhone 5s, iOS 7.0.2

Posted on Oct 5, 2013 9:33 AM

Reply
43 replies

Jan 4, 2014 6:14 AM in response to KiloDiesel

I have experienced soft crashes (white screen/black apple for 3 or 4 seconds) on many occasions. I began to notice it only occurred after using the print unlock method. I tested this by using swipe unlock with code only for a week solid and experienced no mini-crashes. After the week, I began using the print method again. I experienced at least 4 or 5 crashes the next 24 hours and continue to every once in a while.


This is by no means scientific evidence that the print scanning crystal or software is faulty; however, it's pretty close from my perspective. Each crash is shown as a Springboard event and is sent auto to Apple. I continue to use the print ID method in that I prefer it even with an occasional crash.


I believe (hope) Apple is aware of this minor issue and will eventually address it. Many of you on here are far more proficient with this platform than me and may disagree and continue to dive into diagnosing this apparently common problem. I'll continue to watch this tread and urge anyone experiencing this problem to try my little experiment as described above.

Jan 20, 2014 11:29 AM in response to KiloDiesel

I've had springboard crashes after touch ID since day 1 of a new 5s. Tried several restores...still crashing. Finally a new phone, no luck. Senior service rep says its software related (which I already suspected) and must be due to a bug in firmware that's in the backups. So try restore as new phone and start over. I hesitated since this is an evil solution. After HOURS of downloading all my apps, settings etc. it was fine for 1 day. Then today springboard crash!!! I Can't believe it...I give up...this may be my last iPhone.

Jan 20, 2014 12:29 PM in response to WDH1000

I have done the same as you described with my new 64 GB iPhone 5s. I was scheduled to receive a replacement but some "issues" came up. I have done the restores as you mentioned you did and they take hours to complete.

One thing that I did note, to reduce the number of crashes was using WiFi whenever possible. I have the ATT 3G Microcell running at home with a cable internet connection.

As much as I like LTE, I think it is tied directly to the crashes and the chipset that is in the iphone 5s. Upon receiving the new phone in the first month I used LTE whenever possible. It was great until ATT started to throttle me at about 5 GB of my "unlimited" data plan. I continued to use it until the new biling period taking my usage to 7 GB for the month. I typically in the past never used more than a max of 2 GB od data on any iphone in the past.

Long story short this has helped with the crashed, but it came at my expense, I had to add Cable Internet connectivity from Comcast as the ATT DSL just did not offer enough speed and a consistent connection. The worst part of being throttled by ATT was being in need of some decent data speeds when away from a wifi location and not having it, they throttled me to a point that my phone's data barely worked over the cellular network.

Last month was my 2nd month of having the 5s. I used about 560 MB of cellular data and had less than ten full crashes of the iPhone. But there again I was on WiFi 99% of the time. Strange??

What is the memory capacity of your 5s?

How many apps do you have on your phone (a topic the tech support reps like to bring up, but should have not bearing on the crashes)?

What are you going to do next?

Did the tech support reps offer you any other solutions?

I think this could very well be an Apple issue that is either a problem the chipset or the software or both. If you Google this topic you will get many hits.

Jan 20, 2014 6:27 PM in response to JustMy2Cents

I have 32g phone about 100 apps. After doing a lot of research, I've come across a possible solution: turning "reduce motion" (under accessibility) back to off. Many have had luck with this. The parallax effect makes me dizzy, so I've had reduce motion set to on sine my iPhone 4. Do others with the springboard crashes have this set to on or off?

Jan 23, 2014 9:32 AM in response to prest86

Thank you very much for the post. I loved how it was treated by the "company" as a user error until now. I worked on the issue for 2 months and then backed off this month completely after reading the posts on here and elsewhere that it is clearly an iphone problem. I think I have close to a 100 hours of researching and working on trying to resolve this issue. Thanks again.

Let's hope that the new fix comes to us quickly.

Jan 23, 2014 9:38 AM in response to WDH1000

I have the parallax effect turned off. Sorry for the delay in replying.


Did you see the news release, Apple admits fault. prest86 posted it earlier today, (thanks prest86):

Good news guys, here official report from Apple:

http://mashable.com/2014/01/22/iphone-screen-of-death/

They officially said they know the problem and that a fix is under development...

Jan 23, 2014 11:35 PM in response to prest86

Let's hope that iOS 7.1 will resolve the the native app crashes as well. I can't believe we have to wait until mid-March 2014 for iOS 7.1 or so the other reporters are saying. Yet none of the other reporters have direct quotes from the same Apple PR person. I find it highly suspect that no one else has a direct quote from the same PR person Apple corporate and that there's no official Apple press release.

I spoke with Apple corporate today and there is zero press releases on the topic reported today. I left a voicemail for the PR person quoted in the "Mashable" news story and had my Apple contacts follow up with her late this afternoon. Still waiting to hear back. Wouldn't this be a big wild goose chase if the PR person that was supposedly quoted never said anything. I will be ****** and the author of the news story should be banished from journalism and shipped off to North Korea. I'd be glad to buy him a one-way ticket to North Korea.


I have found no workaround regarding the crash of the native apps and to this day still it continues. I'm open to suggestions if anyone knows of any workarounds.


As for the screen of death (yes I know I am repeating myself for the sake of new readers), what has help me so far is turning off cellular data and using Wi-Fi exclusively whenever possible. And then away from home or office I use the cellular data very sparingly. I am still the firm believes that the problem is inherent to the LTE chipset in the iPhone 5s. I'm not an engineer but I would dare say that it's a **** good guess considering that 90+ percent of iPhone 5s crashes has stopped occurring as soon as I turned off cellular data and avoided the 5 GB throttling limit of AT&T's unlimited cellular data plan. I actually had to go and subscribe to Comcast Internet service so that I could use Wi-Fi at the house efficiently in conjunction with a AT&T 3G microcell. I was using AT&T's Internet access it was completely pathetic and inconsistent.


Let's keep each other posted on this forum.

iPhone 5S Springboard Crashes

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.