yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] EDNYLaw:
People seem to prefer Westwood. I use it myself and have no complaints about speed whatsoever. Try out the various ones, cubic is Google default, but if you go over to Franco's GSM Galaxy nexus thread (same kernel as ours) and search for TCP you'll see people's analyses

Sent from my swagged out AOKP Xoom 1.5 Ghz 512 Mhz GPU
[Samsung Galaxy Nexus] wtherrell:
Yes, thanks, That was very helpful. Westwood it is!
[Samsung Galaxy Nexus] AirBoss24K:
Currently testing out nightly #298. Getting frequent data drops and was wondering if I'm the only one. Coming from nightly #295, I wasn't having this issue and might go back if it persists.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] EDNYLaw:
Haven't had a single data drop, try upping the CORE voltage a little (by 5 or 10 mV). Also, r300 is, give that a whirl and see that improves anything.
[Samsung Galaxy Nexus] :
Hey Franco,

I know your'e probably in a rush but do you have plans on getting your kernel compatible with 4.2? Thanks in advance.
[Samsung Galaxy Nexus] Wynnded:
He has mentioned that he's already trying to grok it.
[Samsung Galaxy Nexus] jcmm11:
You should really keep an eye on the gsm thread. This question is answered there. That thread is much more active.
[Samsung Galaxy Nexus] :
Alright thanks so much.
[Samsung Galaxy Nexus] xolanir:
Yeah Franco is working his black magic with the source kernel, and from the sound of it, it may take him a minute since 4.2 brings a lot of changes all the way down to a kernel level. Once he's done, he'll update both gsm and cdma kernel variants. I guess I'll just patiently wait for the kernel to be done before flashing any 4.2 ROMs. Thx Franco for your awesome work!
[Samsung Galaxy Nexus] jcmm11:
Just a note that there is no difference in the kernel for gsm and CDMA. It's the exact same kernel. (Yes I'm sure.)
[Samsung Galaxy Nexus] mordakk:
I'm running stock ROM, rooted, and unlocked boot loader.

everytime I change my cpu frequency, after I lock my phone, or reboot, it resets to stock speed.

I've tried setcpu and multiple programs.

Any ideas to fix please? Yes I have set on boot turned on
[Samsung Galaxy Nexus] JohnKuczek:
Do you have set on boot turned on in only one place? If multiple apps are trying to set different things, they could be overwritting each other.
[Samsung Galaxy Nexus] TEK112:
Are you using SuperSU or superuser?

People have had issues with superuser not having settings stick on reboot.
[Samsung Galaxy Nexus] mordakk:
Superuser. And I'm only trying to use one app to set the cpu at a time...

Just tried supersu and same problem

Example, just tried setcpu to 1.3 or 1.4 ghz, it works and overclocks it, but when I lock my screen and go back into app, it's back to 1.2 ghz
[Samsung Galaxy Nexus] TEK112:
1st double check that set cpu speed on boot is enabled. 2nd, ensure the ROM you are using isn't trying to override Franco's app. For instance, an AOKP ROM would have me check ROM Settings and Performance.

Lastly, clear app data, uninstall and reinstall Franco's and app and try again.
[Samsung Galaxy Nexus] mordakk:
As I said in my post I'm stock ROM and enable on boot is turned on. But thanks for not reading my post
[Samsung Galaxy Nexus] TEK112:
That was completely uncalled for. Don't act like a child.
[Samsung Galaxy Nexus] Wynnded:
The fella was trying to help you. Good luck finding a solution on your own. smh
[Samsung Galaxy Nexus] mordakk:
I fixed it by going from Franco stable to Franco nightly... Weird.

Do you guys use bfq, noop, or deadline?
[Samsung Galaxy Nexus] EvanVanVan:
Hi, I've never flashed a custom kernel before but am thinking about it and have a few questions...

1. Can I just flash this on top of my current phone setup (CM10) or will it erase everything?

2. What kind of work does it take to setup? Flash and it's good? or do I need to configure it somehow?

3. Does this need to be reflashed every time I flash an updated nightly?

Thanks for your help
[Samsung Galaxy Nexus] bigbear6708:
1. Won't erase anything...I suggest a cache and dalvik wipe first however.

2. None until you learn how to tweak it

3. Flash a ROM and the kennel that Comes with the ROM will be poor on your phone... So yes
[Samsung Galaxy Nexus] kmcrane:
I'm on muzzy's newest 11-20 and I have been using this rom for a week. But my Franco app and / his download site thinks i am on an ics rom. It says newest is 196. Is there a 4.2 kernel, or am I doing something wrong?
[Samsung Galaxy Nexus] :
There is no 4.2 kernel. And it shows the ICS builds because it doesn't recognize your firmware.
[Samsung Galaxy Nexus] kmcrane:
Ok. Thanks. I thought that, but read something different somewhere else. So I figured I better ask here before I go too far... Thank you again.
[Samsung Galaxy Nexus] jcmm11:
There is a 4.2 kernel. It's experimental hence boot.img only (not flashable via recovery). Latest is r315.

http://xdaforums.com/showthread.php?p=34388627
[Samsung Galaxy Nexus] jharvey24:
I read the tiny kernel over @ rootzwiki supports 4.2, but have not flashed it. Running Eclipse.
[Samsung Galaxy Nexus] KJW979:
http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/

Here is latest from Franco for 4.2, 318. Currently running on Eclipse build 3, no problems so far.
[Samsung Galaxy Nexus] artjef:
Interesting, the Franco app stills gives me an error that there is no kernel for 4.2. I assume that means nothing officially available. I wonder when there might be an official beta or better.
[Samsung Galaxy Nexus] :
I'm getting an FC when I select the Frequencies Tab in the franco.updater, anyone else?
[Samsung Galaxy Nexus] jcmm11:
I'd check the other thread.
[Samsung Galaxy Nexus] ncvikingx97:
Where do I find the Franco 4.2? Is it stable? Is the latest kernel milestone 6?
[Samsung Galaxy Nexus] vtmike:
Wifi hotspot isn't working for me with 318.
[Samsung Galaxy Nexus] horten229:
I was getting this a few days ago but some of the recent Franco Kernel Updater releases (I'm on 8.0.10) seemed to have fixed it.:)

---------- Post added at 10:25 AM ---------- Previous post was at 10:15 AM ----------

It's out there somewhere but hard to find. Search the Franco threads for release 318. It is not a zippable load but at bin that has to be loaded with FKU. And it's still in Beta so use at your own risk.! Milestone 6 is for 4.1.x and won't work on Android 4.2.
[Samsung Galaxy Nexus] ncvikingx97:
Thanks
[Samsung Galaxy Nexus] :
Awesome. But I think from now on I'm using trickster for my kernels.
[Samsung Galaxy Nexus] hshaikh:
I posted previously that I was having launcher lag issues in stock odexed 4.2. I was told that this is a known issue. So I changed my governer to dyn interactive and the lag is gone. Does anyone have any explanation. This is awesome. But I'd like to know why
[Samsung Galaxy Nexus] :
Fun dyninteractive changes the tunables due to the system load so it probably fixed your lag because it adjusted itself to handle what your system was handling at the moment
[Samsung Galaxy Nexus] SH4YD33:
http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/
[Samsung Galaxy Nexus] A.C.Sanchez:
Is there a fix for tethering yet? I haven't seen one reported. Sorry if I missed it.
[Samsung Galaxy Nexus] allan1313:
Damn. My phone runs great on Franco's 4.2 kernel but can not connect to wifi at all.
[Samsung Galaxy Nexus] EDNYLaw:
Is your WIFI router using WEP security? If so, the new 3.4 WIFI drivers do not work with WEP. Switch to WPA/2 and profit.
[Samsung Galaxy Nexus] darklordofthesith:
Has anyone tried francos 328 yet? I downloaded the zip but need feedback before flashing. Still using tiny right now.
[Samsung Galaxy Nexus] allan1313:
Thanks. I will give that a shot.
[Samsung Galaxy Nexus] stuckintheskull:
Not working yet but hes working on it.

I'm using it right now with no problems. Just no tethering yet. There have been some reporting SOD's. Seems to be related to PGM( i think that's what its called).
[Samsung Galaxy Nexus] jcmm11:
I can confirm the pgm problem. Solution is to uninstall before flashing 328, then reinstall afterwards. No problems after doing that. (Might be enough to just disable it prior). Before I did that I had sod and boot loop issues, none since.
[Samsung Galaxy Nexus] kuronosan:
Got nothing but force close upon booting.
[Samsung Galaxy Nexus] scadilla:
Question about kernel settings

Hello all,

I am running mmuzzy's latest 4.2.1, was considering trying out a couple of different non-Franco kernel, I plan on coming back to Franco's once the tethering is fixed, 4.1 ran great with it. What I wanted to know is if Franco's app can be used with kernels other than Franco's or Lean? Any thoughts are welcomed.
[Samsung Galaxy Nexus] klobkelosh:
Right there with you. I was using Franco's app with tiny kernel and it worked fine. I wound up getting trickster mod app, but Franco's worked.
[Samsung Galaxy Nexus] ncvikingx97:
Same with me
[Samsung Galaxy Nexus] mlgneo:
work on 4.2.1? (muzzzzzy'sROM)
[Samsung Galaxy Nexus] jcmm11:
Yes. Running 328 on muzzy. If you use pgm uninstall pgm, install 328, reinstall pgm.
[Samsung Galaxy Nexus] :
1) did you edit the IVA & CORE voltages?

2) Did you disable any of the 3 smart reflex settings?

3) What is your current IO scheduler set to?

