Database Users

[Q] SetCPU on NAND ROM's

Hello,
is SetCPU recommend on NAND ROM's and if yes, what could be the best Settings to set on NAND ?
i thought about
MAIN:1075=384
CONSERVATIVE
PROFILE:SCREEN OFF 384=245
priority=40
conservative
Click to expand...
Click to collapse
any tipps from others?

I have noticed that Set cpu bind very processor! Try to uninstall and install this program: Temp+CPU V2
Link: http://www.appbrain.com/app/temp-cpu-v2/com.sanels.tempcpuv2
...and see that its processor to work at low levels ....

Mordon2008, I guess you're trying to say that setcpu is using a lot of cpu power? Which I don't think it does when you configure it correctly. On the other hand, if you're using a build/rom/kernel that comes with a smartass governor by default, it is true that setting up setcpu wrong might even give you a worse performance than not using setcpu at all, because it already handles energy saving during sleep and interactive scaling during load very well from what I understand (somebody please correct me if I'm wrong). Therefore, my answer would be that it depends on the build/rom/kernel you're using.
Sent from my HTC HD2 using XDA App

Personally, I don't see the use of SetCPU on NAND builds to be honest, unless you're looking to overclock your CPU (when available).
I'm not using SetCPU and i'm on my 3rd consecutive day without charging the phone. (30% left).

KrewsialNL said:
Personally, I don't see the use of SetCPU on NAND builds to be honest, unless you're looking to overclock your CPU (when available).
I'm not using SetCPU and i'm on my 3rd consecutive day without charging the phone. (30% left).
Click to expand...
Click to collapse
it is impossible that you're on the third day! I do not even arrive in the evening! What do you keep it just in standby? Which rom do you have? which radio do you have?

mordon2008 said:
it is impossible that you're on the third day! I do not even arrive in the evening! What do you keep it just in standby? Which rom do you have? which radio do you have?
Click to expand...
Click to collapse
read my sig..
I'm not playing with the phone the entire day. I have more important things to do..like work
I 'stress' the phone maybe 40 to 45 minutes a day during travelling to work. And all that stress is the internet connection and the music player
apart from the occasional calls i must say it's holding up well.

KrewsialNL said:
Personally, I don't see the use of SetCPU on NAND builds to be honest, unless you're looking to overclock your CPU (when available).
I'm not using SetCPU and i'm on my 3rd consecutive day without charging the phone. (30% left).
Click to expand...
Click to collapse
That's actually what I was going to add... I think there's at least one use for setcpu even with the smartass governor. I myself am using it in order to restrict the maximum frequency to about 768MHz. For my purposes, this is enough and does not make the build I am using less snappy. But it might save at least a little bit of energy and therefore improve my battery life a bit.
Greetings, tsrzealot
Sent from my HTC HD2 using XDA App

SetCPU vs. CMSettings Built-in CPU manager

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.

OC'ing SGS

Hi there,
I actually want to know if it is harmfull to OC your SGS to 1.2GHz. Ofc it's better to run stock but is it of any real harm and how do you OC? I had a quick test with Galaxy Tuner and I must say when I use my phone heavily 1.2GHz is better. So if this is safe and done easily I would like to do this . Thanks in advance!

Well that seems like a small overclock, so if you have setcpu to your minimum with screen off, it should be OK.
Sent from my SilverBullet "HTCDesireZ running CM7"

Alright and how long can i use my phone when its on 1.2? Also next to that my phone is in a leather case when not being used so cooling will be a bit harder. Some more information from other people plz? I just want a consensus . Thanks for the quick reply.
Sent from my GT-I9000 using XDA App

my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.

darkside748 said:
I actually want to know if it is harmfull to OC your SGS to 1.2GHz.
Click to expand...
Click to collapse
No one can say for sure what would happen when you push a chip beyond its design parameters. Not all chips are made equal. Usually the standard speed rating is what all chips passing QC should be able to operate at. However some chips may be able to operate at higher speeds without ill effects while others may fail catastrophically even with a slight increase in frequency. So its anyones guess...
Frankly I dont see the need to overclock right now. What ROM are you using ? Flashing to a newer / better ROM can give you a bigger improvement than what 200Mhz can give you on a laggy unoptimized ROM, so why risk it ?? .

minjiet said:
my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.
Click to expand...
Click to collapse
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
+1, charging and gaming at the same time is never a good I idea. They both heat up the phone greatly
Sent from my GT-I9000 using XDA Premium App

Hmm I'm running docs mod v9.9.5 XD with speedmod kernel and twlweaks enabled. So it pretty fast already however with the oc there is just less loading time. But you are saying that its useless?
Sent from my GT-I9000 using XDA App

minjiet said:
my SGS motherboard burnt due to OC....
1 day while i was playing dungeon defenders with OC to 1200, with charger ON. suddenly the phone off it by itsself..
sent to service center, they said motherboard burnt!!!!
lucky they replace the board for me which still under warranty.
so high chance i think is the OC that cause overheat n burnt it.
Click to expand...
Click to collapse
If you can oc, that means you root right! either that or droidclock/setcpu correct?

