yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Original Android Development] Fidelator:
Switching to thunderkat kernel seems to hace fixed the sudden hang ups and reboots that I had been suffering with kt, a shame as I love my UVing
[Nexus 10 Original Android Development] Khaon:
new beta builds online

Same here, didn't want to start debugging KtManta, will most likely do it when I got more time. I have no ideas if the ktmanta's unstability comes from linux patches or something else. So I guess we will found out. original proper ktmanta is freezing/unstable aswell.

So for anyone who wants, you can try and download one of the two new thunderkat beta builds : here are the changelogs. Let me know if you can reproduce bugs, will trace this time the errors if needed. Would be very appreciated if anyone can try reproducing bugs, you can also boot the kernel through fastboot, it allows you not to flash before testing)

Thunderkat 67 :

Merge remote-tracking branch 'common/android-3.4' into thunderkat ( google's branch. Kernel updated from 3.4.39 to 3.4.67)

thunderkat : defconfig updated

Makefile : ccache enabled

ARM:

ARM: crypto: add NEON accelerated XOR implementation

ARM: be strict about FP exceptions in kernel modee

ARM: move VFP init to an earlier boot stage

ARM: add support for kernel mode NEON

FS :

f2fs: truncate stale block for inline_data

CPUFREQ :

CPUFREQ : ktoonservative gov added

cpufreq: added VOLTAGE CONTROL and some tweakage on OC/UC

OC/UC is LIVE (2.1Ghz) ( last commits thanks to [MENTION=4325945]ktoonsez[/MENTION])

Block

bfq : tunnables tweaked for nand drive

block: bfq: add Early Queue Merge (EQM) to BFQ-v7r5 for 3.4.0

block: introduce the BFQ-v7r5 I/O sched for 3.4

block: cgroups, kconfig, build bits for BFQ-v7r5-3.4

ThunderKat 103 :

all commits above

Merge remote-tracking branch 'stable/linux-3.4.y' into thunderkat ( kernel updated from 3.4.67 to 3.4.103)

You can download them here
[Nexus 10 Original Android Development] ericp2:
Hi khaon

I installed 3.4.67 thunderkat yesterday, all working fine. I am running interactive/bfq with it. Please note though I think one zip name is wrong, because I thought I was downloading 103... But it actually contained 67...
[Nexus 10 Original Android Development] Fidelator:
103 working great so far, thanks man.
[Nexus 10 Original Android Development] tathagatab:
Hi,

I'm on Chroma latest build.

I'm not sure the booting problems are due to your kernel. I can't boot my ROM's native kernel (which is probably the vanilla aosp kernel) either; I have to flash your kernel from May 27 before I can boot the device. So I think my problem is due to some quirk that's common to your kernel and the aosp kernel. I wonder what it could be.

Thanks for your interest.
[Nexus 10 Original Android Development] Koopa777:
Are you formatted f2fs?

---------- Post added at 10:26 PM ---------- Previous post was at 10:20 PM ----------

Try TWRP 2.8.6.X. 2.8.7.0 was borked for me on hammerhead, it would do as you said, and instead of entering recovery it would boot to android.
[Nexus 10 Original Android Development] tavocabe:
Yeah, I had to revert back, cant live without recovery. I really had no need to update just wanted to try to boot a newer kernel than the one I'm using, thought maaaybe the recovery was the problem but now I will never know :p

Btw, I'm using TWRP 2.8.7.0 on my Nexus 5 without problems, the MultiRom one though.
[Nexus 10 Original Android Development] tathagatab:
Nope, never touched the filesystem.

And for what it's worth, twrp 2.8.7.0 is working fine for me.
[Nexus 10 Original Android Development] tavocabe:
Hi Khaon, is it possible to add MultiRom compatibility to our Nexus 10 kernel?
[Nexus 10 Original Android Development] drewski_1:
Can you point me to the N10 Multirom thread?

Would love to give it a try (use it on a couple of my other devices), but I can't find it :(
[Nexus 10 Original Android Development] tavocabe:
I don't think there is one. Some kernel developer has to merge the kexec-hardboot patch but it may be too difficult as no one has done it. Maybe because of the exynos processor.
[Nexus 10 Original Android Development] drewski_1:
Interesting. I thought the patch was the easy part and more porting the MR framework, but I'm no Dev.

Sent from my Moto X
[Nexus 10 Original Android Development] Khaon:
I don't know if it could be easy or not, I can have a look !

Sorry didn't see your messages, just noticed them !

I have uploaded a new kernel build.

Here is the changelog

gpu:mali:dvfs:set gpu boost sysfs interface in msecs instead of usecs
mali:dvfs:enhanced gpu voltage control
defconfig:enabled f2fs crypto
f2fs:fix compilation errors when crypto is enabled
KEYS: Add invalidation support
f2fs: fix the prototype of find_target_dentry
Revert "vfs: make it possible to access the dentry hash/len as one 64-bit entry"
f2fs: import upstream sources
defconfig:compile nightmare governor
cpufreq:add nightmare governor drivers/cpufreq/Makefile
dt2w: enhancements to prevent the device to be all the time awake when dt2w is disabled
Merge remote-tracking branch 'common/android-3.4' into HEAD
Fix incorrect conflict resolution in "vfs: Add setns support for the mount namespace"
proc: fix build broken by proc inode per namespace patch
Revert "android: drivers: Fix build broken by android debugfs fix."
android: drivers: Fix build broken by android debugfs fix.
proc: Allow proc_free_inum to be called from any context
proc: Usable inode numbers for the namespace file descriptors.
proc: Fix the namespace inode permission checks.
proc: Generalize proc inode allocation
vfs: Allow unprivileged manipulation of the mount namespace.
vfs: Only support slave subtrees across different user namespaces
vfs: Add a user namespace reference from struct mnt_namespace
vfs: Add setns support for the mount namespace
consitify do_mount() arguments
do_add_mount()/umount -l races
fs: introduce inode operation ->update_time
VFS: Comment mount following code
VFS: Make clone_mnt()/copy_tree()/collect_mounts() return errors
get rid of magic in proc_namespace.c
get rid of ->mnt_longterm
vfs: umount_tree() might be called on subtree that had never made it
brlocks/lglocks: API cleanups
brlocks/lglocks: turn into functions
lglock: remove online variants of lock
Revert "vfs: umount_tree() might be called on subtree that had never made it"
android: drivers: workaround debugfs race in binder
Revert "android: drivers: workaround debugfs race in binder"

Mainly I have updated the f2fs source to upstream revision. For those encrypting their tablet, you should have more performance as f2fs crypto is included now in my sources !

To those who want to tweak gpu controls, you can edit the 99khaon_gpu_controls.sh file in the archive (patch folder).
[Nexus 10 Original Android Development] Khaon:
I have uploaded a new kernel package that fixes some bug when applying custom voltage to the gpu.
[Nexus 10 Original Android Development] Khaon:
Ok I havea bit of updated the OP,could anyone tell me if they are facing issiues with my kernel package? and also confirm thatgpu overclocking works to them ?
[Nexus 10 Original Android Development] Khaon:
If anyone is facing issue withgpu control make yourself known please
[Nexus 10 Original Android Development] Bastlwastl2010:
With Kernel Audiutor and latest CM12.1 no GPU settings

Edit

Which place do you mean? OP? Nothing found to fix this problem for me.
[Nexus 10 Original Android Development] b1g.p0ppa:
You must edit the /system/etc/init.d/99khaon_gpu_controls file and change the 533 value on the line:

echo 533 > /sys/devices/platform/mali.0/dvfs_upper_lock;

to another frequency as listed in the line:

gpu_table="100mhz:875 mV 160mhz:900 mV 266mhz:900 mV 350mhz:950 mV 400mhz:1000 mV 450mhz:1050 mV 533mhz:1100 mV 612mhz:1150 mV 667mhz:1200 mV 720mhz:1250";

Mine reads:

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

and I'm quite happy with it. Works well, [MENTION=4577448]Khaon[/MENTION]! No issues thus far.

Easiest way is via the init.d functions within kernel audiutor. It's a bit technical, but then so is all of this, no?
[Nexus 10 Original Android Development] b1g.p0ppa:
[MENTION=4577448]Khaon[/MENTION], is it possible to update TWRP with newer f2fs? I don't seem to be able to boot into recovery after installing this latest kernel. Could it have upgraded my f2fs past what your 2.8.7.0 twrp can read? Getting "too many open files" errors throughout /tmp/recovery.log. And twrp never fully loads, just reloads splash screen every couple of minutes.

Edit: Not sure what went on but I went ahead and fastboot flashed userdata then re-formatted f2fs in twrp. Back on track.
[Nexus 10 Original Android Development] tathagatab:
Since you asked, I'll mention once more that I've been unable to boot any of your recent kernels after May 27, so that's what I'm still using. This latest kernel is no exception.

For what it's worth, I also can't boot my ROM (Chroma) unless I flash your May 27 kernel. I'm baffled. Do you have any clue?
[Nexus 10 Original Android Development] Khaon:
I had a damn bootloop entering each time to twrp too, I just formated back to ext4 internal storage and then all of a sudden everything was ok , but I can build a newer latter, I saw they introduced some newer commits. I could report this too on irc, I ll go tell them
[Nexus 10 Original Android Development] Khaon:
I would like you to gimme your adb logcat and adb shell, canyou do that ? enable debugging and allow your device for it( a prompt will appears)
[Nexus 10 Original Android Development] Khaon:
I am open a pull request to add to kernel audiutor the path relative to our device... No one ever has enter those :P
[Nexus 10 Original Android Development] Bastlwastl2010:
I will test it....Its not so technical, and hey....this is a developer forum :). I think edit init.d scripts is a basic requirement....

