Fwiw, you only need to use android:exported if you are communicating with it from another process. Also be aware this means *any* other application can poke your service in the same way.
On Thu, Nov 10, 2011 at 7:01 PM, Shaun Shirey <[email protected]>wrote: > Thanks everyone for the help, I managed to implement a communication > to the service using the intent. What I missed was having the intent- > filter android:exported=true option set in the manifest. > > Now I can communicate and pass data to the service using the > startService(..) method that streets of boston pointed out. Ideally, I > would still prefer a way to "bind" to the remote service and use aidl > (as this would minimize the intent filter handling I have to do within > the service), but it seems as though it cannot be done due to the life > cycle of the BroadcastReceiver. > > On Nov 10, 7:50 pm, Dianne Hackborn <[email protected]> wrote: > > If you just want to communicate with a service if it is already running, > > you can use this: > > > > http://developer.android.com/reference/android/content/BroadcastRecei.. > ., > > android.content.Intent) > > > > On Thu, Nov 10, 2011 at 3:06 PM, Shaun Shirey <[email protected] > >wrote: > > > > > > > > > I would love to do that, the only problem that I'm running into is > > > that I can't bind to the service (via a service connection). > > > > > The startService works fine but the bind won't work in a > > > broadcastreceiver object. If I can't bind to the service, I don't > > > believe there is a way to communicate with it? > > > > > On Nov 10, 9:17 am, Streets Of Boston <[email protected]> wrote: > > > > Use Intents. Put data in the Intent's 'extras'. > > > > Put this Intent in the startService call. The Service's > onStartCommand > > > will > > > > be called with this Intent and you can handle it there. > > > > > > Or you can define an AIDL that your service implements. Bind to the > > > service > > > > and communicate with the service through the methods defined in this > > > AIDL. > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to > [email protected] > > > To unsubscribe from this group, send email to > > > [email protected] > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
