Use Chromium's Logging instead of Android's Logging for media files

media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java

Index: media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java
diff --git a/media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java b/media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java
index 21def1fd9fd75b1d6bd058404a3e9ca5acab4dd9..ba470fd526dbce3f378ec8417394aded436e5b83 100644
--- a/media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java
+++ b/media/base/android/java/src/org/chromium/media/VideoCaptureAndroid.java
@@ -6,7 +6,8 @@ package org.chromium.media;
 
 import android.content.Context;
 import android.graphics.ImageFormat;
-import android.util.Log;
+
+import org.chromium.base.Log;
 
 import java.util.ArrayList;
 import java.util.List;
@@ -41,7 +42,7 @@ public class VideoCaptureAndroid extends VideoCaptureCamera {
 
     private int mExpectedFrameSize;
     private static final int NUM_CAPTURE_BUFFERS = 3;
-    private static final String TAG = "VideoCaptureAndroid";
+    private static final String TAG = "cr.media";
 
     static int getNumberOfCameras() {
         return android.hardware.Camera.getNumberOfCameras();
@@ -67,7 +68,7 @@ public class VideoCaptureAndroid extends VideoCaptureCamera {
         try {
             camera = android.hardware.Camera.open(id);
         } catch (RuntimeException ex) {
-            Log.e(TAG, "Camera.open: " + ex);
+            Log.e(TAG, "Camera.open: ", ex);

[jdduke (slow), 2015/06/25 16:34:03]

Are we missing a %s here?

[dgn, 2015/06/25 16:46:09]

Depends on what we want to do. Currently it should output something like

E/TAG: Camera.open:
E/TAG: Exception: exception message
E/TAG:    at ...trace...

So the exception is not lost here.

Adding %s should get us

E/TAG: Camera.open: exception message
E/TAG: Exception: exception message
E/TAG:    at ...trace...

Using ex.getMessage() would remove the stack trace.

If you noticed a different behaviour then I have a bug somewhere...

[jdduke (slow), 2015/06/25 16:53:12]

Oh nevermind, I guess format just appends the stringified exception?

[dgn, 2015/06/25 17:02:56]

Well, Throwables have a special handling when they are the last argument of the
call. They are always forwarded to the variant of the framework's log function
that prints the stack trace. So they can't be lost.

Then for the formatting of the log message itself, it takes as many objects from
the arguments as there are placeholders. Since there is none here, message
formatting ignores the exception. With a %s added, it would call
String.valueOf(ex) or something similar, yes.

             return null;
         }
         android.hardware.Camera.Parameters parameters = getCameraParameters(camera);