yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Piccles:
I am trying to go back to the default Governor settings (and start from scratch) but it stays the same after i have cleared app data & cache.

Should I just uninstall > reinstall FKU?
[Samsung Galaxy Nexus] Schneewitzchen:
unceck both, set cpu settings and set governor control on boot, then reboot and all settings are reverted back to stock franco's
[Samsung Galaxy Nexus] CaspaTheGhost:
And like I said on G+, I'm with you all the way Franco!

£279 for the 16GB is just too good a price, can't see any reason not to sell the Gnex and get one. At 'normal' smartphone prices of £500 I wouldn't bite, but they have got it at a sweet spot I think, its the impulsive buy price range.

I'm with Yellowdie on this.

Firstly I'm in the UK so LTE has just been released today, one network and stupid capped tariffs. Even if it was prevalent I don't think it offers enough, great speeds only where you have coverage, but offset by massive battery drain.

Use WiFi at work and home, out and about 3G/HSPA+ is perfectly adequate.

Just ordered a GiffGaff sim for personal use (use a work line in my Gnex but looks like they will be moving back to BBs shortly), £10 per month for 250 minutes and unlimited texts and data is absolutely cracking value.

298 is running well so far, had a SOD just after auto flashing it but none since. Running it fully stock at the moment and performance is good. To early to judge battery life.

Don't know about anyone else, but I'm really excited about the Nexus 4! Birthday is next week so definitely buying it as a present to myself!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
Have you disabled SR with UV? Also what "Governol Control" settings are you using?
[Samsung Galaxy Nexus] Piccles:
Danke :D
[Samsung Galaxy Nexus] Schneewitzchen:
Bitte :D
[Samsung Galaxy Nexus] Tommy_FIN:
With r298 charging stops at 99%. R295 didn't have this problem. Battery life extender is set to 100.

No big deal. Just wanted to share.
[Samsung Galaxy Nexus] chugger93:
I'm getting ridiculous battery life on 298. Out of all the franco' kernels (nightlies) etc that I've flashed (pretty much every one for the past 2 months) this is the only one that I've exceeded over 2 hours on screen time. with still 43% left! That's insane for my phone. That means for the first time, I could reach close to 3 hours which has never been done in history!!

God bless 298!!!!!!!!!!!!
[Samsung Galaxy Nexus] nuwan32:
I'd say it's better to have a lower input, but your choice. Try it out and see what you like best
[Samsung Galaxy Nexus] stellaryt:
Have you tried to reboot when you saw it stopped at 99%? This happened sometimes here,but after reboot it shows 100.
[Samsung Galaxy Nexus] JBNex:
Here are my new undervolted:are they reasonable
[Samsung Galaxy Nexus] whitedragonz83:
I can't speak for most of the settings as I leave SR in charge, but for 192 I can do 725 uv. You could probably easily do 750 safely.
[Samsung Galaxy Nexus] aimcr7:
You can try 192MHz @ 725mV, if it caused freeze try 750mV.

Here is mine

Running for 4hours now, No reboot, freeze, whatsoever. Stable as a rock :p

And SR was disabled
[Samsung Galaxy Nexus] WarByte:
Noticed this too, thought it was me. I plugged it again and it finished charging to 100% :) kernel is too awesome to worry about it.
[Samsung Galaxy Nexus] bar_rodoy:
With r298 the battery is way better and the phone runs a lot better. Very smooth.
[Samsung Galaxy Nexus] loudaccord:
Just curious, why is your 384mhz voltage higher than 537mhz?
[Samsung Galaxy Nexus] aimcr7:
I dont know, just lower it all -150mV then i see it was lower than 384, first i want to upper it but i thought just give it a go, and no freeze so far, no lag or anything. I am curious too with my settings :p

Just 192 & 384 which i set it manually, 192 i always set it to 725 and 384 i lower it 5 or 15mV lower.
[Samsung Galaxy Nexus] a5pe4:
Do you have to disable smart reflex if you under volt?
[Samsung Galaxy Nexus] Sik-1:
384-1420max, dyninteractive, deadline, Sr-off

