yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] tobitege:
You should be able to connect to ADB when rom is booted up... enable MTP in Storage and in command line (e.g. Windows) use this after the FC:

adb logcat > mylog.txt

After a couple of seconds - if it is not terminating itself - hit CTRL+C and it should have created the log for you (in the folder you were or add a path to the file).
[Nexus 10 Original Android Development] Khaon:
He he no it is not a feeling it is more smooth. I work hard on optimizing modules. ( a module is simply a code on its own). We do have really nice cores and even now. Our cache is better than snapdragon 810 LOL.

So I am trying to force as many we can instructions to be excetuded by the SIMD.

However running floating operations on this processor won't assure the result will be precise! For shadow or animations you don't need computations to be precise ! Look here http://fr.m.wikipedia.org/wiki/Racine_carrée_inverse_rapide

But ! Of course some part of the sources code requires computations to be precise !!

I have removed and added few new modules to make their computation to be rnned on the co processor.

While our CPU can only understand an instruction of 32 bits long our neon processor instruction are 128 bits long!!!

So you can't fit let's say 27889075 + 6358997 on a single instruction... An integer us 32 bits long! But the neon co processor can ! But again doing soneed to be carefull . if I would enforce all computations on the neon it would damn unstable. So I am trying to compensate our GPU with the CPU co processor

Weird been on the releases I posted. No issues but sometimes dt2w bugging.( I know why but don't understand why heh)
[Nexus 10 Original Android Development] ronald_loulan:
Hi there, I searched around but didn't found any info on OCing the gpu.

And what's the max safe OC for cpu n gpu ya?

Btw thanks for this good kernel!
[Nexus 10 Original Android Development] ricco333:
Does anyone know which kernel release does not have Double tap to wake? In my case D2W makes the table unstable and I'm looking for the last release without it.

Thanks in advance, [MENTION=4577448]Khaon[/MENTION] you are the man, thanks very much!

Erik
[Nexus 10 Original Android Development] tavocabe:
Search a couple pages back.

You can disable that using a kernel tweaker app. I'm using kernel adiutor.
[Nexus 10 Original Android Development] ricco333:
I know it can be disabled, I have it disabled right now, but even disabled it is causing me problems that I don't have with the CM ROM kernel.

Erik
[Nexus 10 Original Android Development] drewski_1:
how do you know it's the DT2W? if you have logs, they might help Khaon troubleshoot / bug-fix
[Nexus 10 Original Android Development] ronald_loulan:
what I did in terminal:

su

echo off > /sys/devices/platform/mali.0/dvfs

echo 612 > /sys/devices/platform/mali.0/dvfs_upper_lock

echo 612 > /sys/devices/platform/mali.0/dvfs_under_lock

cat /sys/devices/platform/mali.0/clock

Current sclk_g3D[G3D_BLK] = 533Mhz

Possible setting : 720, 667, 612, 533, 450, 400, 350, 266, 160, 100Mhz

Did I did something wrong here??
[Nexus 10 Original Android Development] tavocabe:
I added the dvfs_upper_lock command to the 00firsties init.d file, so it is applied at boot. I just increased the limit but you can add dvfs_under_lock command also if you want a frequency to stay all the time.
[Nexus 10 Original Android Development] ronald_loulan:
I've added it in my 00firsties init.d file located at /system/etc/init.d/ and it works!

Thanks
[Nexus 10 Original Android Development] tathagatab:
I've been using the May 01 kernel; seems to be the last one without dt2w. It's stable & fast.
[Nexus 10 Original Android Development] ricco333:
Thank you very much! (already hit the button) that was the sweet spot! That release should be labeled stable, now everything works fine.

Erik
[Nexus 10 Original Android Development] coalee:
Khaon

The latest version (05/26) still has Google Play Service bug. When using apps that require GPS (Location set to accuracy, battery saver). The bug has been described here https://github.com/temasek/android_libcore/commit/4d46de25bdb6d3b8150612a49849e251dcfcb035

OptiPop has already been merged this fixed. Could you please re-compile the new build?

Cheers :)
[Nexus 10 Original Android Development] Khaon:
Nice!

