Database Develop

Is it weird to have 1774 at Quadrant?

Hello all,
I'm quite shocked when testing quadrant and I got 1774 score. Usually I only got around 1400-1500.
Then I tried that time, I had around 1400 for the first time, and I repeat the test directly and get 1774 score.
I repeat the method the next day and get also a huge difference between the first try and the second try.
anyone can explain this??
I'm running CM6 RC2
1113MHz monks kernel

pretty nice score, possibly some other proceses running in the background, i got a 1200+ score then killed a bunch of stuff running and then got a 1500 score

I usually hit 1700-ish.

disgustip8ted said:
pretty nice score, possibly some other proceses running in the background, i got a 1200+ score then killed a bunch of stuff running and then got a 1500 score
Click to expand...
Click to collapse
try again directly after you got 1500 score. I got 1700 for the second try

samsung galaxy s
I did the benchmark before applying the voodoo lagfix on my SGS, i was the third on the list just after moto droid x, after the lagfix and reboot, i'm now 1469 and on top of all the device, the original SGS score is way below...
the point is, how this thing work ? is this reliable ? i mean what's the point of the app finally ?

I honestly think that the score doesn't matter. Isn't the most important thing most aim for is speed and stability? If your phone feels fast then you shouldn't care for the score.
Sent from my Nexus One using XDA App

1774marks? no it's not strange.
Here is a screenshot i have made about month ago on original-chinese-odexed Miui [email protected] without any hacks, it was fast as lighting (Or diarrhea)
Miui12.31 not so fast

Overclock or not?

A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.

ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.

set to 1.13 ghz
then screen off to minimum 245mhz

josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?

Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.

i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App

shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.

im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents

Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.

I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.

Didn't knew the voltage would increase above 1075Mhz, will keep that in mind

ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.

Give us some feedback

I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.

Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.

I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.

liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One

ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One

shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.

Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.

Cyanogen8

Cyanogen 8? Is this next? Or is this in the works? Also is 2.3.5 next and would it be numbered a different version when Ice Cream comes out? Also is anything coming from the devs to overclock to 800 yet?

cell2011 said:
Also is anything coming from the devs to overclock to 800 yet?
Click to expand...
Click to collapse
It's been done. So very very few phones are even stable at 800, and those that could generally performed worse in benches at 800 than at lower clocks. Many of these devices bootloop above 700.

Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.

Also, on a side note, this should not be in the Development section. This should be in general or Q&A

This belongs in Q&A for future reference.
CM8 will be next, obviously. It will be based on Ice Cream Sandwich, so no, it won't be in development until ICS is released to AOSP so that the CM team can start using that code. 2.3.5 is an update coming out soon for the Nexus S 4G that fixes wifi and network speed, as well as adding more secure NFC for Google Wallet. It won't really affect us when it is merged into CM7. ICS is expected to be Android 4.0, but it could be 3.5 if Google decides.
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.

rizdog23 said:
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Click to expand...
Click to collapse
I lol'd at this statement. Did you not read any of the posts above you?

When i began to post there were no posts yet. They must have got posted while i was typing. So seeing as the only post at the time was the op, then yes i did read the post(s) above mine.....

There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
Click to expand...
Click to collapse
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D

dastin1015 said:
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes

rizdog23 said:
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
Click to expand...
Click to collapse
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App

rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.

In before bierce gives birth over ANOTHER question being in the dev section
Sent from my Android using Tapatalk

rizdog23 said:
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
Click to expand...
Click to collapse
Correct me if I'm wrong, but from what I've noticed is that newer Hero's that were sold with Eclair as opposed to the original Donut, when I bought mine, are not able to reach those higher processor speeds past 691Mhz.
Sent from my Hero that never dies! ;D

i bought mine at radio shack back in september and it was still on 1.5 and ive never been able to get over 768mhz without it freezing and bootlooping its different with every hero.
i stay at 352-691 ondemand and thats plenty fast for me

Mine was running 1.5 also and it will run fine at 768 but battery life suffers so I usually run at 352/710 and battery and performance are good (depends on rom kernel)
Where can I get the godmode kernel ....
Sent from my HERO200 using XDA App

I actually got mine two weeks after it came out.....so i mean it could just be that this phone is dead now. I never had a refurb or anything. I got it wet once but it got repaired. I've only had this one the whole time. Do you think that is the issue?

rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks

chalan30 said:
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
Click to expand...
Click to collapse
It depends on the cpu governor that you use.
nandroids are for
sissies

ch1naski said:
It depends on the cpu governor that you use.
nandroids are for
sissies
Click to expand...
Click to collapse
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.

chalan30 said:
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
Click to expand...
Click to collapse
I believe that you can set the ramp up frequency and that may help with the lag. Setcpu, advanced settings, I think?
nandroids are for
sissies

Undervolt/Overclock Captivate...

What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.

RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.

Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD

I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.

PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

overclocking to 1200 mhz will made any difference ?

Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.

[Q] Mini Performance

Hey, i think i have a big problem.
Im using a new ROM (this one http://forum.xda-developers.com/showthread.php?t=2622069) and i changed my Max CPU freq to 729Mhz and Min freq. to 122Mhz using ONDEMAND. So i decided to run a benchmark test using Quadrant Standard Edition and i got around 800 points i was kinda shocked because i saw many screenshots from other Mini Users with 2000+ points using an old ROM in this post -> http://forum.xda-developers.com/showthread.php?t=1437030.
I dont know what i have done to get so low score, i only have facebook and skype installed and greenify. I think my phone is faster then before but with this Benchmark Score i think my phone is in a pretty bad condition
Any suggestion?

erasem said:
Hey, i think i have a big problem.
Im using a new ROM (this one http://forum.xda-developers.com/showthread.php?t=2622069) and i changed my Max CPU freq to 729Mhz and Min freq. to 122Mhz using ONDEMAND. So i decided to run a benchmark test using Quadrant Standard Edition and i got around 800 points i was kinda shocked because i saw many screenshots from other Mini Users with 2000+ points using an old ROM in this post -> http://forum.xda-developers.com/showthread.php?t=1437030.
I dont know what i have done to get so low score, i only have facebook and skype installed and greenify. I think my phone is faster then before but with this Benchmark Score i think my phone is in a pretty bad condition
Any suggestion?
Click to expand...
Click to collapse
Well, what you're running is a Jelly Bean, which is NOT officially supported by Galaxy Mini's hardware.
Also, if you think your phone is already fast, then DON'T believe benchmark. I never choose benchmark for testing phone's smoothness, instead I use the ROM around 1 week, then see how does it responds. If it's faster, then I would say the ROM is good.