yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Khaon:
For now, TWRP can detect when you are wiping your partition what tools it would has to use. I.e : if you choose to wipe data partition, system, etc.

And use the correct tool accordingly. But official version do not mount yet however f2fs partition.

The fstab is in the ramdisk, so contained yep in the boot.img. But there are few mount options, some may need to be activated in case of unstability
[Nexus 10 Original Android Development] b1g.p0ppa:
Thank you for your reply. Perhaps the best thing is to create a flashable zip to be run after ROM flash to install fstab.manta?

Also, FWIW, here's some sed commands to update your updater-script per the instructions in the OP:

sed -i 's/^mount("ext4".*\/system*/run_program\("\/sbin\/busybox", "mount", "\/system"); /' updater-script

sed -i 's/^format("ext4".*\/system*/run_program("\/sbin\/mkfs.f2fs", "\/dev\/block\/platform\/dw_mmc.0\/by-name\/system"); /' updater-script
[Nexus 10 Original Android Development] Khaon:
Hello I just added some executable java program that convert a rom script to be f2fs compatible.

Also, having less issues with lastest kernel build but I tried it on new roms. ROMs fully working so far and stable : liquidSmooth 3.1 & slimkat 4.9.

Before I was using CM11 M7 it was working but was encoutering some freezes/reboot- especially at the beginning - but then it was ok. I can not tell if this is still happening with cm rom.

I haven't test the pc program on windows if anyone could say it does work, thx!

EDIT : thank to [MENTION=3999298]dust40[/MENTION]; he told me the tool was working on Windows as well! Should work on mac too then i guess.
[Nexus 10 Original Android Development] b1g.p0ppa:
Well I successfully converted /data and cache to F2FS. I made the effort way more work than it had to be by preserving my data. WAY more work. Booted in recovery mode I tar'ed up /data to a exfat formatted usb-otg drive then ran the conversion. Ran into 'value too large for defined data type' errors from tar when extracting. I ended up extracting the tarball onto my workstation, deleting the file it crapped out on, tar'ing it all back up to the usb drive and re-running the extraction. Had to repeat this procedure a good dozen times and I ended up with messed up permissions on all my data. I don't suggest anyone try this because it would have taken much less time to just set up a fresh installation, but if you do here's some good commands to fix up permissions (TWRP's fix permissions command doesn't fix what I messed up). I found these commands at http://xdaforums.com/showthread.php?t=2222297 but had to adjust them a little bit. The chown command has to be run when booted to android, the chmod commands can be run from either recovery or android. Reboot immediately after running. Best to run through adb shell than in an app on the tablet.

find /data/media/ -exec chown 1023,1023 {} \;
find /data/media/ -type d -exec chmod 775 {} \;
find /data/media/ -type f -exec chmod 664 {} \;

[MENTION=4577448]Khaon[/MENTION], can you ask ktoonsez to compile 4.4.4 versions of the kernels? Latest OmniROM update for manta is 4.4.4 but will not boot with this kernel. And obviously I cannot run any other kernel as none others support F2FS. Thanks in advance! And thanks for putting this thread together. Without your good instructions I probably wouldn't have had the guts to convert this early.

One last thing, I can report that OmniROM works perfectly with /data and cache formatted as F2FS (once permissions are set right!). And since I preserved my data I have an apples to apples comparison of performance and it is noticeably faster and smoother!
[Nexus 10 Original Android Development] ericp2:
kt-recovery stuck at splash screen

Hi,

I had originally posted this in ktmanta thread:

I have been running F2FS on cache+data for past 2 weeks and it works very well (still some strange system freezes, i will need to investigate further on that).

However, now, when i boot to recovery, screen stays stuck at splash screen showing "f2fs enabled by Ktoonsez..", and does not go anywhere else. i can still flash using adb, but clearly, it's less than convenient, and using twrp 2.7.10 is not an option, as it can't mount f2fs sdcard properly anyways.

with adb shell, i can see that all is mounted properly, f2fs or not, but obviously, it's less than ideal... i have attached /cache/recovery/log file .

Note: i connect usb cable 2 to 3 mn after waiting for splash screen to go away, and i pulled recovery log at that moment. this was also the only way to get out of this stuck mode, via 'adb reboot' command.

i also tried to re-flash recovery via fastboot, but that made no difference.

any help appreciated !
[Nexus 10 Original Android Development] Khaon:
[MENTION=5906781]ericp2[/MENTION] [MENTION=3721939]b1g.p0ppa[/MENTION]

