yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] phonedroid:
I didnt use the kernel app - just flashed the boot image using fastboot.

Have read elesewhere that "Smartreflex" will be gone when you overclock. I don't have any idea what it is.

Tried OC'ing using SetCPU to 1.6 GHz, still phone didn't feel as responsive as before. Now restoring the back up from CWM.
[Samsung Galaxy Nexus] nuwan32:
Oh.. I would recommend flashing r300. That is the most "stable" release imo. All the fast boot images are still highly experimental and missing things such as fast charge and volume boost etc, so unless your using android 4.2, try r300. Working perfectly for me and I'm in no rush to try 4.2 till an official PA version is released
[Samsung Galaxy Nexus] JBNex:
Idk why this is happening but my nexus phone has been rebooting itself constantly. And it's really hot
[Samsung Galaxy Nexus] TEK112:
Sounds like a voltage issue. Are you running stock values for the kernel?
[Samsung Galaxy Nexus] nuwan32:
Set stock voltages, delete any other apps that control CPU settings like set CPU or voltage control and if you set your min voltage to 192, try upping it 384
[Samsung Galaxy Nexus] franciscofranco:
What kernel are you running? I can't figure it out if you dont give me any info.
[Samsung Galaxy Nexus] JBNex:
it cant be the kernel, its my device... Nvm
[Samsung Galaxy Nexus] franciscofranco:
It can be the kernel if you're running #312.
[Samsung Galaxy Nexus] alex999999:
guys i give a **** about benchmarks, but look at this with standard franco kernel

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] a5pe4:
Guys I've used cwm since I rooted so I was wondering if you can flash Franco's kernels on twrp. My initial guess would be yea but I just want to make sure.
[Samsung Galaxy Nexus] simms22:
move along, nothing to see in this post..
[Samsung Galaxy Nexus] TEK112:
It is okay.
[Samsung Galaxy Nexus] franciscofranco:
He was just showing the bench with standard options that I ship the kernel with :)
[Samsung Galaxy Nexus] simms22:
ahh... OK, then. keep doing what your doing :)
[Samsung Galaxy Nexus] yellowdie:
lol. I remember back in the day when I used to care about benchmarks (it really wasn't that long ago :silly:). I can't even count how much of my battery life was wasted running benches. Not to mention the OCs to 1.8GHz and running the bench with the phone in the freezer just for the heck of it. haha. Oh good times, good times...
[Samsung Galaxy Nexus] metal_god69:
What IO scheduler should we be using for the new r313 4.2 kernel? Noticing default is noop?
[Samsung Galaxy Nexus] osm0sis:
Franco has the default at noop because he wants us to try it and tell him how it feels. :good:

Switch to the others for comparison if you like.
[Samsung Galaxy Nexus] :
Brings a new meaning to the word "Ice Berg Cooling" , lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xolanir:
Will this kernel work with the CDMA variant of the Gnex? I'm running an aosp 4.2 version. Thx in advance for the help.
[Samsung Galaxy Nexus] rmcsc:
I don't give a crap about benchmarks. I care for stability, battery life and a speed. Franco's kernel gives me these, always.
[Samsung Galaxy Nexus] SorryGoFish:
How can I diagnose WiFi issues? I get very frequent disconnect and re-connects. This happens on low signal, and medium signal. It happens with screen on, and screen off. Thanks.
[Samsung Galaxy Nexus] fallingd0wn:
Yes
[Samsung Galaxy Nexus] hungmung:
If you haven't already make sure you uncheck avoid poor connections under advanced options in Wi-Fi settings

Sent via moon rays...
[Samsung Galaxy Nexus] gianton:
Yes kernels are compatible for all three models of the GNex.
[Samsung Galaxy Nexus] SahilC:
Omg how I'm getting like 3000 :eek:
[Samsung Galaxy Nexus] franciscofranco:
Stock Wi-Fi drivers on my 4.2 compatible kernel, so its either Google **** or its your ****.. I would point to being your **** rather than Google's :)
[Samsung Galaxy Nexus] yellowdie:
lol. What do you think about the 4.2 wifi drivers vs the 4.1 drivers? I heard stock had a big improvement there. Thoughts?
[Samsung Galaxy Nexus] The Gingerbread Man:
Same here I changed jobs recently, as I security guard I could hide behind CCTV podium / desk / metal structure at front of stores in my old job and now at my new job as a security guard in different chain of stores they don't have these about so much so hence I'm not about as much as I'd like to be but still always here reading / lurking just have little time to post :(

Sent from my Galaxy Nexus

---------- Post added at 09:12 PM ---------- Previous post was at 09:00 PM ----------

Also just wanted to say massive thanks to Franco for the two quick updates for 4.2 and been running the second test boot.img for some 14 hours since release and my phones running great, under clocked to 1.0ghz and performance is fine and had no SOD etc and stability has been 100% so far. Especially with your big move and change of jobs let alone changing continents and time zones lol Very happy on stock 4.2 rom with Franco 313 and got stock kernel backed up in my kernel back up folder. I'm even running stock recovery ATM lol Real excited for minco ROM to be updated :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] saar73:
is it possible to get the new build in recovery version please? :)
[Samsung Galaxy Nexus] The Gingerbread Man:
I actually prefer the .IMG as just pop it in kernel backup folder and choose to restore it, you don't to wait for android to mess about upgrading or what ever due to ram disk change , just would be better if the builds were labeled as their 'proper' names and its just quicker and easier all round :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nuwan32:
Just do it yourself and put the boot.img in any flashable zip

