| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/frameworks/base into t13.0
Android 13.0.0 Release 52 (TQ3A.230605.012)
Change-Id: Ic80f318636f1f70bbd009504352ddde511d0dead
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change uses StatusBarStateController to check if the device is
dreaming, since that state is based on the dreaming broadcasts which are
only sent after the dream has finished waking up. This means that
StatusBarContoller.isDreaming will remain true during the wake-up phase
of the dream, therefore allowing full-screen intents in notifications.
This change also removes the RPC to DreamManagerService, since the dream
state is locally cached in StatusBarController
Fixes: 265977861
Test: atest StatusBarStateControllerImplTest
Test: atest NotificationInterruptStateProviderImplTest
Test: atest CentralSurfacesImplTest
Change-Id: I8e97fdb064c4b23517d69498638769aac26f419f
Merged-In: I8e97fdb064c4b23517d69498638769aac26f419f
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`secondaryLabel` is public and may be changed from other threads, therefore make a local reference and use the local reference.
Bug: 271270746
Test: build SystemUI and verify the secondary label works properly
Change-Id: I71c79bcf380ce46ad5f0be6b8e2a7647df55f5bf
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL was generated automatically from the following command:
$ external/ktfmt/prepare_upgrade.py --repo=frameworks/base/ --build_id=9645412 --bug_id=266197805
This CL formats all files already correctly formatted with the upcoming
version of ktfmt.
Bug: 266197805
Test: Presubmits
Change-Id: Ide7d63a75fed98aabe348821355356c77f00a9ec
Merged-In: Ide7d63a75fed98aabe348821355356c77f00a9ec
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 270206382
Bug: 270388304
Test: atest ClockRegistryTest
Change-Id: Idd2668e3fa49af8039f48636c10aea8630d18581
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 269215830
Bug: 269794489
Bug: 269221040
Bug: 269203967
Test: Manually checked the color update on several clocks
Change-Id: I0ed636ed1a5a24c9943702124a5b8ae64e87424c
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also, rename Weather class to WeatherData.
To enable weather data, run:
adb shell device_config put device_personalization_services \
EchoSmartspace__enable_weather_data_extras true
Test: atest SystemUITests:LockscreenSmartspaceControllerTest
Test: Attach debugger and read values
Bug: 265069396
Change-Id: I800703be0af19e352542919c8cbb8bfa4ccb9932
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 266139726
Test: manual
Test: DreamSmartspaceControllerTest
Test: LockscreenSmartspaceControllerTest
Change-Id: I35e2b0a1d8b3f203371dfb23b9a3c0d7590ce4d5
|
| | |/
| |
| |
| |
| |
| | |
Bug: 262443413
Test: manual
Change-Id: Idb8c8e17623b6dddc22aa5bf69834dcbb87a3626
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change correctly supports settings for the currently active
user, and properly switches when a user switch occurs. It also takes
the Settings.Secure binder calls off the main thread.
Bug: 267535577
Bug: 265061202
Bug: 267372164
Test: Checked multiuser scenario on device
Change-Id: I467212aa452ec3f7fcfb74f4bf60be5805803672
|
| | |
| |
| |
| |
| |
| | |
Test: Manual
Bug: 268052542
Change-Id: I04d6a330b2d7cd150e874ca5fa94cdd58518cad6
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting up new Clock Event and data flow to handle weather data updates for the custom
weather clock.
Bug: 265069396
Test: manual
Change-Id: I2711660b34935936c9a1d2651a14415c54b551ef
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 242332478
Fixes: 266700158
Test: atest KeyguardClockSwitchScreenshotTest
Change-Id: I2887054bec077f63001a08318b7077f4fc11b5f8
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Enable the flag to write mock data using:
adb shell device_config put device_personalization_services \
EchoSmartspace__enable_mock_weather_data true
Then, set the icon enum (represented as an int) using:
adb shell device_config put device_personalization_services \
EchoSmartspace__mock_weather_state_icon_id 2
Set the temperature (int) using:
adb shell device_config put device_personalization_services \
EchoSmartspace__mock_temperature_value 22
Set the temperature unit (boolean) for isCelsius using:
adb shell device_config put device_personalization_services \
EchoSmartspace__mock_temperature_unit false
Test: Use device_config commands to test mock data
Bug: 265069396
Change-Id: Ibb110c324f3eb21c0c4fba70b2da5f0c042e9cff
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some clocks want to refresh faster than the current once-per-minute
rate. This allows them to do that on the lockscreen (but not AOD)
Bug: 265846399
Test: Manually validated faster ticking analog clock and default clock
Test: Manually checked faster updates enabled only in non-aod keyguard
Change-Id: Icc14517e8fde6de650c6fdde2126a714bf4e51da
|
| | |\
| | |
| | |
| | | |
BcSmartspaceDataPlugin.java." into tm-qpr-dev
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Many methods are only useful for BcSmartspaceView (At-A-Glance).
Most of the default methods now throw a "Not implemented" exception.
However, kept `setKeyguardBypassEnabled` as a no-op, so that it can be
called in a loop over SmartspaceView's.
Bug: 261752855
Test: manual
Change-Id: I8f250a6d2c5a8e84f78183b4563caa56ed79f77f
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change pipes the current dream state to OverviewProxyService,
similar to how doze information is shared. A condition has been
added to monitor the dream state, and a callback relays this
information to the StatusBarStateController. A new CoreStartable
maintains the monitor for this interaction.
Test: atest StatusBarStateControllerImplTest#testSetDreamState_invokesCallback
Bug: 265755700
Change-Id: Ic927a7e55864453da026c14cd1c87e6a7cf22489
Merged-In: Ic927a7e55864453da026c14cd1c87e6a7cf22489
|
| | |\ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
IContentProvider calls are causing jank in NOTIFICATION_ADD. To debug
the issue, we need more trace sections to find the root cause.
Bug: 261706477
Test: Capture trace, search for new trace sections
Change-Id: I39ad5b9a436e1dea429e2b8e26977413b5d047bd
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add BcSmartspaceConfigPlugin for smartspace config and register to bc
smartspace view.
Bug: 262630440
Test: Unit tests/ Manual
Change-Id: Ic5c61255d619806855adfc5bc4c09ee8f062fb4c
|
| | |/
| |
| |
| |
| |
| | |
Bug: 262112441
Test: Manually took a bug report to validate logs
Change-Id: I92fa88fca862fb5bf80ff6b0ca3a95438484414f
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Make use of AOSP config to set default initial value
Ref:
https://github.com/crdroidandroid/android_frameworks_base/commit/345ff7b8618bd57f6c6ccbf875cf860338deb513
https://github.com/crdroidandroid/android_frameworks_base/commit/ab1aad9aa76391d675ca38a93f23120032c1d957
Change-Id: Ib0adde055d91527a57b203cb488bce6f62974322
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
|
| |\|
| |
| |
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/frameworks/base into t13.0
Android 13.0.0 release 35
Change-Id: I709958b2f015d1774b2ece25894467c3a279f93c
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, we only need to set this for lockscreen Smartspace. When the
UI surface is set to "lockscreen", the date will update on Always-On
Display. See ag/20750544.
We can also deprecate the existing setIsDreaming method in favor of
setUiSurface. That's a separate issue and will be addressed separately.
Bug: 262046287
Test: manunal. Compared behavior and trace before/after the fix.
Test: atest LockscreenSmartspaceControllerTest.kt
Change-Id: I57126499dce033444d2c134f33a8b417e111ba65
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- adding ShadeWindowLogger using LogBuffer
- adding interface for all loggers wanting to log simple constant strings: ConstantStringsLogger
- adding default implementation of ConstantStringsLogger which can be used easily in Kotlin and using it in other loggers
- moving mForceOpenTokens from NotificationShadeWindowController to its State
Test: logging works
Bug: 245441667
Change-Id: Ic7c3b553c6388982bbc50b34a99a26de9f5e0d86
|
| | |
| |
| |
| |
| |
| |
| | |
Bug: 242332467
Bug: 242332371
Test: Manually checked existing clock positions and sizes
Change-Id: I3feea196bf348630697385e010a13955cdb0a897
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds isFalseLongTap method and makes an absract class for SingleTap and
LongTap as they only differ in touch slop.
Bug: 241487855
Test: atest BrightLineClassifierTest
Test: atest BrightLineFalsingManagerTest
Change-Id: Ia606afe2ebe5c454bcc74294210ced52f63e33ef
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
adb shell dumpsys activity service com.android.systemui/.SystemUIService
dependency DumpController KeyguardClockLog
Test: see logs in sysui dumpsys
Bug: 222260948
Change-Id: Ie668c7d85ad4278500253d20567eccaf64b78d92
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the clock moves on a large screen (e.g. when locking/unlocking the
device), this adds a subtle offset for each digit of the clock.
This hooks a new transition in to the existing clock move transition,
which just forwards progress through to the actual clock. This also adds
a feature flag (210) to enable/disable this, since it needs a little
more polish yet.
As above, this needs more polish (tweaking the time and/or easing), but
this at least gets something moving to start with :).
Bug: 199051139
Test: Manually verified.
Change-Id: Icec0bcfdb431d24b9405c5dfe8993016f687cac5
Merged-In: Icec0bcfdb431d24b9405c5dfe8993016f687cac5
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Consequently, RingBuffer is also moved to
SysUI/plugins
Test: builds, logs still work (see dumpsys)
Test: atest SystemUITests
Bug: 253490717
Change-Id: I91e3ef3ebdc6a2d929b2c1ae8ef158aeffa4c733
Merged-In: I91e3ef3ebdc6a2d929b2c1ae8ef158aeffa4c733
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change cleans up the Clock interfaces a bit by seperating some of
the interface methods and passing darkness data in to each clock face
seperately.
Test: Manually checked existing clock on device. Some unit tests.
Bug: 229771520
Change-Id: I8fee1c6c9bfff3a970f8333c5d5c3940f797dc28
|
| | |/
| |
| |
| |
| |
| | |
Bug: 247883311
Test: build success
Change-Id: I9cd535e84dc1eea40617485a5deb2744c3451e9b
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Conflicts with QPR2 implementation
This reverts commit 35ccfd76968a9e55fe46987e896c41831055285c.
Change-Id: I3bdcb7d9ca0fbf4e8fdb996b64669c98943578f4
|
| |\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Android 13.0.0 Release 16 (TQ1A.221205.011)
Also included the following reverts:
1. Revert "fw/b: Import Wi-Fi standard icon [1/2]"
2. Revert "Add preference for toggling the wallpaper zooming animation"
Co-authored-by: Semavi Ulusoy <doc.divxm@gmail.com>
Change-Id: I9a6b51e452c28d10411712c59778bb54da5783e9
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows the back arrow to report back trigger state to BackAnimation
as the gesture is going on. The trigger state might be included in the
future back progress API.
Bug: b/238475284
Test: Manual for now, because the current back arrow doesn't have tests
unfortunately, and will be deprecated soon. We should add tests when we productionize the
arrow prototype.
Change-Id: Idcbc2244d942788cd18a07ece252b0e7b6ef849a
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In this transition state, the device is not technically
pulsing, but it is Dozing. The primary difference
is that the display state is the display is still ON
(not DISPLAY_STATE_DOZE) and the DozeSensor wake gestures
aren't registered yet.
Because isPulsing=false during this transition, instead of checking
isPulsing, check isDozing instead. Only touches when the display
is ON get sent through the NotificationShadeWindowViewController =>
PulsingGestureListener, so the DozeSensors will still handle the
wakeups that aren't fake AoD2 (including both pulsing + transition
period).
This CL:
- updates the PulsingGestureListener to only check
the falsing manager on the ACTION_UP event of the single tap
and double tap gesture. The FalsingManager only works if checked
right after the action occurred. Previously, we'd check double
taps on the double tap's ACTION_DOWN.
- allows the FalsingManager to analyze taps from the NotificationPanel
while Dozing, as to include the taps when the device is
transitioning to AoD. When the device enters the display state DOZE,
taps will no longer be sent to the NotificationPanel.
- removes the vibration when DOZING that goes along with the falsing manager's
feedback when an additional tap is required. if the device is
dozing, its likely the device may be in the pocket so there's no
reason to buzz.
Test: manual
1. Enable AoD
2. Power off display
3. Tap display right after power off
4. Observe: device wakes up to LS
Test: manual
1. Disable AoD
2. Send a delayed (5000ms) high-priority notification
3. Screen off
4. When the notification shows, tap the screen
5. Observe: device wakes up to LS
Test: atest PulsingGestureListenerTest NotificationPanelViewControllerTest
Fixes: 246722709
Bug: 244659326
Bug: 242125976
Change-Id: I1330f2c87482d8bc743a61d652d245fd9b4c69a0
|
| | |\
| | |
| | |
| | | |
tm-qpr-dev
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Adds more xml resource configs to be able to more precisely control
the expansion transition:
- QS transition start delay
- QS squish transition distance
- QS squish transition start fraction
- On split shade:
- Fades in notifications scrim later
- Fades in QS earlier
- QS squshiness starts at 0.5 instead of 0
- On large screen portrait:
- Fades in QS and notifications only after the behind scrim finished
fading in
- QS squshiness starts at 0.5 instead of 0
Change-Id: Id0941d11fe194c8be74f6101cf6f9f7d22888fc9
Test: QSFragmentTest.java
Test: NotificationPanelViewControllerTest.java
Test: ScrimControllerTest.java
Test: LockscreenShadeQsTransitionControllerTest.kt
Test: LockscreenShadeTransitionControllerTest.kt
Test: Manually
Bug: 239904136
(cherry picked from commit ae32ffdaedbe2acdf56cf8931063d468b1b93948)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As the QSPanel doesn't reach the top of the screen, the
LargeScreenShadeHeader peeks out from behind the Edit screen
in certain configurations. In order to hide it, we fade it out/in
together with the circular reveal.
Test: manual
Test: atest NotificationQSContainerControllerTest
Test: atest LargeScreenShadeHeaderControllerTest
Test: atest LargeScreenShadeHeaderControllerCombinedTest
Fixes: 244455245
Change-Id: Ie8b8fb07b28e18b9620a948fbb6589394c4224d6
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is largely a cherry-pick of change
I6b32776dac1853eeab87c2a65da69478e4da5b75 but with
some notable changes to accomadate existing code
differences in tm-qpr-dev.
- We use a boolean instead of an enum for clock region
darkness as the enum is in a different place in tm-qpr-dev.
- We clean up some of the initialization code in
ClockEventController to prevent testing issues and provide
a dependency injection point to the screenshot test.
- Pull the clock color setting from the theme when region
sampling is disabled instead of defaulting to always dark.
Test: Manually validated colors matched reference images on
light and dark backgrounds with the region sampling feature
both enabled and disabled.
Bug: 229771520
Change-Id: I7906850b5de7f512f55e47e1122dfaacbc9c9406
|