Age | Commit message (Collapse) | Author |
|
tm-frc-adbd-release
Change-Id: I4e6f310de3de7072376a84df3094b3620176c93e
|
|
It is NOT guaranteed that drawInner will be called before a
ClockIconDrawable UX is shown on screen. To test this, I tinted the
ClockIconDrawable's foreground blue in its constructor, and red in its
drawInner method. If drawInner was always called before showing the
ClockIconDrawable on screen, it would be expected that all visible
ClockIconDrawables would have red tinted foregrounds. Instead, only 1
ClockIconDrawable is tinted red, and the rest are tinted blue. Here is
a screenshot: https://screenshot.googleplex.com/5saGse4nazp98QB.png.
Therefore, it can be concluded that drawInner is NOT guaranteed to run
before showing a ClockIconDrawable on screen. To failsafe against the
event that drawInner is not called before showing a ClockIconDrawable's
UX on screen, we set the time immediately in ClockIconDrawable's constructor. This method takes less than 1 ms to run and so there is no performance hit for putting this line of code here.
Bug: 188377749
Test: Verified that the time doesn't jump backwards to an incorrect time
when a user taps on the clock icon, then rapidly swipes back. It stays
at the same time as it was before the user tapped on the clock icon.
Change-Id: I67328c973d97974bcea340943f7ce02c55550d8e
|
|
tm-frc-adbd-release" into tm-frc-adbd-release
|
|
tm-frc-adbd-release
Change-Id: I25e903a3031d18a52c11a291530e44f0dffaff5e
|
|
tm-frc-adbd-release
Change-Id: Ieef638144e6ea5fe94f15b6fa0fffafee11d346e
|
|
|
|
Bug: 230522977
Test: Verified with extreme battery saver
Change-Id: I2ff2686eb014b02042b5110f2180f720350da419
|
|
Design intends for predicted app disc to use the app color, and the
dot to use tertiary T90/shade100. Both currently use `color`. Separating
into two separate colors lets use define the two separate colors
requested by design.
Bug: 213314628
Test: Manual inspection at runtime
Change-Id: I2e1656e9d806427a2fa8d4e79e414f99d9308086
|
|
tm-frc-adbd-release" into tm-frc-adbd-release
|
|
tm-frc-adbd-release
Change-Id: Ice97f065632ea77cc628ac92bc65778115f2c224
|
|
tm-frc-adbd-release
Change-Id: Ic6dbecf87a40e1501d742a4b9a7cbaaca1555149
|
|
Bug: 227627523
Test: manual
Change-Id: I488fd030e2c4ee3e5d7183ee53d48acd0cb5db4d
|
|
Previously, when a user clicked on the clock icon, the icon redrew
itself to an incorrect time for a split second before the clock
application was launched. This change disables this janky redraw.
Bug: 188377749
Test: Verified bug no longer occurs after change.
Change-Id: Ie38573c45e1f634c306b7e1556b146d58bfe376e
|
|
tm-frc-adbd-release
Change-Id: I4dc0c01bcb7ac7e2ff6c361ac6714b5baf658773
|
|
Bug: 223981931
Test: Verified that the clock icon drawable looks correct in all
combinations of dark, light, themed, and focus UX modes.
Change-Id: I2506b9322cd5d0590d1ee58715e6d69aff22d382
|
|
Change the function visibility scope from 'private' to 'protected' for use in IconCache.java
Bug: 226132413
Test: N/A
Change-Id: Icef3b03a959fb52e4a703d2e75d3ee1b7710592c
|
|
Bug: 220922858
Test: Manual
Change-Id: Ie269febaafe3027acfce5806ec3ce4ac57545000
|
|
taskbar" into tm-dev
|
|
Bug: 217247494
Test: change between dark and light mode and transition in and out of apps
Change-Id: Iccafe71b628e65d4b9df69195c28ee8238f06807
|
|
Bug: 189498337
Test: Hard-coded the notification dots to be visible, and verified they were the correct color.
Screenshot: https://screenshot.googleplex.com/AVbbW6P2bm6jYNS
Change-Id: I38a78cda056273eb300d458e663f79ccdd28f36a
|
|
|
|
Ibfec753b1f82b0ff97341a742b2933e2f18b234a adds the ability to upload
ALPHA_8 Bitmaps to HARDWARE. Take advantage of it when possible for the
themed icons.
Bug: 141480329
Test: manual
Change-Id: Ibcc75e0fd22c1600b54e562f2153c1cb25e461bf
|
|
-s ours am: 1ae9043346 -s ours
am skip reason: Merged-In I146a7e642778aa3c5c5c8f0b7f03535de5d9a814 with SHA-1 820707d6c9 is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/2013318
Change-Id: I9efda1237dd428e098b4311439dd0035a571acce
|
|
-s ours
am skip reason: Merged-In I146a7e642778aa3c5c5c8f0b7f03535de5d9a814 with SHA-1 820707d6c9 is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/2013318
Change-Id: I118c340ebe7cbdabd9bbede91e1f70bc7fd474d7
|
|
am skip reason: Merged-In I146a7e642778aa3c5c5c8f0b7f03535de5d9a814 with SHA-1 820707d6c9 is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/2013318
Change-Id: I8a1a8151778562531f1aaf6067f338eb131ab2cd
|
|
Bug: 222710654
Merged-In: I146a7e642778aa3c5c5c8f0b7f03535de5d9a814
Change-Id: Ifa4f1fb59786da5910892ac8f04ff837bfc79f3a
|
|
|
|
Bug: 204699454
Test: manual: https://screenshot.googleplex.com/B8Qhqi8Yf9dXCi7
Merged-In: I3ad0325fd0eb701d895eb6406b2726d671765c2e
Change-Id: I3ad0325fd0eb701d895eb6406b2726d671765c2e
|
|
Bug: 221273742
Test: Manual
Change-Id: I99fcb11e4cb306b9e4795ca2a9a17db3eb799445
|
|
Bug: 218147353
Test: Verified on device
Change-Id: I4a893693cfffce5d01b3112ac107fc26ed4b7003
|
|
|
|
820707d6c9 -s ours am: e263f7dd37 -s ours
am skip reason: Merged-In I4e434816b505b320b78efd90c910bc0a464e6175 with SHA-1 fabee8386f is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/16845264
Change-Id: Id405681e9b354681bc21bb5f0f70a81187a7c726
|
|
820707d6c9 -s ours
am skip reason: Merged-In I4e434816b505b320b78efd90c910bc0a464e6175 with SHA-1 fabee8386f is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/16845264
Change-Id: Ic49c31e16bacde1f22ca42bb05ea58d68b39d094
|
|
Bug: 214455710
Merged-In: I4e434816b505b320b78efd90c910bc0a464e6175
Change-Id: I146a7e642778aa3c5c5c8f0b7f03535de5d9a814
|
|
Test: manual
Bug: 195674813
Change-Id: Iae73360a980fd5ecd7b8fdbbf2451adb2f5fe516
|
|
Bug: 205803230
Test: manual
Change-Id: I7529f6a12d507e7f4557a4fb21e7e33359acd9be
|
|
|
|
|
|
Instead of checking against current user, checking the badge
with packageManager. This ensures that badging is applied even
if the app is running under manager user
Bug: 209503720
Test: Manual
Change-Id: I7089050a900e12d6315e83afd2c7aa6fb3b2edee
|
|
Bug: 213314544
Test: Manual
Change-Id: I6750eebfa4e0a83f5f9d2931b6c5e5c885dee912
|
|
* changes:
Fix launcher crash loop.
Revert "Fix launcher crash loop."
|
|
A null title in a cache entry causes a crash loop, however this title is necessary. Without the title, there is no point to caching the entry. Added logging and removed the null check to catch future errors.
Test: started launcher with a forced null title and without.
Bug: 210847986
Change-Id: Ief8be84254f3115aa4fa288171e8242953f39cd4
|
|
Bug: 200082620
Test: Verified on device
Change-Id: Ie0844312a3361da15ab3601cf6261da597d4d731
|
|
This reverts commit fabee8386fd90349d7a66feb50e073d8f5e642b7.
Reason for revert: Allow crash to continue on master
Change-Id: I474ff193de6b1ce728c3c053b61a4e3764e1a256
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/16493487
Change-Id: I91c48b82cc008e3f5d92d86e8180e0d6f7329357
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/16493487
Change-Id: I48d70a21bfd42557a762d064b49059b5faeedf48
|
|
A null title in a cache entry causes a crash loop, however this title is necessary. Without the title, there is no point to caching the entry. Added logging and added a null check.
Test: started launcher with a forced null title and without.
Bug: 210847986
Change-Id: I4e434816b505b320b78efd90c910bc0a464e6175
|
|
|
|
Bug: 209503720
Test: Manual
Change-Id: Iacfc5f2fdbdeb4d76a639b3e187b1ef7854f0d5b
|
|
6d932bc9c1 -s ours am: e05bdc2d38 -s ours am: b9acabe9f8 -s ours
am skip reason: Merged-In Id5bc2eca540bc13ab44c52cda5bf2e637614ae59 with SHA-1 7eb2ea9a58 is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/libs/systemui/+/1921937
Change-Id: Ic57d0a16c5ef74519c03b56cf46e28b517eb0850
|