yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] simms22:
new SEXY boot image too! heres a video http://goo.gl/tkEoE :D
[Nexus S Android Development] jlevy73:
Quadrant from the last morfic kernel
[Nexus S Android Development] morfic:
http://goo.gl/2uSLV

Try this on stock roms, it SHOULD work, make sure you have a backup kernel already in case it does not.
[Nexus S Android Development] jlevy73:
I'm finding this latest kernel to be a bit unstable. Every time trying to play dungeon defenders it's caused a bootloop.
[Nexus S Android Development] willcpfc:
Flashed the latest cm kernel and I like the new boot picture :) thank you.
[Nexus S Android Development] morfic:
Nothing changed from what you tried earlier, just bootlogo is new.
[Nexus S Android Development] alturismo:
same here, many issues also with UV kernel, new boot logo is pretty nice actually ;)

black screen, open app like gallery, cam, ... lets phone reboot sometimes ...

widget locker stopped and no way to start anymore

running cm7 #23

edit.

after the 3rd reboot now wifi error ;)
[Nexus S Android Development] jlevy73:
Figured as much. Will try wiping and reflashing.
[Nexus S Android Development] kfjunky:
So I thought, but after an hour or two, same with the Bionix kernel, browser stops downloading. Also tried the stock version, but couldn't boot.

Please, please, Modaco version:o
[Nexus S Android Development] DebauchedSloth:
Thanks. Am doing that. Would like to add overclocking.

Please attach your patch files. I repeat: you are hacking on a GPL source base. You should release your changes.

Thanks.
[Nexus S Android Development] twistywizard:
Has anyone tried the Trinity13 with R10 Modaco ROM? Does it have the Download issue people have mentioned?
[Nexus S Android Development] alturismo:
Are you guys using setcpu again with UV Kernel?

I cant get it stable here ...

Flashed back and forward again so at least BT works again.
[Nexus S Android Development] simms22:
he'll release it when its ready. meanwhile he has more important things like his life and family to take care of. as far as i know, the world doesnt revolve around you. when the spare time is available to morfic, im sure it will be taken care of. ive seen you asking for it repeatedly, as im sure morfic has. i repeat, stop being an a-hole.
[Nexus S Android Development] www1:
I have a lot of problems with CM7 lastest KANG 31/01/11.

Reboot FC.

I try to reflash and fix permission with any luck.

With previous version of kernel and Cm working good.
[Nexus S Android Development] irishrally:
I'm finding the original CFS version of the UV kernel to be the most stable. Very interesting how our phones behave so differently with these mods. Do your electrons flow downhill?
[Nexus S Android Development] DebauchedSloth:
Releasing it is a simple diff (or even zip it up, trivial), not asking for much here (five minutes, max), and have been extremely patient. He's right, all of this could be done using the base stuff an scrounging around the various kernels that HAVE released source, but the idea of open source is to build on what others have learned. Hard to do that without source, eh?

It's GPL, you are distributing it, distributing source is a requirement.

Yes, people do tend to get a bit touchy around patches for GPL code not being released. Take a look at cyanogen's twitter feed, for example.
[Nexus S Android Development] simms22:
see, the thing is you are right. at least to a point. the only thing youre not right about is the time frame. youre not taking into consideration his personal constraints. i know for a fact hes working a 12 hour shift today at work. after that he has his family to deal with too. that will always go before any of his dev work. as you know, most of the devs are doing this work just for the love of it and on whatever personal time they have. yes, he should release his source, thats part of the devs responsibility. and im 100% sure that he will. but it will be on his time frame, not yours or anyone elses. you do not have the right to demand that he does it asap, over and over again. what you should do is, instead of asking in the thread over and over again, is write him a pm. be understanding. maybe he has some clean up of the code to do before he publishes it, but just hasnt had the time. maybe you both could even find a happy medium. maybe HE needs some help and YOU could help him out. what i do know is the more someone pushes me, i tend to push back. understand? i hope this makes some sense(not the htc kind :p )
[Nexus S Android Development] DebauchedSloth:
We've been politely requesting the source for a month now. Now, if that were a difficult or time consuming request to fill, I'd agree.

It's not. All of these files should be in one directory, and a simple zip will pull them all, then the rest is as easy as uploading a zip file.

Here, let's make this simple:

Morfic, I'd love to help. Dump me the changed files. Just zip up the whole platform directory. Attach them here or let me know where they are. Should take all of 30 seconds. I'll integrate them into a kernel tree and put them on github for ya - so that pulling them is as simple as pulling the Voodoo improvements is. Heck, I'll even use the Voodoo improvements as a basis for the kernel, so we can have both changes in one place.
[Nexus S Android Development] DebauchedSloth:
Looks like Netarchy is already headed down that path, and we now have an overclock kernel with source out there.

Excellent - I'll just use that.
[Nexus S Android Development] kenvan19:
Edited because unnecessary.
[Nexus S Android Development] thegod2012:
Can't we'll all just be friends
[Nexus S Android Development] simms22:
as far as i know we're all still friends :D
[Nexus S Android Development] morfic:
No it's all about RTFD and KWTFYD, copy / paste teaches you nothing, do not pretend, stop wasting more of my time.

I watched a smart guy recently overclock his kernel in mere minutes, he RTFD, and he gets a grasp, and i will provide any help to him i can, in a way that works for me, providing source (and i will) is not going to teach you nothing.

Not that you actually strike me like the kind of guy who is interested in learning.

I will release code, not now, i have no finished stable product that source would belong to.

I don't expect you to understand the reasons why i rather fight my way through my aversion to git than to release it in a way i do not find it useful. But i will do it on my time when i have a product it belongs to.

Until then i am happy for every user who gets a use out of test versions i am releasing on the way.

The documentation i suggested with RTFD are on XDA btw, you will find several references to me correcting "1.6GHz" kernels on at least 2 SGS variant device threads.

I share, i help, it's a thrill seeing someone i helped get going become as good or better than me (and i don't mean just forums/internet, i mean my work as well)

Did my answer satisfy you now?
[Nexus S Android Development] morfic:
Thanks, now the whole lord splitting you thing in places, yeah, door stage left.
[Nexus S Android Development] jlevy73:
How about those Spurs :p
[Nexus S Android Development] morfic:
New #NexusS Trinity UV | http://goo.gl/wUJBu cm7 | http://goo.gl/GmH4W Bionix NS | Should address reported game freezes.
[Nexus S Android Development] jlevy73:
Thanks morfic time to throw dungeon hunters at it
[Nexus S Android Development] simms22:
dungeon hunter plays well.. then reboot.

at 1000/100 dungeon defenders plays a little then exits. at 1000/1000 it froze :eek:
[Nexus S Android Development] simms22:
From morfics twitter...

its got the performance and the voodoo!
[Nexus S Android Development] jlevy73:
I'm getting the play for 30 seconds then freeze problem.
[Nexus S Android Development] RinTinTigger:
I LOVE the 14bv3!!
[Nexus S Android Development] thegod2012:
started playing Heavy gunner as soon as i started shoot in froze