4) Current TCP setting?

Thanks.

Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2
[Samsung Galaxy Nexus] djh816:
anyone able to run 335 on cm10.1? I just get a ton of "___ has stopped"
[Samsung Galaxy Nexus] marcusva79:
Working great her. Could be a bad download.
[Samsung Galaxy Nexus] daviddemarco79:
Yea same thing here for the new aokp ROM.... Keep getting ui has stopped
[Samsung Galaxy Nexus] jcmm11:
Franco (in the other thread) said he has to modify the ram disk to be compatible with cm. Should be done with next release.
[Samsung Galaxy Nexus] allan1313:
Is tether working on his latest builds??
[Samsung Galaxy Nexus] jcmm11:
Should be. Unfortunately I'm not in a position to test, but reports I've seen say it works now.
[Samsung Galaxy Nexus] allan1313:
It does work. Good deal. Love me some Franco kernel's.
[Samsung Galaxy Nexus] Blaqhawk:
Yep, love me some Franco. Just put his latest on my Nexus 7. Noticeably better than the stock kernel.

Edit, I guess I should have mentioned that I am running Stock Android. 4.2.1 rooted.

Swyped on my Nexus 7 using Tapatalk 2
[Samsung Galaxy Nexus] bose301s:
How do you flash the boot.img kernel, I tried and all I got was a boot loop or everything FC'd, can't remember. It's possible this kernel isn't compatible with CM10.1 I suppose as well.
[Samsung Galaxy Nexus] Blaqhawk:
Franco's kernel is running great, I got over 8 hours of screen time yesterday! I have the. V3 cpu in my Nexus and have underclocked all the voltages in this kernel by either 25 or 50 (I don't recall the exact number, I'd have to check). I may try to go down a bit more as the kids no noticeable lag or differences, including but not limited to lockups / force closes.

FWIW, Adam.
[Samsung Galaxy Nexus] nitsua98:
Download the zip instead and flash in recovery
[Samsung Galaxy Nexus] Blaqhawk:
I think he is referring to the kernel for the Nexus 7. If so, there is no .zip so you have to flash the boot.img.

If not, do as previous post said and download / flash the zip.
[Samsung Galaxy Nexus] exzacklyright:
Do does 4.2.1 work with this kernel? Latest nightly is 342
[Samsung Galaxy Nexus] jcmm11:
Latest nightly works with 4.2+
[Samsung Galaxy Nexus] TheHunterOfShadows:
Out of curiosity, with the 4.2 nightlys did we stop doing the 512gpu? Not that it all that stable anyway but was just wondering.
[Samsung Galaxy Nexus] Whompy:
You've actually got it backwards; the 384 GPU has been discontinued. All builds will use 512 GPU from now on.

