Explicitly enable StrictMode VM policies.

Explicitly enable StrictMode VM policies.

Since StrictMode currently interprets intents from
ChromeLauncherActivity to view a file:// URI as exposing the URI,
even though it will be handled by Chrome anyways, this causes
false positive StrictMode violations.

This change explicitly specifies all the StrictMode VM policies
that we detect, and in so doing skip over the file URI exposed
detection. In the future when Android fixes this StrictMode
issue for multiprocess apps we can turn it back on.

BUG=508282
Committed: https://crrev.com/fa3cc2102b6d90e695319247cc21a733d87d062d
Cr-Commit-Position: refs/heads/master@{#340957}

[Peter Wen, 2015-07-29 13:48:00]

wnwen@chromium.org changed reviewers:
+ dtrainor@chromium.org

[Peter Wen, 2015-07-29 13:48:01]

Hi David,

This CL removes a StrictMode false positive by explicitly avoiding detecting
that type of violation. In the existing API it's not possible to temporarily
ignore it.

Thanks,

Peter

[David Trainor- moved to gerrit, 2015-07-29 18:15:12]

lgtm

[Peter Wen, 2015-07-29 18:54:17]

The CQ bit was checked by wnwen@chromium.org

[commit-bot: I haz the power, 2015-07-29 18:55:51]

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

[commit-bot: I haz the power, 2015-07-29 19:48:34]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-07-29 19:50:30]

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