yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] droidholic:
Wow, I can't believe some people would rate this thread as anything below excellent. This has been one of the most helpful and informative threads ever....I have learned a lot about kernels and maximizing battery life. Keep up the good work, Franco!

On a different note, I was one of those that had connectivity issues on #10. However, after doing more testing, I have concluded that the connectivity issues had NOTHING to do with Franco's kernel, at least in my case. The connectivity issues were caused by WPA2 encryption for wifi tethering. I do not experience any connectivity issues if I enable WPA. Just throwing this out there in case some people thought the kernel was the culprit. I am currently enjoying #10 since I saw some amazing battery life with it; haven't really tried #11 yet.
[Samsung Galaxy Nexus] Elganja:
anyone else having this issue with hotplug? I didn't even think about this case, but I haven't made a call since I turned on hotplug... lol
[Samsung Galaxy Nexus] SomeGuyDude:
I have no idea what this is telling me. Does the user have to punch these in, or what?
[Samsung Galaxy Nexus] TEK112:
There is an old saying... only one way to find out...lol
[Samsung Galaxy Nexus] emplox:
nevermind! i feel dumb. There was a tiny plastic piece from this zagg like wrap i put on my phone last night around the same time the kernel came out that was covering the mic. I looked at it like 10 times to make sure that wasn't it...and finally this morning i just ripped the whole wrap off the phone and found that there was a tiny circle piece covering it that you couldn't see.
[Samsung Galaxy Nexus] TEK112:
I am on AXI0M 2.4 and I am not having this issue. What ROM are you on, perhaps it is ROM specific.
[Samsung Galaxy Nexus] chkn:
bump I would like info as well
[Samsung Galaxy Nexus] Natolx:
I still get the delayed lock sound.(Unlock sound is better though)
[Samsung Galaxy Nexus] mike216:
Those echo commands are to turn hot plug on or off or you can buy franco app and it will do it for you
[Samsung Galaxy Nexus] mike216:
Colors + just means he tweaked the colors some. You won't be able to use voodoo. Not yet but hopefully one day we have some kind of color driver app
[Samsung Galaxy Nexus] bowsersoulstar:
Was on build 9.2 for a while since it had very good idle drain and overall battery life.

Flashed 11 last night and noticed idle drain was a bit more than 9.2; lost an average of 3-4% per hour idle. 9.2 was averaging like 1-2%. I did wipe cache and dalvik and recalibrated batstats. No ROM changes or app changes either.

Gonna give it another day or two for the kernel to truly see if there's a warranted difference.
[Samsung Galaxy Nexus] Pupalei:
I'd like to know this also. I've been killing the camera with the long press back button (cm). Is this necessary or is just backing out of camera sufficient?
[Samsung Galaxy Nexus] Znomon:
open the app, then just press home.
[Samsung Galaxy Nexus] TEK112:
Press the Running Process button at the bottom of the screen (shaped like two overlayed rectangles)and swipe the app you want to kill to the side, no more running process.

---------- Post added at 03:43 PM ---------- Previous post was at 03:43 PM ----------

That does not kill the app.
[Samsung Galaxy Nexus] damobster54:
Love this kernel but tested my search today and found out my Mic isn't working... I'm running this is Roman's build 15. I flashed the kernel back to ten and have no problems again.
[Samsung Galaxy Nexus] dadsterflip:
Correct me if I'm wrong. Does color+ tweaks make the white look tinted ? Or what exactly does it do? Besides the obvious.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CBMC:
Quick question. Sorry if it had been answered. Why is the kernel zip file always named franco-nightly? Why isn't there any indication of the version in the file name. Not a big deal, but seems to make it unnecessarily confusing.
[Samsung Galaxy Nexus] franciscofranco:
#17.1 is up. Just a little try to fix the reboots from last version. It's strange how the GN devices are so different from eachother.

200mhz and 400mhz are gone, just 350mhz like on stock to rule out any incompatibility from changing that value somehow.
[Samsung Galaxy Nexus] hredder:
I had that problem as well. I was rebooting the phone and didnt have set at boot checked so it was reverting back to default. Not sure if that was the cause but it fixed it
[Samsung Galaxy Nexus] CrushD:
Mmm, tried 17.2, phone won't even get past the first Samsung screen, and it just keeps rebooting from there.

Update: Well I reverted back to an older kernel version 15.2, then wiped out my init.d folder, then reflashed 17.2, looks to be working now.
[Samsung Galaxy Nexus] ajftl:
Oh boy lol. Updater still don't work? I switched kernels. Love to run this but. Colors off and other things not working properly.
[Samsung Galaxy Nexus] sway40:
This is crazy coming from 16.2, I flashed 17, then 17.1, then saw 17.2 like damn really. No problems on any of them and they all flashed how they were supposed to. Definitely weird how these phones differ from each other this much.

~Sent from my GNexus running Cm9 ~
[Samsung Galaxy Nexus] Natolx:
New kernel boot loops me as well... can't seem to find unit.d folder in root explorer
[Samsung Galaxy Nexus] luckylui:
New kernel all good on flash.

Flashed it through franco apk-->kernel auto flash reboot itself and bam! All good :)

Running it w deodexed version of 4.0.4

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CrushD:
Yeah, I definitely believe in my case, something in my init.d was causing this issue. I tried replacing my init.d stuff back, and once again my phone wouldn't boot, removed the folder, and I could boot again.

To find it, it is /system/etc/init.d

If you don't have it, then I guess you're facing a different issue.
[Samsung Galaxy Nexus] Icey34:
Hey guys, never flashed a Kernel on the GNex, does this require any wiping?

Are these on the app or it's a custom setting with the kernel in the OS? And the app is "Franco.Kernel" for $1.91. right?

This kernel ONLY works on 4.0.3 builds, or 4.0.4. right?
[Samsung Galaxy Nexus] Zacisblack:
Stability fixes? Phone lags/freezes constantly on 17.2 at 1.5Ghz. Had no issues with 17.
[Samsung Galaxy Nexus] Natolx:
Found it. Deleting it fixed the issue. Thanks
[Samsung Galaxy Nexus] Pupalei:
I didn't try it on 17 so I can't speak to that, but I'm also lagging hard at 1500 on 17.2.

1200 and 1350 seem fine. And by fine I mean great.
[Samsung Galaxy Nexus] luckylui:
Zipping through things with 17.2 @1500 francoturtle. Came from 16.2. Greatness of 1.5 I love it. Reminds me of my Evo 3D @1.512 :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] luckylui:
Wipe cache and dalvik before kernel amd after. Learned that from the good god himself kernel dev chad.goodman over at Evo 3D land :)

Franco apk you will find the oc undervolt options. And I believe it is 1.91... Have fun! :):)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RickROM:
I'm having the same problem. I had no problems with 17, but 17.2 is basically unusable at 1.5GHz.
[Samsung Galaxy Nexus] Zacisblack:
It was fun while it lasted =\…
[Samsung Galaxy Nexus] masri1987:
17.1 was rebooting for me, on turtle 350 min 1200 max. I think I shall try 17.2
[Samsung Galaxy Nexus] mikeacela:
why do the colors look really blue now since 17+?
[Samsung Galaxy Nexus] Zacisblack:
What he said. Didn't even notice until now.
[Samsung Galaxy Nexus] jwood:
Downloaded and installed 17.2 all I get is boot loops at the init GOOGLE screen with the unlocked padlock....Back to 16.0 :mad:
[Samsung Galaxy Nexus] masri1987:
this has happened to me a lot, from version 11 or 12, what i do, is flash faux's 4.0.3 reset kernel before flashing any kernel.
[Samsung Galaxy Nexus] yyz71:
Oh boy 17.2 lags like hell anybody have the zip for 17 ? 17 ran smoother :confused:
[Samsung Galaxy Nexus] mkarps:
So how do I tell what version I have. I forget....
[Samsung Galaxy Nexus] websterzx10r1:
Go to settings, about phone, and in there should be the kernel version ur using.
[Samsung Galaxy Nexus] countryfolk07:
How can you tell if hotplug is actually enabled? Just came from the incredible forum, so this is pretty new to me. I typed the command in terminal but I like to see proof. I must say for being stock Android, this thing (the GNEX) sucks battery beyond belief. Lol. Ran ICS on the Inc and could go a day and a half. :eek: Anyway thanks for any info.
[Samsung Galaxy Nexus] druidking:
Not sure if this is a FrancoKernel error or anything, but my phone this morning shut off randomly and is now perpetually stuck in the "Encryption unsuccessful" error screen. I have the ability to boot into CWM, however I cannot access the SD card (it says unable to mount). Is this an error with my Kernel? I just autoflashed using franco's app last night to 17.2. Any help would be much appreciated.
[Samsung Galaxy Nexus] jbdan:
Not at all you just have to find what works on your phone just like the Inc was 1 year ago. I go 2 days between charges on the GN.