View attachment 1443150

Extremely stable since last night, battery test today:D
[Samsung Galaxy Nexus] osm0sis:
I leave SR on then selectively UV the higher frequencies which it doesn't handle (1420 and above), and UV 384 and 192 to below 830mV so that they are taken out of SR's control for improved idle drain at the lower frequencies.

And yes, Franco's new default tunables under Governor Control.
[Samsung Galaxy Nexus] nuwan32:
Wow... That's amazing. For sine reason I'm finding I can uv more on this release.. weird I haven't tried pushing it but now I definitely will :P
[Samsung Galaxy Nexus] Sik-1:
I didn't think I could either until I was playing around with samurai kernel, then r295 and now I'm stuck with these uv's on r298 pretty sweet huh, but these may only work on my phone as our hardware handles different limits
[Samsung Galaxy Nexus] mariachi202:
Yes.
[Samsung Galaxy Nexus] gianton:
I noticed that leaving SR on with your UV settings, after a reboot I have to re-apply them they don't stick.

Could you please upload a screenshot of the Governor Control settings?
[Samsung Galaxy Nexus] franciscofranco:
Voltage settings never stick, I think I already posted this thousands of times :p
[Samsung Galaxy Nexus] BigBake88:
And it states it right in the app as well:) No excuses! Lol
[Samsung Galaxy Nexus] gianton:
Sorry my bad.
[Samsung Galaxy Nexus] timbck2:
Found a minor bug in the app... If you're using the Holo Light theme, the text in the Battery Life Extender numeric entry field is unreadable because it's white on white.
[Samsung Galaxy Nexus] gm007:
Bug in your theme not the app:p
[Samsung Galaxy Nexus] osm0sis:
@gianton: Yeah SR has nothing to do with that, that's just Franco's safety measure for all UVing, regardless of SR setting. :) Franco's default governor tunables are easily returned to by unchecking the set on boot, and then rebooting. If I recall correctly they're 60k/65/45k/15k. There is an init.d script solution for that to set and apply UV on boot but I'm always a little iffy about posting it because an average user with unstable voltages could get stuck in a bootloop that way.

You can find it by searching the thread for "init.d voltages" though (look for my post). You'll need to modify that command for the new extra 537MHz step in the middle. Just manually reapply them for a few days (or weeks!) to make sure they're stable first. And if you don't follow that advice and anything goes wrong, well, you were warned. ;)

@BigBake88: Hey! So what's the story on speedbumps and microlags in web browsing for you on r298? I've been interested to hear from you and the others reporting those issues before to see how it matches up with my experience.
[Samsung Galaxy Nexus] willl03:
Flashed r298, went to bed with 100% battery and woke up with 82% 7 hours later. Probably not really kernel related, had full time BTLowPower wakelock

Guess it's that girl Macbook Pro BT trolling my Android
[Samsung Galaxy Nexus] dominatore22:
Here is my actual score with r298 undervolted kernel ;) not bad..
[Samsung Galaxy Nexus] gianton:
Thanks, I'll manually re-apply them and check if they make a difference in battery life. :good:
[Samsung Galaxy Nexus] yellowdie:
Hey guys, unless you really, really know that you know that you know how Smart Reflex and undervolting works (like osm0sis), I highly, highly recommend not touching the voltages or SR. Just leave it all stock. Don't even look. The numbers you see there are not the actual voltages that are running when you phone is using that clockspeed, it is the

highest

that SR will be allowed to go, but it is not the

lowest

it can go. So just because 384's "listed voltage" is higher than 537's, does not mean that 384 uses more voltage. Major misconception.

If you know what you are doing then go for it, but if you don't or you aren't sure but you really want to try it, then the 192MHz slot is the only one that you should mess with. Try lowering it to 750mV if you want to "undervolt." But do not disable SR. SR should stay on all the time. SR can only go down to 830mv, so when you manually lower a voltage to less than that, then SR stops controlling that clockspeed spot. So leave SR on, but it will ignore 192MHz @ 750mV.

And remember, Franco's app will never set the custom voltages after a reboot; doing that is what leads to horrible bootloops that are hard to recover from. So every time you reboot, you need to go apply the voltages again.

:) :D :laugh: :good:

-Sent from my phone because my work's Internet is down because of Sandy. Lol
[Samsung Galaxy Nexus] atiartstudio:
Franko default and my Google latitude and my news are in love battery and performance.... A+
[Samsung Galaxy Nexus] shawnaye:
Is anyone even getting any usage on the new intermediate frequency?

FYI, under my oc/uv tab. The 537mhz is at 900mv. And that's odd considering the frequency before and after it is higher than that voltage.
[Samsung Galaxy Nexus] osm0sis:
I answered that a few pages back. The new 537MHz step isn't controlled by SR, so you're not looking at a normal nominal voltage, you're looking at the final, low, stable, voltage as Franco has personally calibrated it. He likely did this because letting SR calibrate it would make it too low and unstable.
[Samsung Galaxy Nexus] bat0nas:
:D:D

View attachment 1443404

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
Hmm.. But the frequency isn't being touched more frequently. Haha. Stock governor settings Btw. Re flashed with option unticked as well.
[Samsung Galaxy Nexus] six_dfx:
This is your wifi router (or most probably a public wifi router) that's hijacking your http requests to ask you for authentication.
[Samsung Galaxy Nexus] yellowdie:
osm0sis is right. But the reason you're not seeing it used much is because our tweaked settings don't leave much room for the middle ground. Usually your phone jumps to input_boost_freq when you touch the screen and it jumps to hispeed_load when it's being used. When it's not being used, it jumps down to the bottom level. Therefore, the mid range is not used as much. In my case, I set 537 as my input_boost_freq and my max screen off so it gets used a lot, but for me 384 is rarely used now. :)
[Samsung Galaxy Nexus] whitedragonz83:
I mentioned it a few pages back, but the frequency just below the hispeed_load seems to not get much use, at least in this case and this example: Setting hispeed_load to ~1305 I saw almost zero use of 1228. Just the way it works I guess. I since have set my off screen to 537 and find it gets more use like that, at least with the rest of the settings remaining default.
[Samsung Galaxy Nexus] fayezkhan555:
Hi all, I tried r98 both 384gpu and 512gpu on AOKP jb milestone 1 but stuck on boot screen of Google. This was the first time happened to me on flashing a kernel. One of my AOKP colleague is fine with it but I dono why this happened to me?? Anyone with any solution??
[Samsung Galaxy Nexus] BigBake88:
@Osmosis For me personally I feel browser scrolling is a little worse to be honest. I have a lot of speedbumps and microlag. I'm also getting lock ups as well. Instagram is freezing for a few seconds as well when scrolling. Double tapping for me in browsing locks up for a few seconds as well. Franco I love your kernel, please don't tale it as me bashing your work. Just trying to give some honest feedback and I was not experiencing this in previous versions. :cowboy:
[Samsung Galaxy Nexus] nuwan32:
Hey guys I think there might be something wrong with the new version of the app or kernel, because I can under volt like crazy now, it's not normal lol. Look at my voltage chart I can probably go even lower. I restarted and everything but it works, it's definitely to good to be true.

Btw I'm only using 192 - 729
[Samsung Galaxy Nexus] franciscofranco:
I just undervolted 192Mhz step to 600mV and instant freeze.

