yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nklenchik:
It must be my rom. I went back to m2 and it happened...gonna try wiping some things.
[Samsung Galaxy Nexus] nikulogical:
Oh man r116 feels amazing. Let's hope screen on time is greater than 4h.
[Samsung Galaxy Nexus] nodstuff:
But you are supposed to have SOME wakelocks, its normal.

Just not one that keeps your phone awake for 8 hours.

Say for example you have a process that wakes your phone 200 times and for 36 seconds in total from an 8 hour deep sleep. This is normal.

A process that wakes a phone 3 times and holds a wakelock for 7 hours and 3 minutes out of 8 hours, this is a problem wakelock.

The kernel has to hold wakelocks sometimes, they aren't the problem ones.

P.S. r116 is the **** Franco, noticeably faster from boot!

Great job and thanks for releasing 4.0.4 version so fast after release, even though it means you have to stay up so damn late.

We Appreciate it!
[Samsung Galaxy Nexus] mgear356:
Is it me or did r116 makes my build 29 even more smooth?

On the other hand I do notice my keyboard lagging abit.. anyone else feels this way?
[Samsung Galaxy Nexus] nikulogical:
agree with you on both points. i thought the keyboard lag was fixed in 4.0.4 but I guess I was wrong.

Has anyone noticed a real difference between 384 gpu and 512 gpu? Performance or battery-wise?
[Samsung Galaxy Nexus] nklenchik:
It's definitely a lot faster. The problem I'm having is my screen turning back on numerous time each time I shut it off with switchpro widget/extended controls
[Samsung Galaxy Nexus] robrob777:
running 116 with BBeast, runs perfectly.

Any plans in going 350mhz or lower as an option?.

Default to be 384mhz as it is right now
[Samsung Galaxy Nexus] ArmanUV:
@franco can you give us some details about changes in 4.0.4 aosp kernel comapred to 4.0.3? Did they fix/add anything important?

I noticed it's still 3.0.8. I really thought they were gonna use a more recent mainline build.
[Samsung Galaxy Nexus] nodstuff:
Well maybe there's your problem.

The widget. Try not using it and see how it goes, I remember reading a thread or post saying something about Widgets not working properly with 4.0.4

---------- Post added at 06:03 AM ---------- Previous post was at 06:02 AM ----------

+1 to this!
[Samsung Galaxy Nexus] nklenchik:
I did a wipe...gonna see if that helped.
[Samsung Galaxy Nexus] Diger36:
Stock battery. I don't know. All I know is now I get those battery stats and they rock :p
[Samsung Galaxy Nexus] drewlim:
Guys on 4.0.4, just wondering if i need to flash the newer radio or will the rom automatically install it during flash? Is r116 for 4.0.4 only? Tnx
[Samsung Galaxy Nexus] stellaryt:
Is there anybody use bluetooth earset？

Im use aokp b29 with r116.If I use bluetooth earset,only could make a call,but no sound with music or video.
[Samsung Galaxy Nexus] clefster:
ROMs don't usually include bootloaders or radios because that would be making an assumption about what you want, and also makes it more risky.

So go flash those yourself separately.
[Samsung Galaxy Nexus] kashix:
Flashed r116! Smooth!
[Samsung Galaxy Nexus] idan_mo:
using it happily with cm9 and updating with your app.

by any chance there will be overclock more than 1350mhz?
[Samsung Galaxy Nexus] raubkatze:
Flashed r116 on b29. UI is very smooth but using Apex had minor lags when scrolling screens. Tried both 384 and 512 with any governors - the same result. Went back on r112 and vualya - no lags...

Guys, what do you think about it?
[Samsung Galaxy Nexus] stellaryt:
Im nearly forgot what is lag long time...aokp with franco's kernel
[Samsung Galaxy Nexus] nklenchik:
There's really no need. It runs just as fast, for myself anyway at 700/1200 than it did at 1500
[Samsung Galaxy Nexus] raubkatze:
I also forgot but remembered after r116 flashed.

Any ideas?
[Samsung Galaxy Nexus] cyanoviper:
r116 is super smooth for me, its awesome!

700 to 1300 ondemand and the 384gpu version! also aokp #29
[Samsung Galaxy Nexus] raubkatze:
Sorry but where did you find 700 and 1300 in franco kernel?

Maybe 729 and 1344? )
[Samsung Galaxy Nexus] stellaryt:
I use r116 with b29 since franco released

it.Till now they work nice and smooth as usual.I use hotplug governor.
[Samsung Galaxy Nexus] grumphy:
+1. No issues so far.

AOKP B29. FK r112.
[Samsung Galaxy Nexus] raubkatze:
I wrote that tried with any governors (including hotplug).

Flashed r116 again and set Nova as default launcher - works very smooth. WTF... I really had not any lags with r112 using Apex.

I'll use Nova from this time.
[Samsung Galaxy Nexus] cyanoviper:
i didnt remember the exact values
[Samsung Galaxy Nexus] raubkatze:
Sorry... It was a little stupid jest)

But seriously there are no stock values in franco kernel. It has: 384, 729, 1036, 1228 and 1344 MHz.
[Samsung Galaxy Nexus] dimmanramone:
Anyone using 116 with mcr?
[Samsung Galaxy Nexus] bryant_16:
Can this be used for the latest gsm 4.0.4??
[Samsung Galaxy Nexus] sago62:
Yesss....it is for 4.0.4 :-)
[Samsung Galaxy Nexus] raubkatze:
Why not? I use it with AOKP b29. It's 4.0.4

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] bryant_16:
How do I root my stock 4.0.4 gsm and flash this kernel?
[Samsung Galaxy Nexus] franciscofranco:
Using the search function, this is not a root thread.
[Samsung Galaxy Nexus] modstorm:
Hi! Is there a way I can edit to kernel to add more steps to the cpu speed so I can OC to 1.65GHz?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bryant_16:
I just flashed the stock rom to 4.0.4, I'm not sure whether do I still need to root my phone to flash this custom kernel.
[Samsung Galaxy Nexus] modstorm:
Do you have Clockworkmod installed? I'm not sure but I think you can flash it by downloading the .zip and installing it using CWM. However you wont be able to auto-flash the kernel from Franco's app without root.
[Samsung Galaxy Nexus] bryant_16:
Yup, I think I have the CWM installed.

So I can straightaway use CWM to flash this custom kernel?
[Samsung Galaxy Nexus] raubkatze:
If you don't need high performance, very fast and smooth UI with great battery life, don't do it.
[Samsung Galaxy Nexus] Vangelis13:
Franco, 116 is an outstanding kernel! Fluid, good on the battery (2hrs with 30 minutes screen & 15 minutes in calls and it's only lost 7% since unplugged) and stabile.

Respect. :thumbup:
[Samsung Galaxy Nexus] modstorm:
Yes, just download the .zip file from this thread, reboot into CWM and flash :) However I do recommend rooting as you will be able to use all of the features of this kernel using Franco's app.
[Samsung Galaxy Nexus] bryant_16:
Which one do I download? The Milestone 2 or nightly?

---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------

What feature are you referring to?
[Samsung Galaxy Nexus] raubkatze:
Yes you can use CWM or franco.Kernel Updater. Second way on my opinion is correct as Franc's app gives you more kernel customization tools.

---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------

See in first post.
[Samsung Galaxy Nexus] bryant_16:
r116 or milestone 2 to flash?
[Samsung Galaxy Nexus] raubkatze:
M2 is stable release but r116 exactly for 4.0.4

I tried M2 on AOKP b29 - works fine.
[Samsung Galaxy Nexus] EnIXmA:
M using r116 on aokp m4 with no problems. It seems like this kernel also supports 4.0.3. 116 is rock solid.

thnx Franco.

I saw your interview live on Google plus yesterday. Good stuff :)
[Samsung Galaxy Nexus] stellaryt:
I use NOVA,but I have tried apex.No big difference for performence.I have no idea what could help u.Just wipe,flash as usual.
[Samsung Galaxy Nexus] franciscofranco:
Flash milestone 100, I hear it takes you on a cruise to the moon ;)
[Samsung Galaxy Nexus] raubkatze:
Thanks anyway! Probably it's individually but I see the diference between nova and apex performance. And unfortunately see apex lags when using it with r116.

Now using nova - no issues.
[Samsung Galaxy Nexus] bryant_16:
Does it help in battery life performance?
[Samsung Galaxy Nexus] raubkatze:
I really don't know what it will give you but us it gives the best performance and the great battery life)

Try to read this thread. We have posted here our screenshots with comments.
[Samsung Galaxy Nexus] bryant_16:
Understood would like to see how the performance and the battery life play out..
[Samsung Galaxy Nexus] yeeson:
Try this configuration：

Red：275

Green：290

Blue：400

GAMMA：7,12,19
[Samsung Galaxy Nexus] yyz71:
francos kernels seems to mesh nicely with my phone :)
[Samsung Galaxy Nexus] leelaa:
Franco would you say that the battery drain in 4.0.2 was kernel issue? Seems to be fixed in 0.4, so will your kernel be just as good in terms of battery?
[Samsung Galaxy Nexus] raubkatze:
As I remember franco.kernel suports 4.0.3 and 4.0.4. Maybe the problem is here?
[Samsung Galaxy Nexus] cyanoviper:
hi everyone,

i just rain into the wifi bars tunring grey/no internet issue again. no idea what is going on. last_kmsg wont help there will it? could i provide anything else if it happens or has anyone new insights for me?
[Samsung Galaxy Nexus] nodstuff:
Very unusual battery drain issue last night, unplugged my phone 9 hours ago at 100%, woke up to 76%.

Checked betterbatterystats as you do but there were no wakelocks worth talking about, the longest was maybe 8 seconds or something.

It has me confused!!
[Samsung Galaxy Nexus] raubkatze:
Try to set Min cpu to 729 MHz
[Samsung Galaxy Nexus] arhung:
how can i change it??
[Samsung Galaxy Nexus] zephiK:
buy Franco Kernel from the play store and use his app to change it.

alternatively, you can change it the hard way thats in his op post

https://play.google.com/store/apps/details?id=com.franco.kernel&feature=search_result
[Samsung Galaxy Nexus] cr0wnest:
Just flashed r116 w/ GPU overclock. Games dont perform as well as r98 with 460 GPU but still very decent, much better than stock. I think we found a sweet spot here. ;) Just gotta test the battery life now.
[Samsung Galaxy Nexus] raubkatze:
What build did you flash? There are 2 builds with GPU overclock: 384 and 512 Mhz.
[Samsung Galaxy Nexus] spaceman860:
I lost 4% battery life after 9 hours of sleep with wifi on b29 r116 512 MHz I think we have a winner :D super fast

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] bryant_16:
If battery life is good, will flash it straightaway.
[Samsung Galaxy Nexus] bendirkss:
4h? What settings do you use ?
[Samsung Galaxy Nexus] nodstuff:
My drain problem is sorted, dunno what caused it but a reboot sorted it.

Betterbatterystats said all was OK, os battery stats showed that the phone was awake 95% of the time and cpuspy showed no deep sleep, only 384mhz, and I have min set to 729.

After a reboot its all good, deep sleeping no prob now so it was just a fluke I think.

Thanks again Francisco!
[Samsung Galaxy Nexus] cyanoviper:
about the grey bars: my min freq is at 729! it seemed to have solved the issue at first but it came back
[Samsung Galaxy Nexus] raubkatze:
Probably it was a problem with battery cache?

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

Did you set "Set at boot" with Min cpu 729?
[Samsung Galaxy Nexus] nikulogical:
Auto brightness on demand 700/1300 I've been getting ~ 3h with Franco's and 3h30m with lean kernel so I thought with the new 4.0.4 it would give me around 4h.
[Samsung Galaxy Nexus] nodstuff:
Nah. It was coz the phone wouldn't deep sleep.

No big deal! ;)
[Samsung Galaxy Nexus] cyanoviper:
does it make a difference if i set it manually or if it is set automatically at boot?
[Samsung Galaxy Nexus] raubkatze:
Yes. If don't set to "Set at boot" after reboot you will stay with stock value.
[Samsung Galaxy Nexus] bradm23:
116 is the bees knees.
[Samsung Galaxy Nexus] bendirkss:
What ROM? I got 3h once with bamf but usually can't get over 2
[Samsung Galaxy Nexus] rgbc:
Just tried out Play Music and Bluetooth streaming is working fine. Check to see if your paired device says (No Media) beside it or if Media Audio is unchecked in the paired device setting, if so try unpair/repair
[Samsung Galaxy Nexus] stellaryt:
EDIT:

I just flashed back to r112,it works well.

I think is r116's problem?

I'm sure setting is right.I resotre my backup with r112 which I was backuped after clean install it workes well.
[Samsung Galaxy Nexus] windmark:
For once I actually think I'm going to wait with flashing a new nightly ^^ I really enjoy 112 and it's running super smooth, and I think I'm waiting for a more stable 4.0.4 rom release before flashing 116.

Or what do you think, is there a good reason for updating to 116 from 112 if staying on 4.0.3? :)
[Samsung Galaxy Nexus] hasnol143:
No I'm waiting for the same thing, til aokp releases a stable 4.0.4
[Samsung Galaxy Nexus] nikulogical:
Always been on aokp. Running b29 right now which is amazing.
[Samsung Galaxy Nexus] Diger36:
Went back from r116 to r112. R116 (384) was lagging for me on AOKP B29. R112 rocks although it wasn't specially released for 4.0.4.
[Samsung Galaxy Nexus] dwang:
With r116 and a 4.0.4 rom I think we are finally approaching iPhone 4s territory in terms of speed and smoothness.
[Samsung Galaxy Nexus] cr0wnest:
Pretty sure it was 384. I couldnt find the ones with 512? Unless i was looking in the wrong area.
[Samsung Galaxy Nexus] raubkatze:
You can flash it with franco.Kernel Updater or download from ftp - http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/
[Samsung Galaxy Nexus] rgbc:
I'm using AOKP b.29 + FK r.116 + UGLA4 baseband with Bose series 2 headset, voice quality, voice dial and A2DP streaming are all working pretty much flawlessly.
[Samsung Galaxy Nexus] 02busa:
THANKS!!! I needed that laugh this morning!
[Samsung Galaxy Nexus] cr0wnest:
I downloaded from the ftp gpu_384mhz folder, so my kernel should be the 384MHz GPU. Where can i find the 512MHz GPU kernels? I didnt buy the franco.Kernel Updater app so i dont know :p
[Samsung Galaxy Nexus] bendirkss:
Ya I've always been on aokp also. Just trying out bamf though, its very smooth and simple
[Samsung Galaxy Nexus] zephiK:
512 is what in its main folder.... when u go into 384, its 384... leave 384 and its 512
[Samsung Galaxy Nexus] eRajesh:
Umm when does the GPU actually ramps up to 384MHz? I can see no improvements in benchmarks with the 384MHz or the 512MHz kernel
[Samsung Galaxy Nexus] skyhigh2004:
Maybe this. I know for a fact on 4.0.1 if I UV on 1200 MHz below 1050 it rebooted that's why I found that 1100 was my sweet spot for that frequency.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stickjohnonaah:
Finally able to try this kernel and is very impressive for a stock speed! I definitely saw a large improvement on read/write speeds for the SD card based on various performance test apps. Well done. Can't wait to try an oc version. Haven't had it installed long enough to tell on battery life. Currently old set up was gummynex with his included kernel now testing yours. Thanks
[Samsung Galaxy Nexus] franciscofranco:
New nightly is up.
[Samsung Galaxy Nexus] HaRdC0r3:
New MD5 for new nightly?
[Samsung Galaxy Nexus] Jrbourque:
Just updated...will kill battery before sleep and then put it to test tomorrow
[Samsung Galaxy Nexus] skinote:
Franco, I am using a Verizon GNEX and your 2nd nightly is the first kernel I've found to be able to mount external storages (though I realized I may have been doing something else wrong, so there are perhaps others). It seems like nightly 3 includes some changes that might be specific to the GSM GNEX - is that the case, or can I use it?
[Samsung Galaxy Nexus] theboo7:
Flashed on LTE and running great, Go ahead
[Samsung Galaxy Nexus] skinote:
no OCing in nightly 3 though?
[Samsung Galaxy Nexus] theboo7:
No, but I don't see how that's really necessary at this point.
[Samsung Galaxy Nexus] skinote:
That's fine, I just wanted to make sure my not seeing it wasn't some error I was experiencing.
[Samsung Galaxy Nexus] MFD00M:
Great kernel, thanks for making this compatible for the lte gn.
[Samsung Galaxy Nexus] skdubg:
Hi Franco,

can you reduce the RAM size which would be used by the GPU?
[Samsung Galaxy Nexus] eRode:
Anyone managed to get cifs and vpn working ?
[Samsung Galaxy Nexus] MontAlbert:
stupid question- how do we know that undervolting is not working and its not just a protection thing?

I mean if undervolting wasnt working why do we get reboots when we drop past a certain level? Obviously if it drops to a stupidly low level it seems to be working- but maybe thats a safety thing. How do we explain the reboots when voltage is dropped from say 850mV for 350MHz down to 750mV? If undervolting wasnt working why would it then reboot?
[Samsung Galaxy Nexus] hosmsdos:
There is a bit lag with nighty3, nighty 2 was faster.
[Samsung Galaxy Nexus] sim_jim:
+1
[Samsung Galaxy Nexus] pattsy:
+1 ... Looks like it takes a litle longer to "wake up" when unlocking it... e few sec's later it's all smooth again. #2 was more responsive after wake up...
[Samsung Galaxy Nexus] Vangelis13:
+1 on those, however battery consumption seems to have gone down.
[Samsung Galaxy Nexus] Shetlander:
I too have gone back to nightly 2. I found with 3 the bit of lag but also 3D performance took a huge nose dive. Not sure if thats why GTA is not working but for me nightly 2 is better.
[Samsung Galaxy Nexus] jkoljo:
After multiple hours of debugging I found out what was the problem with GTA III not running properly on 4.0.3 AOSP build + this and some other kernels. It is the /system/bin/sdcard binary, which causes com.rockstar.gta3 to fail and close. Replace it with the stock one (in recovery, I might add), and GTA III works flawlessly. Faster than with stock kernel btw :)

So please remove the sdcard tweak in future builds.
[Samsung Galaxy Nexus] raubkatze:
512 - franco.Kernel-r116.zip

---------- Post added at 09:19 PM ---------- Previous post was at 09:16 PM ----------

Yes actually oc. Try AnTuTu Benchmark
[Samsung Galaxy Nexus] eRajesh:
You mean I actually need to OC the CPU for the GPU to clock up to 384MHz?

And if yes, I did that. The 3D scores in Quadrant actually decreased after that. >_<
[Samsung Galaxy Nexus] raubkatze:
I meant that kernel already has overclocked (oc) GPU to 384 and 512 MHz.

Quadrant doesn't show correct benchmark on my expirience. Try AnTuTu Benchmark app.
[Samsung Galaxy Nexus] eRajesh:
I used Nenamark 2. No improvements :(

Flashed the 384MHz kernel again. OC'ed to 1344MHz using Franco's app. Ran AnTuTu. No improvement. WTF?
[Samsung Galaxy Nexus] franciscofranco:
Nenamark 2 scores:

307mhz is 24fps

384 is 27,5fps

512 is 31fps.
[Samsung Galaxy Nexus] alvespt:
hello i currently use the 29 version of AOKP rom and this kernel, im new to both, just instaled, can anyone tell me which is the best cpu config for batery? thanks!
[Samsung Galaxy Nexus] raubkatze:
Methinks the best balance between performance and battery life is:

- r116 with 384 OC GPU

- Min cpu 729

- Max cpu 1228

- hotplug governor
[Samsung Galaxy Nexus] bendirkss:
Ive been getting some lockscreen lag for a while now, and I mentioned my music lag earlier. I set my min to 700, on latest nightly. Anyone else getting this?
[Samsung Galaxy Nexus] ArmanUV:
100% agree.
[Samsung Galaxy Nexus] ArmanUV:
Disable autobrighness. 99% of the time that's the issue. I don't know why Google didn't fix it in 4.0.4. It's a ridiculous bug to exist in the latest offering from Google.
[Samsung Galaxy Nexus] raubkatze:
I had lags in Apex with both 384 and 512 oc gpu builds. Now on Nova - works smooth without any lags. Have not issues with music.
[Samsung Galaxy Nexus] franciscofranco:
Can you download no frills from the market change the io scheduler to deadline and tell me if music works fine again?
[Samsung Galaxy Nexus] bendirkss:
Ya I already disabled it a month ago cause of lag so its not my issue now.
[Samsung Galaxy Nexus] bendirkss:
I can do that in bamf settings. Or should I use frills?
[Samsung Galaxy Nexus] robto:
Thats nice and sad at the same time ....
[Samsung Galaxy Nexus] alvespt:
what do you mean by?

- r116 with 384 OC GPU

- hotplug governor
[Samsung Galaxy Nexus] raubkatze:
I meant that I'm using franco kernel nightly build r116 (OverClocked GPU to 384 MHz) with hotplug governor.

By the way try the franco.Kernel Updater app. It gives more kernel customization tools and will make flashing, setup etc very comfortable.
[Samsung Galaxy Nexus] franciscofranco:
No its the same thing. Can you reproduce the bug with deadline?
[Samsung Galaxy Nexus] as0k:
What is best to save battery at average usage (not idle time); hotplug or onDemand governor?

Im using the #r116 512 kernel and 4.0.4 custom rom :)

Thanks
[Samsung Galaxy Nexus] robto:
Hotplug is like on demand. Only difference when phone is idle.
[Samsung Galaxy Nexus] raubkatze:
Hotplug. This is ondemand governor + dinamic hotplug. Hotplug shut down cpu1 when it doesn't need.
[Samsung Galaxy Nexus] spaceman860:
Aokp b29 Franco r116 512mhz hot plug gov 729 1344 CPU wifi on :D

View attachment 975864

View attachment 975876

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] nikulogical:
Same set up except I'm using ondemand. I got 3h40m screen on time. Gonna try 384 gpu to see if it makes a difference.
[Samsung Galaxy Nexus] bigeyes0x0:
I got a crash right after reinstalling ARHD 3.0 and franco nightly 160 (384MHz). Here's the last_kmsg.

I haven't got the chance to do anything except finishing the initial boot screen, go to settings, turn on wifi and change some sound settings, so the kernel should have been running stock.
[Samsung Galaxy Nexus] chardd23:
Anyone knows what causes this to happen?
[Samsung Galaxy Nexus] blitz911:
Media scanner? If it is that, it could be a corrupted media file..think it used to happen on either my nexus one or mt4g, ate the battery like crazy..just throwing it out there..
[Samsung Galaxy Nexus] chardd23:
came from a fresh wipe(AOKP) all is well until i autoflashed francoKernel :(
[Samsung Galaxy Nexus] Ownatik:
116 nightly, latest cm9 kang, moderate use. My GN is a very stable and fast phone. I wouldn't trade it for any other.
[Samsung Galaxy Nexus] clefster:
Got an SOD running 116 on a 4.0.3 ROM (B28 of AOKP) .. no last_kmsg available. Stock kernel settings.
[Samsung Galaxy Nexus] winner00:
On #116 and its running great! Never had a SOD with your kernels and I have UV also. Running my CM9 kang.
[Samsung Galaxy Nexus] ChongoDroid:
+1 except aokp b29

I've never had a sod either but on your earlier kernels I had occasional wake lag. I think this latest nightly is the perfect balance of performance and battery life/stability.

**** a battery benchmark let's see who can go the longest without a reboot. :D
[Samsung Galaxy Nexus] bendirkss:
Switching to deadline didn't fix it. Still s lot of lag
[Samsung Galaxy Nexus] jkoljo:
Sorry for being late (I am doing the national service, so I have limited free time..), I tried with Deadline too, and it did not fix my problem with music lag. I also noticed that when I am watching a movie and doing something in the background such as file dl, it stutters every 10 seconds or so.
[Samsung Galaxy Nexus] bryant_16:
Erm.. so many problems with this r116?

Anyone can confirm??
[Samsung Galaxy Nexus] raubkatze:
I have not issues except lags with Apex that I wrote above. No SoDs till now.