With root explorer or similar, navigate to: /sys/module/dsscomp/parameters/hotplug_enabled

Then open "hotplug_enabled" with text editor (built in to root explorer)...if it says "1" then it is enabled. If it says "0" then it is disabled.
[Samsung Galaxy Nexus] kichard:
Newest AOKP and Franco 15.2 all stock. Sure I may have had wifi on but damn I've never seen screen on time like that.
[Samsung Galaxy Nexus] kjwalker:
Franco, I had 17.2 flashed and was unable to watch Netflix videos. Tried multiple videos, reboots, etc. Reflashed 17 and Netflix played fine.
[Samsung Galaxy Nexus] Hatman41:
I flashed 17.2 and my phone lagged very badly. I went back to 17 and no issues.
[Samsung Galaxy Nexus] Gahh Its Lee:
Everyone I suggest checking out the GSM version sections thread for this kernel its the same kernel but they are much more active and figure a lot more out.
[Samsung Galaxy Nexus] tyrnight:
no problems with Netflix or any other video..

running 1000/700 FrancoGazele on battery and 1350/700 Performance on charge

the only thing Ive noticed so far is Battery life is bad..

I also have SQlite enabled and hotplug mod on and logger off.
[Samsung Galaxy Nexus] Stank0:
+1

10 char
[Samsung Galaxy Nexus] TEK112:
Here is 17 for those that want it:

http://dl.dropbox.com/u/21166889/3.0.21-franco.Kernel-nightly-17.zip

Click thanks if you use it.
[Samsung Galaxy Nexus] TechSavvy2:
I've wiped before flashing each of these and haven't had a single issue yet. All have run smooth, even on 1500. Only problem I ever had was the auto flash not working on the one build.
[Samsung Galaxy Nexus] mikeacela:
ok phone just sod and won't boot back into the rom, I get hung at a boot loop and/or the phone just keeps shutting itself off. was running AOPK m3 and 17.2 with stock kernel settings. This has never happened to my nexus yet lol. Ill have to ref lash the rom, I don't know what happened. All was good on 17, 17.1&17.2 were worse.
[Samsung Galaxy Nexus] ericmc:
My only question is how do I get rid of the "Franco Kernel" boot animation?
[Samsung Galaxy Nexus] Kidd_Funkadelic:
Rather than reflashing the ROM, boot into recovery and reflash an older version of the kernel. Much quicker and painless, no?
[Samsung Galaxy Nexus] mikeacela:
too bad I deleted it from my phone... and I can't mount storage to my mac cause it needs to use that new stupid android file transfer program. And that program needs the phone to boot to transfer files.
[Samsung Galaxy Nexus] TEK112:
You need to flash a new boot animation over it.

Try here:

http://rootzwiki.com/topic/12938-boot-animations-for-galaxy-nexus-updated-021412/page__fromsearch__1
[Samsung Galaxy Nexus] Kidd_Funkadelic:
Ugh, sorry dude. I always try to leave an out in case the unexpected happens. I guess that is one of the issues w/ not having external storage...
[Samsung Galaxy Nexus] ericmc:
Thank you!
[Samsung Galaxy Nexus] Droid_JD:
If you have the app you can disable it there. Otherwise i think it's stored in data/media? You can probably delete it from there and instead it'll play the default anim.

