[Android] A prototype of the interactive media notification.

chrome/android/java/AndroidManifest.xml

 <?xml version="1.0" encoding="utf-8"?>
 <!-- Copyright 2015 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. -->
 
 <!--
 Note: This is a jinja2 template, processed at build time into the final manifest.
 
 Blocks denoted with { % block some_name % }foo{ % endblock % } can be overridden
 by a child template that "extends" this file.
@@ skipping 569 matching lines @@
             </intent-filter>
         </receiver>
 
         <service android:name="org.chromium.chrome.browser.media.remote.NotificationTransportControl$ListenerService" />
 
         <!--  Receiver for lock screen input when casting -->
         <receiver android:name="org.chromium.chrome.browser.media.remote.LockScreenTransportControl$MediaButtonIntentReceiver"/>
 
         <service android:name="org.chromium.chrome.browser.media.MediaNotificationService"
             android:exported="false"/>
+        <service android:name="org.chromium.chrome.browser.media.ui.NotificationMediaPlaybackControls$ListenerService"
+            android:exported="false"/>
 
         <meta-data android:name="com.google.android.gms.version"
             android:value="@integer/google_play_services_version" />
 
         <meta-data android:name="org.chromium.content.browser.SMART_CLIP_PROVIDER"
             android:value="org.chromium.content.browser.SmartClipProvider"/>
         <meta-data android:name="org.chromium.components.service_tab_launcher.SERVICE_TAB_LAUNCHER"
                    android:value="org.chromium.chrome.browser.ChromeServiceTabLauncher" />
         
         {% block extra_application_definitions %}
 
         <!-- 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 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.
              The downstream manifest replaces this block, and hence replaces the list of media route
              controllers with its own list. -->
         <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
             android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
         
         {% endblock %}
     </application>
 </manifest>