yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
Thanks.

Yes, all P2C kernels are pre2.3.3 voodoo color kernels.

For those who don't like the yellow snow look of the later kernels.

In the process of needing further test kernels due to an influx of random reboots, this detail is no longer obvious.

Stable kernels are in OP.

In thread are test kernels, anyone is welcome to participate in testing.

However these are "special interest" as they have no dimmers either.

Thanks,

Daniel.
[Nexus S Android Development] jjhrrsn:
I've been on the newest test teuv and not one issue since deleted the 95 dimmer. This was the one posted on 9.14
[Nexus S Android Development] asdfghjkl:
Im using the Teuv from OP and i had my first freeze up today. Phone was locked and bottom button lights were on and i had to pull battery...never had a problem on older trinity kernels :/
[Nexus S Android Development] Bamdroid:
Wonder if that's the fix?? May hafta try that.. I just use touchwake script anyways.

私のネクサスSから送ら
[Nexus S Android Development] Kurupt1:
I have not had one issue. Been testing each new release. Good work morfic!
[Nexus S Android Development] treUse:
Loving the pre 2.3.3 colors, keep the awesome work up :)
[Nexus S Android Development] formaldehyde:
I flashed the newest test kernel simms posted and left my phone on the charger overnight. This morning it showed full charge (screen was on to get to 100%). When I tried to start any apps they just FC'd so I decided to boot. After the boot the phone showed only 67% of charge (it was still on the charger), so I decided to go back to the TUV on the OP. It's stable for me.
[Nexus S Android Development] Tenhi:
Not working for me :(! Random reboots while I was sleeping :S. And what's up with that boot sound :S? Woke me up few times during night :S. And those colors are not great for me. Normal pre 2.3.3. colors are too pinkish, and voodoo pre 2.3.3 are too greenish.

Again, back on TUV10, and annoying boot sound is still there :). How to remove?
[Nexus S Android Development] melvinchng:
System/media delete power on folder... 120911 uv is quite fine without screen dim

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] morfic:
Guys, check the "Endursa link" in the OP.

Enjoy

'night!
[Nexus S Android Development] formaldehyde:
morfic: could you please have a look at http://xdaforums.com/showthread.php?t=1239240&page=4 -- the touch key dimmer needs a bit of tweaking on i9023. It would be great if you could implement that :)
[Nexus S Android Development] morfic:
Tomorrow, got sidetracked with the dimmerless branch.

Also need to see why people can't git clone my source.
[Nexus S Android Development] :
it works well thanks.
[Nexus S Android Development] superfloup:
Woow, 3d render is really better ! Thanks morfic !
[Nexus S Android Development] melvinchng:
No freeze in uv11 120911... but it do freeze while I turn off my screen while playing fruit ninja. The screen won't switch on.

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] Roscopcoletrain:
once or twice I get the issue where the screen wont turn on. Try plugging the phone in if you have a plug handy. Seems to work most of the time.
[Nexus S Android Development] :
latest quadrant

1000Mhz

1400Mhz
[Nexus S Android Development] melvinchng:
Tuv11 can reach 4000++...

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] steve.garon:
This is a superb mod! You should add it in your kernel install script :P

So it basically removes the GL driver right? what driver does it use instead?
[Nexus S Android Development] jungbum:
TUV11 0912 and Erdusa Modification, which seemed to have upped the FPS to 65
[Nexus S Android Development] JmPTaz09:
Using the healthy as a horse TEUV with no problems... never seem to get freezes or reboots with TEUV... TUV is nice while it runs, but freezes too much on my phone. I don't notice any decrease in performance at 880 for my uses...
[Nexus S Android Development] endursa:
it only removes the software rendering libGLES afaik! so hardware GLES is used all the time :)=
[Nexus S Android Development] simms22:
t1440 from 0809 benched with quadrant, with the libGLES removed, 1440/1440 ondemand. check out the insane 3D score :eek:

thanks endursa
[Nexus S Android Development] dario3040:
I knew there was something fishy about the Nexus S 3D score..
[Nexus S Android Development] anremi:
TEUV880 : 3300++

Amazing !
[Nexus S Android Development] melvinchng:
Hmm... hope it is a daily kernel.. but it is not.

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
what was your 3d score before? yes there is a 65fps frame limit on the nexus s and 68fps on the ns4g.
[Nexus S Android Development] reddv1:
So is there any downside removing libGLES_android.so?

Sent from my Nexus S
[Nexus S Android Development] lolokman:
3d score is 200-300 higher after the fix

btw, finally reach 5600+ score with t1536 kernel:)

but 3d test still stays at 65fps:(
[Nexus S Android Development] simms22:
there you go..

btw, the nexus s is capped at 65fps.
[Nexus S Android Development] Tenhi:
Can someone explain to me what's the purpose of trying to get best score possible in Quadrant :)? Turning on airplain mode, wiping this, wiping that, closing processes, just for a higher meaningless number :P.

Real use performance and battery life is something that matters for me :)...
[Nexus S Android Development] cheech87:
It's not about getting a higher number. It's about having a standardized way of measuring performance. If you pick up your phone at a random point during the day and run quadrant, there are many factors that will greatly affect performance. By cutting out the radio and closing the processes that are currently backgrounded, you are now able to compare two quadrant runs from separate kernels without having to worry about exogenous randomness. It puts both kernels on a level playing field and reduces the risk of "lucky" or "unlucky" quadrant runs.
[Nexus S Android Development] simms22:
just for fun mostly.
[Nexus S Android Development] Tenhi:
Thank you both :)! I have now two points of view on that matter, and I prefer the first one :P...Because all I can see is that people are clocking CPU to the max, and posting their "amazing" score, can't see anything helpful and useful about that :cool:
[Nexus S Android Development] simms22:
its actually useful to compare quadrants when youre working on kernels. that way you can see how changes made effect the phone, whether the changes are good or not. and to a point, they do show you real world performance.
[Nexus S Android Development] cheech87:
Yeah, this was the point I was trying to get at, but kind of got away from me while I was typing my response lol.

Anyways, no benchmark is perfect. But whenever it's possible to compare two things via an objective measure, it shouldn't be overlooked.
[Nexus S Android Development] Tenhi:
I believe that in those cases scores can be more than useful, but here, in most cases scores are just like, "hey, look how big my **** is, it's WAY bigger than yours". And I'm not so sure that they are showing real world performance, because I don't believe that many people use their phones overclocked to 1.5 GHz and with radio and WIFI turned off, with all background processes closed...

Ah, enough of this :P. That's just my opinion on that "phenomenon" :P...

Edit:

Totally agree on this! I was just trying to point on bolded part above :). It's how I see some of the quadrant scores posted here :P
[Nexus S Android Development] dario3040:
I don't kill tasks before benchmarking, and I am running 1.44Ghz as a daily driver, your point is invalid :eek:
[Nexus S Android Development] Ezekeel:
I think his point was that synthetic benchmarks like Quadrant do not properly reflect performance in real-life usage scenarios. The **** thing was just internet humor to lighten the mood, like http://www.catsthatlooklikehitler.com.
[Nexus S Android Development] simms22:
alrighty then..

using that rational, i think that i have the bigger ****. nothing in the background was killed, everything is on as usual. T1544 1544/1544 ondemand with that file deleted :p
[Nexus S Android Development] Tenhi:
LOL :D! Great! Amazing, huge, brilliant co...i mean score :-P
[Nexus S Android Development] matt2053:
Can you post a link to dl that 1544 kernel? :D
[Nexus S Android Development] simms22:
heres the download link for T1544 from 31052011 http://goo.gl/OlytF

if it breaks your phone, i am in no way responsible :p

and yet another, soooo close to 6000. i feel that 6000 is gonna get broken sometime today :eek:
[Nexus S Android Development] morfic:
We all knew it, my Vibrant always did 65fps on planet.

Just how simple the fix is I didn't know.

Sent from my Trinity G2x
[Nexus S Android Development] jlevy73:
I got 4051 then it murphed on me, with corpses
[Nexus S Android Development] jlevy73:
Morfic's github just gave me a headache :eek:. Couldn't find the acpu file that would have the listing of all the voltages he used.
[Nexus S Android Development] adewey234:
I'm just asking because that version looks like it is supposed to be matched with the kernel cyan uses now...I haven't compiled a kernel but I have screwed around with ramdisk images etc... but I think this could lead for a more stable BFS version. I love BFS because it can be really fast if done correctly. I haven't seen an awesome kernel with BFS since I had my G1, when we first started incorporating it into kernels. What do you think?
[Nexus S Android Development] RickROM:
What is the easiest way to completely disable the bootanimation? I liked the Honeycomb one, but I'm not feeling this new one . . . I still get the splash screen before the bootanimation if I disable it.
[Nexus S Android Development] jlevy73:
Cyanogen using BFS kernels :confused: AFAIK he hasn't used them in years going back before the Nexus One was released.
[Nexus S Android Development] adewey234:
Yes I know, but im saying the kernel that he is using, 2.6.37.4 and use the patch that matches that version.
[Nexus S Android Development] jlevy73:
Gotcha, make sense.
[Nexus S Android Development] terryhau:
Rebooted again at 1.44ghz.