Tapatalkin' from my CM10.1 Toro
[Samsung Galaxy Nexus] ShredEight02:
Lawl at the comment for nightly #345 about a" derp on #344 that could cause major battery drain". I was wondering why my batteries were only getting like 7 hours out of em. Glad to see you got that figured out, I thought I might have been the latest aokp nightly that I flashed recently as well.

Looking forward to getting some longer battery life tomorrow :)
[Samsung Galaxy Nexus] :
What screen times are you guys getting with the newest build
[Samsung Galaxy Nexus] exzacklyright:
WiFi didn't work on the latest build
[Samsung Galaxy Nexus] kmcrane:
Barley an hour, on eos 4. Speed was awesome, standby was awesome, but screen on time seems to be less than I get with others. This one benchmarks higher than any other by 15-20%
[Samsung Galaxy Nexus] timbck2:
You keep posting this in every single Franco kernel thread. Yet you provide no details, no log files, nothing that will help anyone help you with your problem (which most likely has nothing to do with the kernel, by the way). Stop posting unless you can supply some useful information, nobody can or will help you otherwise.

Sent from my Nexus 7
[Samsung Galaxy Nexus] hogowner:
Where do you find 345...when I click on the link in the op for nightlies....it only goes up to 293

Thanks

Sent from my "Blazing" fast Nexus
[Samsung Galaxy Nexus] jcmm11:
Flashable zips on the appropriate subdirectory.

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/

