yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] bananis:
appreciated.

as an FYI to other n00b players - trinity14b v3.0 doesn't work with stock gingerbread.

so... i backed up stock rom through recovery, wiped data through recovery, installed cm7rc16 from sdcard, let it boot up, went into rom manager, selected install rom from sc card, chose trinity14b_v3.0_cm7.zip and installed without clearing data/cache.

working like a charm so far :)

edit: missed the step about gapps... :o
[Nexus S Android Development] irishrally:
Couldn't get past trinity boot screen on initial attempts. 1.6Ghz kernel.
[Nexus S Android Development] XtremeKh:
Boot loop on Cm7 Build 18 with 1.6 GHz Kernal... damn. Hopefully a more stable one comes around that works.
[Nexus S Android Development] jlevy73:
Success 1.6 boots. Now to bench this baby
[Nexus S Android Development] :
The farthest I got on 1.6 was a 2/3 rotation of the boot animation arrow.
[Nexus S Android Development] Xandlinger:
Trinity16 booted just fine for me -- using CM7#18, rebooted during Smartbench though.
[Nexus S Android Development] teledude:
1.6 booted - reboot during quadrant....
[Nexus S Android Development] bergqvistjl:
tried 1.6, with the latest CM7 (build 18 or 19 i think) and it was veery unstable, it booted, and i let it wait for a few mins, but it would still randomly freeze and reboot, either while still loading CM7, or sometimes it would get to the unlock screen yet freeze after a few seconds then. Gone back to 1.5 for the time being.
[Nexus S Android Development] td0s:
Nothing but mushroom cloud for me on 1.6 - 1.5's a charm (cm nightly 19)
[Nexus S Android Development] bergqvistjl:
On 1.5, everything works fine apart from the browser, when viewing pages with streaming flash videos, it has a tendency to freeze the browser, well not actually freeze, but that page and any other page i try loading after that refuses to load, and i have to force close the browser. Shame, because i mainly wanted the speed increase for better flash performance, which when its working, is great. its just that 9/10 times it renders the browser unusable.
[Nexus S Android Development] alexis_p3300:
i'm testing the kernels on my stock rom 2.1 worked fine except bt,all the others don't seem to work stuck at the trinity boot image,that's the most stable compination of rom kernel atm?

**ok kernels found,seems 1.3 is the limit for stock rom
[Nexus S Android Development] dingdonghei:
This is a known problem for a lot of us. 1.5 works really smoothly on my phone, except for the browser. It locks up completely even loading google.com for me.
[Nexus S Android Development] avetny:
1.6 working....but some times when i use phone for max, i see restarts.....but working better than 1.5 !!! because i didn't see think like force is clouse....or freezing....just some times restarts.. (already 3)

_____________________________