With CM12.1 i think there is one more problem, latest nightly 08.14 wont boot with the 06.26 nor with the 08.13 kernel.

08.08 works. Will test it with the next nightly 08.15
[Nexus 10 Original Android Development] Khaon:
I put a newer build of twrp on my drive.
[Nexus 10 Original Android Development] Bastlwastl2010:
No more install problems on CM 12.1 08.16

To edit the init.d have no change to me, facing the GPU Values in kernel Audiutor
[Nexus 10 Original Android Development] drewski_1:
I'm running the latest Chroma with your Kernel. F2FS.

With 6/26 kernel, I got a 31k Antutu (1800 + performance gov)

With 8/14 kernel, I get a 21k Antutu ? 2d & 3d scores look comparable. It's the CPU scores that are low. Like it's not running both cores or something.

Latest Temesek is comparable to the Chroma + 6/26, so seems to be just the standalone kernel?

I did notice the installer is a little different. It didn't say the formats of the partitions and some other stuff that the 6/26 installer put into the TWRP terminal window.

Sent from my Lollipop TF700T
[Nexus 10 Original Android Development] Khaon:
Temasek builds comes with my kernel by default. Yesterday I made 31k but with default settings(interactive @1.7ghz).

Sources and compiler are the same for the standalone and the ROM, hm.

