yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
In the OMAP kernel driver we set nominal values for the frequency steps. Those values are the starting point. Then SmartReflex kicks in and calculates a much lower value that the device can handle for each of the steps.

For example:

1228Mhz Nominal: 1250mV - Calibrated: 1050mV

When we undervolt we are changing the nominal value ONLY. So if we undervolt to 1100mV the Calibrated value will still be 1050mV what means we are still using the same voltage.

However if we undervolt to 1025mV the Calibrated value will obviously decrease to 1025mV but the chance of crashing the device will increase much more.

For 1536Mhz steps and beyond I made it so SmartReflex won't calibrate to prevent crashes so we're using the nominal values directly from the kernel.
[Samsung Galaxy Nexus] IgnorantNerd:
So if I've changed the nominal values in the undervolt settings but didn't go lower than the calibrated values then in reality it didn't have any effect on anything? Just trying to understanding this stuff
[Samsung Galaxy Nexus] cpomike13:
I've been reading these type of threads for 3 years, and still haven't seen explanation on how to undervolt. From what I've read it's the way to getting longer life on my battery. Please explain how to undervolt.

Oozed from my sick Jelly Bean Nexus Prime via tapatalk2
[Samsung Galaxy Nexus] osm0sis:
UVing is useful for improving power consumption and heat reduction, especially at higher frequencies. If you UV too much it crashes/freezes. So basically we're talking about finding the sweet spot here and SR does a great job of that for all frequencies it operates on (per franco's post above).

DO NOT UV THE SAME ACROSS THE BOARD. Different frequencies can take different levels of UVing, so adding or subtracting 25 could work for one or two but be unnecessary or unstable for others. Each frequency must be UVed separately.

Here's the reference doc I made for myself, pulled from several other peoples' posts, so all credit to them (not sure who anymore, my apologies!):

And here's some more recent information, on what to look for with GPU and IVA undervolting to know you've gone too far:

http://xdaforums.com/showpost.php?p=42835670&postcount=42344

After all that I'd like to mention that UVing isn't really necessary! SR does a spectacular job and I'm not worried too much about the higher frequencies as I only clock to 1.5 GHz (the TI OMAP 4460 chipset factory specifications - so I'm not overclocking, I'm de-underclocking ;)).

Edit. As nemotheblue pointed out, a lot of this likely came from rogersnm's extremely informative posts. So many thanks and all credit to him and anyone else I might have gotten some of this from but forgot.
[Samsung Galaxy Nexus] willl03:
Well put osm0sis
[Samsung Galaxy Nexus] franciscofranco:
You know the answer for that question if you read my post ;)
[Samsung Galaxy Nexus] dracon6ai:
Just to add to the under voting info train here's something I copied from a post way back is this very thread I believe. Just something about the POTENTIAL benefits of under voting, not guaranteeing these results. Me personally I just let SR do all the work.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] franciscofranco:
franco.Kernel updater patch

6.4

Common:

* Re-code all the download kernel functions - clean and improved code

* Re-implement the kernel download dialog information - now it shows real percentage of the file plus file sizes

* Touch events won't cancel kernel download dialogs anymore

* Some more bug fixings

If you have any issues please email me.

As usual you need to wait until Google takes care of the update push into their servers.
[Samsung Galaxy Nexus] nnnnr14:
Hey Franco I just found something odd, I was running #248 since you first uploaded but I was getting a lot of data drops. At first I shook it off but then it got more aggressive and I reverted to #246 and now I get better signal and it doesn't drop as much.. Weird.

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] drawde40599:
UV may get u like 5% better battery but by then most people are looking for a charger, don't waist your time it's been proven over and over agn that no real benefits. I've done my own tests weeks at a time and 5% was all I got, most people install a kernel screw with all the settings before they ever tested stock so there input is worthless ;)
[Samsung Galaxy Nexus] gianton:
Now it's crystal clear to me, NO more Undervolting!

Thanks for the heads up mate!!
[Samsung Galaxy Nexus] mohaimed:
i did that.not once but twice.prevoiusly i was on trinity kernel.now changed to franco.but same problem... :S
[Samsung Galaxy Nexus] Kappa Lamda:
Last 2-3 pages made it more clear. No reason to UV.SR does a great job and we have to undervolt below the calibrated SR value which increases the risk of crashing much more than the real power save we get. So no UV and for me from now on.

