and is it normal for this amount to decrease over time?
I've noticed when switching from rom to rom, that different roms have a different amount of free RAM and some more than others have that amount decrease more rapidly.
I'm back to my stock rom w/o Sprint apps, gk.031 kernel and setCPU and mine will be ~85 on boot but go as low as ~60, but if I go into manage applications or sometimes in SpareParts, it will shoot back up to ~85. When I tried Fresh and Pancake these numbers were significantly lower and seemed to drop of much faster than my current configuration. Is this normal behavior?
Also is this something I should worry about or am I just driving myself insane watching SysTray Monitor?
i am using Gumbo ROM 1.5c FULL w/ Gumbo Kernel Tweaker Edition, at boot up i have about 70mb if i can remember correctly, used the phone heavily, mms, ebuddy running, and listening music from htc widget and i have 55mb free. phone is running smooth as butter and i haven't noticed ANY slowdowns at ANY given time. i can say this rom gave life back to cupcake, i'll be jumping to Gumbo 2.1 when issues are resolved.
stop looking at those stats or switch to my config. setcpu is a mayor player here also. good luck.
Meaning? and I really am starting to think i/m just making my self insane haveing systray running
phiqtion said:
setcpu is a mayor player here also. good luck.
Click to expand...
Click to collapse
you really shouldn't worry too much about ram usage or task killing. android, since its linux underneath, runs the same whether it has 100 mb of free ram of 30 mb of free ram.
but as for a 'normal' amount of ram, it differs. gbhil's kernels have the low memory killer(android's default task killer, search in forum) set pretty aggressively, so you'll get likely above 80 or even 90 consistently unless you lower the settings yourself.
on roms that don't have the internal task killer configured, you'll likely see significantly lower numbers.
Even with gbhils kernel's, I am seeing widely varying #'s. for instance Fresh ran at 60 tops with the gk 0.31, yet it dropped off rather quickly to as low as 38mb. Pancake hit 45 and I nadroid'ed back to my stock configuation with the gk0.31, Gumbo 1.5c seems to be staying at least in the 60's. But that is no where near the 80~90 you speak off....am I missing something?? No task killlers running just SetCpu and the kernels
justinisyoung said:
you really shouldn't worry too much about ram usage or task killing. android, since its linux underneath, runs the same whether it has 100 mb of free ram of 30 mb of free ram.
but as for a 'normal' amount of ram, it differs. gbhil's kernels have the low memory killer(android's default task killer, search in forum) set pretty aggressively, so you'll get likely above 80 or even 90 consistently unless you lower the settings yourself.
on roms that don't have the internal task killer configured, you'll likely see significantly lower numbers.
Click to expand...
Click to collapse
Related
ok i was under the impression that cynanogen mod autmatically over clocks the cpu to 528mhz. But someone told me it doesn't. Does it? and if i use setcpu will affect the stability?
Your not really Oc'ing because the CPU was made to run at a max of 528 and 384 is the stock(Offical OTAs) to save battery life. It will only go that high when needed, you dont drive at a 100MPH just to do it, you do that when no one else is around. It will reach that high under heavy load not if your dialing on just swiping on home.
ace is right from what ive been told and read. the cpu is underclocked so its not hitting its full potential.
also no cyanogen does not do this automatically. this is best done by the user anyway as they can get a prefered setup then on their phone as this does consume battery life.
Ok i downloaded setcpu but i dont see a big difference i selected 528 as max and the max stock as minumum and put set on boot and i rebooted. I dont know why im typing in upper case, im on my g1
to be honest i never really noticed too much of a difference myself.
I've been using SetCPU now for about 48 hours and am very impressed with it. See my sig for current system setup. As far as SetCPU settings: on-demand throttling, 528 MHz max, 245 Mhz min, no profile settings, scaling up setting 75%, and both "set on boot" options checked. The SetCPU settings definitely make the phone snappier compared to the normal CyanogenMod settings.
is there a difference between on demand governor or performance? whitch one is faster?
nahanee20 said:
is there a difference between on demand governor or performance? whitch one is faster?
Click to expand...
Click to collapse
http://www.pokedev.com/setcpu
On demand will scale CPU speed between the minimum and maximum settings, and performance runs it at maximum constantly.
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
BoomBoomPOW said:
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
Click to expand...
Click to collapse
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
TeeJay3800 said:
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
Click to expand...
Click to collapse
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
The main thing that SetCPU does that CM does not is adjust the threshold at which the CPU begins to scale up. I have mine set to 50% which is far lower than CM's setting, and I believe that is the main reason my phone is so much faster.
Also, SetCPU does not stay running in the background. A script runs at boot to apply your settings, but the app doesn't actually run unless you start it yourself.
CM's default up threshold is at 40, so I have no clue where you got the idea that is far higher. Also, it does not affect speed. It's the percent cpu usage before going up a speed step. So actually the higher the threshold, the longer it stays on current/lower speed.
SetCpu does stay running in the background. Open your app drawer, open Dev Tools, Running Processes, and you will see SetCpu (com.mhuang.overclocking) running.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
EDIT: That process is not running.
It boils down to user experience. If it feels cold, then it must be cold. Am I right? But these are all perceptions manufactured by our brain. That is why we have crazy people. I'm not calling you crazy, but crazy people see things that are not there. Perception is the word of the day.
I guess we'll have to agree to disagree. I could measure the before and after difference with a stopwatch, meaning it genuinely is faster. In my opinion, it is entirely possible that SetCPU allows for faster performance than CM does by default. Unfortunately, that is impossible for me to prove via an internet forum. Anyway, it was fun debating with you.
BoomBoomPOW said:
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
Click to expand...
Click to collapse
I've been rooted and running SetCPU for a while but just recently switched to CM. I had CM running with SetCPU until today when I decided to remove SetCPU to see how CM does on it's own. My phone seems exactly the same from what I can tell... if not a tad faster. BUT I really liked the ability to have SetCPU clock the CPU waaaay down when the battery gets below a certain %. I had it set to run at 245max/128min when the battery dropped below 30%... yes it was sluggish but it would stretch that 30% for many hours if I needed it to.
Does CM do anything like this or have a provision somewhere for setting cpu speed based on battery level? I don't like having stuff installed if I don't need to, but missing this feature may have me reinstalling SetCPU.
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
bast525 said:
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
Click to expand...
Click to collapse
Good catch. I'm looking at it now, it gets down to 448mhz while downloading an APP from the market over the mobile network. Once downloaded and installed, it stays between 600-900mhz?? Rebooted and it still never goes below 6, and mostly stays in the 7-800's. Not good! I have a fresh install of Skyraider 2.01 with sense removed, using launcher pro.
I found this really interesting but I think systempanel is reading incorrectly. I say this because if you watch set CPU read the processor you can see that it drops down to 245mhz when idle even though systempanel reads 600-700mhz.
Sent from my ADR6300 using XDA App
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
gkallivrousis said:
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
Click to expand...
Click to collapse
1.2 should be no problem although all phones are different. start with the low voltage at 1.1 make sure the phone is stable. a quick test is to open the browser and load a few pages. a GOOD test is to run quadrant. then just increase the speed until it locks up. pull the battery and set it down 1 or 2 speeds and thats your max stable overclock at that voltage. most people are able to run 1.2 or 1.3 with no issues. i can run at 1.3 with no issues. any higher and after a few days (or less respectively) my phone hangs. Also increasing voltage will yield higher clocks but will drain the battery faster. just play around if the phone locks up just pull the battery. also i would not play with the manual settings until you are familiar with the basic ones first.
I am most stable at 1.25ghz LV. Currently running GummyJAR2.5 with Blueberry Theme.
No issues. I would recomend installing AutoKiller. This is not same as Task Killer. It frees up memory. Same function as the one that comes with Jrummy Overclock but you can customize it more.
auto killer waste battery we have plenty of memory on our phones
so what do you recommend for a jrummy oc? i was thinkin 1.2 on lv
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
friguy3 said:
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
Click to expand...
Click to collapse
yup...some people can run 1.4 with no problems...try upping the voltage a little
1loudsvt said:
auto killer waste battery we have plenty of memory on our phones
Click to expand...
Click to collapse
I wasn't a believer until I installed it. My ram use to run low and some times made my DX run slow. Since installing the autokiller, my DX runs smoother, zippier and consistant. I have mine pre-set at extream. As for the battery, I don't notice any difference and I am semi heavy user. I been running Autokiller for a while.
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
I could never get over 1.1 using jrummy untill I changed the gov, use anything but "on demand" and I can get 1.4 all day. The stock settings work well using the "performance" gov but battery life can suffer if you get crazy. Performance keeps it running at top speed all the time. Hope this helps.
Sent from my DROIDX using XDA App
Droid-Xer said:
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
Click to expand...
Click to collapse
Ive used similar settings and worked fine on my phone running Rubix.
Well ill start off by saying I'm new here and this is my first post. I'm also very new to this stuff and have a lot to learn. A buddy of mine recently rooted and overclocked my phone using the sense 2.6.32.21 1.5ghz oc/uv kernel. I currently have it set to 1.19 max 768 min and am experiencing temps above 107 running emulators and just web browsing.. I am also seeing pretty poor batt life even using battery booster and advanced task killer.. any help is greatly appreciated!
Battery apps and task killers tend to have the opposite of their intended effect on battery. Android has a built in utility to watch battery usage, why do you need a 3rd party one? Also do some reading on task killers, you will see why they are unnecessary on Android. I've stopped using one and my phone runs faster and more stable than before.
768 min is VERY high. Might explain the heating and battery life drain quite a bit.
Try this for me, please. Set your governor to interactive and drop your min down to 245. Run that for a whole charge. You may be surprised.
Sent from my PG06100
Also, I second the post above me. Advanced Task Killer and anything like it ultimately cause more harm than good. Battery apps, such as Juice Defender, also shouldn't be necessary. Although, it is YOUR phone.
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
bearsblack said:
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
Click to expand...
Click to collapse
well they gave some suggestions. which it seems you dont want to listen to. you dont need task killers of any kind
Sorry I'm stubborn. Uninstalling now
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Compusmurf said:
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Click to expand...
Click to collapse
because all the cool kids are doing it smurf...duh.
But seriously, min. should not be set at anything greater then 245. Only use performance if you are benchmarking. Default at the moment should be interactive.
Just gonna add my 2 cents in from personal observation....after doing some reading on overlooking and stuff I've noticed when going into the different ## modes, the shift usually drops its processor cycles to pretty low numbers in the 200-300 mhz range when its just in standby or not doing anything...it only kicks it up when you need the power. So the heating up is probably caused by constantly running at what used to be its max territory...PLUS youre going above and beyond the original limits/specs at a constant so it never gets to relax even when the phone is idle...I hope that makes sense. So as one poster mentioned keep the min at the stock setting and if you really want to/need to then raise the max mhz to whatever your phone can handle reliably. Correct me if I'm wrong anyone who is more into the overlooked setups. Me personally, stock has been able to keep up with whatever I have thrown at it after 30 days and still getting 25+hrs on one charge.
Sent from my PG06100 using XDA App
I currently have it governed at 245 max screen off. Running 1.2ghz max interactive with no task killers or batt savers. Batt life seems to be somewhat better but temps still creep past 105. Thanks a lot for the info
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Excuse me if I am wrong it's early and im too lazy to reread up on it but I believe the difference is with on demand there is a slight delay(second or two) and it gradually kicks up to where it needs to be where is interactive is a spike the second you need it...
JAREDR said:
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Click to expand...
Click to collapse
Interactive is, usually, a lot better for battery life.
If you look at your cpu's scaling history when on the two, TYPICALLY, you'll see a whole lot more time in higher frequencies using ondemand.
That's not to say, however, that with some devices and some kernels they will act the same.
Sent from my HTC Speedy
Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!
http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.
063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.
Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...
Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.
I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.
dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.