yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
Aside from plans to include voodoo sound once it settles some more. A UV seems interesting.

would actually be fun to investigate the limits of a UVOC kernel.

and I want to investigate areas of possible tweaks.

for your particular phone I would suggest to look at 1.3ghz kernels as they will provide a more well rounded experience right now.

taking you to 1.4ghz would require a voltage bump or two most likely.

I build kernels to enhance usability, reduce waste by improper built kernels, there is no use in going past the phone's abilities.

rebooting isn't fun.

1.3ghz on nexus s is pretty fascinating. 1.4ghz can outscore 1.3ghz only in linpack.

I'd love to target 1.3ghz for a UVOC kernel (if UVOC is possible)

just a few thoughts/suggestions.
[Nexus S Android Development] kzakaria:
Would you Please bump the voltage one stage up. This will make my phone super stable. I will be very thankful if you can do that ASAP. I love the 1.3 but the fact that 1.4 is working on my phone makes me always go back to it!!!!:D

Again THANKS for the great work
[Nexus S Android Development] morfic:
I certainly could. it would mean you run it at the Max allowed without further tweaks to go beyond that limit.

If that does not concern you. I'll build it.
[Nexus S Android Development] kzakaria:
Would you please;)
[Nexus S Android Development] morfic:
Then I might just as well build a 1.6ghz kernel at Max voltage.

At least 2 vibrants run it.

Who knows who else wants to play :D
[Nexus S Android Development] jlevy73:
You never know. With N1, the max was about 1.26ghz and while it was completely unstable for me there were a few people that were able to boot it up long enough to run some benchmarks.

I like the idea of UV/OC kernel at 1.3ghz. That seems to be stable for the majority of people in this thread.
[Nexus S Android Development] kzakaria:
I am all yours!!! Make the 1.6 and I will be more than happy to test it for you.

As usual THANKS for the great work :)
[Nexus S Android Development] kzakaria:
Thank you so much for all of your time and effort. Let us try to reach the Max Hz with the maximum possible voltage and then optimize from there. Cannot wait to test your new build

Thanks:)
[Nexus S Android Development] mprziv:
1.4 is perfect on mine.

I'd love to try a 1.6
[Nexus S Android Development] tommyz2kool:
So what kind of decrease in battery life can be expected at 1.3ghz from stock? 1.3ghz feels really fast but sometimes it seems like the battery will deplete very quickly.
[Nexus S Android Development] defysword:
UVOC is on the way. just be patient. :)
[Nexus S Android Development] morfic:
Well well well

So the over spec bus runs fine at 1.4GHz too.....running rock solid.

So now i need a little longer for a UV, or a 1.6GHz kernel, since a 1.4GHz with faster bus is giving you a much funner overall system.

a 3fps increase in nenamark is quite siginificant. Nenamark publishing is not working so their website still reports me with 59fps max (old 1.4GHz score with nenamark1.5)

so packing that up now.
[Nexus S Android Development] DroidRC1:
Do you know if its working on cm7 lastest build(55) again??
[Nexus S Android Development] morfic:
Since it's just frequency changes and same old ramdisk, i would think yes.

IF it still to your phone's liking i can't say, mine likes it, a lot.
[Nexus S Android Development] jwr2d2:
Trinity14 doesn't boot w/stock or is it just my phone

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Doesn't want to boot CM7, just hangs at the Trinity logo (coming from a full wipe).
[Nexus S Android Development] kzakaria:
Can you increase the voltage for this one as promised please :)
[Nexus S Android Development] jwr2d2:
Same thing on stock and came from a full wipe of another rom

Sent from my Nexus S
[Nexus S Android Development] morfic:
you guys want a V3.0 that runs on stock, like 13 v2.1 did?

i'd have to switch out the ramdisks
[Nexus S Android Development] jlevy73:
Could just be the boot.img but I'm sure Morfic will figure it out.
[Nexus S Android Development] morfic:
But making a faster kernel is so much more fun!

