Two quite common wakelocks we have: msm_hsic_host and qcom_rx_wakelock.
First one is related with the modem itself, while the second one related with the wifi driver.
From what I could see, there's no easy way to fix the issue with msm_hsic_host, and this is a common issue with default android as well. Many people tried to fix this wakelock, but the issue keeps coming back, so I'd guess we don't have much to do here.
Also tried CM-11 kernel, and the behavior is similar.
One thing I know for sure is that we're currently not requesting the modem to enter in low-battery mode when turning the screen off, and that might be helping the wakelock to be around longer than needed.
As this device is not officially supported by our kernel team (besides critical security fixes), not going to spend much more time on it. Please raise this issue with the kernel team if you think this is a blocker for you.
Two quite common wakelocks we have: msm_hsic_host and qcom_rx_wakelock.
First one is related with the modem itself, while the second one related with the wifi driver.
From what I could see, there's no easy way to fix the issue with msm_hsic_host, and this is a common issue with default android as well. Many people tried to fix this wakelock, but the issue keeps coming back, so I'd guess we don't have much to do here.
Also tried CM-11 kernel, and the behavior is similar.
One thing I know for sure is that we're currently not requesting the modem to enter in low-battery mode when turning the screen off, and that might be helping the wakelock to be around longer than needed.
As this device is not officially supported by our kernel team (besides critical security fixes), not going to spend much more time on it. Please raise this issue with the kernel team if you think this is a blocker for you.