Switch running V1 app launcher items between users desktops

BUG=309024
TEST=unittest (and of course also tested visually)

Review URL: https://codereview.chromium.org/44313004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231229 0039d316-1c4b-4281-b951-d872f2087c98
Read and process up to 32 QUIC packets before yielding to the message loop.

Review URL: https://codereview.chromium.org/44633004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231230 0039d316-1c4b-4281-b951-d872f2087c98
AndroidVDA: only engage if it's likely that the codec is backed by hardware.

BUG=311581

Review URL: https://codereview.chromium.org/45073002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231231 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 231231
(1 of 2) Move InvalidationController to chrome/

Move the InvalidationController Java class from sync/notifier to
chrome/browser/invalidation.  Move its IntentProtocol inner class into
its own class, InvalidationIntentProtocol, and keep it in sync/notifier.

In order to prevent this change from breaking the downstream build, a
reduced version of InvalidationController has been left behind in the
old location.  The second part of this patch will remove it.

An unfortunate side effect of having two InvalidationControllers is that
they may be double-notified when the when the activity state changes,
and this may cause the start or stop signals to be sent to the
InvalidationService twice.  This is wasteful, but otherwise mostly
harmless.

TBR=jhawkins
BUG=172391

Review URL: https://codereview.chromium.org/45103003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231232 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 231232