yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] yamaha_wins:
Im on twrp 2.6.3.1 I must say that I havent converted to F2FS.... on the blissrom thread everyone was saying use the khaons kernel to get the lastest release of the rom to boot. I had clicked a link that took me directly to the kernel download. after attempting to install both together it wouldnt boot. so here I am now. I was able to just reflash a version of blisspop and get my tablet running again. but would still like to get the newest version working. I'll look into the F2FS and see if thats somethings I could benefit from. are all kernels/roms going to the F2FS conversion?

I did convert the file system, and updated twrp. I was able to get the latest release of blisspop installed and booted. the system does seem somewhat laggy.
[Nexus 10 Original Android Development] Khaon:
No you made me remind that official/stock TWRP was lacking some binaries so I added them into my own custom TWRP.

This must be the reason why it was failing with an official one.

This issue can be avoided if I add the missing binaries you find in the official version.

Format your partitions to F2FS and then install my kernel.

Not all ROM however support system partition formated with f2fs

I assume you got to install my own TWRP you can find on my former google drive foldeR.
[Nexus 10 Original Android Development] Bastlwastl2010:
[MENTION=4577448]Khaon[/MENTION]

I see you have a new kernel for Lollipop, compiled 10.28

In the init-scripts there is no 99khaon_gpu_controls script.

It is no more supported? Or can i take my own to oc the cpu?
[Nexus 10 Original Android Development] Khaon:
Hello, indeed there are new builds. [MENTION=4631882]yamaha_wins[/MENTION] [MENTION=4135807]_Raziel666[/MENTION]http://xdaforums.com/member.php?u=4631882

The only new thing is that error with official twrp recovery seems to be resolved.

I think you must have downloaded the MM kernel, the lollipop does still include the gpu script.
[Nexus 10 Original Android Development] Bastlwastl2010:
Nothing from the commits since 10.22 to 10.28?

I download it this morning, the 10.28 release for Lollipop in "Old Release"

Jet there a two build...one on "Old Release" from this morning and one new from this afternoon.

I think i download to early.....:angel::angel:
[Nexus 10 Original Android Development] Khaon:
Only f2fs sources were updated.
[Nexus 10 Original Android Development] tathagatab:
Hi, a few questions.

I can't seem to find the 28 October kernel in your uploads. Did you withdraw it?

Will the Marshmallow kernel work on Lollipop?

There doesn't seem to be a decent Marshmallow release for manta yet. Do you know of any? This one seems to have many flaws: http://xdaforums.com/showthread.php?t=3222477
[Nexus 10 Original Android Development] Khaon:
Hello,

someone said the MM build was working on lollipop. However if you want all features using MM build is not advised.

I have uploaded back lollipop build if you want them.
[Nexus 10 Original Android Development] SKORPiO1975:
Doe this kernel support adjustment of microphone levels? Skype sounds like Crap on N10. I wonder if someone figured out a way to fix that.
[Nexus 10 Original Android Development] Subrad5446@aol.com:
Hi guys. I'm still on 4.4.4. Which kernel version can I download? Can't seem to find that info anywhere. Thanks!
[Nexus 10 Original Android Development] Khaon:
Weird I had never issues on TS or skype while using the embedded mic.

My kernel does"nt include any tweaks/patch for the mic

Try looking Ktoonsez's kernels.
[Nexus 10 Original Android Development] Subrad5446@aol.com:
Nah that's who I used to use. Now I'm on f2fs. I'll just upgrade to lollipop. I was waiting for xposed and its official now so cool.
[Nexus 10 Original Android Development] elgar:
Is this kernel going to work with rooted stock android 5.1.1 without changing to f2fs?
[Nexus 10 Original Android Development] ilciumbia:
Sure!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 10 Original Android Development] elgar:
I am on stock rooted android 5.1.1. Flashing this kernel resulted in a "google" bootloop. So, is this kernel only for f2fs?
[Nexus 10 Original Android Development] ilciumbia:
I haven't played around with Ext4 in a long time, but I think I remember that, in earlier times, I was using that kernel without F2FS... However I may be wrong, so I ask for someone's confirmation...

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 10 Original Android Development] Khaon:
What kernel did you flash over what rom ?
[Nexus 10 Original Android Development] elgar:
deleted

