Related
hi, i've got a htc wildfire.. well obviously considering i'm posting in this section
anyway, i've installed wildpuzzle 0.8 with the overclocking kernal, what i'm wanting to find out is....
when running setcpu, the cpu will change it's frequency depending on usage.
but what about if setcpu isn't installed and you use the rom to overclock to say 748.. will the cpu stay at 748 permanently, or will it drop down and up natively depending on usage, like setcpu does??
thanks
i would say without set cpu or a specific speed framework, it would revert back to standard 528max 480min
which overclocking kernel have you got, be aware that if you have 130 kernel and overclock, wifi hotspot will not work, you can see phone but you won't be able to connect, you need to use 055 kernel from wildpuzzle 8.0.11 thread.
a small side note, i have just recently changed my overclocking from 691max to 652max, no discernable difference in speed, linpack for 691mhz was 2.9, for 652mhz i'm still getting 2.8 mflops, but huuuuge difference in battery life.
691 max struggling to get 2 days, 652 max after 24 hours i still have 82% battery left.
how do you see this mflops thing? and is it like a cpu score?
subwars said:
how do you see this mflops thing? and is it like a cpu score?
Click to expand...
Click to collapse
Download Linpack For Android from the market, and, Yes, in a way, it is like a CPU Score.
Been lurking for close to a year, but first time posting, so my apologies if this is not the correct forum or location for this question. I would have posted in the Glitch kernel thread but I'm still stuck in the noob-lockout.
I'm running the latest CM7 with the latest, high-leakage Glitch kernel. I became suspicious after I "calibrated" my battery (charged to 100%, reset stats, drained to 0%) and noticed that my battery life was much better while in deep sleep, but with the screen on it was draining at almost 1% per minute. In deep sleep I will get somewhere between 2-5% drain per hour.
CPU Spy shows my frequency breakdown as 1000Mhz at ~10% and Deep Sleep at ~90% with all other frequencies at virtually 0% (this is with resetting the timers and running for a day).
I would think that even with the screen on, there will be moments when the CPU will be throttled down. Running SetCPU on previous roms, I noticed that when idling, the CPU speed would often drop to 100Mhz, but this doesn't seem to be happening with my setup.
I didn't notice any comments in the Glitch or CM7 threads regarding this phenomenon, so I'm wondering if it's something I failed to setup correctly or some other cause.
As an update, I've switched back to the stock CM7 kernel and it is properly throttling down now. 100Mhz is now showing a much higher percentage in CPU Spy.
I would really like to switch back to Glitch, but unless there's some solution it doesn't seem like it's worth the huge increase in battery usage.
Sent from my SCH-I500 using XDA App
You must have a setting incorrect.
Being clocked at 1.2ghz (BFQ i/o and Smartass) CPU spy is telling me the following
1200Mhz - 4:03 - 0%
1000Mhz - 1:01 - 0%
800Mhz - 9:05 - 1%
400Mhz - 7:037 - 1%
200Mhz - 4:59 - 0%
100Mhz - 21:09 - 4%
Deep sleep - 7:40:15 - 90%
What Governor did you try?
I was using bfq with smartass.
Sent from my SCH-I500 using XDA App
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Cota82 said:
I'm also using cm7 and tk-glitch v11 hl since yesterday.
Playing with settings right now, using pimp my cpu and cpu spy.
Questions:
-Do I have to enable the option "force minimal freq. when screen off''?
-After how many minutes does my sgs go into deep sleep mode?
Click to expand...
Click to collapse
Are you experiencing the same increased battery drain with the screen on?
1. Using SetCPU is asking for trouble (random reboots, etc). The Glitch thread OP says to use Voltage Control instead.
2. High Leakage = fewer problems for those with lower quality hardware build (yes, it varies from Fascinate to Fascinate - all Fascinates are not assembled equally), but poorer battery life. Low-leakage = better battery life, but you better hope your Fascinate was assembled well because if it wasn't, you'll have more fcs and freezes than on medium or high leakage.
3. There is no combination of governors, voltages, and schedulers that is the best for everyone - each combo will work better for some than for others
I hope this helps
Another Fascinating post by my XDA app...
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
lagbot7000 said:
I remember reading about the dangers of using SetCPU with this ROM, so I've only been using Voltage Control.
My problem doesn't seem related to the governor or scheduler, since each combination yields the same result.
The problem is that the CPU speed jumps to 1000Mhz as soon as the screen is turned on, and stays at 1000Mhz until it's turned off, which causes it to drop down into Deep Sleep. There is no in between, not with any combination of scheduler or governor, it's either full blast or nothing.
Click to expand...
Click to collapse
Try an overclock - train your phone to use something other than 1000 Mhz
Another Fascinating post by my XDA app...
I decided to restore back to DI01, and use the OTA updates to bring myself back up to ED05. I then reflashed CM7 and Glitch and this problem has gone away. Not quite sure what caused it, but it's running great now.
Running at a solid 1200Mhz with -50mV.
Yes still draining, locked up in 800 mhz cpu freq. (cpu spy) and no deep sleep mode. I'm going to reflash the kernel soon.
Something went wrong I guess (stucked in glitch bootscreen after flashing).
First cleaning scripts and flash the default cm7 kernel for my sgs to be sure.
It should work well according to a member in glitch sgs topic.
Can someone please suggest an overclocking range for use with setcpu? Id like to gain some extra performance and dont mind a higher battery drain,but I am concerned about going too high and cooking the tablet
Any suggestions would be appreciated, thanks!
i believe you need a custom kernel or ROM to overclock; SetCPU will definitely let you underclock just rooted.
Once you have a kernel w/ OC enabled, I'd suggest starting with 1400MHz, then load a cpu-intensive game & play for 30mins or so. If SetCPU doesn't show the temps going north of, say, 110F/43C, increase the max speed by 100, repeat until temps get past your comfort zone, then drop back to the prior setting.
I was unable to find a max suggested temp range for Tegra2, so you may want to err on the side of safety and/or comfort and aim for a lower max temp.
As stated above you need a custom kernel to overclock, but it isn't rom related at all. I have been running mine sense i was able to load a custom kernel at max freq 1,504 Ghz and min 216 Mhz and have never had a problem at all. Using setcpu you can set profiles to save battery life, like screen off profiles and also use different governors to help battery life. I usually just leave my governor set to ondemand and can't complain about battery life or over heating.
thank you to you both! Much appreciated
Please share
1. your favorite governor (do you use any different governor on different profiles?)
2. your voltage parameters
3. Your benchmark using quadrant
Thanks
No one wants to play?
Maybe like me, they have no idea what you are talking about
What is a governor?
What voltage do you mean?
My quadrant score is 3900 ish
Thanks for the reply, I don't think I'm good enough to explain but, in a nutshell,
A governor is a a piece of code in the kernel that decides on the cpu speed. each kernel has multiple governors
voltage is where you can decide what voltage is delivered to your cpu at certain frequency. undervoltage will usually help you save battery. we have to pay attention not to go too low or it phone will freeze
download setcpu it will all become clearer
I will give this another bump before letting it die
Even I would be intrested in sharing this
currently I am using CF root with ondemand and its working all good
FM kernel with interactive. I find my phone snappier with this governor. I liked it the most with smartassv2 on Abysssomething (don't remember now) kernel, but too many teething problems with this one, had to revert to FM. I'll give it another shot soon though.
pjm77 said:
FM kernel with interactive. I find my phone snappier with this governor. I liked it the most with smartassv2 on Abysssomething (don't remember now) kernel, but too many teething problems with this one, had to revert to FM. I'll give it another shot soon though.
Click to expand...
Click to collapse
Do you use any additional profiles with Interactive?
Nope, I like the way it is.
pjm77 said:
Nope, I like the way it is.
Click to expand...
Click to collapse
Have you tried InteractiveX? Or, better yet, know the differences between the two? I am currently using smartassv2, FM kernel and have no complaints but would be interested if there was something a bit snappier when opening an app (I still get a bit of lag if I quickly select an app after unlocking the phone).
Yes, I've tried InteractiveX and OndemandX - they're both absolute rubbish (at least from my point of view). Both responsiveness and benchmark results were dismal (2800-3300 quadrant advanced). These are governors for anally retentive battery life lovers. Nothing wrong with that itself but beats the purpose when buying state of the art top shelf performance smartphone IMO.
Good to know. I appreciate the advice. Does that mean you also tried smartassv2 with the FM kernel? Any discernible difference between that and interactive, if you have? And sorry for all the questions but it saves me the trouble of trying them!
I just flashed the 1.3 FM a moment ago. Now running 100-1704 smartassv2, haven't played with voltages yet. Responsiveness in terms of screen scolling, lags & stutters seems better than 200-1400 interactive. Performance in Quadrant Advanced and Nenamark2 seems a tiny bit worse (but I don't really care about that, I use benchmarks only to roughly estimate, smoothness is what I'm after). I can't give you direct sources because I don't remember, but having spent several hours digging last weekend I concluded that for people who put performance slighly over battery life governors to be considered are interactive, smartass(v2), savagedzed and performance. Funny enough - I'm getting consistently worse benchmarks on performance governor on all kernels. I wonder why?
Thanks again. I will play around with some of the governors and settings to find the right fit. I think I will try savagedzen next but I am pretty happy with smartassv2 and may just stick with it.
Handy explanation of most of the governor options available in custom Note kernels: http://forum.xda-developers.com/showthread.php?t=1369817
AND
http://forum.xda-developers.com/showthread.php?t=1242323
Smartassv2 and vr. After reading a bit about it they seem to be the best for performance and balanced battery life.
i share with you my SetCPU config, voltage ...
it's very stable for me. It's not performance oriented but battery friendly.
what you think ?
EDIT : I use AbyssNote Kernel 1.2
I'm getting nice results here on FM Kernel 1.3. 1704mHz (1375mV) - 100mHz (775mV), lulzactive governor. 5000-5872 in Quadrant advanced, 32-35 in Nenamark2. Battery life good with low to med usage, poor when playing games, running satnav etc. - hardly a surprise We'll see about stability but so far so good.
This thread is finally picking off ! thank you all
I am currently on FM 1.3 and preferring lulzactive
I don't use any over clocking I guess I don't dare. is it safe?
I think i'm pretty aggressive with under voltage i'm running 1175mv at 1400mhz and 775mv at 200mhz. For some reason my phone freezes any time I use the 100mhz no matter the voltage .
Can you share the whole voltage for a comparison ?
with all this I can hardly get a full day of use with my battery but I guess I'm a pretty heavy on usage. no gaming or anything extensive but wifi-browsing-emails-3g-bluetooth all day
ArcticCat said:
For some reason my phone freezes any time I use the 100mhz no matter the voltage .
Click to expand...
Click to collapse
I read on some other kernel thread that Samsung's implementation of the 100mhz step is incomplete/buggy. That's probably why it doesn't work properly.
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
GSF1200S said:
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
Click to expand...
Click to collapse
Did you try reflashing fresh? I'm currently runnin CK23's Urban Precision 1.1 with Samurai 3.0.4 and I'm OC'd to 1400/200. I honestly don't kno why its not working for you, I'll be sure ta mention it in the thread tho.
Sent from a Epic like no other usin XDA Premium....
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
kennyglass123 said:
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
Click to expand...
Click to collapse
Yes, Ive done it a third time just to make sure; 100% reproducible with 3.0.4. The first 2 times I booted ACS ICS 5.5 FIRST, then booted back into CWM to flash the kernel. This last time, I flashed the ROM, then flashed the kernel immediately after. Same result. I guess its just my device? Ive never had issues with this before, so..
Did you clear data in Voltage Control? Perhaps it's your governor.