Add OpenSL ES enable setting to AppRTCDemo (part 2)

Add OpenSL ES enable setting to AppRTCDemo (part 2).

It is now possible to enable OpenSL ES on devices that supports it.

Fix for https://codereview.webrtc.org/1449083002/

Committed: https://crrev.com/5c489c9d3e03e57a1c626928ff828b2118626983
Cr-Commit-Position: refs/heads/master@{#10678}

[henrika_webrtc, 2015-11-17 13:14:40]

Description was changed from

==========
Add OpenSL ES enable setting to AppRTCDemo (part 2)

BUG=
==========

to

==========
Add OpenSL ES enable setting to AppRTCDemo (part 2).

Fix for https://codereview.webrtc.org/1449083002/
==========

[henrika_webrtc, 2015-11-17 13:14:41]

henrika@webrtc.org changed reviewers:
+ glaznev@webrtc.org

[henrika_webrtc, 2015-11-17 13:18:59]

I think we have to do something like this to ensure that OpenSL ES can be
toggled on/off. The reason is that blacklistDeviceForOpenSLESUsageIsOverridden
is set to true at first call and can then never be set to false again. Hence, if
we ever start to override, we must keep overriding and can't expect default
behavior to kick in.

To summarize: by default we did always call
setBlacklistDeviceForOpenSLESUsage(true), and it would set
blacklistDeviceForOpenSLESUsageIsOverridden to true as well.

It means that 

private boolean isDeviceBlacklistedForOpenSLESUsage() {
    boolean blacklisted = blacklistDeviceForOpenSLESUsageIsOverridden ?
        blacklistDeviceForOpenSLESUsage :
        WebRtcAudioUtils.deviceIsBlacklistedForOpenSLESUsage();
    if (blacklisted) {
      Logging.e(TAG, Build.MODEL + " is blacklisted for OpenSL ES usage!");
    }
    return blacklisted;
  }

would always return blacklistDeviceForOpenSLESUsage and it was previously only
set when peerConnectionParameters.useOpenSLES was false.

[henrika_webrtc, 2015-11-17 13:19:56]

Description was changed from

==========
Add OpenSL ES enable setting to AppRTCDemo (part 2).

Fix for https://codereview.webrtc.org/1449083002/
==========

to

==========
Add OpenSL ES enable setting to AppRTCDemo (part 2).

It is now possible to enable OpenSL ES on devices that supports it.

Fix for https://codereview.webrtc.org/1449083002/
==========

[henrika_webrtc, 2015-11-17 13:22:39]

The CQ bit was checked by henrika@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2015-11-17 13:22:45]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1455563002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1455563002/1

[commit-bot: I haz the power, 2015-11-17 15:36:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-17 15:36:09]

Dry run: This issue passed the CQ dry run.

[AlexG, 2015-11-17 18:11:02]

lgtm

[AlexG, 2015-11-17 18:11:24]

The CQ bit was checked by glaznev@webrtc.org

[commit-bot: I haz the power, 2015-11-17 18:11:33]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1455563002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1455563002/1

[commit-bot: I haz the power, 2015-11-17 18:12:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-17 18:12:56]

Patchset 1 (id:??) landed as
https://crrev.com/5c489c9d3e03e57a1c626928ff828b2118626983
Cr-Commit-Position: refs/heads/master@{#10678}