---------- Post added at 11:11 PM ---------- Previous post was at 11:01 PM ----------

I flashed the latest kernel from this thread: UPDATE-AnyKernel2-khaon-kernel-manta-09-12-2015.zip. I flashed it over stock Android 5.1.1 LMY48X.
[Nexus 10 Original Android Development] lepa71:
[MENTION=4577448]Khaon[/MENTION]

Is there a compiled kernel for MM?

Thanks
[Nexus 10 Original Android Development] elgar:
yes, look in the download folder
[Nexus 10 Original Android Development] drewski_1:
it's not only for F2FS.
[Nexus 10 Original Android Development] yamaha_wins:
Does changing the file system break xposed from working? I changed the file system, flashed the new bliss ROM ,installed khaons kernel. Now I can't get xposed to install on my nexus 10 running 5.1.1
[Nexus 10 Original Android Development] Khaon:
Can you check on your system's partition free space ? I don't know if bliss rom's flashing packages are block based or not. You should have an internal storage of 800 mb
[Nexus 10 Original Android Development] mikeharris:
DELETED
[Nexus 10 Original Android Development] Aleq:
How is it running for you, guys? I switched from stock and despite nicer storage performance, the actual experience is horrible. It's freezing more and more. It runs well but only if I keep restarting the device after every bigger game. For instance it's impossible to run anything bigger after Minions Paradise game. We share the tablet with my wife and every switch, we do the reboot. Without that you can even hear the freeze for several tenths of a second as the sound goes bzzzzzzz.
[Nexus 10 Original Android Development] ilciumbia:
Yes, same for me! I am keeping the default kernel provided with temasek's build, as using this kernel is out of the question... I don't know why but I think it has to do with memory management... I asked some time ago about editing the minfree parameters, but I got no reply... [emoji20]

Inviato dal mio Nexus 10 utilizzando Tapatalk
[Nexus 10 Original Android Development] Aleq:
Does that temasek's kernel support f2fs? Do you have a link to that, please? I was thinking of formatting the storage back to ext* and going back to stock kernel, but I'd prefer to stay with f2fs
[Nexus 10 Original Android Development] ilciumbia:
Yes it does. I am not sure there is a separate link, but if you download the full temasek ROM it is in there...

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 10 Original Android Development] Khaon:
link will be back realy soon.

the kernel that comes with my temasek bulds supports f2fs but has less features than the standalone one. However, I prefer using the temasek one.
[Nexus 10 Original Android Development] ilciumbia:
[MENTION=4577448]Khaon[/MENTION]:

[quote name=khaon]Do you mind , please, repost your suggestion so I can review it ?

[/QUOTE]

Sure, here it is. I am still using the old lollipop build, but, no matter what kernel I try, it is not possible to customize the minfree parameters, neither via kernel adiutor nor with other apps. Since adjusting the minfree parameters is the best way I found to improve Android responsiveness, I am wondering if this limitation is intrinsic to manta or it is due to kernel and/or Rom...

Thanks!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 10 Original Android Development] Khaon:
Sure, here it is. I am still using the old lollipop build, but, no matter what kernel I try, it is not possible to customize the minfree parameters, neither via kernel adiutor nor with other apps. Since adjusting the minfree parameters is the best way I found to improve Android responsiveness, I am wondering if this limitation is intrinsic to manta or it is due to kernel and/or Rom...

Thanks!

Inviato dal mio Nexus 5 utilizzando Tapatalk[/QUOTE]

Oh I see , well sorry to disappoint you but look at this !

Kernel-side LMK has been disabled, do you think it has to do with the fact you can't custom your LMK parameters ?

I guess it has ? From my little knowledge, LMK is mostly ROM sided ?

