Bionic Chronic
Android Enthusiast
We have a benchmark thread already
He does make alot of threads..
Swyped from my LG-LG855 using Tapatalk 2 Beta-5
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We have a benchmark thread already
Sorry if you took what I had to say the wrong way.. I am not asking for you to stop posting here.. I am glad we have a new member here on the Marquee Section! As I had said welcome to the Marquee Forums! I am just asking to look around and see if there is not a thread made already for your topic. Just makes it more difficult for others to find information in multiple areas. Hope I could clarify what I was saying.Ok, fine, have it merged then... :/
And I guess if I post a lot of threads then I'll just stop posting, guess it'll stop people from complaining and make them happy, take care...
Score: 3103
1300 MHz
(how can I post a pic from my pc?)
Check these out. Take a good look at the sd card write speed. Just to make sure it didn't screw up the first time I ran it again. This phone was not hooked to the pc. I have no idea why the write speeds are so high. Either way these are some kickass scores!




Ok..... I had to go ahead and turn it up since you did.
I wonder what's causing the write speeds to be so high? The highest scores AnTuTu will give is a 150 looks like. I also notice that after I loaded some more stuff on my sd card and loaded my phone down with apps that the write speed dropped. Still high but not near as high as it was. Either way I'm happier than a pig in mud!![]()
I fear I will not be able to get that high because my database i/o doesn't usually pass 475 :[ My phone doesn't lag or freeze at 1400mhz
Damn you wetbiker! lol i wanted to have the highest scoring benchmarkI fear I will not be able to get that high because my database i/o doesn't usually pass 475 :[ My phone doesn't lag or freeze at 1400mhz
![]()




........



.......



.
This is CTmod 3.6 w/ the Hyperkernel.

![]()
I think it may have bugged out during the test.....![]()