yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] simms22:
well, at least you tried. try the cm7 version http://goo.gl/RUT5b
[Nexus S Android Development] Hostile89:
Bionix version also hung at boot. cm7 version booted and appears to be working ok. testing it out now.
[Nexus S Android Development] morfic:
Going to build something with stock ramdisk then. Next time I build kernels.

I will adjust my script to build 3 kernels then. So there will be a stock kernel until I check why it's not booting on stock with the Bionix ramdisk.

Sent from my Nexus S Trinity
[Nexus S Android Development] avetny:
HELLO :)

i found very nice boot logo for maxV

"final fight"
[Nexus S Android Development] morfic:
If we pretend it's portrait and that I liked it.....it has copyright infringement written all over :/

Sent from my Nexus S Trinity
[Nexus S Android Development] avetny:
Oooh I didn't think about that! :(:eek:
[Nexus S Android Development] nicholasbgr:
Thanks, looking forward to try it :)
[Nexus S Android Development] burnfire:
To prevent spam....aaaahhhhhh.

Mr. Simm22 himself... Regarding the last kernel link you posted.

Does this kernel have the voodoo patch?

XDA APP---*Death to IPHONE!!!! Maybe not yet; Lets torture them first*
[Nexus S Android Development] simms22:
absolutely.

oh, and i agree, lets torture them first :)
[Nexus S Android Development] asci:
"morfique: Trinity15(b) should be in xda thread. The maxes are more likely to be on timeline"

Where is it?
[Nexus S Android Development] icandy75:
http://db.tt/C74soXC for CM7. It was post #1192. For future reference you can use the search this thread button on the top.
[Nexus S Android Development] deeren:
on flashing the netharchy kernel 1.2.1 or morfic kernel for cm7 nightlies, the backlights of the softkeys( home,search,back...) do not light up when i power my phone. i have to manually press them so that they light up. also if i go over 1200 (on morfic one), the phone vibrates continuously on pressing (only once )the softkeys.

while i know that this is probably my phone concerning the OC, could anyone confirm whether the soft keys not lighting up is a feature or a result of my buggy phone.
[Nexus S Android Development] floomat:
phone bootloops constantly after flashing Trinity14b_V3.0 or Trinity15b_V1.1-cm7...

hope you guys know why :D
[Nexus S Android Development] icandy75:
Never noticed before but mine does the same. They only light up after being pressed. I haven't run a stock kernel in a long time so I'm not sure if it was always like that. I have never had the vibration issue you speak of though.
[Nexus S Android Development] deeren:
try it on a fresh flash. either u didnt wipe or well... its just like this. some phones will manage the OC and some wont. that's how it is

thanks for the answer.

can someone else please confirm the issue whether the softkeys backlight not lighting is a feature or an issue?
[Nexus S Android Development] simms22:
my soft-keys light up as soon as the trinity boot image appears, then stay lit through bootup. it was the same on stock. just rebooted/checked to make sure.
[Nexus S Android Development] jerrycycle:
Is the trinity max cm7 uv'ed like the trinity cm7b?
[Nexus S Android Development] alexis_p3300:
same as simms22 here never had any ploblems with lighting on any morfic's kernel
[Nexus S Android Development] irishrally:
If we can find this boot animation it would be very sexy: http://phandroid.com/2011/02/05/android-honeycomb-boot-animation-video/
[Nexus S Android Development] avetny:
oooohhh daaamn !!!! 100% love it
[Nexus S Android Development] avetny:
people check this out ;)

http://cgi.ebay.com/CARBON-FIBER-IN...Accessories&hash=item20b6c8b03f#ht_4640wt_940
[Nexus S Android Development] jlevy73:
I prefer my NS naked :)
[Nexus S Android Development] irishrally:
Simms, give it up, we know you got the secret pre-release for the maxV.
[Nexus S Android Development] simms22:
its called vmax
[Nexus S Android Development] irishrally:
Ok.

..........
[Nexus S Android Development] simms22:
oh, its not made yet. not that i know of at least.
[Nexus S Android Development] morfic:
For once his shakes are worse than yours.