update: 1.6Ghz- phone stop reboots (rarely)..... (CM#16)

update: after using 1.6Ghz (1 Hour) i come back to 1.5Ghz,.....and the point is 1.5 working with out stop forces, or any laggy at all !!!

update: come back to 1.4Ghz.....1.5Ghz reset programs some times....
[Nexus S Android Development] iinviktus:
Does anyone have functioning BT with any of these kernels? Bionix, MoDaCo and CM7 don't work for me on any of these kernels after a full wipe.

Thanks.
[Nexus S Android Development] c_licious:
Yea, did that. No luck :(
[Nexus S Android Development] morfic:
It boots up and is 1200MHz as top speed.

Once i push things higher i will boot to 1000MHz and you can go higher after that with many means.

SetCPU is one, but it has so many options, people tend to make a less stable system with it.

There is a overclock widget in market (never used it, but i know people who use it)

OSmonitor actually let's you change governors and min/max frequency. (if people only pay attention to enabling root mode ;) )

I use a "script" with sl4a to do things like change governors, change max freq, and more. (you can change everything from the commandline)

With sl4a you can run any script in ADW EX as a shortcut, so you could have a reboot icon on homescreen, or a reboot recovery/bootloader one, or all three for example)

The changing of frequencies could be done this way too. or use 4, 1.0, 1.2 for frequencies and a performance and a ondemand one for governors.

The benefit of those would be, nothing running all the time.

The perl examples make me think i should push sl4a with the kernel.zip once i have a perl script that let's you choose min/max and governors.

But toys will have to wait until after i see what goes wrong on the bluetooth end.

Yes, I *DO* love sl4a.

For those wanting to force it to another frequency at boot, do so in /system/etc/init.d/S_50overclock

again, an option that does not require running an app all the time.
[Nexus S Android Development] graemegb:
Getting 17.081MFLOPS in Linpack! also getting arour 2900s on quadrant advanced. great job!
[Nexus S Android Development] dsmflyer:
Could you tell us what voltage changes or any other changes you have made to your new kernel? Should we flash to your new kernel if we are already rock stable with your first kernel that you posted? I wouldn't want to increase voltages elsewhere on the system if it is already stable with lower voltages.
[Nexus S Android Development] mortzz:
There's a new one? Is it different from the one in the OP?
[Nexus S Android Development] gbhil:
maybe I missed it.

Source?
[Nexus S Android Development] dsmflyer:
No, there is no new one. I was referring to the very first kernel where most people found that their phone was unstable. The one on the OP is the new updated one.
[Nexus S Android Development] graemegb:
EDIT: nevermind. just flashed new kernel
[Nexus S Android Development] morfic:
2900? check out Trinity :D
[Nexus S Android Development] DebauchedSloth:
Second that. Would love to play with this.
[Nexus S Android Development] morfic:
Like i said, while this is in a preview state i won't push my minor changes to git(hub).

Once this is in release state i will push it to github.

It's minor changes to the official source in git, based on what i already did with the i9000 source for Samsung Vibrant.

So if you want to play with it before i fork and push changes to github, the source is already there.
[Nexus S Android Development] graemegb:
After flashing the updated version, I am getting quadrant scores between 2600 and 3056
[Nexus S Android Development] Greenarcher707:
Great work, now just one minor request. How and can i remove that awful looking boot logo? Sorry, i just want to keep things clean. I'm OCD like that.
[Nexus S Android Development] schizopunk:
+1 to this... not really fond of the new boot logo.
[Nexus S Android Development] yaachi:
flashed the trinity kernel, auto rebooted after few hours, same as the last 1.2 kernel:)

