* Use make fragments for various subsystems
* Move dexopt flags to device
* Move SSR script to common
Change-Id: I2a002f24c308481664b516a761b7978292c3efca
* msm8916-common now supports msm8939 as well, which required some
changes. Track those changes here.
Change-Id: I30c7b37026a6dcdc781321ed953f724bd0edbdeb
The features making use of MAX_ACL_CONNECTIONS and MAX_L2CAP_CONNECTIONS
are already initialised, by default, as 7 and 16 respectively.
BTA_SKIP_BLE_READ_REMOTE_FEAT, BTA_BLE_SKIP_CONN_UPD, and
BLE_PERIPHERAL_ADV_NAME are no longer used.
Change-Id: I2251332619eb206809d01279bf5c1bfd67199a30
AAPT ignores densities in PRODUCT_AAPT_CONFIG.
The use of PRODUCT_AAPT_PREF_CONFIG for density is
encouraged, as AAPT is able to determine the fallback
density to use if a resource of the specified density
does not exist.
Change-Id: If2b43a44593bc234118045d03bd48cd9820dc05a
* This is required per CDD now. A lot of devices disable it because it
can be absurdly slow (as it is in this case). We'll make sure it's
only used where necessary.
Change-Id: I636bb78cc6bd920c7c39727a561d3cd835fd975e
The variable persist.sys.usb.config is no longer honored by the framework,
and it's presence causes unnecessary toggling of the USB driver, which
disonnects ADB and makes the device's connection unstable.
Delete it.
Bug: 21404762
Bug: 18905620
Change-Id: Iaeded8a7617e9d787480b91387ca993d4e0a786c
Change I0d1163d7f7716f9a0366f2be245d50adad55b0cc in the audio HAL
changes the output for line-out from headset to an explicit AUDIO_DEVICE_OUT_LINE,
with change I5c574dc08e26fa053f60337acb17fb5b73ebbaa1 extending it to speaker+line
Declare it here to avoid "no such HW module" errors.
Change-Id: Icd1b90604ad563885e08d7a6cc6d7fa4a243a4cf
Ref: CRACKLING-1028
This reverts commit 6017ea120f, the
new acdb messes up a lot of other scenarios
Ref CRACKLING-1024
Change-Id: I0d66c5fee4665a543b7e0ddf079644736db8da07
We're getting some gain distortion at the top volume. Clamp it down
a notch.
Ref CRACKLING-623 and CRACKLING-662
Change-Id: I23ba76e514bd92ca7707592e7c74e9b4d1357398
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
Ethan Chen
Arvin Quilao
Pat Erley
Michael Bestas
Zhao Wei Liew
TheStrix
Adam Lesinski
Steve Kondik
Nick Kralevich
Ricardo Cerqueira
Ramswaroop Ghanshyam Somani
Scott Mertz
Valeri Atamaniouk
Sampath Vangaveti