yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Zacisblack:
Increasing the GPU clock speed past 307Mhz does nothing but waste battery. I was getting 3299 in Quadrant on Gummy 0.7.0 and Franco kernel 15, and that's clocked at 307 for the GPU. I'm now getting 3000 tops in quadrant and the linpack score is lower too. Both were at 1350Mhz. A Google engineer posted in Franco's thread saying that the bus speeds aren't fast enough to support anything faster than 307Mhz on the GPU, so doing so just causes excessive battery drain. In the 5 minutes I've spent on this kernel I've watched my battery go down 4% just flipping through menus.
[Samsung Galaxy Nexus] morfic:
At 1500 for reference. L3 was actually stock at the time, but I don't expect 3D to get huge enough a boost for this to make too big a dent on the avg. Score.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] morfic:
You are doing it wrong.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] Zacisblack:
Quote from Colin Cross(A Google Engineer):

'"Most GPU workloads on 4460 with a 720p screen are limited by the

memory bandwidth, not the GPU computation ability (which is fairly

linear with clock speed). With the GPU at 307 MHz, the core is at

OPP100, the and the memory bus is at full speed. At 384 MHz, the core

is at OPP_100_OV, which raises the core voltage (not counting

SmartReflex) from 1.127V to 1.25V, causing a huge increase in power

usage. Without the GPU, the core is almost always running at OPP100

when under load, because CPU OPP100 (700 MHz) requires core OPP100.

That means scaling the GPU from 150MHz to 307MHz costs very little in

terms of power. Nothing else in the chip requires core OPP100_OV, so

scaling the GPU to 384MHz is a pure power hit for very little (or no)

performance gain."
[Samsung Galaxy Nexus] nklenchik:
Is this a new experimental of yours?

PS: Are we gonna see some UV under 350 in the works? :P
[Samsung Galaxy Nexus] morfic:
I know what you quoted.

You act as if the gpu didn't scale. It won't be at 512, 384 or even 307 while you read a forum.

He is right and you are still wrong if you don't take the sum of changes into consideration.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] morfic:
Yes.

UC? Maybe.

Gpu UVUC for lowest clock? Maybe.

Anything tied to core I can't drop endlessly.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] nklenchik:
Yeah I meant UC lol I've tried Franco's 280 before and that didn't go far with my phone at all
[Samsung Galaxy Nexus] parkson:
Something about this kernel breaks my doubletwist media player.

If I come from a fresh rom install, doubletwist recognizes and reads my mp3 files just fine. It works with every kernel I've tried, other than this kernel and franco.kernel. After I install this kernel, the mp3s show up in doubletwist, but as soon as I hit play, I get an error along the lines of 'media player not recognizing this type of file', then it keeps scanning for the next file repeatedly, skipping past all music tracks... (its only mp3s)

I've tried installing a different kernel but doubletwist is still broken. Only way to get doubletwist working properly is to nandroid a backup made prior to installing Trinity. What gives?

*edit* have had this problem on the roms CND (1.1.4 and 1.2.0), Redemption, aokp m2 and now m3.

## Mp3s play fine on Google music and also CM music.

##
[Samsung Galaxy Nexus] nklenchik:
There's your problem...you're using Doubletwist :P Gotta hop on that PowerAMP boat
[Samsung Galaxy Nexus] parkson:
Lol I know. If it weren't for the fact I paid for airsync, I would have moved on long ago...
[Samsung Galaxy Nexus] simms22:
go to manage apps, find doubletwist and clear its data,. if that doesnt work, run a fix_permissions.
[Samsung Galaxy Nexus] morfic:
Open your .zip you flashed.

Does it contain system/bin/sdcard

If yes get the one from your rom's zip and put it back into /system/bin/

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] gaetawoo:
Yea, i'd like to know what this is all about also... please?:D
[Samsung Galaxy Nexus] morfic:
Avoids accidental software rendering and causes everything to use hardware rendering.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] belair56:
My line is

