commit 33b6729930a10ddd784b7bb2e8c2e6509c54ef54
author Tyler Gunn <tgunn@google.com> Mon Apr 27 15:41:35 2015 -0700
committer Tyler Gunn <tgunn@google.com> Tue Apr 28 08:31:12 2015 -0700
tree f259743661fa451e51372a98fec696ac8673daf1
parent 51d0dfa37b075f0f5692784e7f8f5839ad5b7221

Intent handling fixes for TestInCallService and TestCallActivity.

I had added the android:process to the TestCallActivity section in the
manifest.  This made my test intent work, but broke the intents in the
TestCallActivity which communicated back to the TestConnectionService.

Correctected this by adding a new BroadcastReceiver which is used to handle
intents for the TestInCallService.

Change-Id: I665b381a5519b0a1ddac39f580ce6482615dcffa

testapps/AndroidManifest.xml

diff --git a/testapps/AndroidManifest.xml b/testapps/AndroidManifest.xml
index 3483391..5a24799 100644
--- a/testapps/AndroidManifest.xml
+++ b/testapps/AndroidManifest.xml
@@ -53,10 +53,16 @@
             </intent-filter>
         </service>
 
+        <receiver android:name="com.android.server.telecom.testapps.TestInCallServiceBroadcastReceiver"
+                 android:process="com.android.server.telecom.testapps.TestInCallService" >
+            <intent-filter>
+                <action android:name="android.server.telecom.testapps.ACTION_SEND_UPDATE_REQUEST_FROM_TEST_INCALL_SERVICE"/>
+            </intent-filter>
+        </receiver>
+
         <activity android:name="com.android.server.telecom.testapps.TestCallActivity"
                   android:theme="@android:style/Theme.NoDisplay"
-                  android:label="@string/testCallActivityLabel"
-                  android:process="com.android.server.telecom.testapps.TestInCallService">
+                  android:label="@string/testCallActivityLabel">
             <intent-filter>
                 <action android:name="android.intent.action.MAIN" />
                 <category android:name="android.intent.category.DEFAULT" />