Can you just try this recovery and tell me if you are running any issue? This is just last official twrp 2.7.1.0.

Just formated and installed a new ROM, ran into no issue, guess should be the same for you :D.
[Nexus 10 Original Android Development] Khaon:
Glad you like the kernel running this, if I understood correctly, you wanted to back up the internal storage( so /data/media/0) and your apk folder to an exfat usb drive you mounted with otg? If the fs of this one was exfat that is probably the cause of your issues, I am not even sure our tablet nativly supports exfat( isn't a samsung fs that allows 32GB ++ partition size?). Lastest Omni kernel is booting I assume?
[Nexus 10 Original Android Development] ericp2:
:cool: Issue fixed. this version of TWRP starts correctly, and f2fs formatted sdcard can be listed, so i can again flash CM updates.

many thanks!
[Nexus 10 Original Android Development] nigelhealy:
So is .107 and CM not getting along? The other kernel does what?
[Nexus 10 Original Android Development] ericp2:
Apparently not. all other kernels by Khaon i have tried so far worked, but not this one. i thus reverted for the moment to khaon_kernel-09-26-2014 which works just fine. (see first page for download links)
[Nexus 10 Original Android Development] nigelhealy:
There are two current ones

http://xdaforums.com/showpost.php?p=55766146&postcount=168

khaon_kernel_manta_linux_mainline-02-10-2014.zip (is running linux 3.4.67, you not tried?)

khaon_kernel_manta_google_mainline-02-10-2014.zip (is linux 3.4.104, you get boot loop on)
[Nexus 10 Original Android Development] Khaon:
Both last kernel from media fire ( 02/10 build) are booting fine on my tablet. I am running cache/data with f2fs and system ext4.

Try cleaning again your caches
[Nexus 10 Original Android Development] ericp2:
Hi,

it made no difference. please find included last_kmsg, there are a few disturbing lines like:

[ 7.130780] F2FS-fs (mmcblk0p9): Invalid blocksize (0), supports only 4KB

[ 7.130905] F2FS-fs (mmcblk0p9): Can't find valid F2FS filesystem in 1th superblock

and a lot of recovered inodes (which is probably due to reboot)

Also, kernel indicates

[ 0.000000] Linux version 3.4.39-g9aa8b83-dirty (khaon@khaon-pc) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Fri Sep 12 21:04:21 CEST 2014

which does not seem right either!

Please PM if you want more info.
[Nexus 10 Original Android Development] Khaon:
Hmm.

Make sure you trying latest version also if not working repair your data partition through cmd line or recovery

I just flashed to be sure the build on mediafire was working.

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] nigelhealy:
This is what a /cache /data f2fs /system ext4 looks like

cat /proc/version; mount
Linux version 3.4.104-khaon-kernel-09109-g03b955c (khaon@khaon-pc) (gcc version 4.7.4 (crosstool-NG linaro-1.13.1+bzr2694 - Linaro GCC 2014.06 - Cortex-A15) ) #1 SMP PREEMPT Wed Oct 1 01:36:46 CEST 2014
rootfs / rootfs rw,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[B]/dev/block/platform/dw_mmc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0[/B]
[B]/dev/block/platform/dw_mmc.0/by-name/cache /cache f2fs [/B]rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,flush_merge,active_logs=6 0 0
[B]/dev/block/platform/dw_mmc.0/by-name/userdata /data f2fs [/B]rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,flush_merge,active_logs=6 0 0
/dev/block/platform/dw_mmc.0/by-name/efs /factory ext4 ro,seclabel,relatime,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

So far, under Thunderkat, this is performing and stable. :good:
[Nexus 10 Original Android Development] lynnux:
Is this notably smoother and faster than ext4? I need to be convinced, it's a little more trouble than just trying out a new rom. Where do you notice the improvement?

My biggest complaint with my N10 is the jitter/lag when scrolling through home pages, while browsing, and some lag opening apps. I'll try this in a second if I think it'll be a big enough improvement.
[Nexus 10 Original Android Development] nigelhealy:
"Noticeable" for me is too strong a term. Benchmarks for read/write show better performance which is what /data and /cache use. /system is read-only and ext4 benchmarks faster than f2fs for read. Whether that shows as perceptible gains, I don't know.

AS to it getting rid of the lag on scrolling, NO, I still see a wobbly page as I scroll the right drags relative to the left. That's due to too slow GPU and CPU for the resolution.

