Now that AAPT2 is library-aware, it needs to take care of
all library related work, including merging manifests.
The logic was taken from the current Java ManifestMerger.
Change-Id: Id93f713f27ae8617922bf89e325e45be9f863c06
This CL sets the position of EdgeEffect based on whether
clipToPadding is enabled. When enabled, the EdgeEffect will be
bounded to the padding. Otherwise, it will be drawn at the view's
bounds.
Bug: 21595866
Change-Id: I3968e5b8d3a75ce2d7607e2037bc372024694d5b
- highlighted text changed to match the application primary color
- change highlighted background to light gray
- remove highlight icon tinting (provides insufficient contrast against
the new light gray background)
BUG=18685226
Change-Id: I4040fa951fd2822cea324e0bd1924d10024b6a11
This makes sure that symbol characters who have both an alternative
or "full-width" version in the CJK fonts and a more regular version
in the symbols font get the default or "half-width" version by
default in non-CJK locales.
This is not a complete fix: such "full-width" symbol characters only
exist in the Simplfied Chinese font for now, which means in
Traditional Chinese, Japanese, and Korean locales, they characters
would now appear "half-width", which *may* be sub-optimal. The
complete fix would make sure the ones that actually need to be
"full-width" in TC/J/K are also included in the TC/J/K font.
Bug: 21525318
Bug: 21525012
Bug: 21524421
Bug: 21521330
Bug: 21520316
Bug: 21518544
Bug: 21517912
Bug: 21503807
Bug: 21502245
Bug: 21501669
Bug: 21525905
Bug: 21524018
Bug: 21503952
Bug: 21502678
Change-Id: I93cf7119b45ed3c080cd39d631a687e0ef9fd8ce
When the socketpair communication channel was added to
ParcelFileDescriptor, the CREATOR method for DropBoxManager.Entry was
not updated to read the extra fd from the Parcel. This was causing reads
to end too early.
Also removed comments referring to the now-deleted native methods in
the native Parcel implementation.
Change-Id: I49a9691da6ea927382ceb2fcbfdc7985a601111b
(cherry picked from commit ba953230f71e5117d819d9e7153da8304b141695)
There is a race condition when processing intents inside
PairingCancelHandler.onReceive() that could trigger NPE.
A speculative list of events (untested) that could trigger it:
1. Trigger Pairing Cancel for a Bluetooth device.
2. Turn Off Bluetooth
This should call CachedBluetoothDeviceManager.onBluetoothStateChanged()
and should remove the device from (1) from the list of cached devices
3. BluetoothEventManager.PairincCancelHander.onReceive() receives
an intent about about Pairing Cancel event.
Within the processing of that intent, cachedDevice.getName()
is called without checking whether cachedDevice is null.
In this specific example, cachedDevice could be null because of (2)
Bug: 21368124
Change-Id: I86f5d5287b440d1d2e0fe147278b1c2257902e95
No actual defined center for the Android sensor coordinate system
exists, so define the translation relative to the largest camera
device facing the same way.
Bug: 20123879
Change-Id: Ica33d23717c976c063c26b768af5b6148483909c
This CL alone doens't fix the whole bug, see the bug
for the AI list.
In normal mode, clicking at application icon on a task view
is ignored to avoid accidental clicks. To open app properties,
we need a long click.
In accessibility mode, we want to make it easier to open app
properties, and accidental clicks are less likely. Hence, allowing
"simple" clicks.
Bug: 20945599
Change-Id: Iec3f911dced1eda09175500fc1e798dd09b6f9e2