Ok, bumping voltage, just for you.
[Nexus S Android Development] jlevy73:
Yeah, that would be great.
[Nexus S Android Development] kzakaria:
Thanks!!!!
[Nexus S Android Development] jwr2d2:
Please sir

Sent from my Nexus S
[Nexus S Android Development] mamba720027:
Running the Trinity14b_V3.0 kernel no problemo here,finally my cpu can clock at 1.4ghz. Thanks :D
[Nexus S Android Development] morfic:
http://db.tt/j3ZYOY0
[Nexus S Android Development] jlevy73:
Which Rom are you using? I've tried them all and no boot for me.
[Nexus S Android Development] yungfresh:
Hey guys, I am using CM7 on my nexus S and is wondering if the trinity 14 stable enough? because I need bluetooth to work. If not, which do you guys recommend? all responses are appreciated. Thanks!
[Nexus S Android Development] morfic:
http://db.tt/8YFfsTl
[Nexus S Android Development] jlevy73:
Trinity 14 does not boot with CM7 so at the moment I'd recommend sticking with the stock kernel if you are looking for stability
[Nexus S Android Development] morfic:
now if the kernels work for their recipients i may add them to OP, at this point their are "in testing"
[Nexus S Android Development] DanRyb:
Aside from an extra 100 MHz, is 14 V1 "better" than 13 V2.1.4? I am running MoDaCo r8 and flashed 14b_V3 and I my phone either froze or reboot itself a lot!

So, then I flashed 13 V2.1.4 and it seems to be very stable, smooth, and fast, but of course part of me is still tempted to try out 14 V1 ;)
[Nexus S Android Development] jlevy73:
I was able to boot this kernel with Modaco's r8: http://db.tt/8YFfsTl

Unfortunately BT does not work, but everything else seems functional.

That same kernel did not however boot with CM7
[Nexus S Android Development] jlevy73:
Some impressive benchmark numbers from the last kernel uploaded on r8:

Smartbench: 1640/4121

Nenamark: 50.1 FPS

Neocore: 65.1 FPS

Quadrant: 3447
[Nexus S Android Development] jwr2d2:
Kernel working nice on stock, haven't ran into any problems. Thanks

Sent from my Nexus S
[Nexus S Android Development] jlevy73:
Can you test to see if BT works please. Thanks
[Nexus S Android Development] DanRyb:
I'm on Trinity 13 v2.1.4 and MoDaCo r8 and Bluetooth isn't working.
[Nexus S Android Development] jwr2d2:
Yea I am having problem with BT working

Sent from my Nexus S
[Nexus S Android Development] mamba720027:
im useing it on Bionix NS 1.2 w/trinity v2.0 rom, at first the Trinity14_V1.0 kernel did not work for me but now that i tried the new Trinity14b_V3.0 kernel it works smoothly.so im getting 1.4ghz and my bluetooth is working,i guess it dident work for some, but i was useing bionix rom from the start so i guess must be it.
[Nexus S Android Development] jlevy73:
Yeah I got Trinity14b V3.0 to boot with Bionix NS 1.2 but with stock kernel. Everything ran very smooth just couldn't get BT to work.
[Nexus S Android Development] gundamboy:
when i installed it over CM7 nightly, i experienced an array of FC's
[Nexus S Android Development] vesparny:
when bln will be enabled?
[Nexus S Android Development] deez1234:
Thank you morfic! I'll have to check in on IRC soon. New 1.4 kernel running stable on Bionix 1.2 (can't wait for the next revision) Also having BT issues but haven't tried wiping anything for my last few flashes. Thanks again "Kernel King". Lol
[Nexus S Android Development] rb9228:
I used Trinity 13 v.2.1.4 on CM7 Alpha 2. Not only it was solid enough for me, bluetooth functioned as well.
[Nexus S Android Development] jwr2d2:
morfic, I have ran into a few random reboots on trinity14 for stock

Sent from my Nexus S
[Nexus S Android Development] kzakaria:
morfic