I guess i have to use 1.0ghz, which sucks because it was fine at 1.4ghz.

The splash at the start is programmed into the kernel.

The only way to remove it, is to get the kernel source, change it, and build it yourself. I'm not sure why the splash is needed when there's already the boot animation, and the spash is just the same as the first frame of the boot animation.

I guess morfic wants to still show his kernel, even when people change the boot animation.
[Nexus S Android Development] RickROM:
Thanks . . . that is what I gathered from searching, but I wasn't sure if that was the only way. I don't really want to mess with the kernel since I don't know what I'm doing.
[Nexus S Android Development] RickROM:
Highest score I've seen on any of my phones . . . runs really well so far. Thanks!
[Nexus S Android Development] simms22:
if you kill some of that background activity that you have going on, youll probably hit 4000.
[Nexus S Android Development] RickROM:
Haha . . . I was thinking of doing that, but I decided to be lazy and just reboot it before running the test.
[Nexus S Android Development] G1_Lucky:
I pulled that one off ;)

lol

Morfic wanna give me a 1.8 :D
[Nexus S Android Development] dario3040:
1.8 is definately gonna fry it after a while.
[Nexus S Android Development] dario3040:
Morfic, would it be possible to use the same voltages and the same bus speed as trinity 15b (cm7) ?

Could be stable
[Nexus S Android Development] kevin_ngckk:
im using nscoll 1.0.19 and i have oc to 1440ghz.

