android-Small set up a permanent resolver problem that terminates abnormally because of an uncaught exception

(i) Preface
Dear Lunch shoes, are not often because of their own programs in the non-layer caught exception caused the program to terminate unexpectedly painful? Well, yes. However, we do not fear, today to share a dongdong can solve everyone this kind of distress, roar!

(ii) Uncaughtexceptionhandler interface
This interface, as the name implies, is the exception that is not handled in the handler, and it is the exception that caused the program to terminate when the system throws an abnormal! So, how do you use it in Android?

(c) How to use Uncaughtexceptionhandler
1. First, we have to create a specific class of uncaughtexceptionhandler, such as:

 Public classCrashhandlerImplementsUncaughtexceptionhandler {Private StaticCrashhandler instance;//Singleton Reference, here we make a singleton, because we only need a Uncaughtexceptionhandler instance in an application         PrivateCrashhandler () {} Public synchronized StaticCrashhandler getinstance () {//synchronization method to avoid exceptions in single-threaded environments         if(Instance = =NULL) {instance=NewCrashhandler (); }         returninstance; }          Public voidInit (Context ctx) {//Initialize, set the current object to the Uncaughtexceptionhandler processorThread.setdefaultuncaughtexceptionhandler ( This); } @Override Public voidUncaughtexception (thread thread, Throwable ex) {//when an unhandled exception occurs, you will come here. LOG.D ("Sandy", "uncaughtexception, Thread:" +Thread+ "Name:" + thread.getname () + "ID:" + thread.getid () + "Exception:" +ex); String ThreadName=Thread.getname (); if("Sub1". Equals (ThreadName)) {LOG.D ("Sandy", "" "xxx); }Else if(){                       //Here we can discriminate according to the thread name, and we can also write the exception information to the file for later analysis.                }     } }

2. Next, we customize the application class

 Public class extends Application {     @Override     publicvoid  onCreate () {         super . OnCreate ();          = crashhandler.getinstance ();          // set our exception processor to Uncaughtexceptionhandler processor in Appliction      } }

3. Configuring the Androidmanifest.xml File
Since we are using custom application, we want to declare it in the Androidmanifest.xml file

< Application          Android:icon = "@drawable/ic_launcher"          android:label= "@string/app_name"         android:name= ". Ourapplication "         android:debuggable=" true "         >

4. Testing
We start a thread in the activity and then throw an exception inside the thread to see what the program will do.

Button BTN =(Button) Findviewbyid (R.ID.BT); Btn.setonclicklistener (NewView.onclicklistener () {@Override Public voidOnClick (View v) {thread thread=NewThread (NewRunnable () {@Override Public voidrun () {LOG.D ("Sandy", "I am a sub thread"); String s=NULL;  S.tostring (); //Throw Nullpointexception                     }                 }, "Sub Thread"); Thread.Start (); }

5. Results
Because we have handlers for the default unhandled exception, the following log information is printed without throwing an exception causing the program to terminate abnormally
D/sandy (2228): I am a Sub thread
D/sandy (2228): Uncaughtexception, thread:thread[sub Thread,5,main] name:sub thread Id:148exception:java.lang.nul Lpointerexception

What are we waiting for? Quickly add the default unhandled exception handler in your application! There is no longer a program crash because of an uncaught exception: ^_^