there is no need to increas the voltage. the new version is awesome! thanks
[Nexus S Android Development] bethedealer:
I install Trinity14b_V3.0 on top of Bionix NS 1.2 and it even cannot boot up properly. Just keep rebooting. However Trinity13_V2.1.4 works well. I wiped everything before flashing.
[Nexus S Android Development] demo23019:
wasn't even able to get past loading screen with V1.0 but new V3.0 kernel im able to boot to homescreen but freezes almost instantly

tried with NS 1.2 and modaco

maybe a slight boost in vcore will help?
[Nexus S Android Development] avetny:
HAHAHAHHA this is so FAAAAAAAAST haahahaha !!!

1.4b - IS awesome !!!!:D:D:D:D:D:D:D:D:D:D
[Nexus S Android Development] td0s:
Same for me using 14_v3.0 and 13_v2.1.4 - I think the CM7 nightlies have stopped being compatible.
[Nexus S Android Development] willcpfc:
Hi which is the best version for stock rom and is it of benefit to me? Thank you :)
[Nexus S Android Development] icandy75:
Willcpfc I suggest you check out Bionix NS1.2. It's very much like a stock rom on the outside but tweaked for performance.
[Nexus S Android Development] avetny:
ok people !!!!!!:)

i post it LONG TIME AGO ABOUT - cyanogen mod stopped being compatible.:eek::eek::eek::confused::confused::confused::confused::(:(:(:(

AND LAST compatible IS - B#39-crespo-cm7src-grid-eng:(

(i have it)
[Nexus S Android Development] willcpfc:
OK...I will bite the bullet when I get home. Now do I need a separate zip for Google apps? Also I shall report on my experience with this...my first custom rom flash :eek:
[Nexus S Android Development] avetny:
you need to try THIS: http://xdaforums.com/showthread.php?t=916630
[Nexus S Android Development] icandy75:
Easy flash no Gapps needed.
[Nexus S Android Development] Beatle405:
1.4 v3.0 works great on mine except when trying to run smart bench. As soon as it starts the 3d tunnel test, it locks then re boots. Quadrant works occasionally just like on 1.3. Getting about 3359.
[Nexus S Android Development] d0ugie:
Am I doing it right? :)
[Nexus S Android Development] avetny:
yes u are :D
[Nexus S Android Development] zdiddy14:
Ok, is it possible to boot this kernel with fastboot without flashing it? When I try, all I get is a prompt saying (cannot load 'oc.img').
[Nexus S Android Development] avetny:
update ur recovery
[Nexus S Android Development] RaQHoliday:
Yeah, this doesn't play nice w/the CM7 nightly lol
[Nexus S Android Development] slopresto:
Have had 0 issues with Trinity13_V2.1.4 since I exchange my Nexus and reinstalled everything.

Originally, I had some issues with Trinity14v1. It would boot, but it was not stable.

I am happy to say that I put Trinity14b_V3.0 on and everything is running great.

Great work and thanks again.
[Nexus S Android Development] Superfrag:
Is it possible to get a kernel with stock speeds, but undervolted for maximum battery life?
[Nexus S Android Development] Star Shadow:
I would like to try the Trinity13_V2.1.4 without flashing it. Earlier posts say to use this command:

fastboot boot oc.img

But, in the zip file that I downloaded, there are other directories and files. What would be the way to try this kernel without flashing it?

I am using Stock Android. Do I need to flash over CWM again and/or need to be superuser on the phone?

Thanks.
[Nexus S Android Development] bethedealer:
Thanks for your reply. I follow it to the letter. The NS still stuck in the boot loop with v1.4b
[Nexus S Android Development] avetny:
damn dude, u scare me :(

BECAUSE IF IT'S 1.4ghz IS LIMIT :eek:! i will die:mad:...i don't need famous "NS" which cant overclock more than 1.4Ghz:mad::mad::mad:
[Nexus S Android Development] willcpfc:
Hi....which is the most stable kernel for bionix rom?
[Nexus S Android Development] icandy75:
Hey willcpc, it all depends on your phone as they all are a bit different. I suggest you try the newest 1.3 first and if your phone likes that then try the newest 1.4b.
[Nexus S Android Development] ragiut1:
any solution for the latest CM7 nightly??
[Nexus S Android Development] willcpfc:
Thank you....shall try. I have tried each rom now and bionix is my favorite. Its just fast and mean :D

Now can you tell me in simple terms the advantages of overclock...I mean the rom is already rapid.
[Nexus S Android Development] icandy75:
Currently the main benefit is more speed. In time I'm sure there will be UV kernels that will help with battery life. The Trinity kernels are nice as they do not need set cpu and regulate themselves on demand like the stock ones. It basically just means more power when you need it (a restore though Ti runs much faster on 1.4 than stock).
[Nexus S Android Development] willcpfc:
Put 1.3 on and its running good so far :) such a linpack score improvement over stock.
[Nexus S Android Development] avetny:
OH PLEASE ! linpack - is a shame for us:D
[Nexus S Android Development] willcpfc:
Lol according to it my old x10i destroys the nexus! :D:eek:
[Nexus S Android Development] avetny:
Daaaaaaamn! Lolololol we need to hack it hack it :D
[Nexus S Android Development] burnfire:
1.4b its wicked fast and run smoother than 1.3.

The only thing is, if I set one of my pic as my wallpaper the gallery freezes and I am forced to reboot.
[Nexus S Android Development] morfic:
Going to do some UV work later this week.

Today I'll rest. Messing up your car in the morning is sort of a mood killer.

Boss also changed my shift to days, which further infringes on time to work on this.

I'll work on a 1GHz "Supersaver" first though, balancing a UVOC kernel will be taking a little more time.
[Nexus S Android Development] thegod2012:
installing

how do u install these do you flash at the same time or do u reboot after flashing rom then go back to recovery to flash kernel
[Nexus S Android Development] jerrycycle:
I wiped everything flashed the rom then rebooted and the back into recovery and flashed the kernel then gapps because on a older cm rom
[Nexus S Android Development] rb9228:
I flashed them at the same time. Do the ROM first, then the kernel. Then reboot.
[Nexus S Android Development] thegod2012:
i tried updating cwm and that did it for me thanks
[Nexus S Android Development] Star Shadow:
Can we try the kernel without flashing it? There are several directories in the zip so how do we handle it? Thanks.
[Nexus S Android Development] avetny:
I hope team gonna fix kernel for latest cyanogens builds
[Nexus S Android Development] thegod2012:
nightly

yess indeed i tried them on build 5 didn't work have u tried build 7
[Nexus S Android Development] kid1da:
They don't work on build 7 as well.
[Nexus S Android Development] jlevy73:
No, they are not compatible with the CM nightlies. The OP will have to push out an update in order for them to work.
[Nexus S Android Development] morfic:
I booted 1.5ghz, and ran it, but didn't like it, as 1.4ghz is just a better *SYSTEM*

at 1.5ghz i am forced to a lower bus speed again.

IT's the system experience that counts not a single number being the highest

the bus speed on 1.4ghz is MUCH more impressive than on 1.5ghz, like most telling, nenamark with 1.4ghz and high bus speed whips 1.5ghz with low bus speed, since the gpu is tied tot hat same bus.

so beware what you wish for, you may get it, and not like it.

as i have to figure out what to do with my car now where the insurance called back and said it's a total loss, i will not be pushing things.

If i get around to work on it, it's likely to relax my nervs from the stress of not having a car :)

working days+extra days does not help finding free time, "weekend, off modnay, where art thou?"
[Nexus S Android Development] kzakaria:
can you upload 1.5 just for fun
[Nexus S Android Development] morfic:
unzip

fastboot boot boot.img

if it is stable flash

push the bcm4329.ko to /system/modules if you want to try wifi AFTER backing up your stock bcm4329.ko

if it all works, flash zip as usual

note: fastboot flash boot boot.img will flash the kernel, so do not accidentally add flash to the line above
[Nexus S Android Development] avetny:
thank you for explain

damn dude sorry for your car...i know how it's hard with out....(im the person who love speed, not only in a car, in a phone eithe).

Never think about bus speed (only now understand, how it works, why some phone got crazy overclock but after certain step got no point of overclock )

so hope insurance gonna pay aloooot of $$$$$$.....so u will get rest after that for a month in miami :)
[Nexus S Android Development] avetny:
NO DUDE....Kernel no more work with CM7 nightly.....it's something what Whiskey team supposed to fix

last one CM7 build which is work with all Bionix kernels (1.4b)!!!!!!

it from Unofficial CM 7 - Crackflasher Builds....

the number of build is:

B#39-crespo-cm7src-grid-eng.

when i understand than CM7 stopping work with Bionix kernels i download last one working one....(with new media3 player) ( i have this build, still using)
[Nexus S Android Development] morfic:
http://db.tt/vvWnwCg how about this?
[Nexus S Android Development] kzakaria:
no way to get the 1.5?
[Nexus S Android Development] jlevy73:
I will try it and let you know.

Boot#1: No wipe flashed the kernel right over CM7, booted ok. However, I am getting serious lag and BT is not working. Will try more drastic measures such as a full wipe.
[Nexus S Android Development] mcp2009:
Same here :( And a random reboot. Not gonna do full wipe though. Gonna try crackflash
[Nexus S Android Development] jlevy73:
I broke down a did a full wipe, flashed cm7, gapps then kernel and booyah, everything is working great. Very smooth and BT works as well. Nice job Morfic.
[Nexus S Android Development] mcp2009:
Ahh. Dang Don't really wanna do a full wipe. I'll wait til tomorrow to do it. I got too many apps to restore.
[Nexus S Android Development] jlevy73:
I know the feeling, I've got over 200. If it wasn't for titanium I wouldn't even bother. Should point out that getting root access with su is not working so well.
[Nexus S Android Development] yiuwing_hk:
Same random reboot, with Bionix NS1.2
[Nexus S Android Development] jlevy73:
Spoke to soon, on CM7 phone just rebooted and is now in a bootloop. Nandroiding back
[Nexus S Android Development] simms22:
flashed the trinity14b cm7 version with the cm7 nightly build 8. no wipe, no problems so far. booted fine and root apps are working. i wiped dalvik, reflashed the rom, reflashed the gapps, then flashed the kernel. now lets do some tests... i thought i was going to bed, lol.
[Nexus S Android Development] simms22:
i think my phone loves this kernel! this is with cm7 nightly #8 and the latest trinity14b cm7 kernel...

quadrant

smart bench
[Nexus S Android Development] Star Shadow:
Thanks for the clear instructions! Your 1.3 kernel is really stable and I've never felt phone feel so fast. The UVOC kernels should be really cool with greater battery life. :)

Thanks for your hard work.
[Nexus S Android Development] Alexkidd85:
You're the only one running the kernel you know? :eek:
[Nexus S Android Development] willcpfc:
Trying the new trinity with CM7 Build #7. All seems stable so far....using wifi and browser, hope its fine now because you can feel the difference trinity makes :)
[Nexus S Android Development] avetny:
PEOPLE THIS IS SAME bionix 1.4b KERNEL EVEN BETTER:) because "mr. Morfic" HELP to make WORKING WITH CM nightly !!!!!!!!!

:D lol THANK YOU !!!!!!!!!!!!!!!!!!!!!!!!!!! u saved US !!!!!

THANk you for you time !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

check THIS OUT PEOPLE: http://www.youtube.com/watch?v=QWfbGGZE07M :D
[Nexus S Android Development] willcpfc:
Quick update and question....the Trinity/cm nightly combo is still fine :) also I was wondering if having jit enabled is needed or could it cause conflict with the new kernal? And yes, thank you morfic. :)
[Nexus S Android Development] simms22:
thank you morfic for making the kernel compatable with cm7 again. im curious with what you changed to make it compatable. btw, ive been using it at 1ghz high/100 low without any profiles for the most part, setting it to 1.4ghz every once in a while for a boost. ive had no stabilty issues and all the root apps work. again, thanks for your effort!
[Nexus S Android Development] jthornton71707:
What kernel are you guys getting thus to work with? Trinity 14 just freezes at boot for me and 14b freezes shortly after boot. I've wiped data, cache, and dalvik
[Nexus S Android Development] simms22:
trinity14b v3.0 cm7. this one http://xdaforums.com/showpost.php?p=10748560&postcount=557

