From 0db54643c33be75a1162b6d4cd8ac5fe0b9492c6 Mon Sep 17 00:00:00 2001 From: "Rishikeshan Sulochana/Lavakumar (Work)" <92720632+ris-work@users.noreply.github.com> Date: Tue, 24 Sep 2024 20:30:55 +0530 Subject: [PATCH 1/6] [WIP] Update Service.xml Fix markup --- docs/xml/Android.App/Service.xml | 54 ++++++++++++++++---------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index dd306762b..cb5275a5c 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -57,39 +57,39 @@ as a standard implementation of Service that has its own thread where it schedules its work to be done. Topics covered here: - <ol> - <li>What is a Service?<li>Service Lifecycle<li>Permissions<li>Process Lifecycle<li>Local Service Sample<li>Remote Messenger Service Sample</ol> +
    +
  1. What is a Service?
  2. Service Lifecycle
  3. Permissions
  4. Process Lifecycle
  5. Local Service Sample
  6. Remote Messenger Service Sample
- <div class="special reference"> - <h3>Developer Guides</h3> +
+

Developer Guides

For a detailed discussion about how to create services, read the Services developer guide. - </div> +
- "WhatIsAService"><h3>What is a Service?</h3> + "WhatIsAService">

What is a Service?

Most confusion about the Service class actually revolves around what - it is <em>not</em>: - <ul> - <li> A Service is <b>not</b> a separate process. The Service object itself + it is not: + Thus a Service itself is actually very simple, providing two main features: - <ul> - <li>A facility for the application to tell the system <em>about</em> + When a Service component is actually created, for either of these reasons, all that the system actually does is instantiate the component and call its #onCreate and any other appropriate callbacks on the @@ -100,7 +100,7 @@ as a local Java object that you make direct method calls on (as illustrated by Local Service Sample), to providing a full remoteable interface using AIDL. - "ServiceLifecycle"><h3>Service Lifecycle</h3> + "ServiceLifecycle"

Service Lifecycle

 There are two reasons that a service can be run by the system. If someone calls android.content.Context#startService Context.startService() then the system will retrieve the service (creating it and calling its #onCreate method @@ -133,14 +133,14 @@ in aidl. A service can be both started and have connections bound to it. In such a case, the system will keep the service running as long as either it is - started <em>or</em> there are one or more connections to it with the + started or there are one or more connections to it with the android.content.Context#BIND_AUTO_CREATE Context.BIND_AUTO_CREATE flag. Once neither of these situations hold, the service's #onDestroy method is called and the service is effectively terminated. All cleanup (stopping threads, unregistering receivers) should be complete upon returning from onDestroy(). - "Permissions"><h3>Permissions</h3> + "Permissions">

Permissions

 Global access to a service can be enforced when it is declared in its manifest's android.R.styleable#AndroidManifestService &lt;service&gt; tag. By doing so, other applications will need to declare a corresponding @@ -165,32 +165,32 @@ See the Security and Permissions document for more information on permissions and security in general. - "ProcessLifecycle"><h3>Process Lifecycle</h3> + "ProcessLifecycle">

Process Lifecycle

 The Android system will attempt to keep the process hosting a service around as long as the service has been started or has clients bound to it. When running low on memory and needing to kill existing processes, the priority of a process hosting the service will be the higher of the following possibilities: - <ul> - <li> + Note this means that most of the time your service is running, it may be killed by the system if it is under heavy memory pressure. If this happens, the system will later try to restart the service. An important @@ -219,7 +219,7 @@ importance of the overall process beyond just the importance of the service itself. - "LocalServiceSample"><h3>Local Service Sample</h3> + "LocalServiceSample">

Local Service Sample

One of the most common uses of a Service is as a secondary component running alongside other parts of an application, in the same process as the rest of the components. All components of an .apk run in the same From 778575e64a6590a2e63bdbd9cdda0e67e0d2a4c3 Mon Sep 17 00:00:00 2001 From: "Rishikeshan Sulochana/Lavakumar (Work)" <92720632+ris-work@users.noreply.github.com> Date: Mon, 30 Sep 2024 04:05:39 +0530 Subject: [PATCH 2/6] Update Service.xml Fix more.... It's XML not HTML. --- docs/xml/Android.App/Service.xml | 34 ++++++++++++++++---------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index cb5275a5c..e47151a21 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -58,23 +58,23 @@ schedules its work to be done. Topics covered here:
    -
  1. What is a Service?
  2. Service Lifecycle
  3. Permissions
  4. Process Lifecycle
  5. Local Service Sample
  6. Remote Messenger Service Sample
