i'm also looking to this sensors.qcom error except i rather would like to find the reason for its behavior.

i don't see errors when enabling debug for sensorfwd
(it are exactly the same things that appear in journalctl -af on jolla phone and on nexus5)

temporary disabled sensors.qcom in init.hammerhead.rc for now

i've seen that in cm 13 and 12.1 the build.prop fiole has changed.

it's nor longer ro.qc.sensor.xxx but it's now ro.qti.sensors.xxx
i would like to find a way to disable each specific sensors to find which one exactly is the reason for the high cpu usage

someone else a suggestion to achieve this?

regards