Building stock clock / kernel right now. Uploading should be fun as I rebuild my system right now.

Vmax will appear this weekend.

Sent from my Nexus S
[Nexus S Android Development] avetny:
Doctor we waiting this happy day !!!!:D
[Nexus S Android Development] ping33tx:
Thanks TW love the first boot screen very awesome :)
[Nexus S Android Development] tominater12:
So are all the bugs ironed out?
[Nexus S Android Development] simms22:
hey, guess what... op is updated ;)
[Nexus S Android Development] QuantumRand:
Any benchmark screenshots from a 1.6GHz OC???? Pretty exciting.
[Nexus S Android Development] simms22:
haha.. youre going to feel sorry you asked :D

heres a youtube vid i made http://www.youtube.com/watch?v=Gmqf01bOdpE

plus some screenshots

and the last one :eek:
[Nexus S Android Development] alturismo:
Does bt works for anybody on the cm version with this kernel ?

browser seemed very fast now ;)
[Nexus S Android Development] asci:
With 1,5b 1.1 kernel it's the very first time I can run a kernel version over 1,3. However I'm getting continuous rebooting that makes it not usable for daily purpose.
[Nexus S Android Development] morfic:
Test the new kernels, Vmax for bionix and stock tomorrow.
[Nexus S Android Development] deeren:
@morfic,

thanks for the kernels.

Difference between the 3 kernels is only clock speed and voltage?

My phone with latest nightly:

Trinity max: soft buttons backlights not lighting... reboots

Trinity stock: softbuttons backlight not lighting... works good till now

Trinity vmax: lights working as expected (surprised:confused:) , everthing good till now
[Nexus S Android Development] jlevy73:
Quick and dirty results for 3am testing of Vmax:

1.4 is stable: Quadrant = 3810, Nenamark = 48fps (don't understand that number)

1.5 works however, it's only stable enough to run quadrant than it crashes. Got a 4120
[Nexus S Android Development] dario3040:
Its more stable than max but it still freezes on 1.6 and 1.5 GHz.

Could you increase the voltage a bit more? :cool: :)
[Nexus S Android Development] willcpfc:
Loving the stock trinity.....v. stable :)
[Nexus S Android Development] tempera:
It is better than max but again 1.5 doesnt work. As soon as I switch to 1.5 it reboots and also for some odd reason 1.6 works but has too maby force closes and reboots on games such as fruit ninja and angry birds.

I think it has something to do with the 1.5 itself, the voltages should be fine because they run 1.6.

Thanks
[Nexus S Android Development] burnfire:
Vmax cm7 setcpu@1.4ghz

Nan: 61.2 fps

Quad: 3753

XDA APP---*Death to IPHONE!!!! Maybe not yet; Lets torture them first*
[Nexus S Android Development] avetny:
Vmax:

so i believe my stable one is gonna be 1.4 Ghz -always....

1.5, 1.6 no one can run like stable.

if some one gonna tell me he can !... just do this:

-tern on live wallpaper

-tern on music on

-go to browser

(example xda samsung nexus s forum, and play with browser for 10 min)

you gonna get surprise
[Nexus S Android Development] tempera:
I was able to do that with 1.5b but only 1.4 is stable on vmax!
[Nexus S Android Development] asci:
The same here with vmax
[Nexus S Android Development] avetny:
so people DO YOU THINK MAYBE 1.4 ITS last STEP for all of us??????:confused::confused::confused::confused:
[Nexus S Android Development] kenvan19:
Personally I ran quadrant 7 times in a row at 1.6ghz until it overheated and started rebooting. For now i clocked it down to 1ghz just to let it cool for a bit lol

Sent from my Darkginger CM7 Google Nexus S running Netarchy's amazing kernel!
[Nexus S Android Development] simms22:
1.5 and 1.6 are stable for me. ran benchmark after benchmark, no freezes or reboots. i wonder if its possible to "stretch" the limits of my processor from running 1.6 so often. because 1.5 and 1.6 run just as stable as 1.4 and down.