If you tell me you can't eidt the LMK than it has to be kernel-side with this config disabled.
[Nexus 10 Original Android Development] jegormeister:
Is the download link working? It is not for me.
[Nexus 10 Original Android Development] drewski_1:
in his ROM thread Khaon said the host is not available anymore and that he would be reverting back to Google Drive. may be the same as the "Former Downloads Link" in the OP, but that does not yet have the latest stuffs
[Nexus 10 Original Android Development] ilciumbia:
Oh, wow! So you are telling me that LMK is not implemented in the kernel? Of course this can be the reason why I cannot edit minfree parameters... But the real question is: without LMK, how does memory management work? I think we have a problem here!

Inviato dal mio Nexus 10 utilizzando Tapatalk
[Nexus 10 Original Android Development] rgao007:
Which version should I use for 5.1.1 (CM12.1)?
[Nexus 10 Original Android Development] Aleq:
Khaon's Kernel 11-22-2015 flashed over latest manta system image solved the issue completely. Thanks a lot!

UPDATE-AnyKernel2-khaon-kernel-manta-11-22-2015.zip - but I guess newer versions will work as well
[Nexus 10 Original Android Development] lynnux:
By latest manta system image do you mean 5.1.1? How is it running? I haven't been very happy with mm, mainly because of the stutters/jitters when scrolling, thinking of going back to lp with this kernel..
[Nexus 10 Original Android Development] Aleq:
Yes, 5.1.1, the latest stock image from https://developers.google.com/android/nexus/images. It works well in my opinion. Especially after the suffering with previous version of the kernel, this feels like heaven.
[Nexus 10 Original Android Development] Medizinmann:
Where can I get the 11-22-2015-kernel?

I only found older builds...

Greetings

Medizinman
[Nexus 10 Original Android Development] vitorugo-8:
this kernel works with cm13?
[Nexus 10 Original Android Development] Bastlwastl2010:
Yupp
[Nexus 10 Original Android Development] vitorugo-8:
so, i changed system, cache and data to f2fs. Then i flashed CM13 with gapps and everything works fine. Then i flashed this kernel and it changed the system to ext4. What's wrong? Can i just change the system again to f2fs? i'm kinda noob so apologise me
[Nexus 10 Original Android Development] Bastlwastl2010:
kernel support cache and data f2fs, no system

System must be on ext4. This is no handicap, f2fs bring advantage in write speed, and to system you only write while you flash...
[Nexus 10 Original Android Development] vitorugo-8:
thanks again... in one hour you saved me 3 times!

and about the kernel, is it working properly with cm13, or the stock cm kernel is better ? i've tried it but seemed to laggy
[Nexus 10 Original Android Development] RichieXX:
Where can i download the newest kernel for MM? The download link on first post are not working.
[Nexus 10 Original Android Development] glockman4519:
You have to use the link that says "former download link". Or the old Google drive download link.

"Chance Favors the Prepared"
[Nexus 10 Original Android Development] RichieXX:
Thank you. I was of the opinion that there are already a newer version than 2015-10-18.
[Nexus 10 Original Android Development] EddyTeddy01:
I don't want to come across as self-entitled, but i sure do hope this kernel continues development. Being the only kernel left for Manta, it's very important to Manta's rooting community. If it's done being worked on, thank you Khaon for making an AMAZING kernel for us and letting us utilize the wonders of f2fs!
[Nexus 10 Original Android Development] Khaon:
Hello, sorry to say things like that, but I was busy then a bit pissed as I lost my server( that was building and hosting my releases) as my friend stopped his subscription :p.

However, I was still active.

I built a new kernel. It is downloable over there :

main new features are the following :

