yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Rem3Dy:
For me the issue is the undervolting is to low for my phone. The 100/200mhz values cause the phone to freeze requiring a battery pull:( I just wish we had the control to change voltages to suit our phones needs
[Nexus S Android Development] dsellers2:
He has said many time it wont happen. Not sure why, not sure I care either cause his kernels work for me. But If they did I would probably try to grab his source and learn to compile it myself after changing the voltages. But since they work I wont. :) I have seen some other kernel here based off Morfics source but higher voltages. At least I thought I did.
[Nexus S Android Development] khartaras:
Thermite still doesn't boot for me, but...

OH **** is Gigglebread fast. Sorry Taichi but Gigglebread is just crazy fast with T11.
[Nexus S Android Development] Serious_Beans:
Why is 04/10 your favorite compared to 05/10?
[Nexus S Android Development] benrees21:
Can someone explain what these "kangs" are? I'm looking under gigglebread/kangs. Might flash it when I've got some details on what it is. Also if your already on it then let me know how it performs etc. Thanks.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] simms22:
its pretty much the same as 05/10 but its the s22 version. it was the test version to 05/10.
[Nexus S Android Development] red_skittles:
from what i understand, kangs are nightly builds of CM that incorporate different CM features that haven't yet made it into the official CM builds. So in terms of cutting edge features i guess theyre ahead of the nightly CMs if youre the type of person that always wants the latest and newest
[Nexus S Android Development] benrees21:
Ok thanks :-)

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] morfic:
Just a heads up, when you see your phone charge to 100%, cm style, it's just cosmetics. Nothing will happen to your phones.
[Nexus S Android Development] simms22:
if you actually want to reach the real 100%, youll still have to bump charge(or charge with wireless tether on). because, as morfic said, its just a cosmetic 100%. its not tbe real thing.
[Nexus S Android Development] cabstrak:
:eek: So because it's just a cosmetic, I guess Trinity won't be including them?
[Nexus S Android Development] morfic:
The heads up was intended to ease the mind of those who freak out over 100% battery, it's in Trinity right now, but likely only thermite users know this.

And I don't want to have people freak when I build the other speeds and they see the battery full.

I don't like blx, I don't mind a cosmetic fix that shows full when the battery was safely filled.
[Nexus S Android Development] GeezyAF:
I couldn't get past the splash screen with the thermite Simms just posted a bit back, lol.

I'm hoping it's just me trying out MIUI.

Running T144 wonderfully though!

Nice change of pace from running TEUV forever.
[Nexus S Android Development] belair56:
F.Y.I. , Morfic

Update on my silly "non-reboot to recovery" phone.

Interestingly it DOES with THERMITE-S22-optos. Does not with TEUV-NS-19102011.

Not *****ing, just want to share.
[Nexus S Android Development] morfic:
Thermite has that name since it's special and not your normal Trinity.

The high bus even at 1GHz is unfortunately what makes it or breaks it at bootup.

Not sure if booting at 800MHz would be a real fix.

At least you could boot and download another kernel. ;)
[Nexus S Android Development] morfic:
The successrate of thermite actually makes me think I need a 1GHz max bigbore again.
[Nexus S Android Development] simms22:
thats an idea ;)
[Nexus S Android Development] kjaved373:
Anyone having the problem where the screen goes green when on lowest brightness or screen dims?

I'm using latest Miui with TEUV kernel.
[Nexus S Android Development] Paul627g:
I just wish I could run this kernel :(

I've overwritten current setups on Oxygen 2.3, I've done a full wipe and reinstalled everything from scratch on Oxygen 2.3 and still can't get a successful running on this kernel...

Either get boot loops during the flash and when I have gotten a good flash and thought everything was going to be good then I get random reboots, lock ups and other issues.. It varies..

NS4G/Oxygen 2.3

TEUV-NS-05102011 (0.88GHz with 220MHz bus/gpu,ExtraUnderVolted)

Just won't work for me :(

I guess I fall into that small percentage of devices that just don't react well to a certain kernel.
[Nexus S Android Development] ragnarokx:
Perhaps the voltage is too little for your phone. Try a TUV kernel instead :)

Sent from my Google Nexus S
[Nexus S Android Development] GeezyAF:
There's fixes for that.

Google "fix green dim miui"

