Phone: d2lte (Verizon S3 unlocked)
Rom: CM11 M10
Kernal: default CM11
Radio/firmware: MB1
Issue - Seemingly at random, "sec-ril" will kill my CPU and continue hogging until I completely power off and pull the battery. I simple reboot alone will not fix the issue.
By using developer tools > show CPU usage, you can easily see what is hogging the CPU, and "sec-ril" is the culprit. I cannot nail down when it starts or if there's a specific app or process that is triggering it to go crazy. I know this is related to the "radio interface layer" but that's about the extent of it. Investigating wake locks has not led me anywhere, this isn't really a wakelock issue, this is a internal system process going crazy on my CPU.
I cannot go back to TW, it's awful. I also cannot try flashing a different firmware/radio since if I do, this breaks SMS for me, where I can only send 1 text, and all subsequent text's will refuse to send. I have to either cycle airplane mode or reboot to send another text.
I cannot go try CM11 M11 or M12 since this breaks GPS for me and results in MMS media text's not receiving.
Given my limitations, has anyone found a solution other than a battery pull? The only thing I haven't tried yet is another kernel.
Rom: CM11 M10
Kernal: default CM11
Radio/firmware: MB1
Issue - Seemingly at random, "sec-ril" will kill my CPU and continue hogging until I completely power off and pull the battery. I simple reboot alone will not fix the issue.
By using developer tools > show CPU usage, you can easily see what is hogging the CPU, and "sec-ril" is the culprit. I cannot nail down when it starts or if there's a specific app or process that is triggering it to go crazy. I know this is related to the "radio interface layer" but that's about the extent of it. Investigating wake locks has not led me anywhere, this isn't really a wakelock issue, this is a internal system process going crazy on my CPU.
I cannot go back to TW, it's awful. I also cannot try flashing a different firmware/radio since if I do, this breaks SMS for me, where I can only send 1 text, and all subsequent text's will refuse to send. I have to either cycle airplane mode or reboot to send another text.
I cannot go try CM11 M11 or M12 since this breaks GPS for me and results in MMS media text's not receiving.
Given my limitations, has anyone found a solution other than a battery pull? The only thing I haven't tried yet is another kernel.
from xda-developers http://ift.tt/1BQSxHu
via IFTTT
Aucun commentaire:
Enregistrer un commentaire