yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mike216:
That's some bull**** how he got passed up when they gave away some.He's been developing for awhile now!
[Samsung Galaxy Nexus] :
I agree, but luckily we are slowly getting there in donation thread.. *touch wood*

Thanks!

--

Sent from my Nexus Prime powered by Trinity currently in 1st circle of Dante's hell
[Samsung Galaxy Nexus] morfic:
meanwhile, idle drain fixed versions are in testing
[Samsung Galaxy Nexus] mike216:
Thanks morfic! I just downloaded the 384 Fsync disabled version. Does it have the idle drain or is it the current idle drain test version? Thanks donated also
[Samsung Galaxy Nexus] morfic:
http://en.wikipedia.org/wiki/Fsync

I'm not going to interfere with people's facebook habits ;)
[Samsung Galaxy Nexus] mike216:
?

Feel like an idiot! What version is better? For battery or in general, thanks
[Samsung Galaxy Nexus] mykenyc:
Haha, how would we know if a kernel has been updated, since there is no date indication.

Instead of Fsync you said Facebook.
[Samsung Galaxy Nexus] morfic:
Let me put it this way, if anyone downloads any of those kernels, they will see when there is a new one, it will be easy to spot and obvious.

For those who flashed the initial release, ANY change in filename will be meaningful and obvious, for those who stumble upon this kernel after the 4th release, the names of the first 3 releases will be meaningless, and they too will be able to recognize release #5 has a difference in filename compared to the release#4 they flashed first.

Think about that for a moment.
[Samsung Galaxy Nexus] mike216:
Is the idle drain up, sorry if this was answered in your reply but as you can tell by my facebook sync question I'm not playing with a full deck!
[Samsung Galaxy Nexus] morfic:
It's being addressed, idle drain is back down in the 2 test kernels being evaluated now.

Taking time to test the 384MHz Inferno longer, dropped core voltage for 384MHz, so they will get more testing.
[Samsung Galaxy Nexus] mykenyc:
Sarcasm noted, thanks, hope you get the nexus soon.
[Samsung Galaxy Nexus] morfic:
Nah, I saved the sarcasm for another post. I just used a lot of words to describe what's going to go down.
[Samsung Galaxy Nexus] mike216:
When I get my income tax check back ill make a nice fat donation! Should be soon I hope were close and it would be really nice if this awesome community would give a little,not only would morfic appreciate it but the contribution made by morfic would ripple through the whole kernel development community! I'm a factory worker who loves his technology so I find a way to give back!
[Samsung Galaxy Nexus] :
Inferno installed, donation sent. Glad to have a Morfic kernel on my GNex after all the different versions I ran on my NS and G2x.
[Samsung Galaxy Nexus] mykenyc:
Cool, love the kernel nonetheless.
[Samsung Galaxy Nexus] LexusBrian400:
Love the kernel.. donation incoming.
[Samsung Galaxy Nexus] Stadsport:
I just wanted to share that I get noticeably better battery life with the powersave governor. It just limits the clock to 350mhz, which makes the phone laggy at some points, but it's surprisingly snappy at this speed, so I don't mind it capped at this speed during the day.

I was initially running conservative, and towards the end of the battery's life, I switched it to powersave. The drain was noticeably better during use.

Here's a closer view of that change:

I haven't done any long-term tests to show what the total difference in battery life is, but it definitely seems worth having slightly choppier animations. I have SetCPU set up to switch me to interactive while on USB/AC power, and powersave when on battery power. It would be nice if it could switch on a per-app basis, ie, switch to interactive or performance when running N64oid, and back to powersave once it's closed.

This is with the 512mhz kernel, by the way. I'm going to flash the 384mhz kernel and see if there's a significant performance and/or battery change. According to imoseyon, the GPU isn't actually seeing 512mhz. I mean, maybe it's not the 512mhz that makes this kernel fast, but just the kernel itself.