but it reboot:( what can i do?
[Nexus S Android Development] dario3040:
Sadly, you can't do anything.
[Nexus S Android Development] kevin_ngckk:
what cause this result :(???

it that im using the cm internal oc??
[Nexus S Android Development] dario3040:
Your phone can't handle the overclock, maybe its too sensitive or its too little voltage. Its hard to tell.
[Nexus S Android Development] alexis_p3300:
I also freeze at 1.44 sadly,i was running perfectly on h15 zotir,and other h1.4 kernels,less voltage here?
[Nexus S Android Development] arash64a:
i use of CM7 nightly rom and i want to use any kernel without oc and only under volted for better battery life with the same performace, now i yhink i must use of this kermel, wich kernel u prefer for me?

Please any direct link?

tnx
[Nexus S Android Development] gotjazz:
falling head over heels with the new uv11 right now.

Some past releases have been even better battery-wise but this one is still great plus it's quick as lightening and smooth as butter. no slowdowns, no hanging nothing.

Awesome! :D
[Nexus S Android Development] simms22:
trinity1.1ghz should be good for you http://t.co/UakvKxl

its only slightly oc but very uv :D
[Nexus S Android Development] gullygossner:
What uv settings are being used?
[Nexus S Android Development] dsellers2:
The good ones. :/
[Nexus S Android Development] lvnatic:
Is there any way to apply the kernel without touching the boot img and boot animation? I prefer the stock ones from, "Google".
[Nexus S Android Development] window7:
No :p It's in the Boot.img.
[Nexus S Android Development] johnkim0011:
New Trinity UV12 for Nexus S seem to eat up battery power pretty harsh.

Did 5 minutes of Facebook on 3G, some XDA and net surfing on WiFi, transferred some files from Dropbox.. I unplugged my phone about 6 hours ago and I'm already at 60%, whereas with NS4G version of T12 last me over a day...?
[Nexus S Android Development] window7:
Really? Hmmm. I see that NS is better over NS4G :D
[Nexus S Android Development] drizztzou:
Yes, I also saw better battery on new T12, but with this new T12, I can not get USB to work:confused:
[Nexus S Android Development] window7:
Hmmm. I have flashed every kernel of Trinity, never faced issue with USB :)

Do you have chain fire 3D installed??
[Nexus S Android Development] nickwarn:
It doesnt work here either (i9020T). And theres people complaining about usb not mounting on TUV12 in diffrent threads. For me it doesnt matter as long as i can mount from clockwork.
[Nexus S Android Development] arash64a:
Thanks but usb connection not work with this kernel!

no any kernel without issue?

tnx
[Nexus S Android Development] dario3040:
I know how you flash it without the boot animation, but not without the image.

Just open the kernel in winrar, and go to the system/media folder, and delete the bootanimation.zip, and if a folder called poweron exists there, delete that too.
[Nexus S Android Development] igor.tonky:
opposite experience - working good on i9023 here.

1d 5h on, 35 mins display on - 55% left.
[Nexus S Android Development] vivmar:
i have flashed latest test versione of T1.2 and i have noticed:

*Bigger battery consumption thant older 1.2

*Strange thing:i can set highter frequency like (1.4-1.504-1.544)...why???
[Nexus S Android Development] martinsjt:
I have the same USB issue with the T12-CM7-NS-VSV9-6142011 on I9023.

Works fine with T12-NS4G-VSV9

Best
[Nexus S Android Development] arash64a:
witch kernel dont have any problem?
[Nexus S Android Development] window7:
I guess, something goes wrong with your phone. DO you do a dalvik cache wipe?
[Nexus S Android Development] simms22:
UPDATED! Trinity1.1ghz UV. Special Edition http://goo.gl/sTzM4

btw Oppenheimer was removed. if youre still getting Oppenheimer, remove the old file from /system/media/audio/poweron/.
[Nexus S Android Development] thedudejdog:
Flash this at your own risk. Haha my ns4g froze the second I hit OC.

I tried it twice.
[Nexus S Android Development] morfic:
Without knowing how far to OC, you don't know how far you could safely UV.

The benchmarking is not all about OC.

A tweak that affects memory throughput, file io, removes broken software rendering libs, changes memory management, removes debugging all affect your daily realworld use and are not OCing.

Now how do suppose this gets measured in means other than "well, I think it feels better."

I use the "feel" measure on top of something more objective. Just not as sole measure.

So what if people have a little fun with benchmarks.

I think it's hilarious my nexus s outscores my G2x

Now sure, the io seems disproportionate, and 3D is higher...wait was higher on G2x, but guess what I do more of? Starting apps, not playing games.

It all has merit, other people care about other things more than you and I.

I don't like the tone of this post, you are not better than anyone else, without the meaningless numbers, you wouldn't get what matters to you.

Sent from my Trinity G2x
[Nexus S Android Development] morfic:
reddv1:

git clone http://morfic.euroskank.com/git/linux-samsung.git -b android-samsung-2.6.35

or -b testing

just need to be given a branch, voila

morfic@othris:~/NSDEV/testclone$ git clone http://morfic.euroskank.com/git/linux-samsung.git -b android-samsung-2.6.35

Cloning into linux-samsung...

morfic@othris:~/NSDEV/testclone$ ls

linux-samsung

morfic@othris:~/NSDEV/testclone$ ls linux-samsung/

arch COPYING crypto drivers fs init Kbuild lib Makefile net REPORTING-BUGS scripts simplified-quickbuild.sh tools virt

block CREDITS Documentation firmware include ipc kernel MAINTAINERS mm README samples security sound usr

morfic@othris:~/NSDEV/testclone$
[Nexus S Android Development] gotjazz:
Just testing the tuv 1409 kernel simms posted. Quadrant score is about the same as 1109 but fps in 3d tests seem to be quite a bit lower. Well high enough anyway.

Mostly curious about battery usage
[Nexus S Android Development] Tenhi:
Tone? I was just joking because I found some of those posts with quadrant scores funny :). Nothing more ;). And I was just curios why do people do that ;). I said that it is just my opinion, and I didn't mean to offend anyone. I tried to put many smileys in my posts, but i guess that wasn't enough :p. Sorry again to anyone who didn't like my "tone" :(

Enough now, I got few opinions :). Let's talk about things that matter :cool:
[Nexus S Android Development] morfic:
Alright, sorry, you are not another Tanclown.

Yes, the Smileys were not enough, shame on you missing the humor marking Smiley quota like that.

Sent from my Trinity G2x
[Nexus S Android Development] simms22:
that damn TanClown.. gets me all worked up too. i just want to shake my fist at him.
[Nexus S Android Development] matt2053:
I don't have any problems on 144, but this is rough. It runs fine until i get to the 2d graphics on quadrant then it crashes back to the quadrant app main screen. hrrmmmmm i shall keep trying.
[Nexus S Android Development] simms22:
are you using ondemand?

also, be sure that your phone isnt hot. if it is, that could make it freeze at this high oc. in the mid summer, id bench in front of my ac or put it in the fridge for 15-20 minutes before benching. but its cool in nyc now, so i didnt have to do any of that.
[Nexus S Android Development] matt2053:
I had the battery cover off and had a fan blowing on it :)

