SensorListener in some Android applications running into a hot loop
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Anbox Cloud |
Fix Committed
|
Medium
|
Gary.Wang | ||
Bug Description
When running the Marvel Battle application, the following logs flooded the Anbox logcat:
...
06-13 12:12:16.403 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.408 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.413 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.419 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.424 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.429 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.434 3221 3221 D SensorMonitor: Temperature Sensor value changed
06-13 12:12:16.440 3221 3221 D SensorMonitor: Temperature Sensor value changed
...
...
This indicates that the sensor data was sent to the emulated sensor HAL modules unexpectedly frequently, which caused a hot loop in both the Android framework and the Android application.
| Changed in anbox-cloud: | |
| milestone: | none → 1.23.0 |
| assignee: | nobody → Gary.Wang (gary-wzl77) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