i just flash it over my old uv kernel
[Nexus S Android Development] avetny:
link is dead :(

http://goo.gl/NVfuo
[Nexus S Android Development] avetny:
Hello people! If I understand correctly mr. morfic already make 1.4Ghz with oovooo sound add. This is true? Thank you.
[Nexus S Android Development] TheMorpheus:
This is quadrant in my device:

Now let see how is stability!
[Nexus S Android Development] avetny:
how much this kernel can overclock?:confused:

____

1gHZ
[Nexus S Android Development] alexis_p3300:
after testing kernels,i 'm feeling that v13 2.14 is the most stable,good performance for my nexus,much faster than 1.2,not to slow vs >1.4
[Nexus S Android Development] TheMorpheus:
If I remember correctly, I had to remove it... too many reboots, 1.4 GHz
[Nexus S Android Development] avetny:
should we wait update on "1.5Ghz or 1.6Ghz_CM_alpha ?????"
[Nexus S Android Development] morfic:
Only the 1ghz UV kernel has voodoo sound right now.

Trying to stabilize that first.

Then push to github.

Then branch and add oc versions.

The 1ghz UV kernel is no slouch. Just sayin

Sent from my Nexus S Trinity
[Nexus S Android Development] avetny:
THANK YOU!!!!!!!!!!!
[Nexus S Android Development] scottb75:
I've been running the 1.4 GHz CM7 Kernal for 2 days now and I've had zero stability issues so far (no reboots, no crashes, and no freezes), just blazing speed. I'm half tempted to try the 1.5 GHz CM7 Kernal with the next CM7 nightly.
[Nexus S Android Development] simms22:
the trinity15b is my favorite of the kernels. it runs very stable over here. if 14 is stable for you, 15 probably will too
[Nexus S Android Development] grubynawro:
Morfic, when will we see UVOC kernels? This is next step after UV?
[Nexus S Android Development] jlevy73:
Look 4 posts up from yours.
[Nexus S Android Development] mylexon20s:
I down Loaded the 1.3 kernel and would like to flash it with SGS KERNEL, my question is that I'm currently rooted, but on the stock rom. Can I flash the kernel, or is it preferred to be on a custom rom..

Any info would be appreciated
[Nexus S Android Development] grubynawro:
I know, maybe more concrete date, but i know too, that morfic has not much time for developing.
[Nexus S Android Development] avetny:
Thank u boss!
[Nexus S Android Development] morfic:
Soon? Might have something by end of week. Went lower yet on UV kernel voltages first.

Feel the need to build a voodoo sound oc kernel next.

UVOC I have yet to decide what compromise to make to get what I want

Sent from my Nexus S Trinity
[Nexus S Android Development] simms22:
via twitter... new kernel :D
[Nexus S Android Development] icandy75:
New kernel seems rock steady, love the steps in OC, new boot image and Voodoo sound. Is it my birthday?
[Nexus S Android Development] morfic:
Yes it is, simms22 special ordered you this kernel.
[Nexus S Android Development] Xandlinger:
New bootscreen is awesome. Loving tyre new kernel.
[Nexus S Android Development] willcpfc:
Wow a vari speed kernel...is this adjusted by setcpu? Sorry for my ingnorance :) I am new to this kernel game, nexus, super devs and xda have shown me the light!
[Nexus S Android Development] icandy75:
You can use setcpu or OSMonitor from the market.
[Nexus S Android Development] tempera:
With the new kernel with CPU adjustments, I keep getting reboots every minute. I run the 1.5b trinity and have no reboots?

Any suggestions?
[Nexus S Android Development] willcpfc:
Hmmm for some reason setcpu would not work at all...just a blank screen. And my wifi died. May try it all from scratch tomorrow and see if a fresh install helps.
[Nexus S Android Development] bananis:
i'm using trinity14b v3.0 cm7 with cm7rc24 and quadrant only has a result of 1300...

i'm not using setCPU or anything similar...
[Nexus S Android Development] simms22:
install setcpu or something similar. then crank it up to 1.4ghz, youll notice a difference ;)
[Nexus S Android Development] bananis:
booyah...

edit: ok, i'm starting to think my trinity kernel has wiped with one of the cm7 updates (i assumed cm7 update doesn't wipe the kernel) as setcpu only alows me to slide up to 1ghz.
[Nexus S Android Development] kenvan19:
Every time you install a custom rom it comes with a kernel unless otherwise specified. CM7 comes with its own kernel and therefore whenever you flash it you overwrite any pre-existing kernels.
[Nexus S Android Development] bananis:
ok, i feel more educated now...

Thanks.

trinity rom reinstalled - and set cpu cranked up to 1.4ghz

