Revert 253087 "Add UMA stat to count unique origins using getUse..."

Revert reason: Because the in-memory cache was in the renderer
process, not the browser process, this implementation actually did
little to approximate a unique count of origins using the
APIs. Something more involved is needed.

> Add UMA stat to count unique origins using getUserMedia and RTCPeerConnection.
>
> BUG=none
>
> Review URL: https://codereview.chromium.org/174013003

TBR=joi@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253828 0039d316-1c4b-4281-b951-d872f2087c98
Revert 253798 "Exclude unused strings for chrome://ntp on Android"

> Exclude unused strings for chrome://ntp on Android
> 
> BUG=326023
> 
> Review URL: https://codereview.chromium.org/174453002

TBR=aurimas@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253829 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 253829
Add support for localized time strings with two units, eg. "2 hours 17 minutes"

At that occasion, replace five existing formatting functions for one-unit time strings by a single consistent interface with the aim to make time formatting functions easier to use by highlighting the availability of different formatting options.

Also at that occasion, rename IDS_TIME_DURATION_LONG* to IDS_TIME_LONG* to be more consistent with other IDS_TIME* ids.

BUG=339835
TEST=full unit test coverage
TBR=oshima@chromium.org (for resolution_notification_controller.cc)
TBR=jennyz@chromium.org (for ash/system)
TBR=asanka@chromium.org (for download_item_model.cc)
TBR=tim@chromium.org (for profile_sync_service.cc)
TBR=xiyuan@chromium.org (for imageburner_ui.cc)
TBR=estade@chromium.org (for foreign_session_handler.cc, policy_ui.cc)

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253830 0039d316-1c4b-4281-b951-d872f2087c98
Fix handling of the default comm device when it is not the 'console' device.
Previously ducking would only work correctly if console and communication devices mapped to the same physical device.
If they were different, ducking would not happen and worse, we could fail to open the device if the device properties of the two devices were different.

See more details in the bug report.

BUG=347531
NOTRY=True

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

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