[Samsung Galaxy Nexus] 7175:
Excellent job on this kernel Smitty. Nice job with the custom unified ramdisk Osm0sis, tested on both ext4 and f2fs, works great, well tweaked. Great set of options, gov's, tcp alg's, voltage control.

Really happy to see the f2fs scene happening after seeing Smitty tinkering around with it on the developers developer thread a few months ago, this is definitely the way to go. I finally went over to f2fs after backing up my system. Performance is great, system seems to be a lot smoother. The only problem Ive run into is mounting with busybox which has been mentioned already. Also I needed to format all of system, data, cache, leaving system as ext4 didn't work for me.

Thankfully toolbox mount works with f2fs. Make sure sysrw, rootrw are scripted with toolbox remount and also symlink toolbox to mount and umount in /system{bin,xbin}.

Few things I thought id mentioned related to file backup and voltage while I'm posting:

(1)

For anyone wanting to make an init.d script for mpu or regulator voltage, I've found "here files" to be most effective, my battery saver voltage script:

#!/system/bin/mksh
#-

set -C; set -e

cat << 'eeooff' >| /sys/class/misc/customvoltage/regulator_voltages
VANA: 2100 mV
V2V1: 2100 mV
VAUX3_6030: 2500 mV
VAUX1_6030: 0 mV
VDAC: 1800 mV
VCXIO: 1200 mV
VUSIM: 2200 mV
VMMC: 1750 mV
VUSB: 3300 mV
eeooff

#cat /sys/class/misc/customvoltage/regulator_voltages

cat << 'eeooff' >| /sys/class/misc/customvoltage/mpu_voltages
1760mhz: 1400 mV
1720mhz: 1425 mV
1650mhz: 1415 mV
1600mhz: 1400 mV
1500mhz: 1395 mV
1400mhz: 1388 mV
1350mhz: 1300 mV
1200mhz: 1180 mV
920mhz: 980 mV
700mhz: 975 mV
525mhz: 880 mV
350mhz: 810 mV
230mhz: 800 mV
190mhz: 790 mV
eeooff

#cat /sys/class/misc/customvoltage/mpu_voltages

set +C; set +e
:

(2)

For people who want to back up their phone as fast as possible and preserve file attributes:

If you have linux pc or cygwin on windows, I would back up all your data via nc (netcat). First you need a connection a to your PC. Port forwards with adb and a USB is usually most convenient. Telnet, a ftp server, wireless adb also convenient options.

General process: Make a fresh pipe, cpio archive /data or subdirs to the pipe, nc cat the pipe to port 5555, and with your Linux PC or cygwin, listen to the port and write to a file such as data.cpio. Reverse to restore. This is much faster than adb pull and preserves symlinks, perms, etc.

(This is documented on xda: pull up the first result for the search "yes we can" and check the links at the bottom of the post.)

To stream a /data cpio archive to a pipe file to your PC, use these commands after you have pc-android connection established:

Adb or on term emu:

mkfifo -m 0666 /cache/mf

nice -18 find /data -print0 | cpio -H newc -oF /cache/mf

nice -18 nc -l -p 5555 -e cat /cache/mf

On your pc:

adb forward tcp:5555 tcp:5555

nice -18 nc 127.0.0.1 5555 | pv -i 2 > data.cpio

OR without pv spinner:

adb forward tcp:5555 tcp:5555

nice -18 nc 127.0.0.1 5555 > data.cpio

If you don't have 64bit PC, or are restoring files, use split to split the giant output archive v to sizes less than 4GB. Then on android do:

cd /data; cat ...a ...b ...c .... | xargs | cpio -i

(Use xargs with some options for throttle control if you run into OOM problems, super lag)