Android - myLooper() vs getMainLooper()

Question

Just clarifying but in an Android activity on MAIN Thread if I call Looper.myLooper() vs Looper.getMainLooper() the return the same reference, right? they are the same thing? I know I would never have to call these usually as Android takes care of this but I'd like to know how they differ when being called from the main thread?

if from the main thread I call

Looper.myLooper().quit(); // or Looper.getMainLooper().quit(); 

They both give the same runtime exception so I'm assuming they are the same reference:

Caused by: java.lang.RuntimeException: Main thread not allowed to quit.

can anyone confirm?

Answer 1

You have it described in the docs:

getMainLooper()

Returns the application's main looper, which lives in the main thread of the application.

myLooper()

Return the Looper object associated with the current thread. Returns null if the calling thread is not associated with a Looper.

As for whether getMainLooper() is of any use, I can assure you it really is. If you do some code on a background thread and want to execute code on the UI thread, e.g. update UI, use the following code:

new Handler(Looper.getMainLooper()).post(new Runnable() {   // execute code that must be run on UI thread }); 

Of course, there are other ways of achieving that.

Another use is, if you want to check if the currently executed code is running on the UI thread, e.g. you want to throw / assert:

boolean isUiThread = Looper.getMainLooper().getThread() == Thread.currentThread(); 

or

boolean isUiThread = Looper.getMainLooper().isCurrentThread(); 

Answer 2

Looper.getMainLooper() is convenience API to get looper which is attached to the main thread of the activity.It is usefull when you want to excute some code on main thread from a background thread.

It is usually used as follows:

new Handler(Looper.getMainLooper()).post(task); 

Looper.myLooper() is api to get looper attached to current thread