skyfire now runs crazy fast....

muchos gracias senior.
[Nexus S Android Development] kenvan19:
No problem =) Happy things are working for you now!
[Nexus S Android Development] simms22:
you should give give the new trinity kernel a spin :D
[Nexus S Android Development] jlevy73:
Are you referring to the UV one?
[Nexus S Android Development] irishrally:
This one: http://xdaforums.com/showpost.php?p=11083621&postcount=1224
[Nexus S Android Development] jlevy73:
That looks nice, thanks for the link
[Nexus S Android Development] irishrally:
****, hit thanks in.stead of quote.

The latest kernel is great for me up to 1.2, but the phone freezes when I change to 1.4Ghz in setcpu. I've gotten the phone to work well with 1.4Ghz and 1.5Ghz in the past.
[Nexus S Android Development] jlevy73:
What's the thanks button. I don't have that option
[Nexus S Android Development] irishrally:
Pull the back cover off your NS and take the battery out. Then use a 1/8" drill bit to drill a hole in the top left corner of the battery compartment (closest to the camera). Make sure your hole is tangent to the top and left face of the battery cavity, as close to the corner as possible. Now take a tooth pick or an unbent paper clip and stick it through the center of that hole. This will depress the thanks button.
[Nexus S Android Development] jlevy73:
Yep, 1.4ghz crashes on me too whereas the non UV 1.4 and 1.5 do not crash.
[Nexus S Android Development] simms22:
yea, that one :D
[Nexus S Android Development] simms22:
you have 40 thanks... dont you know where they came from?
[Nexus S Android Development] irishrally:
I thought about this quite a bit before my last post. The chance of jlevy having never visited xda since the UI change and has solely used the xda app since then is almost nill.

EDIT: Simms, have you been able to bump up the latest kernel with setcpu to 1.4Ghz and above without issue?
[Nexus S Android Development] jlevy73:
Lol, I was using the xda classic skin which does not have the thank button. Just changed it to xda 2010 and voila I see it. Gave you a thanks btw :)
[Nexus S Android Development] jlevy73:
deleted....
[Nexus S Android Development] jlevy73:
Can I un-thank you :)
[Nexus S Android Development] irishrally:
Hah, I would have put money that you were pulling the piss. You can go into statistics and you can find all the people that thanked you and for which post.
[Nexus S Android Development] simms22:
ive had it at 1.5 since this afternoon. 1500/1500 earlier, and 1500/100 now. no problems except an occasional su issue with setcpu(which is easily fixed by killing that root app, then reopening it). no hiccups, freezes nothing. fast as heck!
[Nexus S Android Development] irishrally:
This is the best I can do with CM #26 and the latest Trinity kernel at 1.2Ghz (the highest I seem to be able to go):
[Nexus S Android Development] simms22:
hahahaha....
[Nexus S Android Development] jlevy73:
As soon as I put setcpu to 1.4 it just freezes and goes into an endless bootloop. I think simms has the jesus phone.
[Nexus S Android Development] jlevy73:
Your phone is a freak of nature my friend. When morfic has you test a kernel and it works, your pretty much the only person who gets to use it. I think one of us mortals should be added to the testing because your phone is representative of maybe 0.1% of all the NS's out there :p
[Nexus S Android Development] simms22:
truth.

my phone probably represents near the top for OC. so, if my phone cant run it, nobody can. but if i can run it, that means that there are others out there that can too. thats why this last kernel is nice, it boots up at a safe speed, then you can clock it yourself to whatever the ceiling is for your phone. i think the 1.3 and 1.6 options are coming soon too.
[Nexus S Android Development] jlevy73:
Well said.

