yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
r130:

THIS NIGHTLY IS A BIT EXPERIMENTAL AND MIGHT BE UNSTABLE SO FLASH AT YOUR OWN RISK. Nevertheless I haven't got complains yet

* Added roughly 40 OMAP4 power management patches - might help, or not, the battery life

* Reduced voltages of two components used by the screen - might increase screen_on battery life

* Added a patch to Ondemand to improve responsiveness

* Tuned Interactive up_threshold from 95 to 80 to be on par with Ondemand's and thats my sweet spot for battery/performance balance.

* Added an helper to Interactive to acknowledge a request for max frequency before the system is loaded. Might help with a little extra performance and battery

* Increase Hotplug governor up_threshold from 80 to 90 - it's a very conservative governor so we now make it even more aggressive.

* Increase Hotplug governor down_threshold from 35 to 40

* Disable generic_hotplug by default

* One or two extra small patches
[Samsung Galaxy Nexus] laureanop:
So far so good on 130. Went through all the benchmarks without a hiccup. Will keep checking for sod. Running on demand. 384-1366, no hot plug , undervolted to withing 50 of calibrated

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] TEK112:
Sorry, but you definitely said the rate of drain was higher. That's why I responded about it being a reporting bug.

Also, it's not the kernel that affects Android OS reporting, it is the ROM.
[Samsung Galaxy Nexus] mike216:
No the kernel made a difference on Android OS reporting. Definitely lower reporting on 4.0.4 kernels if I explained this wrong before then I made a mistake.

On 4.0.3 kernels the average Android OS reporting is on average 16% and on 4.0.4 kernels the drain average is around 9%

So the kernel made a difference for me on the same rom
[Samsung Galaxy Nexus] TEK112:
Now that is very possible.
[Samsung Galaxy Nexus] Adan.Mejia3:
Franco love your work man. First Kernel I am a loyal user to. No need for anything else, your kernel is best out there hands down.

Trying to figure out a way to buy you a touchpad so you can develop for it. I would love your work on my touchpad.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BixBix78:
I must say I've been on your kernels for some time now and r130 on the latest miui rom is smooth as silk. Great nightly on my device. 0 issues
[Samsung Galaxy Nexus] holysnikey:
I personally am getting really bad battery compared to r121 which was giving me some of the best screen time I've ever gotten on the GNex. I used the Franco app and autoflashed. Should I may be flash the proper way?
[Samsung Galaxy Nexus] mike216:
No but you can go back in recovery and wipe the dalvik cache
[Samsung Galaxy Nexus] TEK112:
Awesome!

Franco, how about an option to view the GPU clock speed?
[Samsung Galaxy Nexus] axne1:
Yeah oc gpu WORKS for me now!!!!!

Thanks Franco! Now to test battery and performance :)
[Samsung Galaxy Nexus] spinkick:
Franco, does overclocking the GPU make any sort of difference on this phone? I keep asking and nobody really knows.. so I thoughtd id ask I cant get a real world difference
[Samsung Galaxy Nexus] andrew53517:
See, I'm the complete opposite. I notice very little difference in benchmark results, etc. but a major difference in smoothness in scrolling and overall user interface. I think 512 MHz gpu clock speed, if you can run it, makes a pretty big difference personally.

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Aerocaptain:
I believe it does make a difference. Transitions and scrolling seem to improve. Apple may actually have something right. Their philosophy seems to prefer high GPU clocks and lower processor speeds. Of course this could all be a placebo effect.

Sent from CDMA GNexus w/Liquid & franco.kernel
[Samsung Galaxy Nexus] NinjaMic:
This is all you have to do to go back a few versions right?

I'm on 121 and I'm thinking of trying out M2
[Samsung Galaxy Nexus] axne1:
Yep
[Samsung Galaxy Nexus] spinkick:
Interesting. I'll give it another try.
[Samsung Galaxy Nexus] TEK112:
I have noticed the same thing. Since running the OC'd GPU I have less homescreen/drawer lag and less chop when playing high end graphic games. The games played fine before, but the initial cut scenes while data was loading would be choppy.
[Samsung Galaxy Nexus] kingoanklebreakn:
Yeah I've noticed it too. But I just wonder what the difference in battery life is.
[Samsung Galaxy Nexus] zeke1988:
Here are the pictures of my gn using 130 oc gpu

I say it's pretty good.
[Samsung Galaxy Nexus] Aerocaptain:
If I remember correctly, from Franco's first OP, he mentioned that he wouldn't implement the GPU overclock because he had heard from a reputable source that a relatively small GPU increase produces a largely disproportionate increase in power consumption. Whether he had found a way to reduce that disproportionate battery drain or not, I'm not sure. But personally I'd rather have a device that lives up to the Nexus name by operating smoother than most if not all other android devices rather than having an extra hour of battery time at the end of the day.

Sent from CDMA GNexus w/Liquid & franco.kernel
[Samsung Galaxy Nexus] franciscofranco:
Thats true thats why the stable releases have stock GPU clocks.
[Samsung Galaxy Nexus] kingoanklebreakn:
@Zeke1988 We have much a much different definition of good battery life. Your screen has barely been on.
[Samsung Galaxy Nexus] TEK112:
Agreed, but I blame that on his white screen. White backgrounds kill battery life super amoled screens.
[Samsung Galaxy Nexus] laureanop:
Just for the sake of argument I installed the higher gpu speed 130 kernel and the difference in speed and fluidity of graphics is negligible . As a matter of fact the only place I see it is in the boot animation. Curious thing : my quadrant is 500 points lower and antutu 1000 points lower. Go figure. Also my smart keyboard seems to be less responsive.

Battery life seems to be the same.

I'll stay on the 512 gpu till your next release

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] spinkick:
This has been my experience.
[Samsung Galaxy Nexus] TEK112:
Isn't 512 the higher GPU?
[Samsung Galaxy Nexus] laureanop:
Yeah I meant I don't feel like flashing back to the 384 mhz...

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] blckngldhwk:
Anyone know what the 'hotplug' governor is on the latest app update, build 130?
[Samsung Galaxy Nexus] zeke1988:
If I set everything black and lower to 20% and limited my cell phone use. Wouldn't it be better if I buy an iphone and use it without any of those limitations?
[Samsung Galaxy Nexus] mikespe:
When the iPhone 5 comes out with 4g then ALL will be even! Comparing apples to oranges when the iPhone 4s (3g ONLY) goes against the Nexus
[Samsung Galaxy Nexus] azsl1326:
Running r130-384 and experiencing multiple SODs using the hotplug governor.
[Samsung Galaxy Nexus] axne1:
Giving oc gpu for a lil before I judge.

so far stable though.

:thumbup:
[Samsung Galaxy Nexus] kingoanklebreakn:
Lol my point was that you hadn't really used it much.
[Samsung Galaxy Nexus] ArtnerC:
121 was fantastic on 700/1200 384 ondemand no-hotplug for battery life and felt extremely responsive on AOKP 30/31. Normally I had to use the 512 to feel the same consistent fluidity. Now 130 doesn't feel much worse but the battery drain seems quite a bit higher when the screen is off. Could have been the difference in use but still appears to be worse than 121 regardless.
[Samsung Galaxy Nexus] sic0048:
No, but he is still on pace to get 4+ hours of screen time and 14+ hours of total time. Obviously actual results might be a little different and we don't know were he started the day when he removed the phone from the charger (was it at 99% battery, or 91%, etc). But that isn't all that bad IMHO when you factor it out like that.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Not really. Apple actually cares about battery life. LTE won't make the battery life any worse because Apple will put a better battery in it. iPad 3 is a great example.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
stop all this apple talk I'm eating lunch
[Samsung Galaxy Nexus] zeke1988:
yea, they even upped 4s battery even tho iphone 4 was doing good.
[Samsung Galaxy Nexus] chicojd:
WiFi Tether?