Indeed the output doesn't display anymore the messages, I need to review that as it should display what you were saying. I have updated the installer for the people having trouble flashing.

For now the only thing I can think of doing ****ty thing is this : https://github.com/Khaon/AnyKernel2/blob/manta/ramdisk/sbin/post-init.sh

What you could do, if you can, is to delete this file, flashing again the package, and try again a benchmark!

I have upload a new revision of the anykernel: the message are back, I have removed few tweaks from the post-init.sh and let the important ones. Now the flashable package is setting the same parameters that you would get from the Temasek ramdisk of mine.
[Nexus 10 Original Android Development] glockman4519:
Thank you once again for the updated kernel. It is greatly appreciated.

"Chance Favors the Prepared"
[Nexus 10 Original Android Development] Bastlwastl2010:
Sorry i am no programmer, just a user, but i see no open or closed pull request in Github

https://github.com/Grarak/KernelAdiutor/pulls

https://github.com/Grarak/KernelAdiutor/pulls?q=is:pr+is:closed
[Nexus 10 Original Android Development] Khaon:
Yeah I haven't done it because currently kernel audiautor support only the gpu Max freq, selecting the GPU governor and some other voltage support for qcom chips.

Here the driver support setting a min and max freq. Setting the voltage for each freq steps and also setting the thresholds for each freq steps.