---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------

Yea or that, like other users have mentioned put the img file in the kernel backup folder and restore it using the app
[Samsung Galaxy Nexus] The Gingerbread Man:
That's exactly what I mean but instead of these test builds being called boot.IMG I mean Franco actually naming the file bootr***.IMG and just restore it. That way it cuts out long boot up process and those really passionate about fastnoot commands and stuff can still do it as the cmd will still work as long as the correct file name is typed properly. Fastboot .IMG can be called anything and file will still work as long as it has the correct .extension file name

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] saar73:
works like a charm :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Of course we have been talking about it for months :p:D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mekanismen:
Is that even possible? Pretty sure it has tö be named just boot.img.
[Samsung Galaxy Nexus] yellowdie:
Nope. Boot.img is just what it comes with as stock. But you can name it whatever you want. I rename them and throw them in the kernel_backups folder as well. Simple.

:):D:laugh::good:
[Samsung Galaxy Nexus] arzbhatia:
Edit: Nevermind, I'm stupid :p
[Samsung Galaxy Nexus] The Gingerbread Man:
Sat in my living room approx 2 meters away from WiFi router and getting mostly full signal bars and sometimes drops to 1 bar off full and quickly bounces back to full.

Only two requests for next build if its not too cheeky is getting 1228 step back and also headset volume increase (sound quality seems to be improved in terms of clarity with 4.2 but is slightly too quiet for my liking)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I'm personally hoping for that tasty wifi driver from kernel 3.4 that we were all drooling over before, now that it's stable. :D
[Samsung Galaxy Nexus] xolanir:
Perfect thx! Since this is a nightly build, how long before Franco puts out a more stable build. I've never used a nightly build before and don't know what to expect performance wise.
[Samsung Galaxy Nexus] The Gingerbread Man:
Ah yes I almost forgot about that, around the 250 nightly or something, yes that one was awesome *adds to wish list :D*

Sent from my Galaxy Nexus

---------- Post added at 11:19 PM ---------- Previous post was at 11:17 PM ----------

Well strictly speaking I guess this is an alpha build as in the nightlies are made as flashable zips so these last two being .IMG to fast boot I'd say are perhaps argueablely prenightly but still damn good

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I think I won't bring 1228MHz back. My idea is to use 1,3GHz as default since it uses the same voltage as 1,2GHz, and its marginally smoother.

