Adds logging for:
- Default action buttons
- Close by going back
- Close by tapping outside dialog
- Open via QS button
Also added new events to be implemented in future CLs
Bug: 182830510
Test: atest com.android.systemui.globalactions
Test: atest com.android.systemui.qs
Change-Id: I43c449450ba5b3879b128eaf64b1098dd625f8d3
The new api will be similar to "transferTouchFocus" and
"pilferPointers".
In the new api, we will be transferring touch, wherever it might be,
to the specified window. This will be used in the case where the app
is fullscreen, and the user swipes down to check notifications.
Currently, the behaviour is like this: user swipes once to show the
status bar, and then swipes again to show the notification shade.
The desired experience is for user to swipe once to show the
notification shade.
This new api will allow the StatusBar to transfer touch to the
notification shade, so that it can continue to get expanded.
Bug: 177997773
Test: atest inputflinger_tests
Change-Id: If38d395669104d6aebb68f97e830fa80393b50d5
Before, it tried to access WindowManager from a non-visual context. Now,
it should use a window context.
Bug: 187644235
Test: manual
Change-Id: I3994d7b86fd28598d375c1c8033d72bbc9a9fdcf
Bug: 187429663
Test: Checked ApplicationInfo.hasRequestForegroundServiceExemption()
of a test app, with and without the new attribute set.
Change-Id: I98342a35a82e44327db896c9820806eb3eda5b4c
Unsigned subtraction lead to arithmetic overflow which caused aapt
to reference the vector out of its bounds.
Bug: 175789289
Test: dump badging on a manifest with no uses-sdk tag
Change-Id: Id1b96376a8bfe13c0c195bb6f62b681c3d686034
This change adds a new UiEvent enum for NOTIFICATION_PEEK and logs it in the same places where we already count note_peek using MetricsLogger.
Test: atest HeadsUpManagerTest; manual verification via statsd_testdrive
Bug: 159697717
Change-Id: I10aebd73b4889f3f677de421018f39ce2ab8fb66
Increase timeout to 45 days based on feedback.
Bug: 183103253
Test: atest AppStandbyControllerTests
Change-Id: I7a36c720dbf16c16940308576a3965384889e527
When the user's touch first enters the udfps area, play the
keyboard pressed (click) haptic feedback.
Test: manual, atest UdfpsControllerTest
Fixes: 187535630
Bug: 185124905
Change-Id: I2e5231e74dbbc2617ba9f0f04127827fd14078e9
When IME is targeting notification shade, IME will be above status bar,
and IME won't receive status bar insets anymore. The surface position of
the control of IME will be changed because IME fits status bar. If the
IME control target receives the new IME control (new surface position)
after the IME animation starts, the IME position will be stale until the
next IME animation, because the controls would be copied before playing
the insets animation.
This CL lets IME receive insets no matter what z-order IME has. So the
IME position will stay the same while it is moved above system bars, and
the IME behavior will be the same as before Android S (receiving status
bar insets while targeting notification shade).
Fix: 186178729
Test: Steps as below:
1. Make, install, and open EditTextVariations.
2. Open menu, and select Direct Reply.
3. Expand notification shade.
4. Expand the notification of EditTextVariations.
5. Click Direct Teply Test.
6. See if IME is overlapped with (button-based) navigation bar.
If no, press home button and repeat 3-6 for several times.
Change-Id: I53c64a5598f246ad577f652156903e4666a30cd9
Pushing these as a metric will come in a future change.
This is a direct cherrypick with no changes.
Test: unit tests
Change-Id: I8a123f7aed7c0ce416814372f2287b04a8a04ac0
Merged-In: I8a123f7aed7c0ce416814372f2287b04a8a04ac0
(cherry picked from commit 8d0ecde2b8)
* On an org-owned device with a managed profile,
quick settings has a tappable security footer
that shows privacy disclosures.
* The footer should be untappable if there
is no policy applied by the admin that
requires a disclosure (e.g. network logging).
* The device ownership text will no longer be
shown for org-owned devices.
Manual testing steps
* Set up org-owned device with managed profile.
* Verify QS footer is visible but untappable.
* Enable network logging.
* Verify QS footer is visible and tappable.
* Verify device ownership text is no longer shown.
* Verify behaviour is unchanged for device owner
and profile owner.
Bug: 186196610
Test: Manual testing
atest QSSecurityFooterTest
Change-Id: I0df6dc69dc249544d596375f7cd364d8a4080230
For packages don't have READ_VOICEMAIL permission, CallLogProvider will
limit its access to voicemails by applying strict grammar check. Add
this permission to CallLogBackupAgent to avoid exception when backup and
restore.
Bug: 184244328
Test: Manually restore the device
Change-Id: I7848a6b58f4502d4dd9a346e5e3725e5d741c02f
