yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] brianbgrp:
Lol at 144 I got 1700 my first quad...that 3200 I posted was my fourth run.

also I can run t144 @1GHz without issue lol. If I go 1440 certain actions force a reboot(like uploading a pic here lol)

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
thats why i always say to throw away the first two quadrant benches..
[Nexus S Android Development] skinner12:
Bad.. T144 not working here..

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] simms22:
not booting or other issue? try redownloading?
[Nexus S Android Development] skinner12:
Not booting.. A lot of reboot..

Now I'm testing T132. silentrotter :thumbup:

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] simms22:
shhhhhhhhhh... :eek:
[Nexus S Android Development] brianbgrp:
My interest is piqued...

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] skinner12:
Ok ok :D

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] :
I hear secrets being whispered...
[Nexus S Android Development] heX79:
lol, can't wait to flash whatever goodies you guys have in the worx! With how stable T132 runs on my phone, I'll be using this kernel forever.

Just flashed it on a buddies phone yesterday. That and rooted, busyboxed, bootloader unlocked and took him from out of the box GB to ICS for the first time. His 9020A is loving the T132 as well. I found using Doomlords root exploit is perfect for getting root on the phone (while leaving the bootloader intact) so a titanium backup can be used to backup all stock settings, apps and data. Even after unlocking the bootloader, the superuser stuck, I was surprised. Saved a lot of time!

Only small issue I ran into with his phone was the recovery_from_boot.p file or whatever on GB causing CWM not to stick properly. After removing that, all went smooth!
[Nexus S Android Development] Lento10:
T132. silentrotter?
[Nexus S Android Development] skinner12:
New? I don't think so.. :eek:

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] mamba720027:
So I'm running latest teuv and while I was in setcpu I notice it showing my cpu scaleing higher than 400mhz,taught it was weird since the cpu monitor above in my taskbar shows otherwise,the other frequencys was also on another scale but anyways I guess weird screenshot of the day lolz.
[Nexus S Android Development] simms22:
its the 10% oc on the gpu. when the gpu is active, youll see 110mhz, 220mhz, 440mhz..
[Nexus S Android Development] mamba720027:
Ahh I see,sounds kewl :)
[Nexus S Android Development] droidance:
Do you mind sharing the link to latest TEUV ICS kernel? Looked back few pgs but couldn't find it.. Thanks!
[Nexus S Android Development] FL0OD:
Huh... What?

°•neXus S4G•°
[Nexus S Android Development] morfic:
Latest TEUV is still on www.derkernel.com
[Nexus S Android Development] mamba720027:
Yep that's the one I'm useing as morfic mention on the website.

An here's my run on teuv a nice 5+ screen time moderate to heavy usage. I get better time with ksm turn off with barebone trinity but for some reason recently couldent turn it off in cm9 rom control,no biggy just think it scale the cpu more than without it or me being paranoid lolz.
[Nexus S Android Development] xmatrix13:
Hey I just flashed teuv (any) and no big deal but I get no boot animation. I even tried flashing another boot animation but just get a black screen. Fyi I'm using cybergr-mod v8 rom
[Nexus S Android Development] simms22:
yup, thats how it is. flashing a cm9 based rom/kang with a cm9 ramdisk trinity will give you a boot animation. looks like the cm9 ramdisk kernels have been booting on many different roms.
[Nexus S Android Development] xmatrix13:
I just tried flashing the TEUV (cm9) on the same rom but still no boot animation.
[Nexus S Android Development] simms22:
reflash the rom, then the kernel, then boot up.
[Nexus S Android Development] xmatrix13:
If I re-flash the rom do i need to wipe, or just re-flash and then flash kernel?
[Nexus S Android Development] simms22:
dont wipe a thing. reflash the rom, gapps if needed, kernel, boot up, profit.
[Nexus S Android Development] brianbgrp:
What app puts the CPU frequency on your status bar like that?

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] mamba720027:
That's "cool tool" ,found in the market.
[Nexus S Android Development] simms22:
Two kernels, both T132, both with the green flash fixed, both with Trinity colors, both for all roms, both slightly different. no, im not telling you the difference. you decide which is the keeper.. :p

T132-violentotterb http://goo.gl/ewKJF

T132-violentotterc http://goo.gl/XuBT2
[Nexus S Android Development] brianbgrp:
I can't break 2k in quadrant standard with violentotterc but no noticeable green flash. Gonna a try b in a minute