benchmarks are slight lower or the same at 1600, nenamark at 1500/1500...
[Nexus S Android Development] dingdonghei:
Isn't 35000 in and3d extremely good when running at 1.4?
[Nexus S Android Development] bigxie:
I'm sorry if this has been mentioned before, but I have a bug where root apps won't work (SetCPU, Adfree, ROM Manager to name a few). Is this an issue with the kernel or CM7? I don't recall having this issue with the stock kernel.

Either way, is there a fix?

TIA
[Nexus S Android Development] obyn:
nice kernel!

the boot screen looks kind of ugly even though it's a nice motive.

running the vmax version and can get 1400mhz without problems. 1500 freezes/reboots my phone however, so i guess i'm semi-lucky. :)

if i set scaling governor to performance and run at 1400mhz i get 61fps in nenamark.

however if i use ondemand and scaling 100-1400 i get ~40. 800-1400: ~45.

seems like the scaling is terrible.

have you thought about implementing the interactive governor in your kernel?

i remember it made a BIG difference on my old hero (didn't matter if i ran performance or interactive, got same scores since the scaling was so damn good).

regards robin
[Nexus S Android Development] dingdonghei:
+1 on everything he just said.
[Nexus S Android Development] irishrally:
I can't get more than 48.7 on nenmark no matter what I've done. 64.3 in neocore though.
[Nexus S Android Development] obyn:
with "performance" set as scaling governor and 1400mhz?
[Nexus S Android Development] irishrally:
Yes, 1400/1400 and set to performance, set on boot.
[Nexus S Android Development] alturismo:
Same here, also bt wont start and freeze the phone ...

Not all apps but some ...

Its a nice Kernel too see what is possible :)
[Nexus S Android Development] nicholasbgr:
Thanks for the kernel for stock roms :)

Is BT suposed to be working on those? I can't get mine to enable.
[Nexus S Android Development] dario3040:
just turn the screen off, and wait for around 8 seconds.

Then try again
[Nexus S Android Development] jlevy73:
Yes, BT does work but there is a trick to get it to work. Before flashing this kernel you must turn off BT. Flash the kernel and reboot. Then turn BT on. If BT is on when booting the kernel I've found that BT will never work. Also, if the phone should reboot (for any reason) while BT is on, the phone flips out requiring a wipe of cache and dalvik.
[Nexus S Android Development] dinan:
BT not working here... on vmax CM7 nightly 29
[Nexus S Android Development] jlevy73:
The highest I have gotten is 49.3fps on 1400/1400 using Vmax. On cm7-max 1300/1300 would give 59fps on nena

Edit: Odd, I checked the settings on setcpu and even though it was set @1400 it was only clocking 800. Deleted and reinstalled setcpu and 1400/1400 gave 60.3fps on nena
[Nexus S Android Development] dingdonghei:
This is a recurring issue for me as well. You don't have to uninstall setcpu though. Changing the setting fixes it (ie sliding down to 1200 and back up to 1400 again)
[Nexus S Android Development] nicholasbgr:
I keep BT off most of the time and I'm pretty sure that was the case when I flashed the kernel. :(

Update: BT started to work after a reboot. I experienced a new issue though. After the reboot the external partition failed to mount so I rebooted and this issue is gone as well. Is that a know issue? Do you guys think it will occur again?
[Nexus S Android Development] jlevy73:
Yes I've had that issue before along with half dozen of other weird issues. Then again I'm a flash whore so most of the time I just flash whatever I am given :p
[Nexus S Android Development] derfasaurus:
Freezing

Hey, I don't know what I'm doing wrong here. I'm running CM7 Alpha 29 and installed Trinity-Max-CM7 this morning. I'm not using SetCPU or anything but the phone is completely unusable.

It boots up just fine but once it is booted everything is frozen. Things will unfreeze for a few seconds and I can open an app or unlock the phone but then it will freeze again for 30 seconds or so. Eventually the phone just gets tired and reboots. Anyone out there have a similar problem or know a solution?

