New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 739893 link

Starred by 3 users
Status: WontFix
Owner:
weidongg@chromium.org
Closed: Jul 2017
Cc:
█ senj@chromium.org
adlr@chromium.org
vapier@chromium.org
█ de...@chromium.org
steve...@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 739788



Sign in to add a comment

Update over mobile connections allowed by default

Project Member Reported by weidongg@chromium.org, Jul 6 2017 
Updates over mobile connections should be allowed by default because we already have the behaviors to make users confirm downloads.

Changes in UpdateEngine:
set kPrefsUpdateOverCellularPermission to true by default.

Changes in UI:
Remove SetUpdateOverCellularPermission() call in OOBE phase, because it is allowed by default now.

Although enabled by default, updates over mobile connections could be disabled by setting kPrefsUpdateOverCellularPermission to false. It could also be disabled by admin by setting device policy DeviceUpdateAllowedConnectionTypes to exclude mobile connections.

Comment 1 by benchan@chromium.org, Jul 7 2017

Cc: de...@chromium.org senj@chromium.org steve...@chromium.org vapier@chromium.org adlr@chromium.org
Components: OS>Systems

Comment 2 by weidongg@chromium.org, Jul 7 2017

Status: WontFix (was: Assigned)
After discussion with deymo@ in  issue 739788 , kPrefsUpdateOverCellularPermission is supposed to be as it is right now. ==true means "never ask me for updating over cellular"; ==false means "ask me whenever you would update but you didn't because of cellular".
►

Sign in to add a comment