| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using a strict basetype only coding style is not a good idea
especially when we are dealing with callbacks which use portable
typedef like int64_t. This kind of coding style would most likely
end up in overflows at various places especially when dealing with
timestamps and sensor delays which are caused when typecasting
datatypes of different size.
Switch to portable typedefs and get rid of "long".
Change-Id: I75b9cace7602345dba9095f046292e6d4db07df4
|
| |
| |
| |
| | |
Change-Id: I7cad5c048c1a9877889216ca8ca43bb13daeb4b0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Orientation Sensor is deprecated and no longer required.
Additionally this implementation is never even used, since Android
automatically replaces it by it's own implementation if the sensor HAL
doesn't also provide a Rotation Vector sensor. Furthermore the current
implementation only uses the accelerometer and magnetometer for the
sensor fusion and doesn't make use of the Gyroscope. So should we at
some point decide to implement our own complete sensor fusion this
would have to be rewritten anyway.
Change-Id: I45d8a9afd2089b49131e6cc69cdf2f3dfee46c92
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Actually this fixes several more problems, but the compass orientation
is the most noticeable symptom of this:
Android expects sensor event timestamps in nanoseconds. Linux timestamps
on the other hand are saved in the timeval struct in seconds and micro-
seconds. Therefore these need to be converted, which is easy enough and
is implemented in input.c of libsensors. Unfortunately, the current
implementation uses type long int for the return value and all further
calculations. Since the nanosecond values easily exceed 2^32 the buffers
overflow and wrap, which results in the reported timestamps moving between
-2^16 and 2^16. The consequences of this are noticeable especially with
fused sensors integrating the gyroscope readings, which use the difference
of two timestamps to calculate the change in orientation by multiplying it
by the rotation rate. When the buffer wraps around this results in a huge
time difference and thus leads to a momentary orientation change every
~4.3 seconds.
This commit fixes this behavior by using long long int.
Change-Id: Ib47bdc36ece16371c82f61b125315074ec048e32
|
| |
| |
| |
| |
| |
| | |
also fix a typo
Change-Id: I69246a96c53d7ec02ca90d73bc85dec4cbc73343
|
| |
| |
| |
| | |
Change-Id: I81ff71c8ae6bf25c1aabac4a6d8d6fcf64bd2e0b
|
| |
| |
| |
| | |
Change-Id: Iee501b65c23bed22bfe769496bafc852f939a8ac
|
| |
| |
| |
| | |
Change-Id: I3dd56f4d7fb0de8feca2422c165fe0c3cd92761a
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 9f7182d0542f4c82b6fe4722b8b9389021ad6ae9.
Let's not mess with the magnetometer sensitivity adjustments.
The magnetometer orientations are correct as is.
Change-Id: I218578088c43a27f4ff89d8c9e1671641725817a
|
| |
| |
| |
| |
| |
| | |
- Orientation sensor still broken
Change-Id: I7d20afbbc1f8b1ca5d046a38c0c3b7ce824c12cd
|
| |
| |
| |
| | |
Change-Id: I3c5cd29a497d2a84da7742b8fdf54bf4e0869cee
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
camera/CameraWrapper.cpp
Change-Id: Ic33d9a91629cf04e99c6e316e4871489f9f45924
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
BoardConfig.mk
Change-Id: I5794d6c3fb2e2ca542fc0eff65317334be9047b7
|
| |
| |
| |
| | |
Change-Id: I554de271021b595b27620135189f4dc61f604170
|
| |
| |
| |
| | |
Change-Id: Ie8f657544212a70a2ce0c7fb61d050d87f6247f6
|
| |
| |
| |
| | |
Change-Id: I537df0d39ceddfabb5e0a859398d5068f6860faa
|
| |
| |
| |
| |
| |
| |
| | |
We have only one analog source and one speaker,
do not use right (mute) channel for AIF2
Change-Id: I65780e0d022263976712e79a70bf217bf1b988eb
|
| |
| |
| |
| | |
Change-Id: I037aace6fae22c8635332bc5888663ac8c9e3851
|
| |
| |
| |
| | |
Change-Id: Iebfe3b797e3f44de1c6527111105122ed871f1c8
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Framework was responsible for enabling or disabling the
noise suppression using audio parameters. However, this is
currently broken in lollipop and most of the newer devices
have noise suppression enabled by default.
Use noise suppression when using the default
input device (main microphone).
Conflicts:
audio/audio_hw.c
overlay/packages/services/Telephony/res/values/config.xml
Change-Id: Ie8bdfe1d9860fdad996640d1664e8111df7d3cec
|
| |
| |
| |
| | |
Change-Id: I8593343012faf5b528df03cc9ed098bf44b66888
|
| |
| |
| |
| | |
Change-Id: Iccb763b48a687b88692c84976a7cddf72031b5be
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Lower the main and sub mic gain to prevent distortion.
* Increase the headset mic gain
* Enable +30db boost for headset mic
Change-Id: If5a3605b8742fc125d36d2b11e9c2bb15f089f92
|
| |
| |
| |
| | |
Change-Id: Ie28205afda03280d9cc6437a7c98f7b995fd4f50
|
| |
| |
| |
| | |
Change-Id: I25cab57acb84a14200006e832a43676ff3c8b9d0
|
| |
| |
| |
| | |
Change-Id: I5b76be2d7d5d9754974295fce81b26498ccee391
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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: I38ed9cc72108c290a3f74c4bbc08ae37a56efa4f
|
| |
| |
| |
| | |
Change-Id: Ica5b5c3035c6e5ff2756564fa3d894ba8a6d24bd
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* ril: update ril header to v11
from https://github.com/ArchiDroid/android_device_samsung_i9300/commit/706bc3c354d2f6d6d905e6a26ccee282357c26ee
* ril: LCE support
* set BOARD_RIL_CLASS and add SamsungExynos4RIL
* add Samsung symbols shim library
* use ril-wrapper to stop libsec-ril from crashing
(based off dmitry-ril for the Nexus S)
Change-Id: I169024341621ea05db5b8d8e82c4bf958b7bc6c0
|
| |
| |
| |
| | |
Change-Id: Ia8b8eeb35ee487c4b3729765e4c7ef79e7894eb2
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
rootdir/init.target.rc
Change-Id: I76d330088c9fcf6e6ce20388980293d366af2997
|
| |
| |
| |
| |
| |
| |
| | |
This property was used in GB to work around a hardcoded list of
interfaces in MobileDataStateTracker and is no longer required.
Change-Id: Iaba910f52331079ab19ba05c2d2fc6586f895231
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
i9300: selinux updates for cm12
Change-Id: I724a1acb4724ae34e60881da4708f7fbc98080ad
i9300: Selinux updates
Change-Id: I4e31d24c2eefcfdffa49cf1ee7468498200bb83c
|
| |
| |
| |
| | |
Change-Id: I8891182a084c9b05c3203b8bc8aeb1c066f6a60d
|
| |
| |
| |
| | |
Change-Id: I1fb529396f7a039bf9843368f4f1b5036c889e82
|
| |
| |
| |
| |
| |
| |
| | |
The phone app isn't relevant anymore, the overlays were switched to
the Telephony overlays, so this change was needed
Change-Id: I469a40f3ba023b8b0f356b289dd3e62b5659ff28
|
| |
| |
| |
| |
| |
| |
| | |
the standard value for high brightness changed to false. the i9300 supports that feature.
so it should be enabled.
Change-Id: Ibf67bbff5f7c3f5e9a0277b42206eece48bc5de4
|
| |
| |
| |
| |
| |
| | |
Change-Id: Ic38fca9b0972e2e54b2972c4800e675203e2f04e
JIRA: CYAN-4539
Issue: https://jira.cyanogenmod.org/browse/CYAN-4539
|
| |
| |
| |
| |
| |
| | |
It's taken from the old wrapper and works just fine.
Change-Id: I4c6f5c040f5c4612d4694611b62417c7521dca84
|
| |
| |
| |
| |
| |
| |
| |
| | |
After stopping a video record, the camera preview was always freezing
with the cm camera. With the google camera, the whole camera even crash and
you could not connect to the camera anymore. This commit fixes the issue.
Change-Id: Ic2b6e626e983fcd9d5c7e73ad99b27e5afd16dc7
|
| |
| |
| |
| | |
Change-Id: Id5c0f45bfaa7a89db0979e51d0740e298a9c15f9
|
| |
| |
| |
| |
| |
| | |
This reverts commit 7c9742c6af99b5a395fe8b8a2d99e3f9676aa808.
Change-Id: Icf8f4024c92537e1fde1e17191196135e28cbf9a
|
| |
| |
| |
| |
| |
| | |
Subclass it into "vendor" to allow the wrapper to load it
Change-Id: I3e541eba02cf514eba72b9dd699c87825bd5617d
|
| |
| |
| |
| | |
Change-Id: I2ab420398de6b0f6d6bb994d1c87843acba4c9da
|
| |
| |
| |
| | |
Change-Id: I9a457b7bab327a9252cf13a6ee46517063f603fa
|
| |
| |
| |
| | |
Change-Id: Ia6a0a358ec5152742ab5b65236cc527ec70b8688
|
| |
| |
| |
| | |
Change-Id: I3dc4762de2b321f3d01d6d6c07ec5fba33fb90e5
|
| |
| |
| |
| |
| |
| | |
These are now declared in the global sepolicy
Change-Id: I2861d939a43e0f7b736534006b83505fe52fbd35
|
| |
| |
| |
| |
| |
| |
| | |
Add compatibility libutils symbols required by it, and use it
again. It's much more reliable than the reimplementation
Change-Id: Ic837f4688015a956d635f0cf6b9846c24265a4e1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
http://review.cyanogenmod.org/61104 has reverted http://review.cyanogenmod.org/51085
which has bought back issues with microphone after a voice call. After a voice call,
the microphone is either not working or the recorded audio is very faint and not
audible.
The Input device has to be explicitly set to AUDIO_DEVICE_NONE after a voice call,
since force_all_standby() wouldn't work for a voice call usecase.
More details about the fix is included in the gerrit comments for the actual patch.
Change-Id: I87c63b0ec4390ec3e5703e1de5804c10289ee423
|