This CL fixes that physical keyboard layout is not changed when user
changes it in settings. This happened because we compare
InputDeviceIdentifier instances by using Object#equals to choose
specified input device. However, one of them has been serialized and
deserialized, so it never be true.
Bug: 27747115
Change-Id: Ied84c510ccb8e2de919ba8bb326e0355a065e604
Stop repeating request if any of its output stream is abandoned
and notify that repeating request has been stopped.
Update binder tests for binder interface changes.
Update CameraDeviceImpl to expect an exception when canceling
a repeating request that is already stopped.
Bug: 21270879
Change-Id: I9fa72ae7218948aac88cb1a8e57839bd022c4a5e
- Make FingerprintService more closely track the expected state of fingerprintd.
- Don't switch to a new operation until fingerprintd completes previous operation.
- Refactor clients into separate classes and add tracking logic.
- Add missing enumerate()/cancelEnumeration() methods to IFingerprintDaemon
- Make late-binding decision of "foregroundness" of activity so that it's
decided in the order the events are actually handled.
- Add more logging so we can determine FingerprintService state when errors occur.
- Cache a copy of authenticator_id from the last time it was set so we don't
interrupt the driver during actual authentication.
- Don't allow clients to access authenticator_id unless they're current.
Fixes: 27902478, 26273819
Change-Id: Ic1f9e30bd89bcdbb8fe7f69e0545e68339317721
Lens shading correction should be full correction that
corrects both color shading and vignetting.
Bug: 18175853
Change-Id: Ia552345b2bd78b1b2eed2472096ebae80680d70b
- 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
We provide a preferred constructor for the user which will
always generate a serializable NanoApp object. While we
still support the other path, we throw a specific exception
when trying to serialize a bad NanoApp object to ease
debugging.
Change-Id: I7ee610f0fce2f0dd489526e4819f66035281024b
Per API concil recommendation, made below API change:
* change method name from createCaptureSessionByOutputConfiguration to
createCaptureSessionByOutputConfigurations
* Change method name from
createReprocessableCaptureSessionWithConfigurations to
createReprocessableCaptureSessionByConfigurations
Bug: 27950067
Change-Id: I8346d384210556a40bc2544c3660cc4819f304a1
Previously, the KeyphraseEnrollmentInfo would iterate through the list
of Enrollment APKs and just use the first one for a list of supported
keywords (of which there only could be one). Now, all APKs will be
enumerated and the enrollment APK that provides the given
keyphrase/locale will be used for the enrollment intent.
Change-Id: I78b0ef758c6c024b5787603bba5907a646f3c3f1
Not removing the listener causes warning logging, which is especially
heavy when a lot of camera connect/disconnects are happening.
Bug: 27217534
Fixes: 28000512
Change-Id: I4911f27cc0f69301975b110a9b456977050ce5bc
Some devices support HDR output for preview in addition to still
capture, so explicitly allow for that in the documentation of
SCENE_MODE_HDR.
Bug: 27313038
Change-Id: I894d7449dc0cfb7353f535db23acd12143590208
The correct stream ID is required to be sent along with buffer drop
errors, and LEGACY mode was putting in a placeholder. This would
cause an error in the client-side implementation, triggered by
abortBuffers (Which is the only source of buffer drops from LEGACY).
Bug: 27828602
Change-Id: If3fba7a76f7aa0ff305efa4cce6c225eb720b30e
Added handling of app query reponse from context hub.
Exposed the maximum message size to clients.
Change-Id: Ie96a860774d005ad6ad72acc88dc79964835486b
Added handling of app query reponse from context hub.
Exposed the maximum message size to clients.
Change-Id: I8d8ecaa2e75f6ef86ee65a3a050538cbbadc32eb
* Resolve issues pointed out by API Consul:
. Privacy concern about sensor UUID
. Callback name consistency,
. A few document error and typo.
* New API to tell app if the sensor system support dynamic sensor
discovery.
* Added API to make dynamically connected sensor directly
identifiable.
* Explicitly indicate sensor additional information support for a
sensor
Bugs:
b/27715564
b/27911274
Change-Id: Ie93ab4c07fea82002f3f107b7c35827a088312be
Camera sensors on Android may be either landscape or reverse-landscape
oriented, but the vast majority of shipping devices only use landscape.
This means that many camera-using apps (which are generally forcing
themselves to landscape orientation) never call setDisplayOrientation,
since its default value of 0 is correct for the majority of devices.
However, there are some reverse-landscape devices, and for those, such
apps get upside-down preview.
This bandaid changes the default value of displayOrientation to be 180
on such devices, so that apps that never call setDisplayOrientation get
correct preview. This bandaid has no effect on apps that do call
setDisplayOrientation, so hopefully such apps are doing the math
correctly.
Also update documentation to indicate that setDisplayOrientation should
be called, and to note the change in default orientation behavior in
Android N.
Change-Id: I1b2c957642fda8edead61bd07eda9d18c38d1fe6
Fixes: 27840948
This CL add private sensor type base constant to java file to match
C header file.
It is defined that all vendor sensor types have to be >= 0x10000.
There is a constant in sensor.h for reference. However, there is
no such constant defined in Sensor.java before. This CL adds it.
Change-Id: Ia8f8c06583c62879e51779815051c346f1a9cd14
(cherry picked from commit 1795e14dab)
Since this Callback class is scoped within ContextHubManager, we
remove the redundant ContextHub from the name. This CL is just
a rename and should not modify any behavior.
Change-Id: I40fea3ab7b5312d32a6f22b7543669ed563b9992
Reconnect to camera service if camera service is down when
registering a device availability or torch status listener.
Bug: 22483263
Change-Id: I56868b301151175e18aa1932a8b903e840bcac50
Previously UsbModeChooser activity is automatically closed when Android
is connected to another Android and works as host. This is because
ACTION_USB_STATE intent does not include the information whether Android
is connected as host and UsbModeChooser regards Android is not connected
USB devices.
The CL introduce the HOST_CONNECTED extra to ACTION_USB_STATE so that
UsbModeChooser can refer it.
BUG=27535640
Change-Id: Ie29583b78319078430f6d9a8390787780410ac8c