and i have to clear setcpu user data in order to use it after reboot
[Nexus S Android Development] RinTinTigger:
I want to have the stock bootsplash picture back :(
[Nexus S Android Development] AllGamer:
i like it this way, keeps things under the hood.

not a fan of those ROMs with heavy skin customization, and wall papers and boot animation changes

i actually like very much the stock 2.3 boot animation is very nice

Bionix is running great, looking forward to try the 1.2 Ghz kernel when it's more stable
[Nexus S Android Development] Amin Sabet:
Kernel is working beautifully for me. Everything seems very stable, and I don't use Bluetooth.

Don't care about the bootscreen animation. One thing I noticed is that boot time is very short. Don't know if that's due to the ROM or the kernel, but I like it!

Thanks, morfic!
[Nexus S Android Development] RinTinTigger:
I love the kernel, but the bootscreen looks awful =/
[Nexus S Android Development] ragiut1:
how to go back to stock kernel? is there a zip file to flash?

thnx
[Nexus S Android Development] jlevy73:
No, BT does not work for me on any of these kernels except a few in the OP. 1.2 and 1.4ghz are the only ones that BT works on (for me)
[Nexus S Android Development] thegod2012:
flashing

i flashed all of these except for the 1.6 and the dont i tried all methods for this thread zip nada anyone know why my ns doesnt like these for cm
[Nexus S Android Development] bergqvistjl:
Looks like i'll go back to the stock kernel then.
[Nexus S Android Development] jlevy73:
There are only a few of the kernels that are specifically for cm7. Check a few pages back, I believe simms22 listed the a couple of them. I believe there is a 1.4, 1.5 and 1.6 cm7 version
[Nexus S Android Development] thegod2012:
those

i flash 1.4 1.5 and same results
[Nexus S Android Development] dingdonghei:
Yea, I've given up on the trinity kernels for now. Tried dolphin browser as well, but won't run properly. Also too many random reboots for my liking. Nice benchmarks and gaming though, hopefully it will get more stable with time and effort.

Something I've noticed is that the phone is unstable when performing 2D tasks, and not 3D tasks. Browsing and games like world war makes it reboot, but need for speed and 3D benchmarks run great. Anyone else noticed this trend?
[Nexus S Android Development] willcpfc:
I have found them generally stable (up to 1.4 only for me) but I would always find my wifi connection die no matter which browser I used. I also found playing music would trigger reboots. I have stopped using them for now due to these issues but I so hope the faults are sorted as the kernels do make a massive difference to performance.
[Nexus S Android Development] rb9228:
13 v.2.1.4 worked well for me on CM7 too.
[Nexus S Android Development] TruLuvNvrDies:
I've pretty much given up on the 14 and 15 kernels. but something interesting happened when flashing the 13 kernels. I didn't get a boot loop like the other kernels, just fc problems with all of the running apps. This was for both versions of the 13 kernel. Has anyone experienced this before? Would fixing permissions resolve it?

---edit---

for anyone wondering, fixing permissions doesn't work. i'll just wait for the 13 cm7 kernel.
[Nexus S Android Development] simms22:
fixing permission could solve it, its worth a try.
[Nexus S Android Development] kenvan19:
So lately I've been having a lot of issues with google apps so I decided this morning to do a completely fresh install of everything. I didn't install a kernel right away just out of laziness but I decided I wanted one again so I flashed the 1.4GHz a few minutes ago to strange results. My phone actually seems a LOT slower and a lot more jittery. I can't explain it, so I flashed the 1.5ghz kernel and it was no better. I'm just baffled as to why this would happen given how amazingly they ran before I wiped.
[Nexus S Android Development] dingdonghei:
Already tried that yesterday. Does not work. Boot loop.
[Nexus S Android Development] grubynawro:
I checked few kernels on 2.3.2 stock rom - 13 v2.1 is stable for me, 15b.v1.1cm7 is working too, phone started but a have reboots and freezes. Rest not working.
[Nexus S Android Development] bergqvistjl:
Yeah, general usage was really smooth, and when flash decided to work every now ant then, it was briliant. But far too many bugs for daily usage though.
[Nexus S Android Development] alexis_p3300:
is bt working with 2.1 kernel on stock rom?
[Nexus S Android Development] grubynawro:
Yes, BT is working for me.
[Nexus S Android Development] alexis_p3300:
maybei'll try again, curently i'm on bionix with 2.14 kernel everything work just fine and speedy except the dawm ota upgrade warning...
[Nexus S Android Development] morfic:
Working on Bionix and cm. On/off/on/off/on, no problem, sound is excellent.

Sent from my Nexus S
[Nexus S Android Development] simms22:
did you try rebooting once after, to see if it would still behave jittery? do you use setcpu? if you do, what is your setup? any profiles? have you tried to use a task killer to solve the jitteriness?
[Nexus S Android Development] jlevy73:
If you could get working BT on either 1.3 or 1.4 it would be awesome.
[Nexus S Android Development] morfic:
http://dl.dropbox.com/u/16615951/Trinity-UV1-cm7.zip

http://dl.dropbox.com/u/16615951/Trinity-UV1-bionix.zip

To start with a UVOC, i actually ended up with a UV first, no OC at all, lowered voltages except for 1GHz which is stock.

Test those betas if you are interested. I will now apply and test coolbho3k's sleep death fix.

Which allows you to use screen off profiles with setcpu that are below and exclusive 800mhz w/o sleeping beauty effect on phone. This patch would be first used on the UV / UVOC kernel.
[Nexus S Android Development] morfic:
yes, 1.3, 1.4, 1.5, 1.6, 1.0UV all of them, i think the only one needing reasssembling would be the 1.2
[Nexus S Android Development] jlevy73:
Tried the UV kernel on cm7. I'm seeing noticeable lag when waking the phone up. Besides that no issues thus far.
[Nexus S Android Development] jlevy73:
Not sure what you mean by 1.3, 1.4, 1.5, 1.6? I tried all of those this evening and BT did not work on any of them except 1.2. I only tested them on Modaco so perhaps that's not an issue when coupled with the Bionix rom. Dunno

But I can say all of the cm7 kernels do not have BT working otherwise I'd be very content with the 1.4 kernel.
[Nexus S Android Development] morfic:
http://goo.gl/CfNXu CM7 1.0GHz UV Kernel

http://goo.gl/PT8iU Bionix 1.0GHz UV Kernel

Ok, the same 1.0GHz UV kernel with coolbho3k's fix applied, it ensures 800mhz is available for phone to enter and wake up from sleep.

Tested with Nexus S to 100/100 and 100/200 in "screen off" profile.

I like those UV Kernels a lot and they should have a live of their own, so any suggestions for a bootlogo?
[Nexus S Android Development] jlevy73:
My phone didn't like that kernel. Upon boot got FC's and general weirdness.
[Nexus S Android Development] iinviktus:
Same here, except I've tried Bionix and CM7 as well.
[Nexus S Android Development] morfic:
will be interesting to see what the consensus is going to be once a few more people tried this.
[Nexus S Android Development] simms22:
after an initial slow-mo phase and after i rebooted it once, the kernel is awesome, 2400-2900 quadrants. on an undervolted 1ghz kernel, not bad! smooooth btw @jlevy73 bloetooth is working here on cm7 latest kang.
[Nexus S Android Development] jlevy73:
Phone basically froze up on me. Let me try again and see if I can get it to boot. Thanks
[Nexus S Android Development] simms22:
it was weird on my phone at first too. after reboot then setting setcpu up to 1000, this baby cooks... and on low heat!
[Nexus S Android Development] willcpfc:
Hi....on cm build 20 and the new UV kernel. Booted no problem, noticeably slower to ready Widgets. However there are no issues thus far. Seeing how my wifi behaves now as that's where my problems running kernels have always been. Looking good so far :)
[Nexus S Android Development] willcpfc:
Just ran smartbench and my score was significantly down. Don't know if its reliable or relevant but thought I would share.
[Nexus S Android Development] simms22:
its a 1ghz kernel. your scores probably are down(great for a 1ghz) but your battery life should be great!
[Nexus S Android Development] jlevy73:
No luck. Tried rebooting a number of times as well as reinstalling. End result is the system runs in slow mode and every app I open FCs. Nandroid :)
[Nexus S Android Development] willcpfc:
Thought so :) and my wifi is fine! Is there any useful way I can help test this kernel or is just running it and seeing out for any problems all that's needed?
[Nexus S Android Development] www1:
Fantastic kernel.