I have no idea, its butter smooth to me.
[Samsung Galaxy Nexus] osm0sis:
Really! It did seem worse with min 192MHz but I've basically decided 192MHz is a lost cause with 384GPU. That said, it seems marginally improved to me with min 384MHz, but I'm also using bfq scheduler to smooth it a little more. I don't have to resort to making hispeed_freq 1036 anymore, so that's a minor improvement in my eyes.
[Samsung Galaxy Nexus] yellowdie:
Okay, so lets assume you have Google's stock for everything (100/50/60/20). Your timer_rate at 20000; that means your CPU can only change voltages every 20 milliseconds. So you pick up your phone and turn the screen on, it jumps to your input_boost_freq, then waits 20ms before dropping to the bottom level (because you haven't started doing anything yet). You then open your email app and the cpu load goes up a little, so the clockspeed jumps up again to input_boost_freq, then drops down. Then you open your sms, browser, and XDA and the cpu jumps to 50% load; with go_hispeed_load at 50% (Google default), that means as soon as your phone hits that mark, you're going to be at hispeed_freq. Then in another 100ms (above_hispeed_dealy default), if the load has gone higher, then the clockspeed goes higher. So factoring all that in, in order to hit the freq below hispeed_freq, you would have to very slowly open apps in such a way that you made the cpu slowly climb (like a few % every 20ms) to force it to slowly go up the chain of steps. Because once you hit go_hispeed_load, then you're at hispeed_freq. There really isn't much of a chance that the midrange steps (especially the one before hispeed_freq) will get used much in your case.

In my case, input_boost_freq is the step right before hispeed_freq, so it does get used a lot. But if you have your hispeed_freq really high, then you're going to be using much higher freqs more often and your midrange will feel abandoned and cry.
[Samsung Galaxy Nexus] dracon6ai:
Heads up. On r298 the PGM2 app no longer works. Missing my slide to wake and slide to lock.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] zephiK:
r298 + PGM2 works fine for me. Update to SuperSU and reopen app. Turn PGM off then back on, then reboot.
[Samsung Galaxy Nexus] whitedragonz83:
Great explanation. Wonder why Franco defaults the opposite you do with hispeed_freq being higher then input_freq. Anyways, hopefully that helps explain also to people wondering why the new frequency isn't being used much/at all.
[Samsung Galaxy Nexus] franciscofranco:
I'm currently testing yellowdie's perspective of the tunables, instead of 1036 input_boost I decreased it to 537. So far so good, don't notice a single difference performance wise, which is good.
[Samsung Galaxy Nexus] sk8oldschool74:
What is slide to wake slide to lock? Is that like volume wake? If so we're can I get it???
[Samsung Galaxy Nexus] osm0sis:
Personally I'd maybe reverse them so input_boost = 729 and hispeed_freq = 1036, but I wouldn't want to decrease them.
[Samsung Galaxy Nexus] HuMpS 97 DoHc:
works fine for me too. After flashing a new kernel I had to open the program up and start it up and set it to run on boot.
[Samsung Galaxy Nexus] nuwan32:
Ok Nvm it does crashes but it just takes longer
[Samsung Galaxy Nexus] Piccles:
Works fine for me aswell.

P.s. I love that app!
[Samsung Galaxy Nexus] mariachi202:
Search the play store and welcome yourself to a brave new buttonless world!
[Samsung Galaxy Nexus] dracon6ai:
Already have SuperSU version 0.97. Tried uninstalling PGM, rebooting, reinstalling and still no go. Going to try reinstalling r298 to see what happens.

Edit: reinstalled kernel and it's working good now. Damn voodoo bugs

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] yellowdie:
Sweet! Thanks, Franco! And Os, I am still on the fence about 537, but so far I like it. What you just said is the setup I've been running since Boss Man blessed us with the awesome input_boost_freq; but now that we have 537, I'm just testing it. I'd love to run 537/729 if the performance holds up, and so far it is. If it doesn't then I'll go back to 729/1036. But because 1036 is my max, I don't really want hispeed_freq at my max (then above_hispeed_delay is a totally pointless variable), so I may try 729/729 as well. I may also try 1228 as my max again, but I just don't feel like I need it. lol

