Move the logic for managing dimming the navigation bar
elements on the lockscreen into BarTransitions.
Replace search light + camera assets with new
versions at full brightness, and apply 50% dimming
at runtime, including the IME dismiss button.
Remove unused StatusBarManager _NOP hints.
Improve choreography between camera button +
password security (w/ IME). Fix a few found bugs
in PagedView.
Improve password security unlock transition, manually
fade in back along with the rest of the icons.
Bug:11221659
Change-Id: Ifd1f8c9f400d90542f0ca858b9a4deacabbd518a
Previously, turning the screen off with the panel expanded would
run one time through panelExpansionChanged, leaving the background
in an intermediate state.
This has probably been around for a while, only uncovered now
that we can see it (if the status bar is translucent).
Bug:11357145
Change-Id: I55b768696c8791f82265a61d2c0f665503ad8bb0
- reuse intermediate bitmaps when loading resources
- only use hardware layers on views that are animating
Bug: 11269977
Change-Id: I39ad7aff16468632da47448404416404f3b54cc4
Out with TransitionDrawable.
The new background drawable knows about all possible
background styles, and optimizes the transitions
between them - including picking up from the current
state, force finishing on screen off, and using
SystemClock.elapsedRealtime() for timing.
Bug:11254317
Change-Id: Ice83dc966f6674ef97f7008f2a1b62d67ec59e7d
This occurs when switching users on devices that
don't have a rotation lock quick settings tile.
Change-Id: I738ca15ca754be90cec7eaf3a8eda3e38ed96b33
(cherry picked from commit e8f50a1400)
Currently it's possible for the home application to suggest new
wallpaper dimensions and the WallpaperService to request the bitmap
between when the new dimensions have been propagated and the old
bitmap has been forgotten. This leads to the WallpaperService
drawing a Bitmap with the old dimensions into a Surface with the new
dimensions.
By forcing the WallpaperManager to forget the old Bitmap immediately
before we reload it, we can ensure that we always have a Bitmap of
the correct size.
Bug: 10853302
Change-Id: I298ac5f3f8bcde54eeb1e45d21bf2ba3cbb618c9
- store desserts as ALPHA_8, saving 75% of bitmap memory
- run DessertCase in its own process, avoiding bloating
systemui every time the daydream or platlogo activity run
- lock orientation in DessertCase to stop thrashing around
when the device is rotated
Bug: 10918599
Change-Id: Ia2fb0696b903ae355c75b53d3a0c45b70784d00c
This gives the location quick setting the same ability that all the
other quick settings have: the accessibility text can now be
different from the display text.
Bug: 11010329
Change-Id: I0dee7b6f974b4e1dc314a35e39d907e90dc8dc3c
Defense in depth:
1. If there's a sticky battery broadcast waiting around for
us, apply its information immediately.
2. If for some reason there is no battery information,
just don't draw anything.
Bug: 11208146
Change-Id: I43e4b55a90a4ca619816ad0315e329f88b529581
Regression of ancient bugs 6955586 & 7086018 (navigation bar
missing buttons since they're stacked up off the screen
along the wrong axis).
Bug: 10341684
Change-Id: I778b085bf256cb20ecceaf38fd229a7de9b75aae
Resources that change based on MCC or MNC will now
show on the RSSI tile in Quick Settings.
bug:10518893
Change-Id: I55a77f967d2630b5c1aa17382069a15f37745405
There was a problem with a cached instance of a Date object such that it
would retain information about the default TimeZone that was not updated
when the TimeZone was set to the correct value. This resulted in NotificationPanel
sometimes showing the wrong date, based on the time and the delta between
the local timezone and GMT.
The fix is to use an ACTION_TIMEZONE_CHANGED broadcast to recreate the cached
Date object appropriately.
Issue #10854196 Incorrect date showing in notification shade
Change-Id: Ibf883e1ff37f4d0aae6840fb19e43e7e9e45bcc2
This changes the accessibility code to monitor state changes
and replace the touch listeners with click listeners when
touch exploration is enabled.
It also fixes a bug where the first touch on the camera was being
ignored by ensuring KeyguardTouchDelegate has started the service
by the time the button is touched.
Bug 10991981
Change-Id: I7c4bf01f9bfa10f54cadb0809b6af526c5386af5
