yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] hnx6310:
Great... I use franco Kernel 15.2

I hope to do increasingly more stable, not vice-versa.

Good Luck
[Samsung Galaxy Nexus] CaspaTheGhost:
16.2 is running well for me with MCR Ir11. Whole new setup as I was running Apex 1.0.2, but now it's bedded down everything is running smoothly. Battery is also looking impressive with Franco's default setup...

Kudos to you Franco...
[Samsung Galaxy Nexus] LuffyPSP:
bought the Franco.updater to support ya! :D
[Samsung Galaxy Nexus] franciscofranco:
Thank you. I will add that to the OP.

While that is 100% true gives me, again, a lot of extra load of work that I can spend improving my kernels, after all, thats my "job" here. I'll dedicate some of my time later today improving the OP with some "obvious" information just like you suggested. Thanks.
[Samsung Galaxy Nexus] The Kid Cassidy:
Just wanted to say THANK YOU Franco! been running 16.2 since release and im getting great battery life (screenshot) and its super fast....This is the first i have ever ran your kernels and i bought the updater app to support...keep up the good work!

I do have one question though...In the changelog it says the min cpu is now set to 400...inside rom control or your updater app there is no 400 option? 350 is the lowest setting?
[Samsung Galaxy Nexus] AzzaD:
go to the market and update his app
[Samsung Galaxy Nexus] The Kid Cassidy:
I'm on the most up to date version...:confused:
[Samsung Galaxy Nexus] jdk82:
Did you wipe the cache and dalvik cache before you flashed the kernel? Also, did you unset any "Set At Boot" options you may have check for cpu speed options? Other than that, I would suggest flashing the kernel again.

Edit: Oops :rolleyes: Did you install the kernel via the franco app? If so, none of the above applies to you (other than the "Set at Boot" part, that's still a good idea AFAIK).
[Samsung Galaxy Nexus] petsasj:
Since most of you seem to prefer the 15.2 kernel, can you please upload it either here or in the wiki?

TIA
[Samsung Galaxy Nexus] The Kid Cassidy:
Yea, i did all that and I don't have nor did i prior have anything set at boot? But I really don't care since still fast as hell and great battery life...I was just curious that's all...
[Samsung Galaxy Nexus] Colpophage:
I've found that my GNex has had exceptional GPS, stock, rooted stock, custom ROM, other kernels, franco kernel.

Blatantly blaming the kernel without reading the many posts here saying they get great GPS signal is unfair.

You should try to find what it is about your specific setup that needs to be fixed. We'd all be happy to help with more info (ROM, other mods, carrier, location, baseband).

Swyped on my rooted AOKP(22)-franco Galaxy Nexus with Touch Recovery using XDA App
[Samsung Galaxy Nexus] aeo087:
FrancoKernel 14 Performance

Franco, I love your kernel but I haven't been able to get back the incredible performance that v14 gave me with the new updates. Browser performance, responsiveness, etc... Any chance I can get v14? I lost the file :( I've read that the new Kernels have a bit better battery life but I personally dig performance more than an hour or so more of battery.

Great work btw, your kernel is definitely the best out there. I got your app and it makes updating very convenient, could you add a little archive for kernel versions? also, an option to increase the GPU clock to 384MHz :) (I've seen noticeable difference in 3D games and the load time of the multi-task panes).

Thanks for your awesome work!
[Samsung Galaxy Nexus] samizad:
Francisco has mentioned a few times that he will not support older kernel versions. The GPU overclock issue has also been discussed lots on this thread.

For older versions of the kernel see http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] edwin124:
do any of you notice the phone run a little warmer then usual when using it? mine heats up more then normal or when i had it stock/other kernel.

