yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Khaon:
Hm weird, adb logcat should be ro.debuggable is set to 1.

Log from recovery doesn't help, however you can provide me your kernel.img

adb shell "dd if=/dev/block/platform/dw_mmc.0/by-name/boot of=/tmp/boot.img"

will copy your current image into /tmp/boot.img

adb pull /tmp/boot.img OUT_PUTDUR

will copy the image to your chosen dir.

Doing that from recovery will be easier for you, you don' t have to wait the recovery to have finished booting to do so, as soon you see the twrp blue screen you can type the commands.

What solution did you just flash?

You should not be in the need of wiping caches any more, seems art is smarter, however, it happened to me sometimes that I need to reboot the first reboot, dunno why but it was stucked at the boot seq, to make things work.
[Nexus 10 Original Android Development] Khaon:
Just to notice people who didn't know,

Official twrp 2.8.2.0 supports natively f2fs, so you can now just go ahead and use official release!
[Nexus 10 Original Android Development] b1g.p0ppa:
I flashed the 12-10 anykernel (f2fs version wasn't available yet). A second reboot without clearing caches did not work. Am clearing dalvik and /cache now and will report results. boot.img: https://www.mediafire.com/?lbii2zkh4phd94s

---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------

Whoa. 2.8.0.2 official takes a really long time to boot. I read somewhere that they've solved that in 2.8.2.1 but it's not available yet for manta. I flashed back to your 2.8.1.0 recovery as it works great for me.

Just getting around to rebooting after clearing caches. Will report.

Edit: unfortunately it still did not boot. Flashed the 12-10 f2fs kernel and is booting properly.

Edit2: 12-10 f2fs kernel got to the end of optimizing apps and rebooted itself. It wouldn't progress past the boot animation after that. boot.img from it: http://www.mediafire.com/download/vcofnv4d6oc19ig/f2fs-boot.img

Flashed back to 11-26 kernel and it's time for me to go to sleep. Will check back in tomorrow.
[Nexus 10 Original Android Development] Khaon:
Reading your logs I could find out the reason why it was not working on your device.

The TWRP 2.8.1.0 blkid built-in fails at recognizing the userdata's filesystem partition type... since I was using latest one, well, I was not having this issue. I changed anykernel2 script to use another binary(the one I was using actually on kitkat) to identify partitions's filesystem. I just flashed the same twrp than yours( so the one I compiled heh) and I didn't anymore the encryption screen. Data was never mounted as it was expecting it to be ext4.
[Nexus 10 Original Android Development] b1g.p0ppa:
Did you upload a new zip for the 12-10 kernel yet? Thinking you may have I downloaded it again and it still did not work. Since the file is named the same as yesterday I thought maybe you did not upload an update but the timestamp on it at mediafire is the same time as your post so I thought maybe you did.

Attaching recovery.log just in case you need it.

EDIT: flashed twrp 2.8.2.0 official and still won't boot. recovery.log2.txt from that attempt also attached.
[Nexus 10 Original Android Development] Khaon:
I have just uplodaed again the zip's archives and tried it out before on my twrp 2.8.1.0, it boots.
[Nexus 10 Original Android Development] b1g.p0ppa:
Confirmed! Thanks Khaon! Worked with both your 2.8.1.0 and official 2.8.2.0. Staying on your 2.8.1.0 because it starts so much faster than official recovery.
[Nexus 10 Original Android Development] Khaon:
Good, didn't expect internal blkid to fail us like that :P. At least now, it seems we have a fully working solution for partitions schema's.

So people can format with f2fs any partitions they like.

---------------------------

PA Gapps for lollipop are available

Beside that, overall, is there any significant performance improvements between formers releases and latest ones?

Now most of the build is being built with O3.

Also to notice, Apollo has been replaced by a new application : Music.

It forces portrait instead of allowing landscape, I removed that.
[Nexus 10 Original Android Development] b1g.p0ppa:
*format any partition as f2fs and afterwards re-install anykernel zip. fstab gets generated during kernel according to how partitions are formatted. Otherwise you can't boot. Verified :silly:
[Nexus 10 Original Android Development] Xodus83:
Hey I tried flashing kt-twrp and now I am stuck in fastboot and when I select recovery, restart bootloader, or start it reboots right back to fastboot. Any suggestions ? Thanks
[Nexus 10 Original Android Development] Khaon:
Flash my twrp 2.8.1.0 or the latest official one.

fastboot flash recovery x.img

will do
[Nexus 10 Original Android Development] frontalot:
12-12 kernel works great. The only issues I'm having are:

1. CPU speeds are unavailable in aero tweaker

2. GPU speeds and voltages are unavailable in aero tweaker

Other than that, your kernel with F2FS and FIOPS makes my Nexus 10 fly.
[Nexus 10 Original Android Development] Khaon:
There are no support for gpu over clock however you should be able to access voltage and cpu clock speeds.

Are you running 2.0.0?
[Nexus 10 Original Android Development] frontalot:
Yes, and CPU frequencies show "unavailable." I can adjust them on the 11-26 kernel.
[Nexus 10 Original Android Development] tavocabe:
I think CPU clock speeds don't stick after you turn off the screen.
[Nexus 10 Original Android Development] Khaon:
Indeed just noticed. It is because of powerhal driver setting max speed to 800mhz on turn off and 1700 on screen on will take a look at that

You can add manually a sysfs entry by adding its path .but cpufreq is broken when turning off will need to fix that

BTW I am using 2.10 beta you can grab it from its xda thread .

There is a link into settings that redirects you to it
[Nexus 10 Original Android Development] foxymyeung:
Great ROM & F2FS Support!

Wow.. with F2FS, this ROM + Kernel really flies!! Definitely brought some new life to my N10.

One thing that'd be great if you could fix is the bluetooth function. I regularly like using my bluetooth keyboard/cover on my N10, so it kinda sucks I can't use that function at this time.

On a random note, I'm not sure I'm a fan of the new lollipop format on the N10 because of the wasted real estate...
[Nexus 10 Original Android Development] necropuppy:
Digging the latest kernel w/ the cm12 build on f2fs fast as hell. Scored almost 29k in an tutu with stock kt conservative gov and fiops... However still having the Bluetooth crashing issue. I had to freeze the Bluetooth sharing app.
[Nexus 10 Original Android Development] Khaon:
I will tomorrow make a build with default settings to see if the problem comes form the ROM itself or the compilation
[Nexus 10 Original Android Development] Khaon:
BTW, you never could get into kt-twrp interface?
[Nexus 10 Original Android Development] ericp2:
strangely enough, i could at the beginning, as i did all the conversion work using kt-trwp. i had since then flashed a new CM nightly, still using it, but then this recovery "stopped" working for a completely unknown reason! very odd in the end, as i don't see how this could happen since the recovery partition never gets written doesn't it? unless some configuration flags are saved across sessions, and some were not properly stored?

Possible explaination: i think i had done a single CM update, using cyandelta. in it's updater script, i see:

package_extract_dir("recovery", "/system");

and further:

set_metadata("/system/etc/install-cm-recovery.sh", "uid", 0, "gid", 0, "mode", 0544, "capabilities", 0x0);

but the script never invokes install-cm-recovery.sh.... so it should not matter.

btw i always have to edit this script now, especially removing the line

package_extract_file("boot.img", "/dev/block/platform/dw_mmc.0/by-name/boot");

as this forces to re flash the f2fs aware kernel (and xposed) everytime i update cm, which is overkill.

This is done easily enough :

sed -i 's/^package_extract_file("boot.img".*/ /' updater-script
[Nexus 10 Original Android Development] Khaon:
I ll check around unless ppl do not want to use kt twrp anymore xDD
[Nexus 10 Original Android Development] Khaon:
Is this what you want?
[Nexus 10 Original Android Development] b1g.p0ppa:
First off, your TWRP 2.7.1.0 is working fine on my manta.

I had no issues with exfat. The reason I switched to it from fat32 it is because my tarball wouldn't grow past 4GB and I thought I remembered that was a fat32 limitation. TWRP 2.7.0.5 mounted exfat usb-otg no prob and I have Usb Mass Storage Watcher installed which must have mounted it for me when booted into android.

My next challenge is android 4.4.4. From what I can tell, the boot.img contains the fstab.manta so if I don't want to wait for a ktmanta 4.4.4 update I can research injecting a F2FS'ed fstab.manta into my ROM's default boot.img. Do you know if that is all that needs to be done? I found this thread http://xdaforums.com/showthread.php?t=2319018 that could help me do it if that's all that needs done.
[Nexus 10 Original Android Development] Khaon:
check post above I sent, isn't what you wanted?
[Nexus 10 Original Android Development] b1g.p0ppa:
We must have been writing at the same time. If that supports F2FS and the boot.img provides the proper fstab for F2FS for /data and cache, then YES, I would love to have that! I would love even more for you to PM me the location where I could get fresh nightlies that also support F2FS but I would understand if that needs to stay private.
[Nexus 10 Original Android Development] Khaon:
here you ktmanta supporting 4.4.4

Mediafire updated with the kernel using lastest google's source!! Seems to boot on lastest nightly since it did work for me :D. I ll need to upload soon my own sources heh!
[Nexus 10 Original Android Development] b1g.p0ppa:
I don't have any reason not to continue using kt twrp. In my mind it would be most compatible with ktmanta and F2FS efforts. I flashed it back after testing your 2.7.1.0 because I like the splash screen better :silly: and because I've already used it to back up and restore data.
[Nexus 10 Original Android Development] Khaon:
[MENTION=3721939]b1g.p0ppa[/MENTION]

Tell me if you are encountering any issues! There is also some folder for debugging it is located here : /sys/kernel/debug/f2fs/ , although I haven't looked into it so far, so I do not even know if informations from there could be reliable!

Also I found a git with some port for android, however, in the meantime samsung made a 3.4 branch of f2fs, but who knows this port might be even more stable, need to be tested!
[Nexus 10 Original Android Development] b1g.p0ppa:
No issues! Sorry I took so long, ran a new kt twrp backup before applying latest Omni nightly + your kernel. Everything working great! Thank you so much!
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=1536797]khoan[/MENTION], pls check your PM.

