yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kong:
Those mods are not implemented in Trinity.
[Nexus S Android Development] PIKO1982:
:(

Ok

This is a "price" to pay
[Nexus S Android Development] Accidd:
To make BLD and BLN work with Trinity App i set it in NSTools and uninstalled. Then installed TrinityApp and it still works because it was wriiten in init.d I guess.
[Nexus S Android Development] morfic:
on todo list for my app.
[Nexus S Android Development] G-DannY:
Last "current" T11 + Androxide rom: cannot set more than +0 analog gain on voodoo control plus
[Nexus S Android Development] rickbosch:
Back on Trinity, I missed the colours and battery life of TEUV too much to resist. Running with latest BuglessBeast nightly. Just because I prefer the gradient background which RasCream doesn't have :(

I posted about the screen cutting up a bit when exiting apps with white backgrounds and the green tinge when unlocking the screen a while back, happy to say that with 56mhz TEUV the cutting transitions are gone. However, the green tinge is still there on auto-brightness. I could fix it by running trinity on a rom with an adjustable backlight brightness setting.

If you raise it slighty (12 worked perfectly on Apex) then the tinge disappears. I mostly use manual brightness, so it's not a major issue for me, but I thought the dedicated trinity team would like to know.

Cheers guys

R
[Nexus S Android Development] simms22:
i smell some even higher bigmem trinity kernels running around.. :eek:
[Nexus S Android Development] skinner12:
Welcome back, good choice :thumbup:

Nocerino's Rulez with RAScarlo's ROM features TriNitY ;-)
[Nexus S Android Development] kong:
Refreshing Testing tab on DerKernel site.... :D
[Nexus S Android Development] karx23:
Love the T11's performance and battery. It's my favorite trinity.

The sad thing is that I have reboots sometimes.

How do i get a logcat with aLogcat? Everytime it reboots it starts all over and I can't see the error that caused the reboot.
[Nexus S Android Development] albundy2010:
Its because your phone can't handle the undervolt.
[Nexus S Android Development] sperelli:
anybody has clues about IMM76I?
[Nexus S Android Development] DaXmax:
What i know its just the kernel based changed for GNex...
[Nexus S Android Development] att1cus:
Are you talking about the sound settings? I don't have that issue on the 50hz T11, fyi. I'm on aokp though.
[Nexus S Android Development] simms22:
heres a t132 teaser with more ram, higher bigmem, 50hz.. http://goo.gl/RPfSk

---------- Post added at 04:18 PM ---------- Previous post was at 04:04 PM ----------

if you already downloaded it, download it again. i linked the wrong kernel first :eek:
[Nexus S Android Development] dinos3:
This is only cm9 based ,as was recently said morfic..?
[Nexus S Android Development] simms22:
no. its an anykernel. for any rom :)
[Nexus S Android Development] dinos3:
Anybody test video/cam/other on t132 ?
[Nexus S Android Development] Randomwalker:
*ROFL* Was just about to ask. Flashing the new on now :-)...
[Nexus S Android Development] att1cus:
'Other' is BROKEN!!!

Just kidding, no issues here with cam or youtube or anything else for that matter.
[Nexus S Android Development] simms22:
damn.. i hate when the other breaks. i guess im stuck with this instead of the other ;)
[Nexus S Android Development] att1cus:
I hear that is an option too. Fo' sho.
[Nexus S Android Development] Accidd:
There's something wrong with this new kernel... After I installed there's no lag in my MIUI V4! I ;)

It's so smooth in launcher and it's only 50hz ;)

Oh and 401 mb of ram ;)

Wysyłane z mojego Nexus S za pomocą Tapatalk 2
[Nexus S Android Development] legolas93:
Flashed now.. Fantastic! :D..All is smooth like butter..Tomorrow i will test it some more..Now i go to bed!..Thanks Morfic (And Simms :D) We really apprecciate your work :)
[Nexus S Android Development] albundy2010:
Not so sure about this 50hz. It produces higher than 50fps (56) in antutu and quadrants planet test
[Nexus S Android Development] dinos3:
Maybe soon higher bigmem with 65 fps on t132 ?
[Nexus S Android Development] simms22:
its the good kind of broken :)

---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------

oops..

it could be 56hz, just named wrong. we tested both 50hz and 56hz late last night :eek:
[Nexus S Android Development] sdhanjal15:
Kind of wish this had BLX and smartassv2 governor. Then I would behappy

Sent from my Nexus S
[Nexus S Android Development] tmello56:
Running teuv with the latest euroskank, but I'm experiencing broken wifi. Any suggestions?

Sorry if I missed a post but I've been trying to read up and answer my own question, but no luck so far.
[Nexus S Android Development] simms22:
try this teuv, its the latest(for now) http://goo.gl/bQRqz

you might have picked up an older teuv.
[Nexus S Android Development] tmello56:
Thanks man. That one works.
[Nexus S Android Development] simms22:
i thought that it might be the issue :)
[Nexus S Android Development] sdhanjal15:
Blx?

Sent from my Nexus S
[Nexus S Android Development] morfic:
Blx == No, sorry.
[Nexus S Android Development] Paragon_X:
Hi I'm about to flash this kernel once my phone charges however a few questions. If I read correct there is no deep idle? Well my concern with that is I play music a lot and want to know will this kernel take that into account and help save battery. I prefer to do 200 min freq and max 800 or 880 I guess from what this says... should everything be ok?
[Nexus S Android Development] sdhanjal15:
Oh poo. Just wondering....why?

Sent from my Nexus S
[Nexus S Android Development] albundy2010:
Because it is just cosmetic and there is no need for it.
[Nexus S Android Development] sdhanjal15:
Meh...I guess that's true.

Sent from my Nexus S
[Nexus S Android Development] simms22:
your phone will be ok :)
[Nexus S Android Development] morfic:
Blx is not the fix of showing 100% when full.

Blx let's you set the phone so it stops charging even before it reaches 96%.

You know, so you can enjoy less idle and screen-on time.

That's all it's good for.

Sent from my GSM Nexus Prime.
[Nexus S Android Development] Dorilife:
Sorry but must say ..

Faaack!!!! The test T32 is hella f*cking smooth..seriously though it runs so smooth.:D
[Nexus S Android Development] Bamdroid:
I can't get the test T132 to download. Whiskey tango foxtrot..:banghead:

Edit* would it be in the toolbox?
[Nexus S Android Development] thegtfusion:
Navo alphabet :D
[Nexus S Android Development] Bamdroid:
:thumbup::thumbup:
[Nexus S Android Development] thegtfusion:
Yankee Echo Sierra :). I downloaded it fine....
[Nexus S Android Development] morfic:
off of www.derkernel.com it works fine, if you tried simms22's old link, it's moldy.

http://goo.gl/q3CnT is what the download button will give you
[Nexus S Android Development] albundy2010:
Doesn't blx do both? Stop the charging at 96 ( or whatever else you set it at) and report that charged state as 100 percent?

Morfic I wish you still had a ns just so you can see this latest test kernel run first hand. This thing is just super smooth now. Not even overclocked.

What ever combo of mods/locations of taking ram to achieve this bigger mem brings amazing results. Feels like how a PC behaved when lowering memory timings and getting a rapter hdd years ago
[Nexus S Android Development] simms22:
i believe that he sliced some off the gpu this time..
[Nexus S Android Development] sdhanjal15:
I wish it still had blx

Sent from my Nexus S
[Nexus S Android Development] Bamdroid:
Tango hotel xray Morfic :D

;)
[Nexus S Android Development] morfic:
I'd say i'll keep 56Hz as defacto standard until the panel frequency can be changed at run time down the road,,,,however, nothing is going to happen over night.

so much to add to both NS and NP kernel and the app, things will seem like they trickle to the impatient when it actually will be Trinity's fastest evolution.

about blx, it's its function as i understood it when it came out, if it since has evolved, i didn't hear about that.

I ever really had the 100% fix in GB, as in my mind, the battery is 100% full when the battery reaches the level at which the manufacturer determined is the save level, that *IS* full.

To pass it off as "only cosmetic, not a fix" well there is nothing to fix but to say "full == 100%" and make it show that as such.
[Nexus S Android Development] morfic:
November Papa
[Nexus S Android Development] morfic:
No, that was what we tried between the first xbigmem build and the fullset, i ran out of sleep time and we will reattempt after i manage to get a ton of other things done that can be easily completed, instead of letting the TODO pile up while chasing the holy grail that is not confirmed can be done (although it is logic that it should be possible)

anyone on cm9 kernel (like next kang flash) what is the exact number in :

cat /proc/meminfo

the first number i want
[Nexus S Android Development] att1cus:
so any test kernels on derkernel with '201212302' in the filenames are the new ones? the descriptions still have april 21st listed as the build dates.
[Nexus S Android Development] albundy2010:
Those are the latest full batch with all the normal kernels and 56hz,50hz versions as well

simms posted a new test kernel today. This is the one that most of us are currently yapping about.
[Nexus S Android Development] att1cus:
I don't think so--I just loaded one and it has may 2nd as the build date in 'about phone'. I already dl'd the one simms posted. That one locked and rebooted my phone when I selected 800 as max tho.
[Nexus S Android Development] albundy2010:
Yeah you're right. They are up there now. The build date is wrong on the site as you stated
[Nexus S Android Development] att1cus:
thanks for the confirmation. i was confused.
[Nexus S Android Development] morfic:
the crespo php fails to update the timestamp, works on app it would seem, works on ics-tuna.php

ignore the script glitch 201212302 is a date stamp too, and that one is absolute
[Nexus S Android Development] afzalarsalan:
Wouldn't reducing gpu memory decrease game performance. I mean there must be a reason that so much memory is assigned to the gpu.
[Nexus S Android Development] morfic:
there is always extra, be it 8MB or 32MB, there is always extra to be had.
[Nexus S Android Development] :
Nice, so how much ram does this version have?
[Nexus S Android Development] morfic:
MemTotal: 411244 kB
[Nexus S Android Development] simms22:
401mb ram.
[Nexus S Android Development] morfic:
What I'm too tired to finish tonight.

Yes I test build on NP even if they are NS only features.

Sent from my GSM Nexus Prime.
[Nexus S Android Development] Dorilife:
Wooaaa I thought it would take more time, thanks for putting time into this.
[Nexus S Android Development] morfic:
I'm behind, wanted to have BLN/BLD in much sooner, but when everyone on NP worried about CPU temp, i figured seeing it easily is useful and i added that. (Updates every 5 secs and does not rape battery, how about that?

NS doesn't seem to have a CPU temp sensor, so all i'll be able to offer on NS later is a battery temp widget.

The fast charge toggle plug check drove me nuts for a little while but it's much easier code now than i initially had planned, so that's exciting (Sorry, *to me*) :)

(trying to say many little things popping up in front of BLN/BLD

But it's my next project, aside from making sure we have 411000KB on Trinity NS too.

If i have my way, NS app version should be sporting the missing tab too.
[Nexus S Android Development] tycruickshank:
666 downloads
[Nexus S Android Development] rickbosch:
I may have been #666. Winning.

Sent from my Nexus S
[Nexus S Android Development] rascarlo:
Hey Simms, I've got your number!

And thanks to all you crespo users.

Been a busy week and I miss building Android. Really want to push a new build asap.

Thanks for the love
[Nexus S Android Development] tycruickshank:
Thanks so much for all the work!! Is there any chance you could include the framework-res.apk bluetoothquickswitch<false> in the next build? I've spent a couple hours trying to decompile and recompile it with apktool, but i'm having a hard time with recompiling.
[Nexus S Android Development] iamxeph:
I just flashed the lastest teuv with 400± bigmem, and i noticed init.d scripts are not working.

I'm using AOKP milestone 5 and init.d scripts are working with previous version of teuv
[Nexus S Android Development] sperelli:
hi there rascarlo, can u please explain how to make flashable out of your bootanimation zips?
[Nexus S Android Development] morfic:
Check:

run-parts -t /etc/init.d/

Sent from my GSM Nexus Prime.
[Nexus S Android Development] iamxeph:
a/local/bin:$PATH <

app_60@android:/ $ run-parts -t /etc/init.d/

/etc/init.d/00check

/etc/init.d/01zipalign

/etc/init.d/02sysctl

/etc/init.d/03firstboot

/etc/init.d/05freemem

/etc/init.d/06removecache

/etc/init.d/07fixperms

/etc/init.d/09cron

/etc/init.d/10sdboost

/etc/init.d/97nstools

/etc/init.d/98tweak

/etc/init.d/98tweaks

/etc/init.d/99complete

app_60@android:/ $

Results are same. I noticed init.d scripts are not working since i put 97nstools file to activate bln/bld/cpuclock and removed nstools app.
[Nexus S Android Development] alen1901:
407660 kb. On cm9 v7, stock kernel.

Sent from SpeedMachine i9023
[Nexus S Android Development] WarByte:
Check your rom settings. Milestone 5 here. No issues with init.d and I use no apps, only scripts to turn things on and off. Milestone 5 has a way to disable scripts on boot with rom control, would be worth checking :-)
[Nexus S Android Development] dinos3:
Morfic do you have build 400+ mb kernel with 65 fps ?
[Nexus S Android Development] deani77:
Maybe after all every newly add modification working as it should.

Sent from CM9+T132 Kernel on NXS
[Nexus S Android Development] iamxeph:
Oh, I get it to work. Thank you.

@morfic: sry for confusing you :eek:
[Nexus S Android Development] Randomwalker:
Bigmem 1320 stable and very smooth on CM9v7 for me.

No reboots so far, even when streaming via A2DP. That's where I usually get thrown off by T144.
[Nexus S Android Development] Dorilife:
Yeah same here but on AOKP M5, got 13 1/2 hours with 4 hours 20mins of on-screen time..with 20% left..
[Nexus S Android Development] morfic:
Nah, good for me to know.

Since I don't supply my own ram disk to avoid this very scenario, I'm not too worried hearing init.d issues.

But now I can at least suggest something to check.

Sent from my GSM Nexus Prime.
[Nexus S Android Development] morfic:
As everyone screamed in unison about how smooth new kernels are, which are 56Hz, I was gonna ride that a while.

Daily use, 56Hz is perfect, gives deeper color too.

So let everyone get used to this batch, then we get good comparison feedback on next 65fps kernels

Sent from my GSM Nexus Prime.
[Nexus S Android Development] Ritwik7:
I'm not getting anything like that on RasCream with TEUV 50Hz. Right now: 9 1/2 hours with 1 1/2 hours voice call and 1 hour on-screen...37% left. Is it the ROM or kernel or should I wipe battery stats?

Must mention that I'm on 3G though and the signal does get very weak very often.

@ morfic - Does the 56 Hz kernel have deeper colours than the 50Hz ones. Which do you personally recommend for good performance and battery life with latest RasCream?
[Nexus S Android Development] rickbosch:
I'm with Morfic on that, the 56mhz perform better and no cutting up of the screen. Latest t11 with latest RasCream is awesome.

Sent from my Nexus S
[Nexus S Android Development] kong:
I still have the feeling that 201211200 builds are smoother than the recent two batches. Just wondering if they were also 56Hz? :confused:
[Nexus S Android Development] dinos3:
Is it possible to this kernel show cpu temp ?

Ss from me

App name = tempmonitor, downloaded from store
[Nexus S Android Development] Bamdroid:
I dunno about everyone else but the test T132 clocked at 1.3 has been AWESOME for me. Getting decent battery as well as stable/fast.

..Can I has more boom?

私のネクサスSから送られてくる
[Nexus S Android Development] stuff:
I kept getting reboots on 1320mhz. I'm not sure my phone can handle it at the current voltages.

I'll be trying the T12 or T11 in a few. Is there really a difference in 200mhz GPU and 220mhz GPU?
[Nexus S Android Development] Dorilife:
Morfic said that it seemed like the NS doesn't have a CPU temp sensor...
[Nexus S Android Development] simms22:
no, not possible for the nexus s to show cpu temp. its lacking a cpu temperature sensor.
[Nexus S Android Development] simms22:
its not just the extra .04, its the oc'd bus too.

i have the sampling rate set at 15000 and the up threshold at 98 in advanced setting in setcpu. no profiles whats-so-ever.
[Nexus S Android Development] lichti1901:
Im on last tuv11, 1 day 20 hours and 33% left with normal usage! Tuv11 is awsome! Love it!
[Nexus S Android Development] window7:
Lol. I simply like the T13 kernel. It just that nice :) haha. Having 1 day battery life with 2 hours music, 100 text, 1 hour of calls, 1 hours of gaming, msn messenger and Skype chat for 1 hour and all the time data connected. Wow. Simple awesome!
[Nexus S Android Development] simms22:
UPDATED! Trinity12-Any-2.3.5 kernel for the Nexus S http://goo.gl/jeoyz

Goes great with a side of bacon :)

Thanks morfic
[Nexus S Android Development] Kurupt1:
Thank you sir

Edit does thus include morfic's ns4g fixes?
[Nexus S Android Development] coloxim:
it is no possible...
[Nexus S Android Development] HareyCarey:
Is that on one of the lower clocks or 1.44ghz clock? Think that will work for me on 1.44ghz? I don't NEED 1.44ghz...but I want it:) Other than having to reboot in airplane mode to get my service back everytime I power off, I am loving this kernel.
[Nexus S Android Development] RevengeITA:
which ROM do you use?

I have TUV11 on stock 2.3.4 but I don't see any improvement..
[Nexus S Android Development] HareyCarey:
Running fine in Oxygebg5
[Nexus S Android Development] Po0yAn:
i started the kernel trying process again,since the netarchy kernel become so glitchy lately(although it still has the best benchmarks specially in graphics). i tried the Matr1x v4,5 for 2 days on CM7 nightly #144 and 146, it was a very good.

then i decided to try the Trinitys, starting TUV11.

i was using it for a day and it had the best combination of battery life and performance in any kernel on any phone i had, so i decided to use it for full time, but last night something bad happened! i charged the phone and pulled the charger to test the battery use during night,and went to sleep. after 8 hours when i hit the wake button , the display didnt turn on, but the soft buttons were light up. so i pulled the battery and restart the phone , but it didnt pass the red trinity boot up screen. i reinstalled the kernek through recovery, installed matr1x kernel again, and reinstalled the #146 build, and restored my backup from 3 dayse ago, and the phone couldnt get to bootanimation, and was stocked on google boot screen. a mini brick if u say. i find out the battery is so low on charge that the phone cant initiate the booting up process.

anyway i used my first backup from 2.3.1 and the phone booted up and i fully charged,then restored my last nand backup (Matr1x kernel) and gladly it booted up.

i want to know does anyone had the same problem or is it just my phone's cpu that cant catch up with morfic's undervolted voltages?I really like this kernel and IMO is the best kernel for NS, but i really cant use it with the problem mentioned above
[Nexus S Android Development] simms22:
yes it does include them
[Nexus S Android Development] simms22:
its on the lower clock speeds too
[Nexus S Android Development] simms22:
what rom are you using?
[Nexus S Android Development] HareyCarey:
I'm on Oxygen, will this affect those settings? I love this rom, but I haven't had any other good suggestions for roms for the 4g. I tried those settings earlier and it seemed to eat more battery. My quadrant scores were awesome, though lol.
[Nexus S Android Development] Po0yAn:
Nightlies. when this problem happened i was on 146.

now im on #147, and again trying the TUV11!:D

had one reboot about 10 mins ago. still testing to see what will happen
[Nexus S Android Development] simms22:
try the kang i just posted in the nightly thread. reboots are probably a nightlies issue.
[Nexus S Android Development] HareyCarey:
Any suggestions of 4g roms that work well with these kernels? I want to wait and see the T13 update and run it for a while. I really like T13
[Nexus S Android Development] simms22:
i dont have a 4G so i cant really suggest one. does oxygen have a 4G rom?
[Nexus S Android Development] HareyCarey:
Yeah, I'm using it. I see cool stuff for the NS but the 4g is having yo catch up on dev. I may try MIUI later, who knows? I haven't used CM7 yet either. I like the stock launcher,honestly
[Nexus S Android Development] IIIV:
What governor is everyone using? I just had a reboot while multi-tasking (reddit + browser + Quickpic). I'm using the latest T11 set (using NSTools) at ondemand and 400-1096 MHz.
[Nexus S Android Development] Maximilian Mary:
Whatever you changed from 113 to 123, please think twice before changing it again. This is the smoothest ICS build yet.

Later I will make it crack under the sheer strain of my awesomeness, but for now, it feels like ICS has finally arrived.
[Nexus S Android Development] stuff:
I am getting reboots with the exact same setup. I think it's the 220mhz GPU bus. I don't think mine (possible yours as well) can fully handle it.

Also I had force GPU rendering enabled. I'm going to disable it for now and see if it helps with the reboots at all
[Nexus S Android Development] DaXmax:
I have discovered something which you requested last few days ago, and its ready, only... Waiting for the time that you pushed in. ;)
[Nexus S Android Development] IIIV:
I've always had my GPU Rendering disabled. I'm thinking it could be CM9's Performance settings (memory, surface dithering, etc.).

Edit: I just enabled KSM, which CM9 and also this kernel supports. We'll see if this helps.
[Nexus S Android Development] stuff:
I'm on MIUI right now though
[Nexus S Android Development] Paragon_X:
Hi guys I recently did a fresh install of AOKP Milestone 5 and added this kernel the 1100 max and 200 min setup. My question is my charging seems to take forever... when it hit 100% on a full charge I did a battery wipe of stats through CWR and then let it sit like normal over night and took it to work where it died to about 15% and am now charging but it's been struggling to go anywhere. Has anyone else experienced this?
[Nexus S Android Development] DaXmax:
With AOKP•TW + BM Tweaks + BIGMEM + TRT (which i just bought few mins ago) + T11-0105 build + My Strawberry Sandwich = Goodies to heaven. Thanks, i love the smoothie now. But i hope when playing Fifa 12 later doesnt give lags as its on 220mhz GPU. ;)
[Nexus S Android Development] tycruickshank:
In regards to rascream I think I've just found out that you have to hold the back button for a fairly long time and then the app will be killed. Sorry if everybody knows this already but I thought I'd share just in case. There doesn't seem to be any haptic feedback or any message but the app does quit
[Nexus S Android Development] stuff:
I constantly get reboots with GPU at 220mhz. Not constantly, but it's consistent and I can get 4-5 minutes of doing whatever before the phone locks up and reboots. I switched over to the regular 200mhz 56hz 1.2ghz kernel, and no problems for about an hour.

My phone might not like that GPU oc
[Nexus S Android Development] DaXmax:
I think Galaxy S3 sucks even more. Becuz Galaxy Nexus has the same features.... Only the **** camera + quad core...
[Nexus S Android Development] rickbosch:
It must be the overclocked GPU, yes. Been running latest rascream with the 56mhz t11 for two days, no problems at all. This is today, with 2hrs screen time.

Sent from my Nexus S
[Nexus S Android Development] apatal:
Nope. Doesn't work for me, and in other ROMs where that mod is working, we at least get this message in the screen after holding the back button:

Application killed.

Nevermind, it's still an awesome ROM, and am looking forward to next iteration. :)

Sent from my Nexus S