Wondering about the use of tethering apps with this Kernel... I tried it with the stock 4.04 kernel and would not work. Is it enabled in this one?
[Samsung Galaxy Nexus] sway40:
Got good results from aokp 31 and franco nightly 130 with battery, this after just not so good things happening for some reason. I still can't flash fresh aokp roms bc my camera freezes and makes my phone reboot. I have to flash over a aokp rom 28 or under to work right.

Anyway 3.5hrs screen on with a lil over a day on battery, generic hotplug on, aokp battery saver on, screen half brightness, some wifi not a lot, and ondemand.
[Samsung Galaxy Nexus] TEK112:
I had to use wireless tether beta. The stock tether would not work:

http://code.google.com/p/android-wifi-tether/
[Samsung Galaxy Nexus] chakra:
Or you could always pay for the service and it will work every time, just saying.
[Samsung Galaxy Nexus] Aerocaptain:
Sure. You can pay again to use data you already pay once for.

Sent from CDMA GNexus w/Liquid & franco.kernel
[Samsung Galaxy Nexus] alphanu22:
just turned on the Hotspot Toggle and worked fine-
[Samsung Galaxy Nexus] TEK112:
The toggles are ROM dependent. Some work and some don't.

However, I prefer wireless tether for it's MAC filtering abilities.
[Samsung Galaxy Nexus] TEK112:
This....
[Samsung Galaxy Nexus] Tree of Knowledge:
Running AOKP 31 and nightly 130 and stock tether works just fine for me.
[Samsung Galaxy Nexus] mike216:
Hey sway was this 4g or mostly wifi?
[Samsung Galaxy Nexus] cdchris12:
I've started to notice a startling trend after flashing nightly #121. I'll turn my wifi on, leave my phone asleep in my pocket for a while (usually a couple of hours or so at a time), and check my phone again to find that I could cook an egg on the battery cover, and wifi has turned itself off. This is also accompanied by a dramatic drain in the otherwise awesome battery life.

I'm running BAMF Prodigy 1.1 with Franco nightly 121.

Power consumption is at 34% screen, 22% phone Idle, 17% cell standby, and 14% android os. Any ideas?
[Samsung Galaxy Nexus] franciscofranco:
That is a 4.0.3 rom, this is a 4.0.4 kernel, I'm sure something along those terms is causing the problem.
[Samsung Galaxy Nexus] mike216:
Thanks Franco!

Touchwake touchwake
[Samsung Galaxy Nexus] gnexdude:
Thanks Franco!
[Samsung Galaxy Nexus] spinkick:
Can someone teach me what BLX is? I'll google but for the sake of all of us it might be interesting to list here.

---------- Post added at 08:46 PM ---------- Previous post was at 08:39 PM ----------

Here is an artical on the GPU in the galaxy nexus and why its set the way it is. even comments on the overclocking:

http://knowmydroid.com/blog/why-is-the-gpu-inside-the-galaxy-nexus-clocked-at-308mhz-instead-of-380mhz
[Samsung Galaxy Nexus] vtmike:
I was able to run nightly 130 at 584mhz with no problems. For some reason I'm not able to run 133 at 584mhz, 384mhz is working though.
[Samsung Galaxy Nexus] illcat2000:
I'm getting a forceclose on the Franco app when I tried to download 133 nightlie. I tried a few times anyone else getting this I sent the app crash in however. It was the 384 version btw.
[Samsung Galaxy Nexus] sway40:
Running 133 stock gpu with no problems yet, I flashed manually in cwm though. Kernel seems snappier.
[Samsung Galaxy Nexus] DDRFAN:
BLX stands for Battery Life Extender. It limits it from hitting 100 (As Li-on batteries tend to get worse when they are as full as can be, or as empty as can be) BLX limits it to sit at whatever value you want it to at max charge.
[Samsung Galaxy Nexus] SomeGuyDude:
I'm still seeing higher IVA/Core voltages on the 384 slot with r133. 1012 and 1050 respectively.
[Samsung Galaxy Nexus] TheColdOne:
Started running into severe graphical issues with 133. Went back to 130 and it works fine still. Wasn't able to test further for other issues.

Attached screenshots show the issue (though not to the severity that it reached).

Running Galaxy Nexus i515 with AOKP Build 31 and (now) Franco Kernel r130.

http://dl.dropbox.com/u/3294071/Screenshots/2012-04-10%2022.13.47.png

http://dl.dropbox.com/u/3294071/Screenshots/2012-04-10%2022.14.18.png
[Samsung Galaxy Nexus] laureanop:
Was that with the 384 or the 512 ?

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] TheColdOne:
512
[Samsung Galaxy Nexus] mike216:
I'm on 133 and everything so far is fine
[Samsung Galaxy Nexus] mike216:
Screen on drain is very good! At this rate I'm on track to get that magical 5 hour

screen on!

This screen on is insanely good! This is and edit so I can add its even better the more I use it and if this kind of stability and battery holds up then I don't see how this couldn't be M3! Without a doubt the best nightly yet! Nice work Franco!
[Samsung Galaxy Nexus] mike216:
Your on a nightly rom with its own color control built into it. Maybe this could possible have something to do with it?
[Samsung Galaxy Nexus] laureanop:
It might be that your phone can't handle the 512 oc. Did you try the 384 ?

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] gnexdude:
So far so good on 133, I notice a snap pier feel to it! Flashed it using the app, no issues...I'm obsessed with battery lol!
[Samsung Galaxy Nexus] axne1:
So far so awesome! Didn't go for the 512 this time... But I'm still on the night train.

:) :beer:
[Samsung Galaxy Nexus] csseale:
I've been running all your kernels on BAMF and never had a problem. The two seem to work perfect together. So I wouldn't automatically jump towards the 4.0.3 thing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] spinkick:
Cores seem to be upvolted still on this release as someone else noted.
[Samsung Galaxy Nexus] mike216:
+1 I'm old school also,still on 4.0.3 and everything is great
[Samsung Galaxy Nexus] sway40:
He's saying that if your on a new nightly which has the source code for 4.0.4 and your on a 4.0.3 rom then things won't run right. You need a 4.0.3 kernel like m2.
[Samsung Galaxy Nexus] Tree of Knowledge:
This. I'm on 384 and it looks like it's still the same for me too.
[Samsung Galaxy Nexus] GinoSylum:
Has anybody seen this one? I am running AOKP 31 with Franco m2. No problems at all. Music works, I have a song as my ring tone, all good. I downloaded the latest nightly Franco kernel and all my music programs stopped reading music. It says it can't read the file type. My ring tone stopped working too. So I went back to M2 and no change, music still doesn't work. For the record I download, dropped into CWR and flashed there, not in the app. So i did clear cache.
[Samsung Galaxy Nexus] NinjaMic:
Similar thing just happened to me using the browser and playing Sonic CD

Went back to 121 for now
[Samsung Galaxy Nexus] NinjaMic:
Also I just downloaded the kernel from the OP.

Should I try the 384 zip using the updater? I haven't touched settings in any case.

On AOKP b28 also
[Samsung Galaxy Nexus] gnexdude:
You should be OK. That's how I flashed it. I'm on Axi0m M1
[Samsung Galaxy Nexus] AngelsPunishment:
Tried 133 with AOKP 31 and it would not even boot. Flashed 130 back and it works again.
[Samsung Galaxy Nexus] GinoSylum:
I fixed my music problem in case anyone else runs into it. Nothing at all worked. I had to delete all my music and copy it back over from my computer and it was back to normal...
[Samsung Galaxy Nexus] mike216:
I hope I don't experience any of these problems because so far this is the best release ever! Battery life is amazing
[Samsung Galaxy Nexus] laureanop:
Franco 133 384mhz , on demand 384-1367 , no hot plug , calibrated voltages running very solid on liquid 1.25

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] masri1987:
I want Francoturtle back
[Samsung Galaxy Nexus] lunacie:
133 is the first nightly that I've had gpu issues with (noise in graphics, stuttering), had to go back to 130.
[Samsung Galaxy Nexus] vtmike:
133 is the first nightly that I've had gpu issues with (noise in graphics, stuttering), had to go back to 130.

Same situation for me.
[Samsung Galaxy Nexus] azsl1326:
Agreed. Love francoturtle. I got great battery life with it.
[Samsung Galaxy Nexus] mike216:
ondemand is about the same as Franco turtle
[Samsung Galaxy Nexus] mike216:
Anyone know between ondemand or conservative will be better on battery? There both really good but for some odd reason conservative feels quicker. I know ondemand should be faster but this conservative governor is amazing!
[Samsung Galaxy Nexus] RonnieRuff:
You did something wrong.. works fine here
[Samsung Galaxy Nexus] mike216:
This is the only kernel that gets a solid 60 fps. It scores very high on benchmarks also. Its strange because there are many kernels that also have 384 gpu but none of the others get that high FPS. Not that benchmarks matter but its nice for bragging rites ;)
[Samsung Galaxy Nexus] fclifton:
I have something strange. Running nightly 133, my phone will not go into vibrate mode. If I long press the power button, the stock menu comes up, I select the vibrate mode, that icon highlights, but the status bar icon is the speaker with a line through it. And the phone acts muted. I went back to M2 and the vibrate works fine again. I only just noticed this, but it is possible it started before 133. My ROM is IMM30B.
[Samsung Galaxy Nexus] mike216:
That's odd because everything is working fine. Just turned on my vibrate to test for you and its working fine. Try deleting the old version and download 133 and flash again. Wipe cache and dalvik cache before flashing. I'm loving this build!
[Samsung Galaxy Nexus] fclifton:
Did that, now vibrate is working with 133. Gotta love this stuff :confused:

Thanks!
[Samsung Galaxy Nexus] mike216:
Glad its working for you. Sometimes wacky stuff happens. I always reboot after the flash if not two reboots. That's a good way to get rid of lag if you experience any
[Samsung Galaxy Nexus] formula84:
I think this is just turning off smart reflex. You can already do that with his app.
[Samsung Galaxy Nexus] danman7:
What is this Signal Bug? I have apparently missed any mention of it.
[Samsung Galaxy Nexus] igorr35:
Just bought Franco updater on the market, nifty app.
[Samsung Galaxy Nexus] hawkye:
Same as disabling SmartReflex in the app. I have that pesky bug so I am trying out disabling SR to see if it helps. So far so good!
[Samsung Galaxy Nexus] mike216:
Hey Franco can I get 133 without ezekeels color control so I can use super curio display control?
[Samsung Galaxy Nexus] VolcyDX:
Coming from Milestone2 of your kernel to nightly 133. Did a Dalvick wipe and battery stats wipe. Maybe this is normal but I thought I was getting better battery life during sleep. It looks like the phone wasn't awake for most of the night, I thought I was getting better battery life on milestone 2 while phone was sleeping. Noapps appear to be using an abnormal amount of battery.
[Samsung Galaxy Nexus] spinkick:
wiping battery stats does nothing for you. Google has even said so.
[Samsung Galaxy Nexus] kingoanklebreakn:
It might not improve battery life but I've had times where no matter how many times I did battery pulls I couldn't get past the Google logo then after wiping battery stats it would start though.
[Samsung Galaxy Nexus] TEK112:
Are you sure the battery stats wipe wasn't in conjunction with a Dalvik or cache wipe? It makes no sense that the battery stat file would prevent a phone from booting.
[Samsung Galaxy Nexus] kingoanklebreakn:
Positive. It's the only thing that would fix it and it's happened multiple times. It didn't really make any sense to me either. I tried wiping Dalvik and cache and it didn't help. I have multiple batteries though and it would usually happen right after switching them out.
[Samsung Galaxy Nexus] spinkick:
Maybe the battery stats file was corrupted? Thats the only thing I can think of.

So weird.
[Samsung Galaxy Nexus] kingoanklebreakn:
Yeah, who knows. I was just glad I didn't have to wipe anything.
[Samsung Galaxy Nexus] axne1:
I tried the newest again and she's a runner. I hope it stays this great! Gpu 512

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] irvine32:
+1
[Samsung Galaxy Nexus] tu3218:
Just bought francos app and I've been running the nightly 512mhz gpu. Ran great but battery life was pretty weak compared to M2. Would running the 384mhz help battery at all? There are many settings in the app and I'm trying to decide what's best to alter. I also had the hotplug enabled.
[Samsung Galaxy Nexus] wayneb02:
If you constantly turn your screen on and off hot plug will probably do more harm than good...just a thought
[Samsung Galaxy Nexus] tu3218:
Yeah it varies but I do have a tendency to tinker with my phone a lot. I don't remember what kernel it was, but are Franco's kernel undervolted by default? I don't want to go to low but would like to try that again. I'm not sure what the stock voltages are so I don't know how the voltages under settings compare.
[Samsung Galaxy Nexus] shimmishim:
So is the nightly one better than milestone 2? I tried milestone 2 and moved away from it after seeing how it sucked my battery dry after half a day (coming from Imoseyen 2.8). The culprit was the "android OS." I've never seen the battery usage for it so high before!
[Samsung Galaxy Nexus] mike216:
You'll get much lower drain on 133 because its 4.0.4! I found it to be very good on battery also running codename Android 1.6

I think the Android OS reporting on 4.0.3 kernels was inaccurate and its corrected in 4.0.4 kernels

I remember sway or tech telling me about it just being a bug in the reporting. Sorry I forgot guys.
[Samsung Galaxy Nexus] dw3bb10:
Running AOKP 31 & just flashed M2. Im trying to enable Hotplug, but whenever I try to change the "0" to a "1" (which I assume activates hotplug", Im not able to save the file. Any suggestions?
[Samsung Galaxy Nexus] axne1:
I agree with mike that was a problem in 4.0 .3. The o s is fixed now. That's strange always got great battery with m 2

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
I would love to see this kernel be made compatible with supercurios's Display Expert.

That sucks. Seems like an option to "enable hotplug after X minutes of screen off time" would fix this.
[Samsung Galaxy Nexus] Gahh Its Lee:
It will be with the next release.
[Samsung Galaxy Nexus] laureanop:
Because the error is in the reporting of the os battery consumption. Overall battery life is about the same in 4.0.4 kernels

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] axne1:
I have to disagree. After upgrading to

.4 my battery was a lot better. The phone wouldn't deep sleep

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jaenizzo:
How do I set up my setcpu app to have to best battery life please help
[Samsung Galaxy Nexus] spinkick:
First. Stop using set cpu. Then install Francois app. Use defaults and there you go. 90 percent optimized just by doing that
[Samsung Galaxy Nexus] jaenizzo:
Franco paid app that's what u talking about right?
[Samsung Galaxy Nexus] jaenizzo:
Spinkick Can u give me the link to the app thanks
[Samsung Galaxy Nexus] TEK112:
You need to reboot into recovery and wipe cache and dalvik. The phone will sleep again.
[Samsung Galaxy Nexus] andrew53517:
It's in the market. Just type Franco kernel or something like that.

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] jaenizzo:
Not to keep sounding like such a noob but I just bought Franco app from the market so now what do I do to have great battery life I'm running aokp build 31 with 130 nightly kernal please help thanks