Edit: do these have honeybadgers UV?

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] Lento10:
What's the best way to upgrade?

Should I delete Init.d folder or just wipe? I am upgrading from honeybadger.
[Nexus S Android Development] Dorilife:
Just flashed the violentotterb..:D

Got the beautiful colors and no green flash! Feels hella smooth as allways.
[Nexus S Android Development] albundy2010:
Just flash it Lento
[Nexus S Android Development] brianbgrp:
Ok...at 1320/1320 on demand I did 4 quadrants and 4 benchmark and tuning pro runs. With voc I got 1900/2066/1903/1933 quad and 7912/7933/7916/7940 btpro.

With Vob I got 2766/2154/3033/3055(a new record for me with t132...and close to my t144 record of 32xx). Not sure the differences between the two...but b blows c away for me.

No green flash on either also

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] heX79:
Since we don't know the differences between them, I put both on the phone. Flashed b first, if I get no issues, I'll probably stick with it. Hopefully I won't be missing out on a feature that b doesn't have lol :P

So far, smooth on b. No green flash.
[Nexus S Android Development] d-h:
ViolentotterC, no green flash, but distinct green cast on lowest brightness settings (I like low brightness quite a bit - a great benefit of ICS over GB, IMO).
[Nexus S Android Development] Icecoldmeat:
I'll stick with the violentotterb until the difference is clear.
[Nexus S Android Development] albundy2010:
They both have the green tint with autobrightness on.
[Nexus S Android Development] Dorilife:
I have auto brightness on with no green tint..
[Nexus S Android Development] Icecoldmeat:
Violentotterb has got BIGMEM.
[Nexus S Android Development] skinner12:
With T132 b and c have both a little green tint with low brightness.. For the rest great color as usual.. :D

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] albundy2010:
Then you're using the phone in room that is well lit.
[Nexus S Android Development] Carne_Asada_Fries:
I know I could always push it myself but does Morfic plan on bringing the new boot animation over or is it a Galaxy Nexus thing only?
[Nexus S Android Development] gimiento:
ViolentotterC made my phone grow chest hair. Nice!
[Nexus S Android Development] simms22:
the difference between b and c is the color. c is "cooler white" than b.
[Nexus S Android Development] albundy2010:
People just love to make stuff up. Bigmem type changes can be easily tested. When the total amount of ram available goes up from 335.....
[Nexus S Android Development] brianbgrp:
Than I have no idea why I got such drastic differences quadrant lol

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
difference could be what the phone was running in the background at the time, signal strength, how much ram was available.. it could go on and on.
[Nexus S Android Development] brianbgrp:
Ya both were in similar conditions and shortly after booting without doing anything other than set CPU. Ooh Wells

Maybe my phone just recognizes og trinity colors lol

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] albundy2010:
Back to honeybagerb for me. Don't like the colors on either violent versions.
[Nexus S Android Development] mixtapes08:
Bigmem?

Sent from my Nexus S
[Nexus S Android Development] Icecoldmeat:
I am noticing bigmem, yes
[Nexus S Android Development] mamba720027:
According to simms22, Looks like its just the colors tweaked.
[Nexus S Android Development] thedudejdog:
Don't care, I'm going back to honeybadger. Something about these colors just doesn't look right. Plus I kinda miss the green flash. :p
[Nexus S Android Development] :
Definitely prefer previous colours to c (haven't tried b)

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] ljordan2:
Just tried violentotter b and color seems to be a bit yellowish? Just a feeling. Getting about 20mb more ram probably due to bigmem.

Edit : Tried violentotter c and i like the color of it. White looks more "bluer".

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] FL0OD:
I would agree. I also think that the colors are richer:thumbup:

†††
[Nexus S Android Development] brianbgrp:
do the violent otter series have honey badgers UV?

Also...setcpu updated...but I can't get 100mhz min at all anymore

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] ljordan2:
Violentotter c quadrant

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] albundy2010:
One is honeybagerb. One is violentc. One IS a kernel with bigmem.
[Nexus S Android Development] morfic:
Not to ruin Al's fun....but with everyone so happy with the kernel, I guess I won't have to add BIGMEM at all.

Maybe it's ksm people notice if it's not pure placebo.

