Related
Does anyone feel like posting their benchmarks on the custom ROMs they are running? I know not every GTab will run the same but I would like to get a basic idea of what the hottest scores are. Thanks.
TNT Lite 4.3.x with stock kernel is ~40 fps (Nenamark) and ~2300 in Quadrant. On average.
There are definitely higher scores than that, with some of the other modded ROMs.
2200 with vegan 5.11 Benchmark Atuntu
Thank you guys for posting your benches. I had seen some one some where, posting that they get 60fps. Any one getting 60fps?
there is guide in dev forum where you can get up to 77fps, but the recomended is under 75.
You might mean the frame rate. The default is 50, but TNT Lite and gADAM up the frame rate to 60. At least one mod ups it to 77.
That's not really a benchmark, though - I assumed you meant something like Quadrant.
Im running caulkins rom and clemsyn's kernel #6. I'm averaging around 2400 on quadrant and 3000 on smartbench. The only thing faster on smartbench is overclocked xoom
It looks like most of the new ROMs run pretty fast. If i can get 2200-2500 in Quadrant I will be happy.
I get a little over 3000 qudrant
johnboyjr said:
I get a little over 3000 qudrant
Click to expand...
Click to collapse
what ROM/mods you are running?
i got several scores in the 2400s today and one personal best of 2518.
@johnboyjr
Are you bull****'n? 3000? i havent seen anyone say they are hitting the 3000 mark. I'd like to know what you're running too. Did you overclock? I dont think i want to overclock mine.
nsmartinez79 said:
Im running caulkins rom and clemsyn's kernel #6. I'm averaging around 2400 on quadrant and 3000 on smartbench. The only thing faster on smartbench is overclocked xoom
Click to expand...
Click to collapse
I have the same setup on my gtab... got 39.1 fps in nenamark, and 2399 in quadrant.
I just set my gtab up today so it doesn't have much on it yet.
There is a post in the development section by chengu that has a loopback fix that enhances read/write speeds on the internal SD. This makes the I/O part of quadrant way faster. I have posted on that thread vegan stock 10x average is 2500+. With the loopback fix its a 10x average of 3100 with peaks of 3333. So no its not BS but really how much do quadrant (or any other test) effect daily functionality.? It is great for bragging rights though, especially to xoomers.
Sent from my Chromatic Magic using XDA Premium App
Mantara said:
There is a post in the development section by chengu that has a loopback fix that enhances read/write speeds on the internal SD. This makes the I/O part of quadrant way faster. I have posted on that thread vegan stock 10x average is 2500+. With the loopback fix its a 10x average of 3100 with peaks of 3333. So no its not BS but really how much do quadrant (or any other test) effect daily functionality.? It is great for bragging rights though, especially to xoomers.
Sent from my Chromatic Magic using XDA Premium App
Click to expand...
Click to collapse
Mantara, do you still have the link for loopback fix? I could not find it .
Thanks a lot in advance.
njshkb said:
Mantara, do you still have the link for loopback fix? I could not find it .
Thanks a lot in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=902426
Fyi: restart your tab 5 or six times, I know I sounds weird but it takes that many to streamline it completely. Let it stabilize after boot and then power down, wait 20 sectonds and and power on. It wil take up to six minutes on first boot and get less each time.
It uses boot time to write changes.
Have fun ;-)
loopback fix like others have said
Is there any down fall to using the loop back fix? Heat issues or failure? Why isnt anyone implementing this into their ROMs?
No adverse side effects that I have noticed. Most people have noticed a slight increese in playing video from internal memory and web browsing cashed sights. Read the thread its full of good info.
Sent from my Chromatic Magic using XDA Premium App
Ok, so I just ran a linpack benchmark on my Aria and got the result of 8.903. I decided to save it since that was the highest I got. I went on the greencomputing website to see the best results for the Aria and the highest one was 32.62 mflops. I wonder if that is even possible on the Aria? If so, how do I get that rom/kernel which gets my that amount of speed. the guy had a dell streak rom and was clocked to 998.4 mHz. here is the link --- http://www.greenecomputing.com/apps/linpack/linpack-by-device/
just scroll down to HTC Aria/Liberty.
btw, I am running CM7 on my Aria.
Why do you want that much speed? 806 is fine. Speeds that high would toast the processor. And the phone would get hot so fast.
Sent from my Liberty using XDA App
I know
andrew.cambridge said:
Why do you want that much speed? 806 is fine. Speeds that high would toast the processor. And the phone would get hot so fast.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
I know but I'm just wondering how that guy even got his phone to fully boot up at that processor speed. Also, I am wondering if his phone exploded after that. Really, How is that speed even possible? Also, if you look at other results in that list, you will see that people got it to work on 864 which is impossible for the CM7 kernel. So that really makes you wonder how...
Moved to General, since it's not a development thread.
JazzyCarr0t said:
I know but I'm just wondering how that guy even got his phone to fully boot up at that processor speed. Also, I am wondering if his phone exploded after that. Really, How is that speed even possible? Also, if you look at other results in that list, you will see that people got it to work on 864 which is impossible for the CM7 kernel. So that really makes you wonder how...
Click to expand...
Click to collapse
Doesn't really make me wonder... Here's the deal, that guy (or girl) has a hobby. His hobby is seeing how high he can get linpack for android to run. To accomplish this he can go about it one of two ways.
Either he took apart his aria, overclocked the hell out of it, added additional cooling and custom built an optimized kernel for 1 purpose - running linpack for android while unstable. (it's not a phone anymore)
A more logical approach would be to run linpack in an emulator, and spoof linpack into thinking it's running on an aria.
Hope this helps clear up some of the confusion.
He must of got into that girls pants he was trying to impress by having a super overclocked aria
Sent from my Liberty using XDA App
Works every time. ^^
LOL gotcha
Sent from my Liberty using XDA App
wow..amazing what a dedicated person
I'm running stock, unlocked 198_7 with jokers 1.4Ghz kernel with various tweaks and what not. I'm also using the Myrt Undervolt app as well...my question is how low should I undervolt it? What are safe and suggested settings running my setup and in general? And does undervolting only save battery life or are there other benefits?
Sent from my MoPho
I would also like to know the answer to this question i only lowered mine a little bit havent tried going any lower but i am on 1.3 oc with jokers rom
Hello fellow mopho owner!
Undervolting is quite trivial! Each phone is different. There is no magic number for which you can UV or OC to and not have stability issues without proper testing.
A good way to start would be to pick a frequency, UV it in increments of -25, then proceed to run stability tests. If you encounter no issues, then decrease the voltage by -25 again and repeat the stability tests. You can do this until you encounter issues. If all is stable with this frequency, then proceed to UV another one. And repeat the same stability tests.
I recommend not to UV any higher than -50. You're just begging for a system failure. -50 should easily yield a noticably increase in battery life.
The benefit of UV only yields extended battery life at the cost of some said performance in various ways.
With having said that. Next time you have a question about an specific app, post in the Q&A section of the forums.
If you would like to share an app or theme, post it here. In the "Theme/App" section of the forum.
-cheers
Sent from my MB855 using XDA App
Custodian said:
Hello fellow mopho owner!
Undervolting is quite trivial! Each phone is different. There is no magic number for which you can UV or OC to and not have stability issues without proper testing.
A good way to start would be to pick a frequency, UV it in increments of -25, then proceed to run stability tests. If you encounter no issues, then decrease the voltage by -25 again and repeat the stability tests. You can do this until you encounter issues. If all is stable with this frequency, then proceed to UV another one. And repeat the same stability tests.
I recommend not to UV any higher than -50. You're just begging for a system failure. -50 should easily yield a noticably increase in battery life.
The benefit of UV only yields extended battery life at the cost of some said performance in various ways.
With having said that. Next time you have a question about an specific app, post in the Q&A section of the forums.
If you would like to share an app or theme, post it here. In the "Theme/App" section of the forum.
-cheers
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
This is the only forum it would let me post in...the new member restrictions are frustrating.
Lol. I felt the same way. All good
BigSketchySeaBeast said:
This is the only forum it would let me post in...the new member restrictions are frustrating.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
The tegra is picky and only likes booting at certain voltages. So many of the clocks could be uv'ed by up to 100. Loki manged 175 somehow... test till see causes issues but be thorough. Oh and my next kernels will require new values as im changing uv code to be more compatible with uv apps.
Custodian said:
Hello fellow mopho owner!
Undervolting is quite trivial! Each phone is different. There is no magic number for which you can UV or OC to and not have stability issues without proper testing.
A good way to start would be to pick a frequency, UV it in increments of -25, then proceed to run stability tests. If you encounter no issues, then decrease the voltage by -25 again and repeat the stability tests. You can do this until you encounter issues. If all is stable with this frequency, then proceed to UV another one. And repeat the same stability tests.
I recommend not to UV any higher than -50. You're just begging for a system failure. -50 should easily yield a noticably increase in battery life.
The benefit of UV only yields extended battery life at the cost of some said performance in various ways.
With having said that. Next time you have a question about an specific app, post in the Q&A section of the forums.
If you would like to share an app or theme, post it here. In the "Theme/App" section of the forum.
-cheers
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
1gHz and higher tend to float around -75 to -100 on average. Below 1Ghz it's anywhere between -250 and -150 on average. Attached you will find a list of all reported undervolts on the Atrix minus the ones that are the same undervolt for every clock speed. I've noticed that it's hard to fine tune the jump between the 700Mhz range and 1Ghz. Keeping the jump no greater than 100mV seems to be best.
I would kill to have profiles, under/over clocking and undervolting all in the same app and working. Maybe if enough of us get together we may be able to convince the app devs to put it in. I'd personally love to see it in setcpu or romtoolbox.
Maybe i should build a battery life kernel
Lokifish Marz said:
1gHz and higher tend to float around -75 to -100 on average. Below 1Ghz it's anywhere between -250 and -150 on average. Attached you will find a list of all reported undervolts on the Atrix minus the ones that are the same undervolt for every clock speed. I've noticed that it's hard to fine tune the jump between the 700Mhz range and 1Ghz. Keeping the jump no greater than 100mV seems to be best.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
jokersax11 said:
Maybe i should build a battery life kernel
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
That would be cool. Just a posting of all successful settings would be nice too.
One thing I've never understood are a bit more of the specific on how uv affects performance, from the comments it seems to have even more of an effect the more you oc (you don't seem to be able to uv as much when you oc).
Sent from my Photon 4G
MinceMan said:
That would be cool. Just a posting of all successful settings would be nice too.
One thing I've never understood are a bit more of the specific on how uv affects performance, from the comments it seems to have even more of an effect the more you oc (you don't seem to be able to uv as much when you oc).
Sent from my Photon 4G
Click to expand...
Click to collapse
My undervolt txt are all the successful settings for our sister phone the atrix. From what I've seen, the results are in line with both my mopho's. Overclock/undervolt is more an art than science. There are many factors that affect results such as cpu batch, ambient temps, mainboard variances and the list goes on. This is why pc overclockers will hunt for specific batch numbers when overclocking. The same goes for undervolting.
With regards to performance. There is a very fine line between efficient and inefficient when oc'ing and uv. I'll be honest, I've spent hours fine tuning an oc/uv to get the best performance at a given clock rate. I've used the following formula (benchmark score/uv= efficiency @ tested clock speed) and it has paid off in the past (the art vs science thing still applies though). I have, in some cases, found the device to be more efficient with a tuned undervolt than stock. However no to devices are the same, EVER.
Lokifish Marz said:
1gHz and higher tend to float around -75 to -100 on average. Below 1Ghz it's anywhere between -250 and -150 on average. Attached you will find a list of all reported undervolts on the Atrix minus the ones that are the same undervolt for every clock speed. I've noticed that it's hard to fine tune the jump between the 700Mhz range and 1Ghz. Keeping the jump no greater than 100mV seems to be best.
I would kill to have profiles, under/over clocking and undervolting all in the same app and working. Maybe if enough of us get together we may be able to convince the app devs to put it in. I'd personally love to see it in setcpu or romtoolbox.
Click to expand...
Click to collapse
Thanks man...all these posts have been very informative...this is the most info on undervolting I've seen in one place. You guys are awesome...I'll post some nudes soon in appreciation....HA!..just kidding...unless you ask nicely...then it'll be $5.
Sent from my MB855 using xda premium
Thanks Loki!
Sent from my Photon 4G
ive tried every rom/kernal combination and with each i get lock ups when doing intensive cpu work such as a game or benchmark overclocked to 1.6 any ideas? Thanks
Just means your processor was built a little weak. Its only built to run at 1.2ghz so anything above that is pushing it hard... some phones can be oc'd that much, some can't. Just take it down to 1.4. I can't even get mine to 1.4 so he thankful
Sent from my AT&T cellular device.
What voltage do you have it at? Try raising it 25mV at a time stressing you cpu at each step until you're stable. That is if you are determined to run 1.6 and i would not push more than +100mV personally.
joeyzadoe said:
ive tried every rom/kernal combination and with each i get lock ups when doing intensive cpu work such as a game or benchmark overclocked to 1.6 any ideas? Thanks
Click to expand...
Click to collapse
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Entropy512 said:
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Click to expand...
Click to collapse
Wow... You got real issues man..The OP is just looking for some tips from others that have succeeded in getting their phones to 1.6.. You need some help buddy...
If youve nothing nice to say..
But then I guess youd never speak would you?
/end rant
Sent from my SAMSUNG-SGH-I777 using xda premium
Stevenrogers_420 said:
If youve nothing nice to say..
Click to expand...
Click to collapse
Hope you heed your own advice.
Stevenrogers_420 said:
Wow... You got real issues man..The OP is just looking for some tips from others that have succeeded in getting their phones to 1.6.. You need some help buddy...
If youve nothing nice to say..
But then I guess youd never speak would you?
/end rant
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I do not think entropy is the one who has issues...
This has been discussed in 10 different threads already and in great detail. If the OP did as much as search he would of have found the answer himself. That is why they call it research
the only question left is...... You mad bro?
Keep all voltages stock, then use voltage congrol and click on 1400 and increment the slider+ 25, then do the same for 1600. This is what i had to do to get my phone stable at 1.6 Some phones may need EXTRA voltage and others need less. It takes some testing to get your particular phone stable at anything over 1.2Ghz. I only did it to see if I saw any gains. Actually for me and my phone I found as far as MY SETUP and testing many different benchmark style apps at 1.4Ghz i got better benchmarks than i did at 1.6Ghz. Now everyones phones will act sligbtly different so your mileage may vary.
Sent From My KickAss ATT SGS2 SPORTING CM7
At 1.6 ghz... your phone will be discharging your battery ON your charger... I personally wouldn't recommend doing it as it gets the phone really hot, and causes the chip lots of stress due to high heat. Personally if you need more performance (this phones pretty damn fast anyways) go to 1.4ghz.
Most of our phones can be overclocked to 1.4 and some can go to 1.6 but not all. If you change the voltages and it still craps out, then take it down a notch to 1.4 and see how that works for you.
Entropy512 said:
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Click to expand...
Click to collapse
Now now. Since when do we encourage keeping things stock.
My point is - if it were guaranteed to hit 1.6, it would be sold as 1.6.
Being able to hit 1.6 is luck of the draw, pure and simple.
There's a reason:
1) OC is not default on my kernel
2) I held off on providing OC support for a while here, and NEVER released it on Infuse (users weren't mature enough to handle it over there)
3) I have a warning in GIANT RED LETTERS not to complain about OC stability issues on my kernel thread.
Entropy512 said:
My point is - if it were guaranteed to hit 1.6, it would be sold as 1.6.
Being able to hit 1.6 is luck of the draw, pure and simple.
There's a reason:
1) OC is not default on my kernel
2) I held off on providing OC support for a while here, and NEVER released it on Infuse (users weren't mature enough to handle it over there)
3) I have a warning in GIANT RED LETTERS not to complain about OC stability issues on my kernel thread.
Click to expand...
Click to collapse
This is all true... but the OP was simply asking a question now lets all play nice.
We should have an OC that allows n00bs to melt their cpu.... 2.5ghz ftw
No no no.... We have too many "I tried to load the ICS in the I9100 forums, and I bricked my phone, please help!" threads. we don't need "I OC'ed my phone to 8ghz and melted my cpu" threads too
Tegrak allows you to go past 1.6. I thought these CPU were locked @ 1.6 but i had to up my voltage at 1.7 and i got a small bump in my benches though i probably did run my test enough to confirm the bump. At so.e point, when i get some time ill beat on my CPU some more
penguinlogik said:
At 1.6 ghz... your phone will be discharging your battery ON your charger... I personally wouldn't recommend doing it as it gets the phone really hot, and causes the chip lots of stress due to high heat. Personally if you need more performance (this phones pretty damn fast anyways) go to 1.4ghz.
Click to expand...
Click to collapse
I ran my phone at 1.6 for days just to see performance. No UV at all.. battery certainly drained faster, but not while charging. It charged just fine.. and stayed cool even when stressing. Like many have stated, all CPU's are slightly different .. just cause yours melts at 1.6 and wont charge doesn't mean this will happen for anyone trying to run 1.6GHz.
sent from my SGSII... suckas
Try bumpin' up the voltage 1-2 notches.
Just to add to the stats...
I've been able to run @ 1.4 with the same voltage as 1.2, but my phone will freeze once in a while when running apps like camera or navigation. Had to bump the voltage up slightly to get it stable, though I will likely just run 1.2.
I cannot run at 1.6.
fallingreason said:
Just to add to the stats...
I've been able to run @ 1.4 with the same voltage as 1.2, but my phone will freeze once in a while when running apps like camera or navigation. Had to bump the voltage up slightly to get it stable, though I will likely just run 1.2.
I cannot run at 1.6.
Click to expand...
Click to collapse
Try changing or updating your kernel. Im the OP and had the same problems. with the new siyah kernel at 1.6 even if i try i cant make it lock up or freeze.
Your processor was made from a different silicon wafer than other people's phones and was rated for 1.2ghz.
Since each wafer is different, some processors take voltage better than others as well as speed. It happens.
Sent from my GT-I9100 using xda premium
Hi, I was wondering how people get such huge benchamarks on antutu benchmark for example then it hit me that that's inpossible with stock firmware D:
Does anyone know what rom/kernal they used to get 15000 on antutu when my phone get's 6300 QQ
A few options and their links would be GREATLY appreciated. <3
Also so far i saw 2 roms with 4.1.1-4.1.2 interface one was Cyanogen 10 i think and the other was one featured on the XDA page front BUT it looked like it had a problem, it had those 3 buttons on the bottom which S2 does not need since it has physical buttons. <.<
Certain kernels allow you to set your phones CPU/GPU processor to overclock...your standard maximum setting is 1200mhz...whereas certain kernels will allow you to reach a CPU/GPU speed of up to 1600mhz, resulting in in possible a higher scoring benchmark(antutu or quadrant). I wouldn't advise you to try this though until you've researched it a bit more and understand what you are doing...as you're more likely to make your phone performance not so good at all..you could even brick your device. The on screen buttons you see at pictures of cm10(4.1.1/4.1.2 ROMs) is a navbar which is optional to use.it is originally a part of the os on the galaxy nexus.finally....you're on the wrong thread.... this should be in q&a.
Sent from my GT-I9100 using xda premium
naokilla said:
Certain kernels allow you to set your phones CPU/GPU processor to overclock...your standard maximum setting is 1200mhz...whereas certain kernels will allow you to reach a CPU/GPU speed of up to 1600mhz, resulting in in possible a higher scoring benchmark(antutu or quadrant). I wouldn't advise you to try this though until you've researched it a bit more and understand what you are doing...as you're more likely to make your phone performance not so good at all..you could even brick your device. The on screen buttons you see at pictures of cm10(4.1.1/4.1.2 ROMs) is a navbar which is optional to use.it is originally a part of the os on the galaxy nexus.finally....you're on the wrong thread.... this should be in q&a.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I've had 2 other android phones that i rooted and put roms on successfully alone, and overclocked.
I found some kernal called "siyah" it's a stable.
I decided i'm gonna do a backup, then format-wipe caches and **** and then i'll put a few roms i want to try out
If i don't like them i'll restore and i'll put siyah kernal and overclock till i can bake eggs on my phone.