A newbie here
I tried to overclock my atrix 2 using milestone overclock (first saw on bullet rom :0)
and by manually editing the script and executing it from root explorer i was able to overclock to 1300 mhz , but when i ran a benchmark (quadrant) there was only 10-20 points change from bechmark on 1200mhz . can anyone explain the reason
also my friends sgs2 (not overclocked ) is far way ahead from me
so is this overclock for name sake ?
Cpu isnt the only thing a benchmark tests and adds into your result. Its also memory,i/o writes,other system functions when u run a test.
So just because the overclock is there.its not the only factor,its just one of the factors that a benchmark tests.its a combination that produces the benchmark result.
Sent from my MB865 using xda premium
rdavisct said:
Cpu isnt the only thing a benchmark tests and adds into your result. Its also memory,i/o writes,other system functions when u run a test.
So just because the overclock is there.its not the only factor,its just one of the factors that a benchmark tests.its a combination that produces the benchmark result.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
a big fan of u thanks for answering and one more thing why milestone overclock doesent work on ics ?
After changing the values in oc3 or 00opptimize (or wherever you made changes) did you reboot before running benchmark tests? I've seen that in simply changing echo 3 values to overclock without a reboot doesn't take effect.
Also, sdcard class is a factor, as mentioned above. If using the AnTuTu app for benchmark testing, its the last test performed, so if you're running a class 6 or less, you'll have lower scores. Be wary though, anything above class 6 can create problems with the A2.
I've OC'd to 1250MHz stable, and am hitting (on average) 6250-6300 results -beating SGS2 scores. 1300MHz seems questionable, since I had to do some very fine tuning to achieve 1250MHz on the A2.
1300MHz seems pretty ambitious. Surprised if you hadn't experienced any freeze or random rebooting at that clock speed...
Sent from my MB865 using xda premium
reply
Apex_Strider said:
After changing the values in oc3 or 00opptimize (or wherever you made changes) did you reboot before running benchmark tests? I've seen that in simply changing echo 3 values to overclock without a reboot doesn't take effect.
Also, sdcard class is a factor, as mentioned above. If using the AnTuTu app for benchmark testing, its the last test performed, so if you're running a class 6 or less, you'll have lower scores. Be wary though, anything above class 6 can create problems with the A2.
I've OC'd to 1250MHz stable, and am hitting (on average) 6250-6300 results -beating SGS2 scores. 1300MHz seems questionable, since I had to do some very fine tuning to achieve 1250MHz on the A2.
1300MHz seems pretty ambitious. Surprised if you hadn't experienced any freeze or random rebooting at that clock speed...
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
oh yes i think i have not rebooted from that time
i will try rebooting
and yes i have a stable overclock to 1300 (it shows 1300 in setcpu and no error in its stress test)
i have a class 4 sdcard may be thats the problem
and guess what i tried 1250 oc but it bootloops and its stable on 1300 oc ???? little astonishing
answersamir said:
oh yes i think i have not rebooted from that time
i will try rebooting
and yes i have a stable overclock to 1300 (it shows 1300 in setcpu and no error in its stress test)
i have a class 4 sdcard may be thats the problem
Click to expand...
Click to collapse
Class 4 is fine, I run a class 6 32GB sdcard. Never had any issues. If you haven't rebooted after changing echo 3 to 1300MHz, you may experience that freeze and/or bootloop I described above.
A lot of users have had limitations running any higher clock speeds than 1122MHz, so I'd be very astounded if you were able to clock at 1300MHz -just from my experience.
But, if you are able, you have gotten lucky. Side note: hope you have a portable external battery charger (WPS-601-P793) because your battery is going to be gobbled up like a Thanksgiving turkey.
Sent from my MB865 using xda premium
What are some of the better benchmark apps??
Sent from my MB865 using xda premium
NDSoul said:
What are some of the better benchmark apps??
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I use AnTuTu Benchmark, as well as do some others here. I haven't tried any of the others, like Quadrant Standard Edition or others, but they'll probably do the trick as well...
Here's my last benchmark test result, running rdavisct's and JRW 28's new SuperCharged V6 rom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whats ur clockspeed
Sent from my MB865 using XDA
answersamir said:
Whats ur clockspeed
Sent from my MB865 using XDA
Click to expand...
Click to collapse
When I was running Lithium v1.2.1 I was OC'd at 1250MHz. Now, running rdavisct's and JRW 28's new SuperCharged v6 rom, I'm running stable at 1225MHz. You just have to fine tune the clock speed accordingly -you don't want to get into any bootlooping, freezes, or random reboots.
Also, underclocking is a good idea when OC'ing. I have UC'd to 240MHz at echo 0, which helps out the CPU usage to battery load.
This is pic of my latest benchmark from chainfires app
I have problem in antutu whenever i test i get stuck on sd card write speed any ideas why
Sent from my MB865 using XDA
answersamir said:
This is pic of my latest benchmark from chainfires app
I have problem in antutu whenever i test i get stuck on sd card write speed any ideas why
Sent from my MB865 using XDA
Click to expand...
Click to collapse
What class sdcard do you have?
Class 4
Sent from my MB865 using XDA
answersamir said:
Class 4
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Not sure why you would have any problems during the sdcard read/write tests. I have a class 6 32GB sdcard. How long is it "stuck" on that test, it may be that it just takes longer than you might normally expect. Try to do a Titanium backup of your apps, then format your sdcard, and try running again without restoring your apps. (?)
Sure i will give it a try and does tweaking the sdcard speed might causing problem??:what:
Sent from my MB865 using XDA
answersamir said:
Sure i will give it a try and does tweaking the sdcard speed might causing problem??:what:
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Are you using Rom Toolbox to change the read/write kb values?
You would be surprised at how much you can tweak a class 4
Apex_Strider said:
When I was running Lithium v1.2.1 I was OC'd at 1250MHz. Now, running rdavisct's and JRW 28's new SuperCharged v6 rom, I'm running stable at 1225MHz. You just have to fine tune the clock speed accordingly -you don't want to get into any bootlooping, freezes, or random reboots.
Also, underclocking is a good idea when OC'ing. I have UC'd to 240MHz at echo 0, which helps out the CPU usage to battery load.
Click to expand...
Click to collapse
A NOTE ON OVERCLOCKING
The best way to get a high overclock is to "crawl" your way up. Don't just jump from 1000mhz to 1250,1200,etc.
Try it like this, increments of 20 1120,1140,1160,1180.etc..
This is for the ones who face bootloops when trying 1200+
After each overclock climb with 20mhz,let phone run at that speed for like 5 - 10 minutes. Open some Apps,open menus,etc. And THEN oc another 20mhz and repeat.
This is what i did and my phone never bootlooped because an overclock.now if i wanted to i could run mine at 1300(of course i will not because i don't feel like charging my phone every half hour, but you get the point)
Try this out if you face bootloops and cant seem to oc your phone to 1200mhz or more.. let me know your results and if this helped.
Sent from my MB865 using xda premium
rdavisct said:
A NOTE ON OVERCLOCKING
The best way to get a high overclock is to "crawl" your way up. Don't just jump from 1000mhz to 1250,1200,etc.
Try it like this, increments of 20 1120,1140,1160,1180.etc..
This is for the ones who face bootloops when trying 1200+
After each overclock climb with 20mhz,let phone run at that speed for like 5 - 10 minutes. Open some Apps,open menus,etc. And THEN oc another 20mhz and repeat.
This is what i did and my phone never bootlooped because an overclock.now if i wanted to i could run mine at 1300(of course i will not because i don't feel like charging my phone every half hour, but you get the point)
Try this out if you face bootloops and cant seem to oc your phone to 1200mhz or more.. let me know your results and if this helped.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
This is what I do (I think I learned this from you, rdavisct!) and never had any problems "seasoning" the CPU to run higher clock speeds. Works great, though a little time consuming -but sure beats bootloop'n and freezing your device -which is even more time consuming!
rdavisct said:
A NOTE ON OVERCLOCKING
The best way to get a high overclock is to "crawl" your way up. Don't just jump from 1000mhz to 1250,1200,etc.
Try it like this, increments of 20 1120,1140,1160,1180.etc..
This is for the ones who face bootloops when trying 1200+
After each overclock climb with 20mhz,let phone run at that speed for like 5 - 10 minutes. Open some Apps,open menus,etc. And THEN oc another 20mhz and repeat.
This is what i did and my phone never bootlooped because an overclock.now if i wanted to i could run mine at 1300(of course i will not because i don't feel like charging my phone every half hour, but you get the point)
Try this out if you face bootloops and cant seem to oc your phone to 1200mhz or more.. let me know your results and if this helped.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
This is a GREAT guide to not only OC your phone but OC in general! I feel like most are wayyyyyy too impatient when doing their OC.
Is there a sticky somewhere with these steps (or something similar)?
Sent from my MB865 using xda premium
Related
So I found a kernel on the Fascinate forums that was built off of our EC10 froyo source that was from nemesis2all and I saw that he had added the ability to overclock and undervolt from within the ROM so I installed it just trying (backed up of course) and found that it does indeed work.
I then got the Voltage control app from the market and started playing around doing Quadrant scores throughout after each change. I found that at 1200 mhz I was getting 1600s instead of 1400s and the phone ran great. But when I tried 1400 mhz the phone froze up and restarted while doing the CPU section of the Quadrant test so I reverted back.
My question is, what would be safe to stay at for general use?
Second question, how do you use the voltage app to undervolt I see the settings but I don't know what to set them too.
Here is the link to the kernel
1200 has proven to be the most stable overclock, any higher and it will freeze up eventually.
With voltage control, the way it works is that you set the max clock and then it will give you increments that the phone will automatically clock to within the guidelines you give it. Then for each increment you can set the voltage it will use. Just look around and experiment with voltages, see how low you can go without having issues and never set it to apply at boot unless you know that's what you want, other than that go crazy and a reboot will fix it if you have a problem.
I recommend keeping setCPU installed along with it, that way you can still force it to underclock or overclock or whatever. It all depends on how much you use the phone and what for.
Sent from my MIUI SCH-i500
Thanks sage I'm glad someone who knows what their talking about replied lol.
Swyped using USCC Mesmerize
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
akellar said:
I've been running overclocked at 1.3 and undervolted at least 50 for a couple days now. Only one issue and I'm not even sure it was related as it janet happened again. I posted my settings in the otb thread if you're curious.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
I've been running it for a week @ 1400 -25 undervolted and haven't had any issues. The new 1.6 gives me trouble. I don't think there's enough overvolting in that one to make it stable for pretty much anyone. I use the 1400, 800, 400, 200 steps all undervolted @50 except 1400 which as mentioned is -25. Battery life is good because during sleep it doesnt really hit the high end and by not having the other steps its snappy when in use. Fastest this phone has been by far. I don't use setcpu because I think it and the voltage app conflict. That was nemisis's instruction to install it.
Sent from my SCH-I500 using XDA App
sageDieu said:
H'm, I tried going up to 1.3 and it would freeze up after 5 or 10 minutes every time.
Like I said, 1.2 is the only one that has proven to be safe for everybody... not each phone is exactly the same and if akellars CPU has a soldering that is done a little bit different than mine, it might allow him to clock a little higher. who knows
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Yup I'm just lucky 1.4 worked for me too but I didn't see much of a performance difference so I didn't see the need to stress the cpu out anymore than I already was. battery life had been awesome for me with my setup as well.
Sent from my SCH-I500 using XDA App
I have a question about this kernel, i have it installed on the phone and flashed on it, it said in the post from nemesis2all that there was a Battery hack, i was curious how to use it, i currently have settings at Min=400 max=1300 all settings undervolted 50mV, how good are these settings? and would this be the optimal settings for performance and battery life? or anyone have a better setup that would help. seem to be getting high 1700 quadrant scores with how it is now.
In order to get the best battery life you would not want your phone over clocked, I run otb kernel as well and just uv the stock setting starting at 50 for the 1000, and progressively stepping down to negative 100. Anyways I run, 1000 -50, 800 and 600 -75, 400 200 & 100 at -100 and I have great battery life even with heavy usage and playing memory intensive games, paradise island, drag racing, pocket soccer. Unless your phone is laggy after you enable lagfix I think overclocking is probably just killing your battery faster the only roms I used light oc' ing for was phoenix and miuiwiz, where both launchers seemed to get some lag after a long days use
Sent from my SCH-I500 using XDA App
The other school of thought on battery life is, if you overclock the processor, it will finish the task faster and return to a lower power idle state sooner.
well also i used SuperOneClick to root the phone, is rageagainstthecage a good root to use? or are there better ones out there? also sometimes this kernel like to freeze at start up and i have to re flash it. im pretty sure this isnt supposed to happen. any help or advise is greatly appreciated
I've had issues with OTB kernals before. Your problem could be the kernel, but I see you oc'd it to 1300. That too could be causing it. Each phone reacts differently to kernels and oc/uv.
Sent from my SCH-I500 using XDA App
Are we able to still use any touchwiz kernal from ec10 on the new heintz 57 ee19 updated rom?
Well I re-flashed it and used same ovetclock just lower volts and am pulling a average 2100 quadrant score. Don't know if it means much but no lock ups anymore
Sent from my SCH-I500 using XDA Premium App
This could just be my stupidity, but if you can flash kernels then you have a custom recovery, right? What's the point of using super one click? Wouldn't having the recovery and the ability to change kernels, etc mean your already rooted? Just seems redundant, I never used a rooting app and still use all the root only apps....
Sent from my SCH-I500 using XDA App
evilntention said:
This could just be my stupidity, but if you can flash kernels then you have a custom recovery, right? What's the point of using super one click? Wouldn't having the recovery and the ability to change kernels, etc mean your already rooted? Just seems redundant, I never used a rooting app and still use all the root only apps....
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Kinda. The only way to flash a kernel is with a custom recovery but you don't necessarily have to be rooted to do that. EE19 is not rooted so that's why you need SOC if you want to root. Rooting opens up a lot of options for apps and moving and copying system files but isn't required for Roms/Kernels.
Anyone have any other general good ideas or cool tricks to do to this phone?
Sent from my SCH-I500 using XDA Premium App
Currently, im doing a bit of testing with the new phoenix 1.1 rom.
This baby can handle some crazy undervolting.
Currently:
1000 : -100
800 : - 100
600: -100
400: -100
200: -150
Going to see what i can get this down to...a bit more tweaking i bet the battery life can get phenomenal.
Try opening and closing the camera a few times in a row and see if it freezes. Or try a quad test, those are usually the things that will cause issues with too much under volting.
Sent from my SCH-I500 using XDA App
akellar said:
Try opening and closing the camera a few times in a row and see if it freezes. Or try a quad test, those are usually the things that will cause issues with too much under volting.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Already ahead of you. Up to:
1000 : -100
800 : - 100
600: -100
400: -150
200: -175
Usually ill run 4 quadrant tests and if it passes that it should be stable. Currently ran a 2187 is that a good score for 1.4ghz?
Sent from my SCH-I500 using XDA Premium App
also when using the OTB kernal what are safe settings to use? ive been running it at 1400Mhz but it lockes up and geeps giving me force close things on start up and never stops and i have to reflash to stock and start over? im assuming this isnt typical, can any one help out?
Actually that's probably pretty typical for an OC that high. I know I can't run it that high without lockups. From what I see in the original thread, most people don't run above 1300 most of the time.
Hello everyone. I have had my Nexus S 4G for about 2 weeks now, and I have tried everything I can think of. However, I cannot overclock my phone higher than 1.2GHz. If I set it to 1.44GHz (or even 1.3GHz in most kernels), within the first five minutes, it locks up, requiring a battery pull. I have tried just about every kernel. Trinity, Netarchy, Matr1x, everything. However, I get the same result. I am assuming that it is just my phone. I know that when I had my Evo, it didn't want to OC past 1.1 GHz stably, but the refurb I got from Sprint ran at 1.21 GHz like a champ. I was just wondering if anyone had the same issue, and if so, if it was possible to alleviate this problem. I would love to run my Nexus at 1.44 GHz, because some of the Quadrant scores look amazing.
Thanks again for reading,
StompySan
Try v9.0 of matrix and set it to 1.3
Lemme know plz
Sent from my Nexus S using XDA App
mathkid95 said:
Try v9.0 of matrix and set it to 1.3
Lemme know plz
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
After running Quadrant twice with it set at 1.3, I got a lockup. 100% not responsive. Had to pull battery.
EDIT: I tried benchmarking my phone with CF-Bench, thinking maybe it could have been a fluke with Quadrant, and had the exact same results. At 1.3 and 1.46GHz.
1.2??
Sent from my Nexus S using XDA App
1??
Sent from my Nexus S using XDA App
Ok if neither of those work I need you to do 2 things.
1. Raise all voltages by 30
2. Set it to 1.2 ghz
Sent from my Nexus S using XDA App
I can overclock without reboots to 1.2. Any higher than that is when the problem arises.
Ok now once you flash v9.0, go into setcpu and raise all voltages by 30
Now try 1.3
Sent from my Nexus S using XDA App
mathkid95 said:
Ok now once you flash v9.0, go into setcpu and raise all voltages by 30
Now try 1.3
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When you say all voltages, you mean even the ones that it already runs stably on?
No no, just the unstable ones
Sent from my Nexus S using XDA App
OK, so Quadrant ran fine for 5 tests, and CF-Bench ran OK as well. Should I push it up to 1.46 now?
Try it, and if you get a reboot, raise voltage for 1.46 by 10.
Sent from my Nexus S using XDA App
No lockups yet! I have ran Quadrant 5 times, CF-Bench 2 times, and Linpack a couple times. Seems to be doing great! I am going to test it more thoroughly tomorrow (it's almost 1AM where I live, lol), but it seems great right now!
I have never increased the voltages on a phone CPU before. I have done it on my brother's computer when I overclocked his processor, but I generally try to avoid it. I am just really paranoid to mess with the amount of power going through the processor. That's why I turned to the professionals in this case. Thanks again for your extremely quick reply.
Cool! you just needed a bit of a voltage push, that's all
let's hope 1.46 ghz runs well
Mathkid Ive never been stable past 1.3 so I followed what you told him to do and what do you know! Perfectly stable so far at 1.44 on apocalypse kernel!! Might have to try your 9.0 at 1.46 soon!
Sent from my Nexus S 4G using XDA App
So is there a limit to how far one should overvolt? I upped the voltage at 1440 mhz to 1550 mV. Did run rather stable except for "Lets golf HD!" which froze. I would really like to be able to run at 1440, but not sure what to do. Im using Apocalypse Talon 3.2.1.
Do you think your kernel would handle OCing better, mathkid?
Yeah you can try it out and if you need to raise voltages go ahead
I know that if you OC/UV incorrectly, it can cause stability issues. But I was wondering does it cause any damage to the phones hardware like battery, etc? And like how can you tell when SETCPU is causing problems?
Sent from my LG-P999 using xda premium
Well if you OC to high numbers your just stressing the cpu more.Knowing when you have issues is simple getting random reboots,phone getting too hot etcc.
It differs for every phone but undervolting -25 for each voltages works well.
Personally I really don't see the point overclocking to high levels like 1.4 ghz etc,Is up to individual I guess.
Sent from my LG-P999 using XDA
daxecutioner24 said:
Well if you OC to high numbers your just stressing the cpu more.Knowing when you have issues is simple getting random reboots,phone getting too hot etcc.
It differs for every phone but undervolting -25 for each voltages works well.
Personally I really don't see the point overclocking to high levels like 1.4 ghz etc,Is up to individual I guess.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Yeah I have been wondering what's the point of OC to 1.4? Does it make that big of a difference in the 4g speed? And cpu speed?
Sent from my LG-P999 using xda premium
Honestly, there really is no point other than for benchmarks. I, like mt3g, actually underclock the phone to something like 750-760mhz; it runs beautifully smooth.
Other than that, if you game a lot and want to maximize FPS, then overclocking would do that for you.
Doesn't have anything to do with 4g speed afaik. That's entirely reception.
Yeah 4g is about reception and tmobile simply.
I mean I had single core devices like MT4g ,SGS 4g for the most part on a day to day basis transitions to transitions theres not much diffirence in terms of speed. Now for FPS and a few other games you need that dual core.Point is there"s no need to OC a dual core phone!
Sent from my LG-P999 using XDA
I have had mine OC'd to 1.1 ghz with some undervolts. It is very stable , 10-12 hr battery with medium to heavy use , and ofcourse fast. Took a while to find the best settings.
When I have SetCPU set to 1015 megahertz, that's the same as stock voltage, isn't it?
NekoNyapii said:
When I have SetCPU set to 1015 megahertz, that's the same as stock voltage, isn't it?
Click to expand...
Click to collapse
What does CPU speed have to do with voltage?
theking_13 said:
What does CPU speed have to do with voltage?
Click to expand...
Click to collapse
I meant the same as stock speed.
Sent from my LG-P999 using xda premium
setcpu phone overclocking
Changes you might see are battery life but not that much unless you so how mess with voltage. Like other have said you know it effecting stability when its overheating, shutting down randomly, exiting program randomly.
Alright, before I OCed my phone, and before Chainfire, or AntonX's kernel, I took the test. I think I remember my score being around 2400. If I'm not mistaken, the lower the score the better? Or is it the higher, the better?
Anyways, I'm now OCed at 1.3, running VB Final, Anton's kernel.. and my score is only around 1800. The way the chart shows, the higher the number, the better. How can I get better scores? What is an ideal score for performance?
Also, I've notice a sizeable drop in the FPS during the test, from what it used to get to. The test breaks down as such:
Total: 1808
CPU 1366
Mem 1739
I/O 3720
2D 309
3D 1904
I wish I could remember the details of the last test, for comparison.
Run the test four times in a row. Then let us know what the numbers are. And higher is better
Running tests now, but wanted to go ahead and mention that for some reason today, my phone has been unlocking into the camera.
Ok, Score:
Total: 1845
CPU: 1389
Mem: 1796
I/O: 3955
2D: 175
3D: 1910
If it helps, some additional information:
After flashing my ROM, my phone would reboot once a day. Always while I was asleep. It wasn't really a bother, but after researching the forum a while, I found a fix: Go into CWM, Fix permission, wipe partition cache, wipe Dalvik chache. This worked. This was before OCing
Like previously stated, I'm on VB Final, with boostershot. I'm using AntonX's 1.1rc2 kernel. I have Chainfire 3D, with all three plugins installed. I'm OCed with SetCPU @ Max 1300 / Min 200
Quick Note, fixed phone unlocking into cam. Stupid me
Alright, I've been seeing some crazy high scores, like 2800 and 3400. Are my current ones where they should be? I'm using the app Quadrant Standard.
Are there any tweaks or anything, that could go with my ROM to get my score up? I have Booster Shot already for VB.
How does your phone feel with your day to day usage? Is it lagging? The reason I ask is because benchmark test are not always accurate, hence why your scores fluctuate so much... If you search benchmarking a Android device you'll understand what I mean.
So you can have really high quadrant scores but your phone can be laggy when you open apps, play games, surf the web, take pictures or anything else you may do with your phone.
Good luck
Sent from my SGH-T959V using xda premium
QUIETLYloud said:
How does your phone feel with your day to day usage? Is it lagging? The reason I ask is because benchmark test are not always accurate, hence why your scores fluctuate so much... If you search benchmarking a Android device you'll understand what I mean.
So you can have really high quadrant scores but your phone can be laggy when you open apps, play games, surf the web, take pictures or anything else you may do with your phone.
Good luck
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Yes, I've read the debates and facts in threads regarding the tests. I'm aiming to get slightly better performance. I know people can play intesive games on these devices with literally NO LAGGING, or stuttering. Like GTA 3, or Let's Golf 3. I'm trying to get there. So far, I'm WAY closer than when I started out as just plain rooted. It's playable now, but still stutters and lags more than it should.
what's your governor, i/o scheduler and scaling?
Sent from my SGH-T959V using xda premium
My governer is Smartassv2.
I don't know what you mean by i/o, but on the governer settings it says:
io is busy 1
powersave bias 0
ignore nice load 0
up threshold 45
sampling rate 32500
There's no scaling option, you just set min and max, which i have at 200/1300
My governer says ondemand, even though i have it set to smartassv2. It said smartassv2 before i rebooted earlier.
My governer is Smartassv2.
I don't know what you mean by i/o, but on the governer settings it says:
io is busy 1
powersave bias 0
ignore nice load 0
up threshold 45
sampling rate 32500
There's no scaling option, you just set min and max, which i have at 200/1300
I got it set back to smartass v2
When I was running VB Final with booster I would run a min of 2400. Using ondemand as govener I also use app called sd card speed increase. This is pretty consistent with all roms I run.
Sent from my SGH-T959V using XDA
Anyone else have any tips? I know I've heard people talking about gta3 being lag free and stutter free on this device.
Try it set to performance, but the battery life will suffer
Sent from my SGH-T959V using xda premium
This is what I got
Sent from my SGH-T959V using xda premium
That's about what I'm getting now. I reckon it's normal. Thank you so much!
This is what I got first is stock no or uv second is on to 1.2ghz Sent cap they won't upload says wrong format anyway first I got 2900 second one 3400 ill try screened again later
Sent from my SGH-T959V using XDA
anoymonos said:
This is what I got first is stock no or uv second is on to 1.2ghz Sent cap they won't upload says wrong format anyway first I got 2900 second one 3400 ill try screened again later
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
How did you manage that!? Are you using the same app for the test that I am?
Wodensman said:
How did you manage that!?
Click to expand...
Click to collapse
All sorts of things can can be managed with a little know how. Here's one from Erikmm's MIUI OC'd to 1.5 just for fun.