The puller for the atom frequently fails. We believe it is due to the
size of the pulled atoms. No metric can be correctly build from this
atom.
To reduce the size, we apply transformations that we would likely
perform when analyzing this data. We combine times for all shared app
gids together and combine times for the same apps. We also exclude
isolated uids which are frequently recycled and removed from the
underlying data source.
If these optimization do not help, we will need to introduce different
atoms.
Bug: 157535126
Test: cmd stats pull-source 10010
Change-Id: I0d9a18c78f456e1b0f9d7ad322f15354ead9f02b
Currently, inputflinger would send an ACTION_POINTER_UP event with
AKEY_EVENT_FLAG_CANCELED when we have at least 2 pointers down and
one becomes the accidental touch.
In ViewGroup, if we have FLAG_SPLIT_MOTION_EVENTS, it may split a
multi touch event into some single touch events to the target childs,
so we should also check the cancel flag in order to prevent it trigger
the accidental click on the child view.
Bug: 161655782
Test: enable twoshay, test accidental touch on RecyclerView
Change-Id: Iba864361ca3361e4a720dbe0eb0b39d42a6dc5b2
When "04fb2e7: MediaSession/Controller: Add playback speed related APIs"
was merged, the constant was not added.
This CL adds the new constant.
Bug: 174297519
Test: m update-api -j;
Change-Id: I698737bcfe641edd7b5ea07b4b385c81fe899994
* changes:
Add a convenience method to update a network's capabilities.
Disallow NetworkAgents from changing the owner UID.
Observe mOwnerUID in NetworkCapabilities#equals.
For the attaching the nav bar to the app during quick switch, we
reparent the leash of the nav bar to the app the user swipes from and
restore it back when the quick switch gesture is finished.
There is a callback IRecentsAnimationController.finish() which seems to
be a good timing to restore the nav bar. However, it doesn't work well
in the live tile mode.
In the live tile mode, the overview won't call
IRecentsAnimationController.finish() until a new task is started and
this is why we need to add this API.
Bug: 139273001
Test: make
Change-Id: Iabea2fb222a2dacd57207b74d1778f93237268ea
ConnectivityService is going to be a part of mainline module, to
prevent using @hide method in ConnectivityService, reimplement
DumpUtils#checkDumpPermission() in ConnectivityService.
Bug: 175177794
Test: atest FrameworksNetTests
Test: adb shell dumpsys connectivity
Change-Id: I1e4bc023b39b40a717a3a0fd8cd60aa2f25e9bdb
Show change status in inline setting description
Bug: 173460479
Test: atest com.android.systemui.statusbar.notification
Change-Id: Icda82041e6248b6430b58fcec03084aeb2754861
1. Show different icon for different NAS adjustments
2. Fix style issues in dark theme and new S notification UI change
Test: atest com.android.systemui.statusbar.notification, manually test
on device
Bug: 173460479
Change-Id: I0d4433fecd9f00d2a7705e2329e52a2f6efaf7d8
UserManager#getUsers() is a hidden API, use getUserHandles() to
get user id instead in PermissionMonitor.
Bug: 171529940
Test: atest FrameworksNetTests
Change-Id: Ic304627688de8e49505a95ebc99628b2e0eafab9
Trigger WiFi recovery. The WiFi chip will get disabled and then
re-enabled. The state at the exit may not match the entry state.
Bug: 175084231
Test: atest com.android.server.wifi
Test: atest android.net.wifi
Test: adb shell cmd wifi trigger-recovery
Change-Id: Ie46bc697dcc003758c5df7c7c9d594e365086c7d
Test: atest com.android.wm.shell.flicker.apppairs
Test: go/wm-tests-flicker should become green
Fixes: 175230170
Bug: 172704238
Change-Id: I210430a9f36fe8aca43bc0e97d29b5530c9dcb28
The pending fading out animation is not canceled while dragging.
It should be canceled when the users touchs the button. If it is fading
out when the user touchs it, we should cancel the animation and set the
alpha value to 1.
Bug: 175194712
Test: atest MagnificationModeSwitchTest
manually test
Change-Id: I3dec8520e90db7aff1050924be4e3bab1e27f23d
This reverts commit cf0e36923b.
Reason for revert: Merge conflicts, should have been merged in AOSP
Change-Id: Iee0a3e76c42858bcca45517e3ca02c65bc8eac0c
Bug: 172181610
Test: (1) run statsd_testdrive 277, and check the
metric output correctness after content switching.
(2) run statsd_testdrive 90, and check the metric
output correctness after launching the output dialog
via Sound Setting / Volume Rocker / Media Object Chip.
(3) atest MediaOutputControllerTest
(4) atest MediaOutputDialogTest
(5) atest MediaOutputBaseDialogTest
Change-Id: I0fea0c59afcb44fc1d22920036107524f221a7be
Merged-In: I0fea0c59afcb44fc1d22920036107524f221a7be
Change the instrumentation app build target type to avoid generating a TradeFed test module config file.
Test: make csuite && csuite-tradefed run <plan>
Change-Id: Iedfb415080fbd2c77537fd87f6a7f501c6a9fa97
Before the system is ready getSwitchState() returns KEY_STATE_UNKNOWN
for the lid switch causing the initial lidOpen value to be false on boot
even if the lid is currently open. This defers the triggering of any
callbacks registered before the system is ready to ensure that the
initial callback value is correct.
Bug: 159401801
Test: Manual - ensure first callback value matches lid state on boot.
Change-Id: I9351312e5ecf8b1984ae11a47ed9b89dab1aa07f
