So I recently switched kernels from my long time of using Trinity, and now I am experiencing thermal throttling because of the battery temp. The kernel I'm currently using (Inception Kernel) has this issue and I was wondering if there was any way to disable it? It's causing my GPU frequency to drop to 325/200mhz and really bugs me. Tried to remove reading permissions of thermald.conf and even deleted it.
Tl;Dr - Battery temp @ x>35c throttles, can I turn it off?
Detailed said:
So I recently switched kernels from my long time of using Trinity, and now I am experiencing thermal throttling because of the battery temp. The kernel I'm currently using (Inception Kernel) has this issue and I was wondering if there was any way to disable it? It's causing my GPU frequency to drop to 325/200mhz and really bugs me. Tried to remove reading permissions of thermald.conf and even deleted it.
Tl;Dr - Battery temp @ x>35c throttles, can I turn it off?
Click to expand...
Click to collapse
it depends on the kernel and if they exposed the setting for thermal throttle. i use trinity kernel, and disable thermal throttle after every time i boot up. you can disable it permanently, but can after each time you boot. oh, and trinity kernel disables battery throttle.
simms22 said:
it depends on the kernel and if they exposed the setting for thermal throttle. i use trinity kernel, and disable thermal throttle after every time i boot up. you can disable it permanently, but can after each time you boot. oh, and trinity kernel disables battery throttle.
Click to expand...
Click to collapse
Ah I see, and yeah that's what I like about trinity since the battery throttle is so aggressive in the N4. I would go back to trinity but at the current state of the kernel it's not close to my imagined "Perfect" kernel, although it was before haha. Also I found out that deleted the thermald.conf file and then rebooting was a success, so thanks for replying .
Related
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
dmc971989 said:
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
Click to expand...
Click to collapse
What gov. are you using on setcpu?
theoottesen said:
What gov. are you using on setcpu?
Click to expand...
Click to collapse
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Similar problem...
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
im just curious if this is the original problem or a new one cause by this rom setup... because I dont ever recall reading anything about the CPU getting stuck at 245mhz from sleep mode being the source the slow downs....
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
x99percent said:
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
Click to expand...
Click to collapse
yes, i keep them disabled...
jamesthomas128 said:
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
Click to expand...
Click to collapse
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
tkirton said:
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
Click to expand...
Click to collapse
im fairly positive that the CPU is getting stuck in the sleep mode while the rest of the phone is not, causing me these issues... the problem is i dont know how to fix them
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
Ok, modaco rom sets the governor to "performance" on boot. This essentially "sticks" your CPU to max throttle.
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Will tell you where you are, governor wise..
I'm not entirely sure what setCPU does, I've never used it, but I assume it just tweaks your top and bottom Mhz and maybe changes governor to performance when the screen is on? If it's configured properly? Maybe not, who knows?
If you want the best battery life, put the governor back to msm7k, it's a custom governor modified by HTC to make your battery last longer.
I changed the following line in modaco.sh:
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
to:
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_govern
and haven't noticed any slowdown from it.. my battery is lasting longer than it did on Stock or Fresh 1.1...
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.
Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G
I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App
It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.
I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.
I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.
mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.
jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.
I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max
Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.
Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.
Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now.
Am I overlooking something? Any help will be appreciated, thanks!
Edit: My current rom and kernel are in my sig.
so are you monitoring this via setcpu on Decks?
alaman68 said:
so are you monitoring this via setcpu on Decks?
Click to expand...
Click to collapse
Yes I am, is there a known issue?
My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.
I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.
Is there a good way to monitor the CPU without setCPU? Thanks
cesjr02 said:
Is there a good way to monitor the CPU without setCPU? Thanks
Click to expand...
Click to collapse
check out "system panel"
edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.
cesjr02 said:
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
Click to expand...
Click to collapse
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
alaman68 said:
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
Click to expand...
Click to collapse
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.
Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.
Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.
Definitely experiencing the problem with other kernels. I'm out of ideas.
Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
Sent from my PC36100 using XDA App
Did you restore any apps with titanium backup by chance?
Sent from my PC36100 using XDA App
By the way, I appreciate all your help alaman68.
Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.
Trying, you could try a sense rom for a day and check the scaling for a benchmark.
Is there anything else you are running? Undervolting, v6... Anything else?
Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?
if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?
I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.
I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)
I'll report back
Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.
is anybody else having an issue when you underclock? i usually set it to 1.4Ghz but the phone overrides the setting i put up using Atuntu CPU master. i feel that the phone is still fluid when underclocked, so i tend to under clock to save battery life(and stop if from overheating to 105.1 degrees farenheit).i need to get full usage out of my phone as the day starts at 5 AM till 5PM with heavy usage
any luck with this issue?
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
42 8996883
Steamer86 said:
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
Click to expand...
Click to collapse
in English please? o dont get what wou mean by the SOC Bin and the part after that. i did the trickster, but it still overrides it.
You can't make it stick with default kernel. You need a modified one with inteli so thermald doesn't auto override. SOC bin is details on your "CPU" quality for base volt values, better SOC means better overclock, underclock, and undervolting. If you're serious in doing this, search and learn. This isn't simple modification, and you will not be able do this in simple way. Make sure you have set on boot checked in trickster. Well work somewhat better, but still not a permanent solution.
Since upgrading to KitKat, my phone will reboot (not instantly - after some time) whenever I use any governor other than interactive.
This is with any 4.4.2 ROM, even after full wipes..
Anyone else noticed this with KitKat? If you want to test - please change your governor to ondemand - use your phone normally (may take a while) but after some time the device will freeze and reboot.
Is this normal? Upon restarting the governor will revert back to interactive
Any advice will be much appreciated folks.
Mine does the exact same thing with ondemand governor no matter what rom I'm on. I thought my phone is just messed up. You are the first person I've heard has the same problem. I really don't know why its like that?
Sent from my SM-N9005 using XDA Premium 4 mobile app
same here
I am currently running 4.4.2 stock with BeastMode kernel from freeza and the ondemand governor causes stutter and a reboot after a few minutes of using the device.
As I recall, this also happened on the stock kernel.. the interactive governor appears to be more stable, but it does seem to take a greater toll on the battery.
No matter what voltahe settings(+/- 100mv) I use with the ondemand I keep getting the same results.. weird
By chance is knox included in these roms?
I had the same problem on stock where phone rebooted constantly, tried everything until I fully uninstalled Knox and it has since stopped.
I always have my CPU governor set to ondemand.
I am running stock on my note but have deleted everything concerning knox on system/app. The problem still persists...
Hmm that's really odd.... have you tried using link2sd and searching for knox just in case it left anything behind? Providing you are rooted.
Sent from my SM-N900 using XDA Free mobile app
I just tried that and no knox to be found... I do not know if it has to do with the "silicon lottery" in which OC and OV doesn't play well with some governors. .
Anyway I stuck with interactive and it has been solid so far... my major concern now is fixing that persistent "Cell Standby" battery drain that persists even on airplane mode.