Re: [RECOVERY] TWRP 2.2.2.1 touch recovery
/system and /data are on an mtd device in the optimus v. From my limited understanding, it requires a file system that understands the basic flash layout and can read and write to the raw storage and manage bad blocks. Newer higher end devices tend to use emmc (similar to an sdcard for storage). Those handle the lower level stuff on their own and leave a file system to just do higher level stuff. You make be able to force it to ext or something, but you'll probably kill the device very quickly.
Note: I have not researched this much. Everything I say is just what I think I understand based on what some android devs have posted. I could easily be wrong.
Another random piece of interesting info. Since the file system does almost everything on mtd devices, it also handles the location and sizes of partitions. From what I have seen, this info is passed to the kernel from the bootloader or the kernel command line. Resizing partitions is easy in theory, just change the info passed. Unfortunately, there are a couple partitions between cache and system (recovery, splash, and fotasomething..) that prevent us from resizing that useless partition to give us more /data. On a device with emmc storage, we could just change the partition map and the device will handle everything without issue (just like on a PC)
Also, I prefer ext2 or ext4 without journaling on flash storage. Im okay with risking data loss to extend the devices life. You shouldn't keep important data on a phone anyway.
/system and /data are on an mtd device in the optimus v. From my limited understanding, it requires a file system that understands the basic flash layout and can read and write to the raw storage and manage bad blocks. Newer higher end devices tend to use emmc (similar to an sdcard for storage). Those handle the lower level stuff on their own and leave a file system to just do higher level stuff. You make be able to force it to ext or something, but you'll probably kill the device very quickly.
Note: I have not researched this much. Everything I say is just what I think I understand based on what some android devs have posted. I could easily be wrong.
Another random piece of interesting info. Since the file system does almost everything on mtd devices, it also handles the location and sizes of partitions. From what I have seen, this info is passed to the kernel from the bootloader or the kernel command line. Resizing partitions is easy in theory, just change the info passed. Unfortunately, there are a couple partitions between cache and system (recovery, splash, and fotasomething..) that prevent us from resizing that useless partition to give us more /data. On a device with emmc storage, we could just change the partition map and the device will handle everything without issue (just like on a PC)
Also, I prefer ext2 or ext4 without journaling on flash storage. Im okay with risking data loss to extend the devices life. You shouldn't keep important data on a phone anyway.
Facebook
Twitter
Instagram