title: binding Service using AIDL vs binding using action?
body: <p>According <a href="http://developer.android.com/guide/components/aidl.html#Calling" rel="nofollow">documentaion</a> on Developer's forum, this is how I can bind my service using AIDL:</p>
  
  <pre><code>/* Establish a couple connections with the service, binding by interface names.This allows  other  applications to be installed that replace the remote service by implementingthe same  interface.*/
  
  bindService(new Intent(IRemoteService.class.getName()),mConnection, Context.BIND_AUTO_CREATE);
  </code></pre>
  
  <p>Now I have application A,  which has Service class and AIDL interfaces.</p>
  
  <p>And I have application B through which I wish to access Service class of Application A , using methods exposed ny AIDL in application A.</p>
  
  <p>So I have created exactly same pacakge for AIDLs inside application B and have pasted AIDLs from App A.</p>
  
  <p>But when I'm trying to bind service using above mechanism mentioned in documentation it tells me:</p>
  
  <blockquote>
    <p>Unable to start service Intent { act com.example.service.MyService
    } U=0: not found</p>
  </blockquote>
  
  <p>In App A Service </p>
  
  <blockquote>
    <p>exported="true". </p>
  </blockquote>
  
  <p>Now Insted of this approach I added Intent Filter to my service in app A and tried to specify explicit intent using </p>
  
  <pre><code>intent.setClassName(String packageName, String className)
  </code></pre>
  
  <p>And now it is working!</p>
  
  <p>So is there something I missed out while referring original documentation ? when that approached will be used?</p>