Its like the second link.
[Nexus S Android Development] kjaved373:
Wow been running this for half an hour and its too fast now! This is what I've wanted since day one. I just hope it stays this way. :D

And ^, thanks! I usually google fixes but probably got a little lazy.

Sent from my Google Nexus S 4G
[Nexus S Android Development] GeezyAF:
Trinity is the best for me and I've tried them alL. I would've linked you a link to a fix but its too Mich work on a phone. Just glad you found it yourself.
[Nexus S Android Development] laidick:
The T11 1910 works perfect for me.

Just a dummy question..

I am using KelLMSKing MIUI, it has 'Daemon Controller'

while BM MIUI has 'No-frills CPU Control'

and I found that most of the people is using SetCPU

Which of the above is best fit with our Trinity kernel?

What are the difference?

Btw, I have installed a MIUI Theme with boot animation, however the trinity kernel has its own boot animation bundled, how can I restore to my themed one?

Thanks a lot!.
[Nexus S Android Development] chinopski:
openvpn

i cannot connect my openvpn app with this kernel.

please fix if possible. great kernel but i need to run my openvpn. thanks:)
[Nexus S Android Development] benrees21:
This is to do with voltages. When the voltage is too low it won't reboot into recovery. I had the same problem before.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] benrees21:
I just want Thermite with a 1.3ghz step. :-)

It is a really great kernel though. Best I've ever tried. Thanks.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] albundy2010:
Is thermite running a 250 bus for 1ghz?
[Nexus S Android Development] akshayf:
Been away for a while guys... Can someone please tell me what is this new thermite thingy?? Thanks
[Nexus S Android Development] morfic:
Share a little detail, tun.ko is included, OS might look in wrong place to install it.

If you manually install it, does openvpn work?
[Nexus S Android Development] chinopski:
i've been using NScollab ROM with matrix or franco's kernel, and openvpn is working fine.

i can run openvpn on trinity kernel but i just can't connect. only upto the "Get Config" notice.
[Nexus S Android Development] morfic:
When you get that notice, go to terminal emulator.

Make sure you have # prompt. Type su if you are not.

Type lsmod

Does it list tun as loaded?

Iirc, kiddo is building it in, I have tun as module.

I can build it in if the setup doesn't take care of loading the module.
[Nexus S Android Development] morfic:
Yes.

Edit: try running nenamark at 1000/1000
[Nexus S Android Development] melvinchng:
Why my ass or battery get burned?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] dario3040:
From my understanding it's like T144, just with 40Mhz more, which also increases the bus speed a bit.
[Nexus S Android Development] melvinchng:
T144 bus 250 at 1ghz OR/AND T11 too?

Will battery life effected?

250x 4 = 1ghz

200x 5 = 1ghz... both are same.. voltage too right?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] albundy2010:
Thanks that's what I thought. I seen you mentioned people can't boot due to high bus speed and just wanted to make sure.

I was expecting my phone to not boot but apparently it can do high bus speeds but not clock speeds.
[Nexus S Android Development] melvinchng:
Are you using t144?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] Maximilian Mary:
Would flashing trinity over the CM boot image enable init.d scripts (and possibly fix other issues) on the stock ROM?
[Nexus S Android Development] albundy2010:
No. T144 is not for me. I don't actually want to run at 1.4 but its not stable anyways for me. 1ghz is fine but no reason to run that at 1ghz over the tuev / tuv kernels. I could run 1440 on other kernels if I push up the voltages but basically none of them run without adding more voltage.
[Nexus S Android Development] morfic:
Was hoping *your* fingers.
[Nexus S Android Development] morfic:
Matrix 1440 != Trinity 1440

What was the total CPU voltage on other kernels?
[Nexus S Android Development] albundy2010:
I can't remember exactly. Sometimes only plus 10 others 30 with proton. Since I tested a couple of them and mathkid was adjusting his stock values at the time.
[Nexus S Android Development] simms22:
its possible, if they dont get deleted by trinity. but, chances are, it wont help.
[Nexus S Android Development] ogbreds:
T11 blazes.
[Nexus S Android Development] morfic:
Stock stock won't have init.d support with a "anykernel" as no changes are made to the ramdisk.

Flashed over cm's kernel or any other that has init.d support the 98tweak improves on a few items, I doubt it solves problems. It's meant to make things better without having to touch the ramdisk.