I think it smarter to use my init.d script as many explorer allows you with root access to easily edit from the tablets. Or you can simply edit from the compuetr

Hm that I answer you the problem is flashing my ROM over a former build: it will override the current script with default values.

I can however open a pull request for GPU Max freq as I did to support dt2w

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] Bastlwastl2010:
At the moment i unpack the kernel on the pc. Edit the init.d repack and flash it :)

Its more comfortable as to do it on the tablet :cowboy:
[Nexus 10 Original Android Development] Bastlwastl2010:
[MENTION=4538400]kahon[/MENTION]

Do you have update the TWRP again? (Today?)
[Nexus 10 Original Android Development] Khaon:
Yeah To include latest f2fs tools

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] Izeltokatl:
For those using F2S does it really make a significant difference, just curious.
[Nexus 10 Original Android Development] Khaon:
beside telling you to check benchmarks, I have been for too long running f2fs to actually tell you if I can notice a change.
[Nexus 10 Original Android Development] tathagatab:
Hey,

Your August 18 kernel is working for me! Before this, the last one I could boot was the May 27 kernel. I don't know why the interim kernels wouldn't boot, but this one does, and I'm happy ?

What did you change between the previous kernel and this one? What is common between this one and the May 27 kernel that the interims didn't have? Maybe we can get a clue from that.
[Nexus 10 Original Android Development] Fidelator:
With the lastest build my N10 has been turning off during sleep, I'm using UV values that were stable in previous versions, I even increased voltage a little bit and it keeps happening, the governor doesn't make a difference, did you, by chance implement any kind of universal hotplugging during sleep? I remember this used to happen back when KTManta did that.

Its running fantastically otherwise.
[Nexus 10 Original Android Development] tavocabe:
So... this kernel is compatible with what roms? So far can't boot omni, stock,stock rooted, khaon cm12, remix os, formated cache/data to f2fs and without f2fs. Always get a bootlop in google splash screen. Last working kernel for me 5/18 (There are 2 in the folder, can only boot one). Using stock TWRP or yours. same result
[Nexus 10 Original Android Development] Khaon:
Latest flashable release reboots without reaching boot animation screen ? Is this reproducible with temqasek ROM ?

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] Syk69:
I tried flashing the latest release on latest temasek and it reboots after Google screen. The latest kernel flashes fine on previous temasek though.
[Nexus 10 Original Android Development] tavocabe:
Yes, didn't tried without f2fs though
[Nexus 10 Original Android Development] tavocabe:
What's your ROM/setup?
[Nexus 10 Original Android Development] Khaon:
I am gonna check on this as soon I am home(I.e. tmr.)

Envoyé de mon Nexus 10 en utilisant Tapatalk
[Nexus 10 Original Android Development] tavocabe:
I heard some kernel developers are having trouble using anykernel solution and are switching to release their kernel normally.
[Nexus 10 Original Android Development] tathagatab:
Chroma, twrp, ext4, Khaon's kernel.
[Nexus 10 Original Android Development] Khaon:
I am back home I'll look over the issue you reported.

I am gonna try flashing the kernel package over temasek's build.
[Nexus 10 Original Android Development] Khaon:
I have fixed the install. There is only one bug left: the patching messages are gone, as print to the output doesnt work anymore.

