Enable some webrtc content_browsertests on Android.

Enable some webrtc content_browsertests on Android.

To prevent crashes, it's needed to use ISAC/16000 on Android.

BUG=181069

[wjia(left Chromium), 2013-12-18 05:35:23]

Please review cc and html files. I will clean up the txt file when it's
finalized. 

It seems WebrtcBrowserTest.CanSetupVideoCall and
WebrtcBrowserTest.NegotiateUnsupportedVideoCodec were timed out. But they are ok
on my local machine. I will take closer look tomorrow.

[phoglund_chromium, 2013-12-18 11:25:52]

On 2013/12/18 05:35:23, wjia wrote:
> Please review cc and html files. I will clean up the txt file when it's
> finalized. 
> 
> It seems WebrtcBrowserTest.CanSetupVideoCall and
> WebrtcBrowserTest.NegotiateUnsupportedVideoCodec were timed out. But they are
ok
> on my local machine. I will take closer look tomorrow.

Sorry, I didn't mention I had a patch that would enable all the content
browsertests: https://codereview.chromium.org/118163002/. I didn't put it up for
review yet though while I tried to figure out why content browsertests are still
failing on the Chromium bots. My patch solves the same problem in a more general
way and cleans up the tests as well, so I suggest we go with that instead. I'll
grab your _disabled file and put into my patch. WDYT?

[phoglund_chromium, 2013-12-18 11:27:53]

> It seems WebrtcBrowserTest.CanSetupVideoCall and
> WebrtcBrowserTest.NegotiateUnsupportedVideoCodec were timed out. But they are
ok
> on my local machine. I will take closer look tomorrow.

Yes. My new audio tests have been running for a while on the chromium bots, and
they often crash, often timeout, and sometimes succeed. There are some general
problems that could even be for the browser test binary in general. I'm also
looking into this, so let's keep in touch where our investigations lead. I think
we can get away with enabling more tests for now to get more data points on the
bots, so I think it might be a good idea to enable the tests you suggest here
and see what sticks.