Reduce stalls is a big part of the tweaks.
[Nexus S Android Development] franciscofranco:
Like I said I would, I come here to tell you that deadline with fifo_batch tweak is definitely better than VR ****, you were right.

And your dirty writeback values are much better than the logic I was using with my previous values!
[Nexus S Android Development] morfic:
You are welcome :)

Guess it's indicative of collaboration being a good thing :)
[Nexus S Android Development] franciscofranco:
Yes, when the collaboration is constructive only good things can come from it!

Ah and I used your tweaks to the Conservative governor, and guess what, I never knew this governor could perform so good, I usually neglected it :o
[Nexus S Android Development] morfic:
User request, Tonky is happy now. :)
[Nexus S Android Development] franciscofranco:
Tonky and me, very happy :)

Keep up the good work on the kernels ;)
[Nexus S Android Development] DJTaurus:
Guys which version do you flash....Normal or Experimental and whats the difference?

http://www.derkernel.com/
[Nexus S Android Development] morfic:
Experimental is where right now all the deep idle patches are

Stable is the builds before deep idle was introduced.
[Nexus S Android Development] mike216:
Using your tweaked conservative governor on MK kernel and its amazing on speed,checking battery out tonight,thanks morfic

Sent from my Nexus S
[Nexus S Android Development] morfic:
On what kernel ?
[Nexus S Android Development] mike216:
Mathkids

Sent from my Nexus S
[Nexus S Android Development] dreisus:
Can someone tell me what's the difference between all of those different termites
[Nexus S Android Development] simms22:
thermites ;)

the differences? some are faster, some are slower, some dont boot. thats if youre talking about the simka folder.
[Nexus S Android Development] GeezyAF:
For being an "experimental and beta build," t11 is amazing. I think the CPU and bus speed are an amazing blend. I haven't had an issue with it, yet haha.
[Nexus S Android Development] window7:
Hey morfic, here's a report of crash by tatwamasi

Rom: BrainMaster MIUI

Kernel : T11
[Nexus S Android Development] ellesshoo:
"stable " for me is unusable except for TUV10. All the OC versions crash seconds after moving the max cpu past 1ghz. TEUV crashes off and on. I can run some older "stable" builds just fine though. I was lucky enough to have saved builds from late August and late September that are rock solid for in TUV10, T12, and T13 flavors. Even the usually hopeless T144 from those days would get through a quadrant run before locking up.

All the current experimental versions are in the flavors that lockup too much to even test out for me (but of course I tried at first).

Morfic, any reason why TUV10, T12, and T13 aren't getting any love lately? I can't figure out why not a single stable build from 10/5 will work except for TUV10.
[Nexus S Android Development] Lazat:
Is the conservative governor tweaked in all the kernels? Or do I need to download a special one :) ? In that case, where do I find a Trinity kernel with the conservative governor tweaked :) ?

Thanks
[Nexus S Android Development] melvinchng:
The thermites with 250 bus never boot up here :)

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] melvinchng:
Btw, this thread is hotter than Morfic kernels. :0

Anyone getting a bench for ICS???

http://xdaforums.com/showthread.php?t=1313337

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] polobunny:
Showing some love for your kernels morfic, so far so good. I enjoy testing all those I can tests, running benchmarks and going through a day or two to see how stable they are.

Most 1.1Ghz and under I can run fine, they're stable enough to be daily drivers.

I especially like testing TEUVs, I get awesome battery life from them.