Edit: Removed the first image because people are ****ing idiots and can't read.
[Samsung Galaxy Nexus] cms5423:
All I have to say about the previous post on the powersave governor: LOL!
[Samsung Galaxy Nexus] SomeGuyDude:
So let's get this straight: you used the phone moderately early in the day, then used it HEAVILY, and are attributing the change in battery drain to the governor?

...riiiiiight.
[Samsung Galaxy Nexus] Stadsport:
No, read the entire post instead of just glossing over the pictures and drawing your own conclusions. Towards the end of the battery cycle, I was using the phone the entire time. When I switched the governor to powersave, the drain was significantly less than on conservative. The second picture shows this quite clearly.
[Samsung Galaxy Nexus] cms5423:
Why in God's name would you ever set your max clock speed to 350mhz on this phone haha.

(and of course you would get better battery life when you underclock it by that much)
[Samsung Galaxy Nexus] SomeGuyDude:
Try this out: set the governor to performance, but cap the freq to 350 in SetCPU. See how that works out during constant, heavy use. Chances are it'll drain a bit more slowly than otherwise because you STOPPED THE CLOCK SPEED FROM GOING HIGH.

Unfortunately, for overall, NORMAL use, this is a horrible idea for a hundred reasons I'm far too tired to get into.
[Samsung Galaxy Nexus] Lyxdeslic:
Even with an idle drain bug, I've gotten 10 hours so far today with 33% battery still left as we speak. Screen on time has been 2 hours and 8 minutes. Brightness has not been moved from roughly 25% all day. I've done an hour of playing "Little Empire", exactly 40 outgoing texts, but only 18 total minutes of phone talk time. Web browsing is something I forgot to monitor, but a good guess would be about 15 minutes. Random apps such as Tapatalk: about 10 to 15 minutes total. Major thing to note, however: I havent activated 4G at all today...90% of the time its been WiFi. Minor detail: NFC turned off. Also, its smooth as butter.

Version: Trinity 384 with fsync disabled. Going to donate.
[Samsung Galaxy Nexus] Stadsport:
What's your point? That capping at 350mhz will save power? Because that's exactly the point of my post. All the powersave governor does is fix the clock speed at 350mhz. The reason to use it over interactive (or performance or whatever) & capped is because it won't waste resources monitoring the CPU load. (See http://xdaforums.com/showthread.php?t=843406).

All I was showing was how much battery life can be gained by using the powersave governor. And having used it for a couple of days I can also say it works fine for everyday normal use, and as you can see from my screenshots it DOES have a positive affect on battery life.

But if all you have to say is that I'm wrong for sharing information, then by all means, carry on.
[Samsung Galaxy Nexus] nklenchik:
As far as the kernel goes, I'm running 384(?) on hotplug and it's very snappy. I'll post back here or on rootzwiki for battery life.

Only thing I would say this kernel needs is interactivex or smartassv2 (kinda just for kicks haha)
[Samsung Galaxy Nexus] :
when you try conservative in next release you'll just forget about interactivex and smartassv2 :p
[Samsung Galaxy Nexus] tomit12:
I can't speak to what speed it actually hits, but Nenamark2 instantly jumps from 27.7 to 31.2 fps ONLY when using the 512 kernels. I've tried every other variation of every other kernel and have never broken 27.7. At that fps range, something about the 512 kernel is making a considerable difference regarding gpu performance, and if it isn't the speed, then I don't know what it is.

On a separate note, is anyone able to get GTA3 running on any of the inferno kernels? Its the only game I've had trouble with, but it crashes on launch. Haven't had that happen on any other kernel / rom.
[Samsung Galaxy Nexus] :
As I said in GSM thread, GTA will be fixed in next release. Hard to follow both threads x4 others on different places. :)
[Samsung Galaxy Nexus] tomit12:
Ah, I wouldn't have read the GSM thread, but good to know.
[Samsung Galaxy Nexus] morfic:
You know something I don't?
[Samsung Galaxy Nexus] :
I hope so :P, at least something or I would feel pretty bad, anyway posted in NP dev thread.

Sent from my Trinity fiqfck'd powered Nexus Prime
[Samsung Galaxy Nexus] morfic:
If the system/bin/sdcard is all that's needed, guess it could be fixed in release after idle drain fix.

But then people switching from Franco to Trinity wouldn't have issues. Will look into it.
[Samsung Galaxy Nexus] morfic:
idle drain fixed versions up on www.derkernel.com
[Samsung Galaxy Nexus] hijackerjack:
I'm curious.. is it possible to manually shut off cpu1? I wanna see how my phone would be if it only had one CPU core.
[Samsung Galaxy Nexus] morfic:
Yes you can.

And i can tell you, that when i kept the CPU1 off longer (nvidia bases it on x time over x MHz), noone complained, if you need it, CPU1 is there, otherwise it is off, saving your battery.

I will either use what francisco already has or see what else i can come up with.

morfic@othris:~$ adb shell cat /sys/devices/system/cpu/cpu0/online
1
morfic@othris:~$ adb shell cat /sys/devices/system/cpu/cpu1/online
0
morfic@othris:~$

that is me checking which cpu is online on my screen off idle G2x there.

just do this:

adb shell 'echo 0 > /sys/devices/system/cpu/cpu1/online'

the single quotes are important when using adb

or open a linux terminal on your phone and do this:

echo 0 > /sys/devices/system/cpu/cpu1/online

but keep an eye on it, making sure cpu1 is off when you think it is off
[Samsung Galaxy Nexus] dadsterflip:
Gpu oc running stock voltages?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hijackerjack:
Holy crap thanks Morfic! And so far no idle battery drain. This is pretty awesome.
[Samsung Galaxy Nexus] morfic:
There is a good amount of UV on the kernel to begin with, do not UV if you hit SoD with extra UV.

Test without making changes and let me know how that goes for you.

'night
[Samsung Galaxy Nexus] :
Can you post your UV you tried when getting SOD? Thanks!
[Samsung Galaxy Nexus] :
Thats some crazy uving, will try it.. I am running currently:

1200

1100

1000

900

800

With no sods and I thought I was crazy :p
[Samsung Galaxy Nexus] :
Well you are crazy, but so am I..

I like my numbers to match lol.
[Samsung Galaxy Nexus] nklenchik:
Flashing the 512 right now...wish me luck :)
[Samsung Galaxy Nexus] nklenchik:
Haha so far so good. Is everything stable running that setup? I know if I UV too low and unplug my phone in the morning I'll get the blank black screen and have to do a battery pull haha
[Samsung Galaxy Nexus] hijackerjack:
For me, turning off CPU hasn't been very useful. I still get the same crappy battery life as before, though its maybe a little better. I've even made sure that the core is always off. It seems to only come back on when you reboot.
[Samsung Galaxy Nexus] RamAir02:
Well my phone didn't like these settings. Phone froze upon applying these voltages and backing out of SetCPU.
[Samsung Galaxy Nexus] :
Well, my uv also works fine, didn't set it on boot yet as I'm still not feeling comfortable with going so low.

Sent from my TEUV'd Nexus Prime
[Samsung Galaxy Nexus] bluemoon1221:
Great kernel:)

I first read about this somewhere using pulse and decided to try it out. First few hours is great so far.

One big difference was gaming for me. I used to run Franco kernel. And now I'm using this kernel that has overclocked gpu.

I believe franco has its gpu overclocked too but the gaming experience just seems do much smoother on this kernel.

Thanks for such an awesome kernel :)
[Samsung Galaxy Nexus] :
remove battery from your phone for at least 90 seconds, that should *reset* max17040 or whatever is chip in NP and it will stop doing it :)
[Samsung Galaxy Nexus] housry23:
I'm really tempted to try this kernel out. I'm using Franco's kernel now and it has been good for me so far. I may wait until morfic gets his GNex and can really play with it and test it on his own. How has battery life been for everyone so far? That's really my main concern. I am more interested in battery life than speed.
[Samsung Galaxy Nexus] kronusx12:
Honestly, I love Franco's kernel, I bought the app to support him and everything, but I'm REALLY liking morfics kernel. Definitely getting better battery life with morfic. Still testing it out, but it might actually get me to switch.
[Samsung Galaxy Nexus] mtw4991:
I know it was posted a few pages back but not everyone reads past the last page. I fixed my idle drain on 512b by doing the following:

