WarrantyVoider
Android Enthusiast
Some notes:
1. Like crm701 said,
2.
3.
The copier script does not create or format the partition. The script will remove all files before copying files unless the tag file .LGF6DataOnSD_DO_NOT_REMOVE already exists.
- So, to delete the tag file only, mount /sd-ext and use the file manager to delete /sd-ext/.LGF6DataOnSD_DO_NOT_REMOVE .
- To delete all files on the partition (without relying on the copier script), do:
Settings->check "use rm -rf..."->back to main screen->Wipe->Advanced Wipe->check only "sd-ext"->swipe to wipe->back to main screen->Settings->uncheck "use rm -rf..."->back to main.
- To format the ext4 partition in TWRP, make sure /sd-ext is not mounted. Then in terminal window, use the command:
mke2fs -T ext4 /dev/block/mmcblk1p2
Be careful with any command that formats anything.
4.
The internal memory on a low-end phone usually isn't very fast. I think it might be possible for a high-end SD card to have better performance numbers.
Also, only /data resides on the SD card. The other partitions like /system and /cache remain where they are, on the internal storage. The dalvik cache is normally in /data, so that might be relocated. I think CM puts that in /cache, so you might use CM to see if the lag occurs or disappears compared with the other KK rom. If it turns out a better SD card can actually help performance, perhaps /cache could be moved to the SD card as well.
Thanks for the feedback.
1. Like crm701 said,
EDIT: use either -install OR initd. You dont need both.
2.
After installing the rom, reboot into system to allow the rom to set up its /data. And the partitions need to be set up on the SD card already (1st=fat32, 2nd=ext4). The copier script needs valid data to copy from and needs valid destination partition to copy to. So do -initd.zip after getting back in TWRP (without triggering data wipe from using physical buttons to enter). After flashing the -initd.zip, TWRP will complain about unable to mount /data. In the file copying process, I mount /data read-only and unmount afterwards. Perhaps doing so leaves the partition in a state unknown to TWRP. I didn't bother trying to figure out the reason, since I assume the user is rebooting to the system anyway.Fresh installed 4.4.4
Intd zip installed successful
Install zip successful
Rebooted
No monts no change.
3.
The copier script does not create or format the partition. The script will remove all files before copying files unless the tag file .LGF6DataOnSD_DO_NOT_REMOVE already exists.
- So, to delete the tag file only, mount /sd-ext and use the file manager to delete /sd-ext/.LGF6DataOnSD_DO_NOT_REMOVE .
- To delete all files on the partition (without relying on the copier script), do:
Settings->check "use rm -rf..."->back to main screen->Wipe->Advanced Wipe->check only "sd-ext"->swipe to wipe->back to main screen->Settings->uncheck "use rm -rf..."->back to main.
- To format the ext4 partition in TWRP, make sure /sd-ext is not mounted. Then in terminal window, use the command:
mke2fs -T ext4 /dev/block/mmcblk1p2
Be careful with any command that formats anything.
4.
Try to measure the random r/w performance. Using A1 SD Bench's (dunno if reliable, I just use one I found in play store) random I/O, I get roughly 10.84 MB/s reading and 0.41 MB/s writing on a Samsung class 6 (using internal memory option after mounted as /data) and 17.24 MB/s reading and 0.20 MB/s writing on the phone's internal storage. Class 6 cards are obviously not fast performers, but Samsung cards have very good random access characteristics. Maybe lag exists on my end too, but I haven't tested it enough to notice. Note that I'm not using ext4 for my /data on the external SD, so don't compare with my numbers. Compare your benchmark data between the internal storage and the SD card.I did note a bit of lag, not much, on the browsers or the app stores scrolling up/down. I got thinking and tested my SD-card and got benchmark scores of 27-32 read / 8-11 write. The F6's intern. storage 45 read / 15 write. I was wondering if there is a way to have /cache and maybe /system mounted (or symlink?) back to F6's intern.? If so, would that possibly provide any boost for slow SD cards? I am not sure if it would provide any benefit, or if its possible or feasible, but I am curious.
The internal memory on a low-end phone usually isn't very fast. I think it might be possible for a high-end SD card to have better performance numbers.
Also, only /data resides on the SD card. The other partitions like /system and /cache remain where they are, on the internal storage. The dalvik cache is normally in /data, so that might be relocated. I think CM puts that in /cache, so you might use CM to see if the lag occurs or disappears compared with the other KK rom. If it turns out a better SD card can actually help performance, perhaps /cache could be moved to the SD card as well.
Thanks for the feedback.