I ll push a up to date build then. Expect it to be online by tmr.
[Nexus 10 Original Android Development] ronald_loulan:
Waiting for the new build... :D
[Nexus 10 Original Android Development] tathagatab:
[MENTION=4577448]Khaon[/MENTION]

Dear Khaon,

Any plan to add fast charge?
[Nexus 10 Original Android Development] Khaon:
Sorry I know I have said I will and I didn't have time to look into that . just curious why you want fast charge for ?

Eww I had little time and could not throw a build sorry
[Nexus 10 Original Android Development] tathagatab:
The N10 is a hungry beast, and the battery goes down too quickly when playing games or performing other demanding tasks. Fastcharge will top it up faster, I hope :)
[Nexus 10 Original Android Development] omnis:
Hey there, I am using this kernel with kali nethunter lollipop and I was wondering how/where to add modules for external wifi card support... specifically I am looking for support for the AWUS036H and the TL-WN722N. Any and all help greatly appreciated. I have tried modprobe ath9k to try and get the TL-W722N working as I believe that is the correct module and I get the following errors:

After entering "su" then "modprobe ath9k" in a terminal I get:

modprobe: chdir(3.4.67-khaon-kernel-00615-g3d34d89-n10): No such file or directory

If I enter a terminal and execute "su" then "bootkali" then "modprobe ath9k" I get:

libkmod: ERROR ../libkmod/libkmod.c:554 kmon_search_moddep: could not open moddep file '/lib/modules/3.4.67-khaon-kernel-00615-g3d34d89-n10/modules.dep.bin

Any ideas? Thanks in advance!
[Nexus 10 Original Android Development] ronald_loulan:
I would like to add that my N10 only take 1.5A from the original 2.0A charger...

Mayb fast charge could make the original 2A charger go 100%... ;)
[Nexus 10 Original Android Development] ericp2:
Optipop built from 2015/06/07

Hi khaon,

I have installed successfully this build. all seems to be running just fine. Incidentally, i had a strange crash on the previous version in chrome, when viewing youtube videos. the whole tablet would just freeze and reboot was necessary. this is not the case anymore. i am using included Kernel 3.4.67 as well. note however that i also cleared chrome cache, hard to say what did it in the end..

Thanks for your work.
[Nexus 10 Original Android Development] omnis:
Re: Kernel Audiutor

Kermel Audiutor causes constant reboots upon applying changes on boot. I would love for it to work properly it has great features, but they cause my Nexus 10 to freeze up and then reboot. Any ideas? Thanks.
[Nexus 10 Original Android Development] ronald_loulan:
I've been UV CPU n OC Gpu and is working fine...

Mayb ur setting had problem?
[Nexus 10 Original Android Development] b1g.p0ppa:
Are you overclocking? If so, you may need to bump up voltages for higher freqs. I had very similar issues before I realized my particular tab needed +25mV for each step above 1700MHz.

[MENTION=4577448]Khaon[/MENTION], better battery stats says something called "3-004a" is holding kernel wakelock. Any idea what that is? Doesn't show up in `ps` so I have no idea...
[Nexus 10 Original Android Development] Khaon:
3-004a is the kernel touchscreen driver. When doubletap is enabled this device doesn't go on sleep mode.
[Nexus 10 Original Android Development] andrologo:
latest updated kernel kitkat

Thank you Khaon for your work. What's the latest updated kernel for kitkat?:)
[Nexus 10 Original Android Development] Khaon:
Whaow no idea I don't even know if there are still kit Kat release on the drive. I don't think there are