Besides our Super Amoled is what drains most power on our phone!
[Samsung Galaxy Nexus] DaXmax:
Thank you Franco, been using your nightlys, it's very smooth...
[Samsung Galaxy Nexus] gautam_nexus:
Take out the boot.img file from the rom Nd flash via adb

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
So with 248 overall its great, iv had more microlags than I did with 246 which was very good overall. This 'interactive' interactive is good, my battery life has been acceptable (I normally stick to lazy) and the performance is good, I find he microlags happen more after having a long time without a reboot. Overall am very happy to continue testing 248

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nemotheblue:
I believe that was the wizard known as rogersnm!

@osm0sis - O/T: I note in your sig you're running a yakju build with the new UGLH1, working well? Could I use that radio in Europe on my yakju?
[Samsung Galaxy Nexus] Langduscher:
Dunno if it's ROM or kernel related - but since it happens on both MiNCO v4 & Bamf 2.3.1, I'm going to post it here.

Every now and then my wifi cuts off, then comes back on. Where should I look for trouble shooting?

Thanks
[Samsung Galaxy Nexus] franciscofranco:
Do you have JB's radio?
[Samsung Galaxy Nexus] Langduscher:
Yes sir, LF1 :) and both ROMs radio & RIL match.
[Samsung Galaxy Nexus] chugger93:
Does anyone else have problems with the "Maximum Frequency for screen off" paramter? I leave mine at 230mhz, but most of the time when I perform a reboot or update to Franco's newest app, it always goes back to like 729. Seems like it goes back to my min CPU clock speed always.

The only way to set it again, since you can't just "set it" is to change the MIN CPU to 230mhz, then set the "max freq for screen off" to 230mhz, then go back to set the min CPU back to 729 or 384 (whichver you prefer)

So friggin odd, and its happened for as long as I can remember (month or so when I first came aboard Franco's work)

Thanks Franco for an amazing kernel and app!!
[Samsung Galaxy Nexus] The Gingerbread Man:
Reset your router

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Langduscher:
Okay, I'll try that, it's been a while since I've done that :o
[Samsung Galaxy Nexus] The Gingerbread Man:
You won't save battery doing that, just leave it at 729mhz so stuff completes faster and deep sleep begings. Its all about race to idel

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] danielvc:
Getting stellar battery life and performance with 729-1036 Lazy/smart reflex and 729 maximum screen off. And: GPS off when not needed. My phone is sleeping like a baby.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm using 230-1036 interactive and its very good also. I prefer to allow my phone to choose the speed it wants, rather than having an unesseserily high min speed which could waste battery for long tasks, like MP3 playing. My previous set up was 230 - 1036 lazy which had decent performance and amazing battery.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lippol94:
Just bought your app, Franco, and my Galaxy Nexus hasn't arrived yet :p

But all the work I see deserves to be paid, plus I know I will use your kernel. There are so many happy people with it and I love the fact you're so active on it!

Looking forward to ride my GNex with your kernel :)

I'm really interested in interactive kernel, mostly because it's the google default one, isn't it?

How is it going on performance/battery side? Are you able to drive it all day long without sacrifying anything?

Thanks in advance :)
[Samsung Galaxy Nexus] TEK112:
I would reflash the radios before resetting the router. The fact that you can connect, but it cuts out leads me to suspect your phone. If you couldn't connect, I would suspect the router.

As an aside, under wifi - advanced settings do you have the wifi set to sleep?
[Samsung Galaxy Nexus] franciscofranco:
Too bad I can't thank more than once :)

Nah interactive governor is pretty good nowadays since Google decided to work on it. Interactivity without sacrificing battery life.
[Samsung Galaxy Nexus] lippol94:
pretty good? :p

What do you recommend so? :)

Oh another doubt, does interactive handle hotplugging? But mostly, does hotplugging bring real benefits? I read a lot controversial posts about it. I'd like to get an answer from an expert :)

Thanks in advance!
[Samsung Galaxy Nexus] etche:
I commented this same issue some time ago. I'm on bigxies JB ROM and #246 kernel. The same happens with my phone and I tried it with 3 different routers. It seems as the wifi reception was better before, as if the range got smaller. And I also don't know if it's kernel related or not. As someone suggested, I tried enabling wifi pm-fast but it only seems to work when screen is off.

I tried with JB radio XXLF1 and now I'm back to UGLC1. The same happens on both radios.
[Samsung Galaxy Nexus] Langduscher:
Reset my router and all seems good...

Why reflash radio? Since it's on a partition that doesn't get wiped..?

Wifi is always on, btw.

