Related
What are people using for their setCPU settings? I'm just now rooting and will be installing this to help with battery life. Unless for some reason this isn't necessary on the S3. It was essential on the S2 (in my opinion) to keep my battery life going longer.
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
stalked_r/t said:
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
Click to expand...
Click to collapse
How well does it work if you're playing music and the screen is off?
I use 384 for both max & min when screen off and it works just fine for music player I have.
Sent from my SCH-I535 using Tapatalk 2
I don't have any music on my phone. I just use Pandora for everything, though i should probably put something on my phone.
stalked_r/t said:
I'll start it off apparently!
Not messing with any governor, just the profiles.
Charging - CPU can run at 1512 max, 594 min - priority 100
Screen Off - CPU max of 594, min 384 - priority 99
Battery <80% - CPU max of 1242, min 594 - priority 80
Battery < 60% - CPU max of 810, min 384 - priority 60
Battery < 50% - CPU max of 594, min 384 - priority 50
No profile is exclusive
Click to expand...
Click to collapse
What at are you using to set all this? Have you noticed any improvement in battery life of issues with apps running/ starting/ crashing??
ssnapier said:
What at are you using to set all this? Have you noticed any improvement in battery life of issues with apps running/ starting/ crashing??
Click to expand...
Click to collapse
I just set this up this morning and my phone has been sitting in my dock at work, so i can't say for sure about battery life. As for apps. I've not noticed a single problem. Again, I rooted my phone last night, so I don't have a ton of apps on my phone. Currently I have
Waze
Pandora
One More Clock
SetCPU
Betterbatterystats
MetroStation Icon Pack
Apex Launcher
NFC Task Launcher
Mynetdiary
Rom Manager Pro
Zedge.
Most of those are supporting apps. so it's hard to say if anything is flaking out yet. I'll slowly add more apps. I'm going to start a thread about known battery drain apps so we can start identifying those.
My Settings
Here are some settings I use that seem to work well for me. Id say these settings aren't the most conservative but they aren't battery hungry either. I didn't mess with any of the governors or voltages I just simply added these profiles to control my leankernel. Hope this helps! -Cheers
Screen Off
810 max
384 min
OnDemand
Priority 58
Charging
1900 max
384 min
OnDemand
Priority 54
Battery < 60
Condition Screen On
1026 max
384 min
OnDemand
Priority 53
Battery < 40
810 max
384 min
OnDemand
Priority 52
Gaming
Condition Screen On
1900 max
1026 min
OnDemand
Priority 57
Web
Condition Screen On
1512 max
1026 min
OnDemand
Priority 55
Default
1900 max
384 min
OnDemand
Dont click "make this profile exclusive"
*This gives you a default profile notification
[PHONE] Samsung Galaxy S III i535
[ROM] CM10 M1 9/11 w/ 7/26 GApps
[KERNEL] imo leankernel 0.13
[MODEM] I535VRLG7
[EXTRAS] turning heads with Google Wallet
Set CPU
Do these settings still work good for you? I entered them into my SG3 so will see how it goes for the next few days. I am really looking for battery life more than anything.
thanks
THISisTIG said:
Here are some settings I use that seem to work well for me. Id say these settings aren't the most conservative but they aren't battery hungry either. I didn't mess with any of the governors or voltages I just simply added these profiles to control my leankernel. Hope this helps! -Cheers
Screen Off
810 max
384 min
OnDemand
Priority 58
Charging
1900 max
384 min
OnDemand
Priority 54
Battery < 60
Condition Screen On
1026 max
384 min
OnDemand
Priority 53
Battery < 40
810 max
384 min
OnDemand
Priority 52
Gaming
Condition Screen On
1900 max
1026 min
OnDemand
Priority 57
Web
Condition Screen On
1512 max
1026 min
OnDemand
Priority 55
Default
1900 max
384 min
OnDemand
Dont click "make this profile exclusive"
*This gives you a default profile notification
[PHONE] Samsung Galaxy S III i535
[ROM] CM10 M1 9/11 w/ 7/26 GApps
[KERNEL] imo leankernel 0.13
[MODEM] I535VRLG7
[EXTRAS] turning heads with Google Wallet
Click to expand...
Click to collapse
Is there an app that allows you to monitor the GPU? Im currently playing with the clockspeeds, voltages and thresholds and would like to be able to monitor the results.
Can only set 4 steps with the kernal I have the following settings at the moment.
160 - 837500
350 - 912500
440 - 962500
533 - 1025000
1 up - 90
2 down - 41
2 up - 90
3 down - 70
3 up - 90
4 down - 73
Can only select frequencies of 160, 266, 350, 440 and 533, which is why i've selected the ones I have. Im hoping it will sit at 160, 350 the majority of the time unless im gaming and have set the thresholds so that the over lap to hopefully prevent unessesary jumping between frequencies. Trying to balance performance and power consumption.
If I find it works well, then I'll then look to undervolt.
From a shell:
Code:
$ cat /proc/loadavg
1.60 1.31 1.26 2/1446 19315
According to a.o.
https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-proc-loadavg.html, 2/1446 means that I have 2 CPUs and 1446 tasks waiting to be run.
1446 tasks? On a heavily loaded workstation I seldom see more than a couple of 100 tasks. A simple server shows just over 100 tasks. So how come the Note has so many tasks? Besides,
Code:
$ps|wc -l
224
Given that I sometimes get load values of around 80 I start getting doubts that the numbers produced by /proc/loadavg are useful.
Does anyone have any ideas what could cause these high numbers for loads and tasks?
sciurius said:
Does anyone have any ideas what could cause these high numbers for loads and tasks?
Click to expand...
Click to collapse
Threads. Run "adb shell top -t" and you'll break out each thread:
Code:
User 31%, System 4%, IOW 0%, IRQ 0%
User 111 + Nice 297 + Sys 62 + Idle 828 + IOW 0 + IRQ 0 + SIRQ 0 = 1298
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
3670 11496 2 22% R 504052K 49724K bg u0_a25 MediaScannerSer android.process.media
11192 11192 1 1% R 1792K 1164K shell top top
9091 9114 0 1% S 487544K 40000K bg u0_a170 Thread-416 com.mobidia.android.mdm:remote
2342 5579 3 1% S 701848K 101820K fg system Binder_D system_server
2342 2342 1 1% S 701848K 101820K fg system system_server system_server
2342 2430 0 0% S 701848K 101820K fg system ActivityManager system_server
2342 4431 1 0% S 701848K 101820K fg system Binder_A system_server
3957 4175 0 0% S 549604K 47424K bg u0_a16 NetworkLocation com.google.process.gapps
2342 3887 1 0% S 701848K 101820K fg system Binder_5 system_server
7563 7563 2 0% S 492308K 37216K fg u0_a39 ndroid.calendar com.google.android.calendar
2342 5594 2 0% S 701848K 101820K fg system Binder_E system_server
3555 3555 3 0% S 534276K 67664K fg u0_a121 ndroid.systemui com.android.systemui
2342 4165 1 0% S 701848K 101820K fg system Binder_6 system_server
690 690 0 0% S 0K 0K root ksmd
<snip>
I see. I'm used to applications that have one or two threads, but a typical Android app seems to have at least 10. That adds up quickly.
my phone keeps on overheating as I am playing clash of clans for a prolonged period of time. is there any way to fix it? i am running purity rom with franco kernel.
onecrzyasian said:
my phone keeps on overheating as I am playing clash of clans for a prolonged period of time. is there any way to fix it? i am running purity rom with franco kernel.
Click to expand...
Click to collapse
describe "overheating". what cpu temp is it reaching?
Hi,
Another one...
You have a quadcore at 2,26 Ghz device, under certain conditions (heavy games, browsing in 4g, long run heavy tasks, etc...) it's absolutely normal that the phone runs hot... And you sais it by yourself "I am playing clash of clans for a prolonged period of time."...
In any case there is a thermal protection called thermal throttling that reduces the CPU freq, the number of cores online and the screen brightness when the CPU (and/or battery) reaches some different temperature ranges, so no worries...
And even if Franciscofranco modified the thermal management, the thermal throttle is always present (you can also adjust it to reduce the heat by decreasing the CPU temp limit before thermal throttling).
But guys... in all scenarios there is the thermal throttling, and it does its job when needed. In extreme conditions the phone shutdown itself to prevent any damage. This CPU can handle more than 100 °C. Use your phone as normal, as you need... Or don't use GPS, don't play games, don't run benchs...
As an example on how thermal throttling works:
Code:
sampling 5000
[battery_LCD_monitor]
algo_type monitor
sensor batt_therm
sampling 10000
thresholds 100000 340000 350000 360000 370000
thresholds_clr 50000 330000 340000 350000 350000
actions override override override override override
action_info 10000 7500 5000 2500 0
[SKIN_THERMAL_management_1]
algo_type monitor
sensor xo_therm_pu2
sampling 10000
thresholds 40000 42000 44000
thresholds_clr 38500 40500 42500
actions cpu+lcd cpu+lcd cpu+lcd
action_info 1958400+229 1574400+204 1190400+178
[battery_monitor]
algo_type monitor
sensor batt_therm
sampling 10000
thresholds 480000 550000
thresholds_clr 460000 500000
actions battery battery
action_info 2 3
[CPU0_MONITOR]
algo_type monitor
sensor cpu0
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU1_MONITOR]
algo_type monitor
sensor cpu1
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU2_MONITOR]
algo_type monitor
sensor cpu2
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[CPU3_MONITOR]
algo_type monitor
sensor cpu3
sampling 65
thresholds 115000
thresholds_clr 110000
actions shutdown
action_info 0
[HOTPLUG-CPU1]
algo_type monitor
sensor cpu1
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_1
action_info 1
[HOTPLUG-CPU2]
algo_type monitor
sensor cpu2
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_2
action_info 1
[HOTPLUG-CPU3]
algo_type monitor
sensor cpu3
sampling 65
thresholds 105000
thresholds_clr 85000
actions hotplug_3
action_info 1
[PID-CPU0]
disable 1
[PID-CPU1]
disable 1
[PID-CPU2]
disable 1
[PID-CPU3]
disable 1
[PID-POPMEM]
disable 1
[SS-CPU0]
algo_type ss
sampling 65
sensor cpu0
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU1]
algo_type ss
sampling 65
sensor cpu1
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU2]
algo_type ss
sampling 65
sensor cpu2
device cpu
set_point 80000
set_point_clr 55000
[SS-CPU3]
algo_type ss
sampling 65
sensor cpu3
device cpu
set_point 80000
set_point_clr 55000
[SS-POPMEM]
algo_type ss
sampling 65
sensor pop_mem
device cpu
set_point 80000
set_point_clr 55000
time_constant 16
It's a quadcore at 2,26 Ghz completely enclosed without any additional cooling system, so...
It remembers me the Nexus 4 all these threads/questions about "pseudo" heating/overheating...
Like simms22 said check your temperatures and provide them to have an approach a bit more real, because "it feels hot", "it is overheating", etc... is very subjective (for example I go outdoor with a 2 °C room temperature, I take my phone stays indoor and I feel it "hot", I check the CPU temperature and it's at about 30 °C...if you know what I try to say even if it's not your case here but it's a general idea).
Also you provide more information like overclock? Undervolt? Governor (even if in Franciscofranco kernel there is only Interactive and Performance)?
I am not sure what the temp was before it shut down, but i shall try lowering the throttle temp
onecrzyasian said:
I am not sure what the temp was before it shut down, but i shall try lowering the throttle temp
Click to expand...
Click to collapse
Re,
Because your phone shutdown when you were playing? You did not mentioned it in the OP... (it could be caused by another things too, undervolt, kernel panic, etc...).
Before shutdown, it's the ultimate thermal protection, the CPU freq decreases according to different CPU/battery temperatures to cool down the CPU (thermal throttling)... Post a last_kmsg if you have a hard-reboot to see... Post it in the kernel thread, here, or in this thread: http://forum.xda-developers.com/showthread.php?t=2532422.
Ivanichs CM12 3.4 Kernel Overclocked by Little Lerroyy [IN-TESTING]
Disclaimer
Each kernel release, I will be pre testing on my device first, to ensure adequate stability. However by the use of this kernel, I claim no responsibility to any damaged devices due to the risky nature of overclocking. I recommend that you DO NOT USE THIS KERNEL if you want rock solid stability!
Credits
I won't be taking full credit for this, as a matter of fact, i will only take very little as this kernel is based 100% from Ivanichs CM12 kernel for the sensation. While I only simply transplanted the overclocking code from Sultanxda and SebatianFM kernels to Ivanichs with my touch of voltage tweaks.
Features
In kernel thermal throttling (MSM_THERMAL). Please thank javelinanddart for this amazing fix!
CPU OC to 1890MHz
GPU 3D OC to 320MHz
GPU 2D OC to 228MHz
BUS/Memory OC for overclocked frequencies from 310MHz to 400MHz
CPU Voltage interface. Select your own VCore!
Various idle underclocks and undervolts to improve batterylife
Included sultanxda's panel undervolt interface
Various I/O Scheduler & I/O read aheads and CPU Govenor tweaks for awesome snappiness.
Compiled with Linaro GCC Compiler optimized for Cortex A8.
Bugs (Major)
Device will reboot when entering airplane mode before screen is switched off and then back on again.
Thermal Daemon will set absolute top frequency 1.89GHz when returning from a CPU throttle due to high temperature. In this case some devices can't handle 1.89 and will either reboot eventually or instantly reboot. Hinxnz has provided and excellet workaround for this. - fixed by javelinanddart!
Notes
I recommend that you DO NOT USE THIS KERNEL if you want rock solid stability! Kernel is still currently in testing.
I would recommend only use 1.89GHz and 1.944GHz for benchmarking. I have set the voltages for those frequencies to 1.3v and a monstrous 1.375v respectivly to maintain device from instantly crashing.
My Device only stable on 1836MHz with a moderate 1.25v on the core (This is device depandant)
Source
Kernel Source (GitHub)
Download Link
Google Drive
XDA:DevDB Information
CM12 Overclocked 3.4 Kernel for HTC Sensation, Kernel for the HTC Sensation
Contributors
little_lerroyy
Source Code: https://github.com/littlelerroyy/android_kernel_htc_pyramid
Kernel Special Features: OC Up To: CPU = 1890MHz, GPU3D = 320MHz, GPU2D = 228MHz, L2 Cache = 1.6GHz
Version Information
Status: Testing
Created 2015-03-07
Last Updated 2015-08-12
Changelog
1/8/15
In kernel thermal throttling!!! No more thermal daemon issues! Please give your most thanks to javelinanddart for his amazing fix!
ramdisk file updated to work with the latest versions of CM12.1
Also up-to-date with ivanichs changes.
23/4/15
Increased CPU input boost duration to 300mhz to smooth out UI, and reduced the possibility of intelliactive ramping CPU to max frequency unnecessarily.
Tweaked intelliactive govenor to be less aggressive. It was going to full speed too often and ramping while idling. Phone runs much cooler due to this change and the above
Reduced BUS speed for upper standard CPU frequencies.
Underclocked idle frequency bus from 103MHz to 80Mhz. We dont need performance at idle! We could go lower.
Undervolted L2 cache for idle frequencies. 1.1V -> 1.075V. We could go lower.
Sultanxda panel undervolting sysfs interface added. Navigate to "/sys/module/board_pyramid_panel/parameters/panel_uv", where "panel_uv" is a value between 0 and 700mV to undervolt the panel by (stock panel voltage is 3100mV). Increments of 25mV only accepted
Very basic flashable ZIP made.
19/4/15
Reverted to old CPU Vcore table. The old Undervolted table didn't suit some devices.
Added CPU VCore interface. You can now change CPU voltages within android. Range: (1.35V - 0.7V)
Reverted to stock GPU2D BUS. Noticed no difference with it raised.
Increase Max current intake to 1250mA. Charging should be quicker with >1000mA chargers. (im not sure if I will keep this as i do notice a hotter phone while charging)
Dropped all partitions to 0KB readhead. People should notice a even more snappier phone.
6/4/15
Tested with CM12.1
Overclocked system bus from 310MHz to 400MHz on overclocked frequencies.
Undervolted vcore for standard frequencies. In theroy this should provide better battery life.
GPU Bus overclock
CPU will not switch off the second core while the screen is on (it will turn off when screen is off). I find this helps improve performance drastically without any noticble drop in battery life (i feel it could improve battery life)
ZRAM switched off by default. People can enable this at anytime if they want to.
Set CPU govenor to intelliactive by default. Also tuned for extra smoothness & snappiness.
Set I/O Scheduler to FIOPS as default. Optimised tunable scales to improve performance.
Dropped read ahead levels significantly for internal and external storage. I find this improves loading from storage by quite a bit.
8/3/15
Removed 1.944GHz selection to stop random crashing. I will try later to see if i can stabilize it.
Published boot.img with L2 Cache OC to 1.6GHz
7/3/15
Initial CPU OC to 1944MHz, GPU3D 320MHz, GPU2D 228MHz
Added Ivanichs ZRAM support
Hi . thanks for sharing your kernel ! but would you please re-compile it with the latest code ?! i checked your github and it doesn't contain ivanich's commits from 5th and 6th of March! because 6th of march commits enabled zRam and it must have great impact on performance ! Thanks.
francesco totti said:
Hi . thanks for sharing your kernel ! but would you please re-compile it with the latest code ?! i checked your github and it doesn't contain ivanich's commits from 5th and 6th of March! because 6th of march commits enabled zRam and it must have great impact on performance ! Thanks.
Click to expand...
Click to collapse
Thanks for the input, about a few hours ago I downloaded ivanichs changes onto my PC but havent pushed the updates yet, I will post the zRam kernel tonight
Updated to include zRAM Support
well i flashed your kernel but i always get reboots while doing heavy tasks and some times just normal tasks!! here's the last kmsg :
francesco totti said:
well i flashed your kernel but i always get reboots while doing heavy tasks and some times just normal tasks!! here's the last kmsg :
Click to expand...
Click to collapse
Thanks for sharing this!! May i ask, what CPU speed did you select and what GPU3D Freq did you select? Well just as i thought the last message in your log that it tripped over the 65deg threshold. I tested this last night and the thermal daemon isnt throttling cpu speed! I even tried editing the thermald.conf to drop to 1134MHz when over just a small 45 degrees. and it still powers on at full frequency. Im not sure if there is an issue with the thermal daemon itself, or if it has a problem with my kernel, i will be doing some more testing tonight.
The minimum cpu speed was 540 and maximum cpu speed was 1836 ! And also i hadn't overclocked the gpu !
little_lerroyy said:
Thanks for sharing this!! May i ask, what CPU speed did you select and what GPU3D Freq did you select? Well just as i thought the last message in your log that it tripped over the 65deg threshold. I tested this last night and the thermal daemon isnt throttling cpu speed! I even tried editing the thermald.conf to drop to 1134MHz when over just a small 45 degrees. and it still powers on at full frequency. Im not sure if there is an issue with the thermal daemon itself, or if it has a problem with my kernel, i will be doing some more testing tonight.
Click to expand...
Click to collapse
Haven't tried your kernel yet but will later, cheers.
Not all devices can handle over 1.7GHz and some also can't handle 320 for GPU.
Stock frequency for our CPU according to Qualcomm is 1.67GHz.
I don't think thermald is working either on ivanich's kernel, actually I think it maybe but temperature readings are incorrect when it gets hot causing thermald not to kick in. I'm not sure of this but this was my theory.
Once my phone got quite hot and I noticed that the CPU temp reading was to low for what it seemed like, when at normal temp it seems to be correct.
A dirty work around could be to lower the thresholds, even just to diagnose.
My phone doesn't normally get hot at all, so hence why I haven't reported it in ivanich's thread, this is also the first time I've seen someone else arise this too.
francesco totti said:
The minimum cpu speed was 540 and maximum cpu speed was 1836 ! And also i hadn't overclocked the gpu !
Click to expand...
Click to collapse
Okay cool, ive done some testing and i think i can mainly solve the issue by removing the 1.944GHz entry. For some reason i think it may actually call that frequency even if its not selected. Im testing it now without that entry and the phone isnt getting as hot, and havent had a crash yet, normally i do have a crash under high usage. Im going to try one last attempt to fix 1.944GHz, otherwise i will remove it and leave it for another time (if its even worth it).
hinxnz said:
Haven't tried your kernel yet but will later, cheers.
Not all devices can handle over 1.7GHz and some also can't handle 320 for GPU.
Stock frequency for our CPU according to Qualcomm is 1.67GHz.
I don't think thermald is working either on ivanich's kernel, actually I think it maybe but temperature readings are incorrect when it gets hot causing thermald not to kick in. I'm not sure of this but this was my theory.
Once my phone got quite hot and I noticed that the CPU temp reading was to low for what it seemed like, when at normal temp it seems to be correct.
A dirty work around could be to lower the thresholds, even just to diagnose.
My phone doesn't normally get hot at all, so hence why I haven't reported it in ivanich's thread, this is also the first time I've seen someone else arise this too.
Click to expand...
Click to collapse
Yeah i think there is definitely an issue with the thermal daemon, I have tried setting the first trip temp point to 40c. which the phone operates over most of the time anyway, and i have no throttling of anykind. The system keeps powering on its top frequency. In sultans rom, the thermal daemon definitely worked when overclocking. maybe i might speak to him for some answers.
Running a game for a 5 mins, but can't get temp above 65
Code:
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
ivanich said:
Running a game for a 5 mins, but can't get temp above 65
Code:
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
Click to expand...
Click to collapse
Hmm, i see. Where is the best way to alter the settings of the daemon? Ive tried thermald.conf in /etc/ folder and also /sys/devices/virtual/thermal and it wont kick in to any value i choose.
Ive been testing the kernel without 1.944GHz entry and havent had a crash at all, even with the phone raring hot. I will upload this soon
little_lerroyy said:
Hmm, i see. Where is the best way to alter the settings of the daemon? Ive tried thermald.conf in /etc/ folder and also /sys/devices/virtual/thermal and it wont kick in to any value i choose.
Ive been testing the kernel without 1.944GHz entry and havent had a crash at all, even with the phone raring hot. I will upload this soon
Click to expand...
Click to collapse
I believe that /system/etc/thermald.conf should be used for this. Lower thresholds and thresholds_clr should do the trick.
ivanich said:
Running a game for a 5 mins, but can't get temp above 65
Code:
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1412): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 1412): CPU[1] frequency limited to 1512000
Click to expand...
Click to collapse
I can't seem to bring this up in logcat, I mean it's not in there. So I guess it's not working for me.
Edit: It working, just wasn't up to temp.
This is with your kernel. Do you have the same sensor? pm8058_tz
Code:
D/ThermalDaemon( 1603): No rules to monitor sensor 'pm8058_tz' disabled: 1 num_thresholds: 0
All I get in logcat is:
Code:
D/ThermalDaemon( 1603): Thermal daemon started
D/ThermalDaemon( 1603): Threshold 0 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 1 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 2 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 3 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 0 Action Info[0] : 1134000.000000
D/ThermalDaemon( 1603): Threshold 1 Action Info[0] : 972000.000000
D/ThermalDaemon( 1603): Threshold 2 Action Info[0] : 648000.000000
D/ThermalDaemon( 1603): Threshold 3 Action Info[0] : 384000.000000
D/ThermalDaemon( 1603): Sensor '(null)' config: sampling 500000
D/ThermalDaemon( 1603): Sensor 'tsens_tz_sensor0' config: sampling 3000000
D/ThermalDaemon( 1603): 66560 61440 cpu 1134000
D/ThermalDaemon( 1603): 76800 71680 cpu 972000
D/ThermalDaemon( 1603): 87040 81920 cpu 648000
D/ThermalDaemon( 1603): 88064 83968 cpu 384000
D/ThermalDaemon( 1603): Number of cpus :2
D/ThermalDaemon( 1603): Sensor setup:[tsens_tz_sensor0]
D/ThermalDaemon( 1603): No rules to monitor sensor 'pm8058_tz' disabled: 1 num_thresholds: 0
hinxnz said:
I can't seem to bring this up in logcat, I mean it's not in there. So I guess it's not working for me.
This is with your kernel. Do you have the same sensor? pm8058_tz
Code:
D/ThermalDaemon( 1603): No rules to monitor sensor 'pm8058_tz' disabled: 1 num_thresholds: 0
All I get in logcat is:
Code:
D/ThermalDaemon( 1603): Thermal daemon started
D/ThermalDaemon( 1603): Threshold 0 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 1 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 2 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 3 Action[0] : cpu
D/ThermalDaemon( 1603): Threshold 0 Action Info[0] : 1134000.000000
D/ThermalDaemon( 1603): Threshold 1 Action Info[0] : 972000.000000
D/ThermalDaemon( 1603): Threshold 2 Action Info[0] : 648000.000000
D/ThermalDaemon( 1603): Threshold 3 Action Info[0] : 384000.000000
D/ThermalDaemon( 1603): Sensor '(null)' config: sampling 500000
D/ThermalDaemon( 1603): Sensor 'tsens_tz_sensor0' config: sampling 3000000
D/ThermalDaemon( 1603): 66560 61440 cpu 1134000
D/ThermalDaemon( 1603): 76800 71680 cpu 972000
D/ThermalDaemon( 1603): 87040 81920 cpu 648000
D/ThermalDaemon( 1603): 88064 83968 cpu 384000
D/ThermalDaemon( 1603): Number of cpus :2
D/ThermalDaemon( 1603): Sensor setup:[tsens_tz_sensor0]
D/ThermalDaemon( 1603): No rules to monitor sensor 'pm8058_tz' disabled: 1 num_thresholds: 0
Click to expand...
Click to collapse
I have the same output
Code:
[email protected]:/ $ logcat|grep ThermalDaemon
D/ThermalDaemon( 1486): Thermal daemon started
D/ThermalDaemon( 1486): Threshold 0 Action[0] : cpu
D/ThermalDaemon( 1486): Threshold 1 Action[0] : cpu
D/ThermalDaemon( 1486): Threshold 2 Action[0] : cpu
D/ThermalDaemon( 1486): Threshold 3 Action[0] : cpu
D/ThermalDaemon( 1486): Threshold 0 Action Info[0] : 1134000.000000
D/ThermalDaemon( 1486): Threshold 1 Action Info[0] : 972000.000000
D/ThermalDaemon( 1486): Threshold 2 Action Info[0] : 648000.000000
D/ThermalDaemon( 1486): Threshold 3 Action Info[0] : 384000.000000
D/ThermalDaemon( 1486): Sensor '(null)' config: sampling 500000
D/ThermalDaemon( 1486): Sensor 'tsens_tz_sensor0' config: sampling 3000000
D/ThermalDaemon( 1486): 66560 61440 cpu 1134000
D/ThermalDaemon( 1486): 76800 71680 cpu 972000
D/ThermalDaemon( 1486): 87040 81920 cpu 648000
D/ThermalDaemon( 1486): 88064 83968 cpu 384000
D/ThermalDaemon( 1486): Number of cpus :2
D/ThermalDaemon( 1486): Sensor setup:[tsens_tz_sensor0]
D/ThermalDaemon( 1486): No rules to monitor sensor 'pm8058_tz' disabled: 1 num_thresholds: 0
pm8058_tz hardcoded into the thermald binary
Removed 1.944GHz entry. Kernel is much more stable now.
little_lerroyy said:
Removed 1.944GHz entry. Kernel is much more stable now.
Click to expand...
Click to collapse
Your kernel doesn't have the modified fstab and init.pyramid.rc for zram.
By the way are you going to add 2D overclock?
hinxnz said:
Your kernel doesn't have the modified fstab and init.pyramid.rc for zram.
By the way are you going to add 2D overclock?
Click to expand...
Click to collapse
He added the zram commits from ivanich git i think !! How is it possible that it doesn't have zram ?! How do you check whether zram is enabled or not ?!
francesco totti said:
He added the zram commits from ivanich git i think !! How is it possible that it doesn't have zram ?! How do you check whether zram is enabled or not ?!
Click to expand...
Click to collapse
Enter in Terminal emulator:
Code:
cat /proc/swaps
Ok I just tested thermal daemon, I set cpu to 1728000 and thermald working but it causing reboots because my device can't handle 1890000 which it resets to.
Code:
D/ThermalDaemon( 1596): CPU[0] frequency limited to 1134000
D/ThermalDaemon( 1596): CPU[1] frequency limited to 1134000
D/ThermalDaemon( 1596): CPU[0] frequency limited to 1890000
D/ThermalDaemon( 1596): CPU[1] frequency limited to 1890000
Edit: I don't know what to change yet or add but something definitely in /drivers/thermal/msm_thermal.c
Edit: I tested on ivanich's kernel too and it's the same, meaning if you set max freq to 1188000 it reverts back to 1512000 afterwards.
Also Sultanxda fixed this in his kernel.