darkside748 said:
Hi there,
I actually want to know if it is harmfull to OC your SGS to 1.2GHz. Ofc it's better to run stock but is it of any real harm and how do you OC? I had a quick test with Galaxy Tuner and I must say when I use my phone heavily 1.2GHz is better. So if this is safe and done easily I would like to do this . Thanks in advance!
Click to expand...
Click to collapse
it depends. i personally use tegrak overclock and for battery saving, i use overclockwidget. my sgs has been going for 2 days in a row with battery life only at 48% even with moderate usage(making smses, playuing games occasionally, etc.)

Hmm alright, these apps seems legit. What are your settings with these apps? Or should I use setcpu?

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
If the phone reaches a certain temperature, the phone stops charging, so i dont think playing a game and charging at same time is the culprit.
Granted that the phone would heat up A LOT quicker than usual, but being so hot, the phone wouldnt of been charging even with the charger connected.
there is now way of knowing whether overclocking is dangerous. Personally i think it is, you have to modify the kernel, modify system settings, modify battery voltage.
None of this is recommended, but we do it at our own risk...
Its as dangerous as running a custom ROM or LagFix. some devices are fine, some brick and burn to a crisp.
So choice is yours

Hmm i guess ill be sticking to 1ghz then... thx for the replies!
Sent from my GT-I9000 using XDA App

deliriousDroid said:
The fact you where charging, and playing a game probably had more to do with it than your overclocking.
Sent from my SilverBullet "HTCDesireZ running CM7"
Click to expand...
Click to collapse
i do the same for my x10 n the phone running just fine.
in fact, before i sent my i9000 to samsung for warranty claim, i pass the phone to a local shop, the tech told me the OC cause the board overheat, then burnt it....

darkside748 said:
Hmm i guess ill be sticking to 1ghz then... thx for the replies!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Actually tegrak oc works fine. ocing at 1.3 will crash first time but not crash anymore after the first time. ocwidget is not really useful for ocing but just to same battery life. when not really using my phone i will set it at 100mhz-400mhz. you can play angry birds on stock rom with little lag.

So you're saying i can oc.... but im running setcpu. I can OC with setcpu right? That brings another question when my screen is off what setting should i use for setcpu? In other words what is the minimum frequency?
Sent from my GT-I9000 using Tapatalk

100MHz is fine for the minimum frequency (for me at least) - this may vary between phones, give it a try.
On the subject of over-clocking though, you should take a step back and ask yourself "How much do I really need those few milliseconds less to load up Angry Birds".
I would suggest that Samsung did more testing than anyone on this forum.
All that said though though I take my phone up to 1.2 sometimes for ****s and giggles & to shut up smug iPhone fanboys

lamacow123 said:
Actually tegrak oc works fine. ocing at 1.3 will crash first time but not crash anymore after the first time. ocwidget is not really useful for ocing but just to same battery life. when not really using my phone i will set it at 100mhz-400mhz. you can play angry birds on stock rom with little lag.
Click to expand...
Click to collapse
No. Don't set set setcpu to anything below 400mhz because when the galaxy slips into idle mode it cn sometimes be difficult to wake up
. I'd imagine such a low clockspeed would encourage such behaviour. I set my minimum at 400mhz and max at 800mhz. Spot on.
my i9000..running gingerbread. perfectly.

jj03 said:
No. Don't set set setcpu to anything below 400mhz because when the galaxy slips into idle mode it cn sometimes be difficult to wake up
. I'd imagine such a low clockspeed would encourage such behaviour. I set my minimum at 400mhz and max at 800mhz. Spot on.
my i9000..running gingerbread. perfectly.
Click to expand...
Click to collapse
A bit off topic but gingerbread official or custom? And my phone works perfectly fine. No hard to wake up syndrome.

overclocking

how do I overclock my vibrant safely without destroying it??

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Try installing an overstock kernel, like Eugene373's Deadhorse Kernel, then you can download One Click Lag Fix from the market.

Just install a kernel that has oc capabilities and use set CPU to adjust the frequencies
Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA Premium App

I have overstock 2.2 with minimum at 400mhz and used spare parts to set windows to fast. This thing HAULS ASS!
Sent from my GT-I9000 using XDA App

If he asks how to install an OC kernal I'm reporting this thread to be closed.

LOL
Sent from my SGH-T959 using XDA App

after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers

I don't think that overclocking and not destroying can be done at the same time.
Sent from my SGH-T959 using XDA App

Terrance31 said:
how do I overclock my vibrant safely without destroying it??
Click to expand...
Click to collapse
Flash it, set clock speed with setcpu or voltage control, cross your fingers and hope for the best.
Sent from my SGH-T959 using XDA Premium App

