yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
He is yeah, came from sony ericcson w995 (red push slide walk man phone lol) and I think he's over whelmed already tbh. Hopefully he'll get curious like you say and I'll convert him to the dark side :cool:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] splus:
Franco, I'm guessing that having many frequencies in kernel is not a good thing because CPU has to switch between them a lot whenever there's a higher CPU load, and then back down.

Would it be good then to get rid of some more frequencies? 1305 MHz seems quite close to 1228 and to 1420, so probably no need for it. Same about 1536 slot, it's quite close to 1612 MHz.

So we can have 384, 729, 1036, 1228, 1420, 1612, 1708 and 1804. (Have few more higher slots even though they are close to each other because some devices can not run 1804 without occasional reboot.)
[Samsung Galaxy Nexus] Myster:
I updated on latest version of Franco Kernel Updater.

Fsync setting will not stick after reboot
[Samsung Galaxy Nexus] derPianist:
Can someone explane what f sync exactly does? The explanation in the app is for me not clear enough!

Thank you.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
Games work great on 217. In stock even temple run lags. :D Absolutely no lag in your kernel. :) Thanks a lot for this kernel.
[Samsung Galaxy Nexus] 15israellai:
I think I saw it long long time ago in this thread.

If fsync is on, the I/O performance is poorer but the chance memory corruption (or something like that) after a reboot (you know, the kind when your phone can't handle the frequency) is lower.

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] Tommy_FIN:
Looks like r210 and r216 don't have the idle drain issue. Only r217. Am I the only one with this issue?
[Samsung Galaxy Nexus] The Gingerbread Man:
Get CPU spy to check your deep sleep levels

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Luigi_2:
indeed
[Samsung Galaxy Nexus] mikeandjaimie:
Alot of people, including myself, I use the 1.5 step as a fallback for the the kernels when we can't run higher.... I disagree with this
[Samsung Galaxy Nexus] despard:
I can tell you you are not alone.

---------- Post added at 02:48 PM ---------- Previous post was at 02:35 PM ----------

I think we refers it to deep sleep but there is still battery drain a little bit
[Samsung Galaxy Nexus] sway40:
217 isn't bad at all, clocked at 1305-384, stock battery, data on all the time (no 4g).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] six_dfx:
Actually, 1536 seems to be the sweet spot for a lot of people. On my own device anything higher, including 1612, requires a lot more voltage, and is therefore not as efficient.
[Samsung Galaxy Nexus] franciscofranco:
r217 is fine, nothing has changed to produce **** idle sleep. Check your apps, I'm positive you have one of them messing with you. Possibly maps or facebook.
[Samsung Galaxy Nexus] timbck2:
I've never been one to care much about overclocking, I prefer stability and longer battery life (I usually keep my max CPU at 1300 or so, whatever is closest to that in any given nightly) but last night out of curiosity I cranked mine up to 1920 (making sure it wasn't set on boot) and much to my surprise it worked great - no instability, artifacts or anything of the sort. I was surprised because I've never been able to reliably run any of the 512 GPU kernels (yes I know CPU overclocking is different than GPU overclocking). I'll have to run some benchmarks for comparison.
[Samsung Galaxy Nexus] vomer:
Hey franco, just wondering if 217 is a milestone? Seem like you are working on some major changes since 217 has been out for a while? :D
[Samsung Galaxy Nexus] timbck2:
I take it back, my phone rebooted when I tried to run Quadrant, lol! Still, great work Franco!
[Samsung Galaxy Nexus] Wynnded:
...or Google+. Trying to figure that one out for myself. *Wanders away muttering to self holding phone millimeters from nose.*
[Samsung Galaxy Nexus] wy1d:
Does the volume increase in the app not affect call volume/ear speaker/Bluetooth volume? It doesn't seem to make a difference for me to correct the abysmally low stock volumes.