edit: flashed back my nandroid of CM7 A29 and its running all smooth again. I'd like to play with the kernel but for whatever reason this one is totally unstable, I seem to be in the minority though, don't know what is wrong.
[Nexus S Android Development] demo23019:
Finally 1.3 is perfect and can even run at 1.4 but not stable but oh well 1.3 is plenty for me

vmax/cm7n
[Nexus S Android Development] rb9228:
I noticed you are using Trinity Max. I flashed the Vmax (on CM7 #29)without any issues. Well, at 1400 MHz. 1500 & 1600 MHz on the other hand no so much..it gets squirrelly.
[Nexus S Android Development] derfasaurus:
Where does one set the max amount that you want to OC, especially without SetCPU (since I've read a lot that SetCPU shouldn't be used anymore)?
[Nexus S Android Development] simms22:
with setcpu or a similar app
[Nexus S Android Development] simms22:
anyone still having su app issues, try this version of trinity vmax for cm7 http://goo.gl/gf0Y2

ive been using it since 5am without any su app issues. give it a whirl and let morfic or me know how it goes
[Nexus S Android Development] Doug8796:
Nicely done but you have to admit the galaxy s has the setback of 56fps. I reran and got 2870 in Quadrant so still not too bad.

Thats pretty amazing. The nexus s should be able to get more as well. However, the galaxy s doesn't have a proper gingerbread kernel yet, and not a oc'd one either; so we might see some better results coming out on galaxy s.

Morfic: Would you like to test the dreamcast emu that drk|Raziel is building? your phone seems a bit more quipped than mine at handling something like dc emulation :P

BTW: Do you have a neocore?
[Nexus S Android Development] 651stp:
Get out of here Troll.
[Nexus S Android Development] morfic:
I tried to test the emu a while back, but got constantly sidetracked on irc so i never did get around to that.

My vibrant kernels are limited to 65fps, just like this NexusS kernel, not 56fps as both Vibrant and NexusS are out of the box.

I can not reach those fps in nenamark at 1.4GHz on a Vibrant.

NEocore maxes out at 65fps and is more as a "correct config yes/no" test than a real benchmark like nenamark.
[Nexus S Android Development] Doug8796:
651stp : is your vibrant one of the models that allows for higher than 56fps?

morfic.. could you take a crack at the Captivate as well as it must be similar?
[Nexus S Android Development] 651stp:
im not sure wat your refferring to but i have hit 65 in quadrant with the earth spinning on morfics DoW 1.4

If this is Trinity, then i must be NEO
[Nexus S Android Development] ragiut1:
my NS keeps bootlooping!! on Bionix ROM

Any solution?
[Nexus S Android Development] RinTinTigger:
Wipe both cachesm dalvik and normal one
[Nexus S Android Development] Doug8796:
well then neo :P any way u could unlock other galaxy s's fps limit (including captivate?)
[Nexus S Android Development] ragiut1:
thnx for responding, but it didn't work
[Nexus S Android Development] unremarked:
Had some stability problems with the newest kernel on Bionix. Locked up while in Gmail and YouTube(while video was playing) and rebooted itself to clear.

Flashed back to the Trinity 1.0 version for now.
[Nexus S Android Development] willverduzco:
Same here. Trinity 1.1 has stability issues for me in random places, and so I have reverted to the rock solid 1.0.

The sad thing is that 1.1 benchmarked higher for me than 1.0.

Despite the issues with the latest version, I'm very grateful for your wonderful job so far. I really like running this at 1.2 GHz!
[Nexus S Android Development] RinTinTigger:
Same here! Some issues and reverted!
[Nexus S Android Development] :
Why did you not include 2D/3D benchmark? Was the phone not stable enough to pass it?
[Nexus S Android Development] unremarked:
Quadrant doesn't play nice with Gingerbread(stock kernel, non-stock kernel, custom rom, stock rom, doesn't matter) with those options on. App needs to be updated.
[Nexus S Android Development] ragiut1:
Could someone upload the 1.0 version please

thnx
[Nexus S Android Development] morfic:
Updated OP with 1.3GHz kernel.

