From 4b5da6829aa5e324f5e9414c25d132ba0a9ebeb3 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Thu, 21 Oct 2010 11:49:12 -0700 Subject: [PATCH] docs: fix a couple api links Change-Id: If0e35011a28dc87324e2d53e856cfcdb35236061 --- core/java/android/content/Context.java | 114 +++++++++++++------------ 1 file changed, 59 insertions(+), 55 deletions(-) diff --git a/core/java/android/content/Context.java b/core/java/android/content/Context.java index 0dd2e4a748786..75638312bdeee 100644 --- a/core/java/android/content/Context.java +++ b/core/java/android/content/Context.java @@ -80,7 +80,8 @@ public abstract class Context { /** * Flag for {@link #bindService}: automatically create the service as long * as the binding exists. Note that while this will create the service, - * its {@link android.app.Service#onStart} method will still only be called due to an + * its {@link android.app.Service#onStartCommand} + * method will still only be called due to an * explicit call to {@link #startService}. Even without that, though, * this still provides you with access to the service object while the * service is created. @@ -134,13 +135,13 @@ public abstract class Context { * services, etc). */ public abstract Looper getMainLooper(); - + /** * Return the context of the single, global Application object of the * current process. This generally should only be used if you need a * Context whose lifecycle is separate from the current context, that is * tied to the lifetime of the process rather than the current component. - * + * *

Consider for example how this interacts with * {@ #registerReceiver(BroadcastReceiver, IntentFilter)}: *