Those drivers won't be merged, they break WEP routers connections.

See my answer above ;)
[Samsung Galaxy Nexus] mordakk:
Which I/O Scheduler is best, what do you use and why...?

BFQ, Noop, or Deadline?
[Samsung Galaxy Nexus] osm0sis:
Still? Damn.. I thought since they made 3.4 stable for the N4 that the Wi-Fi drivers would be stable and fixed too. So did Google put broken Wi-Fi drivers on the N4?
[Samsung Galaxy Nexus] The Gingerbread Man:
Fair enough answer to both requests, I was hoping Google got that **** sorted with those WiFi drivers by now, still hopely good news to come regarding headphone volume increase as no comment as yet. I bole your settling in OK in your new place and once again congrats and two big thumbs up for finding time for with your move and all the stress that brings. I don't recall an answer or mention of this but I hope things with you and your gf / wife / fieonce are still good if she came along with you / if she did, so really just wishing you well in your own personal life :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fenerbuuh:
And again good work. And again no uv settings. :(

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] maximum error:
Franco: Firstly I'm loving the kernel! The work you are doing is amazing! I've got the app and i notice there we have the ability to select the min n max CPU clock. Do you think we could get a similar option for GPU clock? I am slightly concerned about the heat my device generates while gaming with the OC'd GPU. I don't want to shorten my device life.

Thanks!
[Samsung Galaxy Nexus] orihuri:
how do i change the colors?i see the option in the app but i dont know how or wich values to change..i like to add some green and blue:rolleyes:

thanks for the help
[Samsung Galaxy Nexus] franciscofranco:
Yes, that's because I made -4 0 5 gamma as default. If you want stock colors just change to 0 0 0.

Because the current UV interface is broken. Imoseyon is working on a best UV userspace implementation, as soon as it is stable I'll ask permission from him to include it in this kernel.

I don't know if that is possible to export the GPU frequencies to the userspace. Ah and this nightly has stock GPU frequency as I found no difference between OC and non OC.

Change the values between -255 and 255.
[Samsung Galaxy Nexus] maximum error:
Ok thanks! Ive just flashed your latest nightly this morning. Wanted to do a totally clean update to AOKP M2 and your latest nightly. :) thanks again!
[Samsung Galaxy Nexus] luffyp:
Maybe you want to as this to the changelog of #12 and delete it from the common feature? I think this is an important piece of information.
[Samsung Galaxy Nexus] franciscofranco:
Later yes, I'm moving houses today, time is lacking.
[Samsung Galaxy Nexus] ironeagle:
YouTube FC :-( cleared cache/dalvik
[Samsung Galaxy Nexus] EddyOS:
It's a YouTube issue, not kernel

However, still getting lag on the lockscreen whilst only using this kernel. So annoying as otherwise it's spot on
[Samsung Galaxy Nexus] ellesshoo:
Franco, not sure if you recognize me from the NS forums but that's when I first tried your kernels. Any chance of getting some of Ezekeel's mods in this kernel? Touchwake or LiveOC? Those were my favorites.
[Samsung Galaxy Nexus] franciscofranco:
Change to interactive.
[Samsung Galaxy Nexus] franciscofranco:
Touch wake yes when the source is out. Live oc Im not planning that. I want this kernel clean, and thats whats it going to stay
[Samsung Galaxy Nexus] hosmsdos:
I have heard that #12 kernel has more blue colors than 11. Can I change this if I did not like it, without using terminal. And one more thing you said in ur app that we can change color now, I want to buy your app but I live in middle east and here we are not able to buy paid apps yet. Can I buy it outside the market or something and still receive update for it.

Thank you best kernel ever
[Samsung Galaxy Nexus] inffy:
You have to have the app to change the colours with out terminal.

Use market enabler or something to get to the paid apps.
[Samsung Galaxy Nexus] EddyOS:
Anyway to do that without using SetCPU or similar? Don't like using apps like that as I don't bother OC or the like
[Samsung Galaxy Nexus] Elganja:
you can do it within franco's app
[Samsung Galaxy Nexus] RTContent:
I'm having the same issue and this didn't resolve it for me. Any other ideas?
[Samsung Galaxy Nexus] nic85:
where is the app for change color?

a question for cpu in idle:

so in idle cpu is 700mhz conservative

this setting drain less battery than

350mhz interactive/ondemand?

because imo leankernel has 350mhz in idle and is much better..
[Samsung Galaxy Nexus] EddyOS:
No offence to Franco, but I'm not going to buy an app I'll never use. The whole point of using the kernel is to use it as it's supplied. I don't use apps to OC/UV as I'm not interested in that
[Samsung Galaxy Nexus] nicandris:
search in market for franco kernel

@franco any chance to add a confirmation when clicking on reboot recovery in the app? i think it was asked before also
[Samsung Galaxy Nexus] franciscofranco:
N4 uses a different Wi Fi chip, and thats the chip those drivers are made to.
[Samsung Galaxy Nexus] Hungry Man:
1.3ghz uses the same voltage (actually I undervolt it further, 1.4 uses less than 1.2 stock) but I rarely use it.

I have 1.4ghz on my system as the max frequency. I hit 1.2ghz once in a while but rarely 1.3 or 1.4. Why not leave 1.2ghz in so it doesn't clock up and then lower the 1.2ghz voltage?
[Samsung Galaxy Nexus] franciscofranco:
I'm going to add in-built volume boost once and for all instead of making it user configurable - just like I did on the Galaxy S3 (I'm not supporting that device anymore). It will be best for me and for the users.

My GF stayed in Portugal, she's finishing Dentistry graduation so she couldn't come with me, but all is ok on that front and hopefully will stay that way during my stay in the US :) Thanks for the concern though!
[Samsung Galaxy Nexus] franciscofranco:
Because I'd rather have more power with the same voltage than less power and less voltage.
[Samsung Galaxy Nexus] Hungry Man:
Right, but you'd be getting that. By making 1.3 ghz the default boost you gain a hgiher clock speed for a lower voltage (relative to stock). If you lower 1.2ghz further (it can use less than 1.3) all you do is stop clocking up as high.
[Samsung Galaxy Nexus] franciscofranco:
But I want it to clock that high, thats the main reason for the 100MHz boost. It rarely uses 1,3GHz though, only really when it needs to, and when it needs to run higher it will be faster and smoother than 1,2GHz.
[Samsung Galaxy Nexus] Hungry Man:
Alright, just not sure I get it. Like (to ridiculously oversimplify) if 70% load would get you 1.2ghz at X volts and 80% would get you 1.3ghz at X+1volts then removing 1.2ghz means youo'd be using X+1 volts for 70% load.

If they both used the same voltage then there would be 0 reason not to. Maybe for most people they do but for me there's a 45mv difference (not that that's significant). 1.4ghz uses very similar mv to 1.3 as well.

IDK, I'm sure you know better. Just not sure I understand it. But that's why you're the dev lol
[Samsung Galaxy Nexus] Culex316:
I am using the default interactive settings for r300 (6/6/4/1.5) except I put the hi speed load at 1306mhz because at 729 it would run my play station emulator more slowly and I found that this is perfect in terms of responsiveness for me. Battery life is the best I have ever remembered it to be. Not like the r28x builds where the drain was somehow quicker.

With my extended battery (3800mah) (and a lot of usage) I got 5 and a half hours onscreen time...yeah I bet you'll say "but you have an extended battery LOL" trust me with the usage I've given it I would have already drained a stock one dry in like under two hours lol
[Samsung Galaxy Nexus] jeetS:
why did you drop the s3?
[Samsung Galaxy Nexus] beren28:
Yay! The louder the better:)
[Samsung Galaxy Nexus] marcusva79:
Franco looking for the 4.2 kernel zip no findy
[Samsung Galaxy Nexus] murdah204:
It isn't available yet.... It's still in testing phase. Use fastboot
[Samsung Galaxy Nexus] marcusva79:
Okay will use that one. His apk still able to change colors?
[Samsung Galaxy Nexus] JBNex:
I have a question. Do high Color Multiplier values (200-300) damage your screen?
[Samsung Galaxy Nexus] joaquinf:
Yes you can change colors using fku and 4.2 kernel

Using high contrast values, among other factors, increase the chance to have burn-in screen on the long run.

Better be safe than sorry is what i think, keep it below 200 ;)
[Samsung Galaxy Nexus] Culex316:
Franco has stated that he will only support Nexus devices from now on since they are much easier to develop for.
[Samsung Galaxy Nexus] chickentuna:
S3 = Exynos = closed source = harder to develop. Main reason why codeworkx from CM Team stopped developing for Exynos powered devices. Also the main reason why Exynos devices are behind when it comes to updates.
[Samsung Galaxy Nexus] mordakk:
What I/O Scheduler is best and why?

BFQ, Noop, or Deadline?
[Samsung Galaxy Nexus] yellowdie:
The answer is yes.

BFQ was the default and favorite for a long time. The Franco made some improvements to Deadline and made that the default. It used to be just those two, but Franco just added noop and just recently made it default to test it and see what people thought.

So to answer your question: try them all and see what you personally think is best, then share your findings. Cool how all the research and development works, huh?

:):D:laugh::good:
[Samsung Galaxy Nexus] Hussainally:
Going to stock 200 bgr colours gives screen a yellowish tint...anyone knows what are francos recommended numbers? Love 215/200/222 but afraid of burn in
[Samsung Galaxy Nexus] yellowdie:
Clear app data and reboot and you'll have Franco colors. But really, don't worry about burnin when you're talking about 220's,that's totally fine. You MAY have an issue if you ran it for three to four years, but I don't think you will even have the phone that long. :). Enjoy what you like to look at. I run 200/150/250 (gamma: 0/5/10)
[Samsung Galaxy Nexus] arzbhatia:
Franco, vibration intensity? Please :(
[Samsung Galaxy Nexus] gianton:
I lost only 1% overnight (7 hours) with r313 on Kalo86's v3.0 ROM! Running 384/1536MHz max screen off 537MHz.

Great job Franco!!
[Samsung Galaxy Nexus] neo-X:
Yes this would be handy!

This is why I love Franco's kernel!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
anyone had SODs on this kernel?
[Samsung Galaxy Nexus] shawnaye:
Not unless you're undervolting, no.

Cmon, i'd expect someone with over 300 thanks to be a little more knowledgeable.

Unless it's your first time using a gnex and you're testing kernels.
[Samsung Galaxy Nexus] renzs:
So far so good. Been 25 hours or so. On kalo's rom

Sent from my GNEX JB 4.2
[Samsung Galaxy Nexus] rmcsc:
If by SOD you mean the phone not wanting to turn on the screen for about half a minute to one whole minute, then yes. Multiple times yes. Running latest (r312?) on 4.2!

Also, no, I'm not undervolting. Only thing I've changed are the colors.

DayDream off, too.
[Samsung Galaxy Nexus] Khizar:
4.2 is new, i had SODs on trinity today and i was using it with stock settings... these kernels are alphas so yes they will have issues.. as for being knowledgeable or not your post said it all :rolleyes:

---------- Post added at 02:04 PM ---------- Previous post was at 01:58 PM ----------

yeah i think i will stick with stock till the SODs are gone on custom kernels
[Samsung Galaxy Nexus] dyepnoodle:
where can i get the latest nightly?
[Samsung Galaxy Nexus] SahilC:
Speaking if burn in, btw, every time I use SwiftKey, and the keyboard goes away, you can kinda see the keyboard 'burnt in' or something. Is this a known issue with SwiftKey?
[Samsung Galaxy Nexus] Shadow-Nexus:
Not only with swift key but with anything else you leave on the screen for too long
[Samsung Galaxy Nexus] gianton:
Running r313 since Franco released it and had no SOD so far. I'm UV at certain speeds (384@775mv, 1420@1250mv, 1536@1300mv).

---------- Post added at 12:11 PM ---------- Previous post was at 12:06 PM ----------

Latest nightly is r313, with r312 I had SODs too.

Latest nightly here or fhashable zip here.
[Samsung Galaxy Nexus] Khizar:
will give the latest nightly a try :good:
[Samsung Galaxy Nexus] G-DannY:
it's perfect ;)
[Samsung Galaxy Nexus] Hungry Man:
Yiiiiiikes. Something went wrong haha tried to flash the latest nightly and couldn't get past the Nexus bootlogo. Not sure what happened, probably ROM Manager being dumb.
[Samsung Galaxy Nexus] Khizar:
i flashed the latest nightly a couple of mins ago, and phone booted up
[Samsung Galaxy Nexus] timbck2:
I haven't noticed that, and I use SwiftKey.
[Samsung Galaxy Nexus] malaroth:
Welcome to America Franco! So awesome to hear that you got the job. Maybe I missed it somewhere in the hundreds of pages of posts but with the new FKU I miss having the device support xda threads in links. Also every once in awhile it says must have busybox to show TCP algorithms. I have the pro version installed and finally forced it by changing it in trickster mod, then it showed up in FKU. But then it sometimes goes back to saying no busybox. Anything I can provide to help figure this out lemme know

Sourcerized, Milestoned, just missing the Cheetos and Redbull. http://teamsourcery.com/Images/teambanner.png FTW Keep the Magic alive!!
[Samsung Galaxy Nexus] Khizar:
flashed it and its been working good so far..hope it keeps on working like this :good:
[Samsung Galaxy Nexus] SahilC:
Nope, even if it's just open for a second.
[Samsung Galaxy Nexus] billykxda:
Scanned recent posts but it's not clear what benefits the latest nightly offers over r300.

Can anyone point out a few?

Thanks!
[Samsung Galaxy Nexus] The Gingerbread Man:
Compatibility with 4.2

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
Latest nightly is under JB 4.2 folder in minooch.com (http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/).

You should only flash it with a JB 4.2 ROM. Latest nightly for 4.1.2 is r300.
[Samsung Galaxy Nexus] billykxda:
Got it.

Thanks.

I am still waiting for the dust to settle on 4.2.

This time I'll let others take the "arrows in the back".
[Samsung Galaxy Nexus] johno86:
Could somebody make a flash zip for r313? The one posted a few pages back that clears the dalvik sends my phone into a bootloop so I had to restore. Would like to try out the new kernel =X
[Samsung Galaxy Nexus] The Gingerbread Man:
The latest build is fine, from what I read the first had some bugs but this one is fine

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
i flashed that zip and it works.. but i did wipe cache and dalvik before flashing
[Samsung Galaxy Nexus] johno86:
Thanks, I'll give it one more try.
[Samsung Galaxy Nexus] The Gingerbread Man:
I think the idea was it was released by Franco as an .IMG for a reason, can't think why that would be :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] johno86:
Thanks, I think I had an epiphany reading that.
[Samsung Galaxy Nexus] All-Star:
Does this work on CM 10 Stable(4.1.2) ?

My actually kernel is "franco.milestone 6"
[Samsung Galaxy Nexus] mordakk:
Can someone tell me which I/O Scheduler is best? Noop, BFQ, or Deadline...and why?
[Samsung Galaxy Nexus] gianton:
No latest 4.1.2 nightly is r300.
[Samsung Galaxy Nexus] All-Star:
Thank you.

Gonna test r300 now and then try Undervolting.

How much testing do i need ?