6a2d3a06caa337857cf60cfc70a9a78909ad3608 |
|
21-Dec-2015 |
Peng Xu <pengxu@google.com> |
Fix sensor uuid, retrofit recent event logger Fix an issue that causes uuid field not being initialzed in sensorservice. MostRecentEventLogger in sensorservice is migrated to use RingBuffer instead of a custom circular buffer. This is expected to improve readability and maintainability of code. Dumpsys print format is retouched to offer more information in easier to read format. Bug: 28305085 Change-Id: I190e43350b60a22a9fccb92a95d6eab06a471560
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
755c451c7861a029e26e5f16e319b629169e656d |
|
08-Apr-2016 |
Peng Xu <pengxu@google.com> |
sensorservice: switch to use sp<> in sensor list * Switch to use smart pointer in SensorList to avoid object life cycle issue. * Refactor HardwareSensor and various virtual sensor class. * Change active virtual sensor map into a set of handles. Change-Id: I674d5eb5c0038179f9ef1b6f0d576b8b605649ec
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
0cc8f809924706c7d683da30605f432635dd5bb6 |
|
06-Apr-2016 |
Peng Xu <pengxu@google.com> |
Refactor sensor list in SensorService Refactor sensor lists management logic in sensorservice: * Factor all sensor list management code into a separate class. * Remove error-prone repeated sensor lists. * Solve synchronization issue when sensor is added or removed during runtime. * Switch to STL containers. Bug: b/27911774 Change-Id: I94d5571e1fa3166dbe893ffac2a2a7584be6349c
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
d9441e4c27bb7d0b1dfe2a8b5c1ee1714442648d |
|
14-May-2014 |
Aravind Akella <aakella@google.com> |
Surface maxDelay and isWakeUpSensor flag in Sensor.java. Change-Id: Idd1e9045190beeca87b086b272e8cbf0bed05bae
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
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/SensorInterface.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/SensorInterface.cpp
|
ac9a96da65f6eae4513654adaad8a457d1c1575c |
|
12-Jul-2013 |
Mathias Agopian <mathias@google.com> |
fix a dead-lock in sensorservice sensorservice would deadlock if for some reason a sensor failed to enable. simplifed the code a bit, and made it behave a little closer to mr1.1 -- I couldn't convince myself that some changes in how locks were used were correct. Bug: 9794362 Change-Id: I6110f5dbb67e543f1c71d127de2299232badb36a
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
4c01b1ad80e084f0cd1057f89fdd1fcedf19dd96 |
|
17-Apr-2013 |
Jaikumar Ganesh <jaikumar@google.com> |
Fix activation issue with auto disabled sensors. Auto disabled sensors get auto disabled after trigger. An activation after this wasn't working because the state was not being reset. b/8609561 Change-Id: If72c9f27345e91671d7ad0a7a066f6dc3d255b78
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
c7839e897646ece32894d3b7d1685c3880d949fe |
|
04-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGI(_IF) to (IF_)ALOGI(_IF) DO NOT MERGE See https://android-git.corp.google.com/g/156801 Bug: 5449033 Change-Id: Ib08fe86d23db91ee153e9f91a99a35c42b9208ea
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
50b66767f6c5635430483393e17d15969dfe2f05 |
|
30-Nov-2010 |
Mathias Agopian <mathias@google.com> |
fix [3237242] sensormanager sensor active count gets out of sync whether a physical sensor needed to be active or not was managed by a simpe reference counter; unfortunatelly nothing prevented it to get out of sync if a sensor was disabled more than once. sensorservice already maintainted a list of all the "clients" connected to a physical sensor; we now use that list to determine if a sensor should be enabled. This can never be "out-of-sync" since this is the only data structure linking a sensor to a user of that sensor. also removed the isEnabled() method, which was never used and implemented wrongly (since it didn't take into account that a sensor could be disabled for a client but not of another). Change-Id: I789affb877728ca957e99f7ba749def37c4db1c7
/frameworks/native/services/sensorservice/SensorInterface.cpp
|
f001c92436b4a66eb7687286325ced7f10c9f917 |
|
12-Nov-2010 |
Mathias Agopian <mathias@google.com> |
Add support for virtual sensors. Rework sensorservice to allow "virtual sensors", that is sensors that report a synthetized value based on real sensors. the main change to sensorservice is around managing which real sensor need to be activated and which rate to use. The logic for all this has been moved into SensorDevice, which essentially wraps the sensor HAL but adds two features to it: - it keeps track of which sensors need to be activated - it keeps track of what rate needs to be used For this purpose an "identity" is associated with each real sensor activation, so we can track them. On start-up we check for gravity, linear-acceleration and rotation-vector sensors, if they're not present in the HAL, we synthetize them in sensor-service. Change-Id: I841db2c1b37ef127ed571efa21732ecc5adf1800
/frameworks/native/services/sensorservice/SensorInterface.cpp
|