On a side note, I love how I have a 1.2GHz proc that I can OC to 1.7GHz (stable), but I run it at 1.0GHz; all while drooling over a new 1.7GHz Exynos 5 that can probably OC to 2.0GHz at least, but chances are I'd run it at 1.5GHz. lol. Just strikes me as funny.

SAD NOTE: :( :( :( :( I totally just dropped a piece of pizza top down on the dirty floor. :( :( :( :( Gah! That makes even a great day sad! :( :( :( :( (lol)
[Samsung Galaxy Nexus] BigBake88:
Yellow, can you post your tunable again please?
[Samsung Galaxy Nexus] osm0sis:
@yellowdie: Hahah. Yeah definitely for your setup (max 1036), 729 hispeed/537 input makes sense, I'm just saying for max 1228+ and knowing not all phones are made the same (as we're seeing with the jitteriness and "speedbumps" in browser for some at lower freqs, myself included) I wouldn't want to push the defaults down too much, but the reversal idea could definitely work.

I'm also rocking a screen-off max of 537 now. Hopefully won't interfere with the race-to-idle but still save us some juice. :good:

Also :laugh: I'm already dreaming of buying a N4 from the Play Store; price is right. We'll see how much longer I can put up with my ****ty Canadian Nexus screen. ;)
[Samsung Galaxy Nexus] yellowdie:
Stock r298 settings, with input_boost_freq at 537 and hispeed_freq at 729. 192-1036, with 537 as screen off max.
[Samsung Galaxy Nexus] franciscofranco:
Thats exactly what I'm running at the moment but with 1228 as max freq.
[Samsung Galaxy Nexus] yellowdie:
True. But I wonder if the speedbumps are only because of 192 min. Do you notice any difference in the lag with input_boost at 729 vs 537? My bet would be it would have the same lag, but 537 would still be as smooth as 729 in the non-laggy areas. Just my thoughts.

And yeah.... I'm torn. I wasn't impressed with the N4 at first, but its growing on me. The IPS screen, with a quadcore and 2GB of RAM.... Nice. :) lol. But I just got my Gnex in July, so the chance of me getting an N4 is very slim. lol. But the N10! Now THAT I want!! (Just can't afford it, lol).
[Samsung Galaxy Nexus] BigBake88:
+1 going to run this for the day but keep max at 1228:highfive:
[Samsung Galaxy Nexus] osm0sis:
I'm still very happy with my 16gb N7, and the price is amazing (now more than ever with the higher models they introduced)! But that video from The Verge where they showed off the N10 and N4 really made me drool for the N4, even though I got my GN in February. :p The discoball **** on the back is kind of lame, but otherwise, pretty much what the GN should have been.
[Samsung Galaxy Nexus] franciscofranco:
Comon don't be little *******. If you can afford it without breaking your real life economies 299 dollars for the device that it is I feel that it almost free. I really can't wait to get my hands on it and use it as my main device.
[Samsung Galaxy Nexus] yellowdie:
Well, compromise goes both ways, my friend. I'm gonna bump my max to 1228 to match your exact settings. :)

lol. When I was single, $300 wouldn't have been much at all. But I just got married a year ago, and all of that changed... lol. No more wild spending for me. :) It's budgets now! ;)
[Samsung Galaxy Nexus] gianton:
I wonder what will be the prices in EU.

Got my GNex three months ago but if N4's prices are that low in EU I'll get one.
[Samsung Galaxy Nexus] timbck2:
What a coincidence, I'm running the same settings as you Franco, since early this morning! :D
[Samsung Galaxy Nexus] Astug:
I'm honestly still not understanding the actual difference between hispeed freq and input boost freq. :confused:

EDIT: Nvm, just found and read yellowdie's explanation a few pages back. Thanks!
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm using this set up now too, thanks yellowdie once again for your good patient explainations and 537 step is now being used for a decent time. Performance holding up nicely, should see battery savings soon :)

About the n4, I think it looks great but I'm not up for renewal or upgrade till next year (sept I think) so I'll probably get the next one, tempting as the n4 is, unless I come by some money but I also would like a tablet :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Empty Hand:
What's the current preference: deadline or bfq?
[Samsung Galaxy Nexus] osm0sis:
I feel like bfq has some small benefits to deadline for scrolling in menus and helps with those jitters and "speedbumps" in the browser. They're honestly both very fast and virtually the same performance wise now though.
[Samsung Galaxy Nexus] 11768:
What is the minimum value we can undervolt? I tried 400 on 384mhz but it still works? Something is not right
[Samsung Galaxy Nexus] osm0sis:
Yeah that's not right. Give it 10 minutes, it will probably die. That or you probably forgot to hit apply. :p I haven't seen anything under 675mV work for anyone (725mV for me) on 192MHz and nothing lower than 775mV worked for me on 384MHz, so I wouldn't recommend anything much lower.
[Samsung Galaxy Nexus] Wh1t3Rose:
Is this good for 80% 4G use 20% 3G use? -75 dBm. all of the media server use was YouTube!!
[Samsung Galaxy Nexus] yellowdie:
You are correct, something is not right. Read this. :)
[Samsung Galaxy Nexus] CallumMarks77:
is there an app to control this kernel...? that lets you control the cpu and haptic feedback ect...?
[Samsung Galaxy Nexus] inffy:
Shouldn't be a problem. I have used this kernel with the fitsnuglys CM9 Kang Rom previously
[Samsung Galaxy Nexus] coleburns:
Yep. got this also. Running AOKP 14 and Franco's 10. Power saver is turned off.

for now, i just set the screen to never turn off when using tunein.

For what ir's worth, i can't say it never did this before as i hadn't used the app in a long time
[Samsung Galaxy Nexus] c00king.c0w:
ok, thank you for the advice... so would you wait before bringing the phone to the service center?
[Samsung Galaxy Nexus] nic85:
with #11 conservative 700-1200

battery monitor say 29-50mA in standby..i think is too high? :confused:

sry i have no time to read all the long thread,but i think there is a good reason to have 700mhz minimum?

with 350mhz and less voltage we can obviously better mA drain in idle,but maybe with conservative it's not stable?
[Samsung Galaxy Nexus] 3c:
29-50 looks like high-drain, did you get this value after a long period of standby? considering the phone doesn't provide real value, it requires long period of standby to show real mA.

I'm at 350MHz-conservative in standby and using lower 675mV voltage (using JDKernel) and it has been stable for a week or so. Trying hotplug now as it shuts down CPU1 when not needed. All these should save even more battery! :D

Managed 3mA in standby (plane-mode) so far! :D

EDIT: Some screenshots to show the real thing ;)
[Samsung Galaxy Nexus] ro_explorer:
Some spoilers :)

While creating the GPU stock clock kernel for testing, Franco introduced a little add-on :) ... I'll not say more ... but I'll show you something:

Both phones in the pictures have bigxie's latest and franco #11 and display at maximum brightness. The one on the left is with the generic #11 while the one on the right is with the tweaked kernel.

I'll let the pictures do the talk (white - red - green - blue - gray):
[Samsung Galaxy Nexus] nic85:
i'm not talking in plane mode ;)

1h in standby isn't enough for deep sleep?
[Samsung Galaxy Nexus] Sayan1987:
Sry, probably has been already asked, but which program is what you using in your screenshot?

Thanks..
[Samsung Galaxy Nexus] ro_explorer:
It looks like "System Tuner Pro"
[Samsung Galaxy Nexus] beekay201:
+1

should have reported way earlier, didn't try later nightlies (was checking how long one charge was getting after several days - using phone just for calls/texts/very light tapatalk i got nearly 3 days)

aosp-dirty+nightly#8

songbird/stock music player. min 700mhz. deadline/interactive.

music/sound notif stuttered only when receiving text message while screen off.
[Samsung Galaxy Nexus] ChongoDroid:
I am giddy, seriously cool.

Sent from my Google phone