EDIT: Don't try that. Error executing updater binary when flashing.
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION], please check your PM again. I found (and fixed!) the problem I was working on.
[Nexus 10 Original Android Development] ericp2:
loop on wake

hi,

i can't be sure wether it's due to f2fs, or to kernel itself, but i am experiencing more and more frequent issues when turning the device on. i have attached a logcat, meaning that the device is not fully crashed but stuck in a loop.

I had tried flashing minimal gapps before, it seemed it help, but i think the problem may be located in the cpu director code. i had it set to interactive, then to performance. (I/O scheduler set to deadline)

the only way out right now is a reboot. i am afraid that eventually, flash memory will start crapping out if this continues.

can you take a look?
[Nexus 10 Original Android Development] Koopa777:
Hey [MENTION=4577448]Khaon[/MENTION], does your tool work for other variants? I was going to start using it on my hammerhead to convert ROMs to f2fs-all. Thanks!
[Nexus 10 Original Android Development] Fidelator:
I'm confused, will there be additional steps whenever I wish to install a ROM if I switch to F2FS?
[Nexus 10 Original Android Development] b1g.p0ppa:
First of all you'll need this thread's TWRP to do anything with F2FS.

If you switch just /data and /cache to F2FS then you'll need to flash this thread's kernel after flashing every ROM.

