Related
hi, i was just wondering if someone can tell me the benefit of cm7 over a2sd please, im S-OFF so no problems changing, but just wanted to know the differences. and also which is better, insertcoin or rcmix??
cheers.
I think I read a possible speed increase with cm7
Different system partition sizes..
Sent from my HTC Desire using XDA Premium App
ok so what the big deal about the system partition being bigger.. what does that mean in real world case?
In the a2sd apps and dalvik are on sd because there is no much space
In cm7, apps are on SD ,but dalvik cache is on internal.
Dalvik is the virtual machine that runs on android to provide that java environment(behind that is Linux). Also internal memory is faster on read/write even from a class 10 SD card. That way we take advantage of the internals speed , which makes the Rom a lot faster. Also since the ext partition is used only for apps, there is more space available for more apps than a2sd
Sent from my HTC Desire
dexter93 said:
(...)
In cm7, apps are on SD ,but dalvik cache is on internal.
(...)
Sent from my HTC Desire
Click to expand...
Click to collapse
Cm7 does not officially support a2sd. Even if you have an ext partition on sd card, you also have to run a special script or program(strange issues occur here sometimes). This is why it's recommened to have cm7 hboot when you run cm7 rom, because with cm7 hboot you do not need a2sd because of the big /data partition.
Furthermore, as far as i know the difference between a2sd and a2sd+ is the following:
a2sd: only apps will be moved to sd card
a2sd+: apps and cache will be moved to sd card.
dexter93 said:
In the a2sd apps and dalvik are on sd because there is no much space
In cm7, apps are on SD ,but dalvik cache is on internal.
Dalvik is the virtual machine that runs on android to provide that java environment(behind that is Linux). Also internal memory is faster on read/write even from a class 10 SD card. That way we take advantage of the internals speed , which makes the Rom a lot faster. Also since the ext partition is used only for apps, there is more space available for more apps than a2sd
Sent from my HTC Desire
Click to expand...
Click to collapse
So. if we're in cm7, it would defeat the purpose if we use mcr scripts to move dalvik cache to sd? It's just that I noticed an increase in internal storage space. Is that not a good thing?
MatDrOiD said:
Cm7 does not officially support a2sd. Even if you have an ext partition on sd card, you also have to run a special script or program(strange issues occur here sometimes). This is why it's recommened to have cm7 hboot when you run cm7 rom, because with cm7 hboot you do not need a2sd because of the big /data partition.
Furthermore, as far as i know the difference between a2sd and a2sd+ is the following:
a2sd: only apps will be moved to sd card
a2sd+: apps and cache will be moved to sd card.
Click to expand...
Click to collapse
that is true indeed, but insertcoin gb cm7 used a2sd while the stock hboot uses a2sd+. I was talking specifically for these roms , not for cm7, but the cm7 hboot gingersense roms
Hi all.
I'd like to understand better the "alternate HBOOTSs and internal partitions" thing.
I've tried to look around but the information seems to be quite scattered.
What I'd like to understand is:
1. Pros and cons in general
2. Whether and how should i change my SD partitioning
Thanks.
with default hboot your system partition is 250mb.
some roms like oxygen or cm7 dont need 250mb. so installing them on stock hboot is a waste, lots of MBs arent used neither by ROM nor by you since we cant install apps in system.
so thats why there are custom hboots, so you use a CM7 hboot with CM7 rom, system is big enough to hold the ROM and you get bigger /data which is where apps go.
EXT is needed if it is writtien in the ROM thread.
there are also Sense 2.1/3.0 roms that run on data++ or cm7 hboots AND ext.
so for example insertcoin CM7 - 130mb is available on nand, however /system of the ROM is bigger. so essetntial parts go into nand, rest is stored on sd-ext. system is still super-fast, as apps run from NAND, not from ext. files present on ext are not essential for the system speed.
so generally
pros: super fast roms since apps run from NAND, lots of space for apps
cons: if you are a retard you can brick your phone if you flash something wrong
dzumagos said:
with default hboot your system partition is 250mb.
some roms like oxygen or cm7 dont need 250mb. so installing them on stock hboot is a waste, lots of MBs arent used neither by ROM nor by you since we cant install apps in system.
so thats why there are custom hboots, so you use a CM7 hboot with CM7 rom, system is big enough to hold the ROM and you get bigger /data which is where apps go.
EXT is needed if it is writtien in the ROM thread.
there are also Sense 2.1/3.0 roms that run on data++ or cm7 hboots AND ext.
so for example insertcoin CM7 - 130mb is available on nand, however /system of the ROM is bigger. so essetntial parts go into nand, rest is stored on sd-ext. system is still super-fast, as apps run from NAND, not from ext. files present on ext are not essential for the system speed.
so generally
pros: super fast roms since apps run from NAND, lots of space for apps
cons: if you are a retard you can brick your phone if you flash something wrong
Click to expand...
Click to collapse
+1
Sent from Oxygen
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Uqbar said:
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Click to expand...
Click to collapse
A2SD/A2SD+ works on this way:
Usually all apps will be installed to /data partition in the internal memory. If you use a2sd/a2sd+, all apps will be automatically redirected to /sd-ext/app. That's a2sd. When dalvik cache is also moved on sd ext, you use a2sd+. The big advantage is, you do not have to move apps yourself to sd card. It will be done automatically, wether the developer of the app has programmed the app for this or not.
NEVER MOVE APPS TO SD MANUALLY WHEN USING A2SD/A2SD+!!
Referring to reflex s rom running cm7 hboot. Actually, the /system partition of cm7 hboot (130 mb or 145 mb with r2 version) does not give you enough space for reflex s rom. So things will be moved to internal /data partition. Problem is, you don't have enough space for apps because internal /data partition gets filled. To avoid this problem you need the ext partition on your sd card.
Conclusion: You should really bother about an ext partition!!!
MatDrOiD said:
Conclusion: You should really bother about an ext partition!!!
Click to expand...
Click to collapse
I though to choose CM7HBOOT to have faster application startup.
You say that Reflex S will fill the /data up and the other apps will end in /sd-ext/app, that is my (sloooow) uSD.
So my question: do you think it's really worth it installing CM7HBOOT with this ROM?
no, no, no, it is not the way matdroid said.
/system is bigger than 130mb (or 145mb) so essential parts stay on NAND, rest goes to SD-EXT, to the folder that is symlinked to the /system (not to /data)
now the apps that you download.
in order for you to understand it, i need to explain a bit. this rom is deodexed. if you really want to know what .odex file is do some research, it is not important. anyway in deodexed roms, apps run from Dalvik-cache and not from the .apk itself (.apk is only needed to create dalvik on 1st boot)
so in reflex S your .apk go to sd-ext BUT the dalvik stays in internal, and since its dalvik what matters ROM is fast.
rom system files do not fill up /data, the /system files that could not fit into 130mb go to sd-ext.
and overally yes, it is worth it, i basically re-discovered my desire after S-OFFing and running custom hboot roms. i have a class 2 sd card, and rom performs super fast (on custom hboot roms your sd class really doesnt matter anymore)
Uqbar said:
1st of all, thanks for the explanation!
So, If I understood well, my favorite ROM, which is Reflex S v2.1.7 should be installed in the CM7HBOOT variant. This ROM claims to support "AP2SD+".
Now, If the apps go in the internal /data partition, why should I bother about the EXT3 partition on my SD?
Very likely I'm still missing something else ...
Click to expand...
Click to collapse
and also i as wrote before ....
why should you bother about ext ???
cause /system is 130mb (or145) but it is not enough !!! AND I DID WRITE THAT REST GOES TO SD-EXT.
seriously, you gotta read everything if you are going to s-off and play with custom hboots
and also apart from some /system files on sd-ext, your downloaded .apk's will be on sd-ext too. only their dalvik will stay on NAND
dzumagos said:
no, no, no, it is not the way matdroid said.
/system is bigger than 130mb (or 145mb) so essential parts stay on NAND, rest goes to SD-EXT, to the folder that is symlinked to the /system (not to /data)
now the apps that you download.
in order for you to understand it, i need to explain a bit. this rom is deodexed. if you really want to know what .odex file is do some research, it is not important. anyway in deodexed roms, apps run from Dalvik-cache and not from the .apk itself (.apk is only needed to create dalvik on 1st boot)
so in reflex S your .apk go to sd-ext BUT the dalvik stays in internal, and since its dalvik what matters ROM is fast.
rom system files do not fill up /data, the /system files that could not fit into 130mb go to sd-ext.
and overally yes, it is worth it, i basically re-discovered my desire after S-OFFing and running custom hboot roms. i have a class 2 sd card, and rom performs super fast (on custom hboot roms your sd class really doesnt matter anymore)
Click to expand...
Click to collapse
Good to know, thanks. Thought it would work the way I described.
Hmmm ... I don't understand why the ROM looks quite slower than before (STOCK HBOOT) ...
Accordingly to what dzumagos says, I should get a (much) better experience now.
I understand the Dalvik cache stuff and what he says makes sense to me.
Nonetheless the ROM seems to be way slower than before ...
My system should be 145MB, cache 5MB and data 287MB.
Settings say that I have 256MB available on /data e 34MB on /system.
This should mean that I'm not really exploiting the internal storage!!!
And in fact my 1GB ext3 partition is at 50% of capacity.
Now, if my /cache is 5MB as said by AlphaRev, I think it's way too small to fit the (Dalvik?) cache I'd need.
What'd be your view here?
Finally, I'm trying to read everything. But the information is scattered among a dozen of threads each with dozens of posts ... and, as you can see, it's far from easy to discern the cream from the crap.
I really tried to figure it out before posting!
Uqbar said:
Hmmm ... I don't understand why the ROM looks quite slower than before (STOCK HBOOT) ...
Accordingly to what dzumagos says, I should get a (much) better experience now.
I understand the Dalvik cache stuff and what he says makes sense to me.
Nonetheless the ROM seems to be way slower than before ...
My system should be 145MB, cache 5MB and data 287MB.
Settings say that I have 256MB available on /data e 34MB on /system.
This should mean that I'm not really exploiting the internal storage!!!
And in fact my 1GB ext3 partition is at 50% of capacity.
Now, if my /cache is 5MB as said by AlphaRev, I think it's way too small to fit the (Dalvik?) cache I'd need.
What'd be your view here?
Finally, I'm trying to read everything. But the information is scattered among a dozen of threads each with dozens of posts ... and, as you can see, it's far from easy to discern the cream from the crap.
I really tried to figure it out before posting!
Click to expand...
Click to collapse
Dalvik cache is not in the /cache partition.
I think I get the reasons for custom hboot but how do you tell which hboot you've got?
My Desire is rooted and S-OFF. I have flashed with STOCKHBOOT version of Reflex_S_2.1.7_LITE_GingerBread_Sense-2.1_GRI40_A2SD+
It works but don't know if I should have used the the CM7 version.
after s-offing you get a stock unlocked hboot.
roms designed for cm7 hboots will work on stock hboot but it works only this way.
MatDrOiD said:
A2SD/A2SD+ works on this way:
Usually all apps will be installed to /data partition in the internal memory. If you use a2sd/a2sd+, all apps will be automatically redirected to /sd-ext/app. That's a2sd. When dalvik cache is also moved on sd ext, you use a2sd+. The big advantage is, you do not have to move apps yourself to sd card. It will be done automatically, wether the developer of the app has programmed the app for this or not.
NEVER MOVE APPS TO SD MANUALLY WHEN USING A2SD/A2SD+!!
Referring to reflex s rom running cm7 hboot. Actually, the /system partition of cm7 hboot (130 mb or 145 mb with r2 version) does not give you enough space for reflex s rom. So things will be moved to internal /data partition. Problem is, you don't have enough space for apps because internal /data partition gets filled. To avoid this problem you need the ext partition on your sd card.
Conclusion: You should really bother about an ext partition!!!
Click to expand...
Click to collapse
Thanks for the heads up but am still a bit confused. Pls help me out.
I'm s-off and using the cm7 hboot running Insertcoin stable 1.0.8 cm7 version. Now in the rom under settings>applications>manage applications when you click on some apps you get the option to move the app to sd card and when you do so it frees up some internal memory. But you say not to move apps to sd card manually Should I do this or not?
Any help to clarify would be much appreciated
This is froyo/android a2sd and yes you can do it. It moves some app data to fat32 while a2sd+ move parts of the app itself (in this specific case the .apk only) to the ext. Dalvik will stay on internal unless you issue some superuser commands in adb or terminal.
Sent from my HTC Desire using XDA App
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
herb1 said:
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
Click to expand...
Click to collapse
Sense since its a sense rom?
herb1 said:
I'm also confused...so for Reflex S, which hboot should I be running?
Bravo Stock
Bravo N1Table
Bravo Data++
Bravo Sense
Bravo Oxygen r2
Bravo CM7 r2
Bravo Downgrader???
Click to expand...
Click to collapse
Use the recommended one. Maybe you need to search the thread for this.
You only need the downgrader if you flashed one of the r2 hboots and want to change it now.
Sent from Oxygen
Ok I use bravo sense but cm7 r2 does work with reflex s too
Then make sure you use cm 7 version of reflex!
I followed instructions on Apharev homepage and flashed the 'bravo_alphaspl-sense.img'
Downloaded the necessary PB99IMG zipfile and saved it to SD card
now phone goes silver ANDROID logo that reflects passing light after splash image but won't loaded my homepage afterwards
HELP????
Hi,
I have recently rooted, full s-offed and hbooted my friends Desire.
Im a DHD user myself and am trying to get to grips with how you guys handle your devices when it comes to roms.
So far, I 'get' the hboot situation and partition layouts etc and have taught my friend.
Now Im getting a bit lost with the whole sdext part of it as well as the apps/data2sd side.
I know how to partition and get them applied but lose it on actually how they work when it comes to roms. Any rom that uses normal layouts such as CM7 I get.
Take for example:
[ROM][Cool3D Sense 3.0][26 July]Cool Sensation v6a|Stable|CM7/r2|DATA++|STOCK
I get this part:
Requirement:
CM7 Hboot 130MB System, 5MB Cache, 302MB Data. Download
CM7 r2 Hboot 145MB System, 5MB Cache, 287MB Data.
DATA++ Hboot 180MB System, 5MB Cache, 252MB Data.
STOCK Hboot 250MB System, 40MB Cache, 147MB Data.
Click to expand...
Click to collapse
So I on put CM7r2, now how do the partitions work?
Is it Partition 1 = /system, 2 = /data?
I tried it with 1=512 & 2=1gb but it just froze with only SystemUI running after the lockscreen.
I can see what the roms doing via the zip/updater-script but this whole partition thing is lost on me.
Any help is appreciated!
On a related side note, this will also help us provide support for lower nand devices with our Flashable ROMCleaner 2.0 we have recently released.
Once we get this down we are pretty much able to support most roms!
I think the easiest, briefest way to explain the ext3/4 partition is to think of it basically as an extension to your internal memory. Don't think of it as being a partition on your SD Card (even though it is) but an extra bit of internal memory. This ext is where apps will be stored if you have a2sd.
To avoid app piracy, many apps can't be stored on the SD Card (normally), so this extension to your SD Card is created to store them, that's why the ext partition isn't formatted as FAT32. If it was formatted FAT32 the phone wouldn't recognise it as being part of itself (if you like), but rather still part of the SD Card.
Hope this makes sense.
EDIT: Just re-read your post and if you've flashed the HBOOT it will automatically repartition depending on which HBOOT you flashed. You don't need to repartition anything. If you already ext partitioned your SD Card this won't be affected.
So when a rom installs to the sdext partitions its pretty much 'symlinking' the data which would normally reside on the internal partition?
When the system want to access this file then would it still 'see' it as sitting on the internal?
If it does then it would make our cleaning script a lot easier lol
As for the hboot, I didnt know it actually created the partitions for you when flashed as he had already got 2 on his sd.
Would this explain the freezing with the roms then? With Cool3d it seems that /system is split between internal and sdext so Im assuming the sdext side of it wasnt getting copied across?
May have something to do with the order of partitions as well, 1=system 2=data?
First of all the SD card needs partitioning, which I'm guessing you did, with something like GParted? You would create either a ext3 or ext 4 partition, minimum 512MB. Normally a ROM states min. size for ext partition but the thread for Cool3D doesn't seem to so 512MB or 1GB would be ok. If in doubt pm the dev to make sure.
Cool 3D requires ext 4 which needs aligning before flashing the ROM (but if the SD Card already has ext 3 this will be converted automatically when aligning to ext 4)
Then flash the correct HBOOT (choice of 4 listed on the thread) using fastboot then flash the new ROM. The thread also states you need to have specific Radio and RIL. All "stuff" you need is linked in the first post. Just follow the instructions on the first post and you can't really go wrong.
The freezing you mention could be caused by not aligning your ext partition first.
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
blahbl4hblah said:
Having sd-ext partition on your sdcard will always be benefical, the phone will run so much better believe me
Click to expand...
Click to collapse
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
ArmedandDangerous said:
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
Click to expand...
Click to collapse
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
ArmedandDangerous said:
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
Click to expand...
Click to collapse
GB has the ability to do Apps2SD but it requires the partitioning as, I believe, a symlink is set up so that partition on the sdcard acts as a part of the devices internal storage.
As for speed, just moving apps to your sdcard won't speed up your phone; what that poster you quoted was talking about (most likely, I'd have to see the original thread) was converting your devices partitions (/system, /data, /cache, etc.) from ext3 to ext4. ext4 is a bit faster however some ROMs do not fully support it.
Sent from my T-Mobile G2 using XDA App
Ok, let's clear this up. GB has Apps2FAT32 (a2sd) natively. A2EXT is completely different but none of that is the point of the OP's question.
When it comes to our phones - there is almost no notable performance gain when using EXT4 over any other EXT format. Our phones don't utilize FAT32 internally - just on the sdcard. EXT4 is designed for use with massive file systems. A couple Gigs really doesn't access it's full potential.
While the question is interesting, I'm not really sure what you're planning on doing. Don't format your sdcard entirely in EXT format, and don't attempt to format your phones partitions as FAT32. The result would be... just don't do it.
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
This has two main advantages: larger sized data partition and more speed as EXT is inherently faster for I/O purposes.
Click to expand...
Click to collapse
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
ArmedandDangerous said:
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
Click to expand...
Click to collapse
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
Thankfully I am already using meXdroid~ Guess I'll just wait for the new version in the next few days to do the formatting. Can I backup all my apps with Titanium Backup, flash ROM (wipe data/cache and dalvik cache), restore with Titanium.
Or would I have to reinstall every app again so that it goes into the ext4 partition?
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
KCRic said:
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
Click to expand...
Click to collapse
I'm doing it for the performance. Have been using 4EXT for a few days and loving it. Already converted internal memory to ext4 from ext3. If further partitioning my SD card for performance is really not noticeable, then I guess I've got nothing to worry about
Hello,
I am new in all the things connected to ROM's, but I have rooted my Desire and s-off. I really like InserCoin at the moment, but I do not know which version to choose. I have STOCK HBOOT, but maybe I should better put CM7 HBOOT and use A2SD? If I understand correctly then CM7 HBOOT has more space for apps, because /data is 287M, but STOCK 147M? As I see changing HBOOT is not very hard, so I want to know.
I have class 4 SD card, and I want to install apps and not to worry about the free space. Which do you suggest?
Also wanted to know some info about EXT2/3/4, I found lots of comments, but everyone says different which to use. Which would be the most optimal for me?
Thank You!
I've been an Insertcoin user until the developer stopped supporting HTC Desire. Since you have a class 4 card, I would suggest you try the Stock Hboot version and see if it's fast enough for you.
If I can remember correctly the main difference between the Stock and CM7 version is that on the CM7 version, dalvik cache was left in the data partition of the phone while on the Stock everything was moved to the EXT partition of the SD card.
They say that CM7 is faster given the fact that dalvik is on the phone and not on the SD card. I've only used the CM7 version so I really can not verify how big is the difference in speed between the Stock and CM7 version.
I've used EXT4 partition as it was recommended for Insertcoin. I never really bothered trying out the other partition types.
The difference between A2SD and A2SD+ is, that with the last one not only app, also dalvik cache is moved to EXT-partition. So if your SD card is not fast enough, you will have lags. But I have moved A2SD+ with a Class 2 SD card and never had any problems. So I recommend to test if A2SD+ is working for you. I am pretty sure it will.
If you wanna use DATA2SD, you may need a new SD card because a Class 4 SD card might be too slow. Although I would also test before.
My recommendation for the type of the EXT-partition is 4, because it is the fastest.
OK, Thank you both for the information, will try A2SD+ and EXT4 later today.