Initialization of audio manager for Android is now done on the audio thread

content/browser/renderer_host/render_message_filter.cc

Index: content/browser/renderer_host/render_message_filter.cc
diff --git a/content/browser/renderer_host/render_message_filter.cc b/content/browser/renderer_host/render_message_filter.cc
index 6a436e23b1e67c06d2be2050bb5d76a36b2f05a9..16a305dcfa3b7b8f22879a6bb3556091686f3651 100644
--- a/content/browser/renderer_host/render_message_filter.cc
+++ b/content/browser/renderer_host/render_message_filter.cc
@@ -469,11 +469,9 @@ base::TaskRunner* RenderMessageFilter::OverrideTaskRunnerForMessage(
   if (message.type() == ViewHostMsg_GetMonitorColorProfile::ID)
     return BrowserThread::GetBlockingPool();
 #endif
-#if defined(OS_MACOSX)
-  // OSX CoreAudio calls must all happen on the main thread.
+  // Always query audio device parameters on the audio thread.
   if (message.type() == ViewHostMsg_GetAudioHardwareConfig::ID)
     return audio_manager_->GetTaskRunner().get();
-#endif
   return NULL;
 }