Adding getVideoStateFromCallType method to ImsCallProfile, which basically
just breaks out some of the existing logic in getVideoStateFromImsCallProfile.
This is used to translate the CALL_TYPE_* from an external call to a
video state (used when pulling the call).
Added a new ImsReasonInfo code for when multi-endpoint fails to configure
because the modem does not support it.
Bug: 27458894
Change-Id: I226e79005dccf3e8cae30e4d448543adbe59f922
am: f2e37da
* commit 'f2e37daeadaa05fb9ac22cba81067adf9a54e2b3':
docs: Updates to API Overview for N Preview 2
Change-Id: I38475c4e17064e39db9216be44d473ee25870361
am: 7037a86
* commit '7037a86e36ddfe23833c80acba258abf9f0c1d62':
docs: Updating Android for Work N Preview page for DP2.
Change-Id: I3b3bc1c7ad096e1c92b64dc764ba571748eb6cc6
The "Direct Reply" section of the "Notifications" page within the
N Preview documentation now includes a code snippet describing how
to show an acknowledgment of a user's response within a notification.
Also, the "chat history" example now has a clearer, more complete
explanation.
Bug: 27665098
Change-Id: I2fd098ab30a00f4fa2a84f3b150cc1c7f7f53750
- Rename "surface set ID" to "surface group ID"
- Remove setSurfaceSetId
- Use constructor overloads to set surface group ID, make
OutputConfiguration immutable
- Add Surface.getConsumerDescriptor to make it possible to verify
if two Surfaces have the same backing consumer
- Cache initial surface generation ID in OutputConfiguration so that
changes in a Surface's internals will label it is as a
new output
- Add sample use case for surface group IDs
Bug: 27950763
Bug: 28076469
Change-Id: I13251d1dd3d26a978ffbedc519966524e93bc61c
- move wfcOperatorErrorCodes to CarrierConfig
- corresponding error alert and notification messages are moved to the
main string.xml and are accessed by index defined in wfcOperatorErrorCodes
- make a list of supported SPN formats and use CarrierConfig to define
index of appropriate format string
Bug: 27170754
Change-Id: I698908157c1022f47a43ef70f03a571f1d0c75da
Use ZygoteHooks code to mark zygote initialization to not be
allowed to create threads. This is helpful when new classes are
found to be used by apps but cannot be preloaded as they spawn
threads.
Bug: 27248115
Change-Id: I1dc3620d9e7d0054c672b993d89459fc4b353dfc
The existing logic just doesn't make sense for a display frame with
nonzero top. Consider if we were docked on the bottom of a 2560 tall
display and so had say a display frame top of 1280. Then if the anchor
were 80 pixels in to our window it's top in screen would be 1320.
When we would add these two we would end up a value greater than the
entire screen height as the possible space above the anchor. Instead
subtract the display frame, to only consider the possible space above
the anchor, within the display frame.
Bug: 26255254
Change-Id: I95d7575a12a4e319f85c1cf6778970ff37918045