this has been the best kernel for me with performance and battery life, but it does run a little warm.
[Samsung Galaxy Nexus] drawde40599:
Nope not even slightly warm here (97°) been on it for an hour, and I have the 2000mah Samsung Korean battery . Now if I'm on a charger while using phone goes up to bout 114° F but that's normal .
[Samsung Galaxy Nexus] EspadaKiller:
Where do i find the color control option? :O
[Samsung Galaxy Nexus] edwin124:
hmm i'll have to check the temp when it goes up to see how bad it gets, it's at 89.4 right now but i'm sure it'll go up once i'm on it

---------- Post added at 07:15 PM ---------- Previous post was at 07:07 PM ----------

within about 3-5 minutes of using it it jumps up to about 100-103 degrees. Anyone have any idea? I might just try and download a new copy of it and flash it to my phone again to see if that'll help any
[Samsung Galaxy Nexus] samizad:
Buy the franco.kernel updater app from the Android Market. This little app gives you all the control you need including overclock, undervolt, colourcontrol and automatic check and flash of the latest kernel.
[Samsung Galaxy Nexus] jdk82:
I would suggest starting with that, something is not right there. What ROM are you using?
[Samsung Galaxy Nexus] Arrio:
Mine even went overheating and rebooted itself after browsing for an hour.
[Samsung Galaxy Nexus] drawde40599:
Ur good that's normal, I've been on for an hour I'm at 100° right now,my phones go from 90-100 ° both my euro, and at&t galaxy s2's do this and my skyrocket its cause there so thin made of plastic and battery cover is really thin its normal trust me never had a issue if I'm on phone while charging it gets up to 114° give or take
[Samsung Galaxy Nexus] jdk82:
I've never had my phone get that hot unless under very high load, and for very short periods of time.
[Samsung Galaxy Nexus] drawde40599:
Strange cause all my Samsungs do, u can't feel 100° u have to physically check with an app . I've called Samsung its normal . Guess u have special phone .
[Samsung Galaxy Nexus] a4840639:
Hi Franco, thanks for your brilliant works.

Can I ask for nls_utf8 module of this kernel? CIFS without UTF8 support is really not very usable.
[Samsung Galaxy Nexus] edwin124:
i deleted it off the internal sd card, flashed the bond kernel, redownloaded the franco kernel and flashed it and it was still getting up to about 100 :confused: i'm running slimc ICS 2.4, but i also noticed it got warm when i was running apex rom

---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------

mine hasn't been that bad and hopefully it never gets to that point as i really like this kernel

my galaxy s2 didn't ever get this warm, which is what worries me a little
[Samsung Galaxy Nexus] mrgeo:
Got a bootloop when I installed this to AOKP b23. Had no problems when I was using it on M3 though.
[Samsung Galaxy Nexus] ratson:
this must be rom related. do a full wipe than retry
[Samsung Galaxy Nexus] Mukosil:
i had with stock kernel and 1,2ghz in AnTuTu benchmark : 5868 points

with franco kernel on 1350 : 5673 points

something is wrong here
[Samsung Galaxy Nexus] minipaolo:
Since I flashed AOKP b23 it looks like it doesn't like deep sleep anymore (16.2).

Edit: fixed.
[Samsung Galaxy Nexus] wallendiaz:
I have a question. I can use the Franco app with another kernel????
[Samsung Galaxy Nexus] samizad:
I guess this is a joke but, just in case, no you can't.
[Samsung Galaxy Nexus] anoraknophobia:
Who cares about benchmarks... Do you notice an lags or problems ?

Mine is running at 700-1200 and i got around 4800 AnTuTuTuTu points.

Do i care ? No. Does it run smooth and without problems ? Yes.
[Samsung Galaxy Nexus] Antob125:
As Roman said aokp b23 was never officially released. You must have snuck in while he was updating and for that, the update was corrupt. He said it on twitter.
[Samsung Galaxy Nexus] renaud:
yes, and it's antutu.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yungboss22:
Yes u can.im on leankernel and the franco app work well
[Samsung Galaxy Nexus] franciscofranco:
Yes you can, nothing wrong with it ;)