No, there is no BIGMEM.
[Nexus S Android Development] formula84:
So confused by this post why not have which pic is what... I see one of them has 363028 total and the other two have 343028 total I am guessing that is the on with bigmem (not moric's) but that one has the lowest available?

@ morfic why not have both...lol I disable KSM because of using more CPU.
[Nexus S Android Development] simms22:
heres mine from violentotterb/cm9 kang.

so is bigmem actually necessary? i can go either way on this, extra ram total doesnt hurt, but..
[Nexus S Android Development] FL0OD:
CM9 T132 VOC

†††
[Nexus S Android Development] albundy2010:
The point of my post with the three pics is rather simple.

I stated yesterday that bigmem is not in the test new test kernels. Stated also what would be a clear indication that it was added. Simms then stated the difference was the colors.

The terminal screens include the older honeybager and newer test kernel along with a kernel that actually does have bigmem. It is a clear as can be that the new Trinity kernel did not have bigmem in it. Two are the same... one has bigmem.

The amount of used/free ram is irrelevant. Took a screen shot with my daily driver kernel that has been running since last night. Other two where after a fresh boot. I just flashed the kernels , booted, terminal screen shot and repeat.

Bigmem is not about free/used ram or memory management like ksm. Simply put it is like physically adding a extra 20mb of ram to the phone. The os will then adhere to the same min free settings etc as always. It just has 20mb or so of memory actually there to use. As the screen shots show.
[Nexus S Android Development] formula84:
Thats what i thought, okay thanks... I agree the more to start with the better. I read somewhere that it takes the 20MB from unused memory allocated to the GPU. Thats why I said why not have both.
[Nexus S Android Development] simms22:
aye, true. dont you love repeating yourself :p
[Nexus S Android Development] heX79:
Id like to know how some of you are able to get 900+ on your 2d graphics quadrant score... Mine is hitting 324 max..

Edit: After flashing both, I prefer the colours of C. Seems a bit more vibrant.
[Nexus S Android Development] mamba720027:
I think u have to enable "force gpu rendering" in system settings/developers option. Don't know if there's more to do with it.

T11 benchmark
[Nexus S Android Development] heX79:
That's what I was missing, thanks!
[Nexus S Android Development] Bandis710:
Just tested your any kernel on oxygen 2.1.6 and so far no problems. Installed an app from the market without a failure message. The bootsound scared the **** out of me :-)
[Nexus S Android Development] catchsomezz:
the latest TUV11+dlt and juicedefender ultimate is doing wonders to battery life.

moderate usage (~20 texts, 2x10min phone convos, 10mins of pandora) and 8 hours later...97%-->79%!

edit: THANKS MORFIC!
[Nexus S Android Development] brainmaster:
The script is not bad, but it kills all of my widgets on the homescreen like Beatiful Widgets or Minimalistic Text.

I'm glad that you got reminded to tweak your Kernel even more that is already very good.
[Nexus S Android Development] coloxim:
Which rom do you use?

Inviato dal mio Google Nexus S
[Nexus S Android Development] kecinzer:
Is there kernel version for Nexus S stock ROM?
[Nexus S Android Development] eiabea:
yes, the new ANY kernel should work ;)
[Nexus S Android Development] tangcla:
haha. I know you did, but as a whole, or does it do anything particularly well etc.
[Nexus S Android Development] morfic:
I used to use oomkiller adjustments in ramdisk.

So that part I believe in.

Anything else is way off.
[Nexus S Android Development] coloxim:
But i don t understand what is it the last kernel..can you explain it?please..

Inviato dal mio Google Nexus S
[Nexus S Android Development] Borky_16:
this kernel can handle every ramdisk so its compatible with oxygen, stock and cm!

oh it is called anykernel!

source: http://xdaforums.com/showthread.php?t=748106
[Nexus S Android Development] brainmaster:
Report on the newest ANY Kernel.

MIUI 1.7.15 - The WiFi Bug is gone, ergo the WiFi can be switched on and off without any problems, no errors.

Here is the screenshot (RAM Script removed):
[Nexus S Android Development] coloxim:
Oh..thanks..And is it better?

Battery life?

Thanks

Inviato dal mio Google Nexus S
[Nexus S Android Development] :
Any kernel working great on the latest CM7 kang
[Nexus S Android Development] wildfire_paulie:
Hello there, just flashed the kernel TUV11-Oxygen

i saw no errors while flashing,

after reboot in my info i see

"kernel version

2.6.35.13-g8057921.dirty morfic@othris #666"

Shouldn't i find "trinity" something?
[Nexus S Android Development] Borky_16:
no dirty morfic is okay!
[Nexus S Android Development] iamxeph:
I have a bootloop on the kernel whenever I turn off the device completely then try to turn on.
[Nexus S Android Development] Babydollll:
Dirty morfic is correct. That's the actual kernel as displayed in about phone....

Sent using two tin cans and some string.....
[Nexus S Android Development] simms22:
last night trinity kernel was just a test, and it passed! heres the REAL trinity11 kernel as you know and love it http://goo.gl/bHTvJ :D
[Nexus S Android Development] lichti1901:
Thanks simms, can i use it with cm? Is it better than the last uv11 dtl? Best regards

Edit: ok, read it in the op!

But what are the differences to dlt?
[Nexus S Android Development] simms22:
i use it with cm
[Nexus S Android Development] Maximilian Mary:
Fine with me. On SG's kernel, my background tasks kept getting killed - music, downloads, steaming radio, etc. I suspect bigmem to be the cuplrit.

Very nice colors on the B test kernel. On samoled, there's just a slight blue tint compared to a piece of paper in daylight, but the grays are good, and the white is very clean. The kernels on derkernel.com had a bad case of jaundice, but this is beautiful.

Edit: As some else pointed out, though the green screen is gone, there is a green pall on brightness levels under 12. (White, however, remains white.)

Edit 2: Wups. I just realized these come with the GSM NS ramdisk. :rolleyes: Will I have problems using this on my ns4g?
[Nexus S Android Development] tobybobby:
Everytime i tried to underclock the 1.32 violentotterC kernel at 800 Mhz, the screen was filled with artifacts and then the phone rebooted. Battery state was at 40%and i am running 4.0.4 IMM26 rom from evilisto. Any ideas?
[Nexus S Android Development] mamba720027:
Probably its the OC/UV gpu,not much I can think of u can do about it, can try bump the min cpu to 800mhz then drop the Max CPU freq to 800mhz then drop min back to 200mhz an if it freezes,then just try min 100/200mhz an max 1000mhz. Just means your cpu may need more volt at 800mhz but it fluctuate between frequency and works out without a reboot on the higher frequency sometimes,dosent rule out instability still exist. Anyways don't know if all that makes sense but instead of doing all that just to UV best to run the t11 kernel or teuv.
[Nexus S Android Development] thedudejdog:
yea, just run it at 1000 MHz. that's what i do.:p
[Nexus S Android Development] ghling:
I did a bit of benchmarking today with the the following kernels:

1. CM9 Nightly #6 (20120305) Stock kernel

2. T11 Honeybadger

3. T132 Honeybadger c

4. T132 Violentotter b

Options were:

- max. cpu frequenz (1320/1320, performance; except T11: 1096/1096, performance)

- forced gpu-rendering enabled

- best score out of minimum 5 benchmarks

- userd benchmarks: 1. Quadrant Standard, 2. Antutu and 3. Benchmark & Tuning Trial

So, here are the results:

1. CM9 nightly #6 (20120305) stock kernel at 1320/1320, performance:

2. T11-honeybadger at 1096/1096, performance:

3. T132-honeybadgerc at 1320/1320, performance:

4. T132-violentotterb at 1320/1320, performance:

Interesting results as CM9 stock kernel beats other kernels in Antutu but not in Quadrant and Benchmark & Tuning.

Anyway, does somebody know if it is possible to (faster) "benchmark" the battery life with different kernels except from just looking how long a full charg lasts?
[Nexus S Android Development] simms22:
the only reason cm kernel beats out trinity in antutu is because cm kernel is using morfics 65fps "fix" and morfic removed this "fix" from trinity(because it actually doesnt actually help anything). if you notice on the graphics benchmarks in antutu, cm kernel will see a higher fps than with trinity.
[Nexus S Android Development] jgreene1014:
What am I doing wrong?

First of all I am loving 132 honeybadger!

I am getting a problem were every once in a while I get a major lag or un responsive applications.

all data was wiped, formatted everything and ran rom prep tool. (installed kernel with fresh rom)

Only change I made was moving up the min CPU to 200 in NSTOOL and turning off backlight and blink.

A quick reboot get everything flying again.
[Nexus S Android Development] morfic:
More a focusing on other issues first.

Now slowly reapplying old patches.

As often as people love and hate the 65fps , it was not high on priority.

It varies since it depends on the game of it helps or hurts.
[Nexus S Android Development] droidance:
Is there ways to change setting like turning backlight dim on, change scheduler without using NSTools? I have both SetCPU and NSTools so I want to get rid of NSTools..
[Nexus S Android Development] xmatrix13:
+1
[Nexus S Android Development] morfic:
You can control those with a init.d script, since mostly you only set how you want it and don't fiddle with it.
[Nexus S Android Development] funkiefresh:
Happens to me also on CNA 1.4 with T11, T132, T144 (refuses to under clock to 800 MHz without glitching. Kernals work normal at higher than 800 mhz.

Tried both setcpu and nstools.

Strangely not affecting TEUV which has an under volt.
[Nexus S Android Development] Dorilife:
Just updated AOKP to milestone 4 and then flashed violentotterC and got the trinity boot animation!:D

Is it me or boot animation wouldn't work on the previously released Trinity kernels..

Anyways still working great here.
[Nexus S Android Development] limeroo:
Green tint

Hey all. Just wanted to chime in on the green tint --- I'm pretty sure this isn't specifically a problem with the kernel itself, but a combination of the low brightness limits set on the AMOLED screen.

If you've ever flashed another ROM that allowed you to customize the brightness levels, if you've ever tried to set the lowest brightness to a really low number (below 10, I believe) the screen would get the green tint. Raising the brightness above that number removes the green.

What I'm thinking is happening is: The auto-brightness feature on Trinity allows a lower setting than the threshold where our screens turn mightily green :)

Morfic -- Any chance on raising the lowest brightness setting? If this really is the case, of course. Would help prevent this issue.

BTW MORFIC thank you for your T11, I had flashed Pixel's mod, and Chrome/Browser would get sluggish till it died, then flashing your kernel and all is speedy again.
[Nexus S Android Development] simms22:
it worked.. just not with the previously released aokp :p

---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------

T132, finally caught up with and passed that transformer prime..

oh, and my antutu bench with 65fps enabled in t132
[Nexus S Android Development] morfic:
You are welcom, but give it time, make sure it's not just the reboot ;)

And for everyone: about green tint.

the green "flash/flcker" should e gone on newer kernels, using the term tint would be more appropriate if you look at a white area and it has a green tint. If it's not true white

considering the fix to prevent the green flicker requires a new set of offsets, i could believe in tint, but that then no longer relates to the lowest brightness levels.
[Nexus S Android Development] tobybobby:
I think that 22022012 t11 kernel is the most optimized kernel. It combines performance, smoothness and good use of battery. Seems also that the phone runs best at 1.1ghz.
[Nexus S Android Development] simms22:
someone was wondering about BIGMEM? this isnt BIGMEM, this is BIGGERMEM :p

(highly experimental and the camcorder wont work)
[Nexus S Android Development] GideonX:
You tease

:D
[Nexus S Android Development] HAKA:
Awesome kernel!

9000th post! :D
[Nexus S Android Development] DaXmax:
Something big (upd) is coming. :rolleyes::rolleyes:
[Nexus S Android Development] simms22:
now THATS a tease ;)
[Nexus S Android Development] skinner12:
Wow ;-)

Nocerino's Rulez CM9 ;-)
[Nexus S Android Development] DaXmax:
Thats a mighty one. Top Secret thing. ;)

Superbly awesome. Waiting for the final one. ;)
[Nexus S Android Development] d-h:
About the green tint: it only appears when the phone reaches the lowest brightness setting, and it is very green (it is not subtle by any stretch of imagination). Very distinct change from blueish to very green.

violent otter b

pixelrom 1.6

I920A
[Nexus S Android Development] Highway 55:
Although it still has a green tint, at least the flash is gone and the tint is quite a bit more tolerable. It is a soft olive tone rather than a bright lime green. Any improvement is better than none at all. VOC is running great here!
[Nexus S Android Development] nexus_junkie:
Any kernel version (zImage only) does not touch the ramdisk of the ROM?

Are there the reasons separately releasing CM9 ramdisk version (boot.img = zImage + ramdisk)? :confused:
[Nexus S Android Development] simms22:
there was reason, not anymore since the cm ramdisk version is booting on all roms.
[Nexus S Android Development] nexus_junkie:
Any kernel version maintaining the ramdisk of CM9 ROM and just replacing the kernel (zImage)? And yet CM9-ramdisk-included version needed? I'm very curious to know. Any kernel version not enough for CM9?