Upstream Chrome for Android Cast.

chrome/android/shell/java/AndroidManifest.xml.jinja2

 <?xml version="1.0" encoding="utf-8"?>
 
 <!-- Copyright 2014 The Chromium Authors. All rights reserved.
 
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file.
  -->
 
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
     package="org.chromium.chrome.shell">
@@ skipping 47 matching lines @@
                 <action android:name="android.intent.action.VIEW" />
                 <category android:name="android.intent.category.DEFAULT" />
             </intent-filter>
         </activity>
         <activity android:theme="@style/PreferencesTheme"
                 android:name="org.chromium.chrome.shell.preferences.ChromeShellPreferences"
                 android:configChanges="orientation|keyboardHidden|keyboard|screenSize"
                 android:label="@string/preferences"
                 android:exported="false">
         </activity>
-
+        

[whywhat, 2015/03/13 19:25:48]

nit: Some unintended ws change?

[aberent, 2015/03/17 21:33:51]

Done.

         <!-- The following service entries exist in order to allow us to
              start more than one sandboxed process. -->
 
         <!-- NOTE: If you change the value of "android:process" for the below services,
              you also need to update kHelperProcessExecutableName in chrome_constants.cc. -->
         {% set num_sandboxed_services = 20 %}
         <meta-data android:name="org.chromium.content.browser.NUM_SANDBOXED_SERVICES"
                    android:value="{{ num_sandboxed_services }}"/>
         {% for i in range(num_sandboxed_services) %}
         <service android:name="org.chromium.content.app.SandboxedProcessService{{ i }}"
@@ skipping 106 matching lines @@
             <intent-filter>
                 <action android:name="android.accounts.LOGIN_ACCOUNTS_CHANGED" />
             </intent-filter>
         </receiver>
 
         <meta-data android:name="org.chromium.content.browser.SMART_CLIP_PROVIDER"
                    android:value="org.chromium.content.browser.SmartClipProvider" />
         <meta-data android:name="org.chromium.chrome.browser.SERVICE_TAB_LAUNCHER"
                    android:value="org.chromium.chrome.shell.ChromeShellServiceTabLauncher" />
 
+        <!-- Activity, service, and meta-data to support casting to Chromecast -->
+
+        <!-- Expanded controller activity is displayed when the Cast Notification is clicked -->
+        <activity android:name="org.chromium.chrome.browser.media.remote.ExpandedControllerActivity"
+            android:theme="@style/MainTheme"
+            android:label="Chrome.ExpandedControllerActivity"
+            android:hardwareAccelerated="true"
+            android:launchMode="singleTask"
+            android:noHistory="true"
+            android:configChanges="orientation|keyboardHidden|keyboard|screenSize"
+            android:excludeFromRecents="true">
+        </activity>
+
+        <service android:name="org.chromium.chrome.browser.media.remote.NotificationTransportControl$ListenerService" />
+
+        <!-- Media route controllers to use for remote playback (cast).
+             This is here, rather than in code, since it varies between upstream and downstream,
+             yet we need this list of classes in the notification service, which belongs upstream
+             and doesn't run the downstream Clank startup code. The Cast code will, for each media element,
+             choose the first MediaRouteController that can play it, so the order of the list can be important.
+             The most specific MediaRouteControllers should be listed first, followed by more generic ones -->
+        <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
+            android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
+
+
     </application>
 </manifest>