4998c16c927003f5bd98427db5f58853b170aa8a |
|
01-Nov-2016 |
Grigory Dzhavadyan <grigoryj@google.com> |
Fix min delay for virtual geomag vector sensor bug: 31808374 N-CTS requires this to be <= 10 ms Change-Id: I0959fa2cb9ae40bc832726fedccc77366aba1520 (cherry picked from commit f1a9141f72fc73af0485d12f5e4b5b176dbe9f34)
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
f66684a6fb2a2991e84a085673629db2a0494fc6 |
|
23-Jul-2015 |
Peng Xu <pengxu@google.com> |
Add AOSP Geomag and Game Rotation, and Gravity Providing AOSP software implementation of Geomag Rotation Vector, Game Rotation Vector and Gravity sensors for platforms that does not have hardware implementation of these sensors but do have primitive sensors (accelerometers, gyrometers and magnetometers). Previously, AOSP Gravity sensor is enabled only when all primitive sensors are available. This is changed so that AOSP Gravity will be available even no magnetometer is in the device. Related bug/feature request: * b/17508800 * b/22610016 Change-Id: I4e2d3e544884047d66e7fdbce2282f1f8234eae9
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
d4dabf872ac0a12e12aebae9032f7d62762c2aeb |
|
13-Mar-2014 |
Mark Salyzyn <salyzyn@google.com> |
am cdbf28b3: Merge "native frameworks: 64-bit compile issues" * commit 'cdbf28b3f7f5327f4cb0eb95b8326bf4c24c87ba': native frameworks: 64-bit compile issues
|
92dc3fc52cf097bd105460cf377779bdcf146d62 |
|
12-Mar-2014 |
Mark Salyzyn <salyzyn@google.com> |
native frameworks: 64-bit compile issues - Fix format (print/scanf) - Suppress unused argument warning messages (bonus) Change-Id: I05c7724d2aba6da1e82a86000e11f3a8fef4e728
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
ebff73c37d5f1581702430f4a0348c160b99b57e |
|
06-Dec-2013 |
Aravind Akella <aakella@google.com> |
Bug fix for SensorFusion data rate. SensorFusion is always returning data at the slowest possible sampling rate (5 Hz). batch() is getting called twice, first time with the requested rate and second time with the slowest rate (which overwrites the requested rate). Fix batch call in SensorFusion::activate() Bug: 12064319 Change-Id: If62f3e514233f69810336fd22b136b4395b667d3
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
bf72deea2f9982a09c6a95f94cfa1654bc8c684f |
|
17-Sep-2013 |
Aravind Akella <aakella@google.com> |
Fix for AOSP fusion sensors not handling multiple clients correctly. Bug: 10786801 Change-Id: I7b938bc583a303a30237c3d93b5accbf64cc90b5
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
724d91d778e71c8186399f4955de14b54812b3ed |
|
27-Jun-2013 |
Aravind Akella <aakella@google.com> |
Sensor batching. Changes to the native code. Bug: 10109508 Change-Id: I7333f3aac76125a8226a4c99c901fb904588df04
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
ba02cd2f6cc3f59adf66cb2b9176bfe6c9e382d1 |
|
04-Jul-2013 |
Mathias Agopian <mathias@google.com> |
improve sensorservice's dumpsys it now displays the reported trigger mode properly, as well as the number and type of the last received data Change-Id: I2ff64b32ab71f1332bc2e09671c8c02bb9550490
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
2e2a560c4b60c24258e0eaadc1189eb9dcc1a0b4 |
|
30-May-2013 |
Mathias Agopian <mathias@google.com> |
use gyro timestamp directly in fusion we used to estimate the gyro rate and deduce the period from that but it turns out this is causing problems. Bug: 5192288 Change-Id: I8ca826d0e11e488587bcaa1720de99e92b82f191
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
0319306670b0344da99efa606b6f172dde575a39 |
|
11-May-2013 |
Mathias Agopian <mathias@google.com> |
various fixes to the sensorservice 1) "google" sensors are now reporting AOSP as the vendor string 2) don't expose the system's sensor fusion if the HAL provides it 3) use uncalibrated gyro if availble for the system's sensor fusion Change-Id: I25140436cdb29d55e39fd6fbbf8c44a410a83d5c
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
a551237de142549fb8a6608ee9d2fbf4b7ca2ebf |
|
20-Dec-2011 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGD(_IF) to (IF_)ALOGD(_IF) DO NOT MERGE See https://android-git.corp.google.com/g/156016 Bug: 5449033 Change-Id: I4c4e33bb9df3e39e11cd985e193e6fbab4635298
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
7b2b32f2e761a919deb6f82d978b379429f77b05 |
|
15-Jul-2011 |
Mathias Agopian <mathias@google.com> |
sensorservice: be more robust when there are no sensor h/w Bug: 5030108 Change-Id: I45b85b3c492b9268cb0ae44d2e5fc8c708b6e66e
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
3301542828febc768e1df42892cfac4992c35474 |
|
28-May-2011 |
Mathias Agopian <mathias@google.com> |
use quaternions instead of MRPs also use correct time propagation equation disable the fused sensors when gyro is not present since they were unusable in practice. Change-Id: Iad797425784e67dc6c5690e97c71c583418cc5b5
/frameworks/native/services/sensorservice/SensorFusion.cpp
|
984826cc158193e61e3a00359ef4f6699c7d748a |
|
18-May-2011 |
Mathias Agopian <mathias@google.com> |
9-axis sensor fusion with Kalman filter Add support for 9-axis gravity and linear-acceleration sensors virtual orientation sensor using 9-axis fusion Change-Id: I6717539373fce781c10e97b6fa59f68a831a592f
/frameworks/native/services/sensorservice/SensorFusion.cpp
|