Envoyé de mon One X en utilisant Tapatalk
[Nexus 10 Original Android Development] tavocabe:
Is GPU OC possible with this version?
[Nexus 10 Original Android Development] tathagatab:
No.
[Nexus 10 Original Android Development] EddyTeddy01:
Constant wakelock that I have no idea what it does but it prevents me from going to deep sleep. Just clean installed optipop ,no xposed. In the kernel wakelocks section of BBS called 3-004a.
[Nexus 10 Original Android Development] leninke:
That's the touch screen driver, when it's enabled this device doesn't go in sleep mode
[Nexus 10 Original Android Development] tathagatab:
And when it's disabled, the device becomes unstable :(

At least mine does.

That's why I've been sticking to the May 01 kernel, in spite of the many improvements introduced since then. Perhaps I'll come away from it if/when Khaon implements fast charge.
[Nexus 10 Original Android Development] joeski27:
Is this what causes the lock screen to come on and off every 15-20 seconds while the device is supposed to be in "sleep" mode? Because this seems like a dumb idea, as this will just drain the battery very quickly.
[Nexus 10 Original Android Development] tathagatab:
Dunno about that; I keep it in a cover, so who knows what happens when I'm not using it.
[Nexus 10 Original Android Development] tathagatab:
Hey, what's up? Why did the posts stop? Why no kernel update in 3 weeks? I hope Khaon is OK.
[Nexus 10 Original Android Development] tylerdurden83:
I have double tap disabled (doesnt work, and kernel audiutor confirms), yet this wakelock has 100% uptime.
[Nexus 10 Original Android Development] Khaon:
Indeed you are totally write and the culprit is none than myself ! I taught I included thenfix for this in the public release but I DID not... Expect it to be included on next build ... Tomorrow or ?Monday at worst.

You can however roll back to a former kernel !

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] tathagatab:
Welcome back, Khaon! :)
[Nexus 10 Original Android Development] ronald_loulan:
Rolled back to 2705 n 2aiting for the new kernel atm.. :D
[Nexus 10 Original Android Development] tathagatab:
Rolled back from what? May 27 is still the latest kernel, as far as I can see.
[Nexus 10 Original Android Development] tavocabe:
Lol, same here

[MENTION=4577448]Khaon[/MENTION], can we expect a kernel with GPU OC but without DT2W? I love the fluid UI but not so much the fact that you can't fully disable DT2W.
[Nexus 10 Original Android Development] Khaon:
It's online. From now on, releases will features dt2w disabled by default.
[Nexus 10 Original Android Development] tavocabe:
I don't know whats happening but I my tablet can't boot any of your newer kernel releases. Using Optipop, stock rooted and now Omni. Not using any patches/scripts/mods, just clean flash. Is anybody using these new versions with F2FS? I think that might be my problem but I don't want to re-format to EXT4 and have to backup all my storage. I can't get a logcat as I just see the splash screen looping.

EDIT: last working kernel for me -> UPDATE-AnyKernel2-khaon-kernel-manta-05-18-2015.zip (first one)
[Nexus 10 Original Android Development] tathagatab:
Same for me, although I'm on ext4, not f2fs. I can't even boot on my ROM's stock kernel (Chroma). The May 27 kernel works for me, though. Maybe it's got to do with fstab entries? Haven't tried formatting /data; could that solve my problem?
[Nexus 10 Original Android Development] leninke:
I'm on latest Chroma, just installed Khaon's latest kernel, until now everything works without problems.
[Nexus 10 Original Android Development] jsgraphicart:
I'm using Chroma and just flashed the latest build. Seems good so far. I'm just wondering, I saw it was mentioned that double tap to wake was disabled by default in the latest build. Does that mean it can be enabled or that it was removed all together? If it can be enabled, how can I do this? I installed trickster mod but don't see anything that refers to it.
[Nexus 10 Original Android Development] leninke:
You can use Kernel Auditor.
[Nexus 10 Original Android Development] jsgraphicart:
Thank you. That works
[Nexus 10 Original Android Development] ericp2:
I had the same, when i tried flashing the kernel only. worked fine when i flashed optipop rom, which contains the kernel
[Nexus 10 Original Android Development] tavocabe:
anyone using latest kernel with cyanogenmod and f2fs?
[Nexus 10 Original Android Development] tylerdurden83:
I flashed the latest kernel over the june 7 and wiped cache, yet it bootloops. Do I really have to wipe system every time????
[Nexus 10 Original Android Development] Morvie:
I do 26.06, everything works fine.
[Nexus 10 Original Android Development] tavocabe:
what the hell? f2fs? really? I don't know what I'm doing wrong.... just flashed the factory images, tried the kernel with that and didn't boot, tried with omni, clean flash, didn't boot, now with cm12, same :confused::crying:
[Nexus 10 Original Android Development] glockman4519:
Is there a way to set this kernel "selinux permissive" permanently? I have used the app from XDA but it's not a permanent fix and would rather have it set this way natively. If not, I can surely keep using the app, I just figured I would ask. I thought that this kernel used to be this way but again, I could be wrong and may be thinking of another kernel.