Any chance to have a version without orribile "Atomic Bomb" boot image?
[Nexus S Android Development] willcpfc:
Quick update. This UV kernal has been the most stable combo with cyanogen yet for me. Running with not a single problem. Superb stuff :D
[Nexus S Android Development] simms22:
i told morfic last night that he should submit this UV kernel to cm, that it should replace the stock kernel in cm7. what do you think?
[Nexus S Android Development] willcpfc:
Well I have been on cyanogen since nightlies began and I always got the odd fc or reboot. But with this it has been faultless and everything seems to work great with it. I do not think anyone would complain if it were the stock one :)
[Nexus S Android Development] kenvan19:
It definitely doesn't blaze like the oc kernels but after that initial boot weirdness, it runs great. I'll run it for awhile to see what the battery is like but even on the 1.4 kernel yesterday my phone was at 60 after 14 hours. hell I ran it hard just to get it below 50 when I plugged it in. I guess any battery life issues I had were strictly related to lack of signal lol

Edit: I decided to try blue tooth and that caused a lot of issues. The phone started lag worse than I've ever seen before and then the screen became unresponsive so I did a battery pull and reflashed the 1.4 kernel. Things are running smoothly again.

Also I have the same bt issue as jlevy on the kernels he listed.

Sent from my CM7 Nexus S!
[Nexus S Android Development] yungfresh:
I just flashed the Cm7 UV kernel. do u see any change in speeds? And is it just for better battery life?
[Nexus S Android Development] simms22:
better battery life and better performance over stock(not like the oc'd kernels).
[Nexus S Android Development] yungfresh:
Do I need to set any profiles using setcpu? Or is setcpu not needed?
[Nexus S Android Development] irishrally:
I really want that new blue honeycomb logo somewhere on my phone, not sure this is the place (new boot logo) but just thinking out loud. Thanks again for another sick round of kernels.
[Nexus S Android Development] simms22:
i use setcpu, but without profiles. 1000/100 ondemand.
[Nexus S Android Development] jlevy73:
No please don't, I wouldn't be able to run cm7 anymore. Don't know why but this kernel is unusable on my phone (even with setcpu set @ 1000/1000). I can get 1.6 to work but not this, go figure.
[Nexus S Android Development] irishrally:
hehe, your life would fall to pieces without CM7. I suppose you could just flash trinity over it. Were you charging your phone when testing the UV kernels? Thermal related issue maybe? Although I've found that is more of an issue of OC kernels.
[Nexus S Android Development] jlevy73:
My guess is whatever it's UV'd too is not stable on my phone. Kind of like with the N1, some people could never run 925-950mv kernel because at those levels the phone would just lag and FC.
[Nexus S Android Development] ryan562:
i flashed/tried both UV kernels on to my NS with modaco's latest rom. runs smooth/normal except they break bluetooth and cause the phone to freeze when trying to enable it. otherwise, battery life seems to be on par with modaco's custom kernel/latest rom (which already offers awesome battery life).
[Nexus S Android Development] simms22:
well of course, it would have to be somethong everyone could run to get into cm.
[Nexus S Android Development] irishrally:
CM7 UV kernel is stable for me so far. For reference I could not get the 1.6Ghz kernel to boot. 1.4 and 1.5 did work well though.
[Nexus S Android Development] dingdonghei:
Uv kernel working great here. Does the kernel include ext4 fix btw?
[Nexus S Android Development] irishrally:
I'm actually getting really good benchmarks with the UV kernel, noticeably higher than what I was getting with the stock kernel but obviously not as high as the OC kernels.
[Nexus S Android Development] simms22:
from twitter...

i flashed the cm7 version. its running much quicker than the cfs version :D
[Nexus S Android Development] simms22:
ive been getting just about 3000 on quadrant. great for a 1ghz kernel!
[Nexus S Android Development] irishrally:
I was getting around 2800 (no apps closing or anything) where I would get around 2600 on stock 1ghz kernel.
[Nexus S Android Development] jlevy73:
Flashed the cm7 bfs and works fine. Albeit benchmark scores are quite poor when compared to stock kernel.
[Nexus S Android Development] simms22:
hows the bluetooth? im getting better than stock benchmarks. quad 2650-2950 with everything on.
[Nexus S Android Development] jlevy73:
Quad for me is around 2000-2100. rebooting now will check bt in a moment.
[Nexus S Android Development] jlevy73:
On reboot Quad is now @ 2700. Sadly, bluetooth breaks with this kernel.

Update: BT works, I need a hug :eek:
[Nexus S Android Development] jerrycycle:
I running the Trinity-UV1-cm7-sleepfix.zip kernel. I did reboot 5 times and now wifi, bluetooth work. I had to un-install & re-install a couple rooted apps because of su permission but now all is working even the browser is loading pages. I have set-cpu sleep screen off 100/200 with no wake issue.
[Nexus S Android Development] simms22:
OMG! THE SKY IS FALLING :eek:
[Nexus S Android Development] willcpfc:
Still flawless on my setup however Bluetooth does break my phone. That is the only issue I have had on UV kernel....spot on.
[Nexus S Android Development] jlevy73:
Try this. Turn off wifi and BT such that your only connected to your network. Before turning on wifi turn BT on. For some reason if I turn wifi on first I can't get BT to work. If I have wifi off BT will turn. Sounds crazy but that's how I got BT to work
[Nexus S Android Development] bratfink:
Post kernel link please for 1ghz UV cfs
[Nexus S Android Development] willcpfc:
Your right! Thank you :D I guess the kernel puts the nexus into female mode...no multitasking ;)
[Nexus S Android Development] irishrally:
Check out the first post of page 101 of this thread.
[Nexus S Android Development] scottb75:
I'm trying out the Trinity 1.4GHz CM7 kernal (on CM 7 build 22) found a few pages back now, and initially it seems to run okay on my NS. I ran Smartbench and it got through that without issue and stuff I use normally (ie market, Facebook, and Gmail) seem to work without issue.
[Nexus S Android Development] DebauchedSloth:
Any word on the source?