I have also updated f2fs source to the upsteram revision.
[Nexus 10 Original Android Development] kwmike:
Similar problem here. 9/2 temasek reboots over and over with 8/18 or 9/2 khaon kernel. 9/2 temesek runs fine with included kernel?
[Nexus 10 Original Android Development] Khaon:
Indeed it was my fault more or less : the kernel image that I included in 9/2 latest build was compressed with lz4 and the current anykernel2 solution doesn't support unpacking lz4 therefore it couldn't work !

I upload a new build btw that is working on the drive to be sure, there is also a new ROM build !
[Nexus 10 Original Android Development] Syk69:
Looks like the latest kernel has that bug again when woken up from deep sleep the touchscreen becomes unresponsive. When d2tw is disabled. Latest kernel boots fine with latest temasek though,thanks!

Edit: I enabled d2tw and then disabled and seems like touchscreen is responvie after deep sleep now.
[Nexus 10 Original Android Development] kwmike:
Still having google boot loop problem with 9/4 kernel. Heres what I've done.

1) Installed 9/4 temesek/khaon rom over working 9/2 temesek/khaon rom. Clean dalvik and cache. Runs fine.

2) Installed 9/4 khaon kernel over working 9/4 temesek/khaon rom. clean dalvik and cache. Recurring Google boot loop. ?

3) Reinstall 9/4 temesk/khaon rom, clean dalvik/cache. runs fine.

Are there any files that need to be removed etc?

Any help appreciated

Thanks
[Nexus 10 Original Android Development] Khaon:
Hello! When you are saying that you got bootloop I assume you are speaking of hardware reboot in a loop, not stuck with google animation ?

I have installed the 9/4 stand alone kernel over temasek 9/4 and I am not running into those issue, eww.
[Nexus 10 Original Android Development] kwmike:
Installing 9/4 kernel over 9/4 temesek rom

Thanks for looking into this.

Yes, hardware reboot ,

manta powered off, press poweron,

vibrate after 5 secs or so, word 'Google' displayed for 20-30 secs, vibrate again, screen black for 5 secs,

word 'Google' displayed again, repeat

only way out is to reboot to recovery.

The op references clearing /sdcard/Android/data. I have never had to do this before. Is this still suggested?

Appreciate your help!!
[Nexus 10 Original Android Development] Khaon:
No, this has nothing to do with that. It is tied with a ramdisk problem, like that my stand alone kernel would mess with the current one when dumping it.

I am gonna flash another ROM build and then over the standalone kernel.
[Nexus 10 Original Android Development] Khaon:
I have uploaded the standalone kernel with temasek's ramdisk on the gdrive. I just flashed a new ROM build and my kernel package. It is booting.

I guess somehow you must have somehow get a broken boot.img.

You can just flash the boot.img I put on the drive to boot.

To do so you can just

fastboot flash boot [path_to_your_file]

Or maybe use some kind of software such flashify or soemthing
[Nexus 10 Original Android Development] kwmike:
Thanks!

Before I do this I wanted to report that, by my testing, it seems that any Khaon rom (tested 3) will install and run ok, yet any khaon kernel (also tested 3) will not install without

looping as previously described. Should I proceed with the boot img install?

Edit:

I installed the boot img. No change.

Is there any other area you think needs to be cleared/changed?

Is it possible that you could put your modified kernel in the install for your rom? I particularly need the custom governors because I have

an old battery and the stock rom governors are very limited.

I appreciate your help! Thanks again!

Edit 2: rebuilt internal storage. Problem resolved. Not sure why?
[Nexus 10 Original Android Development] Khaon:
Hehe I find out the issue! AnyKernel simply doesn't support lz4 decompressing, I am adding this feature so this won't happen again !

So it is not something on your behalf, I am working on this now

EDIT

Honestly I did not think of the issue with lz4 compression. I have added a detection in the install script. Currently lz4 and gzip compressors are supported.

Flashing the package will display the compressor of the underlying kernel image.
[Nexus 10 Original Android Development] Khaon:
@kwmike and any other member who had the same issue(i.e. hardware reboots)