"Chance Favors the Prepared"
[Nexus 10 Original Android Development] tobitege:
Yes, [MENTION=4577448]Khaon[/MENTION] recently removed the permissive flag, not sure why.

https://github.com/Khaon/android_ke...mmit/ff6882b0fc257b1a208666fec39c911fe2a33284
[Nexus 10 Original Android Development] Khaon:
I had permissive set just because of v4a, now that I have included the SEpolicies to fix that, I put back enforcing. Also, permissive is like a full hole, I am not really looking towards security on this device but I guess the average user want something secure.

You can set easily a permanent fix with a init.d script.

Take a look over there
[Nexus 10 Original Android Development] tobitege:
[MENTION=4577448]Khaon[/MENTION]: perfectly fine, I understand. :)
[Nexus 10 Original Android Development] Slyfer17:
Hey [MENTION=4577448]Khaon[/MENTION]

It has been a long time since my last post bere. How are you?

I've seen that your last build is a CM 12.1... Is something changing? Do you remember the old times before Optipop? Eheh :P
[Nexus 10 Original Android Development] OmniSlyfer:
Uhmm it seems I've user the wrong account :p
[Nexus 10 Original Android Development] Khaon:
Sadly As I said

So for Now I am asking myself either I ll build be building Temasek's unoficial cm-12.1 OR AOSP's master branch.

Honestly Temasek's team does/did incredible work: it is not just a simple fork of cm.
[Nexus 10 Original Android Development] b1g.p0ppa:
Difficult choice. Temasek seems a very smart team and has developed very nice and useful features. But it is another band of Ronin, no? Open source developers in it for purposes of enjoyment, education and camaraderie. Will they last? Is it important that they do? AOSP, on the other hand, is 'sensible shoes', they are not full of whistles and bells but they can be counted on to be there for years to come. I don't have time tonight to test your temasek build but likely will soon. Thanks again for any and all efforts you put forth in keeping our devices running optimal and current code!
[Nexus 10 Original Android Development] Khaon:
well seems temasek has been around since 2012 :p
[Nexus 10 Original Android Development] tavocabe:
anyone using latest khaon custom recovery 2.8.7? not working for me but can't use official as it cannot see internal storage, because f2fs?
[Nexus 10 Original Android Development] drewski_1:
what is not working?

i'm using 2.8.7.0 and it's working fine (for installs / wipes - haven't done backup/restore). not sure if it's the "latest" i'll need to see if the date matches, when I get back home.

did you try to redownload / install? or revert to Khaon 2.8.6.0?
[Nexus 10 Original Android Development] drewski_1:
I downloaded my 2.8.7.0 on 6/23. The current is dated 6/25. Not sure on the changes.

I'll try and upload the file I have later (can't seem to do it in Tapatalk)

