Does iOS 7 fail you often? Detect the cause of the crash with this trick

iOS-7-1 (Copy)

By now we all know that iOS 7 brings many good things and other bad things to Apple's mobile operating system. There are many changes that have been introduced and also, the transition to 64-bit architectures complicates things even more if we talk about fix possible bugs on multiple devices.

Since the arrival of iOS 7, there are four updates that Apple has officially sent us. In all of them, the response time has been improved and the number of bugs has been minimized, although there are still quite a few to fix. iOS 7.1 could be the definitive solution to these failures but if we heed the latest rumors, the firmware might not arrive until next March.

Until the final version of iOS 7.1 is available, the bugs will be part of our day to day and although they are rare, there they are. In my case, WhatsApp causes my iPhone to restart every 3 or 4 days and it is something that has never happened to me before (I do not have a jailbreak). These failures are registered by the system and we all have access to them, something very useful to close the circle and find out first-hand the reason that is causing hangs and reboots in iOS 7.

For access this log panel You just have to go to the menu Settings> General> Information> Diagnosis and use (it is at the bottom)> Diagnosis and use data. There will appear the last times that your iOS device has suffered a problem and its cause.

More information - iOS 7.1 may not arrive until March


AirDrop for Windows, the best alternative
You are interested in:
How to use AirDrop on Windows PC
Follow us on Google News

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: AB Internet Networks 2008 SL
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Talion said

    It is useful to know which application may be causing a failure, the bad thing is that when they are an app that one uses a lot or has paid for them, uninstalling them is not usually an option and it only remains to wait for them to update them, although it is not bad to know which one it is. the app that crashes, at least one has the option to decide whether to keep it or temporarily remove it from the iphone / ipod or ipad. 😉

  2.   Solomon said

    Yes ... and how do I know where it was reset in both registration?

  3.   Daniel said

    Mnda cut article ... From here to detect the cause there is a warning. Please .. less quantity and more quality in the articles.

  4.   Talion said

    The truth is that detecting the program that causes an error is very simple, it is easy since it shows the date of the log and the program that causes the exception in the log, with a name and path. That you CANNOT solve the problem without uninstalling the app is another thing, but at least it gives you the chance to uninstall the app that causes the conflict if you want to. I don't think the article is bad, I have been able to detect the problem caused by certain apps in the past using this procedure and it has no difficulty. (As I said, the only problem is that you can only uninstall the app to solve the problem or wait for the app to be updated to correct the issue)

  5.   Alex said

    I have an Iphone 5 IOS 7.0.4, without Jail always. And every now and then it gets to 25% or 15% or whatever figure without being 1% and it just turns off. If I try to turn it on immediately, I get like I have no battery. I wait a while and it turns on and the battery appears as it was before it turned off and then it continues without problem or it turns off again.
    I have read in the Apple Community that it seems to be the Ios and the battery that they bring

    https://discussions.apple.com/thread/5515027?start=0&tstart=0