Boot recovery, wipe cache/dalvik, flash faux123 reset kernel, flash franco 13.1 kernel for ramdisk optimizations, reboot.

Boot recovery, wipe cache/dalvik, flash morfic 384b/512b kernel, #disco idle drain fixed.
[Samsung Galaxy Nexus] Lyxdeslic:
Why would flashing 2 custom kernels prior to morfics be the solution for a fix contained in a previous version of morfics? Do we also have to sacrifice a goat and dance around a bonfire?
[Samsung Galaxy Nexus] MasterRy88:
Couldnt hurt right?
[Samsung Galaxy Nexus] Lyxdeslic:
Alright then, I'll report back in a few. Gotta find out who sells goats in San Diego.
[Samsung Galaxy Nexus] :
Virgins are fine also.
[Samsung Galaxy Nexus] nklenchik:
When are you getting the gnex? I'm loving this kernel btw
[Samsung Galaxy Nexus] mtw4991:
I'm liking the virgins, but still thinking about the goats!:D

Seriously though, (as I understand it) this kernel is an anykernel and doesn't touch the ramdisk at all, that's why it can be used with almost any 4.0.3 rom.

I've ran stock CM9 kernel, faux123 kernel(multiple versions) and morfic's first sets. I couldn't get to the 2mA idle drain that others were getting, 35-78mA at best.

Faux123's reset cleans out any leftover code and installs a new boot.img and gives a clean slate to flash Franco's kernel which mods the ramdisk with some optimizations and those mods stick even after flashing morfics latest. Going forward, you shouldn't have to do this again. Idle drain now at a steady 2mA!
[Samsung Galaxy Nexus] aznxk3vi17:
I'm getting some lag upon waking up the phone and unlocking. This is happening even with min set at 700 and interactive governor. Morfic, is there any way you can implement a CPU ramp upon screen on to avoid any lag? After the phone is unlocked everything is smooth as silk.
[Samsung Galaxy Nexus] nklenchik:
Conservative gov, use that.
[Samsung Galaxy Nexus] hijackerjack:
Not necessarily. I had the one core running at 700 MHz with the software renderer going too so it still was pretty fast. I'm starting to think the battery problems have more to do with the screen.
[Samsung Galaxy Nexus] aznxk3vi17:
How would this help? If anything, conservative would make the lag more apparent, due to the slower ramp up of CPU upon load.
[Samsung Galaxy Nexus] Lyxdeslic:
Thanks for the clarification. This all sounds nice...but I'm still a bit skeptical. If the only way to achieve a low, steady, and stable mA during idle is to flash Franco's prior, simply in an effort to implement some optimization and tweaks that won't be erased after flashing morfics, then why wouldn't morfic just...implement them himself into his own kernel?

Also, morfic made it clear that the idle drain bug was identified and fixed, but nowhere in his posts does it say to "flash stock, then this other dudes kernel, THEN flash mine."

Anywho, I'm just hoping someone could clear this up some more for me. However, if a simple verification/confirmation could be provided that does indeed show that Franco's RAM tweaks do remain constant after flashing a new kernel over his, then I would actually flash Franco's prior to flashing morfics. I have no idea how to test that, though....besides the long way of monitoring performance in specific scenarios. Ew.
[Samsung Galaxy Nexus] :
Try here from post number 207 and up

http://xdaforums.com/showthread.php?p=21790515
[Samsung Galaxy Nexus] morfic:
I prefer ramdisk kernels as it gives better control over the result people will have on their phone.

I stuck to anykernel since it cuts down on ramdisk building time.

