am: 886d17c
* commit '886d17c035805cef3bce3d2d96e53ba48bf5b62b':
Also log IPv4 and IPv6 connectivity of any previous default network
Change-Id: I8c82f1058531d1f5a0cdb73314b8fd742dae7860
am: d17b301
* commit 'd17b3013ce7bd38aaf16d1ffd578d964bfd1808a':
Includes both direct boot aware and unaware apps in Apps default view
Change-Id: I85630c13799c9bbaa558a0f1582691f7a00e0b86
am: f8ef3c3
* commit 'f8ef3c36a97b68b5e27127681973244f481cca09':
Log an event whenever we lose the default network.
Record the transport types for connectivity events.
Change-Id: If019f2c448ed3411a0b23dfdd6038e1b9fe2099d
am: b28d871
* commit 'b28d871a8dc1ae3f78ac6587272f8c8454718188':
Do not update accessibilityTitle in LayoutParams.setTitle
Change-Id: Ie6ce4e042ea3a14e7ed66dad89f4d879e128869b
am: f917e2f
* commit 'f917e2f738f25bcf34ffa073008e872d803458e1':
Populate RangeInfo correctly when acquiring from pool
Change-Id: I4273c7fe4511b8a542f15b604387e6f27ee6d676
More work on issue #26390151: Add new JobScheduler API...
...for monitoring content providers
We now have some delays before reporting URI changes, to allow
them to batch together.
Also clean up debug output, and fix some issues with how we
were managing the content observer state.
And while I am here, fix the device idle and app idle controllers
to no longer maintain their own list of jobs, but just directly
iterate over the JobStore.
Change-Id: I709bd7c77e1b5ffb012e36149a739ecb245dd5cd
Two separate implementation paths, one for Material look / layout, and
one for legacy / pre-Material one.
Bug: 28037149
Change-Id: Id1946802c0a93218d9eb0b73c81ad76dc027763c
am: 0628d32
* commit '0628d324d0f1c2116c051faadd8e4bf26206b1a6':
Also log IPv4 and IPv6 connectivity of any previous default network
Change-Id: Ibcbd79a6674cf062138ccbd031d14721b0367e22
am: 25c43b7
* commit '25c43b78d11f74e98ba9d5f541647aa5ed44ebce':
Includes both direct boot aware and unaware apps in Apps default view
Change-Id: I23eeef915a4607aa387e826056056cb7632a4542
am: 1feca76
* commit '1feca76bd48008aa3421c8741cb147ecc1a6e912':
Log an event whenever we lose the default network.
Record the transport types for connectivity events.
Change-Id: I2aea598dd2926c18fdb4e6301759539c504038dc
This patch adds an event class derived from IpConnectivityEvent that
records parsing errors of DHCP response packets.
Change-Id: I19516cf05e3419c4262e3236899e52987e5f2264
am: 0697c7a
* commit '0697c7a877d87acd572ed7ce62472d5866375e86':
Do not update accessibilityTitle in LayoutParams.setTitle
Change-Id: I006620e1ac9c8571dd698f45da75284010dc58e9
am: c1699a9
* commit 'c1699a9f4cf679ebc87e5b5bc99dd07446950be7':
Populate RangeInfo correctly when acquiring from pool
Change-Id: I0227f6b9a842fa1e63827cda51e0cb5a435e278e
am: 9e31b3f
* commit '9e31b3fd817aed28d9afd712fa49ec9d6fc11329':
More work on issue #26390151: Add new JobScheduler API...
Change-Id: I7c227898d175c15219192fc42c5e4eb5121e9517
am: 677b2c6
* commit '677b2c60aa5bd41b856762d223161220476844bb':
Skip to end for 0-duration animation
Change-Id: Ibc359887f4d96a84742e4369bb0059c1ece1afc1
am: 1dfe35b
* commit '1dfe35b8a797f921d095beeaf1018f7a987e8343':
Skip to end for 0-duration animation
Change-Id: I22f0cbf98b69b24b07de001bfebb86ad06c2170b
Repeating a 0-duration animation makes no sense. In the case of
battery saver mode, all animators are set to 0 duration, and
repeating the 0 duration animations not only waste battery power
but also potentially produce flickers on screen. In this CL,
0-duration animations are skipped to the end, regardless their
repeat count.
Bug: 25451472
Change-Id: I20f9dc2f0ff9c027782a8363ff4cf4a4d390736c
am: b2bbd21
* commit 'b2bbd2114d33c4804f2d53bfe0c5e17464d1c0e7':
Camera: update expectation of post RAW sensitivity control
Change-Id: I1b1030148e19ac308647b043bc2a5d7c56c86f53