I tend to use my N10 for one-app media consumption for which it excels.

I'd suggest just the recovery and kernel changes for fs2fs and keep ROM as ext4 (personally), I'm also got the same question as you can you notice an improvement? (I can't but benchmarks indicate I should be getting some gain).
[Nexus 10 Original Android Development] Khaon:
well according to those result there is a certain gain bench

also according to samsung the io workload can be reduced up to70% !

Check page 318 at this link or or this
[Nexus 10 Original Android Development] ericp2:
Hi, hmm indeed. Sometimes those things behave oddly. I downloaded again .104 along with latest cm, flashed again, and added a fix permissions. All is fine now. Beats me!!! Maybe it was the fix permissions that did it, or first time download was corrupted somehow (although I could browse the archive just fine, I always do that before flashing).... Or something else altogether
[Nexus 10 Original Android Development] Khaon:
No problem at all!

I have built and uploaded a new CM rom. As usual you checkout the build here, it has been compiled with linaro 4.8.4 ( linaro4.9.2 doesn't boot, might be releated to some libraries).

Downloable at this link

This ROM is shipped with default updater-script and kernel !
[Nexus 10 Original Android Development] nigelhealy:
Link doesnt work takes me to signup page not download page
[Nexus 10 Original Android Development] Khaon:
Hm this one should work https://www.mediafire.com/folder/gpqtgw402a8ch/Manta
[Nexus 10 Original Android Development] nigelhealy:
The question was *IS* the N10 noticeably smoother and we've both replied it is theoretically should be smoother and point to benchmarks.

The links you mention show why apps should be faster due to the faster write performance. But /system is read-only.

The benchmarks show read-only is faster on ext4. Hence whilst we've not answered the question, theoretically you should leave the ROM as-is using ext4 for fastest and move /cache and /data to fs2fs. This neatly also is simplest as no ROM changes.
[Nexus 10 Original Android Development] Khaon:
The reason is simple : there are more users using f2fs on /system partition than ext4. Plus some users might be interessted to use the rom without using my kernel.
[Nexus 10 Original Android Development] OmniSlyfer:
Hi guys, i'm on purity ROM, with evrything on fs2fs + lastest Kahon kernel... And my N10 is flyyyying :D It's much smoother then before, no lags, no problems :)

However I've read that keeping /system on EXT4 should be better, giving additional performance?
[Nexus 10 Original Android Development] nigelhealy:
Yes, theoreticaly, which is part of the problem.

The unit benchmarks how f2fs at read/write and ext4 faster at read-only, so /system is read-only whilst /cache /data are read-write. Compare these results

http://xdaforums.com/showthread.php?t=2697069

Whether some app is actually faster, dunno..... I've done the /cache /data fsfs to get any performance going but still when I move to N10 from say OnePlusOne I really notice the speed drop, I'm assuming f2fs is doing some good.
[Nexus 10 Original Android Development] mrgnex:
I have just changed system, data and cache to f2fs and converted my rom using the .jar. I followed the instructions and searched but could not find an answer. I am now stuck at the google logo. Not a boot loop it just won't progress. Any ideas?
[Nexus 10 Original Android Development] nigelhealy:
You tried the same and got the same result as me.

I backed away from all-f2fs and used non-modified ROM with /system as ext4. The actual benchmarks conclude read-only /system is faster hence better as ext4, whilst read-write is faster for fs2fs hence /cache /data as f2fs.
[Nexus 10 Original Android Development] mrgnex:
Yeah I found that, but it was 7 pages back so I thought it was fixed maybe. Thanks!
[Nexus 10 Original Android Development] Khaon:
Hello,

have you still the converted-f22fs archive? is yes could you give its content?
[Nexus 10 Original Android Development] mrgnex:
Yeah but its on my PC, ill share it when I het back home.

EDIT: Here it is: http://goo.gl/8XxzA6
[Nexus 10 Original Android Development] Khaon:
nvm this
[Nexus 10 Original Android Development] Khaon:
Rom update!

Now the updater-script checks if either your system partition is f2fs or ext4 before formating.

You don't need anymore to edit the script

The rom is shipped with my kernel
[Nexus 10 Original Android Development] jarocho151:
Under clocking with setcpu isn't sticking, anyone know of an app that does work and is light?

Thanks.
[Nexus 10 Original Android Development] Khaon:
Give a try with trickster mod you can lock frequencies.
[Nexus 10 Original Android Development] ChaosMinionX:
Latest Linux/Google mainline kernels published in october do not boot with F2FS enabled SlimRom 8.6 - I can get the device to boot with F2FS enabled with the 9/23 9/26 kernels, but the ones built in October do not work.

Any ideas?
[Nexus 10 Original Android Development] b1g.p0ppa:
I'd say ask the ROM Dev? They both worked for me on Omni and on Purity.
[Nexus 10 Original Android Development] Khaon:
I guess it must be related to the kernel. You can try repacking the ramdisk, I will work ASAP on a any kernel script since it will always work better...
[Nexus 10 Original Android Development] frontalot:
How can I use this kernel and F2FS for /data and /cache on stock (unlocked and rooted) KitKat?
[Nexus 10 Original Android Development] nigelhealy:
Flash the custom recovery to enable formatting as f2fs

Boot into recovery.

Wipe. Select everything dalvik system data cache.

Then wipe again but only for cache and system. Go to wipe Advanced. Change filesystem. Select f2fs. Do this just for the ones you want to change. /cache /data leave /system as is ext4.

Then install. Install stock ROM zip then the f2fs kernel. Boot. Should work.
[Nexus 10 Original Android Development] frontalot:
Followed your directions exactly and received:

Error flashing zip '/sdcard/image-mantara-ktu84p.zip'

Updating partition details...

Failed

---------- Post added at 10:30 PM ---------- Previous post was at 10:03 PM ----------

Got it to work:

1. Flash stock everything

2. Flash F2FS recovery

3. Change /cache and /data to F2FS

4. Flash Khaon kernel

5. Reboot and enjoy!

---------- Post added at 10:46 PM ---------- Previous post was at 10:30 PM ----------

Spoke too soon... for some reason I'm unable to root my phone by flashing UPDATE-SuperSU-v2.14.

Suggestions, please?
[Nexus 10 Original Android Development] Khaon:
Hello. You are using stock rom right?

This was reported root seems to be broken. Could you try with cm su ?

http://www.clockworkmod.com/superuser/install.html

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] joeski27:
So I'm trying this out tonight for the first time, and at first glance it looked like a success. Using the custom TWRP recovery, I wiped everything, then changed to f2fs (on system, data, and cache). Then I rebooted recovery, and verified that f2fs had taken in all three directories. At that point I tried to flash the unofficiall 10/12/14 CM rom, but unfortunately after doing so, I checked to see if f2fs was till in effect, and it was not. It does stick with /cache and /data, but not with /system. I have no idea what I could be missing here... :confused:
[Nexus 10 Original Android Development] frontalot:
Yes, using stock rom. Just tried CM SU and it failed to install, too.

