Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm sure this is it but I'm having difficulty with the details. </p> <p>Here's the existing code: </p> <pre><code>Mainfest for the main Application: &lt;application android:icon="@drawable/biosound_icon" android:label="@string/app_name" android:debuggable="true"&gt; &lt;service android:name="com.t2.biofeedback.BioFeedbackService"&gt; &lt;intent-filter&gt; &lt;action android:name="com.t2.biofeedback.IBioFeedbackService"/&gt; &lt;/intent-filter&gt; &lt;/service&gt; &lt;/application&gt; </code></pre> <p>The call to bind the service was in the library AndroidSpineServerLib</p> <pre><code>Intent intent2 = new Intent("com.t2.biofeedback.IBioFeedbackService"); bindService(intent2, mConnection, Context.BIND_AUTO_CREATE); </code></pre> <p>So I can see how the service was bound to a specific application</p> <p>To fix this I tried:</p> <pre><code>Intent intent2 = new Intent(this, BioFeedbackService.class); bindService(intent2, mConnection, Context.BIND_AUTO_CREATE); </code></pre> <p>The problem is that the service was not created. </p> <p>I also tried the following</p> <pre><code>In the manifest of the service: &lt;service android:class=".service.BioFeedbackService"&gt; &lt;intent-filter&gt; &lt;action android:name="com.t2.biofeedback.IBioFeedbackService"/&gt; &lt;/intent-filter&gt; &lt;/service&gt; And in the library where I bind the service: Intent intent2 = new Intent(); intent2.setAction("com.t2.biofeedback.IBioFeedbackService"); bindService(intent2, mConnection, Context.BIND_AUTO_CREATE); </code></pre> <p>Still no luck.</p> <p>Maybe I'm putting the service definition in the wrong manifest. Remember I have the following hierarchy</p> <pre><code>Main Application references: AndroidBTService (Library), which references AndroidSpineServerLib (Library) So I have 3 manifests and not sure which to update. </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload