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...
For close to a month now I have been trying to find/figure out if SetCPU is worth using or not.
I've seen some threads (yes, I DID search/read as many as I could find) that swear by it and others who that say it really doesn't do much and it sucks...
I've also tried it with different ROMs, kernels, settings & profiles only to get mixed and/or confusing results myself.
I, personally-and I'm sure a bunch of others-would love to know if it is in fact worth using or not.
Maybe some generous person could take the time & inform us the proper settings, when/if to use "set on boot", what the "advanced" settings actually do, etc.
It's hard to find a straight answer because everyone does not have the same ROM and/or kernel installed plus everyone's device is different as well.
I for one would like to know if it is true that using "set on boot" slows down/messes up the performance of the ROM/kernel and also how to use the profiles correctly...by correctly I mean how to make each profile that is set for a specific battery charge, etc. run correctly...
[example]:
I had the profile settings at "battery<101%" at 100 priority with max-1190400 & min-652800 with smartass governor (stock setting on chop suey kernel/Evolved ReCharged ROM)...
then as the battery drained some I had "battery<60% at 80 priority with a lower min/max setting with interactivex governor...
now the whole time the battery was under 60% SetCPU kept the min/max settings at max-1190400 & min-652800 (the first/highest profile)...it didn't drop them to the lower/slower "battery<60% min/max" settings...
is this because the "battery<101%" setting was at 100 priority? will it keep that first setting since everything (battery percentage-90%,70%,etc.) is technically lower than "battery<101%" even if there are other profile settings because the priority is set as high as it goes (100) ?
I hope I'm not confusing everyone!
I guess what I'm trying to ask is how exactly do you get the device to follow the profiles?
I've set up all the profiles I wanted, clicked "set on boot" and the only profile that seemed to be used was the one with the highest "battery<**%" & highest profile number (100).
I set all profiles 10 under their previous setting (profile 1-100, profile 2-90, profile 3-80, etc.) but only the profile-100 was followed.
If anyone can clear things up that would be great!
I know from other threads there are a ton of people having the same trouble...
any/all help is greatly appreciated.
If you set a profile to 100% priority, it'll always be used over the others if whatever the profile is for is true... in your case, battery <101% - which is always true.
Don't use a profile for whatever you want the normal setting to be, use the main screen for that. Set profiles for other things (screen off, battery low, temperature high, etc). If you use profiles for screen off, low battery, and high temperature, you need to set the priorities accordingly. Temperature would have the highest priority since it can do damage to your device. These profiles will not override your default settings unless their conditions are met.
Check out the SetCPU site for a lot of answers. http://www.setcpu.com/
It's also important to know your kernel and how it works. Sometimes SetCPU will clash with or work against what your kernel is trying to achieve. For more information on kernels, read this: http://forum.xda-developers.com/showthread.php?t=894880
Sent from my PC36100 using Tapatalk
Smartassv2 governor takes care of a lot of those profiles for you, by limiting your phone to its lowest cpu value when the screen is off automatically. I get so much battery out of my evo, its intense.
I only have 2 profiles.
Main setting - Max 652800 Min - 24500 ondemand set on boot.
Profile 1 - Screen off Max and Min 24500 ondemand, priority 100
Profile 2 - Battery <50% Max - 499 Min 245 ondemand, priority 50
On the main screen, make sure to disable perflock, and check set on boot.
Those are my settings, and I can go about 24 hours and still have about 20% charge, texting all day, playing games on my phone, using the xda premium app, some other ****.
I'm using the stock kernal in 2.3.3 btw.
broad_st_bully said:
For close to a month now I have been trying to find/figure out if SetCPU is worth using or not.
I've seen some threads (yes, I DID search/read as many as I could find) that swear by it and others who that say it really doesn't do much and it sucks...
I've also tried it with different ROMs, kernels, settings & profiles only to get mixed and/or confusing results myself.
I, personally-and I'm sure a bunch of others-would love to know if it is in fact worth using or not.
Maybe some generous person could take the time & inform us the proper settings, when/if to use "set on boot", what the "advanced" settings actually do, etc.
It's hard to find a straight answer because everyone does not have the same ROM and/or kernel installed plus everyone's device is different as well.
I for one would like to know if it is true that using "set on boot" slows down/messes up the performance of the ROM/kernel and also how to use the profiles correctly...by correctly I mean how to make each profile that is set for a specific battery charge, etc. run correctly...
[example]:
I had the profile settings at "battery<101%" at 100 priority with max-1190400 & min-652800 with smartass governor (stock setting on chop suey kernel/Evolved ReCharged ROM)...
then as the battery drained some I had "battery<60% at 80 priority with a lower min/max setting with interactivex governor...
now the whole time the battery was under 60% SetCPU kept the min/max settings at max-1190400 & min-652800 (the first/highest profile)...it didn't drop them to the lower/slower "battery<60% min/max" settings...
is this because the "battery<101%" setting was at 100 priority? will it keep that first setting since everything (battery percentage-90%,70%,etc.) is technically lower than "battery<101%" even if there are other profile settings because the priority is set as high as it goes (100) ?
I hope I'm not confusing everyone!
I guess what I'm trying to ask is how exactly do you get the device to follow the profiles?
I've set up all the profiles I wanted, clicked "set on boot" and the only profile that seemed to be used was the one with the highest "battery<**%" & highest profile number (100).
I set all profiles 10 under their previous setting (profile 1-100, profile 2-90, profile 3-80, etc.) but only the profile-100 was followed.
If anyone can clear things up that would be great!
I know from other threads there are a ton of people having the same trouble...
any/all help is greatly appreciated.
Click to expand...
Click to collapse
I'm just curious as to how this is "the truth about setcpu"?
Evo4eva said:
I'm just curious as to how this is "the truth about setcpu"?
Click to expand...
Click to collapse
the "truth" being is it worth using or not since so many people have different opinions....
the truth=it actually does work
the truth=it does not work
hope that clears things up.
****************************************************************
okay so then the profiles are not actually for setting the speeds of the phone for everyday use...they are mainly for when the screen is off, battery is low or hot, etc.
Thanks...that make alot of sense now.
no prob...
I have done some research into it and contacted nvidia support and got them to confirm that setting a limit to the CPU speed does not currently work, they claim it will be fixed in a future update. I tried to fix it myself but I can't seem to figure out how to get settings in files to stick on boot, some script files seem to be changing the settings on every boot so i can't get get any changes to take place (though I know where the settings are found for each of the profiles, optimized battery saving and max performance)
That makes sense... No wonder why the battery drained equally no matter what..
if you have root though it seems like trickster mod works to limit the CPU speed
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!
I have problem on my OP 8 Pro, I no can set in Franco Manager kernel minimi frequently for little core 300, the same change to 1000? Does anyone have any idea what causes this effect? I no used any app to boost phone... After reboot is normal, i can set 300. Help?
Any advice?
So depending on what kernel you're on it may reset or the settings could be forced.
So EX allows me to go to 300 and stay there, also allows me to lower the max to 100MHz lower. (no performance hit, much cooler phone)
So my advice would be ask in the kernel thread, chances are it's forced to be at 1GHz as Is stock
dladz said:
So depending on what kernel you're on it may reset or the settings could be forced.
So EX allows me to go to 300 and stay there, also allows me to lower the max to 100MHz lower. (no performance hit, much cooler phone)
So my advice would be ask in the kernel thread, chances are it's forced to be at 1GHz as Is stock
Click to expand...
Click to collapse
Ok, I understand, but I restart phone and its normal, I can set 300, after a few hours, I set 300, the same set 1000...
Testing 3 kernels.