android 启动service报错,[Android L]关于Android L的Service启动问题

一 问题描写叙述

Android L[Android5.X.X] 版本号通过Intent隐式启动service时将会报出下面错误：

AndroidRuntime(  792): java.lang.IllegalArgumentException: Service Intent must be explicit

具体信息：

01-02 07:52:44.736 D/PowerManagerService/SmartStandby(  792): sendDetectFaceIntent:com.wtk.smart.standby.DETECT_FACE_ACTION

01-02 07:52:44.738 W/ContextImpl(  792): Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1813 com.android.server.power.PowerManagerService.sendDetectFaceIntent:4155 com.android.server.power.PowerManagerService.handleDetectFaceCase:4137 com.android.server.power.PowerManagerService.access$4400:100 com.android.server.power.PowerManagerService$PowerManagerHandler.handleMessage:3306

01-02 07:52:44.744 E/AndroidRuntime(  792): *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService

01-02 07:52:44.744 E/AndroidRuntime(  792): java.lang.IllegalArgumentException: Service Intent must be explicit: Intent { act=com.wtk.smart.standby.DETECT_FACE_ACTION (has extras) }

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.app.ContextImpl.validateServiceIntent(ContextImpl.java:1801)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1830)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.app.ContextImpl.startService(ContextImpl.java:1814)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at com.android.server.power.PowerManagerService.sendDetectFaceIntent(PowerManagerService.java:4155)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at com.android.server.power.PowerManagerService.handleDetectFaceCase(PowerManagerService.java:4137)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at com.android.server.power.PowerManagerService.access$4400(PowerManagerService.java:100)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at com.android.server.power.PowerManagerService$PowerManagerHandler.handleMessage(PowerManagerService.java:3306)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.os.Handler.dispatchMessage(Handler.java:111)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.os.Looper.loop(Looper.java:194)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at android.os.HandlerThread.run(HandlerThread.java:61)

01-02 07:52:44.744 E/AndroidRuntime(  792):  at com.android.server.ServiceThread.run(ServiceThread.java:46)

01-02 07:52:44.752 V/SettingsProvider(  792): call(global:dropbox:system_server_crash) for 0

01-02 07:52:44.753 D/SettingsProvider(  792): lookupValue table global cache.fullyMatchesDisk() dropbox:system_server_crash

01-02 07:52:44.757 V/SettingsProvider(  792): call(global:logcat_for_system_server_crash) for 0

01-02 07:52:44.757 D/SettingsProvider(  792): lookupValue table global cache.fullyMatchesDisk() logcat_for_system_server_crash

二 问题分析

A . 定位问题点

sdk\sources\android-21\android\app\ContextImpl.java

class ContextImpl extends Context {

……

private void validateServiceIntent(Intent service) {

if (service.getComponent() == null && service.getPackage() == null) {

if (getApplicationInfo().targetSdkVersion >= Build.VERSION_CODES.LOLLIPOP) {

IllegalArgumentException ex = new IllegalArgumentException(

“Service Intent must be explicit: ” + service);

throw ex;

} else {

Log.w(TAG, “Implicit intents with startService are not safe: ” + service

+ ” ” + Debug.getCallers(2, 3));

}

}

}

……

}

B .分析过程

上面源代码中蓝色加粗部分：service.getComponent() == null && service.getPackage() == null

表明通过intent启动service时， 须要指定Intent的ComponentName信息：intent.setComponent(xxx)，或指定Intent的setPackage(“包名”)，假设两者都没有指定的话将会报以上错误。尤其在framework层启动APP层的service时。假设是隐式启动service，可能会导致系统进程挂掉。出现不断重新启动的现象。

三 解决方法

參考一

Intent intent = new Intent();

ComponentName componentName = new ComponentName(pkgName,serviceName);

intent.setComponent(componentName);

context.startService(intent);

參考二

Intent mIntent = new Intent();

mIntent.setAction(“XXX.XXX.XXX”);//Service可以匹配的Action

mIntent.setPackage(pkgName);//应用的包名

context.startService(mIntent);

四 延伸官网

Binding to a Service

The Context.bindService() method now requires an explicit Intent, and throws an exception if given an implicit intent. To ensure your app is secure, use an explicit intent when starting or binding your Service, and do not declare intent filters for the service.

也就是说。在5.0以后不同意使用隐式Intent方式来启动Service