wipe dalvik, flash the rom, flash the gapps, then flash the kernel :D
[Nexus S Android Development] jlevy73:
Do me a favor and try turning on BT. Let me know if it works. Thanks
[Nexus S Android Development] simms22:
nope. stuck turning on. but to me that doesnt matter, i dont use it. i know you do.
[Nexus S Android Development] jlevy73:
It worked for a few hours yesterday (I mean BT) but then the kernel went naughty on me :eek:
[Nexus S Android Development] jthornton71707:
This is exactaly what I've done. It goes for a few minutes then freezes and rebooted randomly
[Nexus S Android Development] SpartusTana:
Not sure if it's the kernel or the Bionix 1.2 ROM, but it doesn't seem to cooperate with live wallpapers. I've had it switch back to the default nexus s live wallpaper whenever i use a different one.

I've also had my phone reboot by itself twice now, not sure what it's related to. First time was when I was updating an app on the market, and the 2nd time was while i was listening to music on my phone.

Looking forward to an update.
[Nexus S Android Development] :
I flashed the compiled boot.img on MoDaCo r3, worked great until I ran Quadrant which caused a reboot before the results.
[Nexus S Android Development] mortzz:
I've done both, same results.

Would a tiny bit more voltage help? Are you running the 1.2@ stock voltage?
[Nexus S Android Development] morfic:
ok, i see something now