(i could be wrong tho)

Sent from my limited edition Galaxy Nexus!
[Samsung Galaxy Nexus] TEK112:
Franco,

I have noticed some bad lagging with 17.2. I play Drag Racing a lot and it is lagging like I am on my OG Droid. I have tried a few combinations and governors, but it would appear it does not like the higher frequencies. 1500 is unusable for me (lag swiping home screens).
[Samsung Galaxy Nexus] luckylui:
Franco... after everything gets resolved w people not being able to run at 1500. Can you bump it to 1512 :)

This phone most deff can handle it, if my Evo 3D did.. this one forsure can! :)

Edit: Question to those that have problems.. are you undervolting? I dont undervolt and leave it as the kernel came, just bump the oc and change the gov but thats it. Im running fine at 1500-350 ondemand hot plug and dalvik to cache enabled. I flashed the kernel through the franco apk n did the auto kernel flash.

Dead space is butter at 1500! Love that game :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
No undervolting here. Hotplug, francoturtle or gazelle. 17 no lag, 17.2 lag. Not real scientific, but specific enough to tell me something went wacky. Drop it down to 350/1000 lag goes away... strange. I know chips have different tolerances, but the only thing that has changed is the kernel. Logically, I have to say there is an issue there. If not, why two updates so quickly for bug fixes?
[Samsung Galaxy Nexus] RickROM:
Thanks... found the answers to my questions there.
[Samsung Galaxy Nexus] TEK112:
This answers a lot.

Taken from the GSM thread.
[Samsung Galaxy Nexus] luckylui:
I got me a boss phone if im reading the up top correctly then! :)

Phone runs perfectly fine at 1.5

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Cincybearcatfan:
Trying it now.
[Samsung Galaxy Nexus] Stadsport:
I'm still running 17, stock voltages. 200-1000 turtle on battery, and 400-1500 gazelle when plugged in. Its been plenty stable and smooth, so I guess I'll hold off on 17.2 for now.
[Samsung Galaxy Nexus] LexusBrian400:
Does anyone have a link to 17? not 17.2?
[Samsung Galaxy Nexus] luckylui:
Check two pages back chief.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] LexusBrian400:
bqahaha

Thank you!
[Samsung Galaxy Nexus] luckylui:
Your welcome. ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mikeacela:
I really wanna hear what franco might think the issue with the latest kernels might be.
[Samsung Galaxy Nexus] Chopes:
Can you tell a huge difference between hotplug on vs off with 17.2 in regards to battery life?
[Samsung Galaxy Nexus] TEK112:
Every phone reacts differently. The best way is for you to try it yourself. It doesn't hurt anything.
[Samsung Galaxy Nexus] Icey34:
New to kernel, what does hotplug do exactly?

In hopes of getting good battery life I'm running: FrancoTurtle, 350/1000. With AOKP.
[Samsung Galaxy Nexus] TEK112:
Turns off one of the cores of the CPU when the screen turns off. So, a battery saving measure.
[Samsung Galaxy Nexus] Icey34:
Do u know if that results in lag when the phone is unlock, and if it requires reboot to enable?
[Samsung Galaxy Nexus] TEK112:
That is more dependent upon your min. cpu frequency. Once the screen is on both cores kick in. You really don't need two cores to wake the phone. I have not scene any real issues with it. Also, it is changeable on the fly. It does not require a reboot to take effect.
[Samsung Galaxy Nexus] Zacisblack:
Any one else notice performance does not decrease at all when turning CPU 1 off? Makes me think if ICS even takes full advantage of two cores.
[Samsung Galaxy Nexus] neverhappy:
I noticed no lag in just unlocking the phone.

I'm not an expert, but from what I have seen, it all depends on how you custom tailor your setup. Try a few of the different govenors to fit you desire.