Also I'm getting terrible battery drain that I can't figure out. It seems to happen on all kernels. CPU spy says I'm getting plenty of deep sleep. I don't run the Facebook app. System Panel doesn't show any high usage apps. Screen is my highest user but I don't get nearly the screen time as others.

Biggest drain is right when I pull it odd the charger. I'll go from 100%-80% in 45 minutes. When screen is on, it drops about 1% per 45 seconds or so. Craziness.

Running r217 on Vicious JB 4.1.1. Anyone have any suggestions?
[Samsung Galaxy Nexus] kmakiki:
I read somewhere that AOSP builds have missing files or something that may be causing drain ROM side. I believe this is from JBQ himself. I believe I read this in the Paranoid topic.
[Samsung Galaxy Nexus] jenicekk:
Did anybody notice a bug in ringtone? When it starts ringing there is a strange sound "grzz" that lasts for 1-2 seconds and afterwards there is a normal ring. I use franco 217 on awsome jelly beam 4.1.1 ROM.
[Samsung Galaxy Nexus] TEK112:
You should post that in the ROM thread. The kernel wouldn't do that.
[Samsung Galaxy Nexus] The Gingerbread Man:
Volume booster is for things plugged into 3.5 jack. Maybe resetting your battery stats in CWM may help your drain, perhaps a fresh install of your set up may help.

I don't think the kernel does anything to the ringtones, I've certainly had no problems. Maybe your speaker is malfunctioning? Does it sound normal playing music files? I can only think its HW related as not seen this before

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Nop not milestone. r217 been out a while because I ve been busy with the app and add support for SGS3. Dont expect a big bump on r218, so far its only fixes.
[Samsung Galaxy Nexus] fclifton:
My list of JB ROMs is now

Bigxie's JB (if you prefer stock)

Jelly Belly (if you want to have some added features)

Android Revolution HD

Vicious Jelly Bean

Paul's Modaco Jr2

One really important thing: Which of these is for a Verizon LTE version of GNex??? Because that is what I have ;)

(It looks like search is working again, so I can do that, but if someone just knows it will be quicker. For me anyway!)

Thanks!
[Samsung Galaxy Nexus] Tommy_FIN:
Right now I'm on r216 and my phone sleeps like a baby with good idle drain. And I don't have any resource hog apps running. Gonna flash r217 again and see what happens.
[Samsung Galaxy Nexus] slayp00n:
Hey Franco, glitch I notice on 217: after plugging into a computer with USB and disconnecting, when I plug in more times the phone charges but I cannot see the device on the computer. I have to reboot. So essentially I only get one plug in per boot.

This is not present on the stock JBK only happens after flashing yours? to be clear adb or PMP does not work.
[Samsung Galaxy Nexus] TEK112:
Sounds like a fast charge issue. ROM fighting the kernel.
[Samsung Galaxy Nexus] mike2518:
Im sorry if I missed this, but where can I download the jelly bean kernel for ice cream sandwich? The downland link from the OP link does not work.
[Samsung Galaxy Nexus] TEK112:
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/

196 is the latest ICS kernel. There is an experimental r200 out there, but 196 was the last official nightly for ICS.
[Samsung Galaxy Nexus] slayp00n:
Yes I think that could be it, i always wondered is fast charge even safe?
[Samsung Galaxy Nexus] TEK112:
Fast charge is safe. It doesn't allow any more voltage than a wall charger.
[Samsung Galaxy Nexus] mike2518:
Thanks. But what I was looking for was the jelly bean kernel for ice cream sandwich. Have they been discontinued?
[Samsung Galaxy Nexus] slayp00n:
Not worried about voltage, usb ports are designed to provide 500ma, wlal charger provides 1000ma, my concern is burning out the computers usb?
[Samsung Galaxy Nexus] Young Cardiac:
Haven't read the whole thread but I'm looking to use this kernal but don't know which file to download.

franco.Kernel-r207-384GPU.zip

franco.Kernel-r210-384GPU.zip

franco.Kernel-r215-384GPU.zip

franco.Kernel-r216-384GPU.zip

franco.Kernel-r216-512GPU.zip

franco.Kernel-r217-384GPU.zip

franco.Kernel-r217-512GPU.zip

What are the different r2xx and the numbers right before the gpu?
[Samsung Galaxy Nexus] superbobup:
2xx are the different releases with 207 being g the oldest and 217 the newest

The different GPU numbers are the clock speeds for the GPU. Some people aren't able to run 512 but you can try it first. If it doesn't work, just try the 384 version

Hally flashing :):D
[Samsung Galaxy Nexus] Antob125:
Has anyone experienced 512 working for them now in JB where before on ICS you couldn't? Just curious. ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
Works well for me but I went back to 384. For some odd reason 384 is a little smoother,maybe my phone is on the verge of not being able to handle it?

sent from my precious nexus
[Samsung Galaxy Nexus] jenicekk:
In my phone this bug happens only with franco kernel.
[Samsung Galaxy Nexus] mike216:
I also really like the 1305 clock. Its a nice balance for speed while maintaining battery. Please consider holding onto this frequency franco

sent from my precious nexus
[Samsung Galaxy Nexus] TEK112:
A wall charger charges faster than USB with fast charge, from my own experience. Therefore, since both are 5v, the wall charger is drawing more amperage than USB. I don't know the exact numbers, but I know it is safe. I have used Fast Charge for years on my netbook, mac mini and dell workstation. You have nothing to fear.
[Samsung Galaxy Nexus] Young Cardiac:
So whats the advantage of being able to run 512 over 384? Performance? Is it worth it if my device and run 512 or does it take a huge battery hit?

Edit: NVM read a few pages back when someone asked the same question.

Edit 2: What apps do you guys use for the cpu? I used to use SetCPU back on the atrix but that was a while ago...
[Samsung Galaxy Nexus] FunkyMcBain:
I don't know if it's just me but my reception seems much more stable with this kernel running on AOKP. I want JB back though :(
[Samsung Galaxy Nexus] superbobup:
I think most people use Franco's app as it gives more options than any other general CPU app

I don't think the kernel has done anything to improve reception...maybe check your radio? There's a good thread in the gnex section :)
[Samsung Galaxy Nexus] Nexus.S:
What's the best app to control the kernel setting set CPU isn't that good. With my nexus s I used Ns tools
[Samsung Galaxy Nexus] derPianist:
Franco Kernel Updater !?

lol :D

via Google Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Does franco.Kernel govern WiFi? My WiFi seems to have taken a major hit in stability since switching to JB. What are everyone else's experiences thus far?
[Samsung Galaxy Nexus] franciscofranco:
The new JB kernel has new Wi-Fi drivers yes.
[Samsung Galaxy Nexus] bigeyes0x0:
This kind of thing is hit or miss, as for me WIFI reception is better. I guess a bunch of things come into play, especially how your router like the new JB WIFI driver.
[Samsung Galaxy Nexus] jeetS:
Yes, 512 wouldn't work for me on ICS but works fine with jellybean
[Samsung Galaxy Nexus] Hanny:
yes, r200 is the only and last ics kernel with a bit of JB taste because franco put some new google, samsung codes in it and the jb new wifi driver is added.

however, i personally recommend r196 because

1) usb fast charge is disabled in r200 for franco testing (and the experiment is already over but the fact that it is disabled, wont change)

2) i am having some instabilities on r200 with the exact same stable voltages on r196 and before

3) r200 does not have 512gpu version

and i can tell that the samsung/google fixes does not improve performance very much because your rom is still ics but not jb. also you need to risk some instabilities which will not help franco in the development even if you report it (cuz r200 is the fullstop of his ics kernels). therefore go flash r196 for rock stability as stated by franco and i agree it ;) if you insist to try out r200 dont forget to turn on fsync as it saved me like 10 times :p

cheers!
[Samsung Galaxy Nexus] Hanny:
@franco

