Similar logic is required for the replacement case, as is already in place
for the update case, although the actions are different.
Bug: 15588056
Change-Id: I9ad115237c589716772e569fa1979a206b77097b
Bug: 15432556
The api council asks to change the interface to an abstract class
and clarify the clearClientCertPreferences api. This change addresses
these.
Change-Id: I7979788c7c041bacbfef5ea4d94309f91279ef22
This was causing strange indentation.
The change also clarifies how to get the supported output sizes in the
ImageReader flow: Although the doc (correctly) instructed the developer to use
StreamConfigurationMap#getOutputSizes(int) with an ImageReader, this instruction
appeared after the bulleted list of output types. Since all other items in that
list specify that getOutputSizes(Class<?>) should be used, the reader shouldn't
be expected to read beyond the list only in this specific case.
Bug: 15574400
Change-Id: Id952b46ae52322d75abbcaffea678d5ba50b22a5
rename isNetworkActive -> isDefaultNetworkActive
rename registerNetworkActiveListener -> registerDefaultNetworkActiveListener
make listenForNetwork/requestNetwork take a NetworkRequest
rename NetworkCallbackListener -> NetworkCallback
rename listenForNetwork -> registerNetworkCallback
rename releaseNetworkRequest -> unregisterNetworkCallback
remove NetworkRequest param from NetworkCallback functions
rename onNetworkCapabilitiesChagned to onCapabilitiesChanged
remove onReleased
change time units in onLosing from Sec -> ms
bug: 15142362
Change-Id: Ibc96e3f461706efe1eafa0d85605249cfd6e9fdd
Don't trust mNotificationData being sorted consistently
at all times...which it actually should. But apparently isn't.
Instead of using binary search to find the previous instance of
the notification when it's updated, use a simple linear scan.
Bug: 15589158
Change-Id: I7a09d0c64e35bd1930b8992d19da1393f4e4bb4e
Also fixes a bug where notifications would be wrongly padded
on Keyguard after rotating the screen.
Bug: 15244051
Change-Id: I2418692c3d2ffdd5fe642361f2924629bf9a75eb
the gdbserver special case wasn't updating mLastSlash. Fix it.
(cherry picked from commit 195b23ef712c51dc8d2f3a1f1943a27054dc4e74)
Change-Id: I52c6bbeb5483f8f6e20dd17de29ab703a6c8ebef
Added a log based interpolator (it's faster in the beginning and smoother
at the finish than the decelerate interpolator)
Scaled the timing and opacity of the falloff ripple based on the size
of the outer bounding radius. Backing circles aren't as apparent for
Smaller touch targets.
BUG: 15591274
SpannableStringBuilder should throw an exception when the
parameters to #insert and related methods are in the wrong
order.
We'll have to reopen b/9570771 and deal with it separately.
Bug: 14965397
Change-Id: I01847e0010d23f98ad3def8ba030d36570528900
http://ag/480881 changed RouteInfo.getDestination() to return an IpPrefix
instead of a LinkAddress. This makes the equals() comparison always fail.
So, when ConnectivityService.updateRoutes() is given identical routes, instead
of realizing that there's no diff, it would consider them different, and thus
add and remove the same route. The add would fail, since the route already
existed in netd, but the remove would succeed, leaving the system with no routes
and thus no connectivity.
Bug: 15564210
Change-Id: I2003b0fcb809cc20837dc489c58af37891ca4556