Exception being THERMITE-S22-optos. It's a no go, boot loop town. Guess that's too extreme for my phone. :(

Most stable TEUV seems to be TEUV-S22-04102011. I saw there's a few new simms22 thermites from yesterday night, I'll check them out later. Hopefully I can find a good kernel with lazy, deep idle (whenever it's completely bug free), good battery life and good performance. :D

Continue the good work!
[Nexus S Android Development] dario3040:
I'll do one after it finishes downloading, really slow download.
[Nexus S Android Development] melvinchng:
Please let us know

-data

-camera

-WiFi

-Bluetooth

Are working properly?

Cause no one is answering my question... thanks buddy!

Is it possible to stack UV kernel on 4.0?

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] polobunny:
Camera FCs once then works, wifi flickers on and off and my data won't connect. Can't use another locale other than the default english otherwise you get more FCs, but calls work fine. Haven't tested tons of things, it's not ready for prime time just yet obviously but it's a real good start. I haven't even tried recovering my apps with Titanium, but it's fun to install then restore your nandroid. :)

Edit: Haven't tried flashing morfic stuff over 4.0.
[Nexus S Android Development] Naa Laa:
Morfic,

Last night my battery died all of a sudden to zero (got late to work today). I am using TEUV-19102011 (experimental Nexus S version).. I have it since the day it was released on your website. Cant really find the culprit - under battery usage it all looks normal to me. The only thing I had different was - flashed new radio image yesterday on my Nexus S (XXXKF1 signed). Do you think the new radio is the culprit? I had XXXKD1 unsigned before. I also have no idea between signed and unsigned radio.

Thanks and any help would be appreciated.

Should I flash the stable version of the TEUV kernel?
[Nexus S Android Development] dario3040:
If Morfic's kernel works I'll **** brix.
[Nexus S Android Development] morfic:
I don't think you have to prepare for a world of pain.
[Nexus S Android Development] morfic:
I went back to kd1, with kf1 I had worse reception and this worse battery life.
[Nexus S Android Development] morfic:
Gimme a paste of the output of:

cat /proc/version

And

cat /proc/meminfo

Just curious
[Nexus S Android Development] dario3040:
Does it work then?

(don't want to risk a wipe)
[Nexus S Android Development] morfic:
If it works, you **** bricks, which Is surely painful.

I don't think you will be in pain
[Nexus S Android Development] dario3040:
I can't handle these mind games after that horrible museum.... :)

Is that a yes, or a no?
[Nexus S Android Development] polobunny:
I went back to NScollab 1.0.50 for the moment though. If I can find some time I'll do it, but that likely won't be before tomorrow.

(yes I'm surfing xda at work)
[Nexus S Android Development] benrees21:
So...Morfic, what you working on at the moment?

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] polobunny:
I bet a 5 he's churning out more high bus kernels for simms to try. Just a gut feeling. ;)
[Nexus S Android Development] Babydollll:
They are also builds that are NOT compiled on CMs "buildbot". Official nightlies and Any other OFFICIAL CM build (RC, Stable, ect) are compiled on the "buildbot"

Although, I think the biggest draw these days are the cherry picks from the gerrit.

Pipsqueak approved this message
[Nexus S Android Development] benrees21:
I seem to be able to run a high bus speed but can't get over 1.3ghz clock speed. Is that weird or just a normal occurrence?

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] polobunny:
Perfectly normal. Take into consideration every part in your phone has met the acceptable tolerance level Samsung has set for the Nexus S. Some get lucky and will be able to run a high bus frequency, a high CPU frequency, a high GPU frequency and even a big undervolt. Others will only be able to run everything at stock otherwise they will get undefined behavior.

Anything over the stock frequency set for the components is something you get without a warranty. You're into unknown territory and nobody can tell you with 100% certitude it will run on your phone.

For what it's worth I'm quite happy with the TEUV's, they're definitely snappy like stock (and even snappier in certain situations) and offer better battery life. Good little daily drivers. I get a reboot every 2-3 days, then again it could be my own fault for messing with too much stuff at the same time. :P
[Nexus S Android Development] benrees21:
I can get a little undervolt on my phone but not too much or it reboots. I find that when you UV the phone ain't as responsive even though your using the same clock speed, but I guess my phone just don't like UV.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] polobunny:
If it's not as responsive then it's likely your phone doesn't like it, as you said. One time or another it would crash on you with those settings. ;)

You get a free thanks, the quote button is next to it. Oops!
[Nexus S Android Development] simms22:
theres a Thermite15-S22b in the simka folder. 1.504ghz with a 250.666mhz bus speed. if anyone is willing to sacrifice their poor NS. mine LOVED the torture test :eek:
[Nexus S Android Development] polobunny:
Jealous. Wish I could touch the Thermites. :P

Might still try later though, who knows maybe it was just a fluke and they will work, not throwing me in a boot loop?