some minor fixes on your app to suggest:

the BLX description - remove the "default is 96 for maximum batt health" and just say "default is 100" because you have already made it 100 since r196 ;)

btw love your recent app updates (although i cant tell what exactly i am loving) but i just feel excited when i see franco.kernel updater in my play store update list lol :p
[Samsung Galaxy Nexus] Marcb:
Following this post, I want to ask something...

Why is that our GPU is clocked at 307Mhz if the OMAP 4460 has a stock GPU of 384Mhz?

http://en.wikipedia.org/wiki/OMAP

I know Franco has to overclock to 384Mhz and 512Mhz...

Thanks!!
[Samsung Galaxy Nexus] osm0sis:
Google/Samsung underclocked it for supposed "battery savings" but everyone here has found them to be neglegible, especially between 307 and 384. Since the HW default GPU clock is 384 Franco is only actually overclocking it for the 512 GPU build. :)
[Samsung Galaxy Nexus] franciscofranco:
Ok r220 is up please take some time to read through this:

* Removed 1.9Ghz and added 1.7Ghz instead - almost no one could run 1.9Ghz so to avoid potential problems 1.7Ghz seems to be a nice middle point

* Added a patch to fix some derps in the kernel LOAD_AVG routines. It's a long description so please take some time to read the commit logs: https://github.com/franciscofranco/Tuna_JB_pre1/commit/74c91872354d61600e284dba9c661b4745439a45 and https://github.com/franciscofranco/Tuna_JB_pre1/commit/36f833cd801929c59c7c4c8bd3b7097520bd1f89

* Some ramdisk fixes

* Added USB_AUDIO modules to /lib/modules - if you have a USB DAC and you want to see what happens just do this: insmod lib/modules/snd-usb-audio.ko and post here the outcome

* Some default voltages refinements
[Samsung Galaxy Nexus] Marcb:
Cool, thank you!!

So the 384Mhz GPU Kernel is actually a "stock" clock for our SoC and 512Mhz is the overclocked version...
[Samsung Galaxy Nexus] franciscofranco:
Stock GPU comes with 307Mhz but I overclocked it to 384Mhz. Since it runs with the same voltage the battery difference is basically... null.
[Samsung Galaxy Nexus] Marcb:
Nice, thanks for the clarification man!

Muito obrigado!
[Samsung Galaxy Nexus] LNJ:
220 running good.

What is screen off frequency anyway? And what is the optimal setting for it?

Also does it make a difference if no power profile is selected?

What's the default power profile?

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] laureanop:
Same experience on wifi and 4g

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] vomer:
Sweeet s3. I was debating that phone so glad you working on that.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ceredics:
Is the jb kernel for 4.1 or 4.1.1? Just want some clarification.
[Samsung Galaxy Nexus] DarkGruf:
Both.
[Samsung Galaxy Nexus] digweed4me:
Working fine on 4.1.1
[Samsung Galaxy Nexus] Paragon_X:
So I'm coming from the Nexus S and used Matrix religiously. I hear Franco on the Galaxy Nexus is where it's at?
[Samsung Galaxy Nexus] franciscofranco:
That's a strange question to place on a kernel thread. Obviously most of the users in this thread will recommend you to use this kernel because they also use it, but I'll do it differently. There are some kernels for the Galaxy Nexus: this one, Glados, Trinity, Fugumod, LeanKernel, Popcorn etc. They are all different in features, CPU frequencies, governors, modules, sysfs interfaces, small optimizations, performance optimizations, battery optimizations, some others have backports like there was no tomorrow, some have kanged **** and so on. You'll have to read what each kernel offers and what you need as an end-user and then test accordingly.

I recommend you to test at least this kernels: this one, Glados, Trinity, Fugumod, LeanKernel, they are all created by good and knowledgeable developers, and in the end you'll use the one that fits you best.

Have fun.
[Samsung Galaxy Nexus] TEK112:
That is classy.
[Samsung Galaxy Nexus] tempera:
Which governer do you recommend for the latest JB #220?