all those who flashed the kernel

adb reboot downloader

fastboot boot the kernel, so it runs the kernel this way and not the flashed one (try to keep an open mind and forget it is the same kernel)

let me know what you find out, i'm heading to bed

'night

http://db.tt/YlpduoF
[Nexus S Android Development] morfic:
Stock is 1.25V, this is 1.35V

I can do 1.40V tomorrow

not that beating the Vibrant at .2GHz less is a bad thing, i run the vibrant at the voltage i am approaching to get 1.2 stable, to explain my apprehension to just bump bump bump the voltage

I'll even lower the voltage for the crashers to try (yes, i have a point to that ;) )

'night
[Nexus S Android Development] mortzz:
The zImage or the boot.img that was posted?

I wonder why it's so different from the SGS' Hummingbird?

Edit: It wouldn't boot from fastboot boot zimage, so I used the oc_final.img that was posted above. Doesn't seem like there is a change. It'll still work properly (and fast) until I try to run neocore or any other program that's resource intensive.
[Nexus S Android Development] Anderdroid:
Does this have EXT4 remounts?

fastboot boot oc_final.img

^^^ made my phone crash on last bootanimation image...

Then rebooted to normal kernel and my WiFi is splattered. Help ? :P

EDIT:

tried fastboot boot oc_final.img again and it booted this time... will see if its stable /crossfingers...

nope rebooted again
[Nexus S Android Development] morfic:
don't use the .img just fastboot boot the zImage

and in dmesg check the bcm module loads w/o errors

then manually:

adb shell mount -o remount,noauto_da_alloc,nosuid,nodev,noatime,nodiratime /data /data

'night, let me know if there is any difference

EDIT: about the splattered wifi, push your backed up module, reboot, yay! ;)
[Nexus S Android Development] Anderdroid:
Can someone post up stock bcm4329.ko I didn't realize the .img posted would replace it facepalm.
[Nexus S Android Development] Anderdroid:
What exactly is -b 0x30000000 -n 4096 ? -b and -n won't work on OS X fastboot
[Nexus S Android Development] mortzz:
Tried that "fastboot boot zImage" and it went through the normal build process, but when it rebooted it wouldn't boot past the Google logo when you first turn the phone on. To be fair, I didn't let it sit for a while and see if it would change, but it didn't look like it was doing anything.
[Nexus S Android Development] Anderdroid:
Same issue. I waited 5 minutes.
[Nexus S Android Development] RinTinTigger:
same here :/

thought it was cuz im using MoDaCo r3