V1.1 of 1.2GHz didn't seem to be too popular, removed.

Readded link to the first 1.2GHz kernel, some might like to stick to that.
[Nexus S Android Development] ragiut1:
1.3 worked great

thnx
[Nexus S Android Development] willverduzco:
v1.3 / 1.3 GHz kernel seems to be much more stable for me than v1.1 at 1.2 GHz.

I've stress tested all 5 speed steps in SetCPU and all are stable for at least 2 minutes. Now to stress the indirectly higher clocked GPU... Quadrant and Nenamark1 here I come!

EDIT: Repeated quadrant and Nenamark1 runs tells me it's quite stable!
[Nexus S Android Development] RinTinTigger:
Great!

Still BT not working!
[Nexus S Android Development] rb9228:
Until CM7 CPU settings work or you use a specific kernel with a set speed (i.e. Trinity 15) the only way to select different UV/OC speeds on Max or Vmax is thru an app like SetCPU (or OverclockWidget, CPU tuner, etc.) SetCPU didn't work great for me as it kept FC, but it's good for now.
[Nexus S Android Development] derfasaurus:
Just flashed VMax and installed SetCPU again. Set it to max of 1.3GHz and everything is running smoothly.

Is Max going to save power over VMax? I'd like to get power savings over OC'ing.

Maybe I'll try flashing Max again since I've installed SetCPU.
[Nexus S Android Development] rb9228:
Thanks. Quick question: The link you gave is to #58. The version that's on the OP is #59 (or so it says on my device under About phone). Am I missing something? By-the-way, I'm currently not having su app issues.
[Nexus S Android Development] willcpfc:
Trying the latest one now, thanks :)
[Nexus S Android Development] simms22:
its a different version. i was testing this one since early in the morning. the reason i posted it is because im seeing that some are having su issues with certain root apps. im not experiencing any su app issues with #58, but had the issue with the other versions.
[Nexus S Android Development] XBOHDPuKC:
Trinity VMax + Nightly CM7 = Bluetooth does not turn on. It waits for 20-30 secs and then stays off. Anyone else seen this?
[Nexus S Android Development] XBOHDPuKC:
and it looks like it's kernel's fault. rolled back to CM7 with the stock kernel and BT turns on just fine.
[Nexus S Android Development] burnfire:
Running smooth for me at 1.4ghz after a few tweeks I'm run quad at 3683.. My best score so far. Will keep tweeking.

XDA APP---*Death to IPHONE!!!! Maybe not yet; Lets torture them first*
[Nexus S Android Development] morfic:
Incorrect, reflash the one you say has no working BT, they all do.
[Nexus S Android Development] morfic:
Everyone with root issues and NOT on v1.1, please update!
[Nexus S Android Development] TruLuvNvrDies:
First, kudos to morfic for hooking up this kernel. Curious, what's the average temp people are clicking on Trinity Max? Im running 1.3 at performance and I'm at 91 degrees f. Is that about right? Im new to the OC kernel thing and just wanted to know.
[Nexus S Android Development] derfasaurus:
I had the same issue. Vmax with cm7 alpha 29, Bluetooth wasn't working. Restored nandroid. Will try again though.
[Nexus S Android Development] simms22:
91 is normal. im actually at 91.4 right now, at 1500/100.
[Nexus S Android Development] XBOHDPuKC:
With all due respect... Re-flashed vmax kernel again - BT does not turn on, period.
[Nexus S Android Development] simms22:
go to main phone settings, try to toggle it back and forth a few times, dont use the power widget. then reboot, if that doesnt help after, try reflashing it again. did you flash the kernel with your bluetooth on? im curious actually.
[Nexus S Android Development] robstunner:
noob comment, but the backlights dont work for me until i press one of them after turning the screen on. Stock Rom, Stock rom kernel. Known issue?
[Nexus S Android Development] derfasaurus:
BT on right now. Ill flash vmax again now.
[Nexus S Android Development] simms22:
you should restore the rom, so bluetooth is working. then turn bluetooth off and reflash the kernel.
[Nexus S Android Development] simms22:
after 20 minutes of an3d benchmark at 1600/1600 @109.4F

