Related
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.
Modifying your nand adress space is okay, but that means that you have to modify your recovery along with the new rom each time you want to flash a new one.
What I propose is a new, flexibile approach (mainly for devs).
This is just a placeholder atm, but once I get some free time, I'll write about making compressed partitions (mainly static data) using squashfs (this has been done to a certain extent in the past for /system/lib/modules), but adding a bit of flexibility with unionfs/aufs.
The advantages are numerous, as are the uses.
For example: no need for complex apps2sd scripts!
Just mount your unionfs in /data and mount-bind that to another folder on the SD partition of your choice, and voila, apps2sd.
;]
This is of course synonymous to modifying the initrd, but a few lines of really simple script and it's done.
I have successfully tested that with /system, and have to further test with /data
I also have to test unionfs / aufs and make a choice. The ideal one without hesitation is aufs, which has practically superseeded unionfs, but there are a few stability issues involved in the 2.6.29 patches.
There are a few knowledgeable (real) devs around (dunno about any in the Hero forum though), so they probably know what I'm writing about.
You know who you are, so just drop in a post in this thread in case you you would have some ideas regarding the implementation.
n.b. I might have to rewrite that post. It's 01:40 and I'm really tired after my training and work.
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
>edit 201008181214<
I've successfully patched the tattoo 3G/Slide kernel to build a healthy Hero kernel with aufs.
It kindda hangs in the beginning, but runs just fine afterwards.
Prolly due to my OC settings.
>leak<
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
dkelley said:
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
Click to expand...
Click to collapse
I am puzzled as well (audio issue).
You might've noticed that I'm no longer as active in the Hero forum.
I'm done with mdpi devices.
;]
In any case:
I have been working these past few days on optimising the kernel (I have based my work on the tattoo kernel) and aufs is working atm.
adwinp said:
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
Click to expand...
Click to collapse
you should use ninpo's repo, most uptodate kernel sources with a lot of fixes/patches included (http://github.com/Ninpo/kernel-hero/). aufs compilation worked at the first try.
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
Click to expand...
Click to collapse
ninpo works with elemag on porting 2.6.34, they already made a lot in porting the board files.
btw nice idea with overlaying the file system, I think a lot of nand protected device use that already? (Desire, Wildfire..) http://forum.xda-developers.com/showthread.php?t=748025
unfortunately I have nearly no spare time to play around, but I'm very interested to see how the compressed squashfs affects cpu load and thus the overall phone performance.
found an old but still interesting thread, so even cyanogen experimented with it, maybe there are unresolved issues?
http://forum.xda-developers.com/showthread.php?t=523662
http://groups.google.com/group/andr...36603d429a/646a017892783e2b?#646a017892783e2b
As a matter of fact, Elemag PM'd me about his work.
To be frank, I am only playing around with this out of boredom, till I buy myself a hdpi device (I am waiting for the Glacier, hopefully)
;]
Thx for the links.
I can see that I was not the only one. lol
Despite a totally different approach, Maxisma's posts about a bigger data partition got me thinking, and ultimately reminded me of some work I did in the past with linux livecd's, which gave me the idea to try it on android.
To answer your question: decompressing squashfs is very fast, with little additional load/overhead (although, running a lot of running apps/widgets on our poor 528MHz/729MHz cpu in addition to a compressed system is generally a bad
idea)
I have another idea (from my linux administrating experience as well ;]) I would like to implement, but that would only work on newer devices, which have a lot of RAM.
My idea is to modify the init.rc in order to copy over the SYSTEM: partition ENTIRELY into RAM (essentially create a tmpfs mount point), do a switch_root, and let android take it from there.
This would of course also mean redefining the ANDROID_ROOT env variable to point to the new location.
A further modification would be to mount the WHOLE /system and /data into RAM (provided it fits and leaves enough for runtimes), and THEN further mount aufs in order to write to disk - or write to tmps, but, in the case of aufs, no further work is required, but in the case of tmpfs, you just have to #find all newer files than $uptime (taken from uptime, obviously), and recompress it to the original compressed fs.
That WORKS on a few linux systems I tried.
whew. a lot of ideas, but no device to test on.
;]
This is my first post in this forum and I hope this works as well for you as it has for me.
First and foremost: I am not a developer; just an advanced user that has spent many many many hours in these forums and has used the tools I have found to make my deice the best it can possibly be. I TAKE NO RESPONSIBILITY FOR ANY DAMAGE DONE TO YOUR DEVICE BY USING THE SCRIPTS PROVIDED. I did not create these scripts and for the life of me cannot remember which forum or developer(s) I got them from; I am sorry that I cannot give the proper credit.
I have been using this DATA2SD method for about a month with several different ROMs and have found it to be very fast and very stable (only one crash in 2 weeks using Hyperdroid 2.1, not sure what caused it).
I am currently using the latest Hyperdroid CM7 (big Thanx to Pongster for a fantastic build!), albeit a version cooked using dsixda's kitchen to include my favorite apps and a few other changes. I have also used these scripts with the AOSP MIUI 1.6.24 and up ROMs (my NAND configuration has not changed between the two [MIUI and CM7], not sure if the large cache size helps or not). I have only used this process successfully with these two builds and cannot attest to the compatibility or stability if used with any other firmware.
I am using a 200MB system partition with 45mb for cache with Clockwork Recovery 4 (partitioned and updated using the HD2 toolkit). My SD card is using EXT3 set at 1024MB. Once again, this is the only configuration I have used successfully.
**BUG**
The only bug I have noticed so far is that whenever the device is rebooted CM7's Theme Manager reverts to the default (system) theme.
Instructions are included in the download. The scores shown were attained running Hyperdroid CM7 with the governor set to performance at 1152mhz (the highest stable overclock speed for my device using an 2.3.4 based ROM). The scores are provided by Quadrant Advanced (of course) and Device Mark.
nice but why is it only for tmous ?
i have one but i wonder why an tmous version is neccessary
errmm and i think u should post some Screens of the homescreen
This should work for 512 as well, i have only been able to test on us version... will post some screen shots
Sent from my HD2
Posted another in the screen shots forum
Sent from my HD2
so can some one tell me how can i try it on a eu version? I mean do i just flash it in the cwm recovery or something else?
beston94 said:
so can some one tell me how can i try it on a eu version? I mean do i just flash it in the cwm recovery or something else?
Click to expand...
Click to collapse
It should work as well as it works on the tmous version because it doesn't use that much place that requires a tmous. You can't to anything wrong
If u try it I would say please report back so that the dev know if it works there too
Sent from my HD2 using XDA Premium App
I included instructions with the download; these are scripts that are flashable visa clockwork recovery and should work with your device. Compatibility issues usually come into to play with the ROM that is used; it must support scripts (I think the proper term is init.d scripts). Usually Rom s that already have Apps2sd support this but i have only used this process successfully ( stable) with the AOSP MIUI and Hyperdroid ROMs
Sent from my HD2
cinnesere said:
This is my first post in this forum and I hope this works as well for you as it has for me.
First and foremost: I am not a developer; just an advanced user that has spent many many many hours in these forums and has used the tools I have found to make my deice the best it can possibly be. I TAKE NO RESPONSIBILITY FOR ANY DAMAGE DONE TO YOUR DEVICE BY USING THE SCRIPTS PROVIDED. I did not create these scripts and for the life of me cannot remember which forum or developer(s) I got them from; I am sorry that I cannot give the proper credit.
I have been using this DATA2SD method for about a month with several different ROMs and have found it to be very fast and very stable (only one crash in 2 weeks using Hyperdroid 2.1, not sure what caused it).
I am currently using the latest Hyperdroid CM7 (big Thanx to Pongster for a fantastic build!), albeit a version cooked using dsixda's kitchen to include my favorite apps and a few other changes. I have also used these scripts with the AOSP MIUI 1.6.24 and up ROMs (my NAND configuration has not changed between the two [MIUI and CM7], not sure if the large cache size helps or not). I have only used this process successfully with these two builds and cannot attest to the compatibility or stability if used with any other firmware.
I am using a 200MB system partition with 45mb for cache with Clockwork Recovery 4 (partitioned and updated using the HD2 toolkit). My SD card is using EXT3 set at 1024MB. Once again, this is the only configuration I have used successfully.
**BUG**
The only bug I have noticed so far is that whenever the device is rebooted http://forum.xda-developers.com/showthread.php?t=852219&page=37CM7's Theme Manager reverts to the default (system) theme.
Instructions are included in the download. The scores shown were attained running Hyperdroid CM7 with the governor set to performance at 1152mhz (the highest stable overclock speed for my device using an 2.3.4 based ROM). The scores are provided by Quadrant Advanced (of course) and Device Mark.
Click to expand...
Click to collapse
Is the same as:
http://forum.xda-developers.com/showthread.php?t=527636
or
http://forum.xda-developers.com/showthread.php?t=852219&page=37
or is another approach?
I don't believe so; i believe the process outlined in that post (i could be wrong) uses a data image similar to the one Rafpigna uses in Rafdroid or in Acura MIUI which is stored on the root of the sd card. This script uses ext 3 for the storage. I could be wrong, this is my first time seeing that post.
Sent from my HD2
Today's run
Sent from my HD2
i tryed with EU HD2 and no problem
one question: it's possible to try to OC tytung kernel to 1.5ghz? (like in rafpigna 1.9)
pirlano said:
i tryed with EU HD2 and no problem
one question: it's possible to try to OC tytung kernel to 1.5ghz? (like in rafpigna 1.9)
Click to expand...
Click to collapse
It should work :$
But make a nandroid backup before flashing the kernel so you can revert to the "stock" rom if booting fails after flashing
Sent from my HD2 using XDA Premium App
pirlano said:
i tryed with EU HD2 and no problem
one question: it's possible to try to OC tytung kernel to 1.5ghz? (like in rafpigna 1.9)
Click to expand...
Click to collapse
I have not been able to use Raf's kernel with any 2.3.4 Rom at 1.5 ghz with or without these scripts. I haven't seen anyone we in the forums mention this so maybe it is my device... if anyone has a suggestion I would live to see it, i really like Raf's kernel, sips the battery...tytungs kernel maxes at 1190, which is also unstable on my device with 2.3.4 Roms
Sent from my HD2
cinnesere said:
I have not been able to use Raf's kernel with any 2.3.4 Rom at 1.5 ghz with or without these scripts. I haven't seen anyone we in the forums mention this so maybe it is my device... if anyone has a suggestion I would live to see it, i really like Raf's kernel, sips the battery...tytungs kernel maxes at 1190, which is also unstable on my device with 2.3.4 Roms
Sent from my HD2
Click to expand...
Click to collapse
tytung is stable for me and 1190mhz on tytung is fast as 1536mhz on rafpigna one, so i was thinking that 1536mhz with tytung would be awesome...
btw with hyperdroid cm7 v2.1 with tytung at 1190mhz and you trick i'm only able to reach """only""" 2500 point in quadrant, and 3d graphic is corrupted (some 3d bench are black). it's possible to update graphic driver with an update.zip in recovery?
what rom are you using to reach 3000 points?
pirlano said:
tytung is stable for me and 1190mhz on tytung is fast as 1536mhz on rafpigna one, so i was thinking that 1536mhz with tytung would be awesome...
btw with hyperdroid cm7 v2.1 with tytung at 1190mhz and you trick i'm only able to reach """only""" 2500 point in quadrant, and 3d graphic is corrupted (some 3d bench are black). it's possible to update graphic driver with an update.zip in recovery?
what rom are you using to reach 3000 points?
Click to expand...
Click to collapse
I am running Hyperdroid cm7 2.1 at 1152MHz ( the highest stake clock speed for my device). Have you tried setting the governor to performance in cyanogenmod settings? Chainfire 3d lets you update the driver of the device but this program is meant to make the rendering of complex 3d graphics easier for older devices (at least that's my understanding). I am using this program but I did not apply the effects to quadrant ( or any other app). The high scores database read/ write speed.
Sent from my HD2
cinnesere said:
I am running Hyperdroid cm7 2.1 at 1152MHz ( the highest stake clock speed for my device). Have you tried setting the governor to performance in cyanogenmod settings? Chainfire 3d lets you update the driver of the device but this program is meant to make the rendering of complex 3d graphics easier for older devices (at least that's my understanding). I am using this program but I did not apply the effects to quadrant ( or any other app). The high scores database read/ write speed.
Sent from my HD2
Click to expand...
Click to collapse
yes when i play games or do some bench, i set performance and min and max at 1190mhz it's possible to go higher than 1190mhz with tytung r10? (limit is written on the kernel or somewhere in system params?)
i tryed to install chainfire drivers but i still got black screen on 3d tests
3d tests on newer gb cm7 are working ok, so i'm asking if there is an update.zip flashable in recovery to update driver in this pongster's hyperdroid cm7 rom
pirlano said:
yes when i play games or do some bench, i set performance and min and max at 1190mhz it's possible to go higher than 1190mhz with tytung r10? (limit is written on the kernel or somewhere in system params?)
i tryed to install chainfire drivers but i still got black screen on 3d tests
3d tests on newer gb cm7 are working ok, so i'm asking if there is an update.zip flashable in recovery to update driver in this pongster's hyperdroid cm7 rom
Click to expand...
Click to collapse
I tried once to substitute Raf's kernel for tytungs using dsixda's kitchen with a gingerbread Rom and it wouldn't boot. I don't know enough about kernels to change the processor values and I don't know if a flashable update for the drivers for this Rom.
Sent from my HD2
cinnesere said:
Instructions are included in the download. The scores shown were attained running Hyperdroid CM7 with the governor set to performance at 1152mhz (the highest stable overclock speed for my device using an 2.3.4 based ROM). The scores are provided by Quadrant Advanced (of course) and Device Mark.
Click to expand...
Click to collapse
Looks like a nice script! Questions:
1) Is it necessary to use the same partition sizes as you for it to work?
2) Once Data2SD is implemented, can you restore data partition to SD using advanced restore in CWM?
So does this script really make the rom faster and more stable than it already is? Like for example dorimaxes rom?
Sent from my HTC HD2 using XDA Premium App
lukedunk said:
Looks like a nice script! Questions:
1) Is it necessary to use the same partition sizes as you for it to work?
2) Once Data2SD is implemented, can you restore data partition to SD using advanced restore in CWM?
Click to expand...
Click to collapse
Thank you...
1) The short answer is; I don't know. I have used this partition setup with several ROMs and just decided to try it with the scripts. I am using this ad my daily driver and have been for about a month with only one crash, so Idon't want to start experimenting with the setup just incase ( Hyperdroid is a very stable Rom to begin with).
2) The script itself is not apart of the backup so you would have to follow the installation procedure after the restore.
Sent from my HD2
i want to create a init.d script with some tweaks but lack the knowhow.
I will post the script in .txt that i have made. I hope some tweakpro or dev could enlighten me on whats right and wrong in the script.
as said in the title:
rom: cm7.2, kalis- app2sd script
monutsd script edited to mount as ext4
Thanks in advance
Why would you NOT want journalling?
from what i understand. better scores in benchmark considering i/o. its a speedtweak
jimmkind said:
from what i understand. better scores in benchmark considering i/o. its a speedtweak
Click to expand...
Click to collapse
Those IO results are not real anyway. ...And thats only for data2sd / data2ext. Increased IO score when /data partition is moved to sd-ext is a bi-product, but it doesnt make the device any faster. Its just due to read / cache.
Benchmark means nothing except showing off. Benchmarks on my rom are not the fastest, yet in real life usage, its very fast.
Yes of course. I know the general opinion of these tweaks is that it is just for showoff, and that it dosent really show for real.
Are you familiar with other speedtweaks that actuallly does improve performnace?
And still. Are you familiar with the formatting and rules to the init.d scripts? I really want to apply the tweaks posted in the attachment in the first post.
Help me please.
.
Not those particular tweaks no,
Have you heard of V6 supercharger? Maybe you could look into that script?
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Monster212 said:
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Click to expand...
Click to collapse
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
SkOrPn said:
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
Click to expand...
Click to collapse
thank you very much for the reply.. i learned something new...
Monster212 said:
thank you very much for the reply.. i learned something new...
Click to expand...
Click to collapse
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
SkOrPn said:
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
Click to expand...
Click to collapse
Thank you for the info, I will now be looking for a good rom or kernal.....
Sent from my SM-T700 using Tapatalk
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
ashyx said:
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
Click to expand...
Click to collapse
thank you i will install it now and see how it goes...
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
SkOrPn said:
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
ashyx said:
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
Click to expand...
Click to collapse
Yeah agreed, EXT4 is slightly faster at reading, but just by a hair on my N7. However, on partitions that have write permissions, it can "sometimes" be three times faster at random writes. I been using F2FS since feb 2014 "religiously" on my Nexus 7 (and wont run a non-f2fs setup on it), so I am very well versed in its use. Legolas was the first one to bring it to custom Android (I know because I was one of his support techs helping users convert to it, until he disappeared that is lol. Then I started helping USBhost with CarbonROM), and was the first to release a F2FS app in the play store. He was also the first, and only individual, to have a Conversion app to convert your ROM to f2fs, which gave new life to my N7 and any ROM I tried back in 2014 (it did not support 5.0 though). Without F2FS, sadly my Nexus 7 is almost worthless.
If only I can find the many screenshot test results we've done with F2FS, it would come in handy here too. On the N7 its a night and day difference, but here this device is already plenty fast. Id love to see some insane results though.... If only Jaegeuk would develop a Windows driver already. I would like to use it for my Linux box, Windows and Android tbh, and format the sdcards with it, and maybe even USB storage drives to try and pick up on the write speeds a bit. Well see I guess...
My SkyHigh TW LL 5.0.2 kernels support both EXT4 and F2FS for DATA and CACHE partitions.
Note: You need to have supported base firmware for successful flash.
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
deadman96385 said:
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
Click to expand...
Click to collapse
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
UpInTheAir said:
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
Click to expand...
Click to collapse
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
deadman96385 said:
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
Click to expand...
Click to collapse
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
UpInTheAir said:
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
Click to expand...
Click to collapse
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
deadman96385 said:
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
Click to expand...
Click to collapse
It's the same (similar) ramdisk fstab changes for Samsung based kernel as well, not just source. Edit: As I said, all you need to do to actual "ROM" is just format the relevant partitions.