Sent from my Nexus 10
[Nexus 10 Original Android Development] 2Kings:
Yeah he started when he had a lg 2X, then had a S3, and now a note 3.. he never gave up, even through the bad times..

An awesome guy! :good:
[Nexus 10 Original Android Development] tavocabe:
I tried flashing using fastboot and flashify but couldn't get it to load. Reboot-> reboot recovery-> google splash screen-> google splash screen-> android boots. Same using "reboot recovery" from bootloader. I'm starting to think my nexus 10 is faulty as I can't get any of the latest khaon's kernel to boot. I already did a clean flash, even flashed the factory images
[Nexus 10 Original Android Development] tathagatab:
Same with me here. Latest kernel I can boot is May 27. If your device is malfunctioning, then so is mine.
[Nexus 10 Original Android Development] Khaon:
Hello may you please state your rom ?

There should be no conflicts but I had one with installing one of my package on top of something else than optipop or cm( installed new distros to try them out).
[Nexus 10 Original Android Development] ericp2:
Hi, if problem seems related to Mali crash, doesnt it make sense that those crashes are related to compilation flags, i.e. A15 configuration? I have the same kind of problem with partial freezes, and I would be happy to try a kernel with current f2fs code, but with the original KT kernel flags. Let me know! I currently use f2fs for cache and data only.
[Nexus 10 Original Android Development] b1g.p0ppa:
Running KTManta_F2FS-11-07-2014-ALLF2FS with OmniROM for a couple weeks now with no lockups to speak of. Using interactive/sio though as I did get a couple SODs with intelliactive/bfq.

[MENTION=4577448]Khaon[/MENTION], I would happily test an updated ktmanta with latest f2fs commits if you'd like. ;)
[Nexus 10 Original Android Development] Khaon:
Was kite busy lately with my exams.

Merged lastest commits from f2fs's dev branch.

changelog

Added ThunderKat kernel with lastest f2fs commits

KTmanta :

Updated to linux 3.4.103

EXT4:

6c32d73 ext4: Add support for FIDTRIM, a best-effort ioctl for deep discard trim

ARM

ARM: be strict about FP exceptions in kernel mode

ARM: add support for kernel mode NEON

ARM: crypto: add NEON accelerated XOR implementation

ARM: move VFP init to an earlier boot stage

F2FS:

f2fs: should clear the inline_xattr flag

f2fs: use macro for code readability

f2fs: introduce need_do_checkpoint for readability

f2fs: fix incorrect calculation with total/free inode num

f2fs: skip if inline_data was converted already

f2fs: remove rewrite_node_page

f2fs: avoid double lock in truncate_blocks

f2fs: prevent checkpoint during roll-forward

f2fs: add WARN_ON in f2fs_bug_on

f2fs: handle EIO not to break fs consistency

f2fs: check s_dirty under cp_mutex

f2fs: unlock_page when node page is redirtied out

f2fs: introduce f2fs_cp_error for readability

f2fs: give a chance to mount again when encountering errors

f2fs: trigger release_dirty_inode in f2fs_put_super

f2fs: don't skip checkpoint if there is no dirty node pages

f2fs: avoid bug_on when error is occurred

f2fs: fix to recover inline_xattr/data and blocks

f2fs: clear FI_INC_LINK during the recovery

f2fs: fix the initial inode page for recovery

f2fs: make clear on test condition and return types

f2fs: should convert inline_data during the mkwrite

f2fs: fix typo

KTManta should be stable, so give it a try and provide feedbacks :D
[Nexus 10 Original Android Development] CazeW:
Thanks, will give both the ThunderKat and KT a try and report back if I can reproduce the crash.
[Nexus 10 Original Android Development] CazeW:
Well, I've now tried both the ThunderKat and the KTManta kernel. The result is that I can make KTManta crash every time with just making TitaniumBackup redo all my backups. This doesn't happen with ThunderKat and I haven't managed to crash it a single time yet. I used interactive/cfq on both kernels when testing. I also confirmed that the crash on KTManta wasn't caused by the mali driver as the same warning appears with ThunderKat as well. Logcat didn't show anything this time either and I didn't manage to pull dmesg as the system completely locked up, but in the previous dmesg I posted and in the attached last_kmsg, you can see that there are a lots of these kind of messages:

"F2FS-fs (mmcblk0p9): recover_data: ino = 10790, recovered = 8 blocks, err = 0"

which don't appear at all in the ThunderKat dmesg. So the crash could be (and probably is) related to F2FS but it's strange that your Omni kernel and ThunderKat so far work flawlessly with the same drivers.

PS. The new F2FS commits did indeed seem to make the difference in SQLite performance in AndroBench as ThunderKat posts almost double the scores compared to your Omni kernel.
[Nexus 10 Original Android Development] Khaon:
Omni kernel has very old sources, but the lastest ktmanta & thunderkat i posted are running the same driver. Hm I thought it might have been related to bfq cgroup but it seemes it doesn't. Well glad at least for now there is one kernel running f2fs that is stable.

I ll try to find out the reason of the unstability of ktmanta, until then , I recommend anyone to use thudnerkat, I ll post soon omni kernel but I don't really think it is worth but I ll do it anyway.

I wonder if mounting with the option "errors=recover" would help but need a full format hehe..;
[Nexus 10 Original Android Development] CazeW:
And of course craigacgomez decided to update his kernel right after you posted the F2FS version. :D

EDIT: And for some reason I can't get ThunderKat_ALL_F2FS to boot while CACHE_DATA works fine. Could be a problem with converted ROM though.
[Nexus 10 Original Android Development] zamula:
I would be happy to test the latest ext4 version of ktmanta if you get a chance to build it. Thanks!
[Nexus 10 Original Android Development] Khaon:
Yeah my bad thunderkat ramdisk was mounting system partition as ext4. Corrected
[Nexus 10 Original Android Development] Khaon:
I just uploaded lastest thunderkat. Omnirom's kernel with lastest f2fs drivers is avaliable also.
[Nexus 10 Original Android Development] CazeW:
Thanks for the quick update, working great so far. And a heads up to others that the ThunderKat ROM itself doesn't seem to like having /system converted as F2FS, as it doesn't allow you to login to play store (I think craigacgomez said there was some issue with SELinux).
[Nexus 10 Original Android Development] Khaon:
Btw I advice using ext4 as fs for /system partition. There is no writting in the /system partition and ext read speed is higher than f2fs. However, f2fs formater is faster than ext's
[Nexus 10 Original Android Development] b1g.p0ppa:
Both valid points and you have convinced me. I would also add that having to modify the ROM's updater-script prior to flashing to support /system as F2FS is extra work and a good opportunity for error. I'm going back to ext4 /system right now.
[Nexus 10 Original Android Development] ericp2:
thunderkat f2fs

Hi khaon,

I have been running this kernel (cache+data) for 3 days now, with absolutely not a single crash,slow down, weird behaviour etc... i must also say that Antutu benchmarks went up to 23800, the highest I have ever seen on my Nexus 10 (for what it's worth..).

Thank you for providing f2fs for this kernel!
[Nexus 10 Original Android Development] b1g.p0ppa:
Wear leveling

Continuation of the ext4 vs. f2fs conversation.

Wear Leveling.

The thought occurred that since I flash a nightly ROM every day, then /system is formatted fresh every day and writes presumably begin again at the start of the partition. I would think this would mean that those blocks see drastically more IO than those at the end.

I'm going back to F2FS for /system (didn't see much perf diff on ext4, btw) and am going to check the TWRP setting to use rm -rf instead of formatting in hopes of leveraging F2FS' wear leveling code. Though the storage will probably outlast my time with the tablet, this seems like a reasonable idea.
[Nexus 10 Original Android Development] David 617:
Anybody try this with Vanir?