Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 02b644fd authored by Harry Cutts's avatar Harry Cutts
Browse files

Fix typos and formatting in DeadObjectException JavaDoc 

Bug: n/a
Change-Id: I0ebdb6bb8d9bf2fed62978913711e0da9a6f097b
Test: Treehugger
Flag: EXEMPT JavaDoc change
parent 4c1803f8

core/java/android/os/DeadObjectException.java

+6 −4
Original line number Diff line number Diff line
@@ -26,7 +26,7 @@ import android.os.RemoteException; 
 * receive this error from an app, at a minimum, you should

 * recover by resetting the connection. For instance, you should

 * drop the binder, clean up associated state, and reset your

 * connection to the service which through this error. In order

 * connection to the service which threw this error. In order

 * to simplify your error recovery paths, you may also want to

 * "simply" restart your process. However, this may not be an

 * option if the service you are talking to is unreliable or
@@ -34,9 +34,11 @@ import android.os.RemoteException; 
 *

 * If this isn't from a service death and is instead from a

 * low-level binder error, it will be from:

 * - a oneway call queue filling up (too many oneway calls)

 * - from the binder buffer being filled up, so that the transaction

 * <ul>

 * <li> a one-way call queue filling up (too many one-way calls)

 * <li> from the binder buffer being filled up, so that the transaction

 *      is rejected.

 * </ul>

 *

 * In these cases, more information about the error will be

 * logged. However, there isn't a good way to differentiate