If you decide to also switch your /system partition to F2FS then you'll need to use Khaon's PC tool to modify the ROM .zip file prior to flashing it and then of course also flash this kernel after flashing the modified ROM .zip.
[Nexus 10 Original Android Development] Fidelator:
Will I notice any kind of performance improvement by switching just /data and /cache to F2FS?
[Nexus 10 Original Android Development] b1g.p0ppa:
I certainly did. I ran that way for a couple of days. I felt /data and cache on F2FS was a larger perf boost than running /system on it was.
[Nexus 10 Original Android Development] Khaon:
Update !!

If you are speaking about others devices I am afraid it woud not. For example many QCOM device got this path for the userdata partition : /dev/block/platform/msm_sdcc.1/by-name/userdata whereas our is /dev/block/platform/dw_mmc.0/by-name/userdata . The tool I code was done realy quickly but I could do a universal tool for converting update-script no matter what would be the device.

[MENTION=4188572]Fidelator[/MENTION]

Two minutes of googling :

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

http://www.xda-developers.com/tag/f2fs/

So as you can see under certains circomstances the gain is realy impressive, if you want some other material I can post some Samsung conference files with more figures , explanations & facts.
[Nexus 10 Original Android Development] frontalot:
CPU frequencies still not working even with Aero beta. Also, anyway we can modify the throttle temps?
[Nexus 10 Original Android Development] Lamba92:
First I would really like to say thank you for this awesome tweak! A new life to my N10 with lollipop stock :)

I have just few, let's say beginner, questions to ask! By mistake, with the latest official TWRP, I changed the file system of the cache and data partitions without even formatting. How is that possible? Do exist a conversion ext4->f2fs without formatting (yes I know I'm noob :P)?