I think maybe 1.44 ghz is my Max. But that's better than my old Nexus S that I replaced. It could barely do 1.2.
[Nexus S Android Development] melvinchng:
Petrol gives you 65... I think you need liquid oxygen + hydrogen to get more than 65...

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] Maximilian Mary:
I barely broke 5000 with this one, but i can get 5600 with 1576. ;)
[Nexus S Android Development] simms22:
finally broke the 6000 barrier on quadrant :eek:

Trinity 1.544ghz and the latest cyanogenmod kang by @gearheadcustoms

thank you morfic, this is all your work, not mine.
[Nexus S Android Development] jjhrrsn:
Photoshop
[Nexus S Android Development] simms22:
:eek:

are you seriously saying that?
[Nexus S Android Development] jjhrrsn:
Lol /sarcasm
[Nexus S Android Development] jjhrrsn:
Hahaha seriously been waiting for you to break it all night to say that
[Nexus S Android Development] melvinchng:
Is it photoshop?? Or it is real?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] melvinchng:
Happy 4000th post! :-)

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] jjhrrsn:
Real. I was giving him a hard time
[Nexus S Android Development] SA-07:
I love xda.

Eeek. ;)
[Nexus S Android Development] simms22:
its real. and happy 4000 :D
[Nexus S Android Development] melvinchng:
Tuv10 300811 super stable... check quadrant :-)

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] JmPTaz09:
Yeah, TUV10 was nice and stable!
[Nexus S Android Development] simms22:
teuv is still my favorite.. from 09082011
[Nexus S Android Development] JmPTaz09:
Yeah, TEUV's have been pretty stable for me also. I don't fare well with the others, but TEUV and TUV10 usually don't give me any reboots/freezes. The old TUV11 was always my favorite, which was apparently only 1 ghz all along, but it was fast and stable none the less with good battery life.
[Nexus S Android Development] melvinchng:
What is the bus speed of tuv10? Is it stock? Cause it is much more stable than tuv11

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
i think it was stock
[Nexus S Android Development] melvinchng:
Can you cook me uv11 with stock bus from the uv10? :-)

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
im not the guy to ask.. you know who you should ask :)
[Nexus S Android Development] jjhrrsn:
Plus 1 teuv is the bomb
[Nexus S Android Development] melvinchng:
He is not here :O

Anybody home?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
hes on #trinitykernel in IRC right now
[Nexus S Android Development] melvinchng:
How to sign in into androidirc?

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] simms22:
webchat.freenode.net

user name

#trinitykernel

fill in the security letters

log in
[Nexus S Android Development] applefanboylol:
Wow GPS lock is fast! Came from netarchy, not disrespect to his kernel but GPS is a must for me. Ill be testing it more!

12092011
[Nexus S Android Development] ellesshoo:
+ 1, can't for the life of me understand scrapping the most stable variant of this kernel and the one most similar to stock clock speeds. I certainly don't have morfic 's skills in this area so it's pretty frustrating.
[Nexus S Android Development] morfic:
Don't be so Frustrated, i "scrap" TUV10 if TUV11 is stabilized.

I will not throw out a kernel if there is no stable replacement.

Everything right now is testing.

If you see the kernels i work on in OP, then they are stable.

If TUV is table at 1.1GHz, great, if not, TUV will be 1.0GHz

Right now my favorite is TEUV though.

Don't confuse what happens in the thread with what's in OP, which is where it seems you meant to look.
[Nexus S Android Development] fr4nkr0c:
I use the latest Kang, with the TUV11

are 2 days and is very stable and so far I have not had any restarts ..

hopefully good!
[Nexus S Android Development] melvinchng:
Any tester?

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

Accidentally sent from my Nexus S using XDA Premium App
[Nexus S Android Development] stavros86:
Morfic have you changed voltages on your last 1.44Ghz kernel?I tried all your kernels a month ago (previous versions) and everything stuck after few minutes, now i run your latest 1.44Ghz for an hour with lots of quadrant tests and games and it works flawlessly!
[Nexus S Android Development] dsellers2:
Love The teuv too.

My favorite thus far. The teuv From 09/08 with the eezekiel mod. A day of battery life and have made it last 2 days, and now I'm getting 3400 quad after deleting that lib file. No reboots since the day I installed it on the 9th of September. That's what I call stable. :)
[Nexus S Android Development] Tenhi:
I did, and failed at "rm /cache/dalvik-cache/*" there's no that dir...and after that everything started FCing....had to remove battery...
[Nexus S Android Development] melvinchng:
Thanks for your feed back... ha-ha!

Accidentally sent from my Nexus S using XDA Premium App