We skipped the applyAnimationLocked to work around a problem with
cached animation loading, however app could be animating without
window animator (only app animator) in which case we shouldn't do
the relayout for potential focus change.
Revert to the old behavior and let applyAnimationLocked decide if
we want to relayout for focus change.
bug: 29874980
Change-Id: I6fdfbe41cbafd7017477c0eda9b4fd26e66c517f
Allow wearable handsfree device for PBAP Access
Usecase:
1) Pair and connect with Jabra Stealth Headset.
2) Go out of range so that connection gets disconnected
3) Come back in range, so that reconnection happens.
Observation:
Headset fails to reconnect with DUT in some scenarios.
Root Cause:
Headset does not send page request to DUT in some scenarios
leading to reconnection issues. This propabaly happens because
Headset fails to connect PBAP in previous iteration so it goes
in bad state, and does not page after Link Supervision Timeout.
Current Settings code only allows Audio_video_Handsfree Class of
devices to have PBAP Access permission, and set Rejected Permission
for other Audio Device Class. This headset being Wearable Class (0x0404)
is set as PBAP Rejected, and all PBAP connection to DUT from this remote
device are rejected leading to issue of bad state in headset.
Fix:
Allow wearable class audio devices to also have PBAP access permission.
Bug: 29219133
Change-Id: I18d8412cbeb86c18610091898d1c79f26d3d808d
In extreme cases the list of recent tasks can grow beyond the size
of a single Binder transaction. This change moves over to
ParceledListSlice which handles chunking any large results.
Bug: 29635557
Change-Id: Iaf1227234f5f8c9451f73a6a5c1dc89f2067f05f
When function getCode is called on
NativeDaemonConnectorException object it may throw exception
due to mEvent object not being set for certain constructors.
Fix is to return a default error code as expected if mEvent
object has not been set rather than trying to call
mEvent.getCode().
Change-Id: Ia8aa23deb8871bb4df73096cc489b685a1765f16
1. removing deprecation for setExtras on Connection/Conference as these
have legitimate use-cases going forward.
2. Expanded documentation on Call.Callback class to clarify how it is
expected to be used.
3. Updated Callback#onConnectionEvent callback docs to clarify its usage.
4. Expanded Call#sendCallEvent docs to clarify expected namespacing of
call event keys and extras keys, as well as clarification about backwards
compatibility and expectations of ConnectionServices.
5. Standardized the "invoked" vs "notifies" language in the Conference
docs.
6. Clarified how Connection callbacks from Telecom should be implemented.
7. Added Bundle parameter expectations for pre-defined connection events.
8. Documented capabilities and properties toString methods.
9. Documented expectations for onCallEvent method.
10. Expanded documentation for sendConnectionEvent method to clarify
namespacing, use cases, etc.
Bug: 29759275
Bug: 29759954
Bug: 29759773
Change-Id: Ib8c983af4dbbfee68edb60937b268e2c1a9b5e64
Each frame directory may optionally contain a `trim.txt` to specify
how the image was trimmed relative to the animation's full size.
See FORMAT.md for more details.
Bug: 29055299
Change-Id: I7a291e9a52b4bbe50a29c519f6a4d0e2cc0389d7