[LIST]
[*]updated the kernel to the android kernel branch: includes the folllowing :
[LIST]
[*]3221ff9 FROMLIST: x86: mm: support ARCH_MMAP_RND_BITS.
[*]379b6cb FROMLIST: arm: mm: support ARCH_MMAP_RND_BITS.
[*]37f4acd FROMLIST: mm: mmap: Add new /proc tunable for mmap_base ASLR.
[*]aa4ef4d BACKPORT: mm: /proc/pid/smaps:: show proportional swap share of the mapping
[*]fb828ff net: inet_diag: zero out uninitialized idiag_{src,dst} fields
[*]e0cfbaf BACKPORT: arm: don't open-code ptrace_report_syscall() (part deux)
[*]8ce3733 UPSTREAM: ARM: Fix the world famous typo with is_gate_vma()
[*]66a6182 BACKPORT: ARM: make vectors page inaccessible from userspace
[*]ac46c41 BACKPORT: ARM: move signal handlers into a vdso-like page
[*]69a303a UPSTREAM: ARM: 7475/1: sys_trace: allow all syscall arguments to be updated via ptrace
[*]ac85270 BACKPORT: ARM: 7474/1: get rid of TIF_SYSCALL_RESTARTSYS
[*]9f6b13d BACKPORT: ARM: 7473/1: deal with handlerless restarts without leaving the kernel
[*]3b8b622 BACKPORT: ARM: 7472/1: pull all work_pending logics into C function
[*]6050e61 UPSTREAM: arm: don't open-code ptrace_report_syscall()
[*]119ee49 UPSTREAM: arm: bury unused _TIF_RESTORE_SIGMASK
[*]ddc2dcc UPSTREAM: arm: remove unused restart trampoline
[*]84bd57d BACKPORT: arm: new way of handling ERESTART_RESTARTBLOCK
[*]004c6bd UPSTREAM: arm: if we get into work_pending while returning to kernel mode, just go away
[*]ff989c8 BACKPORT: arm: don't call try_to_freeze() from do_signal()
[*]c8d7c65 UPSTREAM: arm: if there's no handler we need to restore sigmask, syscall or no syscall
[*]e27c853 UPSTREAM: arm: trim _TIF_WORK_MASK, get rid of useless test and branch...
[*]ec6759e UPSTREAM: arm: missing checks of __get_user()/__put_user() return values
[*]dbaf2b4 BACKPORT: ARM: allow kuser helpers to be removed from the vector page
[*]4da8bd4 BACKPORT: ARM: update FIQ support for relocation of vectors
[*]3a77f4b UPSTREAM: ARM: use linker magic for vectors and vector stubs
[*]de33b90 BACKPORT: ARM: move vector stubs
[*]22bcffb UPSTREAM: ARM: poison memory between kuser helpers
[*]76748c0 UPSTREAM: ARM: poison the vectors page
[*]132e348 ANDROID: android: base-cfg: disable CONFIG_SYSVIPC
[*]6e8f47c UPSTREAM: include/linux/poison.h: fix LIST_POISON{1,2} offset
[*]0b82ef1 UPSTREAM: proc: actually make proc_fd_permission() thread-friendly
[*]f7f420f UPSTREAM: proc: make proc_fd_permission() thread-friendly
[*]f63f8d6 __ptrace_may_access() should not deny sub-threads
[*]5dbbefb ANDROID: exec_domains: Disable request_module() call for personalities
[*]925b1f5 BACKPORT: pagemap: do not leak physical addresses to non-privileged userspace
[/LIST]
[*]f2fs updated to the revision upstream !
[/LIST]

link !!!
​
[Nexus 10 Original Android Development] lynnux:
The new kernel has Marshmallow in the name, is it okay to use with Lollipop?
[Nexus 10 Original Android Development] vidx31:
Anyone has kernal built on 08/18/15? looks like that is best one in term of stability and performance. I couldn't find it on google drive. Would appreciate if someone can share. Thanks.
[Nexus 10 Original Android Development] jddnoob:
Also don't have any problems with .103 so far. Using with latest omnirom home build (allf2fs)