Thx for your response :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Interactive is working well indeed, I'm at 8 hours off charger, 1 hour 40 mins screen on time, 50% battery left. I have been at work so disable sync and been using 2g mostly.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
Sometimes radios need to be reflashed. From my experience, reflashing the radios clears up 90% of radio related issues and reflashing the kernel can clear up radio issues as well. Sometimes a flash doesn't take well. Perhaps a bad download or an incomplete leak? It happens. Not all people verify the MD5 and sometimes they verify the MD5 before the copy the file over to their phone and not afterwards. You would be surprised with the difference it can make.
[Samsung Galaxy Nexus] Langduscher:
Well I'll try reflashing the LF1 JB radio. The wifi disconnection persists :eek:

It's only happened the last couple of days though... :rolleyes: ..before I had no problems.

Thanks for your tip on checking md5 after it's on my phone btw ;) always did that before transferring files to my phone. Doesn't affect radio basebands ad much for me, since I flash these in fastboot.

Again thanks for bearing with me :good:
[Samsung Galaxy Nexus] TEK112:
Try this:

1 - Download and reflash the JB bootloader (just because it is good to have)

2 - Download and reflash the radios (update.zip) from a different source

3 - Wipe Franco's app data

a - Download the latest kernel - not autoflash

b - Reboot into recovery and wipe cache/dalvik

c - Flash Franco's latest

It may or may not work, but it creates a fresh playing for the radios. Also, don't forget that the ROM can affect Radio performance through the RIL (radio interface layer). So, don't rule out the ROM as a last possibility.
[Samsung Galaxy Nexus] Kurre:
Hi Franco. Sorry to re-post this same thing, but I didn't see any response on this and I find this one so interesting :D

I won't re-post this again after this, because I don't want to clutter/mess up this thread :p

Here is some other links too:

http://lwn.net/Articles/509829/

Patch by faux123

http://permalink.gmane.org/gmane.linux.ports.arm.msm/2911

It seems to giving somewhat a nice punch to the read io performance :)

PS. sorry if I have missed your post about this matter..I have been on summerholiday over a week now ;)
[Samsung Galaxy Nexus] Langduscher:
Reflashing the bootloader eh? Even when I'm already on LC03 (JB)?

I used to wipe cache + dalvik and then flash Francisco's kernel - but ever since one can autoflash it I've been doing that :angel:

May be you're right and a fresh install from scratch is in order. Can't be bad once in a while :)

As for the ROM's RIL; I never had this wifi-disconnetion-for-a-second-thing, it's something that happens past few days... started on MiNCO v4 (one would think that RIL would match allright ;)) and now also on Bamf 2.3.1 (Bamf is a stable ROM too).

Again, I'll try a clean and fresh install of everything.

Cheers
[Samsung Galaxy Nexus] TEK112:
Make a backup in case this doesn't work, so you can go right back to a stable already setup ROM.
[Samsung Galaxy Nexus] Langduscher:
:D yea I got me a couple of those Nandroids :)
[Samsung Galaxy Nexus] prembox:
Why would you flash radio(s) to fix WiFi issues, especially when the WiFi drivers are present in the Kernel and NOT the Radio???

Again, Why would you flash radio(s) to fix the WiFi issue?

Edit: WiFi issue with G-Nex is widely known and I guess we need to live with it for some time to come. I've posted my findings from a small experiment some time back...here
[Samsung Galaxy Nexus] TEK112:
Trust me, I don't pretend to understand linux on a hardware interface level, but from my experience and issues posted online, reflashing the radio has helped with WiFi. I you feel as though this is wrong, perhaps you can explain why one wouldn't affect the other. I am sure we would all appreciate the knowledge. A quick google search shows this:

http://www.theverge.com/2012/6/29/3...illa-stock-jelly-bean-on-gsm-galaxy-nexus-now

More especially foot note 4:

XXLA2 radio works fine but in some rare cases, if you are experiencing poor WIFI signals on Jelly Bean after following these steps or if your WIFI is not responsive although remains connected (grey icon, connected) after extended display sleep time or standby, flash the latest radio ROM (XXLF1) (Link) that came bundled with Jelly Bean though CWM touch.

Like I said, on paper they would not seem related, but many have had issues that were cleared up by reflashing.
[Samsung Galaxy Nexus] prembox:
No offense mate.....I'm tellin ya....Radios got nothing to do with WiFi signal performance of the device....in that very footnote you pointed me to it clearly mentions that "XXLA2 radio works fine but in some

rare

cases..." ...its a rare case as in most likelihood a Placebo effect it could've been.....I rest my case here but due thanks for the exchange of info!
[Samsung Galaxy Nexus] osm0sis:
Yes! rogersnm is where I probably lifted the majority of the UV directions, and he keeps that table updated in his sig. Brilliant work on his part.

As for the radio, best radio I've used. I've been using XXLF1 quite happily and felt XXLA2 and UGLC1 were decent too, but UGLH1 feels faster and I'm getting improved signal places I didn't before. That's PEI, Canada though and UG radios are *supposed* to be for North America and XX for Europe, but that doesn't mean that it wouldn't improve signal for you in Europe. People have had similar results in other parts of the world. No harm in testing it out just remember to flash the corresponding RIL. Give it a shot!

Wi-Fi PM_Fast IS only effective with screen off; the blurb in the App should probably be clarified. It keeps the wifi from entering it's screen-off low-power state.

The wifi signal problem is more of an issue with JB in general: Wifi problem Jelly bean yakju JRO03C.

First thing to do is to go into Wi-Fi Advanced settings and disable "Avoid poor connections," that alone makes it a lot less likely to drop now that the signal seems reduced. Between that and using franco 246/248+ the JB Wi-Fi problems seem almost resolved, and I even have "Keep Wi-Fi on during sleep" set to "Only when plugged in" to avoid wlan_rx_wake wakelocks (lets my phone deep sleep longer but makes wifi more up and down when it does wake). It reconnects quickly when I turn on the screen, generally before I even get the chance to open a browser or the Play Store, so it's still seamless to me.
[Samsung Galaxy Nexus] wizayne:
Anybody ever seen this before?

Latest Franco 512gpu flashed in Franco app oc to 1.6 with smart reflex on..Anyway not a bug report I just thought this was pretty crazy to see..its been at the same level for a few hours and it is NOT on the charger.. battery reported 3700mv when screenshot was taken..

Anybody else ever see this? BTW its a standard OEM battery with maybe 30 cycles on it got it a few weeks ago..I have 4 batteries I swap out daily

Edit: a reboot shot it back to normal..it went from fully charged to 4% in that picture but after reboot it was actually at ~%50
[Samsung Galaxy Nexus] osm0sis:
I'm guessing your battery stats might have gotten borked, maybe from you swapping batteries. It flatlined because it wasn't actually at 4%, and assumed it was charging to account for the difference, the big question is whether it would have gone back to normal once it actually reached that point. Either way, the battery stats fix themselves after a discharge so you should be okay. :)
[Samsung Galaxy Nexus] TEK112:
This^

Swapping batteries can cause this kind of behavior.
[Samsung Galaxy Nexus] drawde40599:
log

@Franco I've had a few reboots since yesterday using buikd 248, 512 gpu, i am on a AOKP nightly so I don't expect any diag or anything else ,I don't no if kernel related or ROM related but here is a log maybe something in there is useful if kernel related http://db.tt/j1zloBX4
[Samsung Galaxy Nexus] osm0sis:
What are you clock settings? Or try switching to 384GPU and see if they persist. Could be your ROM of course.
[Samsung Galaxy Nexus] GrenW:
Had reboots on AOKP myself. They seem to have stopped since I flashed the 2nd Sept build. Worth a try?

xda premium app on AOKP'd GNex
[Samsung Galaxy Nexus] drawde40599:
I think it is aokp that's y I don't expect help. .. I'm running sept 3 build one newer than u
[Samsung Galaxy Nexus] foueddyf:
I also have the wifi issue you guys have been mentioning. Had it ever since I bought the phone on release day (Verizon).

Then, Franco's #246 kernel got released and 90% of my wifi connections now stick. And even if the connectivity gets lost, it comes back real fast.

But with #248, my connectivity goes berserk again (flashed twice) . That is why I'm back to #246.

I guess that new wifi commit Franco introduced in #248 doesn't play well with my phone :(
[Samsung Galaxy Nexus] drawde40599:
every phone is different but I'm actually having no wifi issues at all my wifi and speed of internet have never felt this fast
[Samsung Galaxy Nexus] franciscofranco:
My wifi is perfect.
[Samsung Galaxy Nexus] RoscoeDpG:
i always am so happy to not have any probs like this *Knocks on wood* so far 240 been best on battery for me but the newest nightly with the new flex Gov. is running great
[Samsung Galaxy Nexus] osm0sis:
Wifi with both 246 and 248 was an improvement for me over all JB builds before.. couldn't really tell much difference between the two during my testing periods for each though.
[Samsung Galaxy Nexus] cgrimes5:
Recommendations

Hello

I purchase the Franco App, and would greatly appreciate any suggestions on which Kernel I should use, still pretty new to all this. Looking for the best Kernel and the best settings for battery life, and I have heard nothing but good things about Franco in all my research!

Thanks in Advance
[Samsung Galaxy Nexus] osm0sis:
Best thing is to try. Lazy is supposedly best for battery life but you may find it lags/less responsive; best balance is either interactive or ondemand. Start with r246 or r248, they're stable and give you an idea for the differences between the governors as you try them. Start with the 512GPU version and if you see weird video glitches then you should fall back to 384GPU and see if they go away, since not all devices can handle 512.
[Samsung Galaxy Nexus] Savant:
I would back up stock kernel from the app and try out the different nightly kernel 384-512 GPU because they might act differently on your phone.
[Samsung Galaxy Nexus] cgrimes5:
Recommendations

Thanks for the quick response, Do I need any special settings or just run it as Franco has it set?
[Samsung Galaxy Nexus] Wynnded:
Exactly! Until you feel comfortable experimenting.
[Samsung Galaxy Nexus] drawde40599:
Just run it 100% stock Franco spent 100's of hours tweaking it for us, there is no need to do anything, just run it as is, u will not get it working better by tweaking even though some here think they have ;)
[Samsung Galaxy Nexus] IAmAN00bie:
Sorry, but that isn't true. Franco's settings are intended to work on 100% of devices with 100% stability. His default settings are by no means the "best" your phone can do, simply because every phone is different. You can tweak the governor settings, color settings, overclock/underclock, etc. all to match YOUR needs and YOUR preferences.
[Samsung Galaxy Nexus] Exostenza:
This.

I run overclocked to suit my needs and have completely different colour setting as my screen is very warm and I like it cool. Also I have a few other things changed. I'd assume most people at least have slightly different settings than stock to suit their needs.
[Samsung Galaxy Nexus] cgrimes5:
I'm new to all this especially Kernels and Settings. Now I have found some information on colors that I like, so I have change those setting, but as far as the governor setting overclock/underclock I will have to research a little more, that is why I asked about the setting to get me started with the best battery.

Galaxy Nexus

Codename Android 3 nightly 09032012

Dark Jelly Theme

Franco r248 512
[Samsung Galaxy Nexus] fatappel:
Running r248 with latest official aokp nightly (I know haters) and what I've found is the ability to change the default scheduler from bfq to deadline under aokp rom control - performance settings. This option is not available in the franco app which I have as well. Really liking the performance and especially the battery life I'm getting out of deadline. Just an informative heads up for those who would like to give it a try.
[Samsung Galaxy Nexus] TEK112:
I think the point being made was that people end up doing more harm than good when they tweak Franco's stock values. Especially if someone is asking that question it makes sense to tell them to stick with stock.

Now, that's not to say the settings can't be tweaked to make a "better" running device, but I would wager that more than half of those messing with their settings are getting worse performance/battery/stability than stock.
[Samsung Galaxy Nexus] prembox:
+10
[Samsung Galaxy Nexus] sway40:
Just gotta say battery is awesome on 248.

Sent from my paranoid Nexus 7
[Samsung Galaxy Nexus] drawde40599:
EXACTLY!! And they don't even no it cause they didn't give stock any actual use
[Samsung Galaxy Nexus] Pkt_Lnt:
I can not imagine that an I/O scheduler will directly effect battery life.

[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs

http://xdaforums.com/showthread.php?t=1369817

http://xdaforums.com/showpost.php?p=22134559&postcount=4
[Samsung Galaxy Nexus] gianton:
For color settings try this (the best for my eyes):

Color Multipliers R178 G169 B200

RGB Gamma R5 G5 B0

Disable CAB enabled

Trinity contrast -10

OMAP4 Gamma 1.2
[Samsung Galaxy Nexus] meanwhile:
I'm using

132,132,196

Rgb 4,0,0

Trinity -8

Omap 1.0

Sent from microwave
[Samsung Galaxy Nexus] J-Hop2o6:
140, 130, 200

-7, 0, 7

OMAP 1.2

Trinity 0

CAB disabled
[Samsung Galaxy Nexus] Mrc527:
I've recompiled the last (245) version, with CIFS and RTL8187 support! :p

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope you enjoy it.

Bye!

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
Thats exactly what an IO scheduler does.