Related
Hello Vibrant folk, happy hump day! This is TalonMTD, for CM7 and MIUI (and potentially other MTD based ROMs). This kernel has nearly all of the features of TalonDEV--and more coming sooner than later. IMPORTANT: be'st thou careful, here there be monsters--THIS KERNEL IS UNTESTED ON THE VIBRANT! No one in our dev channel has one. If you're good with this stuff, let me know and I'll hook you up with test builds. Lets get into the good stuff!
Code:
Features
[LIST]
[*]Overclock up to 1440MHz/Undervolt for all frequencies (having only 5 frequencies undervolted seems most stable)
[*]Nexus S Framebuffer
[*]Voodoo Color v2 (No yellow tint!)
[*]Voodoo Sound v10
[*]Based on Linux kernel 2.6.35.13
[*]GPU overclock
[*]GPU Tweaks
[*]Bonus Governors: InteractiveX, Smartass, Conservative governor compiled as a module (not enableable yet)
[*]Bonus Schedulers: SIO, V(R), BFQ2r1, CFQ with tweaks
[*]Undervolted ADC and RAM
[*]Disabled Userspace governor
[*]Kangsterizer’s LED notifications
[*]Asynchronous I/O support
[*]Logcat compiled as a module, must be enabled via ‘logcat-on’
[*]Lowmemorykiller tweaks by kodos96
[*]Jhash3
[*]RAM tweaks
[*]Readahead tweaks
[*]Kernel HZ set at 250
[*]Disabled kernel printk for less overhead
[*]KTLO (Keep the Lights On)
[*]Samsung ARM fix
[*]16.25 lbs. of ext4 fixes
[/LIST]
Code:
#include <std/disclaimer.h>
/*
* While this build is heavily optimized, it is also capable of pushing your Vibrant
* much harder. I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the current economic crisis. Please do some
* research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modificiations, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You can download it here...
0.0.3: http://dl.dropbox.com/u/9426310/TalonVibrant-0.0.3.zip
Source code: http://existz.darkirc.info/git/?p=kernel/talonmtd.git
Join us on freenode, channel #suckerpunch for support.
Many thanks to my co-devs eXistZ, kodos96, and zacharias.maladroit/zachy_md. (original Talon thread here: http://forum.xda-developers.com/showthread.php?t=1050206)
Huge thanks to
Supercurio
Teamhacksung
morfic
netarchy
TheEscapist
TK-Glitch
kangsterizer
And a great big final thanks to my testers, the great folks who put up with me breaking stuff and putting up a new build every 5 minutes, the guys who pushed me to greater heights to get stuff done:
Shoman94
Vivified (the great motivator)
Thegodsquirrel
Abee_13
lownox
Wanna say thanks? Buy me a root beer, and/or hit thanks.
Just so everyone knows, I also own an iPhone.
0.0.3 (Maintenance Upgrade)
TONS AND TONS of ext4 fixes (more info here: http://existz.darkirc.info/git/?p=kernel/talonmtd.git;a=shortlog)
Minor upstream fixes including call volume tweak
0.0.2
Improved USB signal quality
OndemandX governor (offers sleep power consumption improvements over ondemand, not ready for the big time yet. Seems to cause 3D choppiness.)
Fixed enable_conservative script (released separately, coming soon)
Upstream DVFS fixes
Many more ARM fixes (for more information visit http://existz.darkirc.info/git/?p=kernel/talonmtd.git;a=shortlog and take a look at the ARM fixes)
Low power mode support (buggy)
Upstream touchkey tweak to prevent accidental button pushing
BUMPED OVERCLOCK VOLTAGES--People were reporting serious instability, so I bumped the voltages. This should fix the majority of issues.
init.d cleaning script from zacharias.maladroit
Major tweaks from Infuse to help with CPU scaling above 1000 MHz
ytt3r said:
This post isn't actually doing anything right now, so here's a picture of a kitten.
Click to expand...
Click to collapse
Just flashed on trigger 2.3.5 8/22 and everything is running good so far.
Thanks!
Thank you ytt3r for bringing TalonMTD to Vibrant! I am about to flash it on CM7 Build #105 and I will let you know if it works ok. I am ready for CM7 to have better battery since the performance is already top notch for Vibrant and most likely will not get any faster.
Dev.... nice work to get another kernel ported over to the Vibrant community. I'll wait to get some feedback from others before I decide to flash as a daily driver.
I'll tell you though, if you haven't followed the Vibrant community.... the CM7 or CM7 based ROM's are having a problem with battery life. So, with that said... if you could figure out a way to get us some blazing battery life... you'd probably be considered a hero.
Dmkjr said:
Dev.... nice work to get another kernel ported over to the Vibrant community. I'll wait to get some feedback from others before I decide to flash as a daily driver.
I'll tell you though, if you haven't followed the Vibrant community.... the CM7 or CM7 based ROM's are having a problem with battery life. So, with that said... if you could figure out a way to get us some blazing battery life... you'd probably be considered a hero.
Click to expand...
Click to collapse
I've had excellent battery life... CM7 is having the same issues on the Captivate, and I'm sure all SGS models. But being completely honest it seems to be running perfectly well for me and I haven't had any battery issues.
So far so good. Phone is flying with CM7 Build#105. No bugs so far. Only issue I had was a freeze at 1.3ghz. This is the first CM7 kernel I have had a freeze at 1.3ghz with. 1.2ghz is rock solid even with -25mv to -125mv undervolt.
16.25 lbs?
Sent from my SGH-T959 using XDA Premium App
Only issue is the captive lights don't time out on miui might just be me tho
To be fair.... I've bought a PowerSkin and been using it for almost a week running 1.8.26. I don't think my input on battery life would be relevant to most.
im using MIUI revamped and i flashed this kernel. i still have the yellow tint
enzomtrx said:
16.25 lbs?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
You're the only person to catch that so far lol
Chwek13 said:
Only issue is the captive lights don't time out on miui might just be me tho
Click to expand...
Click to collapse
Not an issue, a feature, it's KTLO.
Great Kernel.
Thanks for the nice work you done on this.
One question:
Why none so far tried the updated drivers from Optimus 3D for out devices?
They have v1.6 driver and we are at v1.5. Gpu is the same just theirs are 300mhz vs 200mhz for sgs family. (PowerVR SGX 540)
On cm7 my leds stay on all the time when screen is on. This is intentional? Any way to make a version without that? Not that it matters but quadrant scores are 200-300 less then neo17r7 @ 1.2ghz.
hey guys will this work on the surface 3.2 jvr port? it uses the talondve on the i9000 anyone dared to try?
hurtz777 said:
On cm7 my leds stay on all the time when screen is on. This is intentional? Any way to make a version without that? Not that it matters but quadrant scores are 200-300 less then neo17r7 @ 1.2ghz.
Click to expand...
Click to collapse
My leds are staying on with this kernel 2. Switched to immortality cm7 and led is off now. Pls fix as this is the only thing I've noticed. Everything else seems great.
Bluejay913 said:
My leds are staying on with this kernel 2. Switched to immortality cm7 and led is off now. Pls fix as this is the only thing I've noticed. Everything else seems great.
Click to expand...
Click to collapse
That's a feature of this kernel
From the OP
KTLO (Keep the Lights On)
Click to expand...
Click to collapse
Does this work on omfgb?
Sent from my SGH-T959 using XDA App
Dmkjr said:
Dev.... nice work to get another kernel ported over to the Vibrant community. I'll wait to get some feedback from others before I decide to flash as a daily driver.
I'll tell you though, if you haven't followed the Vibrant community.... the CM7 or CM7 based ROM's are having a problem with battery life. So, with that said... if you could figure out a way to get us some blazing battery life... you'd probably be considered a hero.
Click to expand...
Click to collapse
how about Gingerbread Bootloaders ?
aren't modded bootloaders available for the Vibrant (yeah I know it's kinda risky)
*subscribes*
zacharias.maladroit said:
how about Gingerbread Bootloaders ?
aren't modded bootloaders available for the Vibrant (yeah I know it's kinda risky)
*subscribes*
Click to expand...
Click to collapse
Respect and nice to see you back
Hey XDA, I was a bit of a lurker on here for a while, and learned a huge amount about everything from getting root to theme-ing and set up my phone how I thought I wanted it - CM 7.0.3, a lot of ZipThemer and MetaMorph changes, etc.
Anyways, I have seen the majority of stuff on this site about this phone and am wondering what ROMs, kernels, setups, and themes and whatnot you guys think are the best out of all the options you have tried. MIUI definitely is not for me, and I love CM but have been afraid to flash any other kind of ROM, especially after a bootloop issue.
I'm just sick of having to set up everything on my phone again when i change ROMs - (changed to 7.1.0 two weeks ago) - just wondering if there was an easier way, or a lesser known ROM/kernel combo that has great battery life and performance.
Features I really enjoy currently:
ChevyNo1 kernels
just about every CM customization option
RZRecovery
Black and White themes for ThemeChooser, ADW, and Zipthemer/Metamorph
Thanks!
Liquid GB with chevyno ulv .8ghz kernal on interactive governer and your golden
taptaptouch said:
Liquid GB with chevyno ulv .8ghz kernal on interactive governer and your golden
Click to expand...
Click to collapse
sweet! thanks! - what exactly do you recommend about each? and why interactive instead of smartass or on demand?
Hello everyone,
I am a newcomer to the O2X world. My previous device was an Xperia X10 and having that device for a long time it was fairly easy to follow the forums and know what route to go, which rom to get or kernel, etc.. Now being introduced to Rom Manager, and this phenomenal (to me) device its like starting all over again. I flashed to CM7.1 nightly (yesterday) and the device just only seems to get better and better, although being honest, I truly loved the Music App 2.2.2 had, as well as the camera. I tinkered around a little to get those to work without any success yet.
In any event, my real question is about the kernels... running CM7.1 nightly, what is a recommended Kernel to switch to? I am not looking to overclock the device as I feel it just isn't necessary (used to the Xperia), so Im just looking to get any fixes, tweaks, been hearing about Voodoo Sound etc to just solidify the phone.. might someone be able to point me in the right direction? I had been reading the forums for days now since I got the device but still haven't found what route to go as all the features are completely new to me.
Any help would much much be appreciated! and I must add, there are mixed reviews on the O2X but my take thus far, Im completely blown away.
vorkkernel and swiftextreme
http://forum.xda-developers.com/showthread.php?t=1059910 - vork
http://forum.xda-developers.com/showthread.php?t=1325183 - swiftextreme
vork is good in ironing out cm and showing off large score in tests like(quantrant etc.) while
swiftextreme is very good on batterylife
but I still prefer stock cm kernel
welcome to the o2x forums btw
mvsn said:
Hello everyone,
In any event, my real question is about the kernels... running CM7.1 nightly, what is a recommended Kernel to switch to? I am not looking to overclock the device as I feel it just isn't necessary (used to the Xperia), so Im just looking to get any fixes, tweaks, been hearing about Voodoo Sound etc to just solidify the phone.. might someone be able to point me in the right direction? I had been reading the forums for days now since I got the device but still haven't found what route to go as all the features are completely new to me.
Any help would much much be appreciated! and I must add, there are mixed reviews on the O2X but my take thus far, Im completely blown away.
Click to expand...
Click to collapse
hi, welcome
i stick to vorkkernel(normal version), you can get app to install in market for free.
i run it on 1,2 Ghz, with sleep profile in setcpu with 816Mhz.
gives me about 35hrs battery life and great speed in everyday use.
I am on CM7 with swiftkernel, [email protected],2GHz and I am really satisfied. I get 36-48h of normal use with 3G on and the 2x runs as hell.
Only drawback from the swiftkernel: You get a wakeup delay (1 sec.) because the kernel locks the cpu down to 256MHz when the screen is off. (Which results in a higher standbytime.
Hah, I remember my X10, used to run TripNraver MIUI on that does he even still make roms?
Anyway would stick to the stock CM7 kernel if i were you, least problems with that (no SOD, BSOD etc). On vork / swift problems keep popping up (for me at least). CM7 kernel no problems
I really dont have any knowledge about kernel!! pls help me
i am using cyanogen mod 7 and i installed swiftkernel by overclocking to 1.2 ghz wont it damage my phone??? pls do reply thank you very much in advance .....
gomzy27 said:
i am using cyanogen mod 7 and i installed swiftkernel by overclocking to 1.2 ghz wont it damage my phone??? pls do reply thank you very much in advance .....
Click to expand...
Click to collapse
You always take a risk when overclocking. With 1.2 it's not a big risk, but there's always one.
Thank you so much!!! can you pls tell me which kernel is good for daily use ??? i am using cyanogen mod 7 ??? when i installed swiftkernel .. i realized that it was automatically overclocked to 1015??? is this fine???
Yo...
I'm using CM Nightly's, in last week I did the install the Vork Kernel, I think so good to diary use.
Now I'm using the #201 with Vork Kernel, all ok. No BSOD and others bugs.
You can use SetCPU with personal profiles.
I'm using max 1216mhz and Profile's Screen Off: max 816 min 216. All ok in this time.
Already did one week, no problems with this.
Just had problem with #202 CM, in #197 and #201 all ok.
so bro if i am running MIUI , what do i need to do to overclock it??
sill any of these kernals be good enough or is there any specific kernal for miui??
First things first: this is not a "best kernel thread", so please avoid asking or stating in that direction. This is all about spotting what custom kernels are compatible with Omni (for now) Nighties, and what has been your experience with them so far.
In my case, I've tried both Yank's (1.6g-beta2) and Boeffla (beta 1a) and they are working flawlessly. At the moment I'm using Boeffla just cause I find it easier to toy with different configurations and Yank's can only be tweaked from aroma. And in my personal experience, I've found that using ART instead of dalvik, it feels like I'm having a smoother experience (with a bit more battery drain, I must admit). But like I said, this is only how those kernels work on my device and that doesn't mean it will happen exactly the same way in your's and how you'd feel about them.
Any other kernels have been tested and are working in Omni 4.4 nighties?
fermasia said:
First things first: this is not a "best kernel thread", so please avoid asking or stating in that direction. This is all about spotting what custom kernels are compatible with Omni (for now) Nighties, and what has been your experience with them so far.
In my case, I've tried both Yank's (1.6g-beta2) and Boeffla (beta 1a) and they are working flawlessly. At the moment I'm using Boeffla just cause I find it easier to toy with different configurations and Yank's can only be tweaked from aroma. And in my personal experience, I've found that using ART instead of dalvik, it feels like I'm having a smoother experience (with a bit more battery drain, I must admit). But like I said, this is only how those kernels work on my device and that doesn't mean it will happen exactly the same way in your's and how you'd feel about them.
Any other kernels have been tested and are working in Omni 4.4 nighties?
Click to expand...
Click to collapse
I follow you, I would install dual boot with a custom stock 4.3 (Android Revolution HD) and an android 4.4 rom (OmniROM).
I could create dual boot between 4.1/4.2/4.3/4.4(only CM11) roms with excellent Googy-Max Kernel... but nothing to do with OmniROM 4.4 due to recovery or kernel incompatibility.
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Ah, I found Devil2 Kernel http://forum.xda-developers.com/showthread.php?t=2528624 that supports Omni 4.4... and dual booting
Never been a huge fan of dualbooting but since I'm planning to stay with Omni until we reach a estable build... I wouldn't mind giving stock 4.3 a spin.
Has anyone tried out Devil and Omni already?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).
Entropy512 said:
Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).
Click to expand...
Click to collapse
I´m not much more than a resourceful noob, I must admit. But even when your line of thoughts seems very logical, I wonder if there could be any other reasons for kernel maintainers like Lord Boeffla or Yank555 to remain aside from main ROM projects. Both of them have been around for long now, and I've experienced with their work in my device a lot, with no harm at all (I can't guarantee results for other people, just talking about my experience).
I guess custom kernels give you the chance to adjust your kernel to your own needs. Some people would be ok about sacrificing some performance to obtain a better battery result, or would like to have the freedom to choose the governor that best suits you, for instance. Isn't customization and freedom the whole thing about custom ROMS and GPL?
As for me, I go for customs kernels seeking a better balance between performance and battery life. The way I use my phone, I won't last a full day with original kernels. But I must admit that if I had an app to tweak Omni's original kernel myself, I'd do it (I don't got the knowledge to dev my own kernel, thought).
Entropy512 said:
Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).
Click to expand...
Click to collapse
Would you like to impelement CPU and GPU overclock?
Would you like to implement CPU and GPU undervolt?
Would you like to implement WIP governors like zzmoove?
I aksed only three questions from at least a few more, and I'm wondering if you could answer "yes" to at least one. Making custom kernel or custom rom is a great thing because we can push device to the limits, while doing so shouldn't be suggested neither implemented in any official kernel.
JustArchi said:
Would you like to impelement CPU and GPU overclock?
Would you like to implement CPU and GPU undervolt?
Would you like to implement WIP governors like zzmoove?
I aksed only three questions from at least a few more, and I'm wondering if you could answer "yes" to at least one. Making custom kernel or custom rom is a great thing because we can push device to the limits, while doing so shouldn't be suggested neither implemented in any official kernel.
Click to expand...
Click to collapse
Voltage control/overclock - The stability issues these cause isn't worth it. Especially undervolting - at best it saves 3-4% on CPU core power savings, which is only 1-2% of system power even when the cores are at full tilt.
Alternate governors - These will have to, of course, go through review as to whether they have a valid reason for existing. 90% of alternate governors out there achieve nothing that can't be achieved merely by tuning the defaults of existing ones. Many of them are 100% marketing bull**** - Lionheart being the most blatant example. (Lionheart is nothing more than conservative with the minimum polling rate limit properly fixed...)
Entropy512 said:
Voltage control/overclock - The stability issues these cause isn't worth it. Especially undervolting - at best it saves 3-4% on CPU core power savings, which is only 1-2% of system power even when the cores are at full tilt.
Alternate governors - These will have to, of course, go through review as to whether they have a valid reason for existing. 90% of alternate governors out there achieve nothing that can't be achieved merely by tuning the defaults of existing ones. Many of them are 100% marketing bull**** - Lionheart being the most blatant example. (Lionheart is nothing more than conservative with the minimum polling rate limit properly fixed...)
Click to expand...
Click to collapse
Of course you're right but if we're talking about gaming then in long-run uV can actually benefit users a bit more that 3-4%.
The most interesting thing is OC. It's always nice to have a bit more power than usual if you're using it only for a short time. This way you get real performance boost when it's needed, for example when CPU is doing a longer task. Nobody gets hurt if CPU will work at let's say 1.6 GHz instead of 1.4 for a few seconds.
I understand what you're trying to say and I totally agree with you. Most of the changes could be and should be contributed to the base but still most of the devs (including me) wouldn't contribute non-universal device-specific changes.
Do you have anyone the extreme kernel v2.1 for the Xiaomi Mi9? and also what happens with Extreme Kernel website?
Why don't you ask the developer instead of starting spamming, again, the forum?
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Daenjel said:
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Click to expand...
Click to collapse
Arter is a good boy. Always working on f2fs.
BTW why people need that stupid kernel with high antutu score?
Kollachi said:
Arter is a good boy. Always working on f2fs.
BTW why people need that stupid kernel with high antutu score?
Click to expand...
Click to collapse
People seems to be so superficial sometimes, they base the performance of their devices on just numbers without knowing what the OC does to the CPU/GPU and the components in general, just to get those fancy numbers..
I need this kernel because in the last 2 months I'm using the extreme kernel v5 60hz and I have 10-15% better performance...yes on Android games my phone overheating but on any emulator for example dolphin, ppsspp, damonps2pro my phone isn't overheating with gaming and screen recording at the same time. Also on Android games through the Extreme Kernel Manager I choose lower GPU frequency (450 mhz) on these games and better cpu/gpu mods (for throttling at a higher temperature than normal) and I have supper stable gaming without framedrops. So I need in a few months the overclocked Snapdragon 855 with 30%, or the lowest 20% gpu overclock (blackshark 2) for emulators, for better content on YouTube (my name is Greece Mobile) and the comparisons with my future Laptop (gtx 1050, i7 6cores 12 threads). Also the overclocked Snapdragon 855 it has almost similar performance than the gt 1030 and also on my YouTube channel I will test on 2-3 weeks the Malakas Kernel, the most optimize kernel for the Pocophone F1 with 9400 geekbench score without cpu overclock and similar GPU overclock than the extreme kernel.
Overclocking should become a habit, especially as nanometres becomes smaller.
Big wall of text for a YouTube channel advertising.
Nuno Oliveira said:
Big wall of text for a YouTube channel advertising.
Click to expand...
Click to collapse
Not exactly.. This is my love and also I watch these videos since 2014, techutopia, unbox therapy and many others YouTube channels famous or not
Also just yesterday I discovered how I can play the only IR nunchuck + wii remote games like COD 3, COD Modern Warfare Reflex Edition, Moto GP 2008 and many other << unplayable >> Wii games and I am very happy ?
Great advertise...
Also, I wont tell you why OC on mobile devices is bad and didn't make sense over the last 5 years, you can search it for yourself, but yeah, this kernel/project is officially dead, at least that's what the "developer" said on his Telegram channel, if you found a backup/old ver. then great! But don´t expect updates soon..
Daenjel said:
If I'm correct, it was cancelled by the developer itself after a scandal due by the amount of kernels build for many devices, that the developer didn't had to test them by himself. This means that this entire time, he was building blindly and OC blindly as well, for all those devices..
You can find more info on twitter's account of Arter97, the recognized dev. who discovered and brought to the surface everything wrong with this stuff.
Click to expand...
Click to collapse
That's how the vast majority of custom ROMs are built these days. More often than not the ROM devs aren't aware of bugs until users report them. Some devs build ROMs for devices they don't even own or for devices they do own but don't actually use.
This is especially the case with ROMs and kernels for OnePlus phones because devs don't use OnePlus phones but it happens with many other brands and models as well. Bugs are now normal and expected on "stable" builds of custom ROMs. That was not the case 5 years ago. Back then CyanogenMod was the only custom ROM that always had bugs--because they were building for so many devices they couldn't do proper testing.
I'm not sure why there would be a scandal because the Extreme Kernel was built like virtually every other custom ROM and kernel.
jhs39 said:
That's how the vast majority of custom ROMs are built these days. More often than not the ROM devs aren't aware of bugs until users report them. Some devs build ROMs for devices they don't even own or for devices they do own but don't actually use.
This is especially the case with ROMs and kernels for OnePlus phones because devs don't use OnePlus phones but it happens with many other brands and models as well. Bugs are now normal and expected on "stable" builds of custom ROMs. That was not the case 5 years ago. Back then CyanogenMod was the only custom ROM that always had bugs--because they were building for so many devices they couldn't do proper testing.
I'm not sure why there would be a scandal because the Extreme Kernel was built like virtually every other custom ROM and kernel.
Click to expand...
Click to collapse
Yeah you're right, but it doesn't meant that it should be that way.
Building blindly is risky as always, and yeah, every time you flash something to your device , you're doing it by your own risk, but it doesn't mean that the developer can just overclock your CPU/GPU, fill a kernel with "gosht" features and call it a day.. Or even don't knowing that overclocking a cpu/gpu blindly, could lead to "kill" the device in a near future...
Btw, this wasn't the scandal from where he left his projects, it was a lot more behind, that's why I said that everyone should visit that Twitter account from before, to learn why everything from this particular kernel wasn't okay at all...