New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overheat issue #1
Comments
the default config seems very conservative (does nothing until CPU temperature exceeds 85 degrees) & does not limit gpu frequency: debug [SS-CPU2-3] [SS-CPU0-1] [CPU2-3_MONITOR] [CPU0-1_MONITOR] `` |
it seems the thermal-engine.conf from huawei stock firmware does not work. I don't know why. 07-25 23:50:12.378 I/ThermalEngine( 6952): Thermal daemon started |
07-25 23:50:12.380 E/ThermalEngine( 6952): update_cpu_topology: Error reading cluster info node /sys/module/msm_thermal/cluster_info looks like this /sys/module/msm_thermal/cluster_info exists in the stock kernel, but not in cyanogenmod version: root@Che1:/sys/module/msm_thermal # ls -l there are also things like this: and stuff like /sys/module/qpnp_adc_voltage/parameters/therm_cpu also exists in stock kernel (but not cyanogenmod kernel). |
just a quick test before I give up - MoKee also overheats in a short time (same as cyanogenmod). |
a little weird - I deleted thermal-engine and HwPowerGenieEngine3 from the original stock android 5.1 firmware and it still does not overheat (even after 30 minutes of 3D game). |
I have taken real reading from adb device..that means every sensor reading..now I need to compare this reading with default thermal-engine.conf..what is meant by mitigation?I 'll take mitigation from where... |
I need to give better configuration In my hand real time values of all sensor temperature reading is there...I need to compare this one to mitigation value...how I 'll check ?what action its taking?I need qualitative analysis... |
Figure out all sensor board? |
When running cyanogenmod the device is VERY easy to overheat compared to the stock firmware, and my device is now at the service center possibly due to this issue (motherboard damaged). :(
Maybe adding the thermal-engine.conf from stock firmware will help (thermal-engine.conf does not exist in CyanogenMod), however as my device hasn't been repaired & sent back yet so I can't test it for now.
The text was updated successfully, but these errors were encountered: