yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
Well, that's your fault :-P
[Nexus S Android Development] simms22:
i tried to thank you, but xda says that im only allowed to thank a certain number of people per day :p
[Nexus S Android Development] dinos3:
now being tested for t132 hbB, for now everything working fine. ;) thanks

honeybadger is undervolted for more batter life or is not it ?
[Nexus S Android Development] thedudejdog:
Now, I may be "out of my element" but talking about refresh rates, what's the lowest you could go if someone only used the ui, never games or benchmarks? From a battery saving standpoint?
[Nexus S Android Development] d-h:
If it was only a green flash, I wouldn't mind, but if I try to use automatic brightness the whole screen turns green until I turn up the brightness.

Any way around this? I love T132 (testing honeybadger b) but I also really like low screen brightness...
[Nexus S Android Development] d-h:
Honeybadger c fixes the issue... why is it "dead"?
[Nexus S Android Development] ljordan2:
as morfic states it's purer Trintity.
[Nexus S Android Development] Drizzzle01:
Are any of these honeybadger versions for us ANY users or are they specific to CM/KANG users?
[Nexus S Android Development] thedudejdog:
Because it's not trinity with those colors :p
[Nexus S Android Development] morfic:
Correct.

Auto brightness users could augment the lowest level and there wouldn't be any green.

After the fix in c changed the color i tried no fix but different offsets.

But i had an idea after d, will test idea after work or tomorrow.

Depending on how moving disks goes.
[Nexus S Android Development] brianbgrp:
Simms...what an I missing to get Vellamo scores like yours.. I can't break 1280 on t132 with latest Kang.

Not that it's a huge deal...just wondering if I'm missing a performance setting

Edit. Also do you use surface dithering our 16 bit transparency?

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] heX79:
I love T132! (T132-NS-ICS_ANY_22022012). Runs very stable!
[Nexus S Android Development] simms22:
i dont enable surface dithering or 16bit transparency. i do allow purging of assets though. maybe the difference is what apps are or arent running in my/your background.
[Nexus S Android Development] brianbgrp:
Ya...I'll have run some tests later when I got some free time.

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] droidance:
Is it suppose to flicker in green more with stock ROM? I went back to Stock ROM and flashed the same T11 kernel I flashed on CM9 yesterday but it flickers green more even at higher brightness setting (of course with auto brightness off)?

Edit: I noticed the whole screen turns into green (similar to nightscope like green) when the screen is about to go off. It is consistent thing right now... still using the same T11 honeybadger kernel since yesterday. Didn't have this happen with CM9.
[Nexus S Android Development] brianbgrp:
Im convinced these honey badger versions are scared like cobras. It refuses too budge while idling...then just wakes up and goes back too work like nothing after. Crazy.

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] FL0OD:
T132 Honeybadger CM9 Euroskank Surface Dithering Disabled Surface Dithering

°•neXus S4G•°
[Nexus S Android Development] brianbgrp:
Lol so no difference really. Thanks for testing flood!

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
hmm.. :p
[Nexus S Android Development] brianbgrp:
Lol what settings on there?

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
1320/1320 ondemand, no special settings. but right before i benched this, i was tethering. my phone like being benched when its already warm/hot.
[Nexus S Android Development] tyea:
Everything works with the latest euroskank and Trinity T11 cm9 version kernel. I'm getting really high Quadrant values compared to other kernels running at 1100, yet I haven't noticed a significant change in user experience. Does this mean that Quadrant is not a good benchmark for judging speed and fluidity interface improvement, plus web page rendering speed?
[Nexus S Android Development] simms22:
for web page rendering Vellamo benchmark is good.
[Nexus S Android Development] mixtapes08:
Which one is better in performance and battery? Normal T132 or t132 hbc?

Sent from my Nexus S
[Nexus S Android Development] thedudejdog:
Honeybadger. It doesn't care
[Nexus S Android Development] dario3040:
http://www.youtube.com/watch?v=4r7wHMg5Yjg
[Nexus S Android Development] eniamg02:
Just making sure.this is a any kernel, correct?

Sent from the other side of town.
[Nexus S Android Development] simms22:
no. at this point honeybadger is a cm9 ramdisk kernel while its being tested.
[Nexus S Android Development] heX79:
I'm currently testing T132 Honeybadger B on Evilisto's IMM26 port. So far it's running extremely slick! I think I found the new Kernel creator to follow, going forward! The green flicker is a bit annoying (when I actually notice it) but nothing seems to touch the kernels performance! :D

Pardon my ignorance, is it the colour settings that are causing the green flicker? The colours are just too good to give up!

Edit: Just read Simms post above, understanding that it's a CM9 build, should I have any issues, I will flash the T132 Any kernel and see if it persists, before posting a bug.
[Nexus S Android Development] simms22:
well, im glad its working on a non cm9 build. possibly its based on it or is using cm9s ramdisk? it should work on any rom thats has some cm9 base. anyways, its the voodoo color used for trinitys color that has the bug. morfic found something that fixes the green flash, but it ruins trinitys color. trinity isnt trinity without its color. that said, fixing the green flash is on the to do list :D

---------- Post added at 05:50 PM ---------- Previous post was at 05:48 PM ----------

as you read above, many are having luck running it on non cm9(kangs) roms.
[Nexus S Android Development] heX79:
It's a basic port from the NS4G. Busybox'd rooted and deodexed. Doesn't mention anything about CM9. There are no fancy's on this Rom.

Would there be any issues that stand out if the Kernel wasn't going to match-up with a Rom? Or any way to create a possible issue manually? I nandroid like crazy, old backup habbits from programming.
[Nexus S Android Development] funkiefresh:
Just flashed T132 honeybadger b with CNA 1.4, everything seems to work. But should I be using any kernal ver or cm9 ver?
[Nexus S Android Development] atlantis.mu:
http://xdaforums.com/showthread.php?p=23140451#post23140451

TEUV, T11, T132 and T144 unified version possible? :)

scaling_max_freq

oc_target

oc_value
[Nexus S Android Development] simms22:
if it works, then youre using the right version. btw, there isnt an any version of honeybadger. seems like they are working on any rom so far though ;)
[Nexus S Android Development] heX79:
Most likely because it's a Honeybadger, and we all know, they don't give a sh*t! :D
[Nexus S Android Development] simms22:
if it didnt boot or if it booted and youre getting constant fc's, then there are issues. if all is running, then youre good :)

---------- Post added at 06:06 PM ---------- Previous post was at 06:06 PM ----------

so very true :D
[Nexus S Android Development] heX79:
Everything is working well on T132 HbB. Only thing that's not taking effect is my 77 init.d script for the sd card read ahead. But this IMM26 runs 512 by default, so not a big loss.
[Nexus S Android Development] FL0OD:
Deleted

°•neXus S4G•°
[Nexus S Android Development] simms22:
so it appears as there might not be any need for an "any" kernel.
[Nexus S Android Development] funkiefresh:
Same here custom voodoo sound scripts not loading at boot.
[Nexus S Android Development] FL0OD:
And that would be good?

°•neXus S4G•°
[Nexus S Android Development] Po0yAn:
I'm back to Trinity awesomeness after a long time!happy to be here again! Running T132 and so far so great for the first 25 hours and antutu bench constantly above 3200.

Though I know morfic doesn't like to rush into adding features, what are the chance of adding bigmem and touch wake to this kernel?

(Sorry if it's been asked recently)

neXus S i9020T - CM9 Kang - T132 - 100/1320 MHz
[Nexus S Android Development] :
The T11 kingfisher (sic. nice try swype) i tested scored very well on a non cm9 ROM

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] dinos3:
who is voltages in t132 ? thanks
[Nexus S Android Development] albundy2010:
You don't even need to know since you can't change them unless you build the kernel yourself.
[Nexus S Android Development] dinos3:
I just wonder
[Nexus S Android Development] morfic:
Touchwake - No.

Bigmem - Not yet, and when, each part needs testing.

LiveOC - No.

Fixed LiveOC - Although i agree that mod is better/right, i'd need to knit in presets.

Crazy named governors - No.

Custom Voltage - preferably not.

So in essence I'd need a LiveTrinity, because i am not a fan of letting people configure themselves into trouble.
[Nexus S Android Development] mixtapes08:
Just big mem for me this will be the best

Sent from my Nexus S
[Nexus S Android Development] FL0OD:
Kingfisher?

°•neXus S4G•°
[Nexus S Android Development] :
Jokester bushmaster homemaker homepage ... Nope, Swype just has no idea what a honeybadger is.

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] antrobi3:
I have no bootanimation after flashing the t132 kernel !?
[Nexus S Android Development] JakeOcn:
Unless you're using CM9 and T132 (the one containing CM9 ram disk), you won't have bootanimation
[Nexus S Android Development] Lento10:
I am using t132 honeybadger with AOKP 27 and I have a bootanimation.
[Nexus S Android Development] thedudejdog:
because honeybadger is a cm9 ramdisk kernel :rolleyes:
[Nexus S Android Development] simms22:
yup.

cm9 ramdisk doesnt mean only cm9, but amy rom that has a cm9 base.
[Nexus S Android Development] GideonX:
I'm using AOKP B27 as well, I don't see anything.

Also, AOKP isn't CM9 based, so it doesn't use CM9 ramdisk afaik. I have no idea how you are seeing the bootani.
[Nexus S Android Development] simms22:
are you sure about that? they do thank cyanogenmod and post cyanogenmods donate link.
[Nexus S Android Development] GideonX:
Maybe some of the original builds were CM based. As far as I can tell from their recent releases, it's all AOSP sprinkled with their own custom mods.
[Nexus S Android Development] simms22:
as for what im reading after googling it.. it looks like its based on aosp with a lot taken from the cyanogenmod tree.
[Nexus S Android Development] GideonX:
Sounds about right.

Which leads me to think the poster above seeing the bootani to be quite impossible.
[Nexus S Android Development] simms22:
do me a favor if you can.. try reflashing your rom and t132- honeybadgerb(t132-hbb http://goo.gl/yHaId ) and tell me if you get a boot animation. it might just have enough cm in it.
[Nexus S Android Development] GideonX:
Hang tight, be back in a few mins.
[Nexus S Android Development] simms22:
awesome! thank you :)

what im thinking is that if it has its own custom kernel, they might have grabbed some stuff from cm kernel.
[Nexus S Android Development] GideonX:
T132 honeybadger B vs C, what's the diff? I was using C just now.
[Nexus S Android Development] simms22:
c was the one that was rejected by a bunch of trinity users, because it doesnt have trinitys normal colors. but it does have the fix for the green flash when turning off the screen. the fix is what caused the loss of trinitys colors. the fix was removed until we can figure out how to fix the green flash AND keep trinitys colors just how they are.
[Nexus S Android Development] GideonX:
Gotcha.

Just finished flashing, bootani is indeed there after re-flashing. Now I'm confused, so CM9 ramdisk is pretty much identical to AOSP ramdisk?
[Nexus S Android Development] simms22:
i dont believe so. cm9 was using the same ramdisk as aosp until about a month ago. all of a sudden, the trinity test kernels stopped booting on the cm9 kangs that i use. until morfic tried the ramdisk from cm kernel. they changed it. i bet aokp grabbed that change not to long ago.
[Nexus S Android Development] GideonX:
I actually never seen the trinity bootani until now. I had no idea it was blue. I always had it in my mind that it was gray for some reason.
[Nexus S Android Development] simms22:
nice.. its your first time :D
[Nexus S Android Development] antrobi3:
Which T132 version should i flash for Bugless Beast rom ?
[Nexus S Android Development] simms22:
you can flash that t132-hbb that i just reposted, but i believe that you wont get boot animation. you can try to see if you get a boot animation, but you have to reflash your rom then the kernel. im not too familiar with that rom. if for some reason it doesnt boot, just reflash your rom. do not wipe anything.
[Nexus S Android Development] albundy2010:
I think the best way to get the trinity colors would be to use the "voodoo" adjustments in the cm9 with the default kernel to match the trinity colors.. Since I am pretty sure it doesn't work after you flash Trinity. Then take those color settings and bake them in. This is me assuming that they use the same fix for the green and its still voodoo. I'm not sure what the hell is going on with that re branding stuff.
[Nexus S Android Development] simms22:
the trinity colors IS voodoo thats baked into trinity. and you are right, cm's version of voodoo color doesnt work with trinity..
[Nexus S Android Development] albundy2010:
Yeah. Cm9 kernel has the fix in it so it should start with the same base color is my logic. Adjust on cm stock to trinity colors, toss those color setting numbers into trinity and the green flash is gone and trinity colors are back.

Would it be that simple?
[Nexus S Android Development] morfic:
Perfect theory, but I can't verify the look, only snafu.

I'll check more into this in a little bit.
[Nexus S Android Development] FL0OD:
From my experience everyone's "fix" so far isn't a fix at all. It's a, force voodoo color settings to start at zero, which does get rid of the green flash but, does not allow you to adjust the colors down. This only serves to appease some people. Not allowing those adjustments is a workaround and not a fix. I use darker colors, if I am not enjoying trinity colors, so I have just come to expect the green flash as the few milliseconds I actually see it is well worth having more vibrant colors. Nice to see people are looking for fixes but this has been a issue for a looooong time and with all these talented devs no one has ever been able to fix it. As long as we have Trinity and a couple of others with working voodoo, I don't care much that they ever fix it. Just my opinion.

°•neXus S4G•°
[Nexus S Android Development] Oodie:
One of the best kernels available :) Many Thanks .

But what bugs me is that , why don't you update to latest kernel sources ( 3.0.22 ) ? are they buggy or something ?
[Nexus S Android Development] simms22:
Benchmark and Tuning Pro app..

#1 Nexus S and #420 all devices users best results(in the midst of dual cores). T144-hbb and the latest cm9 kang(1440/1440 ondemand).
[Nexus S Android Development] :
I know T12 isn't generally available (not on the download website anyway) but I'm having reboots with it when locked at 1200MHz just fyi
[Nexus S Android Development] simms22:
1200/1200 ondemand?

thats funny considering its the only trinity kernel with a stock gpu speed. a few weeks ago i had some reboots until i removed an app that i installed not from the market. a logcat comfirmed that it was the app that made my phone reboot, not a hiccup since.
[Nexus S Android Development] :
It's not an app, I've just rebenchmarked the latest version of every available ns kernel, and T12 is the only rebooter
[Nexus S Android Development] simms22:
oh, i was just telling you my story :)

what i really wanted to know was if by locked at 1200 you meant 1200/1200, and was it with the ondemand governor?
[Nexus S Android Development] :
Yes, deadline sched., ondemand 1200/1200

I'm sure it's just a voltage thing
[Nexus S Android Development] simms22:
probably is, especially since its only t12 giving the reboots.
[Nexus S Android Development] xmatrix13:
I've had two random reboots spread out between 3-4 days of using honeybadgerb (T132) on the CyberGR-Mod Rom.

I really enjoy the speed and colours but at the same time i use my phone as my alarm so this morning due to a reboot then a boot-loop It didn't go off LOL

Should I try a fresh install? (ROM and Kernel?) Any tips on how I can make it a bit more stable? (ex. Raise voltages)

Thanks forum!
[Nexus S Android Development] brianbgrp:
IM getting 12.4-12.5 on that benchmark app with t132 at 1320/1320 on demand

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
i just had a thought.. did you clean the init.d folder if coming from another kernel?

---------- Post added at 02:28 PM ---------- Previous post was at 02:27 PM ----------

go update that benchmark app in the market.. it was calculating scores wrong :eek:
[Nexus S Android Development] :
Yep, always trash the contents of Init.d before moving onto the next thing!

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] xmatrix13:
By trash you mean deleting everything in that folder? I never did because I though that those files in init.d were part of the ROM as opposed to the kernel.
[Nexus S Android Development] mamba720027:
I also experience reboots with T12 running a clean install of cm9,actually not just T12, T11 and honeybadgers as well and this usually happens if I leave my phone streaming videos from netflix but I dident bother with that since my phone is running teuv nicely :)
[Nexus S Android Development] simms22:
they are there from the custom kernels.. but many roms have their own custom kernels. anyways, its wise to delete the contents of the folder when flashing a custom kernel because the tweaks could work against each other causing reboots or other gremlins to rear their ugly heads.

---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------

t12 is pretty much the only trinity kernel that i dont use :eek:
[Nexus S Android Development] xmatrix13:
Thanks, I will try to see if that fixes the occasional reboot!
[Nexus S Android Development] mamba720027:
T12 is the black sheep lolz ,just kidding
[Nexus S Android Development] droidance:
What files in init.d do I exactly have to delete and where could I find that directory? :o Thanks!
[Nexus S Android Development] simms22:
/system/etc/init.d

heres mine..
[Nexus S Android Development] dinos3:
i dont have 00baner.
[Nexus S Android Development] simms22:
you dont need it. its just junk in my trunk from me crackflashin' kangs. flashed a cm9 kang and t144-hbb right before that screenshot was taken.
[Nexus S Android Development] brianbgrp:
1320/1320.

I wanna try t144 again...but my phone always runs it for 20 mins or so then bootlooping out of nowhere lol

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] droidance:
So I should delete the entire directory if I were to go from Kernel A to Kernel B or only leave the three files you left in that picture?
[Nexus S Android Development] simms22:
yes. if you flash a kernel then delete the unnecessarily files, remember to reboot so that the necessary files will take affect on bootup.

---------- Post added at 08:22 PM ---------- Previous post was at 08:04 PM ----------

i say try t144-hbb again :D
[Nexus S Android Development] brianbgrp:
I need the link for HBB.....I only have

Three CM9 ramdisk version from the site

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
T144-hbb http://goo.gl/LCTvo
[Nexus S Android Development] tyea:
Is the procedure to use a Trinity kernel on a rom to: delete the init.d file of the rom, go to recovery, wipe cach and Dalvic cach, flash kernel, reboot?
[Nexus S Android Development] albundy2010:
I am running yesterday's euroskank and hbb at 1ghz. When I take pictures and use flash the phone freezes. Anybody else ever have this happen? I hardly ever use the flash on the camera so I don't know if its the rom kernel/UV etc.
[Nexus S Android Development] simms22:
if youre coming from another kernel, yea. just delete the contents of the folder. i dont wipe cache or dalvik, but thats your choice. ideally, flash your rom(and gapps) and trinity together then bootup if youre coming from a different kernel.

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

that might be the rom. i had an issue with the camera and flash yesterday too. i ended up killing the camera then restarting it. its worked since.
[Nexus S Android Development] brianbgrp:
Ok....took three tried to boot stable lol....but=

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] simms22:
lets hope that it runs stable for you this time. btw, i get between 8600-9100 with t144 on the updated benchmark with t144
[Nexus S Android Development] GideonX:
Here's what I do when flashing a kernel coming from a different kernel.

1. Kill the init.d scripts if you were on another kernel (if it had any)

2. Wipe /cache

3. Flash kernel

4. Reboot and dance

Skip step 1 if you are going trinity to another trinity version.

I'm not sure where people get the notion that wiping dalvik cache does anything for a kernel. You can skip wiping that entirely.
[Nexus S Android Development] simms22:
thats what i keep saying, people do way to much wiping.
[Nexus S Android Development] brianbgrp:
that was the best I pulled at 1440/1440. This one is weird tho...I've ran 1500+ on other kernels no problem but this one goes fine a bit then flips out. Gonna try some quadrants while I can pull 1440 lol

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] albundy2010:
Yeah it is probably rom related. Since I always use the led as a flash light.
[Nexus S Android Development] brianbgrp:
Rebooted while trying to post this screenie at 1440/1440 lol

I think t132 may have to be my cup of tea....but I c an at least get a few benches in on 144 before dying lol

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] albundy2010:
Just flashed latest official cm9 nightly and its definitely a rom thing. Took a pic with flash in cm kernel and instant crash.
[Nexus S Android Development] MurukanDHD:
Mind telling me which benchmark is the one brian and simms are posting screenshots from?
[Nexus S Android Development] mixtapes08:
T144 hb

Sent from my Nexus S
[Nexus S Android Development] droidance:
Boot animation works for me too. T144 hbb :D

Any recommendation setting for 1000/100 on demand/deadline on T144 hbb.. like io scheduler, sampling rate, and such for battery life and balance performance?? I don't play games other than to kill times occasionally like Doodle Jump..
[Nexus S Android Development] MurukanDHD:
Thanks mate but I need the name of the benchmark app, not the kernel.
[Nexus S Android Development] :
Isn't that the new quadrant advanced?

kernels ; battery ; ROM ; gov/sched

Now with summaries in the first posts. Convenient for XDA app users!
[Nexus S Android Development] thedudejdog:
Quadrant
[Nexus S Android Development] brianbgrp:
My first post was a new benchmark tool called benchmark and tuning trial. The second post was new quadrant

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] brianbgrp:
I use Simms settings of on demand deadline 15000 sampling 98% threshold.

Sent from my Nexus S 4G using Xparent Red Tapatalk
[Nexus S Android Development] albedebbi:
Test rom from @gearheadcustoms + trinity t144hbb

:D
[Nexus S Android Development] simms22:
niiice.. :)
[Nexus S Android Development] albedebbi:
The strange thing is that the quadrant score is less than 2000 :confused: with same setting
[Nexus S Android Development] simms22:
weird :eek: