See issue 692393 for discussion and more context. 

Currently we have an "arc mode" version of many chromeos tests that just wait for Android to be booted successfully and then run the test. This was decided when ARC++ was getting up and running initially. In theory, these tests shouldn't be affected by the container running since they don't have any interaction with the container once booted. 

It is not clear if this approach has found many meaningful bugs so we should do a couple things:

1. Investigate the failures of arc mode tests and see what kind of bugs they have produced.

2. If they are not finding bugs we can disable arc mode in these tests. This will make tests run a lot faster and waste less resources in the CQ/lab.

3. Create a good test(s) that see that ChromeOS is not adversely affected when Android is doing various things.