Clients can query who has set a particular user restriction on a user.
Currently the result can be a combination of none, system/user, or admin.
Bug: 27830375
Change-Id: I50ea9db0a59ffe3abbdcbb1a436d9ace7a35a851
Logs the following parameters :
- Total time spent optimizing apps.
- Total number of apps that were dexopted.
TESTED: with adb logcat -b events:
05-04 15:24:16.303 2065 2065 I sysui_action: [402,3]
05-04 15:24:16.303 2065 2065 I sysui_action: [403,34]
05-04 15:24:16.303 2065 2065 I sysui_action: [404,0]
05-04 15:24:16.304 2065 2065 I sysui_action: [405,163]
05-04 15:24:16.304 2065 2065 I sysui_action: [406,12168]
This shows that:
- 3 apps were optimized
- 34 apps were skipped
- 0 apps failed to optimize
- dialog showed a total of 37 (3 + 34 + 0) apps
- system has 163 optimizable packages
- a total of 12.2 seconds was spent in the optimizing apps dialog
bug: 28528058
bug: 28544474
Change-Id: I9eb5229a1589ca0df57d3fc03102992fa90a877f
...if the restoring data engine thread winds up operations. By closing
the engine side of the pipe unconditionally when exiting the thread,
the unanticipated-failure path is now guaranteed (instead of blocking
forever in write() to a pipe that isn't being read!).
In addition, wire agent-timeout handling into the various stream
data-handling operations (preflight, backup, restore). This were
not sufficiently robust and were in some situations leaving the
backup/restore mechanisms in a livelock state.
Finally, plug a longstanding problem in which we'd have orphaned
timeout messages coming in and producing a certain amount of "wtf?"
logging and wasted CPU. No longer!
Bug 28457158
Change-Id: I597c76c3eada378ffeb20870253847594f73e089
Make sure to "freeze" bounds while dismissing the docked stack by
either maximizing or minimizing it.
Bug: 28196862
Change-Id: Ifcd9deda340de8bc46df949df2fa1049e2f45f92
Also increase the event buffer size to 100, and implement
it as a real ring buffer. And put that implementation in
a generic class for use in other places.
Change-Id: I06936984e2c253fb5f0eb5d15faf0019ec73d4e2
- We should always start the activity when docking to ensure that the
launch state is set up correctly.
Bug: 28470261
Change-Id: I4aae0dedb95a1c796c72b487b6700da0754e66f3
Both of these activities do additional work and look janky when
rebuilding for a config change, especially in the presence of
multiwindow. As neither of them use layouts or other resources that
vary based on configuration, mark them as handling the relevant config
changes.
Bug 27171954
Change-Id: I38df1d875bcb063d72316b586c4d3f8074c4fad9
am: 17bc1fd090
* commit '17bc1fd09042f2749a1c822d32bc48eeb3b280f6':
Fixed a bug where the pin wasn't scaled correctly
Fixed a bug where the scrim was transparent
Change-Id: I3259a79075ece8f4159d5bc4272ce39fd37f3b5f
am: 05d61edeb2
* commit '05d61edeb271167b6a9a97aa9adf1fe7bfb9bfbf':
Fixed an issue where the scrim could be lost
Change-Id: I72f8ed8b302d9e9542e2ae3c540f671d344b74bf
am: 4ad13b3340
* commit '4ad13b334057dc541168d4ffdaf61a63b5fb6864':
Fixed a flickering when expanding and the notifications updates
Change-Id: I99cfb8a7baed888eceeacc44f12cc128d2aec6e1
am: 11619f4782
* commit '11619f4782507e7543b23e5aed5f7164f16b20c3':
Fixed a bug where the content height was wrong
Fixed the fade in animation when coming from dark
Fixed the animation when flinging over the bottom stack
Change-Id: I07107b2694542e1b70e9813b323c026660b81589
am: 910f69e0bb
* commit '910f69e0bb7fc9a6ef880f27fe99ad3a7abbdf15':
Made the dismissal of notifications snappier
Change-Id: Ia5a47a60d8361bcfddca365482ec236f91fe6049
am: 35a8c2f00e
* commit '35a8c2f00e1c3bb2e2cf24260682400d025a49f0':
Fixed an issue where children would animate strangely when removed
Change-Id: Iecb054320ff101638b9d79f8b0d1f25bead30524
* changes:
Fixed a bug where the content height was wrong
Fixed the fade in animation when coming from dark
Fixed the animation when flinging over the bottom stack
