Wow, nice tests, a lot faster! And can you give me a bit of info on what setting the OC to 800/250 compared to 800/800 does differently? I know that with 800/250 it allows the clock speed to be dramatically decreased, but when does this happen? Cause obviously it would be when you're using the phone with the screen on, but why would I want the speed to go down that low when I'm using it? I'm truly just confused, so I would enjoy some input on how and where this helps out?
From what i understand, i could be wrong but im pretty sure that when you are programs that dont use as high a frequency it goes down in mhz. For example if you are replying to a text less mhz is needed compared to using a program such as Google Navigation. If you have it at 800/800 it will stay at 800 mhz to send a text rather then going down in mhz using an un needed amount of mhz. But thats what i understand, i could be completly wrong
Did you clear the cache before testing? Still a useful test, but I was just curious. I almost think the OC'd would be even better on a fresh download, though maybe only a tiny bit.
No i didnt clear cache but i did however re-add each kernal before testing. Again i am going to make more tests but right now i dont have time. To busy watching the Superbowl
yeah, thanks man. I was wondering how an OC'd Droid compared to a stock Droid. Besides browser tests, what other tests can we see between stock vs OC'd.
I just recently rooted my Droid and installed the Bugless Beast on it. Made me a little nervous I might add cause I was just waiting for it to brick or something. Anyway, I had noticed my browser did seem a lot faster as well... along with everything else on the phone. Installing apps from the market is almost instant now, which is great.. it used to freeze up my phone every now n then when I added a new one.
That's a very skewed benchmark. If your going to use the same Wifi/Internet connectiong to test with, you need to time the results per phone, you can't do both at the same time. You are better off doing a comparison with 3g. I already know that overclocking, or having a faster processor in general will increase the load time of web pages. but this hardly identifies how much faster it will load.
Ya that does make sense, silly me. Once i get my friends Droid back i will redo the tests and add some more tests. Any other comparisons people want to see?
That's a very skewed benchmark. If your going to use the same Wifi/Internet connectiong to test with, you need to time the results per phone, you can't do both at the same time. You are better off doing a comparison with 3g. I already know that overclocking, or having a faster processor in general will increase the load time of web pages. but this hardly identifies how much faster it will load.
I dont see why doing them both at the same time would matter much -- especially if he is on 802.11g. It's not like one device gets exclusive use of the bandwidth on an internet connection. Each web page load is broken down into somewhere between several dozen to a couple hundred HTTP requests which are further broken down into however many more TCP packets.
Unless there is something inherent about Wi-Fi that I haven't heard about that causes bottle necking, there shouldn't be any problem running these thing simultaneously.
Secure your router with WPA2 and a long password and no one should be able to jack it.
But yeah, I guess scientifically speaking it is better to time them. Also even to do many tests over a period of several days and weeks and average them. But I think doing them at the same time is good enough for a YouTube test heh. But if you want to try the timing method, have at it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.