Thanks
[Samsung Galaxy Nexus] The Gingerbread Man:
From personal experience either lazy or interactive, depends on how much battery you want to save. Interactive is JB default but lazy works well for me and what I do. Extermination is one if the best ways to learn

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Agreed, that is modesty right there

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
If only more devs were like him.
[Samsung Galaxy Nexus] AdrianE46:
Are there any changelogs for these nightlies because the app is blank where the changelogs used to be.

Sent from my Galaxy Nexus.
[Samsung Galaxy Nexus] daggerxXxsin:
i could not agree more. the whole point of the nexus is development and trying stuff out. all for the betterment of the community. :good:

and as a side note..i couldn't run 1.6ghz upwards on r217 (and older releases) and now i'm running 1.7ghz (on r220) i haven't rebooted yet. not once. awesome :victory:
[Samsung Galaxy Nexus] thuynh022:
I can't seem to download r220/384 kernel using the app. Website works fine though.
[Samsung Galaxy Nexus] Cheeze[iT]:
Worked fine for me, downloaded it maybe 30 minutes ago?
[Samsung Galaxy Nexus] franciscofranco:
I just auto-flashed 512GPU version from the app, all worked fine. Are you auto-flashing or trying to download the .zip?
[Samsung Galaxy Nexus] jeetS:
;)

and a slap in the face to popcorn :angel:
[Samsung Galaxy Nexus] spaceman860:
Check your download path in the app or you build prop

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] jeetS:
just auto flashed 220 512 and it worked perfect. Thanks again Franco
[Samsung Galaxy Nexus] thuynh022:
Downloading the zip. 384 wouldn't download, but the 512 did. Weird thing is the progress bar didn't move on my phone.
[Samsung Galaxy Nexus] franciscofranco:
Check the download path in the settings tab. It's /storage/sdcard0 for me (Jelly Bean rom).
[Samsung Galaxy Nexus] thuynh022:
Same path, all is working well now. Maybe your server was just getting slammed earlier. Thanks for all the hard work.

I was just going to leave my phone stock rooted. But, my girlfriend worked all day yesterday leaving me home all alone. My tinkering itch was killing me and you had so many good reviews on here I thought I'd try your kernel first.
[Samsung Galaxy Nexus] :
r220 running great on my toroplus! Using the 384 gpu and Are-you-jellin-rc3:what:

Super snappy and faaaasssstt! "1420 wheaty" Tks Franco!

Edit: I downloaded from app no problems on my end.
[Samsung Galaxy Nexus] raycaster3:
384 downloaded fine, but took another 60 seconds to auto-flash. I actually exited the app and was going to find the zip to flash it manually and it rebooted. Almost thought it wasn't gonna happen, but it's all good and running smooth.
[Samsung Galaxy Nexus] Hussainally:
Hey Franco thank u thank u so much for 220 .it is the best kernel ever.I am also so happy that I finally can install and run 512 without issues.

One question is 512 supposed to drain more battery compared to the lower GPU?
[Samsung Galaxy Nexus] BigBake88:
Higher clock speed always cosumes more battery. I don't understand why this questioned is asked over and over....
[Samsung Galaxy Nexus] Hussainally:
oops..sorry mate..thanks
[Samsung Galaxy Nexus] bradm23:
Google Butter

Franco,

I am curious how Google's butter compares to the tweaks you have already done with this kernel. Are we still going to get some benefits from butter, or is it mostly a gimmick?
[Samsung Galaxy Nexus] defconoi:
Is this JB kernel based off JB source with tweaks or still ICS
[Samsung Galaxy Nexus] theMaDHakkeR:
It is my understanding that "Butter" has more to do with 4.1 using Triple Buffering and and more frames for every animation. Its not really a gimmick as in ICS running the best kernel under perfect conditions, you still got choppy app drawer rendering.