Are you still using TEUVs as your daily drivers? Currently using TEUV-S22-04102011 if I recall correctly. Loving it, just thinking you need a cool splash & bootscreen. :cool:
[Nexus S Android Development] simms22:
thats still my daily driver too, except for today. today i used thermite optron4. battery life wasnt bad at all. 7 hours fairly heavy use and 42% battery was left(before i flashed thermite15). whats wrong with the S22 splashscreen :eek:
[Nexus S Android Development] polobunny:
Just isn't as sharp as the Triny "boom" one in my opinion. Plus it's not animated. :p

Edit: What's the difference between all the optrons anyway? Yeah, some people are flashing them blindly like I am hahaha
[Nexus S Android Development] simms22:
i was flashing blindly too :-P

some are faster/slower, and some wont boot. 4 and 5 seem to be the best.

flashing blindly = crackflasher :D
[Nexus S Android Development] polobunny:
What is their CPU frequency and bus speed?

I couldn't run optos so if it's 250 on the bus chances are I can't touch it. Still gonna try it though, can't blame me for willing for them to work.

Edit: I'm definitely addicted to flashing zips. :(
[Nexus S Android Development] simms22:
thermite 1480mhz 250 bus

thermite15 1505mhz 250.666 bus.

its a good thing that these are pay per flash ;)
[Nexus S Android Development] benrees21:
Can you link me to the folder please. Thanks.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] melvinchng:
My bull sh*t phone won't even start in 250 bus.. I think... just as usual

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] Hostile89:
You're not alone Melvin. Mine doesn't like it as well.
[Nexus S Android Development] simms22:
simka http://goo.gl/Dn8Bs

with these you are on your own, meaning they are highly experimental. some of them have been renamed and turned into stable. some never make it out of the simka folder. some wont boot. and some run like theres no tomorrow(like forrest gump :p )

thermite15 S22b is the latest(1.504ghz), and the thermite optrons are from last night(1.48ghz), optron4 and 5 ran the best for me.
[Nexus S Android Development] benrees21:
Thanks. Thermite15 S22 or S22B?

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] simms22:
15b. 15 was slow, maxed out around 1700 in quadrant. 15b maxed out at 6089 so far :p
[Nexus S Android Development] benrees21:
Lucky I flashed B then! Yea it is all good here so far, runs nice. I can't believe the amount of kernels in that folder, it's like a sweet shop! Only running at 1ghz, I would never get 1.5ghz :-)

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] benrees21:
Double post mistake.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] morfic:
Mmhhm, extra advertising.
[Nexus S Android Development] simms22:
yea, it is like a treasure trove of kernels. some of them are priceless.
[Nexus S Android Development] benrees21:
Lol. Since your here Morfic, please do me a Thermite build with a 1.3ghz step. Pleaseeeeeee. Even just add it in to thermite15 S22B. These kernels are definitely the best around without a doubt! Thank you.

EDIT: Well it's nearly 2am here in the UK and I'm off to bed. Will see what tomorrow brings *wink wink* lol.

Sent from my Nexus S burning on NSCollab and Morfic's Thermite Beast Kernel!!!
[Nexus S Android Development] roshga:
ohh! I love the new termite and it loves me back (:

my phones seems to run everything out of morfic's kitchen. Well, except for that 1.666 devil one...
[Nexus S Android Development] morfic:
Someone's been cheating, looking at the simka folder file dates!

Just playing with tweaks, see if I missed something. Try new stuff, that's why some kernels have such funky names, they are just acronyms to help me remember.
[Nexus S Android Development] melvinchng:
Hmm... just a feedback. I didn't use the v6 charger anymore. And I will get a two seconds lag almost daily.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] simms22:
:eek::eek::eek:

blah blah blah benchmarks dont mean anything anyways.. :-P
[Nexus S Android Development] Hostile89:
lol.

What kind of sorcery is this?
[Nexus S Android Development] corythug:
I want!
[Nexus S Android Development] simms22:
Thermite15-S22b kernel for the Nexus S and NS4G.

1.504ghz cpu with a bus speed of 250.666mhz. benched at 1504/1504 ondemand. scores higher after the phone has warmed up!

download--> http://goo.gl/F722A

FLASH AT YOUR OWN RISK

Thank you morfic for this work of art
[Nexus S Android Development] melvinchng:
Quadrant said it is too fast to test. So it considered to give you 6.1k instead of 10.1k.

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] HeavenlyWinds:
Holy cow! That's crazy!