Note that 361 is latest (and recommended). It also has hardcoded voltages, just in case you normally play with them (it's a temporary thing).
[Samsung Galaxy Nexus] exzacklyright:
So what are your guys governor settings? My battery life is terrible, my phone is laggy, and it's just an unpleasant experience.
[Samsung Galaxy Nexus] TEK112:
I have the same issues. However, I have determined the issue is ROM related. 4.1 Droidtheory ROMs gave me over 2hrs on screen time everytime. Since then I have never seen that again.

Currently I get 1.5hrs screen time and 10 hrs of real use. I blame LTE.

Also, my usage is heavy. I got a smart phone to use as one. I have two exchange accounts, two regular email accounts and four social network accounts that actively sync along with eight forums on tapatalk.

There is a reason Google dropped LTE support.
[Samsung Galaxy Nexus] EniGmA1987:
LTE doesnt add any battery drain. It all depends on your signal reception. I stay on LTE all the time and if I bother configuring my phone to be at its best I only see 0.5% idle drain per hours on LTE. But if I go to a low signal area, drain can easily be 6-7% an hour when idle. But the same is true for 3G as well.
[Samsung Galaxy Nexus] TEK112:
That's just not true, it does use more power. Unlike normal GSM phones with one radio that utilizes multiple bands (hspa/hspa+, etc), Verizon LTE phones have two radios for CDMA and LTE. This is the beginning of the power consumption issues not to mention inefficient handshaking between 4G/3G/1x, because LTE at -120db will trump -80dbm of 3G.

LTE running at peak performance will be faster than hspa+ by a longshot (http://www.itproportal.com/2012/12/19/hspa-vs-4g-lte/), but the amount of power needed is exponentially more (http://www.eetimes.com/General/PrintView/4229960) even for normal tasks that aren't fully utilizing the bandwidth.

The same correlation can be made between a V8 motor and an 4T motor. While the turbo 4 can almost produce the power of the V8 and sometimes exceed it, the V8 for all practical purposes provides more power on average (area under the curve), but uses more fuel to do it. LTE is the V8 and hspa+ is the T4.

All of the best battery I have seen from people who use their phone for more than an e-reader/web surfer are GSM phones and their modem reporting in battery statistics show a far less utilization of battery over their LTE counterparts.
[Samsung Galaxy Nexus] justen7723:
Pgm not working for me on 364
[Samsung Galaxy Nexus] modernbummer:
+1
[Samsung Galaxy Nexus] justen7723:
Awesome!! Pgm working now for 364.

Update your pgm app.

sound mods.. http://xdaforums.com/showthread.php?p=37541594
[Samsung Galaxy Nexus] RTNDO128:
The 364 kernel has been giving me a handful of random reboots every day, anyone else? I'm switching back to 361.
[Samsung Galaxy Nexus] justen7723:
Been running great for me. I ran 361 until pgm app was updated. Been on 364 since with no problems at all. I don't change a lot just my min to 192, max at 1305 and max screen off at 384.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kr4zy10:
currently running franco r376 kernel and have his app but cant figure out how to enable hotplug or generic hotplug...can someone help me please
[Samsung Galaxy Nexus] TEK112:
Hotplug is a default setting of the kernel itself. Franco removed his own hotplug setting eons ago as it was fighting with the default hotplug behavior.

Bottom line, no more messing with hotplug. It is automatic.
[Samsung Galaxy Nexus] Seion:
Any updates on new nightlies or 4.3 update?
[Samsung Galaxy Nexus] midnightdevil66:
Check in android development forum.

Sent from my Toro
[Samsung Galaxy Nexus] Seion:
There is updates there, but will that work version work on the Verizon GN?

http://xdaforums.com/showthread.php?t=1367341
[Samsung Galaxy Nexus] midnightdevil66:
Yes it will.

Sent from my Toro
[Samsung Galaxy Nexus] ashclepdia:
i have yet to see/use a kernel on Gnex that doesn't work just fine no matter which forum i found it in. (maguro/toro)

actually, lately I've kinda stopped coming to the toro forums for kernels and have been going to the Galaxy Nexus Android Dev section instead (seems to be more lively and all kernels work just fine)
[Samsung Galaxy Nexus] parkson:
Something about installing this kernel (on any rom) breaks my downloaded music players, such as poweramp and doubletwist. Can anyone else confirm this problem?
[Samsung Galaxy Nexus] Stadsport:
Franciso, seriously, thank you for re-implementing user undervolts. I've always been able to undervolt a lot more aggressively with imo's kernel than the default undervolts you set, so I'm really happy to have that control back.
[Samsung Galaxy Nexus] Znomon:
what undervolt settings are you using for your gnex?

and when i click "undervolt" is is supposed to reboot immediately after?
[Samsung Galaxy Nexus] dcoy82:
Thanks, looks like a nice update.
[Samsung Galaxy Nexus] Redflea:
Huge update, both kernel and the app significantly improved. Franco, you are setting the bar really high for all kernel developers, great work.

I didn't see it in the change log...do the overclock settings in the app take affect w/out a reboot/setting boot-up defaults via initd? At one point you mentioned that would be in the next update to your app. Did that make it in yet?
[Samsung Galaxy Nexus] Stadsport:
Currently running:

1350mhz @ 1250mv

1200mhz @ 1150mv

920mhz @ 1100mv

700mhz @ 950mv

350mhz @ 775mv

The lower speeds are where the phone spends most of it's time, and luckily those are the speeds that seem to take to undervolting a little better.

I'm undervolting through SetCPU, I'm not familiar with undervolting through franco's app. But I will say that if you get a reboot after hitting Apply in SetCPU, it means you undervolted too low. Make sure you never check "Apply at Boot" until you know it's stable! ;)
[Samsung Galaxy Nexus] Znomon:
Well I used Franco's and after the reboot I went to the app and the values were set correctly. So I guess that's how it works for him. I'm running at

1100

1000

875

775

750

I'll post back if Its running stable. So far (about a half hour) and a few quadrent tests ( I know the don't mean much anymore) I'm not seeing any lag or loss in performance.
[Samsung Galaxy Nexus] Stadsport:
Those are REALLY low numbers. I just tried them and got a freeze/reboot, though after rebooting I was able to get 350@750 to stick with the rest the same as I had before.

Are you sure you're not mistaking "saved settings" for "current settings" or something to that effect? If you have SetCPU, you might open it up and see what the current voltages are showing as.
[Samsung Galaxy Nexus] bluemoon1221:
Same thing happened to me. I'm using the cm9 music app and it kept saying it has stopped working. Uninstalled and reinstalled and now its fine though
[Samsung Galaxy Nexus] TheBiles:
Nightly 13 screwed my phone up big time. First it was stuck at 1200MHz, even with the screen off, and then I rebooted and got boot loops. Had to re-flash 12 through recovery. I'm using AOKP 19, and I very slightly set it to undervolt.
[Samsung Galaxy Nexus] Geezer Squid:
Sounds like you have a bad download or a bad install. I would suggest you redo both.