The addition of 1.3 will be good. Most people should be able to run that imo
[Nexus S Android Development] tempera:
Any chance of the 1.5b kernel having voodoo? The new kernel doesn't even go to 1.4!
[Nexus S Android Development] RinTinTigger:
Ì only like a stable 1.5 in OP ;) the 14b_v3 works so awesome!
[Nexus S Android Development] Xandlinger:
The one linked earlier in the thread can go up to 1.5GHz... that is what I am using, anyway. Everything is stable as well, loving the voodoo sound.
[Nexus S Android Development] simms22:
i was running at 1.5ghz with voodoo all evening, but that doesnt matter. look what morfic has coming up, with voodoo :eek:
[Nexus S Android Development] rubino90:
what is the best kernel for bionix 3.1? not important the max overclock ( i prefer stable 1.2 or 1.3 ghz) because i work with phone i love the fast but is never without the control :) thanks for the reply
[Nexus S Android Development] adx_x:
what kernel can be used on cm7 nightly #26? Trinity14_V1.0 can't be used on cm7..
[Nexus S Android Development] rb9228:
I'm using Trinity Max which works fine for me.
[Nexus S Android Development] rubino90:
what is the best kernel for bionix 3.1? not important the max overclock ( i prefer stable 1.2 or 1.3 ghz) because i work with phone i love the fast but is never without the control thanks for the reply
[Nexus S Android Development] alexis_p3300:
Running on 1.5b with modaco r10 and feels perfect much snappier than 13,how about 1.6 is it stable ?
[Nexus S Android Development] adx_x:
mine can't boot into desktop,many fc disappear.
[Nexus S Android Development] tempera:
The thing is the new kernel just goes upto 1.2 for me but 1.5b is stable.
[Nexus S Android Development] asci:
Idem...