0 1 POWERVR_5GX540_120

When I modify it to only POWERVR

it will not boot. What am I doing wrong? Thanks...
[Samsung Galaxy Nexus] :
your line is fine, where did you read to modify it to only POWERVR??? o.O
[Samsung Galaxy Nexus] belair56:
Well.... I guess I misread mtw4991's instructions. As ONLY leave powervr in the file. I see my mistake now.

I'm feeling silly now. But I guess it's good to know that kangs have the file right. I just delete the SO. file.
[Samsung Galaxy Nexus] mtw4991:
Sorry, butha, I didn't remember the rest of the file name, that's why I put .xxx there. Should've been more clear...#mybad
[Samsung Galaxy Nexus] gaetawoo:
doesn't selecting Force GPU rendering in Dev Settings do that? or is it different?
[Samsung Galaxy Nexus] mrkmrk:
I feel like apps can probably override that if they specifically *request* software rendering. The option, as I understand it, is to force GPU rendering when it's just not been enabled, not to override a conscious choice by a developer.
[Samsung Galaxy Nexus] jpmcnown:
I'm diggin the new Trinity boot animation......oh yeah, and the awesomeness of the kernel!
[Samsung Galaxy Nexus] Esteway.619:
Where's the boot animation cuz I don't see it.
[Samsung Galaxy Nexus] morfic:
In some newer test kernels.

The 1.38 iirc have a prototype bootanimation, the 1.536GHz have the final.

It's worth clearing dalvik, just to be able to enjoy it longer :P

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] aznxk3vi17:
I've been loving your kernels and work. Just out of curiosity though, are your kernels more performance-oriented, as opposed to some of those that claim leaner or battery-saving kernels (not naming any names :P)? I've been mostly sticking to franco/Lean, and the battery life+performance on those tend to be pretty similar.
[Samsung Galaxy Nexus] morfic:
I tend to look at cutting the fat, adding as little as i can and checking how much reserves were engineered into the SoC/phone. (Me: "less is more" ... i guess it's leaner than lean, cause lean has tons of stuff added, and i tend to try to avoid adding stuff as much as i can, try because it's hard to get around voodoo sound, plus i do tend to like to tune my amoled using a hardcoded version of voodoo color v1 hack)

What are my kernels, hm, let's use the Nexus S as example, there is everything from underclocked 880MHz to 1.44GHz to fun always experimental Thermite versions of the same kernel.

Take the G2x, where the T15 at 1.56GHz top outlasts my nexus s battery at the same conditions (and i mostly took 880MHz or 1.1GHz kernels to work...not that 1.44GHz never made it to work, i distrust apps and a bad app clocking up my 1.44GHz phone is obviously worse than when it clocks it up to 880MHz), there is also a 1.1GHz pre-UV kernel on G2x, squeezed so low, you won't find much room for "personal UV". "But that doesn't make sense, you do take your 1.56GHz g2x to work!" Good catch, it's because i forced myself to take the G2x like this more for testing, but Nexus S was the daily driver i really took to work more often than the Nexus S, that's the difference.

So what are my kernels? Everything.

What can you expect? Nothing. (Never expect, it's always a let down)

What will i try? Everything it lets me get away with.

What's possible? I'll tell you when i know.

I'm more an Analyzer and Thinker than a Patcher.

I don't concern myself with fancy OPs, i have limited time, keeping a bloated OP, listing things changed in a "git pull" from Samsung/Google to make it look like more than it is, that's not me.

What am I or the kernels compared to the rest, I think you got an idea, about Francisco, we are too similar to really say much, i think he tends to write rambly posts like this less often, that's maybe about it :P
[Samsung Galaxy Nexus] fcisco13:
Do they turn off one core when screen off?

G Nexus
[Samsung Galaxy Nexus] morfic:
Who is "they"?
[Samsung Galaxy Nexus] fcisco13:
Lol governors. Btw loyal user on g2x, thanx.

G Nexus
[Samsung Galaxy Nexus] morfic:
hotplug would do it but it was never stable, so if it seems to be too much work (to fix it), i'll force one off and turn it back on x time after screen on.

i like hotplug governor in theory since it is ondemand with extra focus on hotplugging cpus and also it is designed around steps not percentages for scaling which on paper sounds good.

You can check out Francisco's kernel, he is forcing off CPU1 right now

And fyi, your username always makes me think of Francisco (Franco)
[Samsung Galaxy Nexus] fcisco13:
Thanx and yes name is Francisco.

G Nexus
[Samsung Galaxy Nexus] boynamedstacy:
Great work on these Kernels! I've been running/loving the 512 for a few weeks now. Question. Will the 512 experimental build work with the new 4.0.4 AOSP roms?
[Samsung Galaxy Nexus] 9wire:
Wanted to try the 1.5 but I get stuck at the Google screen and it won't boot. 3.0.8 np runs very well though.
[Samsung Galaxy Nexus] mzimand:
Is the 1.5 set to boot at 1.5?
[Samsung Galaxy Nexus] jbzcar:
Same for me. Could we possibly get a version with more default voltage that might boot better?
[Samsung Galaxy Nexus] morfic:
Boots 1.2

Some phones that have issues ocing dislike booting with the OCed interconnect too.

Those don't get past the google logo.

After finishing up my furnace I can link you some higher clocked kernels that do not OC the interconnect.

Meanwhile make sure your nandroids are current.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] 9wire:
Thank you, sir.
[Samsung Galaxy Nexus] dotson817:
Damn this new experimental one flies lol
[Samsung Galaxy Nexus] zerocool79346:
Getting ridiculous screen on with this kernel, thanks man its much appreciated.
[Samsung Galaxy Nexus] mike216:
What version? Thanks
[Samsung Galaxy Nexus] morfic:
It would be awesome if you could include WHICH "this", it helps me out a lot to know which kernel people have what result with.

Thanks.
[Samsung Galaxy Nexus] morfic:
I could build one without smartreflex, so instead of raising the nominal to crazy levels and hoping it helps you would know exactly what voltage you run, no calibration with added margin.

For a consumer "use and don't think about it" phone the smart reflex process is ingenious, so ingenious that 10 phones with the same image flashed with get 10 different run times. Due to 10 different sets of voltages.

OCing though to me requires control, control you will not have if a calibration process lowers the voltages on you.

I suppose i could release one such 1536 tonight or tomorrow, it would be nominal on all voltages, i would prefer to limit it to MPU and CORE, but that won't happen tonight.

If there is interest i could build that.

Due to the amount of testing everyone does trying to reach 1536 i am tempted to readd normal fsync, lowering IO scores and possibly increasing battery usage slightly, but hopefully keeping some of you from restoring from nandroids all too often.

Not sure yet, thinking about it.
[Samsung Galaxy Nexus] dotson817:
Lol true sorry I meant TNP1536-ANY-MVM550 flies
[Samsung Galaxy Nexus] bluemoon1221:
Can you also include what rom you're using? I want to try it out. Thanks

Also, if you don't mind, things like governor and CPU settings please... I don't need voltages since I don't mess with them

Sorry for asking a lot.... and thanks
[Samsung Galaxy Nexus] jbzcar:
You know I'm game to try anything. :)

I'd rather try one with nominal voltages before adding fsync back in. I am comfortable with the adjust-test-wipe-restore-startoveragain process involved in determining what voltages my SoC likes. Nandroids don't scare me, lol. I make them so often in testing different things that I probably have 100+ gigs worth of them backed up on my hard drive from my various Android devices. :D
[Samsung Galaxy Nexus] dotson817:
I was on beta 3 liquid which has been a huge favorite of mine along with Trinity's kernels. All personal opinion but that combo after testing so many different ones has been awesome. Now that combo flew but the 512b kernel actually was extremely smooth and I noticed great battery with. Conservative governor always for me no UV

