Related
when i run long bench with setcpu i'm getting results in the 3,000's. this is rather high isnt it? i'm running damage control 3.2.3 with ffolkes normal volt kernel. any advice with this would help, thanks!
edit - errr should've posted in the Q&A, my apologies.
Just ran on mine with:
BB v0.4
Samdroid JIT
nova fps fix
1190MHz OC
score: 724ms
Linpacks avg around 21
I have Darchs latest Froyo build and it seems to run great without jit enabled.
Who's running without jit enabled and who with? Also post what rom you are using.
I'm just curious as to whether some of y'all benefit having jit enabled.
Sent from my Froyo Hero using the XDA app
I have JIT enabled on dd 2.8 but I rarely see any increase in speed. My linpack scores even run about the same (4.7+).
mbobino said:
I have JIT enabled on dd 2.8 but I rarely see any increase in speed. My linpack scores even run about the same (4.7+).
Click to expand...
Click to collapse
You can get 4.7 in linpack without JIT?
Yeah but I have 50+ apps and I stay around 2.9-3.1 mflops on Froyo without jit.
Sent from my Froyo Hero using the XDA app
seriously who gives a **** about linpack scores? no i don't use JIT, too unstable.
markus_del_marko said:
seriously who gives a **** about linpack scores? no i don't use JIT, too unstable.
Click to expand...
Click to collapse
Linpack is a common and accepted way to benchmark. Just because you don't care about it doesn't negate it's overall effectiveness at what it does.
Edit: And I was wrong on my scores. I get about 3.3 w/o JIT and still don't notice any difference.
Now that Froyo is in a RC build who runs jit enabled on it?
Sent from my Froyo Hero using the XDA app
Tried the RC1 with jit and had pretty good results, no FC's except for the common one in the market. Running the 818, jit enabled, with the uncapped kernal and never could I believe this phone would be this fast. Still the FC in the market though
So does jit drain the battery more?
Sent from my Froyo Hero using the XDA app
i have jit enabled on 8/16 build and im only getting 2.9 mflops...stock kernal...maybe i need to try the uncapped kernal for cm6??
CM6 8/18 build. 8/18 #7 Decad3nce 691mhz uncapped w/ JIT enabled - 4.7 linpack
Currently figuring out my battery life. It did drop severely from the old Fresh 2.3.3 I was running with the 2.6.34 uuV kernel. Just wiped the battery stats and applied the collin battery tweak. We'll see how it goes. Unfortunately, I did not take any note of battery life before enabling JIT - I pretty much did it immediately after dropping 2.2 on.
james33440 said:
I have Darchs latest Froyo build and it seems to run great without jit enabled.
Who's running without jit enabled and who with? Also post what rom you are using.
I'm just curious as to whether some of y'all benefit having jit enabled.
Click to expand...
Click to collapse
I'm running nfinitefx45's latest deoxed rom, urushiol's vUV2 691 kernel with Zen's kernel on top of that, and jit enabled.
Apparently, jit has no effect on my battery life, because I'm getting absolutely astounding battery life ... better than I've ever gotten before, in fact, and keep in mind that I'm the one who posted the thread a few weeks ago about getting 110 hours on a single charge!
I'm running AutoKiller with 82-20-98 settings, and I'm using SetCPU carefully dialed in to deliver the best compromise between performance and battery life. I can give you all the specifics on my SetCPU settings if you want them. For the most part, my settings have me effectively running between 558 and 576 mhz max and 19 mhz min during screen-on, and 245 max and 19 min during screen-off.
With jit enabled my best Linpack scores are in the 3.9 range, and with jit disabled I get a best Linpack of 2.4, so jit definitely makes a difference there. It also undeniably makes a difference in how snappy my machine feels.
With the way I've got SetCPU set up, the fact that my min speeds are set to 19 mhz has no negative effect at all on system performance. The phone wakes immediately from even a deep sleep, with no lockscreen lag at all, and touchscreen response when I'm using the phone is instant.
Suffice it to say, I'm extremely happy with my setup.
Cheers and best of luck in your efforts!
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Jeff5886 said:
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Click to expand...
Click to collapse
Well the 3rd I/O test does take the longest to complete. If you are having I/O issues this certainly would give you a fluctuating Quadrant score since so much is I/O affected especially on a voodoo'd SF. Have your other benchmarks taken a dip as well? Does the phone lag in regular use? If its just a Quadrant issue I would not overly panic. Cross check with other benches
My phone did that with voodoo too, I installed dirrks lv 1200, and when I upgraded it started acting up. I did remove the fix before I updated, did everything right, but it still lagged so I just glassed back to stock and did all the steps for remove lagfix. Still on stock kernel now but will install birdman optimized tonight.
Adrynalyne is the man BTW. Ok, as to the OP, have you reset the CPU in SetCPU after you restart your phone? If I don't, I get a score of 1400 ish too.
that would make sense as I believe it resets to 800 instead of 1200
thestigwins said:
that would make sense as I believe it resets to 800 instead of 1200
Click to expand...
Click to collapse
Yes, it resets to 800. 1.2 ghz is nice, I would like to see 1.6. G2 OC'ed at 1450 I believe... Ugh, one day, one day.
No luck with OC kernels
I have tried a few, everytime I get issues. Seems like setcpu just does not play well with this phone. I get 1800 on stock voodoo .2. Don't see a need for the extra conservative 200mhz that an OC can provide. Good luck with the kernels though.
Anyways, as stated, make sure set CPU is set to 1.2 GHz and not 800 MHz which is where it defaults. I use the widgit and crank up the speed any time I'm using the phone, else, I leave it at 800 when charging / idle etc.
Also, go into System Panel (best app killer around) and do an END ALL - it will kill everything... THAN run quadrant. If your scores skyrocket, don't be alarmed. Quadrant likes to have a very clean system to run on, if you have a lot of cached or running applications, Quadrant seems to suffer, I'm assuming due to the delay between it requesting more RAM from Android and the time it takes for it to release it. Seems to make sense as to why it would slow down to me at least based on what I know about how Android handles RAM.
Just make sure to reboot your phone after to restore your normal app library of running apps.
With a 1.2 GHz overclock on jt's voodoo kernel most of us are/were getting about 1925 . I've not ran dirrk's LV kernel, the undervolting is very minimal and I'd rather error on the side of stability, YMMV.
Accused: Everyone flaming & veering off-topic (You know who you are)
Charge: Violation of XDA Anti Spamming, Trolling & Flaming Rules
Verdict: GUILTY
Resolution: All violating posts have been deleted
Warning: Further transgressions might result in a BAN!
COURT'S ADJOURNED!
So I have tried several Kernels over the last 6 months or so. I did not always have SetCPU on my Vibrant so never noticed what the Minimum clock speed was on most Kernels. I recently test drove the new DOW kernel and installed SetCPU to mess around with OC. I went back to what was my daily driver kernel KA7 W/Voodoo. Then I noticed KA7's minimum clock speed was set at 100 MHz?
I have read that some phones have a hard time waking up at 100 MHz. KA7 has been the best performing kernel I have used to date. Battery life has been amazing and never had a wake issue. Is this just a similar situation with OC kernels some processors can run at a lower clock speed then others and also is it normal for the stock kernels to have a minimum clock speed of 100MHz?
Thanks in advance for any info on this subject...
Yes it is normal.
OC Kernels work differently. Some will allow 100Mhz. Others have problems with 100Mhz and can only go down to 200Mhz. It's about the same thing as far as you and your phone are concerned. You won't notice it and neither will your battery.
First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App
Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.
My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.
Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App
Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!
Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.
If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1
I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App