I have fixed the issue: AnyKernel2 wasn't supporting ramdisks compressed with lz4.

So now there won't be any problems with gzip and lz4 compressors.

Now AK2 for this device will compress with lz4 instead of gzip.

Sorry for slow fix :p
[Nexus 10 Original Android Development] kwmike:
You're the tops!!

Kudos!
[Nexus 10 Original Android Development] Khaon:
I noticed there was a little mistake when reading the dvfs table, so I corrected it and added a correct entry in the gpu script.

This is the content of the gpu script:

#!/system/bin/sh

#Must be a multiple of 25 mv
gpu_voltage_table="100mhz: 875 mV 160mhz: 900 mV 266mhz: 900 mV 350mhz: 950 mV 400mhz: 1000 mV 450mhz: 1050 mV 533mhz: 1100 mV 612mhz: 1150 mV 667mhz: 1200 mV 720mhz: 1250 mV";
#min and max threshold in percent before ramping up or down
gpu_dvfs_table="100mhz:0,55 160mhz:50,70 266mhz:60,79 350mhz:70,86 400mhz:80,95 450mhz:94,99 533mhz:98,99 612mhz:99,100 667mhz:99,100 720mhz:99,100";

echo 533 > /sys/devices/platform/mali.0/dvfs_upper_lock;
echo 0 > /sys/devices/platform/mali.0/dvfs_under_lock;
echo 350 > /sys/devices/platform/mali.0/dvfs_gpu_boost_freq;
echo 350 > /sys/devices/platform/mali.0/dvfs_boost_time_duration;
echo $gpu_voltage_table > /sys/devices/platform/mali.0/asv;
echo $gpu_dvfs_table > /sys/devices/platform/mali.0/dvfs_gpu_table;

So far you can thus edit the min and max cpu freq, the gpu freq for the touchboost and its duration, the gpu voltage table(values must be mutliples of 25 mV) and the min and max threshold(in percent) when to ramp up or down !
[Nexus 10 Original Android Development] RichieXX:
I have bootloop with kernel 08/09 on Chroma 09/09. With kernel 04/09 runs perfectly.
[Nexus 10 Original Android Development] Khaon:
Weird I just flashed the Chroma 09/09 build with the kernel I put on the gdrive it is working. Maybe did you download the 08/09 build from the Former build folder ?
[Nexus 10 Original Android Development] anjo88:
Im using this kernel and temasek rom but my nexus 10 is still buggy any special config that I can do to make my tablet faster?
[Nexus 10 Original Android Development] RichieXX:
I used the following:

https://www.androidfilehost.com/?fid=24052804347811909 and UPDATE-AnyKernel2-khaon-kernel-manta-09-08-2015.zip and can reproduce the bootloop. The older version from 04/09 works correct with Chroma 09/09.
[Nexus 10 Original Android Development] ricco333:
Same here, I just dirty flashed Chroma 09/09 with [MENTION=4577448]Khaon[/MENTION] kernel build 09/08 and everything is awesome, no bootloops, my apps are currently optimizing.

I would suggest to try a clean flash, or maybe a bad 09/08 kernel download, try re-downloading the kernel from the Gdrive.

Erik

---------- Post added at 11:36 AM ---------- Previous post was at 11:20 AM ----------

Latest Chroma, latest kernel.

Erik
[Nexus 10 Original Android Development] RichieXX:
OK. I try a redownload. Thanks
[Nexus 10 Original Android Development] bbubelis:
Still get bootloop

I tried the re download and clean flash of ROM and still get a bootloop with the 9-08-2015 Kernel. Please advise.

Thank you
[Nexus 10 Original Android Development] corumuk:
Bootloops for me on latest kernel. Coming from rastapop with previous khaon kernel.
[Nexus 10 Original Android Development] Khaon:
Is it possible for you to send me a logcat ?

Are those hardware boot loops or stuck at animation screen?

EDIT:

If it is a boot stuck at animation screen I have uploaded a new build that forces R/W for f2fs partitions, it might help.