You're better off formatting /cache and /data only as F2Fs and leaving /system as ext4. I've tried it on 4 different devices and this setup is clearly faster.
[Nexus 10 Original Android Development] Khaon:
Okay I will take a look to fix this.

Envoyé de mon MI 2S en utilisant Tapatalk
[Nexus 10 Original Android Development] joeski27:
Sounds good, am doing that now. But I have a kinda weird issue. While the tablet is absolutely flying now, I'm noticing a strange phenomenon in the Play store, where all the icons are all deformed and pixelated. Again everything else is running fine, and all other images, icons, etc. are appearing perfectly elsewhere. Could this be a kernel issue? As it is, I have toned down the CPU to a 1900mhz max & interactive (was really unstable at 2100 and performance), but I dunno what might be causing this. I plan to flash the latest CM nightly (currently using the custom CM version from this thread), so maybe that might fix things, who knows. Anybody have any thoughts? :confused:
[Nexus 10 Original Android Development] b1g.p0ppa:
I've seen the weird icons in play store mentioned elsewhere. Play Store is in your gapps zip. I'm using latest nano zip from http://xdaforums.com/showthread.php?t=2397942 and am not seeing that issue. Maybe try re-flashing ROM (dirty flash--no need to wipe data) to clean out any gapps in /system and then the nano package?
[Nexus 10 Original Android Development] Khaon:
I think one or two PLL dividers are wrong for 1800+ freq steps. I always forgot to fix that :D since I am not using any OC. Will look on that for next build.

Regarding playstore bug it is a bug that was introduced by linaro toolchain 4.8.3++. This commit was said to fix the problem.

