It's not a guarantee that onCaptureProgressed happens after
onCaptureStart for a particular request.
Bug: 26676240
Change-Id: I900c3b36e1738dd3514954498023eaa4a1618989
As an exercise for a new API candidate LocaleList class, this CL does a
mechanical refactoring to replace Locale[] with LocaleList in
KeyboardLayout class. Note that what changed in this CL is just an
implementation details that is never exposed to application developers.
One take-away from this exercise is that finding the best-match locale from
an ordered locale list is really a common pattern. Perhaps we may want
to have a guideline for this kind of situation.
Change-Id: I142379afbaf24d524ff09cf6c7ee7720150f7489
Adding a System API for applications to access a context hub.
The API is not expected to be exposed to third party Android
applications in the medium term.
Change-Id: Ia2222317c913de6901f3912e4c89b5cfa398be85
This implements a mechanism for sensor hardware/HAL to deliver additional information beside sensor
readings to application. It includes internal temperature reading, untracked delay of sample,
location and pose of sensor device placement in phone frame, etc. This is also a very expandable
frame to account for future need.
Change-Id: Ifd52ff315ef675086326f118eab773b0194bae23
Note: sensor additional information report used to be called sensor meta data.
Defined the dynamic sensor meta data type and UUID of sensor, as well
as the broadcast intent that is related to dynamic sensor status
change.
Modify SensorManager, SystemSensorManager and the JNI layer to support
dynamic sensor discovery.
Added SensorNotificationService to notify apps that sensor connected
or disconnected via broadcast.
Change-Id: I28adfb005357d7e3983d65117d6865830c75027d
Adding new sensor types for the following -
i) Stationay Detection
ii) Motion Detection
iii) Heart Beat Detection
Change-Id: I95dd81605e0ce2467fe5e0b65dbd25447bba412b
This CL implements the SoundTrigger API improvements as given in b/22860713. Only the java-level
parts are implemented in this CL.
Key changes include:
* Addition of a SoundTriggerManager/SoundTriggerDetector system API to manage
the sound-trigger based sound models.
* Addition of a SoundTriggerService service that manages all sound models
including voice (keyphrase) and sound-trigger based models.
* Includes logic to write sound-trigger based models to the database.
* VoiceInteractionManager service now uses SoundTriggerService instead of
SoundTriggerHelper.
Bug: 22860713
Change-Id: I7b5c0ed80702527c4460372efeb5e542d3693a69
LEVEL_3 is a new high-level label for camera devices that support more
than the existing FULL-level capabilities.
Bug: 25114814
Change-Id: Ibed66ed6b83e4f28598455255d86b13b78f1f13b
This change adds support for a separate profile-specific
fingerprint database. This is to be used together with the work
challenge.
Change-Id: I65b3a74a1c887def210d7a6da0b907138f58a5ba
Adding a sensor type that returns the device pose as a -
. quaternion representing rotation from a vector due north
and zero pitch and roll &&
. a translation from an initial position
Change-Id: I8764b8c0b9a2518632f75c7a19c203836dd04b1a
Rather than associate the keyboard layout solely with a specific
hardware model, we should also associate it with a given IME subtype.
This lets users switch between various languages and have the
keyboard change in unison with them so they can use the appropriate
layouts for each language.
This change adds initial support for associating IME subtypes and
keyboard layouts. We still need to:
- Remove support for the old style of layout association once the
Settings apps begins to use the new APIs
- Automatically select an appropriate layout based on the given
subtype (or set a reasonable universal default such as QWERTY)
Bug: 25752812
Change-Id: Ie88ce1ab77dbfe03ab51d89c1dc9e0a7ddbb3216
Automatically select a keyboard layout if we have one that is device
specific and is made for our current locale. Also, provide a way of
requesting layouts for a specific input device rather than just
getting all of them. Custom layouts may not be appropriate for
typical keyboard devices (and custom keyboards may not work with
typical layouts).
Bug: 25062009
Change-Id: I3a0ae5ad68f956b936485791ceb78c347fad7d4f
This change is redundant after the following change is merged:
Camera2: Handle surface size change
When comparing if two OutputConfigurations are equal, also check
the width, height, format, dataspace when the output configurations
were created. With this, CameraDeviceImpl knows that the surface has
changed sizes and will reconfigure the stream.
Bug: 12250682
Change-Id: I4216260a0a08ad87b835ed97e9eaddf1df317fcc
This reverts commit f49f8b0bad.
When a new capture session is created, the old streams
are re-used if same surface and rotation. However, if the
surface has changed size, we must re-create the stream
to ensure HAL is configured properly, which includes
setting up proper sensor resolution.
This is an issue in e.g. CTS testNoiseReductionModes
and testEdgeModeControl, where a new preview with different
size can be setup without first stopping the previous one.
The same preview surface is used here, but with changed size.
Change-Id: I3b88a95209e83cf1cef0f4d1f791c87b0feb093f
Signed-off-by: Mikael Persson <mikael.persson@intel.com>
Signed-off-by: Zhiquan Liu <zhiquan.liu@intel.com>
Previously it skips the device permission check by referring package
name. The CL removes the special case and use general MANAGE_USB
system-only permission to skip USB device permission dialog.
BUG=26048722
Change-Id: I3702393a50696209499d1e5f6549dab9fb2cefe4
