AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
reserved for later
This kernel has been around for the Inc and the Evo. Now I'm bringing it to the N1 and the Desire!!
Great stuff, always nice to have more kernel choices
MOD : Can you post only Nexus One kernel on your post please (more readable)
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
allofusjw said:
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
Click to expand...
Click to collapse
I'm glad it's working for you, but that is strange... The only change I make to wifi from CM is undervolting it. And now that I think about it, I may have forgotten to bring that tweak over to the n1 and desire...
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
mr_raider said:
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
Click to expand...
Click to collapse
Versus the main CM kernel, this has unrestricted overclocking, HAVS, smartass, undervotling, sysfs interface and several other tweaks/improvements. I don't have a N1 and honestly dont know anything about the other kernels out there for it. The kernel started on the Inc and Evo, mostly around MIUI, and I was asked by a few people to bring it over to the N1 and Desire, so I figured I would post it up for everyone.
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
bryanchapman9999 said:
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
Click to expand...
Click to collapse
The on demand governor was removed to force the default to smartass (the default is usually set to on demand by the ramdisk and is not affected by setting the default in the kenrel), but the two are not similar. Smartass was built off the interactive governor.
As for the 128Mhz floor - that is something finicky about the smartass governor. It should drop to 128 on any other governor though.
Smartass Governor shows real potential...thanks for this!
what about the wonk?
From what I gather the wonk is due to something in CM7 kernel. I also noticed that it is absent from stock 2.3.3 and also absent from AOSP builds.
Has anyone tried CM7 with this kernel?
thanks for the N1 kernel.
I'll try ASAP.
I will try this kernel now, thanks for posting. New kernel cooks are always welcomed.
After about 18 hrs on this kernel, the results are pleasing.
Extremely stable on the Smartass Governor, which is surprising because I've had friends compile me kernels incorporating this governor, and the end result = unusable.
Battery life seems fantastic so far.
Clocked 128-998. No profiles.
Thank you again for this kernel.
Results on N1
I have been running this kernel for 24hrs at 128/1228 and it's been running great with smartass selected on my AT&T N1. I tried going even higher than 1228 but that causes it to crash immediately (I'm surprised it can even handle 1228.) Linpack is a little low at 23 compared to other kernels that can get up to 40. Quadrant also comes up behind at only 1051.
tried going at the highest setting & it crashed my N1 , BACK TO RESDTAR'S kernel .
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
phewizzo said:
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
Click to expand...
Click to collapse
same here, got some freeze
btw oc at 1267 without any crash
Related
TEAM n0ob FIRST RELEASE!
Ok after my OverClock How-To, I decided to play with overclocking and see what exactly can be gained from stock Max regulator Voltage (1.3v). I have found that at stock you can get up to around 1.13ghz. It is slightly faster than what pershoots kernel runs (38400khz).
As persiansown says, the standard stock voltage is set to 1275, and the regulator is maxed at 1.3v.
What Kind of gains will you see?
You will notice a difference in games like Asphalt, that use a lot processor. You will notice a decrease in battery life as well. Your linpack scores will vary from about 8.5-9.5 depending on your chip.
I have included pershoots undervolting, 21MB ramhack, and audio hack as well. Several optimizations, following in the footsteps of the Ivan/intersectRaven Kernels. (You could say we KANGED pershoot and just added two frequencies above his)
The frequencies in the kernel from 1113300-1152000 are at stock voltage(1.3v), and I have included the relevant source files. As such they "should" be safe. You never know though! The frequencies below this are Undervolted down to .925v!
This is using SLUB allocator and Deadline IO scheduler.
The recommendation of Team n0ob, is to use set CPU to set your phone to a frequency below 1.11ghz unless you need the extra power for something. Otherwise your battery life will suck and you will stress your processor for no reason.
This is confirmed working on CM-5.0.6-N1.
WARNING!!! THE LONG TERM EFFECTS OF OVERCLOCKING YOUR PROCESSOR CAN INCLUDE:
1. SHORTENED PROCESSOR LIFE
2. OVERHEATING
3. REDUCED BATTERY LIFE
4. BRICKED (IE DEAD DEVICES)
Mod edit: removed link, till source is link to kernel.
I ask that if you notice anything funny that you flash to a more tested kernel and notify this board immediately. This kernel is at stock voltage, but the increased speeds could have adverse effects. Please let us know if you notice any.
Team n0ob takes no responsibility for any damage that may occur to your device.
Credits: pershoot( thanks for the hard work), Kmobs (same), intersectRaven, Ivan (for beginning optimization trend), Rotohammer(experimental random/music/start fix), Cyanogen for awesome roms (whose source this is pulled from), chris soyars, and coolbho3000, Koush for the anykernel updater.
Team n0ob Testers: jlevey, DAMNiaTX Hell! (Thanks)
Following pershoot, I recompiled the Kernel with VFPv3 Optimizations.
resync to 2.6.33.3, old wifi drivers as everyone has problems with the new ones.
Lowered minV to 925. maxV is still 1.3. Voltages are increased to 1.3 only on the 2 frequencies above pershoots 1.113ghz. The other frequencies are undervolted similar to the Kmobs and or the Pershoot values.
Well, by "lowering processor life", how exactly long will my processor last? Does it depend on my phone? My uses? Im all in it for overclocking, and im very aware of said risk.. But processor life I'm not educated in..
Eclair~ said:
Well, by "lowering processor life", how exactly long will my processor last? Does it depend on my phone? My uses? Im all in it for overclocking, and im very aware of said risk.. But processor life I'm not educated in..
Click to expand...
Click to collapse
Not drastic. Not concrete figures but I've heard figures like instead of something like maybe 6 years, you may get 4-5 years. The processors are designed to last so long that even things that harm them typically still leave them outlasting the upgrade cycle of the user. It depends on the silicon in your phone as well.
Also, Gr8Gorrilla, does this include CM's latest commits from a day or two ago that fixes the pink cam tint issue?
No telling really. It shouldn't be much different than stock. However, as soon as I say that someone will install this brick the phone and blame me. So I am using it and I have a two year contract with T-mobile, I figure it should make it that far.
This is basically pershoots kernel plus 38400 khz. (pershoot in no way endorses this kernel). Take that for what it is worth. The top three voltages 1113, 1132, & 1152, are at stock voltage (1.3v).
I resynced my repo last night before compiling this.
Damn nice kernel is all I have to say
Gr8gorilla said:
I resynced my repo last night before compiling this.
Click to expand...
Click to collapse
Ok thanks! Definitely flashing this now!
Stock voltage is actually 1.275v. The processor is, however, rated to handle 1.3v (it was originally going to ship at 1.3v, but qualcomm decided to have it ship at 1.275v instead)
Gr8gorilla said:
No telling really. It shouldn't be much different than stock. However, as soon as I say that someone will install this brick the phone and blame me. So I am using it and I have a two year contract with T-mobile, I figure it should make it that far.
This is basically pershoots kernel plus 38400 khz. (pershoot in no way endorses this kernel). Take that for what it is worth. The top three voltages 1113, 1132, & 1152, are at stock voltage (1.3v).
Click to expand...
Click to collapse
I also am on a 2 year contract with TMobile, hopefully mine last that long also. Might as well flash this, blah..
persiansown said:
Stock voltage is actually 1.275v. The processor is, however, rated to handle 1.3v (it was originally going to ship at 1.3v, but qualcomm decided to have it ship at 1.275v instead)
Click to expand...
Click to collapse
I stand corrected. I should have said stock max regulator voltage. I will update the OP.
thanks Gr8gorilla
I'm definitely gonna try this out. I've been using intersect's and ivan's, just jumping back and forth. Good to see that there's another kernel out there to play with. Thanks Team n0ob!
Gr8gorilla said:
I have included pershoots undervolting, 8mb ramhack, and audio hack as well. The experimental Rotohammer fix for the headphone jack is compiled in as well, along with several optimizations, following in the footsteps of the Ivan/intersectRaven Kernels. (You could say we KANGED pershoot and just added two frequencies above his)
Click to expand...
Click to collapse
Does this have everything else that the default cyanogenmod's kernal has? (i just want to know if I am going to loose anything from cyan to this kernal)
INeedYourHelp said:
Does this have everything else that the default cyanogenmod's kernal has? (i just want to know if I am going to loose anything from cyan to this kernal)
Click to expand...
Click to collapse
Yes that is correct.
Nexus FireBall 1.15GHz.
I will be also flashing this kernel update to 1.15 GHz tonight. I want to try and optimize my nexus one to its fully potential capabilities. : )
Updated, Changed Kernel optimizations. Since this kernel follows pershoot, he recommends if you are on 5.0.6 to flash the VFPv3 optimized version.
VFP works great
Hi guys when i unzip their 4 files i know the ko and zimage but the other 2 files do i need to install them too?? and how? thanx in advance.
The other two files are the source files. They there so you can research what changes I have made in the voltage and frequencies and also you could compile this on your own if you want.
[KERNEL][CM7][Froyo] Dalingrin's OC kernel w/fixed IO perf (quadrant) & 1.2Ghz test
Disclaimer: As always, flash at your own risk.
Background
So, recently there has been alot of debate over why quadrant (and to some extent, system performance) was lower with the OC kernel, as compared to the stock CM7 kernel. (http://forum.xda-developers.com/showthread.php?t=1002504) As part of my examining the problem, i went looking for a solution. Starting from the first OC CM7 kernel, i would run quadrant and see how the performance fared. I finally found the issue appeared in the 3-08a kernel; using that, i rolled back changes until i found the commit remove to fix the issue. Specifically, it seems to be somewhere in the 2.6.29.6 update: https://github.com/dalingrin/nook_kernel/commits/gingerbread-exp
In short, using his source, i have compiled a kernel with fixed I/O performance, and all his other tweaks (interactive gov, etc).
So, I want to make this clear; this is still dalingrin's kernel; in no way do i wish to take credit for his work. But, while he is out, work must go on, right?
Information
Who is this kernel for?
eMMC Froyo and CM7 users
Will this work on SD cards?
It may if you manually replace you uImage, but i cannot guarantee it (since i cannot test it)
Is everything working in this release?
everything like bluetooth and dsp should still be just fine (you may have to do a few hard shutdowns/reboots to kick on BT, like normal).
Kernel Links -3/25/10
OC kernels (up to 1100Mhz, Interactive gov, BT and DSP):
Regular
http://www.mediafire.com/?k00ruvyulf01y64
Extra network features (PPP, etc)
http://www.mediafire.com/?i9h76wn483tk16v
OC kernel (up to 1190Mhz, Interactive gov, BT and DSP):
http://www.mediafire.com/?v6d2jpzaynvchde
For those having problems setting this speed in the CM7 performance settings, give setCPU a try, but don't use profiles. Using set CPU, i am able to get my system stable at 1190, where the CM7 manager instantly locks up.
Feedback
After flashing, please make note of OVERALL system response. The dip in quadrant scores prompted the fix, but i feel that the system is overall better; I would like some more input if others are seeing this as well.
Any and all feedback is welcome, and I will do what i can for support...
Great job man, you and dalingrin both!
Ran 3 quadrant tests on newest nightly (#30)
1. 1856
2. 1700 even
3. Whopping 2030!
Can you be more specific about which network features are in the second choice ?
Thanks !!
ADude said:
Can you be more specific about which network features are in the second choice ?
Thanks !!
Click to expand...
Click to collapse
Um....truth is, i am really not too familiar with it, but looking a the diff between the two configs:
# Core Netfilter Configuration
# IP: Netfilter Configuration
# CONFIG_TUN
# CONFIG_PPP
I am trying out the net kernel again, to see if it is better than the last time i tried it..
Edit: Its looking better than the last time i tried it. Launcher pro hangs for a but on startup, but so far so good after that.
Just started using CM7 last night (w/bottom keys mod, so the nightly is from a few revisions back), but just installed this kernel (the regular version, w/out the Net adds, which I don't need), wiped cache & Dalvik, rebooted, set OC to 1100 and "performance" in CyangenMod Settings and now getting 1918 Quad score...vs. 1372 on the stock kernel with no OC.
I can definitely live with that score...great work to you and dalingrin!!
Thanks for taking care of this while I am gone. Much appreciated.
The update to *.6 is not necessary anyway.
When I get back I will revert the *.6 update and compile some of the netfilter/iptables and tun as modules as this seems to be more compatible than compiling them directly into the kernel.
Madcat, kudos to you. This is perceptibly faster.
great work!
so is this a 2.6.29.5 kernel then?
WOW, scrolling through XDA forum is much smoother than it used to be.
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Can I have the config file for the first? I'm going to play with the kernel a bit.
EDIT: I'm just going to keep my big mouth shut for a while. I hoped it was just a bug with quadrant, but I flashed your kernel just now. There is a huge difference in interactivity. I was playing with the app drawer yesterday and couldn't get it to be smooth with "labels fade in" turned on and a 1000ms or so time on the animation for the app drawer. Now it's perfect every time.
GOOD JOB!
I love Open Source.
Will try this in some minutes. (Nook charging)
Ok, tested it. My scores below.
** QUADRANT SCORES **
Before update, 1100mhz: ~700
After update, 800mhz: ~1500
Now, 1100mhz: 1920
**********************
Awesome!
Just flashed it on mine and seems silky smooth to me. Not real sure there is a big difference, but it is not worse at least. Seems better to me.. Good job Madcat!!
Waiting anxiously for Dalingrin to return to his lab and see what else he can whip up for us..
nice!
i'm getting the same numbers as others (~1800) now. haven't really tested for overall smoothness yet.
will this kernel ever get a nookie version?
cowballz69 said:
will this kernel ever get a nookie version?
Click to expand...
Click to collapse
I have to admit - i said CM7 only, since that is all i have to test it on. If you do want to try it, you don't really risk anything; if it doesn't work, simply reboot to recovery and flash your last working kernel again.
As it is, i haven't really given a good look at what might be different between versions, so i can't give much advice on why it would/wouldn't work on Froyo.
Homer_S_xda said:
Tried on SDcard, installed by copying uImage to Boot. Reboots to EMMC when trying to load desktop. Back to CM7 stock. I guess I'll wait. Thanks though!
Homer
Click to expand...
Click to collapse
Got the same issue with the Net feature kernel. However the other one works fine. Got 1918 Quadrant on SD Card with OC 1100 GHz + interactive gov.
So I guess CM7 performance on SD is not too bad compared to eMMC
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
victle said:
@Divine_Madcat : Could you look into the problem of the Net features kernel with SD Card booting? It run into eMMC after the bootanimation.
Thanks much for your work, an action is much better than thousand words !!
Click to expand...
Click to collapse
Ill be happy to take a look, but can't promise anything right away.
SCWells72 said:
I tried both of these from SD card. The non-net features version boots but posted some terrible #s for me (<700 Quadrant and ~6-7 Linpack); the net features version doesn't boot. Is there something special I need to do with the first kernel to see the benefits? I checked and was clocked to 1.1GHz in CM settings.
Click to expand...
Click to collapse
hmmmm.. that doesn't sound right at all. May i ask which nightly you are using? Right now, i am on nightly 27, and haven't seen anything like that (in my case, it either works, or just boot loops, if i set the clock too high).
Can someone port this kernek to ATT?
http://forum.xda-developers.com/showthread.php?t=1263838
tassadar898 said:
Can someone port this kernek to ATT?
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Its possible, but there are differences in the softkeys, charging hardware, and nfc at the minimum, so it will take a little work to port that over entirely. What would be better is for one of our current kernel modders to add some of the features of the SIYAH kernel over to their own.
I plan on pulling in 100 MHz support.
He doesn't have that much more, other than extremely experimental features that if you read the thread, tend to break.
Gokhan is quite talented, but he's also VERY aggressive - if you're more careful, you don't have to go through long beta periods with lots of broken releases like he does.
He also released source code for older kernels as megapatches, and now releases as straight full-source tarball drops. It makes separating the good from the bad EXTREMELY difficult.
As far as features he has that I don't currently:
1) 100 MHz support - I plan on this one, it's a fairly high priority as part of my current power management research
2) Crazy wacky alternative governors - these are a great way to somehow combine lag and poor battery life all in one
3) Charge current control - not possible on our devices, we have a different (very crippled) charger IC
4) Touchscreen stuff - I have seen no reports of people having touchscreen issues. If it ain't broke don't fix it.
5) BLN - I'm on the fence on this one. I think the I777 community may actually have the maturity to handle this one. (BLN's dirty little secret on the I9100/I777 - it holds a wakelock while the light is on. This means you lose 50% battery overnight instead of <10% if a notificiation comes in right after bed.)
Entropy512 said:
5) BLN - I'm on the fence on this one. I think the I777 community may actually have the maturity to handle this one. (BLN's dirty little secret on the I9100/I777 - it holds a wakelock while the light is on. This means you lose 50% battery overnight instead of <10% if a notificiation comes in right after bed.)
Click to expand...
Click to collapse
Would it be possible to get past the wakelock issue if you could program that the BLN shuts off after, say 30min, or user defined? That would work in my case but not sure if everyone universally would like it that way. Just a thought...
Hey Entropy nice to see you here! In siyah you can control the GPU voltage for undervolting. I currently do it using the Tegrak kernel module and I reduced the minimum step of 160 mhz to 750mv down from 950mv. I've noticed a nice bump in battery life. In his 2.1 beta version he also has this available feature
SiyahKernel v2.1 - not released yet -
Time to break some records... both performance-wise and battery-wise...
Overclocking part is optimized and bus frequency selection is modified.
User customizable frequency levels. you still have 8 steps, but you will be able to customize them. wanna change 100 to 150 as 100MHz is not stable on your device? wanna change 1400 to 1304 and 1600 to 1504? or increase 1600 to 1696?
User customizable bus frequency selection. no more overheating. if you are a battery freak, just set it to minimum and your device will last more than ever.
Based on Update3 sources...
Thanks for developing for us!!
I'll look into GPU voltage control once I finish my current power management adventures.
Custom frequency steps seems like asking for stability problems. There's no way this is getting ported until he releases 2.1 final, since he isn't very good about GPL compliance.
Thanks! I look forward to testing. If you need a guinea pig let me know.
Entropy512 said:
I'll look into GPU voltage control once I finish my current power management adventures.
Custom frequency steps seems like asking for stability problems. There's no way this is getting ported until he releases 2.1 final, since he isn't very good about GPL compliance.
Click to expand...
Click to collapse
GPU voltage doesn't bring that much other than stabilizing 400MHz, undervolting doesn't go that far down from stock voltages, unless you underclock heavily too.
Also get off his horse about GPL . The license states that you've got 90 days to release your code, until now he released it within the day for final versions, and betas are no longer released on XDA to get off that technicality of the 5 day rule.
There's enough kernels out there with the "stable" philosophy, some of which barely differentiate from stick sources, so people can go and use those if they want to. Siyah is more a Swiss army knife, but you'll have to be careful not to cut yourself, and it's more fun for some to tinker with the phone.
Edit: What you should port though, is update3 sources, those bring significant upgrades in battery life, speed and sound quality.
AndreiLux said:
GPU voltage doesn't bring that much other than stabilizing 400MHz, undervolting doesn't go that far down from stock voltages, unless you underclock heavily too.
Click to expand...
Click to collapse
Yeah, I figured as much, which is why it's pretty low on my priorities list
Also get off his horse about GPL . The license states that you've got 90 days to release your code, until now he released it within the day for final versions, and betas are no longer released on XDA to get off that technicality of the 5 day rule.
Click to expand...
Click to collapse
It says that nowhere. HTC claimed they had 90 days and that is a GPL violation. Easy enough to Google that one. It kind of bit them in the ass though - http://thread.gmane.org/gmane.linux.kernel/1048027 and https://freedom-to-tinker.com/blog/sjs/htc-willfully-violates-gpl-t-mobiles-new-g2-android-phone
After much media pressure they backed down and released sources in only 7 days.
GPLv3 gives an explicit 30-day grace period for resolving violations, but the kernel is not v3, it's GPLv2.
I really should stop pointing Gokhan towards fixes since he's a one-way street.
There's enough kernels out there with the "stable" philosophy, some of which barely differentiate from stick sources, so people can go and use those if they want to. Siyah is more a Swiss army knife, but you'll have to be careful not to cut yourself, and it's more fun for some to tinker with the phone.
Click to expand...
Click to collapse
Yup - If someone else wants to port his more aggressive features they can try - it's just not coming from me.
Edit: What you should port though, is update3 sources, those bring significant upgrades in battery life, speed and sound quality.
Click to expand...
Click to collapse
I'll have to look into that - As of a few weeks ago, the AT&T I777 sources were new enough that I9100 kernels (including Siyah) started to be based off of them. The question is - while Update2 to Update3 is a big improvement, is I777 to update3 such an improvement?
I'll have to check those out tonight and diff them.
update3 is a vastly bigger update than what the AT&T sources were to update2. Performance wise, it's a clear-cut, audio too. As for battery life check back in the AOS thread.
Looking forward to see the update being incorporated.
AndreiLux said:
update3 is a vastly bigger update than what the AT&T sources were to update2. Performance wise, it's a clear-cut, audio too. As for battery life check back in the AOS thread.
Click to expand...
Click to collapse
I'm going to start this over the next week - I've split update3 into what should be separate independent patchsets by component (touchkey, audio, wifi, etc.)
Last one is likely going to be the machine-specific ARM stuff - because that means rewriting the clock control patches completely.
I've received different recommendations from everybody I talked to, but I would like to know what custom kernel people love most right now. I'm running simple rooted version of 4.2.2 right now with the stock kernel. I'm looking for something to improve battery life a bit and get rid of the weird graphical hiccups that can take place when rapidly switching tasks.
Let's hear it. Thanks.
Sent from my Nexus 10 using xda app-developers app
lr4life said:
I've received different recommendations from everybody I talked to, but I would like to know what custom kernel people love most right now. I'm running simple rooted version of 4.2.2 right now with the stock kernel.
Let's hear it. Thanks.
Click to expand...
Click to collapse
I've been using Franco Kernel since the start and it's worked great. Definitely helps with thermal throttling issues.
lr4life said:
I've received different recommendations from everybody I talked to, but I would like to know what custom kernel people love most right now. I'm running simple rooted version of 4.2.2 right now with the stock kernel.
Let's hear it. Thanks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I'm using KTManta. Works pretty well and I can recommend.
Sent from my Nexus 10 with XDA Premium HD. ROM: AOKP PUB 4.4.2 Kernel: KTManta
Ktmanta is definitely the best kernel on nexus 10, and other devices for that matter. Load it up with the ktweaker app, set it to ktoonservative and row, and :good:
Franco seems to have a cult following, but the kernel just isn't where Ktmanta is at by any means.
Using KTManta, and loving it. I've tried all the others and keep coming back to KTManta. Behind that I would go with Morfic's Trinity kernel.
Franco and Trinity are great kernels that give smooth performance and good battery. KTmanta is also a smooth kernel though and has far more options and tweaks than the other kernels. By default you wont see that much difference on it over the stock kernel though, since ktoonsez does not like to set too many settings different than what stock has for its defaults. But you can easily load up his free tweaking program, or run Trickster MOD, and set any options you want. The ktoonservative governor is by far the best governor for this tablet.
Definitely KTManta great overall performance
Trinity for life.
KTManta
SLP and ZEN for best benchmark score
Ktoonservative and ZEN for best user experience (Which is all that matters)
Trinity little more soft and not so heat producing like other kernels, little help for battery also ..
Ktmanta its too laggy sometimes and not so much help to the battery like most of here are screaming..
Sent from my Nexus 10 using xda app-developers app
There is no such thing as `the best' in the specific sense of the question.. They're free.. Go download them and try them yourself. Pick the one "you" feel is the best. Polling the forum isn't going to help you. You know what they say about opinions...
I like franco.Kernel. Can't say it's the best or not though since I really didn't do any in-depth testing.
Plenty kernel I try, at the end, I still back to custom ROM stock kernel.
franco - some issue and not stable.
KTManta - I still not sure why this is so famous, not the best in performance, even after use some people setting, it was better but not really great, and hang up sometimes especially when use certain I/O setting.
Trinity - Quite nice actually, not much to complain about it, but I don't see a need to use it.
By the way, I am happily running mrRobinson AOKP ROM with it own kernel.
I'm actually quite happy with KTManta, using the Zen scheduler and ktoonservative governor. Extremely smooth, lag free, with good battery.
... beamed from my Nexus 10 to your planet
Andrewtst said:
[*]KTManta - I still not sure why this is so famous, not the best in performance, even after use some people setting, it was better but not really great, and hang up sometimes especially when use certain I/O setting.
Click to expand...
Click to collapse
Not sure how that happened. Using suggested settings this is the best performing kernel for me. If you're randomly messing with I/o settings yeah it can cause issues but I wouldn't suggest doing that unless you know what everything does KT + zen(minor tweaks) + ktoonservative + UV = battery and performance for me
Sent from my Nexus 10 using XDA Premium HD app
Andrewtst said:
Plenty kernel I try, at the end, I still back to custom ROM stock kernel.
franco - some issue and not stable.
KTManta - I still not sure why this is so famous, not the best in performance, even after use some people setting, it was better but not really great, and hang up sometimes especially when use certain I/O setting.
Trinity - Quite nice actually, not much to complain about it, but I don't see a need to use it.
Click to expand...
Click to collapse
There have been a couple releases with issues for me on KTManta kernel, but a couple releases out of the 20 or so versions is not much. The issues are quickly fixed and a new version put out anyway so maybe you just happened to come in and try it on one of those releases. This kernel is so popular because it has the most active dev and the most options.
And why do you think the Franco kernel is not stable?
For what its worth, Im partial to Franco's r3 kernel--having tested the others. It improved my overall web browsing smoothness on 4.2.2 which is all I was looking for after moving from 4.2.1. As previously stated, what's "best" for me may not be "best" for others. Cheers!
Kernels much like silicon slabs are unique...each device will respond differently. Try em all...and pick your favorite.
Sent from my SGH-T889
You know actually.....
They are all good, if you know what you are doing.
Trinity and Franco are the best if you just want to set and forget. KTmanta is the best if you want to tweak and have options to play with.
This is loosely based on CTXz's kernel. I just wanted a little more from it. I'm using it on my "Nook". Hence the name.
So may I present to you.....
Nuki - Kernel
Install:
Just flash this through TWRP recovery. I use 2.8.7.0. It'll do it's own wipes.
It's built for the "Nook" version. But should work for any WiFi only ROM.
My preferred tuner for the kernel is Kernel Audiutor . But others should work also.
Changelog
V1.1 - Ubertec and Linaro toolchains
Enabled KSM and tweaked
init.d support
Selinux permissive
V1
OC to 1344mhz
Intelliplug 3.9
govs added - lionheart, pegasusq, conservativeX, darkness, nightmare.
Shedulers - sio, vr, zen. I haven't been able to get "row" to compile without errors.
Frandom
Lots of tweaks/optimizations
Downloads:
Nuki-V1.1-Linaro
Nuki-V1.1-Uber
Nuki-V1
Stock-OG1-Nook-Kernel
Thanks to
@CTXz
@laufersteppenwolf
@friedrich420
And the ton of other git's I went through to get this.
XDA:DevDB Information
[Kernel] Nuki-Stock-T230NU, Kernel for the Samsung Galaxy Tab 4
Contributors
engine95
Source Code: https://github.com/engine95/Degaswifi-CPU-tweaks.git
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-10-17
Created 2015-10-17
Last Updated 2015-10-17
reserved
Mine! Will post feedcack! :fingers-crossed:
@engine95 - awesome. Gonna test it out and let you know
Looking good. Confirm working looking the SM-T230NU......should work on SM-T230 as well.
Well done. I hope it works good for you all!
Just a little update.
I'm trying to work on the GPU now, and it's proving very interesting. This GC1000 GPU treats the cores as being separate. Meaning one is for 2d @ 416mhz the other is for [email protected]
It looks like our possible freq's are 533, 624, 702. And maybe one close to 800 according to the specs.
The problem I see happening, is that we'll be locked into whatever freq I build into it. Meaning there isn't a way to change it through a kernel tuner.
So far, I havent had any luck OC'ing either of them. But we'll see what happens.
V1.1 is in OP See read changelog
Still no luck with OC GPU. But theres 2 builds: Linaro and Ubertec toolchains. Let me know which one you like/prefer.
Enjoy
Nice
so what's the point?
new features?
overclocked?
emoboy (Official Name!)
Nice
so what's the point?
new features?
overclocked?
Click to expand...
Click to collapse
I don't know you. So I don't know if this is sarcastic or not. So I'll play this answer in the middle.
Read the change log and look at the git. Almost everything here has been reworked, updated and/or added. Oc is the only thing I haven't touched. Yet.
@engine95 - for me, my tablet runs smoother on the linaro build.
Nice update and thank you.
g_ding84 said:
@engine95 - for me, my tablet runs smoother on the linaro build.
Nice update and thank you.
Click to expand...
Click to collapse
Thanks
On my past kernels, Ubertec seems to usually run faster. While Linaro runs smoother. But on this tab, it's harder to tell. So Thanks for letting me know. :good:
I am impressed with a lot of the optimizations that "Sammy" has already build into this. Source code I'm used to changing is already in it. And this thing sleeps like a baby.
It's too bad Marvell/Vivante/Sammy has throttled this CPU/GPU so much according to the specs. I mean, for a low-end setup it could be a lot better. But then, it would probably lose battery.
I'm not going to add anymore "stuffs" to it, as I think we have a good selection now. What is in it should satisfy " battery thru performance" depending on the settings people choose.
I haven't even looked a OC CPU yet. All I've tried so far is GPU and that hasn't gone well.
These will be the next things I'll work on. Unless......"SQUIRREL!"
forgive my ignorance, normally i would use the googles and xdas to educate myself before asking such a question, however, I have basically given up on this tablet.....so does your development of this kernel bring the tab 4 7" owners any close to getting an aosp build, this tablet is useless running TW?
edit: upon review, my post was thankless but i am very thankful for you doing what you do for this tablet, it so needs the attention!
gammaxgoblin said:
forgive my ignorance, normally i would use the googles and xdas to educate myself before asking such a question, however, I have basically given up on this tablet.....so does your development of this kernel bring the tab 4 7" owners any close to getting an aosp build, this tablet is useless running TW?
edit: upon review, my post was thankless but i am very thankful for you doing what you do for this tablet, it so needs the attention!
Click to expand...
Click to collapse
Its all good. No worries.
Unfortunately, no. It just improves on stock.
Im new to Samsung, so its all a new learning curve for me. I am kinda shocked at how "low-end " this is for a mainstream tablet. I'd have thought it would be.....better.
T-230 with nuki v1.1 linaro. Working amazingly. Thank you much.
Thank you for this kernel! I've never even thought to use another kernel for this low-end device.
Mine was originally the Nook version as well but I have flashed the latest non-nook firmware and heavily modded it.
I'm using the Linaro version. Xposed is running with a few modules. tuning with Kernel Audiutor.
The device it running very well. smoother than normal. It's a bit warmer too. but we'll see about that though.
Uber variant. Makes a huge difference. Thank you!!!
Still using the linaro. I can't seem to make either of the CPU frequencies stop being max. (1344)
Any suggestions? I'll end up trying the Uber kernel in a moment.
brossovitch said:
Still using the linaro. I can't seem to make either of the CPU frequencies stop being max. (1344)
Any suggestions? I'll end up trying the Uber kernel in a moment.
Click to expand...
Click to collapse
When you reboot, you'll need to set min, manually. I don't know why.
Or, try a different gov. Lionheart and conservativex are my preference.
You may need to remove the set on boot option, then reenable it.
It shouldn't be sticking like that
Mhh, that all sounds very interesting. Possible I can test it this weekend.
CTXz kernel is my first choice all that last year, so I can test it against yours. Don't get me wrong it will be very interesting to see what's different.
Not to see what is better, I wish to see the difference. Every ROM has his specific use and modifications. So it is the science guy who wish to know it .
Will report later about it and CTXz I will be every time a fan of your work .