Related
Is it safe to install SetCPU on the MyTouch4G now that we have permaroot? If so, what are the settings we should use with it? Just not sure if the current kernel has been tested with SetCPU or not, and if it works what version of SetCPU... 2.0.3 or 2.0.4?
Thanks.
I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Sent from my HTC Glacier using XDA App
Mr Bill Florida said:
I am running 2.0 4 with autodetect. Set at 1024mhz performance. No issues and been running 3 days now.
Click to expand...
Click to collapse
So you're not overclocking it then, correct? What is your setting for the minimum frequency?
I have it at 245mhz.
Sent from a rooted myTouch4g Glacier.
set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
also download auto killer memory in market and set to optimum for even better battery life
I thought that over clocking required a custom kernel?
Sent from my anti titanic
thelamacmdr said:
I thought that over clocking required a custom kernel?
Sent from my anti titanic
Click to expand...
Click to collapse
You do.
Sent from my HTC Glacier using Tapatalk
Were not overclocking... simply managing the CPU more efficiently at its existing speed set
Sent from my HTC Glacier using XDA App
awdlexusis said:
set up a profile under screen off and set max down to 3000 and minimum at 2000...saves me ton of battery power now
Click to expand...
Click to collapse
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?
I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Sent from my HTC Glacier using XDA App
slowestcivic said:
I was going to say the same thing, from what I have seen on my phone setcpu is not doing anything. It won't change any of the clock speeds whether boosting the low end or limiting the high end.
I have tried a few things like setting profiles for less than 75% battery to lower the max clock speed and that doesn't work either. Am I crazy or are others experiencing a placebo effect on profiles lowering clock speed when screen is off?
Click to expand...
Click to collapse
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.
vels13 said:
For HTC phones need to be rooted and also disable perflock. In setcpu: menu->perflock disabler. I set my perflock to disable on boot.
Click to expand...
Click to collapse
Hot damn, that fixed it! Now to test it out further to see how well it works here. I'm not looking to overclock, just underclock when I'm not using the phone. Thanks for the tip!
dustrho said:
The closest options for this are the following:
368640 max
245760 min
What did you use for the scaling and priority settings?
EDIT - Added a screenshot to this post. I've tried both 2.0.3 and 2.0.4, and no matter what I set for the minimum setting it stays at 245 (not what I defined). Does it not work then on this stock kernel?
Click to expand...
Click to collapse
yes thats the correct setting i didnt know off hand the exact.will stay at minimum untill needed,im on on demand
Best settings for battery life?
Here are my settings and have worked very well. Almost adding 24 hours of battery life.
CBConsultation said:
Here are my settings and have worked very well. Almost adding 24 hours of battery life.
Click to expand...
Click to collapse
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?
Daguse said:
wow... what kind of use are you putting on it? Also are you having any issues with lag or slow response?
Click to expand...
Click to collapse
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.
CBConsultation said:
Just an average power-user. I email and text a lot as I own a consulting business. I am constantly on the go and need my battery to stretch as long as possible.
That is why I kept the stock kernel and didn't over-clock. I simply removed all the bloatware and non-essential apk's that I didn't need and set up a few profiles in SetCPU and now I can get an easy 2 days of power use out of it.
As I still employ the stock kernel and stock ROM I have no lag what-so-ever. Response is perfect IMHO.
Click to expand...
Click to collapse
SO I am new to this... I used your same settings and my bat shows 56%. On the my screen it still shows that its jumping from 1024-245. Am I missing something?
EDIT: N/M I am just dumb and forgot to preflock!
So I set my profile to have
Screen Off Pri 75 Max 3K Min 2K
Bat 75% Pri 50 Max 7K Min 2K
Bat 50% Pri 50 Max 3K Mn 2K
I will let you know how it goes but I am hoping for some good bust in bat life.
Had some issues when waking the phone, so I changed the settings on the screen off to Max 768. Going to test.
I also moved the 50 Bat to 30 and still getting good life out of it.
Well I have been experimenting with some profiles in setcpu and I have noticed a great increase in battery life especially when in standby a lot.
So i have done this according to what works for everyone else. But... my battery still drops from 100 down to 40 in about 5hours and it has been this way since the 2.2.1 smh. I dont kno what to do. I do text alot and get on facebook mobile semi frequently but mainly text and omg the phone gets up to 104 degreez wen using or charging. Any suggestions ? Or anythjng i may be doing wrong
Sent from my HTC Glacier using XDA App
For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?
I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.
I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.
ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.
colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...
Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.
SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?
im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.
Yeah. Even when disabling the perflock, it won't let me chance the minimum frequency. ive tried setcpu, cpumaster, cputuner and a bunch of other apps. is there anybody here who's had the same problemo?
my kernel is 2.6.32
before rc1, just two hours ago, i had nightly version 173. i flashed rc1, because obviously i misread that it had a different kernel, 2.6.35. yeah right. im gonna rage soon. the battery drainage is horrible.
plz helps!??!?1one
edit: oh, what would you recon as the best rom for legend? thanks!
Maybe overclock is only on stable version, rc and nightly made for testing other stuff.
I use some mod of blayo rom, no overclock. Works awesome. More then 90 days without flashing or even reboot. Well only feature i need from custom rom is root and wake up on trackboll.
maksimilian said:
Maybe overclock is only on stable version, rc and nightly made for testing other stuff.
I use some mod of blayo rom, no overclock. Works awesome. More then 90 days without flashing or even reboot. Well only feature i need from custom rom is root and wake up on trackboll.
Click to expand...
Click to collapse
Thanks for replying! actually, the in-built cpumanager works like a charm, and i have been using it clocked to 825mhz. And cyanogen all in all works great, suprisingly nightly version 173 works better than 7.1.0 rc1.
But still, i cant UNDERclock the dang cpu. someone had his legend run with minimum freq at 19 mhz - and had a large impact on the battery life with the setup.
And it worked ok with incoming call?
There is no way to clock this kernel below 245 MHz unless you alter its frequency table and recompile it yourself. May I ask you why do you want to go below 245 MHz?
Sent from my HTC Legend
maksimilian said:
And it worked ok with incoming call?
Click to expand...
Click to collapse
Yeah, silky smooth. No bugs found yet, talking about nightly 173.
BlaY0 said:
There is no way to clock this kernel below 245 MHz unless you alter its frequency table and recompile it yourself. May I ask you why do you want to go below 245 MHz?
Sent from my HTC Legend
Click to expand...
Click to collapse
Bummer. Got no skills for that. I do alot of reading, and the system does not need 245mhz to run a screen with some text on it, i suppose. oh well...
so, your rom can be clocked below 245mhz? would you recommend it for everyday use? thanks!
Yeah, but when you are reading, you have to slide a lot I guess?
My conclusion was (after an extensive testing) that lowering the speed below 245 MHz didn't add much to battery life so I'm actually using just two profiles... one for screen on 245 - 768 MHz and one for screen off 122 - 480 MHz. Scaling governor is interactive in both cases.
If I can recommend my ROM? Dunno. I'm using it since I started it and I'm satisfied with it. I don't need anything else
Sent from my HTC Legend
Hi,
I have a problem, from CM10 nigthly, M1, M2 to CM10 Stable (now) my Nexus S restart 2-3 times per day.
TuneIN + HSPA = phone restart
Apollo playing mp3 = phone restart
After ringing the alarm clock = sometimes restarts
Enable sync after ring alarm clock = sometimes restarts
sometimes not reset within a day or two, is an annoying situation
Any idea ?
Change kernel...
Didn't happen to me
But try matrix cm version . if still... Might be a bad download/flash . or ( hope not) hardware prob .
If your Nexus S is overclocked, stop doing that.
chupchip said:
If your Nexus S is overclocked, stop doing that.
Click to expand...
Click to collapse
Hi, Nop CPU is set to ONDEMAD from 200 to 1200Mhz
raducux said:
Change kernel...
Didn't happen to me
But try matrix cm version . if still... Might be a bad download/flash . or ( hope not) hardware prob .
Click to expand...
Click to collapse
Hi thanks, what version recommend, any link ?
cmenghi said:
Hi, Nop CPU is set to ONDEMAD from 200 to 1200Mhz
Click to expand...
Click to collapse
you do know that stock frequency is 100-1000Mhz? mine's a rebooter at 1200Mhz so yours might be too. for kernel try and use the search function.
Aktifit said:
you do know that stock frequency is 100-1000Mhz? mine's a rebooter at 1200Mhz so yours might be too. for kernel try and use the search function.
Click to expand...
Click to collapse
In the setup menu say 100 - 200 - 400 - 800 - 1000 - 1200 - 1400
im dont use setCPU only the CM setup menu, now im tried al 200 - 1000 for test. thks a lot.
s
this happened to me a lot as well while using marmite kernel, it was the overclocking that make the rom unstable.
hope this works!
I am on the CM 10 stable on the Nexus S for a week now and have not had any reboot issues at all. Everything working smooth. I am using the stock kernel included in the ROM. Replicating your situations also do not cause any issues. My suggestion might be if the issue still persist to download and flash the ROM again and test for a couple of days with the default settings and without flashing any different kernel.
Increase you voltage +25 across the board. Then try to replicate the reboots.
Sent from my Nexus S 4G using xda premium
Bruce lee roy said:
Increase you voltage +25 across the board. Then try to replicate the reboots.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Hi, im set CPU from 200 to 1000 Mhz and for 24 hrs dont reboot, im never touch the CPU freq. before! im use standar from CM setup.
Thks a lot.
Hi all,
I tried lots of combinations to OC my i9023, without any results.
I currently have CM10.1 Nighly + Marmite 7.3.1, which actually seems to be the fastest combination for me.
Btw, if I try to OC to 1096 or 1320 it starts rebooting.
Everyone said me to raise voltage.
I'm using NSTools and it appears that Marmite 7.3.1 already has higher voltage for 1096Mhz and 1320Mhz.
Furthermore, there are two settings: ARM Voltage and Interal Voltage. Should I increase both of them?
Are there other people with 9023 which overclocked it succesfully? If yes, with which tool and voltage settings?
Thank you
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
With that voltage @1500 you will probably burn the cpu fast...i think. Maybe someone with better knowledge can advise you. But i wouldn't keep such a high voltage on my phone
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
It really seems too much high...
Btw, which ROM and Kernel are you using?
mikekir97 said:
I have my i9023 Nexus s OC to 1512Mhz STABLE.. no random reboots or something.. my battery goes easily one day even with lots of gaming.. I use NSTools.. (my snapshots are from SetCPU.. ;p )
Click to expand...
Click to collapse
Which ROM and Which Kernel?
giaomnitel1 said:
Hi all,
I tried lots of combinations to OC my i9023, without any results.
I currently have CM10.1 Nighly + Marmite 7.3.1, which actually seems to be the fastest combination for me.
Btw, if I try to OC to 1096 or 1320 it starts rebooting.
Everyone said me to raise voltage.
I'm using NSTools and it appears that Marmite 7.3.1 already has higher voltage for 1096Mhz and 1320Mhz.
Furthermore, there are two settings: ARM Voltage and Interal Voltage. Should I increase both of them?
Are there other people with 9023 which overclocked it succesfully? If yes, with which tool and voltage settings?
Thank you
Click to expand...
Click to collapse
On marmite i've never been stable on OCs, even with raised voltages. On matr1x kernel you can do 1320mhz without raising voltages.
sidnoit22 said:
Which ROM and Which Kernel?
Click to expand...
Click to collapse
I am using Hellybean (the latest 26/2/13) and my kernel is Devils's kernel NOT the latest but the 21/12/12 release.. this kernel is my favorite.. try it out.. works on 4.1.x, 4.2.x.
migueldbr said:
With that voltage @1500 you will probably burn the cpu fast...i think. Maybe someone with better knowledge can advise you. But i wouldn't keep such a high voltage on my phone
Click to expand...
Click to collapse
I really don't care about burning my cpu. I have my photos backed up with dropbox.. and I'm on contract with my carrier so I will get it fixed within a week..
Is there an official thread/page for Hellybean and for the kernel?
giaomnitel1 said:
Is there an official thread/page for Hellybean and for the kernel?
Click to expand...
Click to collapse
There is a thread on XDA for the ROM Here.. For the kernel there is also a thread on XDA Here, but I don't think that you will find that specific version, just download it from my attachment above..
mikekir97 said:
There is a thread on XDA for the ROM Here.. For the kernel there is also a thread on XDA Here, but I don't think that you will find that specific version, just download it from my attachment above..
Click to expand...
Click to collapse
I have tried it and set it at 1320 (with LIVE OC 110%) and it seems stable.
Why do you suggest that particular version? Have you tried new versions and they are not stable?
giaomnitel1 said:
I have tried it and set it at 1320 (with LIVE OC 110%) and it seems stable.
Why do you suggest that particular version? Have you tried new versions and they are not stable?
Click to expand...
Click to collapse
I have tried all the new Devil kernels and they are stable for every day use but not as fast and battery save as the older version.. This is my opinion.. I have my nexus clocked at 1400Mhz and then apply 108% LiveOC witch took me to 1512.. Stable..! (at max arm volt 1500 mV)