Database Info

SetCPU

I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?

regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.

Profondo_Rosso said:
I have just one profile, screen off= 216/216. I'm now on 14 hours with 30% left. Much better than before, when I was getting 11 hours at the most.
I also use the battery calibration app. But that's all I've done.
Just want to add I use wifi calling, and I run everything else, gps and syncing gmail and facebook is on. Screen is set to auto brightness. The only thing I have off is bluetooth.
Click to expand...
Click to collapse
I do the same.. just 1 screen off profile to underclock it to 216/216 when the screen is off

regP said:
I've always read in the past that the app doesnt actually help with battery life because its purpose was for OCing and Android regulates the cpu clocks already.
So I'm wondering, for those currently using it, have you noticed any difference in battery life (without underclocking while in use)? and if so what profiles are you using?
Click to expand...
Click to collapse
Android does regulate the cpu, but I don't think it will take advantage of more conservative governor modes unless you tell it to. That's only relevant if the kernel supports more conservative governor modes. And, as the other responses have pointed out, you can force Android to be more conservative by capping the max clock speed.

Hmm... Guess its worth a shot. Good lookin out guys.

when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.

charlieb620 said:
when i go into setcpu there are alot of options to choose there is no auto detect like on my mytouch 4g. how did you guys get it to work. i picked the last option which was custom and it forced close on me.
Click to expand...
Click to collapse
Yeah.. When I hit the tegra 2 option it wont let me change the governor.

You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?

regP said:
Yeah.. When I hit the tegra 2 option it wont let me change the governor.
Click to expand...
Click to collapse
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216

jayohwhy said:
I think that that means that the kernel is not supported for the "automatic" governors. However, you can still create profiles to regulate the CPU based on perameters that you set, i.e. Screen off 216/216
Click to expand...
Click to collapse
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?

SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.

rhinology said:
So all G2x see the same in setcpu - no autodetect and only governor available is "driver"?
Will custom ROMs like CM7 change this?
Click to expand...
Click to collapse
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu

jayohwhy said:
From what I've heard, yes, that is what every g2x setcpu user sees. I don't know whether CM7 will fix this, or maybe later versions of setcpu
Click to expand...
Click to collapse
Once we get some custom kernels, we should be able to change the governors in setCPU, dependent upon on what the kernel supports.

SetCPU Custom Frequencies for G2X
I got SetCPU today and was playing around with it and it looked like it was limiting my CPU all the time due to lack of profile, not just when I had the screen off per my profile so I looked into making a text file for custom frequencies and am posting it here since there doesn't seem to be any help for g2x with it.
This is a really simple file, tell me if you guys have any better ideas, I just put in:
216000,528000,712400,1000000
I'm attaching it. I put the file in my dropbox, grabbed it via the app and then moved it to /sdcard/setcpu.txt via astro file manager then loaded custom profile from within setcpu. Hopefully this saves someone some time or you can tell me if I'm going about this the wrong way
I'm sure it could be fine tuned more but I was getting irritated at how much of a pain it was to unlock the phone with it set too low, so for screen off I have it set to 216->528. You could add 254000 in or something. The phone seems to be as usable as before now with setcpu enabled like this while it should be limiting the cpu when the screen is off. It sucked (well not the battery) without a custom profile.

socalTNT said:
You need to be rooted so that you can let set CPU have super user access. Are you rooted yet?
Click to expand...
Click to collapse
rooted?????? what is that?

TheMightiest1981 said:
SetCPU improved my battery life tremendously! Before I was losing about 15-30% and hour, since 8:30 this morning my battery only dropped to 73%. I set my active profile between 457mhz and 816mhz depending on remaining battery and it's still fast as hell.
Click to expand...
Click to collapse
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.

Profondo_Rosso said:
Yep, I agree. My phone has been off the charger for almost 9 hours, and I'm at 70%.
I have everything on, including wifi calling, and one profile in Setcpu for screen off 216/216.
Also used the battery calibration app.
Click to expand...
Click to collapse
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App

I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.

charlieb620 said:
Im assuming u did little to no use. I did moderate use and im down to 52% after 4hrs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Actually, your assumption is wrong, as is often the case.
I'd quantify it more as normal use. Lots of texts, some games of Pro pool, a few phone calls, checking Pulse 3-4 times during the day for 10 minutes at a time, some mild web browsing and watching a few youtube videos.
I ended up at around 18-19 hours of of use.
Today, I'm off the charger for 8 hours, and I still have 45% left, and I would say that's with some moderate to heavy use.

regP said:
I tried that 216/216 profile and got the sleep of death followed by reboot loop every few minutes after the phone booted. wouldn't stop till I manually powered the phone down then back on. oh well... my phone idles fine anyway. wonder what clock speed android idles at by default.
Click to expand...
Click to collapse
Try upping it to 216/312 or a tad higher and you should be fine.

