Related
Thanks for all the info on here that I used to root my NC and sideload apps. I was wondering since we have seen that an OC is possible during the root process, what is needed to make an overclocked kernel for the NC?
The stock kernel isn't going to allow it, but it should be possible on custom kernels.
Then again I may be completely talking out of my ass.
Well we were waiting on the source but thats been released sp now we need someone to build a custom kernel ...and ofcourse i can and probably am talking out of my ass but i think that sounds right
Sent from my SPH-D700 using XDA App
See this post. I tried it one more time and I think the touch sensitivity is just my imagination. As far as performance is concerned, it doesn't seem to make any appreciable difference.
The 3630 and 3621 voltages in the power profiles probably need to be mixed and matched since the normal 3621 profile is at a lower voltage at the same speeds as the 3630.
I already postet this in the Atrix 4G section, because they have a thread there about this topic. But they are discussing more about the locked bootloader than about overclocking and as we don't have such a thread here, I will start this one.
Perhaps you think overclocking actually does not make much sense on this device atm, as it is really fast, but I always like to get most out of my hardware that is possible.
I dont think, I would enable overclocking for everyday use now, but it would be cool to be able to do so if needed. At 1200 MHz as Nvidia had planned for the Tegra2 3D the Phone would for sure even beat the Omap 4 in Optimus 3D.
I am totaly new to Android and also to Linux, so I am not sure if this is helpful, but I have seen something very interesting in the Optimus 2x review at Anandtech.
I dont know where these variables are stored and what is needed to, but for me it looks as if we are able to change them, overclocking should be possible on the Optimus 2X.
It would be great if some oft the developers here could look into this when the Optimus Speed finally has been shipped…
I was wondering the same thing. So i checked other Tegra2 powered devices. And as far as i know none has been overclocked yet. Correct me if am wrong.
So far no overclock is needed since this phone is reaaaaaaalllly fast.
But I am sure as soon as it needs some extra power developers will figure out how to do it
Michael Huang (author of SetCPU) has just overclocked the Xoom tablet today. Now, while the Xoom is a Tegra2 device, its kernel is (apparently) Google based whereas others are nVidia based.
In overclocking the Xoom from 1GHz to 1.5GHz though, he saw about a 1/3rd increase in performance on Linpack and Quadrant. Looks promising so far.
Watch the video here http://www.youtube.com/watch?v=cLNjHyAi8BI and follow Michael on Twitter here: http://twitter.com/coolbho3k
The Reason to Overclock the Atrix in my opinion is as follows
The Linux Based Webtop is slow in reviews
So when pluged into mains power it would be very usful to overclock the device to make the most of the webtop with less lag issues making the device far more usful if you need/want that feature.
Maby possible to make a custom dock (stick fan on it) and clock higher
I'm more interested in underclocking, especially when screen is off with a screen off profile in SetCPU. What do you think is the lowest possible frequency I could set it at?
You can put all the way down. I use the same settings in both my N1 and the 2x. Saves some juice. What I really want to see is custom kernels, pref undervolted if its possible.
Sent from my LG-P990 using XDA App
According to the SetCPU changelog, overclocking/underclocking is now possible:
2.1.1 - Fixed an issue with profiles backup in CM7.
- Added support for the Motorola Xoom, Atrix 4G, and other Tegra 2 devices.
- Fixed various bugs.
- Tablet optimized UI and more profiles coming soon!
2.1.1a - Fixed the 0 MHz display issue on some devices.
Click to expand...
Click to collapse
Convel said:
According to the SetCPU changelog, overclocking/underclocking is now possible:
Click to expand...
Click to collapse
How can you overclock with SetCPU then on o2x? Believe only the powersaving underclocking on demand is working.. overclock needs more work i believe.
The Xoom has been overclocked, but apparently the kernels are from google, which made it easier.
If anybody knows more about this, please correct me
The kernel must be adjusted to make overclock work. I got to read myself into this, but perhaps someone else knows already everything to it .
GPU
i wonder if the gpu can be overclocked, would be nice if it was possible too just OC the gpu and compare the results. Or do you think that the CPU and GPU clock speeds are somehow linked???
Any thoughts?
bumping cause im curious. Can any one please answer ?
well this is arm so id day they are linked
are we able to read the clock speed of hte gpu. does is change?
Look at the date mate
The GPU is not linked with the CPU. The GPU is overclocked in different kernels. Spica's kernel allows on the fly overclocking of the GPU.
After having this device for over a year, the only time i needed OC is for 720P Youtube or Youtube HD app. No OC on the GPU has ever been needed. Yes i have been playing around with 1.2 and 1.4, but they just consumed battery more than giving a better experience. I would go so far and say undervolt it and put it on 900Mhz.
New thread to house the custom kernel built with linaro's gcc 4.7.1 toolchain
This *should* work with any AOSP ics rom.
Just because this kernel is built with the linaro toolchain it does not mean the rom needs to be compiled in a certain way.
Download here: http://tinyw.in/gnOy
I'll add more details when i have some more time.
source: https://github.com/invisiblek/android_kernel_htc_qsd8k
toolchain used: http://tinyw.in/gYmj
General question on this--is this kernel intended to be used with the nightlies in your testing folder only, or are its benefits universal? I'm a little confused by this whole toolkit thing...
Sent from my ADR6300 using XDA
polarimetric said:
General question on this--is this kernel intended to be used with the nightlies in your testing folder only, or are its benefits universal? I'm a little confused by this whole toolkit thing...
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
Good question. This *should* work with any ics rom.
I tested this out last night (been running mamarley's kernel) and I ended up switching back for two reasons: first, this doesn't appear to have the 128MHz CPU speed - I'm not sure if that's intentional or not. And secondly, my phone apparently couldn't handle this kernel on 1113MHz - I got lots of FCs. And the rating on Nenamark was essentially the same as my baseline on other kernels.
Just some observations - and your mileage may vary! I really appreciate the fact that this is even being worked on, invisiblek.
EDIT: Totally meant AnTuTu, not Nenamark.
stiltzkin said:
I tested this out last night (been running mamarley's kernel) and I ended up switching back for two reasons: first, this doesn't appear to have the 128MHz CPU speed - I'm not sure if that's intentional or not. And secondly, my phone apparently couldn't handle this kernel on 1113MHz - I got lots of FCs. And the rating on Nenamark was essentially the same as my baseline on other kernels.
Just some observations - and your mileage may vary! I really appreciate the fact that this is even being worked on, invisiblek.
Click to expand...
Click to collapse
Great to hear feedback. Thats all im looking for here really.. It doesnt have 128mhz because its the same voltage as 245 hence no real benefit to having it. Plus some devices are unstable there. I never overclock but i can look at the voltages and maybe get 1113 stable
I can say it works on the new ICS TW rom, drains kinda fast although I think its rom related only.
I had only one reboot, got a freeze and then 10 seconds later a reboot. Its the only one I've had since reapplying new settings.
On freeze I was running SAv2 1113 Max/245 Min.
I have now lowered it to 998 and its running fine on that rom.
Other than that, its amazing.
Sent from my ADR6300 using Tapatalk 2
invisiblek said:
Great to hear feedback. Thats all im looking for here really.. It doesnt have 128mhz because its the same voltage as 245 hence no real benefit to having it. Plus some devices are unstable there. I never overclock but i can look at the voltages and maybe get 1113 stable
Click to expand...
Click to collapse
i take this back, 128mhz is 25mV under 245mhz here
never mind
Can you clear up the linaro tool chain for me, I'm confused as to if the ROM currently utilizes it... and if so is there a certain kernel you have to use along side it. Sorry if that's a stupid question...
Sent from my ADR6300 using XDA
Does this have fast charge?
thekendog said:
Does this have fast charge?
Click to expand...
Click to collapse
I think so, based on this commit below I'd say yes:
add smb329.c for fast charging when plugged into usb
I'm getting some pretty great battery life with this kernel and the 6/21 kang. 1 day and 9 hours after moderate use and I'm still at 30%
Sent from my ADR6300 using XDA
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
FORMAT 1:
CPU
- [FREQ1] [VOLTAGE1]
- [FREQ2] [VOLTAGE2]
- [FREQ3] [VOLTAGE3]
- ,,,
Click to expand...
Click to collapse
FORMAT 2:
CPU GLOBAL: [OFFSET]
Click to expand...
Click to collapse
I also accept 1 frequency result. You don't have to undervolt everything. I favor the last known voltage that crashes as well if you can send this I am even more happy.
Undervolted mine by 50mv
Sent from my Nexus 7 using Tapatalk 2
djjonastybe said:
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
Click to expand...
Click to collapse
In order to use "advanced mathematics" and "complex formulas".. You might want to provide a format for "the results" you want people to provide.. Without a stream of formatted data to input your "complex formulas" and "advanced mathematics" is impossible..
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
djjonastybe said:
..I will make a undervolted kernel that's stable for everyone
Click to expand...
Click to collapse
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
simms22 said:
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
Click to expand...
Click to collapse
I actually came back to post exactly this but Simms22 was too quick, as usual!
Sent from my GT-I9300 using xda premium
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
styckx said:
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
Click to expand...
Click to collapse
Might as well be honest, set him on the right track early in his dev career rather than him rely on buzzwords and fud like some people do.
These are forums for android devices, not Apple devices, the reality distortion field doesn't work here, fancy marketing terms should be left at the door.
Sent from my GT-I9300 using xda premium
My Galaxy Nexus is proof of undervolting being unstable using software while being stable with manually programming the voltages. So I am going to give this a good shot anyway.
My Galaxy Nexus uses SmartReflex to undervolt.
Look at this table I made:
https://docs.google.com/spreadsheet/ccc?key=0AuqacKmGLKJ6dEdJZG5QTmNtQnoyYk0zbm5IanluMHc#gid=1
You see the core or gpu was already crashing at 974mV, which was the reason why I stopped undervolting using the thread. But don't give up, I tried again using SmartReflex because I felt I should be able to get lower. And now I am at 911mV but I did not try to get lower yet.
I plan on undervolting by actually programming it. I don't know how you guys undervolt for the Nexus 7, since I am fairly new with this device.
READ FIRST POST for formatting
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Student's_t-distribution
Using that I can calculate which voltage to take that will work for 90% of us or 99% of us or maybe 100% ?
For that I need some results. The more the better.
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
nodstuff said:
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
^^ Truth
I've done a bit of pc overclocking over the years and we'd always seek out the best steppings to find cpu batches that would give a better clock speed for less volts. What would work on one person's cpu wouldn't work on another sometimes even within the same stepping. (My current machine is getting long in the tooth but it's running a 33% OC below stock volts and stable as a rock.)
When the N7 cpu's are tested the stock voltage is the point where 100% of them will run without issue. Certainly there are many, maybe even most N7's that will run undervolted but until you try it you just won't know. Undervolting needs to be done on a case by case basis.
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
sorry to break the fun lol
Opened a thread with undervolting settings in different situation. For now i think its the lowest possible
bervin said:
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
Click to expand...
Click to collapse
That's exactly the same as what I have done. 100mV right across the board, and I have also never had a reboot or any other negative effect from doing it. Just a bit more battery life.
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
phonic said:
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
Click to expand...
Click to collapse
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
davidoff59 said:
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
Click to expand...
Click to collapse
When either OCing or UVing, you should ALWAYS test out the changes prior to saving them as a persistent boot state. This way, if you set something too high/low and it proves to be unstable, if you restart the device it will revert back to normal.
In the event that you OC/UV too much, yes, you would see signs of instability. In some cases it could show up as soon as you applied to change, in other cases it could take a while to notice. For example, some games or other high processing powered activities could FC/crash. Or your tablet might freeze or reboot. But again, as long as you didn't save your changes as a boot setting, it will be fine once it reboots.
In the event that you did save it, and the settings were unstable for your device, you could boot up into recovery and then manually erase them from taking effect. Recovery doesn't use those settings, as it's technically a different OS. But that can be complicated a process for some. So test test test save. Or don't save and just apply them manually.
Two other points:
Yes, most (all?) devices do have safeguards to protect itself against permanent hardware damage from OC/UVing. If it gets too hot, they will often shut down to protect themselves.
And just because one device can handle being OC'd or UV'd to a certain level doesn't mean they all can. Very minor differences in each component can impact one devices ability from another. The manufacturers only test to see if they can handle the published speeds/etc., but in many cases they can go higher if set to. In others, not so much.
Thanks for that phonic. Given the range of ROMs and kernel's available and the improvements already built in, under volting may not help a lot but every bit helps. Eg this screen on time is pretty good.Close to six hours screen on time with iirc 35% battery remaining.
Paranoid android with motley kernel. I don't over clock the nexus 7 as its fast enough. In fact I under clocked it to 1000 MHz max before and it was still fast but the screenshots are at stock volts and speeds.
it's actually plain simple. If everyone posts results. I can make a kernel with voltages that work for 75% of all people or maybe for 95% of all Nexus 7 owners.
It's called mathematics. But to do that I need as much results as possible.
Easy to do if you know what you are doing, right ?
http://en.wikipedia.org/wiki/Confidence_interval
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
goodrix said:
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
Click to expand...
Click to collapse
That's the actual battery life. With each new android version, you have a lot more processes running in the background. A lot more Google processes too
It should be ok to just flash the update, but if you run into bugs, don't report them as developers don't have a way of telling whether its from issues caused from dirty flash or from the actual ROM itself.
No it will never be available in the ROM manager app. ROM Manager does not search XDA for ROMs and VivoKat is ported by Szeszo personally.
Thanks.
That answers my questions.
And battery life improved after turning off "Location"
You can also log-out from different accounts such as fb, and so one. some of apps are eating battery. For example some email clients...
moreover, you can turn off wifi
you use Vivokat as your daily driver, that one seems still in beta stage
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
otakux said:
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
Click to expand...
Click to collapse
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
otakux said:
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
Click to expand...
Click to collapse
Voltage changes should make a lot of difference too. But not as evident on the vivo as on big quad core snapdragons
The Gpu oc is not really overclock, it's forcing to 245mhz to up performance
Sent from my HTC One using XDA Premium 4 mobile app
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
i do not know that it is really OC, but according to my test.
the frequency is actually higher that it default.
up to 353Mhz, default is 245M.
so i could sure it is overclocking.
this data is collected in it's kernel, the real runtime data.
otakux said:
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
Click to expand...
Click to collapse
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
otakux said:
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
Click to expand...
Click to collapse
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
poondog said:
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
Click to expand...
Click to collapse
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
otakux said:
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
Click to expand...
Click to collapse
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
poondog said:
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
Click to expand...
Click to collapse
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
otakux said:
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
Click to expand...
Click to collapse
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
poondog said:
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
Click to expand...
Click to collapse
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
otakux said:
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
Click to expand...
Click to collapse
Oh nice. I do have the best results on my One with fiops, deadline, row though
poondog said:
Oh nice. I do have the best results on my One with fiops, deadline, row though
Click to expand...
Click to collapse
yep, but according to my linux desktop test, bfq is more better than cfq.