Good luck.
[Samsung Galaxy Nexus] sinik420:
probably an init.d change from franco. romans 19 has init.d support but it is disabled, causing problems with kernels
[Samsung Galaxy Nexus] TheBiles:
Just tried 13 again with no UV, and I'm still seeing very high time at 1200MHz, and the phone is never entering deep sleep.
[Samsung Galaxy Nexus] sinik420:
like i said, kernel might have init.d changes added to the ramscript. and if its like glados kernel, it wont enable it when its disabled. meaning your system is missing tweaks and things due to this and you will see performance issues
[Samsung Galaxy Nexus] Geezer Squid:
I'm on AOKP 19 with the #13 kernel and so far I'm seeing no issues.
[Samsung Galaxy Nexus] sinik420:
what governor? same question to the guy/girl with issues
[Samsung Galaxy Nexus] masri1987:
me too,

350/1200 on interactive. i don't have any issues.
[Samsung Galaxy Nexus] sinik420:
gah, want to know if the original person had it on performance
[Samsung Galaxy Nexus] dcoy82:
Running #13 350/1200 UV Hotplug enabled conservative governor, so far running great!
[Samsung Galaxy Nexus] TheBiles:
I had it in interactive, but I switched to conservative and rebooted, and things seem fairly normal now.
[Samsung Galaxy Nexus] Geezer Squid:
I like speed: performance and 700/1350. No changes to voltages and hotplug checked.
[Samsung Galaxy Nexus] CDuke619:
I've been trying out Conservative governor with 700 min 920 max with Hotplug enabled and have had no problems with lag really. I wonder if this setup will show me great battery performance as well
[Samsung Galaxy Nexus] dp92180:
I'm using the stock kernel settings and AOKP 19 with no issues.
[Samsung Galaxy Nexus] BankZZ:
I do:

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

Reboot and its back to 0. How can I keep this enabled?
[Samsung Galaxy Nexus] rgoyena:
So....is it safe to update the version?
[Samsung Galaxy Nexus] sinik420:
use a script app that supports set on boot or add to init.d
[Samsung Galaxy Nexus] Stockmoose16:
Problem with Nightly 13

There's a problem with the Nightly 13 kernel. I was dropping about 3% an hour, and then as soon as I installed this kernel, I started dropping much faster. My phone was in the same spot as it was the entire day, without moving.

I went into BBS and noticed there is now a partial wake lock called "NetworkLocationPassiveCollector." What is this?

I'm 100% sure it's the kernel, since my phone didn't move, and I can clearly see in the battery graph that the drain started to occur right after I installed the new kernel. And yes, I cleared cache and Dalvik.
[Samsung Galaxy Nexus] sinik420:
thats from maps 6.0.*. disable network location and see if it stops or force close the app
[Samsung Galaxy Nexus] Stockmoose16:
I don't think the drain is solely from that Wakelock, since it was only Wakelock for 12 minutes.

I'm attaching the picture evidence of the battery drain. I installed the kernel at approximately 3:45.
[Samsung Galaxy Nexus] sinik420:
not saying it was, probably is more since thats a large drain but thought id post about the wakelock you mentioned
[Samsung Galaxy Nexus] Stockmoose16:
Thanks. I was able to stop the wakelock, but the drain is still occurring. Something changed in the kernel for the worse.
[Samsung Galaxy Nexus] Znomon:
Been running these numbers for 4 hours, no problems...

Edit: Franco says those values, but when I check with setcpu it said default values, so Franco doesn't actively check clock speeds. It just guesses based on cache, and cause I had those values set when my phone powered off (which it shouldn't do. I got it to UV normally) it remembered the cached voltages and showed those. Makes sense... I was getting too excited over being stable at those voltages... then realized I was at stock... haha
[Samsung Galaxy Nexus] Elganja:
1125, 975, 875 (1200, 920, 700)

working well for me... will probably stick with it