Thoughts on OverClocking Sensation

Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt

I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.

I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt

I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.

mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App

Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707

I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...

So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt

I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?

i think at LeeDroid 1.2 you must not use setcpu but Demon control?

BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.

Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.

[Q] My device keeps powering off when the I put the screen to sleep.

For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?

supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Ok thanks. What is sod by the way???

supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

oh lol im learning slowly but fa showly.

supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Question about uv. is less best ie -25? and what does disabling the various clock speeds do?

Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.

Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50

jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)

You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation

supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.

Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)

Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.

Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.

[Q] Which kernel is best for Stock ICS?

Hi, first to defend myself, I did search and found that everybody says good things for every kernel. So every kernel is best for Stock ICS?
I got confused. Yes I'am total noob and recently learned how to root and flash custom rom's.
I just want to hear your opinion for best kernel running on Stock ICS.
I need kernel that is good for the battery but also snappy for the system. I don't play games and I use my phone for calls, reading news, working on excel files, google maps, mail and taking pictures.
My phone is Nexus S GT-I9020T on Wind network.

IMO ezekeel kernels
Has lats of featured including voodoo color
http://forum.xda-developers.com/showthread.php?p=20520270
Sent from my Nexus S using xda premium

Thank you. Is this kernel stable?

Im just trying to set it up as we speak, will let you know how stable it appears once I figure it out
Stuck on trying to flash an unsecure boot image at the moment.

*shrugs* The stock kernel?
Unless you want the functions third party kernels bring to the table, I don't see a good enough reason to swap the stock kernel for another.

That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.

Just managed to get ezekeels CFS on there and I get the reboot bug after going to standby.
Looking for updates but the thread is huge. Yet to try BFS.

darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Click to expand...
Click to collapse
You can try and turn off deep idle for your reboots.
Solves the problem 99% of the time (totally made up stat that could actually be true)

But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk

darko.baruh said:
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Deep idle gives more battery time under certain conditions (screen off but not completely idle, playing music for instance). It won't really give you more battery time if your phone is actually idle with the screen off.

But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.

darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel.
Click to expand...
Click to collapse
Same here but not bad at least for me just one reboot since i installed yesterday when he posted. 2.1 kernel I never got any reboots
Sent from my Nexus S using xda premium

darko.baruh said:
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
Click to expand...
Click to collapse
The first post that you linked actually just confirms what I said.
Ezekeel said:
Since this is just theory and Morfic noted that his experience seems to indicate otherwise and that limiting the CPU frequency does actually decrease the battery drain, I put this theory to the test and logged the battery charge over 10h of FLAC playback in Airplane mode with the screen switched off.
Click to expand...
Click to collapse
1) Playing FLAC (not idle)
2) Screen off
Pre-requisites are met.

So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).

darko.baruh said:
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
Click to expand...
Click to collapse
Deep idle only shows savings if there is tasks running while the screen is off VS the same situation without deep idle.
So for someone doing commuting (like simms22 for example) and listening to music for around an hour, they'll lose less battery with deep idle than without.
You won't actually save battery if your phone is actually idle with deep idle enabled.
It's not some kind of magical function that makes your phone use less battery doing tasks with the screen on, deep idle disables certain components of the phone while executing tasks with the screen off, instead of having it "at full speed" as if the screen was on.

Now I understood. Thank you very much.

darko.baruh said:
Now I understood. Thank you very much.
Click to expand...
Click to collapse
No problem. I think Deep Idle is probably the mod by Ezekeel surrounded by the most misconceptions.
Most new users want it absolutely but don't seem to know why.

On His Glados kernel I noticed that Android OS was using 20%-21% of the battery and on the stock kernel 30%-31%.
Android System was using around 14% and on the stock around 19%.

Ok, have you decided to give the Glados 2.2 another go? I believe I have finally tweaked it so that it is stable for me.
Before I was getting restarts within 30 seconds of the screen turning off. I have cornered this (on my phone at least) to a problem with NSTools auto-setting the lower frequency to 100mhz. Changing it back to 200mhz and I have yet to see the system restart itself. Im not overclocked, because I dont see the point as everything is fairly snappy with this new kernel. I dont really play games on it so Im not fussed.

I did used NSTools and the frequency was set to 200mhz and I had system restarting on screen off. Using stock ICS with Glados 2.2
Also I had green annoying flickr on locking and unlocking the screen.

[Problem] Overheating problem

Guys after a month of continue rom changes i realzed my phone has a problem. The problem is the heat my phone burns for every action. Is the hw problem or sfotware? I have hboot 1.27.1100 s-off and viper s. I want try everithing for not send my phone in assistance (in my country htc assistancee is ridiculous).

