When an app is unavailable to get its activity info, it will not have a
color, title or icon and it would look weird in recents. Therefore skip
adding it to the recents list when this occurs.
Test: manual
Change-Id: I1cf2f7f8ea5ce132159f6aabfbfae31df0187660
Fixes: 64236158
BluetoothBatteryDrawable creates the drawable lazily using
the latest(and most correct) context. So it could get the
correct color from the theme.
Also add iconScale field in BluetoothBatteryDrawable so the size
of the battery icon could be scaled.
Bug: 67377756
Test: Manual - connected to bluetooth headphone and open the qs
page and detail page. Retest it after changing it to dark theme.
Change-Id: Ic6c871985a89a503221755eed4bc2605ab53f630
First time going to recents would not have the recents stack created yet
and so SystemUI would fallback to getting the window rect from the
fullscreen stack. The code getting the fullscreen stack passed an
undefined window mode which would return a null stack. Fix this by
asking for a fullscreen window mode.
Change-Id: I372bcf5ccffd87af467a8a1a8cee46def1640654
Fixes: 67864447
Test: manual - on boot, launch app, press recents button
Add support for Supplier<Icon> in QSTile.State, allowing a method for
CustomTile not to cache the drawable for its IconViews. This fixes the
problem that the ImageViews in QQS and QS were trying to use the same
drawable and putting it in a bad state.
Test: Add 3rd party tile to first position in QS and turn on/off; visual
Change-Id: I408d6391a718fcb3f847e72bd303551d2d004dbb
Fixes: 67356768
- Creating com.android.system.shared library with recents model code and
corresponding recents tests
- Removing notion of blacklisted apps since that is now obsolete.
Bug: 67510855
Test: It builds, Recents runs
Change-Id: Ib1f5eefa6e4d4964366061246002509e2e15b19e
The bus event DockedFirstAnimationFrameEvent was not fired to
DividerView from secondary to system user so the last snap target for
DividerView was not recorded instead the bottom of the screen was the
last target. Since the bottom of the screen is last recorded, when
unminimizing, the dividerview goes to the bottom of the screen and
dismisses. This is fixed by piping the event from the secondary to
system user so that DividerView can get the event.
Fixes: 67326180
Test: manual - go to secondary user, drag to dock and minimize, press
recents button
Change-Id: Icd7497c49826d04dc907ef2eff3a5248e78ef67b
Depreciated the TaskDescription constructor when passing a bitmap and
added constructors to support passing drawable resource ID. Passing
drawable IDs allow users to use drawables such as AdaptiveIcons
instead of creating and passing a bitmap. Later SystemUI checks for
either bitmap, file name or resource ID to get a drawable to display.
Test: run-test CtsActivityManagerDeviceTestCases android.server.am
.TaskDescriptionTest
Change-Id: Ib944687249acf9fb6bbf9a9a109930cc04539e14
Fixes: 36298959
Wallpaper would have the wrong placement during
first frame because it would be center aligned
in a surface that's not big enough.
Also removed old OpenGl implementation, in favor of new
hardware accelerated canvas.
Change-Id: Ic9c9eaa817e1f6494aa5431d8278f2c28b2c45a9
Fixes: 66926914
Test: set wallpapaer with different offsets, orientations and devices
* changes:
Remove events bus code from task loading code.
Pull out TaskStackListener into its own class.
Remove unused recents fast-toggle/paging code.
- Remove extra class RecentsPackageMonitor, just have RecentsActivity drive
the event itself.
Bug: 67510855
Test: Remove package while Recents is open, ensure activity infos are
trimmed
Change-Id: Id963434ff868e607fe90ef770e4ba2070905cfba
Subscribe to thermal throttling start/stop events from thermalservice,
if the vendor thermal management subsystem supports push notifications
of throttling events. Update temperature warnings immediately when
throttling start/stop events are received.
Fixup existing comment to reflect current code regarding default warning
temperature value.
Bug: 66698613
Test: PowerNotificationWarningsTest, PowerUITest,
manual: taimen with artificially low temperature threshold and
logcat debugging messages
Change-Id: I021bcd0d06af861fd3a18a1790815a836659cee6
Update comment to describe which value the default temperature
warning notification is used by default.
Test: compile
Change-Id: I421d8f665827c4b45efa169b6ce50ce6655eb74b
* changes:
4/Clean up use of hidden recent task flags
3/Removing unnecessary filtering logic for recent tasks in SystemUI
2/Trimming tasks based on active and visibility
1/Clean up RecentTasks list
- Remove flags to control which recent tasks are returned -- they are now
trimmed with the expected behaviour when the task list is modified.
- Remove unused logic related to force-resetting a task based on inactive
time.
- Remove SysUI logic related to excluded recent tasks since it is already
handled
- Clean up task list subsetting now that returned list is guaranteed to
only be visible tasks
- Only use AM interface to fetch recent tasks instead of through AM
Bug: 34270611
Test: runtest --path frameworks/base/services/tests/servicestests/src/com/android/server/am/RecentTasksTest.java
Change-Id: I3f60ce507563152b5704c63985af621b02d0e7c8
- Remove all code related to last-stack-active-time, quiet profile task
handling, and visible task range filtering
- Remove the notion of firstActiveTime since that was only used to filter
tasks in SystemUI, also convert lastActiveTime to elapsed real time since
it is only used in the system to order active tasks, and in SystemUI as
a part of the TaskKey for caching purposes (it is no longer used to
determine the last visible task based on time)
Bug: 34270611
Test: runtest --path frameworks/base/services/tests/servicestests/src/com/android/server/am/RecentTasksTest.java
Change-Id: I44d494a521f60f302e0976fcf33490fe837f7cdb
Currently when both sims are locked on PIN, upon exhausting
PIN attempts for SIM1 PIN, SIM1 PUK view is not displayed
and the user is not able to unlock the PUK.
This is due to while fetching the getSecurityMode in Key
-GuardSecurityModel, the ordering of checking the security
mode is PIN first and PUK later.So when one sim is locked
on PUK and the other is locked on PIN the ordering of checking
the PIN first is causing to return PIN as security mode in place
of PUK. This will lead to PUK lock screen not been shown to user.
Fix: In KeyGuardSecurityModel.java, while querying the security Mode
modify the order to check for security mode i.e PUK locked state first
and then PIN locked state.
In KeyGuardSimPinView and KeyGuardSimPukView, check for sim locked on
PIN and reset the flags to show the default message.
Test: manually test
Bug: 34796244
Change-Id: I157959d9eb313b9d3af84f86e1429448a0f7f065
Add change to show "Invalid card" on UI on CARD_IO_ERROR when
erroneous SIM card is inserted
Bug: 23147806
Change-Id: Ibaacf06f2aad8f206095783cc431a87485f1c2ad
An incremental improvement to keyboard support on the status bar.
SwipeHelper calls a method on ExpandableNotificationRow, which it then
manually invokes from keydown/ups and the AccessibilityAction shortcut.
Regular clicks on the lockscreen still do not activate the notification.
Bug: 34840327
Test: manual
Change-Id: I5b59dec26c5e20237c4136820fff902ff8221371