Gesendet von meinem GT-I9300 mit Tapatalk
[Nexus 10 Original Android Development] necropuppy:
THUNDER cat 103 working like a charm. I see the ktconservative gov. But the ktweaker app was acting weird. Basically missing the files to monitor the cpu freq. Should I use that or trickster?
[Nexus 10 Original Android Development] Khaon:
ktweaker is designed to be working with kt's kernel. You can use ktweaker, however, for UVing, gov and io sched control. So using trickster or ktweaker is basically the same
[Nexus 10 Original Android Development] ericp2:
thunderkat .67 and .103

Hi khaon

I had .67 on my tablet for a few days, all working perfectly.

I switched to .103 about three days ago and now, I am starting to see similar issues as with ktmanta, although no crash yet:

- sometimes slow wake up from deep sleep (bfq, interactive) ie 5s or more

- sometimes weird keyboard behavior , like long lags

Let me know if you want more information.
[Nexus 10 Original Android Development] tavocabe:
little issue

So, the non-waking up screen was a kernel bug or a rom bug? I read back a few pages it happened when using omnirom, I had the issue and also using omni. But just to make sure, so I can change one or the other. I had this problem maybe 4 or 5 times the last two weeks. Running omnirom, kt kernel and twrp, f2fs data and cache, art runtime. Btw, thanks for your awesome work!
[Nexus 10 Original Android Development] Khaon:
Switch to thunderkat for now. .67 seems to be stablest.
[Nexus 10 Original Android Development] ericp2:
Hi, my keyboard issue is probably not related to kernel... And slow occasional wake up from deep sleep is not much of an issue!

I am keeping .103 for now, because I haven't had any crash with it, and battery performance is fine as well. Cheers, and thanks again!
[Nexus 10 Original Android Development] Khaon:
Would be very appriciated if you you(or anyone) can provide logs, I might be able to find out what is slowing down.

You can take a look at that topic to get usefull logs. Another way, is just to install logcat apk on the play store they back up among other any logs to sd/internal storage.
[Nexus 10 Original Android Development] Khaon:
New build on line :D

Seems to be the smoothest and fastest kernel I released so far!

Happy flashing , don't hesitate to report to me any logs in case of bugs.

kernel can be found here.

This kernel works any partition table as long they are formated with f2fs or ext4 !

I also compiled the new twrp recovery who those who are interested in that.
[Nexus 10 Original Android Development] nigelhealy:
Working, in this combination, no other combination worked for me:

Installed your F2FS TWRP recovery e.g. my linux command line sudo fastboot flash recovery twrp-unofficial-2.7.1.0-f2fs.img. Annoying isn't that no other Manta recovery has this? I tried stock TWRP 2.7 and 2.8 and Cyanogen Recovery, none had the f2fs format :(

reboot bootloader, then enter recovery

wipe, and wiped EVERYTHING (when I tried to not it would not boot)

then I wiped and altered filesystem for /cache, then I wiped and altered filesystem for /data, both to f2fs. Not doing /system as my ROM below isn't f2fs.

