Add Galaxy S4 into GPU blacklist

gpu/config/software_rendering_list_json.cc

Index: gpu/config/software_rendering_list_json.cc
diff --git a/gpu/config/software_rendering_list_json.cc b/gpu/config/software_rendering_list_json.cc
index 08d100fb1f051f9175945434486d3cf69b850d5c..9af369460ad0d250a5d6503e1507030596eb7c7b 100644
--- a/gpu/config/software_rendering_list_json.cc
+++ b/gpu/config/software_rendering_list_json.cc
@@ -18,7 +18,7 @@ const char kSoftwareRenderingListJson[] = LONG_STRING_CONST(
 {
   "name": "software rendering list",
   // Please update the version number whenever you change this file.
-  "version": "6.19",
+  "version": "6.20",
   "entries": [
     {
       "id": 1,
@@ -1003,6 +1003,23 @@ LONG_STRING_CONST(
       "features": [
         "all"
       ]
+    },
+    {
+      "id": 85,
+      "description": "Samsung Gaxlaxy S4 is too buggy to use for video decoding",

[Ami GONE FROM CHROMIUM, 2014/01/07 00:50:01]

typo: s/Gaxlaxy/Galaxy/

+      "cr_bugs": [329072],

[Ami GONE FROM CHROMIUM, 2014/01/07 00:50:01]

I looked for evidence of VDA crash in the logs attached to that bug but failed
to find it (instead, all the logcat outputs I see have the main buffer _already_
spewing logs implying a failed decoder, but the actual failure is already gone).
 Would you mind updating the bug to highlight the crash that this blacklist is
working around?

+      "os": {
+        "type": "android"
+      },
+      "machine_model": {
+        "name": {
+          "op": "=",
+          "value": "SCH-I545"
+        }
+      },
+      "features": [
+        "accelerated_video_decode"
+      ]
     }
   ]
 }