The issue states that NumberPicker.setWrapSelectorWheel(false) only works
in a specific call order. The underlying problem is that NumberPicker
does not remember user's preference on whether the selector wheel should
be wrapped. Therefore, it only works when user sets their preference last,
after everything else that could affect the choice gets executed.
Bug: 19049714
Change-Id: Ic27d909cb3dd657993a4df9a04c819b6965ad11b
-Some implementations require a modem handshake to determine
FLP HAL version and can't do it upon initialization. Wait
for a v2 callback before assuming that the HAL implementation
is actually v2.
Bug: 21958418
Change-Id: I7512d293f99363c63580c69d84f80da96a88dd2f
* commit 'c3fbb0ce6c04ea5ece37bf4529271cb14296135b':
Fixes a typo where parens were used instead of curly braces, preventing a link from being created at build time.
This is to be consistent with the style/format in CarrierConfigManager.
Fortunately, nothing in packages/apps/CarrierConfig needs to be updated,
since this variable doesn't have any overrides.
Change-Id: I8910abd28d9c0aae68a04dcfcfb2f3d0c0466ca9
* commit 'bee8d60a1cdfb380904f8770d933e9031c7f9ff3':
Fixes a typo where parens were used instead of curly braces, preventing a link from being created at build time.
The variant of CipherSpi.engineUpdateAAD which takes ByteBuffers
delegated to a byte[]-taking variant of superclass instead of its own
class.
Bug: 18088752
Change-Id: I3b426bbdca54bbf7f6f3939589da07b24db14d0d
a link from being created at build time.
Change-Id: I4086ce5054cc2d5cacd72314810b626aee50df62
(cherry picked from commit e62f4540cd6ce6289fb0196c8e30c3a3d6905794)
When there is only one activity and it gets paused, activity manager will
try resuming some other activity. If there is no other activity, it will
start home activity and try to resume it. This will fail, because the
activity stack doesn't want to enter recursive resuming. We need to
detect this situation and schedule additional resume of top activity
after home gets started.
Bug: 21500945
Change-Id: I6ca703f8d97bcc4001e7da4cd5a5db63bfb5c861
When Google Play installs 2 apps concurrently (e.g.
personal and work profile) PackageManager can hit a
race condition when connection to media container has
not yet been established but the MCS_BOUND event is
triggered from MCS_UNBIND.
Detailed step by step scenario:
1. package1 comes in
2. INIT_COPY (initiate bind, add pending install)
3. onServiceConnected triggers (MSC_BOUND)
4. MSC_BOUND, process pending package and schedule MSC_UNBIND
5. MSC_UNBIND is triggered once the package is verified
6. service is diconnected
7. package2 comes in
8. INIT_COPY (initiate bind, add pending install)
9. MSC_UNBIND scheduled at step 4
10. MSC_UNBIND sees that there is a pending package,
schedules MSC_BIND
11. MSC_BIND arrives before service is connected and we fail.
Solution: do not fail if we wait for connection.
Bug: 21849046
Change-Id: I39928e1efc81ba64e45c622cc08cb786801d6569
Now runtime permissions are granted only to components that are
part of the system or perform special system operations. For
exmple, the shell UID gets its runtime permissions granted by
default and the default phone app gets the phone permissions
granted by default.
bug:21764803
Change-Id: If8b8cadbd1980ffe7a6fc15bbb5f54a425f6e8f9
Set sync adapters to active if the associated content providers are used
at foreground process state.
Minimize how frequently published content providers are reported by
keeping track of last reported time.
Also cache sync adapters associated with an authority in SyncManager.
Bug: 21785111
Change-Id: Ic2c8cb6a27f005d1a1d0aad21d36b1510160753a
The app-linking allows channel input sources to provide activity links
from their live channel programming to another activity. This enables
content providers to increase user engagement by offering the viewer
other content or actions.
Bug: 21884742
Change-Id: Iabeea57884c63ac31ee164c27c6e2fe1860f15f6
Doze wake locks don't actually hold the CPU awake, so we should record them
separately from full wakelocks, which is what we did before.
Bug:21949905
Change-Id: Ib4db3399069e0ad11f1f0dc6925a87ad0ad21ff9
TM.getCellNetworkScanResults: Performs a radio scan for networks and returns
a list of OperatorInfo.
Tm.setNetworkSelectionModeManual: Manually selects a network and returns the
status of the selection.
Bug: 21563489
Change-Id: If64f30d6f1ed373c1d90433688389307f3dfee8c
