This remap causes non-Legacy and Legacy devices to have different
error behavior when the camera permission is removed from a pre-M
application.
Without the remap, both routes map to CameraAccessException with
code CAMERA_DISABLED.
Bug: 21604925
Change-Id: I4ab18dca961cc7cedaccba0531253c9c4ef1d60e
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
Otherwise, registerAvailabilityCallback won't actually cause caller to
receive callbacks, if no other methods on CameraManager are ever
invoked.
Bug: 21536556
Change-Id: I5cded8a59846a971d6272ac3bced44678a533165
Clarify definition of rotation angles used in
SensorManager.getOrientation and SensorManager.getAngleChange.
Clarify the condition of a free-fall in SensorManager.getRotation, and
added code to guard against such condition.
Fix a typo that causes confusion in the definition of
TYPE_ORIENTATION data in SensorEvent.
Change-Id: I614d981ec7b1b52c5ec59d5b40b84cd600df65e7
See: b/21337218, b/21337552, b/21337606.
This adds a new service, fingerprintd, that manages fingerprint
hardware from a separate process. It provides a binder interface that
FingerprintManager uses to talk to the fingerprint HAL.
Change-Id: I84d8e407c1f1a7d1a396e246c382459ad38810ae
- Adds an AIDL interface to allow the proxy camera service
running in system server to accept RPCs from the camera
service running in mediaserver.
- Request an update to the valid user set from the proxy
camera service when mediaserver restarts to initialize
properly + avoid DOS after a crash.
Bug: 21267484
Change-Id: Ib821582794ddd1e3574b5dc6c79f7cb197b57f10
- Annotate everything with @NonNull, @Nullable
- Annotate a few @IntRange
- Annotate a few @IntDef
- Most metadata enums probably canont be annotated usefully,
since get/set() are generic and the annotation system
can't yet manage that.
- Plus metadata annotations need to be auto-generated anyway
- Also add explicit null check to prepare's surface argument
- Also update docs of getCameraCharacteristics to match reality
Bug: 21029463
Change-Id: Ifd81b2a782e29ad069fe25c7db4a1fda73dabcd7
If a session is directly replaced, it no longer will receive state
change callbacks from the device. That means it'll never hear about
abort or idle transitions.
Fix this to signal onClose earlier, after sequences complete. This is
reliable to wait on.
Remove the unconfigure drainer, as we have nothing to do after
null-stream configuration completes, now, so no point in triggering
anything for it.
Bug: 19666551
Change-Id: Ied6fb40126b79886cdbcb27d40a76a1646273dd2