All you need is a kernel that supports OC ie. (DoW, Tigersblood, Overstock, Dragon) you should be golden but double check compatibility with whatever ROM ur running.
I use "set cpu" to torque it up to 1.2(or whatever the kernel OC's to) Then i use "SystemPanel Lite" to check and make sure its actually OCing. In the system app it has a CPU Clock in the top right corner which monitors ur current cpu. When the system app opens it has a list of active applications i simply move the list up and down repeatedly really fast and watch the "CPU Clock" if it maxes out at 1.2 or whatever its good to go. I remember one time(cant remember what kernel)but set cpu showed 1.2 or 1.4 and even in system CPU info it showed OCed but if you did like i just described the CPU Clock never went above 1000Mhz. Like it was just showing as OC even tho it really wasn't it was really weird the clock would max out at 1000Mhz with dead space above it like it could go over but never would.
shreddintyres said:
after you have the oc kernel installed go into set cpu and set an audible alarm and for when your temp goes above 115 Fahrenheit, in that profile have it drop your clock speed down to 1000 or 800 to help your phone cool off before reactivating the full oc. Ive never had any problems with the cpu getting to hot oc'd to 1.2 thats not to say you wont.
Cheers
Click to expand...
Click to collapse
i never knew you could set audible alarms(guess i never really looked into it) thanks for that! running DoW221 OC to 1.4 i used to see my temps hit 120-130 it would freak me out! but never had any problems except for batt life avg 6-7hrs.
Personally my best OC ROM/kernel setup to this date has been MALICE[EDT]+Tigersblood(any release) everything works and great batt life for a OC kernel

Binary100100 said:
If he asks how to install an OC kernal I'm reporting this thread to be closed.
Click to expand...
Click to collapse
LOL
funny

Just make sure you backup before trying. Some Vibrants cannot handle overclocking (and there's no real way to know until you try). Mine is one of those, and if it can't handle it, an Odin to stock will be in your immediate future.

[Idea] Faster Charging

I noticed that in aosp roms, the battery charges faster. If we could hunt down the reason of this, we can implement this in touchwiz based roms.
Sent from my SPH-D700 using XDA App

Possibly they use less power when the phone is idle (ie less apps running in the background, maybe undervolting). Since they use less power sitting there, they would charge faster.

Doesn't our aosp rom still have touch wiz framework?
Sent from my SPH-D700 using Tapatalk

gtuansdiamm said:
Doesn't our aosp rom still have touch wiz framework?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
He's talking about actual AOSP roms like cyanogenmod.
Texted while driving

Well Gingerbread in itself is more energy efficient..its one of the features of gingerbread...that and hummingbird optimizations help too..the faster it completes the process the faster it can go idle.

on related note, I'm wondering if it's possible to undervolt even more at say 200Mhz when the phone goes to sleep ??
just curious if it would even allow the phone to wake up, negative effects, etc. or 'might' it be worthwhile ?

gtuansdiamm said:
Doesn't our aosp rom still have touch wiz framework?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
We don't have a real AOSP rom.
Sent from my Frozen Epic using XDA App

daddymikey1975 said:
on related note, I'm wondering if it's possible to undervolt even more at say 200Mhz when the phone goes to sleep ??
just curious if it would even allow the phone to wake up, negative effects, etc. or 'might' it be worthwhile ?
Click to expand...
Click to collapse
I had -125mV and when the battery got below 40% phone wouldn't wake up. So that will vary from phone to phone.

daddymikey1975 said:
on related note, I'm wondering if it's possible to undervolt even more at say 200Mhz when the phone goes to sleep ??
just curious if it would even allow the phone to wake up, negative effects, etc. or 'might' it be worthwhile ?
Click to expand...
Click to collapse
Not sure whether you meant "undervolt" or are talking about the processor speed being throttled back... two different things (but your units for the 200 are wrong for undervolting). Are you talking about undervolting or CPU speed?

beejmeister said:
Not sure whether you meant "undervolt" or are talking about the processor speed being throttled back... two different things (but your units for the 200 are wrong for undervolting). Are you talking about undervolting or CPU speed?
Click to expand...
Click to collapse
I believe he is talking about both, undervolting at each clockspeed. I do this with Voltage Control.
Do you BONSAI?

marcusant said:
I noticed that in aosp roms, the battery charges faster. If we could hunt down the reason of this, we can implement this in touchwiz based roms.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
this has already been done, nubecoder did it with an older bonsai kernal. works great, unfortunately no one else wants to do it. battery charges much faster and fully to 100% instead of 97%.
I'm not using the kernal now because it doesn't work with cpu spy and it doesn't work with wifi tether. but the info is there on how to do it and should be easy to do to other kernals. Unfortunately i don't have the knowledge to be able to do something like that.

beejmeister said:
Not sure whether you meant "undervolt" or are talking about the processor speed being throttled back... two different things (but your units for the 200 are wrong for undervolting). Are you talking about undervolting or CPU speed?
Click to expand...
Click to collapse
I was talking about both, throttling back the CPU when sleeping AND undervolting the 200mhz step at the same time while sleeping to conserve battery more, thereby 'hoping' for a quicker charge.
just an idea.