am: 2fa2bae0fe -s ours
am skip reason: change_id Ie95555856afdd56728125f7e60b6a78cf9fc0e58 with SHA1 873e19f63f is in history
Change-Id: I19af5ee7f83feb9790ecff4a65972432248e390e
am: c6a2982b86 -s ours
am skip reason: change_id Ie95555856afdd56728125f7e60b6a78cf9fc0e58 with SHA1 873e19f63f is in history
Change-Id: I8c9e309eae92633cb6193f147f81d109cc812d7c
Battery saver was completely aborting the doze service, disabling
all interrupts. This is not ideal since it impacts the user journey,
especially when using face auth.
From now on the screen will still be off, but DozeService will be
retained, in order to receive sensor events.
Test: w/ battery saver: lift, tap, and observe aod being off
Test: w/ battery saver: receive notification, no HUN.
Test: w/o battery saver: lift, tap, and observe aod being on
Test: w/o battery saver: receive notification, HUN is received.
Fixes: 134157254
Change-Id: I9b713c78857c4e4c22d8d9bfff165b1b51dfd804
Merged-In: I9b713c78857c4e4c22d8d9bfff165b1b51dfd804
This reverts commit 0b874d5344.
Reason for revert: this might have caused performance regression
Change-Id: Ic1927292fb13a3acfb6c6e8d069f689e426f5a8b
BUG: 141561372
Test: Verified that the flag could be modified with
adb shell settings put secure...
Bug: 141380252
Change-Id: Ifa24b688a487482e5b02689c1046d85423f73280
- Ensure that the composition sampling listener is destroyed when the nav
bar is destroyed instead of waiting for the finalize callback. That
callback would never be made since the sampling listener has a reference
to the outer class and has a strong ref from SF, and the other class
has itself a reference to the listener.
- Always unregister the nav bar fragment from the mode change callbacks
Bug: 141473489
Test: Switch navigation modes a couple times, take hprof dump and verify
there aren't leaking classes
Change-Id: Ic389a559a3d430af495365102854d531f7d1966d
Merged-In: Ic389a559a3d430af495365102854d531f7d1966d
am: a3b5dd1b89 -s ours
am skip reason: change_id Idf387111b0cdc34ad3762eac0ec6c2b484b393e3 with SHA1 83c87e50b1 is in history
Change-Id: Ieaa24de8d2c65314e146ae9b447731db61d44020
This CL implements a (somewhat hacky) way to enable HTML attributes in
the mobile data type content description strings. This way we can use
some basic styling in the Quick Settings cellular data tile which uses
it in a TextView.
We do this by assuming that the content description is valid, escaped
HTML, and send two separate CharSequences to all of the listeners, all
of which can then decide if they need the regular content description or
the prettified version.
Test: atest SystemUITests; system ui demo mode
Bug: 141177147
Change-Id: Idf387111b0cdc34ad3762eac0ec6c2b484b393e3
Merged-In: Idf387111b0cdc34ad3762eac0ec6c2b484b393e3
This CL implements a (somewhat hacky) way to enable HTML attributes in
the mobile data type content description strings. This way we can use
some basic styling in the Quick Settings cellular data tile which uses
it in a TextView.
We do this by assuming that the content description is valid, escaped
HTML, and send two separate CharSequences to all of the listeners, all
of which can then decide if they need the regular content description or
the prettified version.
Test: atest SystemUITests; system ui demo mode
Bug: 141177147
Change-Id: Idf387111b0cdc34ad3762eac0ec6c2b484b393e3
We're wrongly showing the BigText content after ag/5928752
Fixes: 141446552
Test: post big text notification, look at lock screen
Change-Id: I02506a160afefb457f86eb00adccdaff44ddbd29
as broadcast receivers filter on data, not on extras. Hence changing
data changes the API.
Fixes: 141452043
Test: Uninstalled updates from system app and saw correct app-ops method
to be called
atest CtsHostsideNetworkTests:com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDataSaverMode_reinstall
Change-Id: Icab1fcea6153d5bbf0bf2af51e71d7fd6b5cb3e5
CL [1] introduced a check to see if password entry need to show
soft-keyboard for fixing keyboard popup unexpected issue.
But it shouldn't need to block the password entry re-enable when
lockout finished in screen-off state.
Move the original check right before the showSoftInput to fix the case.
[1]: I3c43d09d4206c48f1afcd8dad79e7978337f1b7d
Fix: 128563724
Bug: 112811602
Test: manual as issue steps:
1). Set up Password as screen lock.
2). Enter lock screen.
3). Input wrong password 5 times, and it will show "Try again in 30 seconds" message.
4). Wait device screen off auto, and then wait 30 seconds.
5). Screen on device.
6). Swipe up and then try to input password to unlock, expected password entry
should enabled and can invoke soft-keyboard.
Change-Id: I3e0eeffdb3536588c0e039c8fbeaf8833e7af06e