As his results show, i'll safe myself more headaches using a ramdisk rather than avoiding it, now that i can test a ramdisk myself, I'll go back to good ol ramdisks, served me best on G2x
[Samsung Galaxy Nexus] Lyxdeslic:
Thanks for the responses guys. Aside from all that, I am seeing pretty sub-par battery life so far with the new Trinity 384-b with both ondemand and conservative. From 100%, on conservative, I'm now at 47% a mere 4 hours and 30 minutes later, with 1 hour and 31 minutes of screen-on time at about 10% brightness the entire time, with LTE off the entire time and WiFi on 90% of the time thus far. I almost feel like the initial release version was giving me better battery life.

EDIT: Eh, I forgot to mention that I still haven't tried flashing Franco's prior to flashing Morfic's. Let me try that tonight and I'll report back tomorrow or the day after.
[Samsung Galaxy Nexus] jake:
Flashed 512b a while ago ... say what you want .. Morfic's kern has some of the best stability out there - right up on par with stock (i am finding even superior?)

Right now testing voltages out to find out my phone's sweet spot. phone runs quite cool

will report back with specifics

*Edit 1* Started out by referencing a voltage chart here (pulled from the thread) (thanks guys (bencozzy +) and playin w/ voltages until things were relatively close to those values, but more on the safe side for the moment - cpu is running cold cold at 29 C / 84 F

O/c'd @ 1350, good old Interactive governor my curve

1350 mhz - 1200 mv

1200 mhz - 1100 mv

920 mhz - 1000 mv

700 mhz - 875 mv

350 mhz - 775 mv

checked out a couple of youtube vids - noticing stability superior to anything kernelwise i've tested yet. + this kernel is super snappy!

/edit 1/25/12 10:35AM (wiped cache / dalv, installed francos booted, returned to CWM flashed Morfics over and noticed the screeching hault my idle drain does appear to have been effected - at time of initial post, with a clean (faux's kernel reset 1st) install of Morfics, batt drain at idle was good (somewhere in the 1% / 1.5 hr range), after flashing francos / followed by Trinity drain has been markedly decreased to roughly 1% / 3 hours +

logic tells me that these commits should be merged (or something lol) in some way (or using similar method) b/c i have not seen this type of stability + batt drain with this device until now. (Yes, LTE is off (as it should be if not in use ), data enabled when in use, screen on above average (over 4+ hrs / charge)

hats off morfic! (thank you!)

testing tommorrow will followup with an edit / new post!

Cheers!
[Samsung Galaxy Nexus] nklenchik:
Anyone correct me if I'm wrong, but I think this was made with conservative in mind
[Samsung Galaxy Nexus] aznxk3vi17:
Which wouldn't make sense, because the default governor is ondemand.
[Samsung Galaxy Nexus] irb123:
So, I flash faux's, then franco's, then morfic? Do I need to reboot and wipe cache/dalvik in between each one?
[Samsung Galaxy Nexus] morfic:
Make sure you have the original kernel of your from.

Flash trinity.

reboot.

Remove /system/etc/init.d/98tweak

Reboot

Next kernels won't contain the script until it becomes necessary again.

You can remove it from the zip before flashing unless you don't know how. Then the above works.

One thing Franco kernel ramdisk achieves is not running init.d so for now remove the script.

Will work on ram disks later anyway.
[Samsung Galaxy Nexus] aznxk3vi17:
Good tidings, indeed.
[Samsung Galaxy Nexus] jake:
Francos will add the RAMdisk tweak , then flash Morfics should notice little to no drain at idle

my phones been off charge for 5 hours and it has 91% batt (normal every day use)

with the GPU overclocked, we can (it seems) undervolt the CPU moreso a bit
[Samsung Galaxy Nexus] nklenchik:
Don't shoot the messenger, just trying to help man
[Samsung Galaxy Nexus] sinik420:
would recommend registering and checking my-andro.com, the kernel is supported over there with a much smaller thread with less frequently posted same questions.
[Samsung Galaxy Nexus] neederishelp:
Like the kernal page says to do too lol
[Samsung Galaxy Nexus] ChickenGod:
Just kidding. Kernel is great.
[Samsung Galaxy Nexus] LexusBrian400:
Which app are you using to detect IDLE drain? Thanks IA.
[Samsung Galaxy Nexus] mrkmrk:
Broken on tonight's CM nightly from winner :(. If only I still had the 1.24 build (I stupidly deleted it), I would just stick to that + 512b. Grrrrrrrrr.

(For what it's worth, he said that "some" custom kernels would not work with this. He apparently knows why? I don't.)
[Samsung Galaxy Nexus] morfic:
Was wondering how long it would take for CM to break samsung/google source.
[Samsung Galaxy Nexus] mrkmrk:
Oh, is that what happened? Consider me sad.

Also, phone is noticeable slower without your delightful kernel. Shame.

(Enjoying actually owning the phone, by the way?)
[Samsung Galaxy Nexus] morfic:
If their nightly suddenly does not work with custom kernels, it's their change that did it ;)

If i like it?

Pfft, what's not to like? :)

Yes i enjoy it.
[Samsung Galaxy Nexus] mightybrick:
What are you using to read CPU temps? I have several apps that usually will give me CPU temp, but currently will not. Are basing these temps off the battery?
[Samsung Galaxy Nexus] avetny:
noooo!!! why galaxy nexus MORFIIIC !!!!!!!:(
[Samsung Galaxy Nexus] nklenchik:
Hahaha what's wrong?
[Samsung Galaxy Nexus] avetny:
You lucky guys.
[Samsung Galaxy Nexus] MFD00M:
from what i understand it has to do with ramdisk changes made in cm9 (no idea what, over my head).
[Samsung Galaxy Nexus] irb123:
Been getting pretty good life, with a quick 10 minute break on the charger
[Samsung Galaxy Nexus] bluemoon1221:
Can anyone confirm this working with

Cm9 kang 1/27?

I'm currently on cm9 kang 1/21 and don't know if I can use this kernel with the latest update.
[Samsung Galaxy Nexus] nklenchik:
Why don't you make a nandroid and test it out for the rest of the crowd? :P
[Samsung Galaxy Nexus] sway40:
+1 on that i want to know as well, go test it out and report back.
[Samsung Galaxy Nexus] irb123:
CM9 works for me, but I have the init.d removed from the kernel, don't know if that would change anything...
[Samsung Galaxy Nexus] Stank0:
Is this possible? How can it be?

It's ondemand. If I switch it to hotplug, It'd freeze and restart.

Confirmation
[Samsung Galaxy Nexus] combatmedic870:
Your voltages are to low man. :eek:

bring 350 up to 775 atleast and 700 up to 925ish.

you need to have some power going to 700 or your phone will never use it.

Im surprised your phone wakes at all.
[Samsung Galaxy Nexus] mistermojorizin:
have there been any updates since you got the phone, morfic?
[Samsung Galaxy Nexus] Stadsport:
I just wanted to report that I've been running an on-battery profile that sets the governor to conservative and limits clock speed to 350mhz-700mhz. I've been using this setup for a few days and I honestly forgot it was capped at 700mhz, the phone runs great like this, and keeping the CPU out of the high clock speeds noticably improves screen-on time.

I wish I could make a quick toggle to switch SetCPU to my "high performance" profile, so I could uncap the clock speed easily to play a game while on battery, but oh well.
[Samsung Galaxy Nexus] Stank0:
That's why I posted it. I'm surprised the thing is even working at all.

CpuSpy says 5%@1350 and 9%@350 the rest is deep sleep. I wasn't using the phone too much. Was riding my motorcycle the whole day with the phone in my pocket.
[Samsung Galaxy Nexus] nklenchik:
Can someone post their voltages for me? (UV wise)

I either go too hard or not enough haha :D
[Samsung Galaxy Nexus] Stank0:
I don't know about y'all but I like my voltage settings. The phone works flawlessly an the battery life is amazing. Given I wasn't using it much but for me it's important that I don't have to charge it 2-3x a day in order for it to be ready if I need to use it.

Note the wifi is on almost all the time and LTE is on.

I want to see how long before my battery drops to 1%. I'll let you know ;)