Francoturtle shows a little initial lag at first when I'm at 350MHz. I do not notice any lag with ondemand.

I would suspect that the best battery life will come with slight sacrifices in performance, but the beauty is you can pretty much custom tailor to what suites your needs.

I can get by with Francoturtle set for 350-1200 without it bothering me. Others want instant no-initial lag performance and therefore may choose a slightly more aggressive profile.

The only thing I can recommend from my experiences so far, is to resist the temptation to undervolt until you know the beast you are dealing with.

Undervolting can add confusion and lead you to falsely condemn a kernel when in fact it was you(me) that created the problem. Again, I'm not speaking about anything other than my experience.
[Samsung Galaxy Nexus] Icey34:
Thanks works awesome.
[Samsung Galaxy Nexus] jenicekk:
BOOTLOOP BOOTLOOP with verison 17.2 on my clean AOKP 19 - 23.

last function version is 17. :(
[Samsung Galaxy Nexus] Gwanatu:
I don't think it has anything to do with ICS not using both cores, it's just that since ICS is HW accelerated it doesn't need the CPU to make it feel smooth, and since the GPU isn't being turned off in this case it isn't affecting the performance of the OS. Dual Core is more for when you need to do heavy multitasking or performance-intensive gaming.

Works fine on my phone, been using AOKP 23 and Franco 17.2 for the last 24 hours now. Make sure you're doing a full wipe.
[Samsung Galaxy Nexus] marinersontop1:
4.0.4

Two things:

1. I am running 4.0.4 with this Kernel and noticed that the Android OS is once again a majority of battery life. Even though battery life is fine, I am curious if this is because the Kernel is based on 4.0.3 or is there something else to it?

2. Bump on the blue-ish tinge color being noticed in the top and bottom bar of apps like Gmail. Is this a known issue?

THANKS
[Samsung Galaxy Nexus] ChaoticPurity:
I fixed this by going to the color settings and turning blue to 3.
[Samsung Galaxy Nexus] TEK112:
Remember that when you wipe your caches you Android OS will be high for a while while it rebuilds those caches. To really comment on a kernel (in regards to battery life) you need about three days.

As for color, that is not normal.

---------- Post added at 10:39 AM ---------- Previous post was at 10:16 AM ----------

Can someone throw up a link to 13.1 please?
[Samsung Galaxy Nexus] delvirtud:
ALL previous versions..

All previous versions can be found here: http://www.world-of-nexus.com/download-section/category/4-franco-kernel , but of course are unsupported.
[Samsung Galaxy Nexus] GatorsUF:
Is it just me or do the latest updates seem to be worse? I think I will go back to 15.2

I was getting great batt life on 15.2 and I have tried update since and they don't seem to be as good.

No disrespect to Franco, he is definitely pushing the limits here so I love his kernel.
[Samsung Galaxy Nexus] xupru:
OCD incompatible?

This is actually a serious question of mine regarding this kernel

Sometimes I notice that I display signs of OCD (Obsessive Compulsive Disorder) and just turn the screen on and off repeatedly, either unsure if I want to do something, or just constantly checking for updates. I've realized that it's probably better to just leave the screen on, but my fingers just naturally turn off the screen now.

First of all... I have a suspicion this is bad for the phone to begin with... confirmation on that would be nice so I can force stop this habit.

Second, with the fact that turning on and off the screen actually deactivates and reactivates core with this kernel, would that make this habit even more damaging to the phone?
[Samsung Galaxy Nexus] TEK112:
Not damaging at all. It beats up battery a bit, but I can't see anything bad happening. I almost do the same constantly flipping the screen on and off. I don't think it is OCD as much as it is you are looking for something more interesting than what you are currently doing... like out of boredom.
[Samsung Galaxy Nexus] TheJ0hnman:
Exceptional battery life here on 17.2, francoGazelle and 700/1350. I've been on franco since #7, and with the exception of the bootloops on #14, have not experienced a single problem or malfunction with either the kernel or the updater application. I really don't understand why people who can't read or search are flashing kernels.
[Samsung Galaxy Nexus] Chopes:
Having your min as high as 700 doesn't cause excessive battery drainage?
[Samsung Galaxy Nexus] TheJ0hnman:
It does not, in my experience, and was previously the kernel default, though with francoTurtle governor. I should note that battery life is not my primary concern, as evidenced by my governor choice. I mention it since it seems others report the opposite experience. If anything, it's improved consistently with new versions.
[Samsung Galaxy Nexus] twiz0r:
Some people say no. Some say yes.

Francisco believes it's better. He has an explanation somewhere in his thread. I forget the reasoning behind it though.

I personally run 350
[Samsung Galaxy Nexus] sway40:
I actually gotta say running my phone at 700 doesn't drain any extra battery than it being at 350, which surprised me. With the newer ones it at 400 min now.

~ Sent from my GNexus running Cm9~
[Samsung Galaxy Nexus] Aerocaptain:
It has to do with processing duration. For a given task when the device runs at 700 the task is finished much quicker than if the device is set at 350. When set at 350, the task would take longer and subsequently eat more battery. That's of course assuming the juice required for the step up between 350 to 700 is farely negligibly in proportion to power output.....which I believe Franco had implied.

Galaxy Nexus running GummyNex w/Franco.kernel
[Samsung Galaxy Nexus] Chopes:
Good explanation.
[Samsung Galaxy Nexus] brooklyn718941:
Why dont everybody just stay on 16.2. With all these bad reviews I won't even dare flash this. Problem solved
[Samsung Galaxy Nexus] sway40:
16.2 is a really good one I'll back that up, I was getting a day of bat life with 3hrs screen time with it.

~ Sent from my GNexus running Cm9~
[Samsung Galaxy Nexus] kjwalker:
There is nothing wrong with 17.
[Samsung Galaxy Nexus] Chopes:
Had a few random reboots with 17.2, never had random reboots before.
[Samsung Galaxy Nexus] cuzzinz:
do you guys all use franco's application for adjusting cpu frequencies?
[Samsung Galaxy Nexus] TEK112:
You can use SETCPU, CPUMASTER, built in manager (dependent on the ROM), or Franco's updater. However, Franco's app is the all in one beauty.
[Samsung Galaxy Nexus] cuzzinz:
Thanks! was definitely curious as to what most people use.

TEK112 have you looked into the HP Touchpad? i also have gtab and i am so done with the screen on that thing.
[Samsung Galaxy Nexus] TEK112:
A friend of mine has one and has CM9 ICS on it. It is usable and definitely can be a daily driver over WebOS. The camera does not work, deep sleep, and wifi can be wonky. I would check out the links. I think the G-Tab is more powerful, but the TouchPad is prettier.
[Samsung Galaxy Nexus] cuzzinz:
The sanpdragon s3 with the adreno 220 is definitely more powerful than tegra2 plus... HP just released the kernel sources for their touchpads :-D

I love my gtab. just getting tired of the screen... been trying to read books and just cant stand it when i have my phone and then my wifes kindle haha.

btw... question for ALL... you guys also getting antutu scores in the 4k range? No one has mentioned antutu in a few pages...
[Samsung Galaxy Nexus] TEK112:
Yeah, I have been out of it for a little bit with the touchpad. Mainly just because I was bitter my order was canceled during their fire sale. However, the stock benchmarks of the touchpad got whooped by the 1.6OC'd G-Tab. However, with HP releasing source it is only a matter of time. The hardware is there, but the software hasn't caught up. If you can get it for under $150, it is definitely the better buy.

Anyway, sorry guys. Back on topic.
[Samsung Galaxy Nexus] cuzzinz:
So ya I am loving this Kernel.... definitely much smoother than the one on the "almost stock 4.0.4"

Hehe for bragging rights i wish the Antutu scores were a little higher... but... smooth is smooth and scores are just numbers that don't mean much.
[Samsung Galaxy Nexus] edgie168:
Bootloop city with latest fitsnugly kang. Had to revert to back to stock kernel.