I see a huge difference in animation and scrolling quality. Not performance, but overall presentation.

Hope that helps. Just my 2c.
[Samsung Galaxy Nexus] MДЯCЦSДИT:
Is anyone else having issues where the phone locks up randomly when you let it sit then auto screen-off on JB? I can't reproduce it under logcat/dmesg as it only happens sometimes...
[Samsung Galaxy Nexus] defconoi:
Who has the stock 4.1.1 kernel? used to be in bigxie's thread, but it is no longer. I've flashed stock jb over just fine, but i'd rather not flash a whole rom just for a kernel
[Samsung Galaxy Nexus] mike216:
Wow is this kernel smooth

sent from my precious nexus
[Samsung Galaxy Nexus] LNJ:
I asked a couple of times and nobody provided it there.

In the Q&A post, there is a link to the 4.1 kernel but it is an older kernel and not the one that came with 4.1.1 OTA.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] chadouming:
I'm sorry, but the voltage is only a part of the energy use equation.
[Samsung Galaxy Nexus] volapyk:
Nothing like project butter with an extra layer of Franco butter on top.

I'm using Bigxie's deodexed 4.1.1 rom (no mods) with #220@384 and I love it.
[Samsung Galaxy Nexus] despard:
Hi, if i come from Trinity kernel, should I flash the stock kernel first then flash franco kernel, or I can just wipe cache and dalvik cache and flash???

If i need to flash stock kernel first can you post me a link please???
[Samsung Galaxy Nexus] mike216:
I certainly hope we see Franco kernel available for the nexus 7

Wahoo just got email that it shipped

sent from my precious nexus
[Samsung Galaxy Nexus] mike216:
Just flash and no need to wipe anything. Francos script wipes for you

sent from my precious nexus
[Samsung Galaxy Nexus] superbobup:
But, since the GPU uses much less energy than the other components such as the screen and radio, the energy usage is essentially the same :)
[Samsung Galaxy Nexus] WhiteHartMart:
Yep - exactly what I did.

Thought I'd test this one out and have to say r220 is great (once I'd adjusted the colour settings ;-) ). Early days but idle battery drain seems better to me so far :-).

Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
[Samsung Galaxy Nexus] grisha1:
Governor and scheduler?
[Samsung Galaxy Nexus] dwang:
build 9 running very nice for me. I was experiencing quite a bit of lag with build 8, but build 9 is very smooth with interactive governor.
[Samsung Galaxy Nexus] Entree:
If it helps, this morning it took my phone about five seconds before the screen went on. No overclock, running stock 9.

I had a little panic lol
[Samsung Galaxy Nexus] DarthPiggie:
Franco; will you ever implement a slot lower than 350MHz Like imoseyon?
[Samsung Galaxy Nexus] franciscofranco:
Yes I'll take it as my fault I set one voltage too low ;)
[Samsung Galaxy Nexus] gn00my:
Just bought your app to support your work a litle bit, great work!
[Samsung Galaxy Nexus] ourakot:
i personally can'wake up my phone.i press the power button and nothing happens.no oc

beacause i have deleted nightly 8 file:D
[Samsung Galaxy Nexus] franciscofranco:
Never ever.
[Samsung Galaxy Nexus] ro_explorer:
Never say never ;) ...
[Samsung Galaxy Nexus] kjwalker:
I have a feeling 'never' applies here, after reading how Franco doesn't even like the 350mhz clock :p
[Samsung Galaxy Nexus] :
always getting better. will try #9.1 once published ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ro_explorer:
I know Franco's approach (I'm on his kernels since his first release for Nexus S) so I got some months to "know him" .. but still .. "never say never" .. is bringing bad luck ...

Anyway, in this case the respective affirmation should have been read as: "I will but not in this timeline" :)
[Samsung Galaxy Nexus] DarthPiggie:
Why doesnt Franco like lower clocks? Anyone know?
[Samsung Galaxy Nexus] daandman:
Franco are previous builds available for download through your market app?