This reverts commit bde04da6bc.
It looks like you can only have profiles declared as "highspeed"
if the framerate is >= 100, regardless of resolution
----
private static final int MIN_HIGH_SPEED_FPS = 100;
...
case CamcorderProfile.QUALITY_HIGH_SPEED_720P:
assertEquals(1280, profile.videoFrameWidth);
assertEquals(720, profile.videoFrameHeight);
assertTrue(profile.videoFrameRate >= MIN_HIGH_SPEED_FPS);
----
Fixes android.media.cts.CamcorderProfileTest#testGetWithId
Change-Id: I4ec23fcbda1993a7bbe4aba1b48aa8746d48c18d
* Default haptics are clunky and exaggerated, making the device feel
slow when using the keyboard and soft keys.
* Sharpen up the response for a better UX.
Change-Id: Iddb3b55fa7d6245c529208a460b5bab73b0ed2f3
After the removal of qcif (the previous lowest resolution) in
change Ie85f72d1c2c24d3c6e3665f7a34dbbe325cc64d7, "low" must now
match the characteristics of the new lowest, qvga.
Fixes android.media.cts.CamcorderProfileTest#testGet, testGetWithId
Ref CRACKLING-962
Change-Id: I4193813d5c21a68c71a3ac13a21cf73e3eaaf746
Although the mag modules in the daemon were limited to 20hz, the HAL
was announcing 50hz. Fix the HAL value so that it matches the daemon
implementation
android.hardware.cts.SingleSensorTests#testMagneticFieldUncalibrated_100hz,
testMagneticFieldUncalibrated_100hz, testMagneticFieldUncalibrated_25hz,
testMagneticFieldUncalibrated_50hz, testMagneticFieldUncalibrated_fastest,
testMagneticField_100hz, testMagneticField_200hz, testMagneticField_25hz,
testMagneticField_fastest
Ref CRACKLING-962
Change-Id: Ia74473d72b2275a3f86e3ff4735b89fd89ddd294
It looks like the scenarios in which the dual-mic echo cancellation
setup is problematic are confined. Surface a toggle for those users,
and leave it on by default for everyone else.
This reverts change I7af67e51c77d75d3803937ec2f5e783bee0bb518
Addresses CRACKLING-665, CRACKLING-617
Change-Id: Icd86af799355bc33c963932667d9b09806f8879a
Reduce memory footprint by moving data sets into const
data segments. Update function parameters to accept const
parameters when appropriate.
CRs-fixed: 928770
Change-Id: I42955cf18de2b0541cfaed89359cdcf9ae6fea8a
Issue:
When scene mode is Landscape/Sunset, Backend AF mode is
set to Infinity and AF state is INACTIVE and then when
APP calls do AF, focus state is still Inactive and since
there is no change in AF state, HAL not sending the state
to frameworks and APP got stuck.
Fix:
Check backend AF mode is INFINITY and if its Active AF call
then send the corresponding AF INACTIVE state to frameworks.
Change-Id: I4663e29ecd3be8f257cfd18dd037c9208fb019ee
Issue :
Reprocess for thumbnail is triggered even though
feature mask is zero. So, Config stream is failing.
Fix :
Unmask all the features which are already applied
on online streams(preview/postview).
And then check feature mask for triggering thumbnail
reprocess
Change-Id: I189f558e5a00b4fae4987410296f7d40e1e216f5
Flushing a pending batch of requested events is blocking for several
causes. The readEvents API call wasn't properly returning the state
of the pendings, and even after that's corrected we were still blocking
on the input reader _after_ filling out the pending requests.
While we're at it, follow the CDD recommendation synchronize with
SystemClock.elapsedRealtimeNano() clock. Replace the monotonic time
with boot time as reference time.
Fixes android.hardware.cts.SensorTest#testBatchAndFlush, addresses
CRACKLING-641
Change-Id: Iae460f503e1ad408a0cb7855000daabec414a459
Ramswaroop Ghanshyam Somani
Ethan Chen
Ricardo Cerqueira
Arvin Quilao
Steve Kondik
Scott Mertz
Valeri Atamaniouk
Sampath Vangaveti
Ramjee Singh
Chong Zhang
Roman Birg
yinhaitao2