Testing android the new 4.04 out now but that was what I was using.
[Samsung Galaxy Nexus] dotson817:
Just confirmed that this boots on modacos new 4.04 rom and dam does it make it so much smoother :)
[Samsung Galaxy Nexus] zerocool79346:
Sorry about that. I'm running the 512RD first release.
[Samsung Galaxy Nexus] morfic:
Awe gee, built you a 1536 with nominal voltages, no smartreflex and it's only for aosp, not cm, hope you are not a CMer....

http://goo.gl/rY6mg

also has a ntfs module for more OTG flexibility
[Samsung Galaxy Nexus] jbzcar:
Thanks, flashing as soon as I hit submit!
[Samsung Galaxy Nexus] 9wire:
Trying this now, wouldn't run 1.56 until I upped the voyage to 14mv. Since lowered it to 1375, running smooth.
[Samsung Galaxy Nexus] morfic:
Jbzcar how did that work out for you?

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] mrfuzzie23:
morific,

were you ever able to fix the issue with BT not working with the kernels that run at 1536 with the interconnect?
[Samsung Galaxy Nexus] MasterRy88:
Been running this kernel for a few hours now with no issues. Will report back after a full days use
[Samsung Galaxy Nexus] mrkmrk:
New 1536 experience:

Installed (again, on winner00's latest cm9 build) without issue. Didn't change voltages from stock, raised clock to 1190/1190, then raised to 1536/1190. Instant reboot. Raised voltage for 1536 to 1350mv, repeated the process and it worked great. Took some nice benchmarks, enjoyed general phone use.

Wake up this morning an hour late--alarm hadn't gone off, got the message that "ISM Service" (I think? I may have that acronym wrong) had stopped working. Caught a bus, used phone normally. Phone rebooted, and when it was boot back into android, any attempt to open any application would just inform me that the application had stopped working. Needing a phone for work/school, I nandroid'd back.

Maybe my phone just isn't cut out for 1536 :(. But it runs 1.38 just fine, and used to run a 1.4 oc nicely, too...
[Samsung Galaxy Nexus] MasterRy88:
Just out of curiosity why do you leave your min freq. so high?
[Samsung Galaxy Nexus] mrkmrk:
Oh! I had just read on either this thread or the one in the GSM forum that that had worked for other people who were having trouble getting 1536 to work. Once it was working, I lowered the min back down to 345.
[Samsung Galaxy Nexus] MasterRy88:
ahhh ok I was gonna say that a pretty crazy min freq. I know that Franco swears by keeping the min at 700 instead of 350 and ive tried both numerous times and couldnt really see much of a difference. maybe if Itry it with morfics kernel Iwill have more luck
[Samsung Galaxy Nexus] jbzcar:
After a night of testing, I can tell you this version kicks ass! Phone runs great at 1536 after I gave it a bit more voltage, and stays 100% stable after dropping the voltages of the of the other slots back down to the previous UV levels. Getting ~3600+ in Quadrant now. :D
[Samsung Galaxy Nexus] mrkmrk:
I've not tried that because I have 350 undervolted more than I do 700, but it might be worth taking a shot. I've had nothing but great luck with morfic's 1.38/512 experimental any-kernel build.
[Samsung Galaxy Nexus] jbzcar:
I've been running Morfic's kernels ever since I found them on my GNex. Ran Franco's before that. Always keep my min at 700 and have no appreciable difference in battery life vs a lower minimum and my phone is very stable, so I keep it there. :)
[Samsung Galaxy Nexus] MasterRy88:
Ok just had 2 reboots in less than 3 minutes. Running that kernel morfic posted a page back. Ill try bumping the 1536 slot voltage up and see if that stableizes it
[Samsung Galaxy Nexus] morfic:
Haven't gotten to trying that yet.

Built 1536s without interconnect oc for now.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] morfic:
Since those are nominal, they are higher or equal to previously calibrated voltages.

this kernel does not calibrate.

Best batterylife out of all 1536 anyways.

In terminal do this:

dmesg | grep calib

Has to be done within minutes of booting.

And do it after enabling highest clock.

Do it on your favorite kernel not necessarily last night's build.

Heck compare the output of last night's with that of your previous favorite.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] mrfuzzie23:
the 1536s without interconnect Oc...is that a new one or the one that doesn't work with BT....if u have a 1536 that works with BT...where can I find it?
[Samsung Galaxy Nexus] morfic:
Those work with BT.

Sent from my Nexus Prime.
[Samsung Galaxy Nexus] bluemoon1221:
I've been using this kernel for a long time now.

Does real soccer 2012 lag for anyone?

My CPU governor is set to conservative while the frequencies are 691-1382mhz.

Also do you guys have force gpu rendering enabled? I'm not sure if that will help...

Would this be an app problem or my settings?
[Samsung Galaxy Nexus] dotson817:
Trinity always has the smoothest kernels, but which one is giving you guys the best battery?
[Samsung Galaxy Nexus] zerocool79346:
First off change your governor from conservative to something more keen to ramping, I'd say OnDemand would be good, see if that stops the lagging. Could be that the developer hasn't allowed for HW acceleration just yet.
[Samsung Galaxy Nexus] masri1987:
I have no idea what kernel to pick
[Samsung Galaxy Nexus] bluemoon1221:
putting it on ondemand governor did help although I had a moment when there was a lot of lag and the rest was smooth...

can anyone please try this game out and share your results playing it?

btw I didn't mention this but I'm running cm9 kang with the TNP138-ANY-Fuv
[Samsung Galaxy Nexus] dotson817:
Try one, try another, and another :) have to find one you personally like, they are all amazing
[Samsung Galaxy Nexus] SomeGuyDude:
How's battery treating y'all?
[Samsung Galaxy Nexus] BMAF:
Had a couple of random reboots, first time ever with Trinity Kernels. So I used CPU Spy to check out what was going on. Pretty impressive deep sleep time in one screenshot. It was just a bad flash, reflashed, and no more problems. Just posting the screenshots because they were so weird.

I really like your kernels, thank you for your time and energy.
[Samsung Galaxy Nexus] morfic:
TNP1344-RD-384-orfusr (series of test kernels have weird set of letters, just so i can keep track of which is which)

Once i can give this kernel a little more runtime i'll have an -RD and -ANY version
[Samsung Galaxy Nexus] morfic:
I would like to take a quick moment to thank the many people that "hang around" (however much that is possible on a forum thread) and answer questions people have, I am fairly certain simms22 too often goes "Oh this was already answered, cool".

I get notifications of questions asked at work, after work, trying to answer, done, taken care of.

Users helping users makes such threads a great success.

And i would like to thank everyone who ever helped someone else, be it to confirm a problem they had so it could be addressed, helped figure out their unrelated issues, helped them flash a kernel, rom, get bld/bln/tw/* working:

THANK YOU

All of this helps me and simms22 focus on testing stuff and zoning in on the big problems cropping up in the thread.

I think i will now copy paste this from the Nexus S thread to others, i feel G2x and NP threads and even Sensation threads show the same traits.
[Samsung Galaxy Nexus] dotson817:
You da man morfic keep up the great work!
[Samsung Galaxy Nexus] aznxk3vi17:
Using your kernels on the 4.0.4 roms seems to cause issues with auto brightness. While I know perfection was not to be expected when using a .3 kernel on a .4 rom, would you know why this would be?
[Samsung Galaxy Nexus] morfic:
what kind of issues?
[Samsung Galaxy Nexus] mrkmrk:
I can only speak for myself (and I'm still on cm9 kangs), but auto brightness seems to just stick at whatever the last manual brightness setting was. It's happened to me in the past and wound up clearing itself up, but it hasn't done so yet for me, this time.
[Samsung Galaxy Nexus] vdub804:
Good kernel man I'm using it with stock 4.0.4 everything is smooth as butta :thumbup:
[Samsung Galaxy Nexus] aznxk3vi17:
This is the issue. Usually for me, it boots and stays at the lowest (or close to) brightness. I've found that sticking the phone in front of a massively bright light source forces the brightness to start scaling again, but this isn't consistent for me.
[Samsung Galaxy Nexus] Stank0:
I tried to flash TNP1536-RD-MVM512. It flashed ok but it won't get past the Google logo. It reboots from there 2-3 times and then it'll just hang there forever.

Did even wipe all wipeable.

What am I doing wrong?

Edit: My phpne can handle 1500 just fine on Franco's.

Oh.. and I'm on AOKP #23 (Romanbb)
[Samsung Galaxy Nexus] dotson817:
1536 any breaks nfc?
[Samsung Galaxy Nexus] nklenchik:
Where can I find TNP1344-RD-384-orfusr? :P
[Samsung Galaxy Nexus] mrkmrk:
It has in my experience.

In the future, my friend.
[Samsung Galaxy Nexus] nklenchik:
KK brb...you guys want anything while I'm there?
[Samsung Galaxy Nexus] 9wire:
a Diablo sammich and a Dr.Pepper.
[Samsung Galaxy Nexus] jbzcar:
Thanks nice lady!
[Samsung Galaxy Nexus] Aridon:
Very nice performance, going to check battery life tomorrow but by far the best performer. Franco is a close second.
[Samsung Galaxy Nexus] nklenchik:
Someone give me some settings and I'll be their best friend
[Samsung Galaxy Nexus] Aridon:
Losing about 1% an hour which is great considering the performance I am getting. Love this with AOKP. Thank you.
[Samsung Galaxy Nexus] fcisco13:
Just flash it select governor and leave everything else how it is, morfic kernels are uv to perfection, just flash and enjoy.

G Nexus
[Samsung Galaxy Nexus] kimboinatl:
Just switched over to this kernel from Franco Kernel to see how I like it. Is there any sort of kernel control app that goes with this like with Francisco's? Or do you just install and let it do it's thing?

EDIT: Just ran some benchmarks... damn, this kernel is blazing.
[Samsung Galaxy Nexus] fcisco13:
Exactly, just install and let it work its magic.

G Nexus
[Samsung Galaxy Nexus] bluemoon1221:
just one question

if i want to use the stock 4.0.4 rom (http://xdaforums.com/showthread.php?t=1481613) this one, then

what kernel should i be using with this?

the kernels with RD or ANY? or can it not be used for 4.0.4 at all?...

EDIT: nvm I think it doesn't work at all since it says 4.0.3. sorry about this...
[Samsung Galaxy Nexus] jbzcar:
Woohoo! So I discovered that less can be more while experimenting with my voltages on the 1500 kernel you made. I have more speed and stability at 1500 with less voltage than I was giving it. Eeked this Quadrant out just a few minutes ago. :)
[Samsung Galaxy Nexus] Rem3Dy:
Your version of quadrant is outdated...
[Samsung Galaxy Nexus] jsms0905:
just flashed the trinity kernel uploaded on the 20th on my Gnex CDMA running AOKP 25, it works properly up to the point where i press the power button, then it restarts, any ideas guys? or at least to which one i should go to?

and where exactly to download them from? the link in the OP is either old, or got disconnected. theres only options for tuna and crespo, not toro
[Samsung Galaxy Nexus] jbzcar:
Better?
[Samsung Galaxy Nexus] buhohitr:
Yes and it still remain the same...KickAsS.

BTW, what rom are you using with this kernel?
[Samsung Galaxy Nexus] jsms0905:
what app are you guys using to tweak the min and max along with volts? and any recommended UVs? brand new to this kernel, heard lots of great things!
[Samsung Galaxy Nexus] jsms0905:
im guessing no one is gonna help me out? huh
[Samsung Galaxy Nexus] bluemoon1221:
it already has all those settings.

from my experience its best not to mess with them. already really good