yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] eriksengh:
Thanks Franco for this fantastic kernel.

Running both 17 and 17.2 at 1.5Ghz without any issues. Get a little better score in benchmarks with 17, but both running without any lag in UI.

I have no GPS in 17/17.2 (This is bad as i use this every now and then..) Hope you can get this working again. Anything I can do to help it?

5 Ghz wifi is also still dead (Have been so for the last two versions i think). It shows up in the list, but when i try to connect nothing happens.

This is not a big issue for me so i just use the regular 2.4 wifi.

I missed out on the 17.1 and would like to test it. Can anyone upload please :)

EDIT:

Nevermind the GPS issue. Flashed 17.2 once more and it´s working again, no gps only goes for 17 :)
[Samsung Galaxy Nexus] deezid:
Maybe change to another kernel. I need GPS for navigation :(

But there's only one kernel with Color Multiplier support. My display looks it has been replaced since #17 :D
[Samsung Galaxy Nexus] drawde40599:
GPs working great here 8 satellites 5 seconds, used navigation to go to the store works fine

---------- Post added at 07:12 AM ---------- Previous post was at 07:07 AM ----------

Try setting min and max to 1000 then max to 1500 them min back down to wherever u set it, no real issue here doing that locked up on internet sometimes but not for awhile now .worked for me
[Samsung Galaxy Nexus] nicandris:
Tried it. Same thing

Reverted to #17 just to be sure. 1.5GHz works fine there

@franco any log I can provide regarding this?

I also tried upping the voltage a bit for 1.5GHz but same thing
[Samsung Galaxy Nexus] paulobrien:
I just PM'd franco re: a bug in his app whereby settings aren't being reapplied on startup. So if this is affecting you, i'm sure he'll fix it shortly.

Basically, the script put in init.d isn't being set executable.

P
[Samsung Galaxy Nexus] nicandris:
The "P" at the end of the previews post made me smile!

paulobrien is using Franco's kernel!!

KUDOS for franco! This is huge!
[Samsung Galaxy Nexus] chakra:
I could not get any downloads to work, I am using chrome beta and franco 17.2 with AOKP m3. I tried another kernal and everything will download again.
[Samsung Galaxy Nexus] dyndragon:
What's the problem? "Download unsuccessful"? Probably not a kernel thing. Try clearing the download manager data.
[Samsung Galaxy Nexus] MultiCulti:
franco, i had to go back to #17 cause with #17.1/2 my phone get´s laggy as hell ... not even can open the app drawer without seconds of delay :confused:

but with #17 everything is fine
[Samsung Galaxy Nexus] lemmy_0:
thanks a lot dude!
[Samsung Galaxy Nexus] chakra:
Ok that worked thanks.
[Samsung Galaxy Nexus] Shetlander:
IF you are trying to run it at 1.5Ghz that is the problem. With v17 DCC is enabled to allow it torun at 1.5Ghz but has been disabled in v17.2 by Franco.

You (like me) are one of the unlucky people who's phone cant handle 1.5Ghz without DCC (but Franco's can).

Personally I cant use the latest version of Franco's app as it freezes and becomes unresponsive. Anybody else having problems with it?
[Samsung Galaxy Nexus] MultiCulti:
DCC? :confused:

but with #17 it´s also running on 1,5Ghz :eek:
[Samsung Galaxy Nexus] dumbdroid:
:D
[Samsung Galaxy Nexus] gravis86:
Read back a few posts...

http://xdaforums.com/showpost.php?p=22561528&postcount=6403
[Samsung Galaxy Nexus] drawde40599:
App

Maybe I'm just not seeing it, but adding a feature to app that checks to.see if its most recent copy from the android market would be nice
[Samsung Galaxy Nexus] nicandris:
found this in Google+ posted by the CyanogenMod page. I'm pretty sure franco will love it!

https://plus.google.com/117962666888533781522/posts/Mv9kitKE246
[Samsung Galaxy Nexus] poopooface:
Holy mother of ****... What ROM and which version of the kernel are you running?
[Samsung Galaxy Nexus] dumbdroid:
AOKP M3 + Franco build 17
[Samsung Galaxy Nexus] poopooface:
Damn, that makes me want to try M3. I am on GummyNex 0.7.0 and too lazy to wipe everything for the moment. Congrats!
[Samsung Galaxy Nexus] diablos991:
I'm on AOKP M3, Franco 17, and OCd to 1.5ghz w/performance or gazelle.

I am only seeing 3161.

How did you double this?
[Samsung Galaxy Nexus] diablos991:
I got it to 4888 if I use turtle. Weird how turtle increases the score by 1700.

The differences between my 4888 and the 7000 score all come from ram, CPU integer, and CPU float.
[Samsung Galaxy Nexus] loudaccord:
my benchmark of the day :)

FF#17 AOKP21

lol at the rankings. Nexus on Gingerbread? 4.0.1 at 1.2ghz is #1??? Not sure I agree with these. ^^^
[Samsung Galaxy Nexus] MS.:
I'm really looking forward to this, as my phone are one of those that works fine @1,5GHZ on #17, but it lags on #17.2. Thank you for your hard work mate.
[Samsung Galaxy Nexus] ChongoDroid:
You didn't read what I said. My phone obviously can handle 1.5ghz since morfics runs just fine even with less voltage. I thought the same thing on morfics but bumping up to 1350mv was completely stable. Now on francos and I can't achieve stability even at dangerously high voltage. Its not the silicone.

Edit: I know what's wrong nvm
[Samsung Galaxy Nexus] GchildT:
Interesting tidbit.

Using 14.2 my CPU Benchmark numbers @ 1350MHz are a lot higher than 16.0 - 17.2. Almost double.

Antutu, Quadrant, and others give similar results. I know a lot has changed, but i wonder what's the culprit?

Just a tidbit...
[Samsung Galaxy Nexus] Shetlander:
Yes but in #17 DCC is Enabled up to 1.5Ghz. With #17.2 he has put it back to what it was to start with which means most people wont be able to get 1.5Ghz to run stable/lag free.
[Samsung Galaxy Nexus] minipaolo:
It looks like user experience is now linked to benchmarks results only.

Everyone running benchmarks as hell...
[Samsung Galaxy Nexus] poopooface:
I was getting a lot of chop on 17.2 so I flashed back to 16.2... It fixed the UI lag and also raised my AnPooPoo by about 1000 points. AND GTA3 is now playable again.

On 17.2, for the first time ever while running a Franco kernel, the "knights swinging swords" portion of AnPooPoo started out running with normal framerates, but then went completely choppy about halfway through and continued like that through the end of the segment. Could it have been the throttle bottleneck kicking in? I don't know. But I do know that 16.2 gives much better overall performance for me.

I am kind of tempted to flash a completely different kernel and then try 17 again, but UFC is on tonight and I don't want to spend all that time un-softbricking my phone again.
[Samsung Galaxy Nexus] GchildT:
Same here; about the "knights swinging swords". It was intermittent for me... But mainly my CPU and RAM performance numbers were abysmal no matter what clock speed i set the device at.... I'm not one to rely on benchmarks, but when you notice a slight performance change you gotta use the benchmarks to compare IMO.
[Samsung Galaxy Nexus] loudaccord:
This is the fastest my phone has ever been... I'm at 45% battery and haven't charged in almost 24 hours... going to see if I can last til the morning :)
[Samsung Galaxy Nexus] homer2320776:
Franco,

Just thought I'd let you know that a lot of people, including myself, who have complained about settings not sticking through reboot were wrong to blame the kernel or the updater program.

After digging around ans reading a ton of logcat info, I narrowed it down to being a busybox issue. For some reason the market busybox, at least for me, will not execute scripts in the init.d folder. The only one I've had success with is the 1.19.3-cm9 build.

Thought it might be a good idea to include a link to that version of busybox somewhere or put it in the .zip installer.
[Samsung Galaxy Nexus] Stretlow:
Other than benchmark numbers what's the main benefit from overclocking an already smooth phone?

Does it have a massive effect on battery if you do so?
[Samsung Galaxy Nexus] AfroCreame:
I'm getting the best performance out of 17.2 vs. any previous builds, including Trinity..

View attachment 903469

Thanks for the hard work!!!
[Samsung Galaxy Nexus] sert00:
also from GLaDOS-V1.12 (now 1.13)it has color multipliers.only thing is the method of set it.here you can via the franco app,on glados you have to change parameters in some files.with franco kernel is more user-friendly
[Samsung Galaxy Nexus] atsavlis:
I cant compare to other kernels, as I have tried them all even with gpu OC and CPU set to max, and I have never had an issue...

What ended up being your problem??
[Samsung Galaxy Nexus] :
I'm having problems with my phone not charging while on. Works 100% of the time while off, but seems intermittent while on. Sometimes it will work, other times not. Have to reboot it to get charging sometimes, which doesn't always work either. Also had the phone say its charging when not.

Unsure if this is a ROM or kernel issue. Anyone else had this? Aokp b23 and 17.2
[Samsung Galaxy Nexus] nic85:
17.2 350-1200 phone get REALLY HOT during browsing web.. NEVER happened before

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Francois88:
Access to network drives via samba (Tried Dice Player and Es Explorer) broken for me in #17. Reverting to #16 fixed it, CIFS broken?
[Samsung Galaxy Nexus] franciscofranco:
Get me your dmesg please.

Flash #17.2.
[Samsung Galaxy Nexus] GchildT:
PLease bring jRCU back. Screw Hotplug!
[Samsung Galaxy Nexus] ACTPOHABT:
Download unsuccessful. Is it just me?
[Samsung Galaxy Nexus] ChongoDroid:
It actually wasn't resolved, I thought I had set "set on boot" and didn't remember it's set to default to 1ghz max with franco turtle without. 1.5ghz is completely unstable still for me regardless of voltage.

Morfics 1.53ghz experimental kernel with 1350mv is stable for me. Weird
[Samsung Galaxy Nexus] chakra:
Go into the settings/ apps/ download manager and clear the cash.
[Samsung Galaxy Nexus] neverhappy:
Using 17.2 on CDMA phone for about 8 hrs so far. Set for 350MHz - 1500, ondemand. hotplug. Working great so far, Web browsing, two exchange email accounts, 2hr phone call. NO uv (just muddies the water). no glitches. Will give it a fresh charge and see how the Bat life is. So far I'm pleased. Thanks
[Samsung Galaxy Nexus] mtmjr90:
Battery life since v17 (currently on 17.2) has been pretty atrocious. I'm set to francoTurtle 350-1200MHz on AOKP23. It seems particularly bad on LTE (moreso than usual). I've got an extra battery so I'll just deal with it, especially since I've had such a great experience with francoKernel (pre-17), but I hope it gets better soon:)

Edit: dunno if it matters, but I'm also on the 4.0.4 radios.
[Samsung Galaxy Nexus] poopooface:
Okay, this is kind of weird, but I tried putting 17 on again. It royally jacked my phone when I went from 16.2 to 17. So I restored to the pre-17 point, then put on GladOS kernel, THEN put 17 on. And now it works- only one restart at first, smooth since then. However, my AnPooPoo is now trash- only 3175!

Ah well.
[Samsung Galaxy Nexus] nikulogical:
So what's the general consensus.. upgrade from 16.2 to 17.2 or wait?
[Samsung Galaxy Nexus] nicandris:
well my only issue is that my phone cant handle 1.5GHz now. if you don't use that upgrade! But even if you use it why not upgrading and downgrading later on? the kernel does not mess any settings on your rom! a kernel flash it's just 4minutes
[Samsung Galaxy Nexus] ACTPOHABT:
Didn't help. :(
[Samsung Galaxy Nexus] THE_KINGDOM:
I had the exact same problem on AOKP Milestone 3 and Franco.kernel 16.2. Phone would be charging but not, instead actually losing charge and also sometimes not even registering that a charger had been connected, so again not charging.

I wiped phone and upgraded to AOKP b23 and Franco.kernel 17.2.. I don't seem to have the problem anymore. For now.
[Samsung Galaxy Nexus] THE_KINGDOM:
Not just u, I had exact same problem, I wiped download manager data and it seemed to fix it. But its not the first time I had this problem either.
[Samsung Galaxy Nexus] Gahh Its Lee:
To Franco. Just curious but any chance of you making a ridiculously fast kernel? 1.53 ghz+? I mean I'm aware a lot of people wouldn't be able to use it but some could and it would be fun.
[Samsung Galaxy Nexus] neverhappy:
Need a governor infringing on a frequency, that after 10 minutes of use, you phone burst into flames, but for those 10 minutes, you get the most incredible benchmark. Flameon Governor. lol
[Samsung Galaxy Nexus] The Kid Cassidy:
Could someone give me a link to #17? My phone runs fine on 17.2 at 1.35, but cant handle 1.5 overclock...wanna see if #17 with DCC enabled will allow it to for future reference...I went right from 16.2 to 17.2...Thanks
[Samsung Galaxy Nexus] ccfly888:
Here you go :)
[Samsung Galaxy Nexus] Gahh Its Lee:
I miss 400 as lowest for some reason my typing is off at 350 it feels like I'm clicking faster than its realizing. At 400 it just seems to work that tiny bit quicker. Edit I tried 17.2 and I'm getting major stutter at 1.5 but I could run it fine on 17.1 switched because i got a few reboots at lower clock speeds.
[Samsung Galaxy Nexus] DooMMeeR:
franco: is it possible to activate more channels on 5GHz?

atm the GN only finds WiFis on channels 32-36-40-44-48 bit non of the other a/n-Channels :)
[Samsung Galaxy Nexus] mazubo:
So knowing this; is there a way to know which devices are able to run without said issues?

Cheers,
[Samsung Galaxy Nexus] nikulogical:
same. turtle 400/1200 on 16.2 felt better than turtle 350/1200 on 17.2 I dont wanna resort to using 700/1200
[Samsung Galaxy Nexus] Gahh Its Lee:
I think once he sees that 350 works the same as 400 just a wee bit slower he will put it back in.
[Samsung Galaxy Nexus] stesmi:
http://xdaforums.com/showpost.php?p=22556504&postcount=6380

// Stefan

---------- Post added at 08:16 AM ---------- Previous post was at 07:53 AM ----------

Do you feel that the extra 30MHz would be a huge benefit to you? I mean 1.50 vs 1.53GHz .. ?

EDIT: I mean that 1.5 would be "normal" oc and 1.53 would be ridiculously fast. That's what I'm talking about.

// Stefan

---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------

There is a rumor that chinese GN are a bit better than Korean ones.

But otherwise, no. Two sequential serial numbers could have CPUs or other components that come from different wafers, or one is from inner of the wafer and one is from outer part of the same wafer. They will be better or worse but both within spec. Some will be able to go higher with/without DCC and some will not.

Of course, the chance that two sequential serial numbers differ massively isn't big.

// Stefan
[Samsung Galaxy Nexus] renaud:
Given that you probably don't have any gain by overclocking (except in benchmarks), I would say no :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea I am happy with 1.5. I was actually thinking 2.0 since my friend said the eco 3d runs 2 ghz now. But checked out that section and he's full of it.
[Samsung Galaxy Nexus] michie:
Great battery life with 17.2 on bugless beast, gonna stick with this one for a while :)
[Samsung Galaxy Nexus] da blitz:
Please add new glados features for remove mpu limit frequency thanks
[Samsung Galaxy Nexus] ACTPOHABT:
Clear data instead of cache worked. Thanks!
[Samsung Galaxy Nexus] marc.tulley:
Does anyone have a copy of 17.1 I can have?

Really want to try it for achieving 1.5Ghz stability. I only need a touch more stability on 17 and 17.2 (with Dcc on) doesnt work...

Unfortunatly I was sleeping while franco was beavering his way to 17.2 :(
[Samsung Galaxy Nexus] Stretlow:
I understand the concept of overclocking but I cant for the life of me see any reason to other than to get a better score

Unless someone can advise me otherwise?

confused:confused:
[Samsung Galaxy Nexus] stellaryt:
done...

10 char
[Samsung Galaxy Nexus] atsavlis:
Link is broken...
[Samsung Galaxy Nexus] minipaolo:
Same here.

I'm fine with 350-1000 on francoTurtle and find it really stable.
[Samsung Galaxy Nexus] drawde40599:
Um, makes phone faster (:
[Samsung Galaxy Nexus] manu93_:
Gta 3 doesn't work for me anymore

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] MS.:
My wife didn't make a coffee for me this morning, rolling back to #13.1 :-(
[Samsung Galaxy Nexus] stellaryt:
fixed,could download now
[Samsung Galaxy Nexus] sotoskawasaki:
Right now I would have to agree with you, that overclocking is for scores. Of course it's also the feeling you have when you hack something, when you use it in a way it wasn't meant to be used. But in 1-1.5 years when the "default" hardware configuration will be 1.5GHz dual core or quad core, and we will be on Android 5.0 or 6.0 or even 7.0, then believe me you will want every bit of Hz you can get from your CPU to be able to run smoothly the new OS.

Soteris
[Samsung Galaxy Nexus] marc.tulley:
Haha exactly. This is just conservative planning ahead ; )

In my opinion benchmark is a quick way to confirm improvements are made. Without spending a few days using it as normal to notice tiny improvements just that peace of mind that 'it is quicker....promise'

But your dead right the use of this improvement is minor now but the feeling of getting better value for money from all these tweaks is rewarding.

By the way thanks to a kind upload of 17.1, 1.5ghz appears fine on my GN now (occational reboots on hoigh load with 17 and 17.2 with DCC causing significant performance stutters making the UI use impractical)
[Samsung Galaxy Nexus] The Kid Cassidy:
Thank You...

Sent from a Galaxy an LTE tower away
[Samsung Galaxy Nexus] MS.:
I did some "tests" with my wife to see if it's just a placebo effect or not. We used HTC Desire S and Galaxy Nexus. I was setting frequencies on her phone (1-1.5GHz) and she did same on mine (1.2-1.5GHz). Both of us were able to tell when phone was running at default speed and when it's OC'ed.

To be honest, on GN it was a bit harder to spot the difference, especially with "Force GPU rendering" option enabled while on Desire S the difference was obvious.
[Samsung Galaxy Nexus] jenicekk:
BOOTLOOP BOOTLOOP with verison 17.2 on my clean AOKP 19 - 23.