kekkojoker90 said:
Guys after a month of continue rom changes i realzed my phone has a problem. The problem is the heat my phone burns for every action. Is the hw problem or sfotware? I have hboot 1.27.1100 s-off and viper s. I want try everithing for not send my phone in assistance (in my country htc assistancee is ridiculous).
Click to expand...
Click to collapse
What part is heating up? The battery? The CPU? The front, the back? Top or bottom?
It could be software. It could be hardware. How is your battery life?
Try installing a fresh version of Viper with limited apps and see if that helps. If it does, reinstall your apps gradually in case one is using too much CPU.
If that doesn't work try a different ROM for a week and see if that changes anything.

Skipjacks said:
What part is heating up? The battery? The CPU? The front, the back? Top or bottom?
It could be software. It could be hardware. How is your battery life?
Try installing a fresh version of Viper with limited apps and see if that helps. If it does, reinstall your apps gradually in case one is using too much CPU.
If that doesn't work try a different ROM for a week and see if that changes anything.
Click to expand...
Click to collapse
In the bottom (front and back). Already tried many rom but is always the same. With and w/o undervolt, with gpu rendering ticked and unticked etc etc... (ics and jb)

kekkojoker90 said:
In the bottom (front and back). Already tried many rom but is always the same. With and w/o undervolt, with gpu rendering ticked and unticked etc etc... (ics and jb)
Click to expand...
Click to collapse
If memory serves the bottom of the phone is where the CPU is. So you are overpowering the CPU somehow....
Do you have a CPU monitoring app? So you can see what load the CPU is under at all times? I'm betting you'll find that it's pushing to the max allowable clock speed and/or being used at 100% most of the time.
Are you using the Performance governor on your kernel, or something like it? Try putting the kernel at Conservative and setting the max clock speed at like 1188 and see if that helps. If it does then we'll have isolated the problem. If it doesn't....I dunno...
And again, how is your battery life?

Skipjacks said:
If memory serves the bottom of the phone is where the CPU is. So you are overpowering the CPU somehow....
Do you have a CPU monitoring app? So you can see what load the CPU is under at all times? I'm betting you'll find that it's pushing to the max allowable clock speed and/or being used at 100% most of the time.
Are you using the Performance governor on your kernel, or something like it? Try putting the kernel at Conservative and setting the max clock speed at like 1188 and see if that helps. If it does then we'll have isolated the problem. If it doesn't....I dunno...
And again, how is your battery life?
Click to expand...
Click to collapse
my battery life i think is normal 2/2.30 hour of screen and 12/15 with intensive usage. Wifi and data always on. My governor is badass without gpu overlock. Tomorrow post screen with battery life.
Today stats is 1h of screen (browsing in 3g) and 21.30 h of standby and 20% of battery remaining.
I dont have a cpu monitoring app you can tell me one?

kekkojoker90 said:
I dont have a cpu monitoring app you can tell me one?
Click to expand...
Click to collapse
system tuner, cpu spy, no frills cpu, setcpu.. any of them are good
Enviado desde mi HTC Sensation 4G

serio22 said:
system tuner, cpu spy, no frills cpu, setcpu.. any of them are good
Enviado desde mi HTC Sensation 4G
Click to expand...
Click to collapse
installed system tuner and program says my cpu have 40° C
Edit 45° C now

kekkojoker90 said:
installed system tuner and program says my cpu have 40° C
Edit 45° C now
Click to expand...
Click to collapse
That's hot, but what kind of load is it using most often?
10%? 100%?
In system tuner look at the TIMES menu. You should see the processor being offline most of the time. If you see it online at a high frequency most of the time then something's wrong.
But you've got to let System Tuner be installed for a while before you have viable results. At least several hours.

Skipjacks said:
That's hot, but what kind of load is it using most often?
10%? 100%?
In system tuner look at the TIMES menu. You should see the processor being offline most of the time. If you see it online at a high frequency most of the time then something's wrong.
But you've got to let System Tuner be installed for a while before you have viable results. At least several hours.
Click to expand...
Click to collapse
ok tomorrow use my phone normally with system tuner reg active (i post log with temp and freq tomorrow)

Also try a different kernel for a few days.
And use the conservative governor to see if that makes an impact as well. You don't have to stick with that governor forever if it doens't provide enough performance. Just try it and see if it makes a difference.

Skipjacks said:
Also try a different kernel for a few days.
And use the conservative governor to see if that makes an impact as well. You don't have to stick with that governor forever if it doens't provide enough performance. Just try it and see if it makes a difference.
Click to expand...
Click to collapse
tomorrow my proof is with vipers and intellidemand to 1.5 ghz.

kekkojoker90 said:
tomorrow my proof is with vipers and intellidemand to 1.5 ghz.
Click to expand...
Click to collapse
You should definitely consider clocking it to a slower speed just for testing. I have had similar issues in the past when it is clocked to that speed.

Little update after 30 min of browsing temp us 56 C
EDIT After this bad result my cpu ruba to 1.18 Noè with 75 undervolt