| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 21955350
Change-Id: I2e610a5a0af39668b7e9447cfd7d48d35e11d299
|
|
|
|
| |
Change-Id: Ic168b250defb30512cb35a836118fe2bdf1b2e78
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Notifications in which the icon resource ID is changed after
Builder.build() is called (even, and particularly, as the
last step in the current implementation of
setLatestEventInfo()) were not having their icons properly
parceled. In these cases we now attempt to catch this at
parcel time and construct the necessary Icon object.
But wait! Parceling does not require a Context. So we don't
actually know which package to load the resource from.
Therefore we now allow an Icon to be constructed with an
empty ("") package name, which allows us to complete this
parceling task despite the fact that a Notification does not
know its own package name. (In case you attempt to load a
drawable for such an Icon, loadDrawable will spot the ""
package and instead substitute the Context from its
parameters to try to load the resource.)
As it happens, even though the Notification does not know
its own package name, BaseStatusBar does, because it was
provided at NM.notify() time and is therefore included in
the StatusBarNotification structure. So we can actually
patch up the Icon (if it is TYPE_RESOURCE) and be sure to
get the icon loaded out of the correct package.
While we've got the hood open, this change fixes a couple of
related problems:
• Foreground service notifications synthetically
constructed for naughty icon==0 notifications (which we
are still allowing...FOR NOW) were losing the
FLAG_FOREGROUND_SERVICE flag (because we're
re-build()-ing them from scratch rather than rewriting
the provided Notification object). Now we set the flag
and hang onto the new notification for next time
setForeground() is called.
• We now allow media notifications to avoid getting bumped
to the top of the notification list if they're
PRIORITY_MIN. You might want to do that, I guess?
Bug: 21333763
Change-Id: Ia5d1f1acb594c7677bcc75ee3d624da4ffca671f
|
|\ \
| | |
| | |
| | | |
mnc-dev
|
| |/
| |
| |
| |
| | |
Bug: 21849185
Change-Id: If9b392d863e808d83a5d90bcc32df6cb9194cbdf
|
|/
|
|
|
| |
Bug: 21342040
Change-Id: I801970c2a25289d670636ad5387ddf244fb48225
|
|
|
|
|
|
|
|
| |
Remove unnecessary lines setting target density on bitmap and nine patch,
since we'll do this later in inflate().
Bug: 21774853
Change-Id: I5ea316bee81f82192ce20f2f1bee0e62c6ec8ccb
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Issue #21825791 add isFilterBitmap() override to appropriate Drawable subclasses
Change-Id: I5cbd72c034be79b0aa53815c7a5a8ea499e6e02d
|
|/
|
|
|
|
|
|
|
|
|
| |
Docs for translucent-vs-transparent-vs-opaque were confusing, especially since
the definition for those constants in PixelFormat are not the same as how they're
actually used in Drawable. This fix simply adds clarifying text to the method
comment for getOpacity().
Issue #21158891 Better document Drawable#getOpacity
Change-Id: I94725592f85e5d7874e3a3ac1c5bab969163fbf0
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I01027ebb9133240cc1c750824a41dd9fca484c1f
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
bug:21706035
Change-Id: Ia1cd4824c742b2d6fc0feb2861ccfde0b6ac2189
|
|/
|
|
|
| |
Bug: 21502154
Change-Id: Iedf4bd07f10ec13070a68870304ab651c1f15c68
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 21580708
Change-Id: Id64bebeb5c39906ed34775e8ccc39f666966bad9
|
|/
|
|
|
|
| |
b/21664621
Change-Id: Ie40c3723860e183c8e4fedd2a76b9debbdf64a2a
|
|\ |
|
| |
| |
| |
| |
| |
| | |
b/21341096
Change-Id: I84e20366db21ceaa4f044be3e322f9215bb06ad2
|
|/
|
|
|
| |
Bug: 21079749
Change-Id: If79dcef59aba616c0446efc623863f563cb16250
|
|
|
|
|
|
|
|
|
|
|
| |
DEPTH16: Use high 3 bits for confidence measurement, with
0 = 100% confidence, 1 = 0% confidence, 2 = 1/7 (14.3%) confidence, etc.
DEPTH_POINT_CLOUD: Add confidence as 4th entry to each point,
with a value in range 0.f - 1.f inclusive.
Bug: 20123879
Change-Id: I23317b922ac727751156fa418ed239a696a898e5
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 19638504
Change-Id: Ie7b639c543150e13aec30dfeca2b303d5b601cf3
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
Adds optical inset support for VectorDrawable and GradientDrawable.
Bug: 19944181
Change-Id: I9df04d9fe17ad858413e7f93694bf37ee2c43c85
|
|\ \
| | |
| | |
| | | |
applyTheme()" into mnc-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This CL works around Animator's lack of support for applying a theme
after inflation by postponing Animator inflation until a theme is
available, either in inflate() or applyTheme().
Includes a workaround for AVDs that don't reference any theme attrs
in their animators and this don't require a call to applyTheme().
Partial implementation of removing non-constant data from the AVD's
constant state. Moves the mutable AnimatorSet to a local variable and
treats the Animators as constant data.
We'll follow up with real support for applyTheme() in Animator or
AnimatorSet, at which point we can remove this workaround.
Bug: 20817800
Change-Id: I555c53c955219990ee376bee568bcc038532f9ed
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. ClipDrawable.getOpacity() now correctly respects the current level
2. DrawableWrapper checks the contained drawable's changing config even
if it doesn't have a constant state
3. DrawableWrapper gives priority to the last valid child drawable
rather than the drawable attribute
Bug: 21406104
Change-Id: I442fe90d0a3865bfdc6b2d14a7358178310dde02
|
| |
| |
| |
| |
| |
| |
| | |
Renames boolean getters to isZzz(), callback from onChange to onChanged.
Bug: 21342040
Change-Id: I9700d645453354b608fd97a832359211d828b52f
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Bug: 21281842
Change-Id: I4a1e33d7e642fa50e8789f1441e8587d1c15119c
|
|\ \
| | |
| | |
| | | |
applyTheme()"" into mnc-dev
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 9b115a9870a184e32bdbd07f792f9b8c956c75ca.
Change-Id: Ief148510472e129f992cf52ef8b8a25b5e17e05f
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only bothers with the background and active ripple, since the exiting
ripples are in hardware animation mode anyway and can't be updated.
Bug: 21079749
Change-Id: I0f70c0c0feea32e2c70bb9b1b0fa3b7846b20c7f
|
|\ \ \ \
| | |/ /
| |/| /
| |_|/
|/| | |
applyTheme()" into mnc-dev
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL works around Animator's lack of support for applying a theme
after inflation by postponing Animator inflation until a theme is
available, either in inflate() or applyTheme().
Includes a workaround for AVDs that don't reference any theme attrs
in their animators and this don't require a call to applyTheme().
We'll follow up with real support for applyTheme() in Animator, at which
point we can remove this workaround.
Bug: 20817800
Change-Id: I5a378a76e3625b9d754cb74ae98c07ba7c5698e5
|
| |
| |
| |
| |
| | |
Bug 21037890
Change-Id: I827e83dd75e301e7d93ead5efdd744f0d8435ae5
|
|/
|
|
| |
Change-Id: Iecf39b53419e07927a3fe3096036a57afd69439a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
And you may ask yourself: what is that beautiful icon?
And you may ask yourself: where does that API go to?
And you may ask yourself: is it a resource? is it a Bitmap?
And you may say to yourself: my god, what have I done
(This patch fixes a number of bugs in the initial
implementation, but other than that, it's the same as it
ever was.)
Bug: 18568715
Bug: 21141842
Change-Id: I1d3f9427abd7f0bb57e533fcfac708851ff644b6
|
|\
| |
| |
| | |
mnc-dev
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This works around situations where corrupted packages cause
Resources.getResourcePackageName to return something that
does't actually work.
Bug: 21144636
Change-Id: I271518599a8eb89d493f1ceda6cb2e47fb38a4ff
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This causes RuntimeExceptions to fall through to the next
case statement.
Bug: 21168985
Change-Id: Ie69610b22c6caf9f6536ebd48673067880cb75a2
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This CL fixes the issue where when start is called, we run the next frame
of the animation drawable while mCurFrame is already set to 0. The result
is that the first frame of the AnimationDrawable is then skipped.
Bug: 21168854
Change-Id: I2b77ae017d3debd0f8cfec81ea86d1120e78bb55
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| |/ /
| | |
| | |
| | |
| | | |
Bug: 20105644
Change-Id: Ia79d2ae5c725c139d2b7c423a899be625cb8f14f
|