last function version is 17. :(

any solution?
[Samsung Galaxy Nexus] tetsuox:
Go back to 17?
[Samsung Galaxy Nexus] minipaolo:
Well, if you are still on GN when Android 5-6-7 is out, I'm not sure you look into oc to 1,5ghz with 5 hours battery life.

However I understand when you say it is about the feeling you have when you hack something and this is the reason most of us are here. :p:D
[Samsung Galaxy Nexus] loudaccord:
Francisco, I know you plan on having 2 different kernels in the future, is it possible to just add a gov which allows for DCC? IE: GazelleDCC?
[Samsung Galaxy Nexus] Stretlow:
I actually installed set cpu as I have the same opinion on underclocking as overclocking (although the battery benefit is obvious)

Erm, in which way? the phone deals with anything you throw at it

Fair point.

How does it affect the battery usage? is it significant?

Apologies for the small thread hijack, I promise I wont continue it, just wanted to question why

Oh and great work though Franco... getting belting screen off time on 17.2

Stret
[Samsung Galaxy Nexus] eiabea:
does anyone know if franco disabled usb host in the newest release? i miss it :-D
[Samsung Galaxy Nexus] The Kid Cassidy:
Flashed #17 and now i can run 1.5 no problem! must be the DCC...
[Samsung Galaxy Nexus] sishgupta:
Works just fine for me.
[Samsung Galaxy Nexus] phunghoang24:
​

i'm happy with 17.2 OC 1350 : very smooth and quickly, But OC 1500 so bad!

:( sometime T9 FC, it's not fixed yet.

Foxhound 1.1 black Edition - IML74K - Great rom

Kernel -Franco 17.2 OC 1.350G

Radio XXKL1.

Someone show me capture screen!!!
[Samsung Galaxy Nexus] nick w:
Sorry if this sounds stupid. But what is the best method to install this kernal. These isn't clear instructions

I have download the Franco.kernal.nightly.zip. can j go into CWMod recovery and install the zip?

I'll be doing this after I update to Paula 11r2 beta

Thanks
[Samsung Galaxy Nexus] zurchpet:
Yes, flash the zip from CWM or extract the containing boot.img and flash that with fastboot.
[Samsung Galaxy Nexus] phunghoang24:
Yes, use recovery as flash a rom, don't wipe anything!
[Samsung Galaxy Nexus] nick w:
Splendid. If only k could find the thanks button on the xda app to reward you!!

Thanks
[Samsung Galaxy Nexus] GchildT:
Agreed. Rollback to 15.2 and it's even better...
[Samsung Galaxy Nexus] poopooface:
Okay, so I am now running 17.2 and I was about to flash back to 16.2 or 15.2 because it was slow as ****. But then I clicked "Force GPU rendering" and boom, I gained over 2500 points in AnPooPoo and now everything is smooth as butter in the UI, whereas before it was giving me chop. Hooray!
[Samsung Galaxy Nexus] THE_KINGDOM:
Hey can somebody explain to me why some people on galaxy nexus cannot overclock to 1500MHz? Something about stability of device? or some people can, somebody can't something like that??

Im on AOKP b32 and franco.kernel 17.2 (which seems to be the best kernel so far btw, thanks Francisco)

and from day 1 i've had it overclocked to 1500 (but on francoTurtle) and device is running fast and smooth, and battery not that much affected more than it was before.
[Samsung Galaxy Nexus] Gahh Its Lee:
Some people can't because not all phones are created equally. Some can handle more than other. If you look back to the droid1 days some people had phones that couldn't handle over 800mhz some people pushed them to 1.25 ghz
[Samsung Galaxy Nexus] THE_KINGDOM:
oh ok i see sorry misunderstood the first time I read it. so what is likely to happen if your phone cannot handle it?

EDIT: mine maybe does run a bit smoother on 1350MHz now that i tried both and played around with it, it can still handle 1500MHz but I guess sometimes i get lag between pages, whereas on 1350MHz, seems that I dont get that lag as much.
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea I was just using that as an example since those phones had so many differences. Our phones are subtle and some can go 1.35 and others 1.5. Its if you luck out and get a better chip than the next guy.
[Samsung Galaxy Nexus] eiabea:
hmm strange, cause i flashed back to #15.2 and now it works, but not with #17.2 :-(
[Samsung Galaxy Nexus] renaud:
Why does the device not run at 1500mhz by default? Do you think some random guy just knows how to make it run at 1500, while Google team doesn't know?

There is a reason why it runs at 1200. Probably manufacturing tolerances and overheating problems or even bus bandwidth like with the GPU.

That doesn't mean you absolutely cannot do it, that just means: if it doesn't work or it burns put the blame on you only, you have gone out of specs.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Voltage

I'm looking at the voltages in the franco app and there set exactly same as stock kernel, is this kernel not undervolted? I'm on 17.2 build . Looked threw wiki but voltages mentioned there from old build not matching what app says there currently at .
[Samsung Galaxy Nexus] Gahh Its Lee:
He out them stock to make it 100% stable. Seems to general thought is changing to undervolting doesn't even save battery.
[Samsung Galaxy Nexus] sishgupta:
Yes quite weird i was using 17.2 and my new OTG cable all yesterday
[Samsung Galaxy Nexus] Nebucatnetzer:
It will most likely reboot. Or if something goes really wrong it will die.
[Samsung Galaxy Nexus] Gahh Its Lee:
That's the usual description of it not working. It bogs out hardcore.
[Samsung Galaxy Nexus] Gabriel Audemard:
Mine seems to run just fine on 17.0. Made in China.

Galaxy Nexus, Franco, KL1, AOKP M2
[Samsung Galaxy Nexus] Icey34:
It's normal to get a momentary lag when unlocking after a while right? Running FrancoTurtle.
[Samsung Galaxy Nexus] Stretlow:
it's auto brightness. Turn it off if you want rid
[Samsung Galaxy Nexus] loudaccord:
Just curious, what do you use this for? I couldn't think of any reason I'd use it.