Originally Posted by littleasian

can anyone explain what the "governor" listed in the refers to? i see that under changelog for nightly #9 that some option for disabling cpu core 1 is possible no matter what the governor is. i'm trying to get the max battery life for my phone so if there's a way to disable the core to save battery i'm all for it.

also, this kernel is already undervolted correct (i'm going by whats listed in the changelog)? so i don't need to install setcpu or anything to mess with it?

thanks everyone.

To answer the second question, it is undervolted by default but somewhat conservatively. At current, you cannot undervolt through setcpu but it seems franco's working on that for an upcoming build. People have had issues with custom undervolting in past versions. As for governor, conservative should be the best for everyday usage.

Originally Posted by johantheolive

To answer the second question, it is undervolted by default but somewhat conservatively. At current, you cannot undervolt through setcpu but it seems franco's working on that for an upcoming build. People have had issues with custom undervolting in past versions. As for governor, conservative should be the best for everyday usage.

Yes. I've said it countless times the UV interface was ****ed up and was creating more problems than it was solving, so I decided to take it off either until I or someone fixed it.

hey guys...i hope this isn't off-topic as i'm curious about these kernel wakelocks.

running AOKP milestone 2 + franco #12, i lost about 7% overnight. I disabled gtalk, maps, g+, and latitude and had both NFC and wifi off. i've gotten the BBS dump and looking at the other wakelocks but i was wondering if these kernel wakelocks are abnormal i understand most of the times it is a rogue app but i want to know if there is anything up with the kernel wakelocks. specifically, this one that has a high count (even though it has no time used)

"secril_fmt-interface" ():  (0 s) Cnt:(c/wc/ec)863/0/0 0.0%

================
Kernel Wakelocks
================
"alarm_rtc" (): 1 m 55 s  (115 s) Cnt:(c/wc/ec)189/0/78 0.4%
"mipi_link" (): 1 m 13 s  (73 s) Cnt:(c/wc/ec)193/19/0 0.3%
"nfc" (): 1 m 10 s  (70 s) Cnt:(c/wc/ec)145/9/145 0.3%
"PowerManagerService" (): 1 m 6 s  (66 s) Cnt:(c/wc/ec)311/0/0 0.2%
"radio-interface" (): 21 s  (21 s) Cnt:(c/wc/ec)41/0/0 0.1%
"alarm" (): 20 s  (20 s) Cnt:(c/wc/ec)245/115/0 0.1%
"musb_autosuspend_wake_lock" (): 5 s  (5 s) Cnt:(c/wc/ec)147/0/0 0.0%
"max17040-battery" (): 2 s  (2 s) Cnt:(c/wc/ec)114/0/0 0.0%
"event2-202" (): 1 s  (1 s) Cnt:(c/wc/ec)158/0/0 0.0%
"vibrator" (): 1 s  (1 s) Cnt:(c/wc/ec)25/0/0 0.0%
"twl6030 adc" (): 1 s  (1 s) Cnt:(c/wc/ec)575/0/0 0.0%
"KeyEvents" ():  (0 s) Cnt:(c/wc/ec)1456/0/0 0.0%
"secril_fmt-interface" ():  (0 s) Cnt:(c/wc/ec)863/0/0 0.0%
"gpio_input" ():  (0 s) Cnt:(c/wc/ec)20/2/0 0.0%
"mmc0_detect" ():  (0 s) Cnt:(c/wc/ec)225/0/1 0.0%
"power-supply" ():  (0 s) Cnt:(c/wc/ec)5/0/0 0.0%
=========
Processes
=========
kworker/u:4 (0): Sys: 6 s  (6 s) Us:  (0 s) Starts: 0
kworker/u:1 (0): Sys: 6 s  (6 s) Us:  (0 s) Starts: 0
kworker/u:2 (0): Sys: 5 s  (5 s) Us:  (0 s) Starts: 0
kworker/u:0 (0): Sys: 4 s  (4 s) Us:  (0 s) Starts: 0
kworker/u:3 (0): Sys: 3 s  (3 s) Us:  (0 s) Starts: 0
com.android.mms (com.android.mms.Messaging): Sys:  (0 s) Us:  (0 s) Starts: 1

thanks and if this is completely unrelated or you need anything else please let me know

4.0.2

---

I'm currently on 4.0.2 and hear terrific reviews on franco kernal, just wondering would this work on 4.0.2

Originally Posted by karthicr25

I'm currently on 4.0.2 and hear terrific reviews on franco kernal, just wondering would this work on 4.0.2

Nope, needs to be a 4.0.3 ROM. Try out AOKP build 17, working great with #12

Originally Posted by chikimonke

Nope, needs to be a 4.0.3 ROM. Try out AOKP build 17, working great with #12

where can i find that

Originally Posted by karthicr25

I'm currently on 4.0.2 and hear terrific reviews on franco kernal, just wondering would this work on 4.0.2

If you look at the name of the thread...what do you think. Could there be anything in the topic that tells you will this work on 4.0.2?

The answer starts with N

Originally Posted by karthicr25

where can i find that

here to go:http://rootzwiki.com/topic/11455-rom...guro-build-17/

Hey guys, should be getting my nexus delivered today, been following this thread since day one, so I pretty much know what needs to be done. One question I have is regarding the radio and kernel compatabillity. I will be using gsm (greece) and I saw there is 2-3 radios I can use (XXKK6 and XXKL1).

Has anyone tried both, and which do you recomend works better with Francos kernel?

Secondly, which bootloader is recommended primekl01 or primekk15???

Thanks for any help!

Originally Posted by franciscofranco

After two long days for real life time I'm back for more ownage.
Things that are coming (or are, at least, projected in my head for now):

- Completely renewed UV tables
- GPU OC changeable via sysfs interface (using the terminal or my app)
- Make the kernel leaner - less is more ©morfic - and thanks Ezekeel for finding out that the battery drain while idle is in fact caused by FIQ_DEBUGGER disabled (which I already had it fixed for a long time, but nevertheless it's very good to know)
- SMP/hotplug/freezer code fixed from a mainline patch - some lockups happened when using the hotplug governor and the hotplug_enable mod that I created could, sometimes, cause unstability, and that is now fixed
- New wi-fi driver from fugumod (thank you)
- Some other minor things + app changes

There is no ETA, so don't ask.

Hi,
It looks good,thanks for the gpu overclock ,i guess the maximum is always at 384Mhz?
If there is not any improvement with the gpu overclock as has been reported by you,for example in benchs i noticed that to,with or without gpu overclock it makes no difference,does this really work?I refer to another kernel where it is specified "Fixed GPU OC to true 384 MHz" or your kernel has already fix this?
Just a question...
Perhaps it's me or my phone ,but with the last nightly,so without gpu overclock,the transitions and animations are not smoother than before (so with gpu overclock).
In any case it's perfect
Thanks
I think you have not seen my post,i repost it...