then I installed Thunderkat ROM (I guess ANY rom would work as I had not f2fs /system, but I tried CM 11 nightly, would not work, but I was trying many things it might be I tried Thunderkat's kernel rather than this f2fs version, not sure).

installed your kernel i.e. khaon_kernel-13-09-2014.zip the odd thing is Thunderkat's own kernel states it supports f2fs itself but it doesn't boot, boot animation stays. This modified kernel though does work

I now got a bit of f2fs now at least for /cache and /data.

The Nexus 10 seems about the same performance, anecdotally, but in an hour's use or so it is still stable (as was TWRP's non-modifed recovery and Thunderkat's non-f2fs modified kernel).
[Nexus 10 Original Android Development] Khaon:
You can use twrp 2.8.0.0 I provided however you can boot on any recovery without having to flash it. sudo fastboot boot xxx.imh would do!
[Nexus 10 Original Android Development] Khaon:
Just repack boot.IMG with a correct fstab
[Nexus 10 Original Android Development] nigelhealy:
Did you use Slimkat without any modifications or with mods and if so how?

---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------

.. oh is that all.

Detailed steps please.
[Nexus 10 Original Android Development] Khaon:
The boot IMG contains the ramdisk and the kernel image . ramdisk is loaded in the ram at boot. Among other you will find the fstab in it. I guess thunderkat is mounting all partition withnext4

Edit : Take a look here https://github.com/xiaolu/mkbootimg_tools it works like a charm
[Nexus 10 Original Android Development] nigelhealy:
Thanks. To show my ignorance, I couldn't even find a download button anywhere for those scripts so I copied+pasted into a file and chmod +x it.

I unpack the CM11 nightly for Manta and I see two fstab files, they have really complicated tuned ext4 mount lines to modify to f2fs.

It's looking like a lot of effort for what probably won't work.

Surely CM and other ROM makes should just make an all-f2fs ROM? The method to just change for /data and /cache isn't that complicated but its getting hard to hack a ROM for f2fs.....
[Nexus 10 Original Android Development] Khaon:
You just have to unpack the boot.img, then correct the fstab.manta, and then repack, and you are done.
[Nexus 10 Original Android Development] CazeW:
Thanks for the new kernel and recovery. Could you update the TWRP recovery to 2.8.0.1? There seems to have been a bug causing graphics glitches and touch issues in 2.8.0.0.
[Nexus 10 Original Android Development] Khaon:
Yeah I already wanted to do it, but unless I am blind source aren't available yet.
[Nexus 10 Original Android Development] CazeW:
You're right, I seemed to have jumped the gun. :)
[Nexus 10 Original Android Development] nigelhealy:
So I was up to 1am trying to get /system to f2fs using both CM-11 nightly ROM and Thunderkat ROM. Failed. :rolleyes:

I used the jar file converter

java -jar convert2F2FS.jar

It did run, no complaints, it did make ThunderKat_manta-KTU84Q-20140824-F2FS.zip and cm-11-20140805-SNAPSHOT-M9-manta-F2FS.zip

I then in your modified TWRP recovery did the steps which should work

wipe all (to be sure)

wipe and format /cache , /data and /system to fs2fs

install zip - did the f2fs ROM then your kernel khaon_kernel-13-09-2014.zip

reboot system

What happened was it simply didn't get past the Google with the unlock symbols screen, no boot logo, no boot loop, which is the same as if no OS installed at all.

Ideas? :fingers-crossed:

Also, I see the post which says that ext4 read performance is better than f2fs read perfomance and /system is read-only hence the FASTEST setup is what I can get get working which is /data and /cache as fs2s and /system as ext4 and no modified ROM (just your kernel). Is that fair true?

I'm currently working with /data and /cache f2fs, your kernal and Thunderkat, seems stable from just a few hours use. I can't tell if its faster. It has hints at instability though, in that if USB connect and MTP files across they seem to stutter and actually run SLOWER. With /data on ext4 I'd get write about 11-13MB, with f2fs the write would appear iniitially a little fast 14-15MB then halt, stutter then resume about 7MB/s. I rarely copy via MTP usually Wifi and it peaks about 8MB/s so I'm not expecting a problem there.

So far, I don't see a performance gain but see cause for concern.
[Nexus 10 Original Android Development] drewski_1:
I don't think so, but backup and give it a whirl? ?
[Nexus 10 Original Android Development] Khaon:
I think it shoudl work lollipop.
[Nexus 10 Original Android Development] cdsbj6508:
I get a bootloop with the latest update.
[Nexus 10 Original Android Development] MrMarques01:
Same here on OmniROM
[Nexus 10 Original Android Development] glockman4519:
I just want to quickly thank you "Khaon" for continuing building a kernel for this device and sharing.

"Chance Favors the Prepared"
[Nexus 10 Original Android Development] Khaon:
I am currently running the last build on my master branch build, is it omni 6.0 ?

Well thx you, but I was for some time away :P while ppl were expecting some answers eww.
[Nexus 10 Original Android Development] MrMarques01:
It's Omni 6.0.1 (latest homemade build). Apparently more users are having issues according to the omni thread. Next I'm going to try flashing your kernel using the custom recovery you posted and report back.