I'm sure I'm not alone in being interested in hacking on this kernel.

This stuff *is* all GPL.
[Nexus S Android Development] Jnowak1981:
Why did flashing the 1.3 kernel revert my rom back to 2.3.1 ? BTW I'm rooted and running the stock 2.3.2 ROM. Anyone?
[Nexus S Android Development] jlevy73:
The kernel overwrites the version number in build.prop. No worries you're still rooted on 2.3.2
[Nexus S Android Development] simms22:
morfic corrected that in todays kernels
[Nexus S Android Development] Jnowak1981:
That might be true, but I keep getting the dreaded update notification....
[Nexus S Android Development] morfic:
For the UV Kernels i am looking for a new logo, i am open for suggestions.
[Nexus S Android Development] Jnowak1981:
I guess my ? is which kernel do I flash for 2.3.2 stock rooted rom
[Nexus S Android Development] thegod2012:
pic

try a pic sure of a dam or something or a some sort of powerful something on a leash or whatever.

or since these other had a nuke just put a grenade
[Nexus S Android Development] Jnowak1981:
Anyone?
[Nexus S Android Development] simms22:
suggestion http://i55.twitgoo.com/2hzha1v.jpg :D
[Nexus S Android Development] kfjunky:
Great!

I love the battery life of the UV kernel. Seems to fit my usage pattern perfectly.

Only issues are browser and NewsRob, stops dowloading suddenly.

Am running Modaco R10 currently, but willing to switch to Bionix NS to

continue using the UV kernel.

Hope Team Whiskey could free up some of their time in the near futures.

Edit: Would be also great if a UV kernel for Modaco is developed..
[Nexus S Android Development] jlevy73:
I like this picture better for the bootup screen :p

1ghz UV, BFS
[Nexus S Android Development] kenvan19:
Odd my score doesn't come close to that. I'm pretty happy with the battery life and lets be frank, the ns is fast even stock.

Sent from my CM7 Nexus S!
[Nexus S Android Development] kfjunky:
CM Kernel Works

Excuse me, I was using the Bionix kernel.

Tried CM7 kernel and browser is now working!
[Nexus S Android Development] morfic:
World, meet Trinity for #NexusS http://goo.gl/x9NmS Bionix NS | http://goo.gl/320FE cm7 | UV 1GHz

Yes, all UV1 links are now dead.
[Nexus S Android Development] morfic:
Sloth: Until i put my minuscule changes up on github, you can still hack on this kernel: git://android.git.kernel.org/kernel/samsung.git