it actually cooled down from 112 before i took the screenshot :-\
[Nexus S Android Development] jlevy73:
Having an occasional su issue with setcpu. Much better than v1.0 of Vmax but every couple of hours, especially after waking the phone up, setcpu will not acquire root. All other root apps are fine.
[Nexus S Android Development] jlevy73:
BT does work, trust me on this. Non-working BT is a deal killer for me no matter how good it might be.

I will say BT is somewhat touchy with this kernel. When flashing the kernel you MUST HAVE BT TURNED OFF FIRST otherwise no matter what you do BT WILL NEVER WORK.
[Nexus S Android Development] simms22:
i cant reproduce it. what is your setcpu setup?
[Nexus S Android Development] XBOHDPuKC:
i was toggling it through phone / wireless networks / bluetooth. Re-flashed couple time, didn't work - just fell back on the stock rom. I'm not particularly keen on installing anything custom, my only problem with the stock is that I still can't get rid of this System Update is available nag message, and I can't install it since I replaced gmail.apk with the black themed one.

And I'm pretty sure I re-flashed kernel with bluetooth off both times.
[Nexus S Android Development] jlevy73:
Currently I am @ 1400/100 ondemand. Sampling @ 30,000
[Nexus S Android Development] jlevy73:
Ah you're on stock, hmm, maybe that's the issue don't really know. I can say that on cm7 using the Vmax 1.1, BT works fine (Jawbone Icon)
[Nexus S Android Development] alturismo:
also can try what i want, bt no way to get working here ...

my nexus freezes even when trying to turn on.

definately installed kernel with bt off, after freezing i rebooted to recovery and

wiped cache + dalvik cache, same issue then, when i try to turn bt on ...

i will try now again with cm30 and clean install, lets see then

root issues seemed to be fixed in vmax 1.1 cause all apps like widget locker works now

thanks for the updates ;)
[Nexus S Android Development] jlevy73:
BT is Working

See the picture...

To get BT working do the following:

1. Wipe cache and dalvik

2. Flash latest cm7 night + gapps

3. Reboot

4. Turn BT and Wifi off

5. Go back into recovery and flash Vmax 1.1

6. Fix permissions

7. Reboot

8. Turn BT on. Make sure you turn BT on before turning on Wifi

9. Enjoy
[Nexus S Android Development] alturismo:
just figured it ...

BT after wifi is messing up ... seems thats the point.

thanks for your note
[Nexus S Android Development] jlevy73:
Cool, glad you got it working :)
[Nexus S Android Development] willcpfc:
Vmax behaving very well....su apps have behaved as advertised. Bt fine so long as wifi not on at same time.

EDIT.....Titanium could not get root rights just now......first time thats happened on VMAX :)
[Nexus S Android Development] redeyes717:
for those having issues with WiFi and BT.

my findings for ALL of the posted kernel is:

- switch wifi OFF, switch BT OFF

- update kernel

-FIRST: on reboot switch BT ON

- THEN switch WiFi ON

I've had issues since I found this simple sequence.

BT and WiFi works indeed, together.

Red
[Nexus S Android Development] alturismo:
Can confirm that :)
[Nexus S Android Development] willcpfc:
Hmmmm still having root app issues :( permissions fixed etc...but I have to kill apps for them to work.
[Nexus S Android Development] willverduzco:
Trinity13-CFS with Bluetooth!!

For those of us DunDef players (or Opera Mobile or Firefox users), morfic has done it again with a modification of his old Trinity1.3 (which uses CFS) to support Bluetooth.

Download from his Dropbox or as an attachment below.

I have been using this for a little over a day now, and everything is great (as it was on the 1.3 with broken BT), only with functioning BT now. It is completely stable, and very responsive in game... even when in play mode with a ton of enemies.

Thank you morfic!
[Nexus S Android Development] derfasaurus:
Sweet, got mine working. Definitely a sequence thing. Maybe I'll try Max again with that same sequence.

Edit: Same process got Max working as well as vmax.