As android terminal users, one of the worst things we suffer every day are those annoying windows that appear without warning and cause the application we are using to close unexpectedly leaving us with a bitter taste.
Today I would like to show to all readers some idea of why they occur, know his motives, how to mitigate its effects and how to fix (or contribute to its solution) effectively.
Android has 2 mechanisms "defense" so that the system is not blocked / damaged to a faulty application or a temporary event wild:
Why occurs:
Android applications perform a large number and variety of tasks, some of them (such as loading a series of images) leave the application in a state of "waiting" while running which is not ideal (for poor conceptualization Programmer because we are doing many things at once and terminal processor can not all, etc).
During this period, if the system detects that our restless fingers are fiddling the screen without receiving any response from the running application, or simply detects that the application takes too long in this state, we will display a message warning that the application does not respond properly and giving us two options: "Force Quit" or "Wait".
How to identify:
If ever you see this message, hit "Waiting" once. If you do not appear again, surely not a fault of the program, but at the end he came a little "hiccup" briefly and choked with many simultaneous tasks.
However, if after a few seconds after giving a "Wait" reappears, click "Force Quit" and reopen the application. Try to find / action performed by the application that shows us that warning again / option function.
How to fix:
Sometimes, however much you use an application, you will not have any problem, and suddenly one day the message will appear. This does not mean that your phone is damaged, or the application is defective. You can simply that chance has made a series of events on your phone that make the application in a given time, unresponsive for a few seconds occur.
However, if you can detect a pattern in your application that triggers this message (for example, whenever you press certain buttons in a certain order, or whenever you open the "X" option) you've found a small bug in the application.
Most application developers will be happy to send you a detallándoles email that pattern and the harmful effects it has for application in your phone.
FC (Force Close or Force Close):
Why occurs:
When the system detects an error not controloado by the developer in an application, we are shown a window with only one option: "Force Quit" (or 2 options if your terminal uses version 2.2 of android: "Force Quit" or "Send Report ").
In these cases we can not do anything else, the application will close inexorably due to this error.
How to identify:
Identify that a FC is simple, if we see that message and our application is closed, is that something is wrong. But, would you like to know why this error occurred? Perhaps knowing the reason, or at least making you an idea of the probable cause, feel less that "uncontrollable rage" suffering any user when your favorite application begins to fail in this way: the "LOG" (read below how to get them).
If you open a log you will see lots of information unintelligible priori. If you have some time and you want to investigate, look at that log the words "Exception" or "Error". They usually appear accompanied by many similar lines to this:
W / System.err (21873) at android.app.ActivityThread.performPauseActivity (ActivityThread.java:3149)
These lines are those that help the developer to fix turn your application, and usually the error usually appears at the beginning of these lines and be very descriptive: FileNotFoundException, OutOfMemoryError, NullPointerException ...
You see, an FC can be caused in many small things, so if you happen sometime, do not throw out the window terminal yet!
How to fix:
These errors can occur for any number of reasons, some of which are insurmountable until the application developer to correct it and release the update. But sometimes, a couple of quick tests can transform our "uncontrollable anger toward the developer" into a simple "mild mosqueo".
First attempt: Force detention and clean any "caches" of information
1- Go to the display settings of your terminal and find the "Applications" option
2-In "Applications" go to "Manage Applications"
3-Find the application that is causing you problems and open it (depending on the version of android we have in our terminal, different tabs will appear to select the downloaded applications that are running or all, or you might have to press " Menu "phone, choose" Filter "and select" All "to display)
4-Press the button "Force stop" to ensure that our application is closed and then the button "Clear Cache" (EYE, not to be confused with "Clear Data" !!!, cache are temporary data used by the application and that can be removed without further damage)
5-We return to open our application and repeat the steps taken to obtain the FC to see if that fixes.
Second attempt: Reinstall / delete data
Follow the same steps as in the first attempt but this time you press the "Clear Data" instead of "Clear Cache". This will leave your application as newly installed (yes, you will lose the data on your application, hence this is the second attempt and not the first).
If your application is not active the button "Clear Data", the remedy that remains is to uninstall and reinstall.
Third attempt: report error.
Although Android 2.2 (Froyo) messages FC are accompanied with a choice of "Report" Automatically error desrrollador, my experience as such has made me see that such reports often lack important details for the correct determination of the errors and possible ways to solve them. So I'm going to advise you that in these situations, realicéis the following steps:
1- Install a program that can read and review of "logs" system (I advise aLogcat, Bug reporter or Catlog, free in the Market)
2-When your favorite application will regale an FC, start the program manager logs.
3-Depending on the used application menu or by pressing a button have the option to send the log directly.
4-Tell developer (usually indicate a contact email on the tab of the application on the Market) indicating if possible your phone model, the version of android you use, and the steps you did in your application for the FC .
With these simple steps you will greatly contribute to the application to be fixed / improved, and costs the same to go to the Market and put "green" developer turn!
I hope this post has been helpful for those users hungry for knowledge and desire to improve their favorite apps!