iPhone 5s crashing infrequently, despite restoring

Solution 1:

I would absolutely recommend a genius bar appointment if it's convenient and they can be sure your phone is reporting these crashes to Apple Engineering. That being said, you have a totally normal volume of logs and glitches for a new OS release that hasn't had time to have all these little bugs patched.

Of the messages you listed, these are harmless and diagnostic whether you have an app crash or not:

• awdd-YYYY-mm-dd-hhmmss-whatever-else
• log-aggregated-YYYY-mm-dd-hhmmss-whatever-else
• LowMemory-YYYY-mm-dd-hhmmss-whatever-else

Your phone is set up report each crash anonymously (they strip the identifier of the device from the reports intentionally) and the genius bar will ensure you are reporting these so that Engineering can make sure the most common crashes get sorted out.

The other benefit of the genius bar is they can run hardware diagnostics. You can also get these to run by seeking phone or web support in many areas:

• http://www.apple.com/support/iphone/contact/

Click the link that says you can get connected with an expert online.

Now, if you can't get to the genius bar, I can also say that they won't likely be able to dig into any of the crash logs other than perhaps the LowBattery log and LowMemory log and they will just look at them with you. You can look at them and figure out mostly what is going by reading the english descriptions and ignoring most of the hex (0x2f8107c6) and UUID (3A197A6D-1D9B-4F1D-BE12-356F8D3F3C2B).

LowBattery logs are how Apple (and the astute user) can tell if the battery needs replacing or if the programs are just using too much power in the background. LowMemory logs are just diagnostic - kind of like keeping your weight so that you can look back and tell when you were gaining, when you were holding steady and when you were losing.

These logs make the most sense when you track them over time and not so much that you have one now to 13 at this point.