Hey guys I see there isn't a thread for posting your Android benchmark scores
so an attempt to determine what is the fastest rom so far, whether it is Hero/Ion/Rogers/Cyanogen/xRom builds. Or whether you have a Vogue/Kaiser/Polaris feel free to post your benchmark scores.
There is 3 apps I will post my score for:
*Benchmark PI*
16536
*Benchmark*
total graphics score: 113.96
total cpu score: 122.89
total memory score: 106.29
total file system: 23.40
*NeoCore*
22.0 FPS
Current Rom: cupcake 1.5 xrom, if you could post one of the three or even all three that would be great, lets find out what the fastest rom, settings are! =D
Also some tips for improving performance: http://androidbenchmark.com/tips.php
EDIT:
Also if anyone needs a the APKs for any of the three files let me know and I'll post them here.
Benchmark scores
Total graphics score 73.05589
Total CPU score 116.98557
Total memoty score: 103.41101
Total fs score: 4.948
At&T Tilt, Ion
dasilva333 said:
Hey guys I see there isn't a thread for posting your Android benchmark scores
so an attempt to determine what is the fastest rom so far, whether it is Hero/Ion/Rogers/Cyanogen/xRom builds. Or whether you have a Vogue/Kaiser/Polaris feel free to post your benchmark scores.
There is 3 apps I will post my score for:
*Benchmark PI*
16536
*Benchmark*
total graphics score: 113.96
total cpu score: 122.89
total memory score: 106.29
total file system: 23.40
*NeoCore*
22.0 FPS
Current Rom: cupcake 1.5 xrom, if you could post one of the three or even all three that would be great, lets find out what the fastest rom, settings are! =D
Also some tips for improving performance: http://androidbenchmark.com/tips.php
EDIT:
Also if anyone needs a the APKs for any of the three files let me know and I'll post them here.
Click to expand...
Click to collapse
there is not a benchmark thread because most chefs post the bench scores in the roms own thread, this is probably how it needs to be done for android as well.
Phone:Kaiser
Rom:custom cupcake based on cyanogen 4.0.4
Graphic 105.0,
Draw opacity bitmap: 48.0 MPixels per secDraw transparent bitmap: 16.1 MPixels per sec
CPU 128.0
WMIPS DP: 9.40WMIPS SP 9.54MFLOPS DP: 1.67MFLOPS SP: 2.27VAX MIPS DP: 6.46VAX MIPS DP: 6.25
Memory: 105.8
Copy memory: 96.1 Mb/sec
Filesystem: 45.0 (IGNORE, its XFS)
Create 1000 empty files: 14.9 secDelete 1000 empty files: 8.1 secWrite Speed 1M into file: 29.2 M/secRead Speed 1M from file: 61.3 M/sec
Running latest Ion build..
Graphics score: 52.471626
Draw opacity bitmap: 23.609756
Draw transparency bitmap: 8.483787 MPixels per sec
Total cpu score: 128.48817
MPWIPS DP: 9.48982
MWIPS SP: 9.806807
MFLOPS DP: 1.5866368
MFLOPS SP: 2.1741862
VAX MIPS SP: 6.500729
Total memory score: 103.6057
Copy memory score: 94.144226 mb/sec
Total file system score: 28.8196
Creating 1000 empty files: 4.159 sec
Deleting 1000 empty files: 2.707 sec
Write 1m in file:4.789272 M/sec
Read 1m from file: 53.19149 M/sec
@newbie16
wow XFS is signicantly faster than what i'm using, how do i change it? what do i have to do to use XFS?
dasilva333 said:
@newbie16
wow XFS is signicantly faster than what i'm using, how do i change it? what do i have to do to use XFS?
Click to expand...
Click to collapse
Sorry for not posting sooner but i'm not sure where the app is doing the test read/write, and until i find that out i don't know if its a useful result, because if its writing to the sdcard then its just the speed of the sdcard itself rather than xfs on the root and data partitions showing the performance boost. There is also umounting issues with xfs, which means it has to be cleaned on startup, Its log is causing lots of extra writes to the sdcard which will shorten its lifespan.
The current method of storing data in the data.img is fine, the only issue is that its in data.img in the first place. I'm frequently messing with my system.img, rootfs.img and data.img and it became time consuming and i had to run lots of commands, i used xfs so that i could just mount the root partition and edit it directly rather than editing the system-cupcake-03 folder, then using cramfs, then mounting the sdcard and copying over the system.img, i hated doing stuff this way, too many long commands.
Its very very very very annoying to have to create a new compressed image just to change a single line or use a new thing, so i wanted everything as a partition and thats how xfs as root and data came about.
[ /sdcard - rest ][ 300mb rootfs.img+system.img combined ][ 200mb data ][ 64mb swap ]
It might be faster with ext2 as root since it doesn't have a journal to write along with the written data but i've always used xfs on my server so i went with it
Newbie16 said:
Sorry for not posting sooner but i'm not sure where the app is doing the test read/write, and until i find that out i don't know if its a useful result, because if its writing to the sdcard then its just the speed of the sdcard itself rather than xfs on the root and data partitions showing the performance boost. There is also umounting issues with xfs, which means it has to be cleaned on startup, Its log is causing lots of extra writes to the sdcard which will shorten its lifespan.
The current method of storing data in the data.img is fine, the only issue is that its in data.img in the first place. I'm frequently messing with my system.img, rootfs.img and data.img and it became time consuming and i had to run lots of commands, i used xfs so that i could just mount the root partition and edit it directly rather than editing the system-cupcake-03 folder, then using cramfs, then mounting the sdcard and copying over the system.img, i hated doing stuff this way, too many long commands.
Its very very very very annoying to have to create a new compressed image just to change a single line or use a new thing, so i wanted everything as a partition and thats how xfs as root and data came about.
[ /sdcard - rest ][ 300mb rootfs.img+system.img combined ][ 200mb data ][ 64mb swap ]
It might be faster with ext2 as root since it doesn't have a journal to write along with the written data but i've always used xfs on my server so i went with it
Click to expand...
Click to collapse
I would also like to know how you set this up. It is very annoying having system and rootfs has RO, and I would imagine that it slows everything down considerably to have to compress and decompress all the time. You using a custom kernel to enable support?
Rhys'Droid said:
I would also like to know how you set this up. It is very annoying having system and rootfs has RO, and I would imagine that it slows everything down considerably to have to compress and decompress all the time. You using a custom kernel to enable support?
Click to expand...
Click to collapse
Then you can create a system.ext2 image and use it rather than the squashfs files. I think rootfs rw, just the system is ro.
Newbie16 said:
Then you can create a system.ext2 image and use it rather than the squashfs files. I think rootfs rw, just the system is ro.
Click to expand...
Click to collapse
If it is that simple, then why is everyone using *.img and *.sqsh files?
Rhys'Droid said:
If it is that simple, then why is everyone using *.img and *.sqsh files?
Click to expand...
Click to collapse
Well .ext2 images are much bigger and so it'll take much longer to upload those. Also there aren't any benchmarks of the performance difference between squashfs and .ext2 system images. But the issue is this, reading from the sdcard is slow, if its compressed you'll read less and uncompress it, and uncompression is pretty fast. It could mean that overall squashfs is faster than ext2, so without a benchmark i think squashfs is fine.
Newbie16 said:
Well .ext2 images are much bigger and so it'll take much longer to upload those. Also there aren't any benchmarks of the performance difference between squashfs and .ext2 system images. But the issue is this, reading from the sdcard is slow, if its compressed you'll read less and uncompress it, and uncompression is pretty fast. It could mean that overall squashfs is faster than ext2, so without a benchmark i think squashfs is fine.
Click to expand...
Click to collapse
hmm, that is a good point. Thanks for the explanation Newbie, I appreciate it!
I don't have any of those phones (Samsung Galaxy with the latest Firmware I7500XXII5) but just for the sake of comparison I am getting these results:
total graphics score: 118.98
total cpu score: 173.3
total memory score: 150.08
total file system: 33.1
htc hero
graphics : 107.88752
CPU : 164.5154
Memory : 89.65
FileSystem 36.80472
cross platform?
Hey now everybody.
So this guy I know got himself an HD2 maybe to spite me for buying an N1 and defecting from WinMo. He's talking a lot of trash, won't relent. Me too.
I'd like to engage him in a drag race and I think since we're talking about two very different platforms the simplest way to do this is just to pit how our respective operating systems handle the Snapdragon against each other by means of a Pi fight.
Maybe this isn't the best place to ask but off hand anyone know of a WM equivalent to something like BenchmarkPI or anything else there may be to standardize something about our phones related to math? Or perhaps there's a better way to make my point other than going back and forth about milliamp hours, weight, the virtues of hard buttons and Google versus Microsoft?
Thanks.
His latest attempt:
everyone knows you can get different speeds based on different browsers.
But the real question Doug, is what resolution is that nexus? Rumor has
it, it's ****ty and WVGA is a lie. Give me some black and white text man...show off that glorious screen that Goog sold to you...sucker
Click to expand...
Click to collapse
I Need BenchmarkPI APK & ...
I don't have access to market !
HTC Desire
BENCHMARKPI
3151
QUADRANT
519
Acer beTouch e400
Android 2.1 Original ROM rooted
BenchmarkPI: 10501
Benchmark:
graphics score : 215.08307
CPU : 211.64232
Memory : 186.24132
File system : 52.740353
kaiser eclair
Linpack: 1.448
Quadrand: 164
Gears: 30 fps
NeoCore: 19.4
kayser froyo
Linpack: 3.524
Quadrand: 338
Gears: 60 fps
NeoCore: 20.5
bye
i have default dhd AND i got from quadrant 1.15 a 1969 points.
minimal scree brightness. killed all apps.
Hi, like in topic - i've at last installed CM 9.0 FXP 130, but when i enter system info its showing only 360MB of ram, instead of 512 (SEX PRO got 512 as far as i know).
Why is that happening? Is this bug, or i don't know something?
I think you can allocate more RAM to your phone...
That's not bug/issue. 360 mb is user-available from 512
Guys I think everyone tested ICS 4.0.4[BETA6] ,well there are a lot of bugs yet to be solved (thanks for Team PECAN) to do such a good job .well incresing RAM memory is not a big issue i think you all know it but still iam posting this thread so that those who are using this ROM for daily use may not have any problem related to RAM uses .
So by this tutorial you can increase your ram memory
Requirements : 1) Swap it ram expander which i think u can download from 4shared.com - free file sharing and storage
2)Free memory in your SD card upto 2 gb ,well using swap it 2gb is the maximum limit for increasing ram (yeah u can expand your ram upto 2gb )
3)well as we know Rooting and all stuff so iam not writing about all these things .
Steps
1) First of all install Swap it ram expander
2)now open application and in my case i gave 512 mb for expansion u can give upto 2 gb as your wish
3)then tick Swap active and swapiness 90
4)u can tick the Autorun option too if u want to use it after reboot and all stuff (well who doesnt want that )
5)Download Link SWAPit RAM Expander v1.2.1.apk - 4shared.com - online file sharing and storage - download
well after these steps you will get notification that swap it is running !!!!
ENJOY
After performing these steps you will be able to get 72 mb of free ram in ICS which is good enough .
If any how i helped you Press Thanks !!!
Follow me on Twitter --->https://twitter.com/prachetas13
Hi guys, i would like to know any advice to improve the speed of my Xperia Play. Sometimes i got lags and when i play heavy games like Max Payne or GTA it reboots. My phone settings are:
Stock GB rom 2.3.4
Lupus v5 kernel
Xperia Mix theme
Root and unlocked bootloader
No frills CPU with min. frequency 245 MHz and max frequency 1,2 GHz
Stock micro SD card with a second ext2 partition of 2gb and 6gb of primar partition (4gb occupied and 2gb free)
Internal memory: 169mb free
Ram memory: 120mb free
Can anybody give me some advices to speed the phone, without changing rom or changing the stock rom with another GB rom liveview-compatible?
Thanks in advance!!!!
Your already running stock with a good kernel. Only other thing is overclock it more and maybe get a faster class 6 microsd. And change your i/o scheduler and cpu governor to a more performance based one.
Use a program like LBE Security Master to block programs from auto starting and clear ram before you start the game.
Sent from XDA app
dedefr89 said:
Hi guys, i would like to know any advice to improve the speed of my Xperia Play. Sometimes i got lags and when i play heavy games like Max Payne or GTA it reboots. My phone settings are:
Stock GB rom 2.3.4
Lupus v5 kernel
Xperia Mix theme
Root and unlocked bootloader
No frills CPU with min. frequency 245 MHz and max frequency 1,2 GHz
Stock micro SD card with a second ext2 partition of 2gb and 6gb of primar partition (4gb occupied and 2gb free)
Internal memory: 169mb free
Ram memory: 120mb free
Can anybody give me some advices to speed the phone, without changing rom or changing the stock rom with another GB rom liveview-compatible?
Thanks in advance!!!!
Click to expand...
Click to collapse
You can try to debloated application to get more memory free.
Upgrade to lupus v6 and enable zram ?
install seeder apk from this http://forum.xda-developers.com/showthread.php?t=1987032
Hello everybody
Currently my system partition has 2113 MB (it is default size), I have CM 13.0 installed with OpenGapps Pico package on it and only 988 MB is used so it's means that 1125 MB is free. I wonder if it is a good idea to resize this partition to e.g 1113 MB and shift all free 1000 MB to data partition? What's your opinion? Does anyone tried this?
best regards,
The question is "can it be done"? Usually resizing partitions is quite difficult and may brick your device.
hmmm... I didn't think about it like that. I thought that I can resize as I want but I have to keep big enough to put ROM on in.