scsjc Well-Known Member Licensed User Longtime User Oct 25, 2018 #1 There is some way to prioritize the services that are loaded when you start the android. I have app that has a service to launch a radio through an intent and it takes a long time (2-3minutes) i use that in manifest to intent: B4X: AddReceiverText(a2dp, <intent-filter android:priority="2147483647"> <action android:name="android.bluetooth.device.action.ACL_DISCONNECTED" /> <action android:name="android.bluetooth.headset.profile.action.CONNECTION_STATE_CHANGED" /> </intent-filter> ) thanks
There is some way to prioritize the services that are loaded when you start the android. I have app that has a service to launch a radio through an intent and it takes a long time (2-3minutes) i use that in manifest to intent: B4X: AddReceiverText(a2dp, <intent-filter android:priority="2147483647"> <action android:name="android.bluetooth.device.action.ACL_DISCONNECTED" /> <action android:name="android.bluetooth.headset.profile.action.CONNECTION_STATE_CHANGED" /> </intent-filter> ) thanks
Erel B4X founder Staff member Licensed User Longtime User Oct 26, 2018 #2 I don't think that it is related to the priority. The BOOT_COMPLETED intent is only broadcasted after the system is fully up. Upvote 0
I don't think that it is related to the priority. The BOOT_COMPLETED intent is only broadcasted after the system is fully up.
scsjc Well-Known Member Licensed User Longtime User Oct 26, 2018 #3 Erel said: I don't think that it is related to the priority. The BOOT_COMPLETED intent is only broadcasted after the system is fully up. Click to expand... thanks Upvote 0
Erel said: I don't think that it is related to the priority. The BOOT_COMPLETED intent is only broadcasted after the system is fully up. Click to expand... thanks