Thanks everyone for all the feedbacks and comments. I've been a little busy but I am here reading and getting ready to deploy another bug fix update later today.
[Samsung Galaxy Nexus] TheInVisibleGoD:
Thanks mate! :)

Just bought my Gnex yesterday, and guess what... my first custom kernel was your kernel 16.2, and also bought your app (must have btw)! ;) I have to say that I'm very pleased with it, very good performance and even better battery life than the stock one at least!

Keep up the great job mate!
[Samsung Galaxy Nexus] nikulogical:
Anyone getting an issue when their clock freezes? It happened twice to me already. My main system clock stays on one time. To reset it back I have to go to settings and unchecked and check auto time. Funny thong is my beautiful widget time is perfect ita just the system time in the corner that's affected. Running aokp m3 and 16.2 francoturtle 400/1200
[Samsung Galaxy Nexus] danielvc:
Is a known bug with AOKP, fixed in version 23.
[Samsung Galaxy Nexus] Unoid:
5ghz wifi doens't seem to work.

on 16.2 and AOKP M3.

It shows my 5ghz Acess point but when I try to connect is disappears.

5ghz worked when on stock 4.0.1
[Samsung Galaxy Nexus] nikulogical:
have you tried version 23? My only issue is the risk of introducing new bugs.
[Samsung Galaxy Nexus] mrfenyx:
boot loop

everything worked just fine for almost 24 hours while using it with AOKP M3. Then, all of a sudden my phone went blank. Had to remove battery to restart it, now it's in a bootloop. Tried wiping, reflashing, still nothing...any ideas?
[Samsung Galaxy Nexus] Booker-T:
I have been following Franco kernel every build and I found #13.1 has the best battery life and system stability.
[Samsung Galaxy Nexus] hasnol143:
What's your radio? You might need to update it
[Samsung Galaxy Nexus] lynxboy:
+1 I always end up going back!

Regards.
[Samsung Galaxy Nexus] minipaolo:
b23 was released today anyway

The latest build number is 23. Released on Feb 13, 2012.

Make sure you grab the newest Gapps (Feb 12, 2012)
[Samsung Galaxy Nexus] taney:
This currently works for me. Netgear WNDR3700 AP.
[Samsung Galaxy Nexus] taney:
All my apps seem to run fine except for Plants versus Zombies. Anyone use that app besides me?
[Samsung Galaxy Nexus] kabauterman:
Had some little glitches right now with the 1112 non OC :(
[Samsung Galaxy Nexus] Rey-619:
Dont know whether it has been mentioned before:

An usere on google+ reported this graphical glinches on stock nexus with stock kernel.

he is often pushing files via adb and this issue allways is showing after pushing files.

maybe there is an problem with the adb driver
[Samsung Galaxy Nexus] bdcdxw:
I flashed the 11/12 oc version. The android os still drian the battery. The other thing is if I leave the phone for a while standby and then wake up it by press the power botton, the screen need 2-3 seconds to response from off to on. It is really annoying:(
[Samsung Galaxy Nexus] franciscofranco:
The reported bugs are all too strange for me, but I always have some "solutions". I'll release another build in a one/two hour tops.
[Samsung Galaxy Nexus] Rey-619:
ahhh forgot to say something... i had none of this issues untill yet! :)
[Samsung Galaxy Nexus] beekay201:
After flashing your kernel first time ever, i did delete that file. After that, I already built and flashed rom more than once; so, i forgot to delete it again :eek:

But I had the file yesterday on 10112011 kernel also, and didn't experience any flickering..

About the "rumour" about adb being the culprit...well, that just can't be. I use adb all the time to push files to the device; like i said, never experienced flickering before switching to 11122022.

Francisco, need anything else man, besides Euro Milhões? :P
[Samsung Galaxy Nexus] franciscofranco:
Yes I do, I need to find the pattern of these glitches. I followed every of my changes and none could do this. Anyway my local build has already a bunch of reverts and additions which I hope that have it fixed for good.
[Samsung Galaxy Nexus] DJTaurus:
I have to admit that with your 11/11/2011 kernel release battery drain in sleep mode is less but still there...keep up the good work.

My stats:
[Samsung Galaxy Nexus] franciscofranco:
I'm sorry but I don't see battery drain there. You used your phone a lot as I can see by the blue bars ;)

I'm gonna release a new one in 10 minutes, just packing the boot.imgs and preparing the OP.
[Samsung Galaxy Nexus] Rey-619:
i just can confirm ^^ this is how it should be ;)
[Samsung Galaxy Nexus] franciscofranco:
Another update is up. Feedback please as usual.
[Samsung Galaxy Nexus] EddyOS:
I'll give this a go, gonna go for a non OC flavour as I'm not fussed about that right now
[Samsung Galaxy Nexus] Homer314:
Just flashed the 12 Revision.

There is no need to delete the library anymore ?
[Samsung Galaxy Nexus] joshnichols189:
I haven't read the whole thread but I've been keeping up with the changelog. What is the "graphical glitch"? I'm on the kernel from last night and sometimes when I turn the screen on it flashes blue/black and is basically useless until I reboot.. not sure if this is the same since the changelog says it was fixed?
[Samsung Galaxy Nexus] franciscofranco:
That's the glitch, I've been attempting to fix it, but to no avail. I hope this last one fixes it for good.
[Samsung Galaxy Nexus] joshnichols189:
Thanks! Wasn't sure, will try the newest update now :)
[Samsung Galaxy Nexus] GchildT:
Same setup as before... No graphical glitches or artifacts...

Quadrant: 2898 (2D Acc ON) 2611 (2D Acc OFF)

AnTuTu: 6981 (2D Acc ON or OFF)
[Samsung Galaxy Nexus] dwang:
I'm wondering if that's the cause of the graphic glitches?

Do people who have the glitches have libgles_android.so deleted?

I restored mine and so far no glitches yet, but my glitches took a while to show up even with the file deleted.
[Samsung Galaxy Nexus] itolson:
oc kernel is jittery for me... going to none oc kernel is fine....

any suggestions...

running

[ROM] Android Revolution HD™ 1.3.1
[Samsung Galaxy Nexus] hosmsdos:
Super excited about 1212 kernel but then i could not find links to it :( i still see 1112 did you upload it?..Thank You
[Samsung Galaxy Nexus] EspadaKiller:
Ah i see, thanks for the info!
[Samsung Galaxy Nexus] chirea.mircea:
Please share!
[Samsung Galaxy Nexus] optmkleung:
http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] jdk82:
LOVE the updated OP man :D Seriously though, it looks cleaner. I think first timers will find it an easier read. Thanks a lot for all your hard work, your kernel rocks! Your app is pretty nice too, although I still flash manually ;)
[Samsung Galaxy Nexus] droidgren:
Have a look here, http://code.google.com/p/2-way-call-recording/source/browse/#svn/patches

Maybe not what you were looking for, but maybe a start?
[Samsung Galaxy Nexus] loudaccord:
New Quadrant is out lol. Just sayin:)
[Samsung Galaxy Nexus] franciscofranco:
Dunno, I'll think about it.

Color Multipliers patch from Ezekeel coming in a few hours along with app support I hope. Stay tuned.
[Samsung Galaxy Nexus] samir5421:
Hi, I've noticed that the kernel is causing a problem with rom manager. I am currently on aokp build 23, though I've have this problem for a long time.

Here are the steps to reproduce the problem:

1. Wipe, install aokp and gapps

2. Install Franco kernel

3. Install another zip using rom manager

The problem occurs at 3. After I select the zip and reboot in rom manager, it reboots into clockwork recovery,but fails to install the zip. I can provide the error log if it is needed.

Has anyone else had this problem?
[Samsung Galaxy Nexus] dcoy82:
Hey Franco any update on why so many people have been reporting SOD on 16.2? You found a fix for it? Thanks!
[Samsung Galaxy Nexus] nrgaway:
+1 on the call recording feature.

Here in Canada it is legal to record a call so long as at least one of the parties know the call is being recorded. It would only be illegal if you say put call recording feature on your girl friends phone without letting her know :)
[Samsung Galaxy Nexus] yeeson:
Looking forward to new kernel！
[Samsung Galaxy Nexus] kimboinatl:
I'm using SetCPU because I like having multiple profiles. Just wondering if y'all are using this or if your setting the governor in the update app.
[Samsung Galaxy Nexus] samizad:
The AOKP ROM has the CPU settings too. I use the updater app so I think having SetCPU as well would be too much.
[Samsung Galaxy Nexus] franciscofranco:
Many people? I don't see SoD reports.
[Samsung Galaxy Nexus] edwin124:
hey man, any idea why my phone would be running 100-105 degrees?
[Samsung Galaxy Nexus] flolep:
Yep. No more SOD on 16.2. It was surely linked to dynamic hotplug and 350 mhz frequency. With hotplug mod and 400 mhz frequency, my phone is very stable, is lagging less than with 350 mhz and the battery usage is very good, even if using 1350mhz at max. Franco turtle is helping. Have a good day!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 2dorr:
Yesterday I had a problem with my phone. When I turned on the screen, the touch was not responsive, I tried to shut off the screen, and back on and still nothing. In the end I managed to reboot the phone from the button. After that it was fine. It never happened till now.
[Samsung Galaxy Nexus] minipaolo:
I'm getting SOD sometimes, but I'm not sure it is kernel related. :)
[Samsung Galaxy Nexus] Elganja:
my phone is a hair laggy when unlocking... I think that is due to the 400mhz though and nothing else... but I can live with that if the battery life continues to be fantastic.

on average, I spend about 2% @ 1000, 3% at 700 and 10% at 400, rest deep sleep... on francoTurtle, no hotplug, no ov and no oc.

I easily get 3-3 1/2 hours of screen time (depending how much 4g or wifi I am using).

---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------

one more thing, sometimes when I press the power button, nothing happens.... but this is not a SoD. All I do is press the button again and all is well...

doesn't really bother me
[Samsung Galaxy Nexus] whiteintegsg316:
What's is sod
[Samsung Galaxy Nexus] Elganja:
Screen Of Death
[Samsung Galaxy Nexus] whiteintegsg316:
OK so basically you have to pull the battery to get it to reboot and everything is fine after. Sorry I'm coming from the nexus s 4g and I never herd that term before.
[Samsung Galaxy Nexus] Elganja:
yes that is correct
[Samsung Galaxy Nexus] whiteintegsg316:
OK one more question and I'm done I known it says 4.0.3 but has anyone tried it on 4.0.4 to see how it works
[Samsung Galaxy Nexus] giangishanghai:
whiteintegsg316

"OK one more question and I'm done I known it says 4.0.3 but has anyone tried it on 4.0.4 to see how it works

as it is describe in the first post from FranciscoFranco, it can work on 4.0.3 and 4.0.4 too.............i think we can believe, right?

try to check....

cheers
[Samsung Galaxy Nexus] whiteintegsg316:
OK thank guys for helping me out.
[Samsung Galaxy Nexus] DarkGruf:
I'm on a Modaco ir11, so a 4.0.4, and that works like a charm.
[Samsung Galaxy Nexus] dcoy82:
Sorry about that, I read back and apparently all the SoD reports I read were from #16 and I wasn't paying attention to the date on threads because I clicked on last unread post, but didn't realize I was posting in the GSM forum and not the CDMA forum. :rolleyes:

