<service mindroid:enabled=["true" | "false"]
         mindroid:autostart=["true" | "false"] >
    . . .
contained in:
Declares a service (a Service subclass) as one of the application's components. Services are used to implement long-running background operations or a rich communications API that can be called by other applications.

All services must be represented by <service> elements in the manifest file. Any that are not declared there will not be seen by the system and will never be run.

Whether or not the service can be instantiated by the system — "true" if it can be, and "false" if not. The default value is "true".

The <application> element has its own enabled attribute that applies to all application components, including services. The <application> and <service> attributes must both be "true" (as they both are by default) for the service to be enabled. If either is "false", the service is disabled; it cannot be instantiated.

The name of the Service subclass that implements the service. This should be a fully qualified class name (such as, "com.example.project.ExampleService"). However, as a shorthand, if the first character of the name is a period (for example, ".ExampleService"), it is appended to the package name specified in the <manifest> element.

Once you publish your application, you should not change this name.

There is no default. The name must be specified.

The name of the process where the service is to run. Normally, all components of an application run in the default process created for the application. It has the same name as the application package. The <application> element's process attribute can set a different default for all components. But component can override the default with its own process attribute, allowing you to spread your application across multiple processes.
Whether or not the service will be automatically started by the system — "true" if it will be, and "false" if not. The default value is "false".