:(
[Nexus S Android Development] avetny:
"@morfique http://goo.gl/WLNS2 Trinity-cm7max Voodoo sound, 1000HZ, BFS, 1.2,1.4,1.5GHz Boots to a safe 1.0GHz pick freq your phone likes."

thank you !!!!!!!!!!!! 1.4 1.5 super stable !!!! (1.5 very stable:cool: !!!!!!!!! not like old one 1.5 !!!, i hope we gonna get 1.6 :):o

MORFIC you got GOLD hands !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! <3

(but didn't rich 4000 in quatro) :p
[Nexus S Android Development] icandy75:
1.6 is out for CM7 and will be out for Bionix after her gets some rest according to his tweet this morning.
[Nexus S Android Development] TheMorpheus:
I' ll definitely give it a try :cool:

EDIT:

Nope, too many reboots. Nandroid!
[Nexus S Android Development] avetny:
oooo good news bro;)
[Nexus S Android Development] rb9228:
You did wipe cache & dalvik cache, flash CM7 #26, GAPPS, Fix permissions, reboot, go back into Recovery then flash Trinity, reboot - in that order, right?

This method worked for me on both #25 (w/Netarchy Nexus 1.2) and #26 (w/newest Trinity)
[Nexus S Android Development] irishrally:
Anyone have any ideas why some of us could run the old 1.4GHz and 1.5Ghz well but can't push the latest variable kernel past 1.2Ghz? Maybe it has something to do with setcpu. I was thinking about reloading the old 1.4Ghz kernel, setting setcpu to 1.4Ghz and check set on boot. Then flash the new kernel and it will be forced to start at 1.4Ghz and may eliminate some glitch that may be caused by trying to increase frequency with setcpu while the phone has already booted. Probably wouldn't make a difference, just a thought.
[Nexus S Android Development] avetny:
you know + quatro score in old 1.4, 1.5 higher than with "latest variable kernel",+ Bluetooth, and superUser root request some time not working :D

but im sure he will fix everything ;) (maybe because it's first kernel "everything in one")
[Nexus S Android Development] wuyanks:
Looks like there are some issues with setcpu and this new kernel. every time i try to Autodetect frequencies, SetCPU hangs. Tried clearing cache and data for setcpu, and it doesn't fix the problem. a few times i had setcpu detect the frequencies, but pushing past 1ghz caused the phone to freeze and reboot.
[Nexus S Android Development] tempera:
Yeh can't even go to 1.2 with new kernel but can run 1.5 kernel stable!
[Nexus S Android Development] avetny:
it's not setcpu its "root rights issues"....just reinstall SETSPU
[Nexus S Android Development] simms22:
morfics twitter...

youtube video of Trinity16 MAX with #CM7 at 1.6ghz(1600/1600) stable and smooth on my Nexus S http://goo.gl/EmYGw enjoy :D

thanks @morfique
[Nexus S Android Development] avetny:
hahahhahhaahaah I LOVE IT !!! THANK YOUUUUUUUUUU

IM FIRST !lol
[Nexus S Android Development] tempera:
I really want my 1.5 back with voodoo!! The new kernel keeps rebooting on 1.4/5/6 but I can run the 1.5b stable.

Am I doing something wrong?
[Nexus S Android Development] tempera:
Forgot to add, I'm running modaco r10
[Nexus S Android Development] avetny:
HOLLY SHIIIIT ! lol 1.6GHZ working FASTER THAN MY D***CK !!!!! lololol
[Nexus S Android Development] willcpfc:
Did a fresh install with cm25 and the variable kernel. Unfortunately setcpu kept not functioning, wifi issues...I just cannot get it to work for me :( any ideas, cos this was from a full wipe and fresh install?
[Nexus S Android Development] avetny:
try this one http://goo.gl/RX56x
[Nexus S Android Development] simms22:
youre welcome. im sorry to burst your bubble, ive been running the 1.6ghz since last night. BUT you did post it here on xda first :D not one reboot since last night. the worst thing that has happened was quadrant closed once while benchmarking. im testing out the battery life today, at 1600/100. so far battery life is actually normal, i thought that it would be terrible but its not.
[Nexus S Android Development] MaliceOmega:
your getting the first oc kernel for the nexus s adding to its awesomeness and the only thing you guys can do is complain about the bootscreen? your forced to look at it for maybe 10-15 seconds tops. and it still shows both the google screen and the nexus bootanimation. are you really gonna nitpick bcuz he decided to sign his work? its morfics kernel, when you dev one you can add or subtract to it as u see fit. you can still use the first iteration of it without the bootscreen or you can wait for someone to release one more to your liking /rant
[Nexus S Android Development] icandy75:
Amen, that's the problem here. There is no way to make everyone happy and for some reason people seem to think the world must do EVERYTHING to their liking. Thank you Morphic for all your work.
[Nexus S Android Development] mprziv:
Awesome work Morphic...I appreciate it!
[Nexus S Android Development] morfic:
I like the bootlogo and at best see it gets refined. Trinity stays, the way Dow stayed.

Thanks for your feedback.
[Nexus S Android Development] morfic:
Look for the dumps here on xda, grab the system too, you will want the original bcm4329.ko to go with it.
[Nexus S Android Development] MaliceOmega:
awesome. im a physics major so the mushroom cloud in the back makes me all tingly anyway lol :D

on a side note i was wondering if its possible to get 1.3 or 1.4 on the processor? loved my vibrant running your DoW kernels lol. is it the same hummingbird that was running with the vibrant or is this one different?
[Nexus S Android Development] PeartFan40:
Nice Work!!! Thank Youuuuu.

Just finished flashing the Team Whiskey O/C'd 1.2 Kernel then installed your Bionix ROM on my Nexus S. Ran Quadrant and got a score of 2,255. Wooot. Thank you!! Keep up the great work!!

BTW, anybody who says the Nexus S and the Vibrant are the same device, should be shot. Not even close. Nexus S pwns the Vibrant.
[Nexus S Android Development] barbarossa2:
hey nice work on the kernel seems very stable I am running it on modaco R3 and its very smooth and fast excellent work thank you for this
[Nexus S Android Development] irishrally:
You have to flash the OC kernel after flashing the ROM. If you flashed as you described you are not using the OC kernel.
[Nexus S Android Development] schizopunk:
Can you at least tell us how to change it back to the default one though?