On the other hand, I was getting multiple SoD on 16.2 myself but maybe it was a bad flash/download. I'll re-download it this morning and reflash. Hopefully I'll have better results this time around, as they have gone away since I reverted back to 13.1 for the time being.

Again, sorry for the misunderstanding and keep up the good work. Been using Franco Kernel and App for a while now.
[Samsung Galaxy Nexus] ratson:
I have also had a SoD a few days ago as reported with #16.2
[Samsung Galaxy Nexus] franciscofranco:
Ok I need some help. How can I reproduce that 200mhz usage bug?
[Samsung Galaxy Nexus] atsavlis:
I use set cpu, and my default settings are 400 min / 1000 max with franco turtle and all runs perfect.

Open set cpu again, and change the governor from turtle to gazelle and leave the speeds untouched. You will notice that the set cpu will immedeately register the lowest speed as 200.

[Edit]

Added a screenshot so you can see what we saying. Another thing I noticed was that with gazelle, the cpu is very erratic, and there is also times that one core is on 1000 and the second is on 200.
[Samsung Galaxy Nexus] franciscofranco:
Oh boy, that's not good since #17 will feature 1,5ghz. Let's see what I did there ;)
[Samsung Galaxy Nexus] atsavlis:
Cant wait.... :D
[Samsung Galaxy Nexus] loudaccord:
I know a lot of people have a problem running 1.42ghz, do you think your 1.5ghz will be more stable? Just curious.
[Samsung Galaxy Nexus] poopooface:
The changes to the OP have been good so far... one more change that wouldn't take too long to put in there would be a link to the site where the old versions are posted. That must have been asked for in at least 100 posts now... This should save you time reading the thread as well.

I am looking forward to 1.5GHz! When I heard the rumor that the Sprint version of the GNex was going to feature 1.5GHz, I almost shat my pants before I realized that the processor in the current GNex is actually rated at up to 1.5GHz.

The GPU in the GNex is also rated at 384... I know about the issue of the bus speed becoming the bottleneck when it's clocked at that speed, but does anyone know whether it's possible to crank the bus speed up via the kernel so we can see benefits from 384MHz GPU speed?
[Samsung Galaxy Nexus] The Kid Cassidy:
what program is that in the screenshot? Set cpu? god i having used that for a while...but when i did, it didnt have all that kind of info on the D1..LOL
[Samsung Galaxy Nexus] jdk82:
In addition to the issue with gazelle, I can confirm turtle occasionally dropping the CPU freq to 200Mhz. I first noticed it briefly when unlocking the screen with setCPU running. Then I saw this while starting Pandora

root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
400000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
700000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
700000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
[B]200000[/B]
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
400000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
400000
root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
400000

Let me know if I can help with logs, testing, or whatever.

Edit: I can observe 200Mhz scaling on every governor except Performance. Some switch more/less frequently (of course) and spend more/less time at 200Mhz (I got OnDemand to stay there apparently indefinitely while sitting idle), but they do get there.
[Samsung Galaxy Nexus] franciscofranco:
I have no idea of what causes it, so I just added a true 200mhz step and be done with it.
[Samsung Galaxy Nexus] loudaccord:
could be a problem with CWM. Some people had to go to an older version 5.0.2 I believe. I'm using the touch recovery and works fine with AOKP & 16.2. I had a problem with SU at one point but that was just a strange glitch.
[Samsung Galaxy Nexus] franciscofranco:
Rom manager isn't mine, I can't fix his jerky code.

#17 is out, enjoy and don't fry your devices with 1,5ghz.
[Samsung Galaxy Nexus] samir5421:
Thanks, I'll try it.
[Samsung Galaxy Nexus] sishgupta:
=S

Thanks!
[Samsung Galaxy Nexus] jdk82:
Thanks man, seems to be running great. Oddly enough, now that you've added 200Mhz I can't get it to drop below the 400Mhz min. I'll keep watching it and see what happens. Thanks again :)