blocks|key|1257477|text|随同|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1257478|<action+android:name="android.intent.action.BOOT_COMPLETED"+/>++|code-block|syntax|javascript|1257479|也可以使用，|1257480|<action+android:name="android.intent.action.QUICKBOOT_POWERON"+/>|1257481|宏达电设备似乎没有赶上BOOT_COMPLETED|1257482|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Along with

<pre><code>&lt;action android:name="android.intent.action.BOOT_COMPLETED" /&gt; 
</code></pre>

also use,

<pre><code>&lt;action android:name="android.intent.action.QUICKBOOT_POWERON" /&gt;
</code></pre>

HTC devices dont seem to catch BOOT_COMPLETED

blocks|key|1257335|text|请注意，在问题的开头，有一个拼写错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1257336|<action+android:name="android.intent.action._BOOT_COMPLETED"/>|offset|length|style|CODE|1257337|而不是：|1257338|<action+android:name="android.intent.action.BOOT_COMPLETED"/>|1257339|一个小"_“和所有这些麻烦:)|1257340|entityMap^0|0|0|1Q|0|0|0|1P|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

note that at the beginning of the question, there is a typo mistake:

<code>&lt;action android:name="android.intent.action._BOOT_COMPLETED"/&gt;</code>

instead of :

<code>&lt;action android:name="android.intent.action.BOOT_COMPLETED"/&gt;</code>

one small "_" and all this trouble :)

blocks|key|1257277|text|我认为你的清单需要补充：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1257278|<uses-permission+android:name="android.permission.RECEIVE_BOOT_COMPLETED"+/>|code-block|syntax|javascript|1257279|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I think your manifest needs to add: 

<pre><code>&lt;uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" /&gt;
</code></pre>

blocks|key|1042406|text|我刚刚发现可能是因为Settings+>+Power中的Fast+Boot选项|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1042407|当我关闭此选项时，我的应用程序会收到this广播，但不会收到其他广播。|1042408|顺便说一下，我在HTC+Incredible+S上有Android+2.3.3。|1042409|希望能有所帮助。|1042410|entityMap^0|A|8|L|5|S|9|0|0|8|G|Q|D|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|M|$]]

I found out just now that it might be because of <code>Fast Boot</code> option in <code>Settings</code> > <code>Power</code>

When I have this option off, my application receives a this broadcast but not otherwise.

By the way, I have <code>Android 2.3.3</code> on <code>HTC Incredible S</code>.

Hope it helps.