+
  • What is a Service?
  • Service Lifecycle
  • Permissions
  • Process Lifecycle
  • Local Service Sample
  • Remote Messenger Service Sample
    • -

    Developer Guides

    +

    Developer Guides

     For a detailed discussion about how to create services, read the Services developer guide. - + - "WhatIsAService">

    What is a Service?

     + "WhatIsAService"

    What is a Service?

    Most confusion about the Service class actually revolves around what it is not: Thus a Service itself is actually very simple, providing two main features: When a Service component is actually created, for either of these reasons, all that the system actually does is instantiate the component @@ -140,7 +140,7 @@ and the service is effectively terminated. All cleanup (stopping threads, unregistering receivers) should be complete upon returning from onDestroy(). - "Permissions">

    Permissions

     + "Permissions"

    Permissions

    Global access to a service can be enforced when it is declared in its manifest's android.R.styleable#AndroidManifestService &lt;service&gt; tag. By doing so, other applications will need to declare a corresponding @@ -165,7 +165,7 @@ See the Security and Permissions document for more information on permissions and security in general. - "ProcessLifecycle">

    Process Lifecycle

     + "ProcessLifecycle"

    Process Lifecycle

     The Android system will attempt to keep the process hosting a service around as long as the service has been started or has clients bound to it. When running low on memory and needing to kill existing processes, the @@ -173,13 +173,13 @@ following possibilities: If the service is currently executing code in its #onCreate onCreate(), #onStartCommand onStartCommand(), or #onDestroy onDestroy() methods, then the hosting process will be a foreground process to ensure this code can execute without being killed. -
  • +
  • If the service has been started, then its hosting process is considered to be less important than any processes that are currently visible to the user on-screen, but more important than any process not visible. Because @@ -190,7 +190,7 @@ happen. In particular, long-running services will be increasingly likely to kill and are guaranteed to be killed (and restarted if appropriate) if they remain started long enough. -
  • +
  • If there are clients bound to the service, then the service's hosting process is never less important than the most important client. That is, if one of its clients is visible to the user, then the service itself is @@ -198,14 +198,14 @@ importance can be adjusted through Context#BIND_ABOVE_CLIENT, Context#BIND_ALLOW_OOM_MANAGEMENT, Context#BIND_WAIVE_PRIORITY, Context#BIND_IMPORTANT, and Context#BIND_ADJUST_WITH_ACTIVITY. -
  • +
  • A started service can use the #startForeground(int, Notification) API to put the service in a foreground state, where the system considers it to be something the user is actively aware of and thus not a candidate for killing when low on memory. (It is still theoretically possible for the service to be killed under extreme memory pressure from the current foreground application, but in practice this should not be a concern.) - + Note this means that most of the time your service is running, it may be killed by the system if it is under heavy memory pressure. If this happens, the system will later try to restart the service. An important @@ -219,7 +219,7 @@ importance of the overall process beyond just the importance of the service itself. - "LocalServiceSample">

    Local Service Sample

     + "LocalServiceSample"

    Local Service Sample

    One of the most common uses of a Service is as a secondary component running alongside other parts of an application, in the same process as the rest of the components. All components of an .apk run in the same @@ -231,7 +231,7 @@ An example of this use of a Service is shown here. First is the Service itself, publishing a custom class when bound: - { + Java documentation for android.app.Service. From eab5bba0e1dc9ebc593ddc39b172e7e711dd96b8 Mon Sep 17 00:00:00 2001 From: David Britch Date: Thu, 28 Nov 2024 11:53:11 +0000 Subject: [PATCH 3/6] Fix XML. --- docs/xml/Android.App/Service.xml | 224 +++++++++++++++---------------- 1 file changed, 110 insertions(+), 114 deletions(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index e47151a21..4405665ec 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -42,7 +42,7 @@ to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use. Each service class must have a corresponding - android.R.styleable#AndroidManifestService &lt;service&gt; + android.R.styleable#AndroidManifestService declaration in its package's AndroidManifest.xml. Services can be started with android.content.Context#startService Context.startService() and @@ -59,14 +59,14 @@ Topics covered here:
    1. What is a Service?
    2. Service Lifecycle
    3. Permissions
    4. Process Lifecycle
    5. Local Service Sample
    6. Remote Messenger Service Sample
    - +

    Developer Guides

     For a detailed discussion about how to create services, read the Services developer guide. - - "WhatIsAService"

    What is a Service?

    + +

    What is a Service?

     Most confusion about the Service class actually revolves around what it is not:
      @@ -100,7 +100,7 @@ as a local Java object that you make direct method calls on (as illustrated by Local Service Sample), to providing a full remoteable interface using AIDL. - "ServiceLifecycle"

      Service Lifecycle

       +

      Service Lifecycle

       There are two reasons that a service can be run by the system. If someone calls android.content.Context#startService Context.startService() then the system will retrieve the service (creating it and calling its #onCreate method @@ -138,13 +138,13 @@ flag. Once neither of these situations hold, the service's #onDestroy method is called and the service is effectively terminated. All cleanup (stopping threads, - unregistering receivers) should be complete upon returning from onDestroy(). - - "Permissions"

      Permissions

       + unregistering receivers) should be complete upon returning from onDestroy(). + +

      Permissions

       Global access to a service can be enforced when it is declared in its - manifest's android.R.styleable#AndroidManifestService &lt;service&gt; + manifest's android.R.styleable#AndroidManifestService tag. By doing so, other applications will need to declare a corresponding - android.R.styleable#AndroidManifestUsesPermission &lt;uses-permission&gt; + android.R.styleable#AndroidManifestUsesPermission element in their own manifest to be able to start, stop, or bind to the service. As of android.os.Build.VERSION_CODES#GINGERBREAD, when using @@ -163,49 +163,45 @@ #checkCallingPermission method before executing the implementation of that call. See the Security and Permissions - document for more information on permissions and security in general. - - "ProcessLifecycle"

      Process Lifecycle

       + document for more information on permissions and security in general. + +

      Process Lifecycle

       The Android system will attempt to keep the process hosting a service around as long as the service has been started or has clients bound to it. When running low on memory and needing to kill existing processes, the priority of a process hosting the service will be the higher of the - following possibilities: - + following possibilities: +
        -
      - If the service is currently executing code in its - #onCreate onCreate(), #onStartCommand onStartCommand(), - or #onDestroy onDestroy() methods, then the hosting process will - be a foreground process to ensure this code can execute without - being killed. -
    • - If the service has been started, then its hosting process is considered - to be less important than any processes that are currently visible to the - user on-screen, but more important than any process not visible. Because - only a few processes are generally visible to the user, this means that - the service should not be killed except in low memory conditions. However, since - the user is not directly aware of a background service, in that state it is - considered a valid candidate to kill, and you should be prepared for this to - happen. In particular, long-running services will be increasingly likely to - kill and are guaranteed to be killed (and restarted if appropriate) if they - remain started long enough. -
    • - If there are clients bound to the service, then the service's hosting - process is never less important than the most important client. That is, - if one of its clients is visible to the user, then the service itself is - considered to be visible. The way a client's importance impacts the service's - importance can be adjusted through Context#BIND_ABOVE_CLIENT, - Context#BIND_ALLOW_OOM_MANAGEMENT, Context#BIND_WAIVE_PRIORITY, - Context#BIND_IMPORTANT, and Context#BIND_ADJUST_WITH_ACTIVITY. -
    • - A started service can use the #startForeground(int, Notification) - API to put the service in a foreground state, where the system considers - it to be something the user is actively aware of and thus not a candidate - for killing when low on memory. (It is still theoretically possible for - the service to be killed under extreme memory pressure from the current - foreground application, but in practice this should not be a concern.) - +
    • If the service is currently executing code in its + #onCreate onCreate(), #onStartCommand onStartCommand(), + or #onDestroy onDestroy() methods, then the hosting process will + be a foreground process to ensure this code can execute without + being killed.
      • +
    • If the service has been started, then its hosting process is considered + to be less important than any processes that are currently visible to the + user on-screen, but more important than any process not visible. Because + only a few processes are generally visible to the user, this means that + the service should not be killed except in low memory conditions. However, since + the user is not directly aware of a background service, in that state it is + considered a valid candidate to kill, and you should be prepared for this to + happen. In particular, long-running services will be increasingly likely to + kill and are guaranteed to be killed (and restarted if appropriate) if they + remain started long enough.
      • +
    • If there are clients bound to the service, then the service's hosting + process is never less important than the most important client. That is, + if one of its clients is visible to the user, then the service itself is + considered to be visible. The way a client's importance impacts the service's + importance can be adjusted through Context#BIND_ABOVE_CLIENT, + Context#BIND_ALLOW_OOM_MANAGEMENT, Context#BIND_WAIVE_PRIORITY, + Context#BIND_IMPORTANT, and Context#BIND_ADJUST_WITH_ACTIVITY.
      • +
    • A started service can use the #startForeground(int, Notification) + API to put the service in a foreground state, where the system considers + it to be something the user is actively aware of and thus not a candidate + for killing when low on memory. (It is still theoretically possible for + the service to be killed under extreme memory pressure from the current + foreground application, but in practice this should not be a concern.)
      • +
    Note this means that most of the time your service is running, it may be killed by the system if it is under heavy memory pressure. If this happens, the system will later try to restart the service. An important @@ -218,8 +214,8 @@ (such as an android.app.Activity) can, of course, increase the importance of the overall process beyond just the importance of the service itself. - - "LocalServiceSample"

    Local Service Sample

     + +

    Local Service Sample

     One of the most common uses of a Service is as a secondary component running alongside other parts of an application, in the same process as the rest of the components. All components of an .apk run in the same @@ -230,7 +226,7 @@ receive from it to a concrete class published by the service. An example of this use of a Service is shown here. First is the Service itself, publishing a custom class when bound: - + @@ -238,9 +234,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -324,9 +320,9 @@     - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -376,9 +372,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -428,9 +424,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -497,10 +493,10 @@ Context.bindService. Note that any extras that were included with the Intent at that point will <em>not</em> be seen here. Return the communication channel to the service. - Return an IBinder through which clients can call on to the + Return an IBinder through which clients can call on to the service. - Return the communication channel to the service. May return null if + Return the communication channel to the service. May return null if clients can not bind to the service. The returned android.os.IBinder is usually for a complex interface that has been described using @@ -516,9 +512,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -590,9 +586,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -631,9 +627,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -712,9 +708,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -759,9 +755,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -805,27 +801,27 @@ - The Intent supplied to android.content.Context#startService, + The Intent supplied to android.content.Context#startService, as given. This may be null if the service is being restarted after its process has gone away, and it had previously returned anything except #START_STICKY_COMPATIBILITY. Additional data about this start request. - A unique integer representing this specific request to + A unique integer representing this specific request to start. Use with #stopSelfResult(int). - Called by the system every time a client explicitly starts the service by calling - android.content.Context#startService, providing the arguments it supplied and a + Called by the system every time a client explicitly starts the service by calling + android.content.Context#startService, providing the arguments it supplied and a unique integer token representing the start request. The return value indicates what semantics the system should use for the service's current started state. It may be one of the constants associated with the #START_CONTINUATION_MASK bits. - Called by the system every time a client explicitly starts the service by calling - android.content.Context#startService, providing the arguments it supplied and a + Called by the system every time a client explicitly starts the service by calling + android.content.Context#startService, providing the arguments it supplied and a unique integer token representing the start request. Do not call this method directly. For backwards compatibility, the default implementation calls #onStart and returns either #START_STICKY or #START_STICKY_COMPATIBILITY. - + <p class="caution">Note that the system calls this on your service's main thread. A service's main thread is the same thread where UI operations take place for Activities running in the @@ -839,9 +835,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -887,9 +883,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -948,9 +944,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1044,9 +1040,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1094,9 +1090,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1165,7 +1161,7 @@ for more details. </div> - + <div class="caution"> <strong>Note:</strong> Beginning with SDK Version android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE, @@ -1185,9 +1181,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1262,7 +1258,7 @@ for more details. </div> - + <div class="caution"> <strong>Note:</strong> Beginning with SDK Version android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE, @@ -1283,9 +1279,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1351,9 +1347,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1400,9 +1396,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1450,9 +1446,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1499,9 +1495,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1546,9 +1542,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1584,9 +1580,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1626,9 +1622,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. @@ -1659,14 +1655,14 @@ The most recent start identifier received in #onStart. - Stop the service if the most recent time it was started was + Stop the service if the most recent time it was started was <var>startId</var>. Returns true if the startId matches the last start request and the service will be stopped, else false. - Stop the service if the most recent time it was started was - <var>startId</var>. This is the same as calling android.content.Context#stopService for this particular service but allows you to - safely avoid stopping if there is a start request from a client that you + Stop the service if the most recent time it was started was + <var>startId</var>. This is the same as calling android.content.Context#stopService for this particular service but allows you to + safely avoid stopping if there is a start request from a client that you haven't yet seen in #onStart. <em>Be careful about ordering of your calls to this function.</em>. If you call this function with the most-recently received ID before @@ -1680,9 +1676,9 @@ - Portions of this page are modifications based on work created and shared by the + Portions of this page are modifications based on work created and shared by the Android Open Source Project - and used according to terms described in the + and used according to terms described in the Creative Commons 2.5 Attribution License. From 4ef28955c026cce1e6bdddb00acd81580dd6ee16 Mon Sep 17 00:00:00 2001 From: David Britch Date: Fri, 29 Nov 2024 10:37:02 +0000 Subject: [PATCH 4/6] Restore escaped <>. --- docs/xml/Android.App/Service.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index 4405665ec..f38d7bb8a 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -42,7 +42,7 @@ to perform a longer-running operation while not interacting with the user or to supply functionality for other applications to use. Each service class must have a corresponding - android.R.styleable#AndroidManifestService + android.R.styleable#AndroidManifestService &lt;service&gt; declaration in its package's AndroidManifest.xml. Services can be started with android.content.Context#startService Context.startService() and @@ -142,7 +142,7 @@

    Permissions

     Global access to a service can be enforced when it is declared in its - manifest's android.R.styleable#AndroidManifestService + manifest's android.R.styleable#AndroidManifestService &lt;service&gt; tag. By doing so, other applications will need to declare a corresponding android.R.styleable#AndroidManifestUsesPermission element in their own manifest to be able to start, stop, or bind to From 054f3787c8a1b6d116548ede3820dc299e2c0670 Mon Sep 17 00:00:00 2001 From: David Britch Date: Fri, 29 Nov 2024 10:43:13 +0000 Subject: [PATCH 5/6] Another fix. --- docs/xml/Android.App/Service.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index f38d7bb8a..096869cad 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -144,7 +144,7 @@ Global access to a service can be enforced when it is declared in its manifest's android.R.styleable#AndroidManifestService &lt;service&gt; tag. By doing so, other applications will need to declare a corresponding - android.R.styleable#AndroidManifestUsesPermission + android.R.styleable#AndroidManifestUsesPermission &lt;uses-permission&gt; element in their own manifest to be able to start, stop, or bind to the service. As of android.os.Build.VERSION_CODES#GINGERBREAD, when using From 9d8f44ee1fd3ac9d8a9b27ae4bfde429329a1037 Mon Sep 17 00:00:00 2001 From: David Britch Date: Fri, 29 Nov 2024 10:48:54 +0000 Subject: [PATCH 6/6] Another fix. --- docs/xml/Android.App/Service.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/xml/Android.App/Service.xml b/docs/xml/Android.App/Service.xml index 096869cad..d873ce358 100644 --- a/docs/xml/Android.App/Service.xml +++ b/docs/xml/Android.App/Service.xml @@ -213,7 +213,7 @@ Other application components running in the same process as the service (such as an android.app.Activity) can, of course, increase the importance of the overall - process beyond just the importance of the service itself. + process beyond just the importance of the service itself.

    Local Service Sample

     One of the most common uses of a Service is as a secondary component