[T-Mobile Samsung Galaxy Note II] pyraxiate:
I'm suppose I will have to record a video of me doing the technically impossible then. .... Because I in fact did. What i posted earlier was for fact what was done. I've no reason to lie to you. If you refer to my post I stated exactly what i did and what the results are.

1-fresh install of jedi master 14 ( wiping everything but external sd )

2- reboot into twrp

3 - made a backup

4- used the aroma ext2 installer backing up / restoring both data and storage. I selected trinity at this point.

5- Rebooted. Everything came up at this point working perfectly and partitions showed at ext2 ( system, data, and cache ).

Then, I rebooted back into twrp, and flashed ptmr3's saberkernel version 28. Wiped cache and rebooted. Everything once again booted up perfectly. No problems whatsoever. ..... but now my partitions showed as ext4. I did not backup / restore any data what so ever after flashing saber. Its as though the kernel was forcing ext4.

In a linux environment, you would generally have to edit fstab and change the mount point / partition type. Im still getting used to how things differ on an android system, but, id think somewhere in the kernels ramdisk, its telling the system to use ext4. Should be easily resolved id think.

As far as on the fly conversion of ext2/3 to ext4 nondestructively goes on a linux system ( without having to copy / format / restore data) , it is possible since kernel 2.6.28-11 using tunefs .... Just in case you were unaware.

http://www.ghacks.net/2010/08/11/convert-ext23-to-ext4/

http://askubuntu.com/questions/2407...tem-to-ext4-to-prevent-fsck-every-time-i-boot

I'm not trying to start an argument or flame in your thread, and I hope you dont see my posts coming off that way. In fact I agree that it probably shouldnt be booting at all. The only thing I can think of is that because we are using kernel 3.0+ now, it is somehow seeing ext2 AS ext4, and since 4 is just a journaled /updated version of 2, it simply works. Technically it should be fully backwards compatible ( hence why since 2.6.28 you can simply convert without losing data ).

Personally I see how ext 2 could possibly benefit our devices otherwise I wouldn't be here trying. .... I am a linux user though and while I may not be an Android developer, I know my way around well enough. They are quite similar in many ways. Im just trying to help where I can.

**Edit**

After a bit more research, you CAN actually mount ext2 as ext4 with journaling off ( since ext4 also has a non-journaled mode). No need to repartition / format / copy-paste data. Ext4 is fully backwards compatible.This would explain why Saber actually does work and reports as ext4! I WAS mounting my ext2 system as ext4. Saber still felt faster than when it was running from a clean ext4 install. I can only imagine its due to not having journaling enabled after boot. Read here: http://en.m.wikipedia.org/wiki/Ext4

Looks like someone owes me an apology as all three of those quotes appear incorrect ;)

As a side note, can't we just disable journaling on current ext4 partitions and see the same performance increase while still retaining some of the good things ext4 has to offer? It would be a whole lot easier writing a twrp / cwm zip and it could then be used with all roms/ kernels still achieving the same thing ( a slight boost in I/O ).

And for the cool part. I pulled the trinity ext2 boot image and placed it into a zip. I can now flash between saber 28 (ext4) and trinity. After reflashing just the trinity kernel, it becomes ext2 again ( as its told to mount as ext2 ). If anyone who has already converted to ext2 wants to test morfics kernel, this is safe. Just flashed it. http://db.tt/L7WwJzSE