When I did this of course most of the things where not working. After a wipe it all went right and now I play hearthstone without a lag :)

There only one bug bothering me; it was present even with stock kernel: the connection stop working even if it says connected, but now is a lot more frequent. Disabling and enabling back the WiFi seems doing the trick, but it's bit annoying.

Last but not least, what are the benefit from changing system partition too in f2fs? Can I do it without wiping /system partition (like I did before for cache and data)?

Thank you again for your awesome work, hoping I'm not bothering you too much ^^
[Nexus 10 Original Android Development] benjmiester:
I too have a noob question. If it's going to wipe my entire internal storage, won't I lose the kernel, rom file, and gapps that I need to flash after converting since they'll be on my tab's storage when I'm in recovery to do the F2fs conversion in?
[Nexus 10 Original Android Development] Lamba92:
The kernel is stored inside /system, so install it, then wipe the internal storage. Moreover the latest TWRP supports MTP while in recovery, so feel free to wipe what you want and then transfer the kernel. If you have MTP drivers really messed up, like i do, just push them trough ADB, but you'll have to disable MTP interface in TWRP
[Nexus 10 Original Android Development] lepa71:
"14. Push ROM to tablet with adb" this is how you will re-upload rom, gapps and kernel to your tablet after formating.

[MENTION=4577448]Khaon[/MENTION]

Can I use your kernel with RASTAPOP 5.x with F2FS?

Thanks
[Nexus 10 Original Android Development] Lamba92:
And that's ok with CM, but how with the stock rom? what do i flash to install 5.0.1 stock?
[Nexus 10 Original Android Development] lepa71:
You will have to find a stock rom that supports F2FS and this kernel.
[Nexus 10 Original Android Development] Lamba92:
Ok, but where do I get a flashable .zip stock rom? The only way i know is to use the official .img and flash it from bootloader. Does this erase the file system and format with ext4?

PS: i'll try CM12 btw :)
[Nexus 10 Original Android Development] lepa71:
you are asking question at the wrong place. Look in "Nexus 10 Android Development" section or ask your question in QA section.
[Nexus 10 Original Android Development] Khaon:
Updated the kernel, fixed the frequencies being overridden by the rom, switched to anykernel2 solution to make the kernel universal once again.

Rom:

powerHAL: reworked the driver to prevent overriding user's CPU freq speed to 1.7GHz.

powerHAL: reworked the driver to break early on screen interaction if the current cpu governor is not interactive