blocks|key|1042251|text|我有一个额外的<category>-tag，不知道这是否有什么不同。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1042252|<receiver+android:name="BootIntentReceiver">++
++++++++<intent-filter>++
++++++++++++<action+android:name="android.intent.action.BOOT_COMPLETED"+/>++
++++++++++++<category+android:name="android.intent.category.HOME"+/>++
++++++++</intent-filter>++
</receiver>|code-block|syntax|javascript|1042253|您是否尝试过省略if子句"android.intent.action.BOOT_COMPLETED".equals(intent.getAction()，因为接收方可能只接收该意图？|1042254|entityMap^0|7|A|0|0|C|1S|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I have an additional <code>&lt;category&gt;</code>-tag, don't know if that makes any difference.

<pre><code>&lt;receiver android:name="BootIntentReceiver"&gt; 
 &lt;intent-filter&gt; 
 &lt;action android:name="android.intent.action.BOOT_COMPLETED" /&gt; 
 &lt;category android:name="android.intent.category.HOME" /&gt; 
 &lt;/intent-filter&gt; 
&lt;/receiver&gt;
</code></pre>

Have you tried ommiting the if-clause <code>"android.intent.action.BOOT_COMPLETED".equals(intent.getAction()</code>, as the receiver probably only receives that intent anyway?

blocks|key|1042645|text|请参阅此链接http://khurramitdeveloper.blogspot.in/2013/06/start-activity-or-service-on-boot.html分步过程，以使用启动服务|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1042646|entityMap|0|LINK|mutability|MUTABLE|url|http://khurramitdeveloper.blogspot.in/2013/06/start-activity-or-service-on-boot.html^0|6|2C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Refer This Link <a href="http://khurramitdeveloper.blogspot.in/2013/06/start-activity-or-service-on-boot.html" rel="nofollow">http://khurramitdeveloper.blogspot.in/2013/06/start-activity-or-service-on-boot.html</a>
Step by Step procedure to use boot on Service

blocks|key|1042816|text|在安装外部存储之前，BOOT_COMPLETE会被发送到execute.if你的应用被安装到外部存储，它将不会收到BOOT_COMPLETE广播消息。为了防止这种情况，您可以在内部存储中安装您的应用程序。您只需在menifest.xml中添加以下行即可完成此操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1042817|<manifest+xmlns:android="http://schemas.android.com/apk/res/android"
android:installLocation="internalOnly"
...+>|code-block|syntax|javascript|1042818|一些HTC设备可以启用“快速启动”功能，这种功能更像是深度休眠，而不是真正的重启，因此不应该给BOOT_COMPLETE提供意图。为了恢复这一点，你可以在你的接收器中添加这个意图过滤器：|1042819|++++++++++++<intent-filter>
++++++++++++++++<action+android:name="android.intent.action.BOOT_COMPLETED"+/>
++++++++++++++++<action+android:name="android.intent.action.QUICKBOOT_POWERON"+/>
++++++++++++</intent-filter>|1042820|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Before mounting external storage BOOT_COMPLETE is sent execute.if your app is installed to external storage it won't receive BOOT_COMPLETE broadcast message. To prevent this you can install your application in internal storage. you can do this just adding this line in menifest.xml

<pre><code>&lt;manifest xmlns:android="http://schemas.android.com/apk/res/android"
android:installLocation="internalOnly"
... &gt;
</code></pre>

Some HTC devices can enable a "fast boot" feature that is more like a deep hibernation and not a real reboot and therefore should not give the BOOT_COMPLETE intent. To recover this you can add this intent filter inside your receiver:

<pre><code> &lt;intent-filter&gt;
 &lt;action android:name="android.intent.action.BOOT_COMPLETED" /&gt;
 &lt;action android:name="android.intent.action.QUICKBOOT_POWERON" /&gt;
 &lt;/intent-filter&gt;
</code></pre>

blocks|key|1257718|text|正如@Damian评论的那样，这个帖子中的所有答案都做错了。像这样手动操作会冒着在设备进入休眠状态时服务在中途被停止的风险。您需要先获取唤醒锁。幸运的是，执行此操作的Support+library+gives+us+a+class：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1257719|public+class+SimpleWakefulReceiver+extends+WakefulBroadcastReceiver+{
++++@Override
++++public+void+onReceive(Context+context,+Intent+intent)+{
++++++++//+This+is+the+Intent+to+deliver+to+our+service.
++++++++Intent+service+=+new+Intent(context,+SimpleWakefulService.class);

++++++++//+Start+the+service,+keeping+the+device+awake+while+it+is+launching.
++++++++Log.i("SimpleWakefulReceiver",+"Starting+service+@+"+%2B+SystemClock.elapsedRealtime());
++++++++startWakefulService(context,+service);
++++}
}|code-block|syntax|javascript|1257720|然后，在你的服务中，确保释放唤醒锁：|1257721|++++@Override
++++protected+void+onHandleIntent(Intent+intent)+{
++++++++//+At+this+point+SimpleWakefulReceiver+is+still+holding+a+wake+lock
++++++++//+for+us.++We+can+do+whatever+we+need+to+here+and+then+tell+it+that
++++++++//+it+can+release+the+wakelock.

...
++++++++Log.i("SimpleWakefulReceiver",+"Completed+service+@+"+%2B+SystemClock.elapsedRealtime());
++++++++SimpleWakefulReceiver.completeWakefulIntent(intent);
++++}|1257722|别忘了在你的mainfest中添加WAKE_LOCK权限：|1257723|<uses-permission+android:name="android.permission.RECEIVE_BOOT_COMPLETED"+/>
<uses-permission+android:name="android.permission.WAKE_LOCK"+/>|1257724|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/reference/android/support/v4/content/WakefulBroadcastReceiver.html#completeWakefulIntent%2528android.content.Intent%2529^0|2B|W|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|C|$G|H]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

As @Damian commented, all the answers in this thread are doing it wrong. Doing it manually like this runs the risk of your Service being stopped in the middle from the device going to sleep. You need to obtain a wake lock first. Luckily, the <a href="https://developer.android.com/reference/android/support/v4/content/WakefulBroadcastReceiver.html#completeWakefulIntent%28android.content.Intent%29" rel="nofollow">Support library gives us a class</a> to do this:

<pre><code>public class SimpleWakefulReceiver extends WakefulBroadcastReceiver {
 @Override
 public void onReceive(Context context, Intent intent) {
 // This is the Intent to deliver to our service.
 Intent service = new Intent(context, SimpleWakefulService.class);

 // Start the service, keeping the device awake while it is launching.
 Log.i("SimpleWakefulReceiver", "Starting service @ " + SystemClock.elapsedRealtime());
 startWakefulService(context, service);
 }
}
</code></pre>

then, in your Service, make sure to release the wake lock:

<pre><code> @Override
 protected void onHandleIntent(Intent intent) {
 // At this point SimpleWakefulReceiver is still holding a wake lock
 // for us. We can do whatever we need to here and then tell it that
 // it can release the wakelock.

...
 Log.i("SimpleWakefulReceiver", "Completed service @ " + SystemClock.elapsedRealtime());
 SimpleWakefulReceiver.completeWakefulIntent(intent);
 }
</code></pre>

Don't forget to add the WAKE_LOCK permssion to your mainfest:

<pre><code>&lt;uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" /&gt;
&lt;uses-permission android:name="android.permission.WAKE_LOCK" /&gt;
</code></pre>

blocks|key|1257577|text|事实上，我不久前遇到了这个麻烦，而且它真的很容易修复，如果你设置了"android.intent.action.BOOT_COMPLETED"权限和意图过滤器，实际上你没有做错什么。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1257578|请注意，如果你在Android+4.X上，你必须在启动服务之前运行广播侦听器，这意味着，你必须首先添加一个活动，一旦你的广播接收器运行，你的应用程序应该会像你预期的那样运行，然而，在Android+4.X上，我还没有找到一种在没有任何活动的情况下启动服务的方法，我认为谷歌这样做是出于安全原因。|1257579|entityMap^0|X|12|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

In fact,I get into this trouble not long ago,and it's really really easy to fix,you actually do nothing wrong if you setup the <code>"android.intent.action.BOOT_COMPLETED"</code> permission and intent-filter.

Be attention that if you On Android 4.X,you have to run the broadcast listener before you start service on boot,that means,you have to add an activity first,once your broadcast receiver running,your app should function as you expected,however,on Android 4.X,I haven't found a way to start the service on boot without any activity,I think google did that for security reasons.

blocks|key|1042686|text|如果我把空的构造函数留在receiver类中，我就会遇到这个问题。移除空的contsructor后，onRreceive方法开始正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1042687|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I faced with this problem if i leave the empty constructor in the receiver class. After the removing the empty contsructor onRreceive methos started working fine.

I've been trying to start a service when a device boots up on android, but I cannot get it to work. I've looked at a number of links online but none of the code works. Am I forgetting something? 

<h3>AndroidManifest.xml</h3>

<pre><code>&lt;receiver
 android:name=".StartServiceAtBootReceiver"
 android:enabled="true"
 android:exported="false"
 android:label="StartServiceAtBootReceiver" &gt;
 &lt;intent-filter&gt;
 &lt;action android:name="android.intent.action._BOOT_COMPLETED" /&gt;
 &lt;/intent-filter&gt;
&lt;/receiver&gt;

&lt;service
 android:name="com.test.RunService"
 android:enabled="true" /&gt;
</code></pre>

<h3>BroadcastReceiver</h3>

<pre><code>public void onReceive(Context context, Intent intent) {
 if ("android.intent.action.BOOT_COMPLETED".equals(intent.getAction())) {
 Intent serviceLauncher = new Intent(context, RunService.class);
 context.startService(serviceLauncher);
 Log.v("TEST", "Service loaded at start");
 }
}
</code></pre>

Trying to start a service on boot on Android

我一直在尝试在android上启动设备时启动服务，但我无法让它工作。我已经在网上查看了许多链接，但没有一个代码能正常工作。我是不是忘了什么？AndroidManifest.xml<receiver android:name=".StartServiceAtBootReceiver" android:enabled="true" android:exported="false"

问尝试在Android上启动服务
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试在Android上启动服务EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问尝试在Android上启动服务
EN