Well tbh, I don't care having glitched icons in the playstore, however if the gappas package @b1g.p0ppa referenced fix the issue just flash this package.
[Nexus 10 Original Android Development] frontalot:
Looking forward to your updated kernel as it's a show stopper for me right now.

Thanks!
[Nexus 10 Original Android Development] nigelhealy:
With Android L not too far off for N10, what is Khaon's intention for a f2fs kernel?

I'm happy to wait obviously just seeking to find intentions.
[Nexus 10 Original Android Development] Khaon:
Well I am really looking forward to lollipol. I will be of course maintaining the kernel to be run on android L
[Nexus 10 Original Android Development] brees75:
Is this CM not compatible with ext4? It booted fine after a full wipe with the included kernel but on the first reboot it bootlooped. I tried it 3 times but had the same results. I haven't had a lot of time to change to f2fs considering the full device wipe and i really wanted to try out CM with linaro. Is it only configured for f2fs? During the flash it said ext4 detected but it also said f2fs detected.
[Nexus 10 Original Android Development] Khaon:
Hello, I guess the second message was for /data partition?
[Nexus 10 Original Android Development] brees75:
I didn't switch to f2fs. I flashed with 100% ext4. Is your CM rom ext4 compatible?
[Nexus 10 Original Android Development] brees75:
Replaced it, now the flash fails with updater binary error. Thanks for the quick response!
[Nexus 10 Original Android Development] Khaon:
Got same thing just now with my mi2s , i just had to replace the binary with a more recent.

I just attached the binary that was compiled with today build i ll release later...

In case this doesn't work as well just replace the script with an actual one targeting ext4, so default one
[Nexus 10 Original Android Development] brees75:
Thank you for the help, i will try it tomorrow after work. Really appreciate it!
[Nexus 10 Original Android Development] Khaon:
ewww 6am here made really noob mistake, if you look the script was mounting

mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name", "/system"),

Ofc couldn't work, i have edit in the former post the script.;

http://xdaforums.com/showpost.php?p=56144259&postcount=225
[Nexus 10 Original Android Development] Khaon:
New builds online

Hello everyone,

new ROM and kernel online !

Changelog

ROM:

20/10 unoficial nightly compiled with linaro 4.8.4 with this build

Shipped with my linux mainline kernel

Kernel :

mm: Added filesystem dynamic read-ahead (Credits to Chad Gooldman)

block:bfq:updated to v7r6

There has been a huge f2fs update, I will try to release by tomorrow.
[Nexus 10 Original Android Development] b1g.p0ppa:
10-20 kernel running great on Purity ROM with /data and cache F2FS, system ext4. Thanks [MENTION=4577448]Khaon[/MENTION]!
[Nexus 10 Original Android Development] Fidelator:
I've been wondering lately, how factible would it be to increase the amount of usable RAM? As you probably remember back when our devices launched we had like 1.7gbs of usable RAM, now we have a little bit over 1gb, that memory was given to the GPU but we never really saw a noticeable improvement in performance, that was a huge price to pay for barely anything.
[Nexus 10 Original Android Development] frontalot:
FYI, new build still isn't rootable on stock.
[Nexus 10 Original Android Development] Khaon:
Oh yeah , I totally forgot about this. Is first thing on my top list things to do! :good:
[Nexus 10 Original Android Development] Subrad5446@aol.com:
10-20 mainline kernel stuck at google logo on slimROM 4.4.4-8. Just an fyi, saw a few pages back it was an issue.
[Nexus 10 Original Android Development] Khaon:
Please provide me a full dmseg and logcat?seems ROM does boot
[Nexus 10 Original Android Development] Khaon:
Sorry for the delay, here is a kernel that should work with stock rom for SU
[Nexus 10 Original Android Development] Khaon:
Little update

Changelog:

f2fs:sync with upstream revision

ramdisk:stock rom should have no longer issues with root.
[Nexus 10 Original Android Development] Subrad5446@aol.com:
how to I do the dsmeg? And how to do the logcat if it doesn't boot? By the way forgot to mention I'm all f2fs. Dno't know if that matters.
[Nexus 10 Original Android Development] Khaon:
http://xdaforums.com/showthread.php?t=2185929

The rom might not boot but the kernel might have
[Nexus 10 Original Android Development] ChaosMinionX:
On these new mainline kernels... what has changed that I cant have /system as F2FS? The last build that worked for all partitions as F2FS was 9/26, since these Mainline-Linux and Mainline-Google kernels I havent been able to get it working.

I did get it working if I made /system as ext4, is this intended?