build:clang: compile the rom with Ofast instead of O3 ( since this flag enables ffast-math, it violates IEEE, thus it may bring instability or decrease in performance, report weird behavior.

Kernel:

ext4 updated to 3.4.105

frandom in replacement for random and uradom

thermal throttling: squashed @ktoonsez thermal algorithm (syfys entries located at /sys/devices/system/cpu/cpufreq/cput_attributes)

various cherry-picking from 3.4.105 kernel and from linux kernel upstream(include among other lz4 up to date, various arm patches, few patches

Anykernel:

Full switching to anykernel2 solution by osmosis:

patch the fstab upon flashing the zip package accordingly to your partitions' file systems

post-init script added to tweak vm,io,sched,...

You should now, could you try and report?
[Nexus 10 Original Android Development] DroidRevenge:
Downoloading...

i will report back ASAP.

Any suggestion about flashing procedure or just flash over?
[Nexus 10 Original Android Development] Khaon:
I just noticed frandom was breaking the wifi, already re-uploaded a fixed kernel, please reflash if you have broken wifi.

About flashing procedure, just flash the zip. If you are running cm12, you won't have any issue, I hope the kernel is universal now for any roms( in case you are using smthing else).
[Nexus 10 Original Android Development] DroidRevenge:
F**K!!

just flashed all, ROM and kernel, i wish it was the one patched 'cause i have problem with nexus 10 and my PC here in office...

cross fingers!
[Nexus 10 Original Android Development] Khaon:
Well the rom comes with cyanogen's default kernel and mount /data with f2fs.

So if you have f2fs for /data you can just stay with cyanogen's to get the patched one.
[Nexus 10 Original Android Development] DroidRevenge:
No f2fs.

flashed old ext4 that was already into download folder, then download again patched one, then... cross fingers again...
[Nexus 10 Original Android Development] frontalot:
Thanks for the 19-12 version. I can now set CPU frequencies and thermal throttling.
[Nexus 10 Original Android Development] Khaon:
Are you using ktweaker or Aero with custom sysfs entries to edit thermal params?
[Nexus 10 Original Android Development] frontalot:
Aero with custom entries. I don't have my tablet in front of me at the moment, but they are somewhere under the CPU branch.
[Nexus 10 Original Android Development] Khaon:
That's I thought, well Aero is really nice, I will provide the dev a list of sysfs entries related to our kernel that aren't supported yet, so they will be natively:D.

-----------------------

Are there around still users having ktoonservative as default gov? I just have added support of generic input driver to add back touch boost behaviour!
[Nexus 10 Original Android Development] tavocabe:
That's great to hear, so now CPU frequencies are sticking after the screen goes off?... I'll need to flash it and see it myself! Thx
[Nexus 10 Original Android Development] lepa71:
Thank you. So far I haven't figured out if that ROM can be ran with f2fs.

Does any rom can be ran with f2fs and the only requirement is for the kernel?

Thanks
[Nexus 10 Original Android Development] necropuppy:
I still use that governor. What do you suggest though for the best battery life?
[Nexus 10 Original Android Development] Khaon:
The requirement is indeed the kernel supporting f2fs.

The only problem can be ramdisk related. That's why I switched to anykernel to make it dump the current rom ramdisk and patch its fstab accordingly to your partitions's file system.

So you should be able to use any rom out there on this device with f2fs as long you use a compatible kernel and ramdisk.

Also note that the fstab patching occurs when you flash my zip package, if you flash my zip package and then format to f2fs you will have to re install it again.

Well, if you tune it correctly according to your utilization it remains a good one. Just the touchboost cpu was missing.

I really like new faux123's intellimm, you should give it a try. Make sure to set up corrects tunnables or watch out the apps you are using.

Some apps, like tricksters fails at showing the correct sysfs entry formating thus it doesnt apply the correct value.

Aero Control, among others, does support all the tunnables of this governor.
[Nexus 10 Original Android Development] foxymyeung:
Thanks for this kick ass ROM!

I'm not sure if anyone else has run into this issue, but when I setup a second user profile account (since I like to share my N10 amongst the family), it seems that the touch input dies after I switch back from one user to the other user. So that I can no longer do anything with the device except long press the power to reboot. This is a repeatable occurrence.

Even if I have a primary user profile, switch to guest user, and then switch back to the primary user profile the pad will no longer be responsive to any touch input. Only the hard power keys work.
[Nexus 10 Original Android Development] Khaon:
Hello, don't know why I didn't think of it earlier. because cm12 is still not released officially, some components are broken.

However, your issue might not be code related but induced by my optimization .s

Example: in the beginning , compiling whole build with O3 was making Fc chrome.

I had to fall back to O2. And now O3 works fine for chrome.

So what we need is to identify if its code related or not and the easy part would be to compare ROM behavior with a reference one : the original.

I don't know how is compiled the other ROMs if there is out there such a thing. If not I will release one with default options and Google compilers.

If bugs dont occur on that version it means I need to look for which part fails and then force it to be compiled with less optimizations to make it stable.

However this won't most likely happen before one day or two gonna be busy until then.

EDIT : if somebody has two nexus 10 make yourself known lol.

Sent from my nexus 10
[Nexus 10 Original Android Development] Khaon:
Guest is working here but my build is 2112 I guess you are having an older one ? I am always most of the time one step ahead lol. Want to try always a bit before releasing

Sent from my nexus 10
[Nexus 10 Original Android Development] necropuppy:
I was having this issue. My second user would lag a lot then become unresponsive. It would happen randomly, Jack the cpu usage up to 100, without warning, but it would happen frequently and require reboots. I tried to look at the process overlay thing to see what was taking it up, but couldn't see anything. I had to to switch over to rastapop (with f2fs and your kernel). Working well so far.
[Nexus 10 Original Android Development] Khaon:
Just switched four times between two users and launching some web pages and then revert to the other one.

Had no issue so it is expected further releases won't suffer of it ... Will try and tell you when I all release next build if users are working .unless you prefer staying on your current ROM p

Sent from my nexus 10
[Nexus 10 Original Android Development] cubalibre832910:
the latest TWRP not show f2fs, there any workaround?
[Nexus 10 Original Android Development] Khaon:
My 2.8.1.0 sp does offi 2.8.2.0

Sent from my Xiaomi MI2s