yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Blackcrx:
Long story short. I was a long term user of Franco but after he went to nexus 4 I strayed away since kernel releases dramatically slowed down. Used Lean, AK, and fancy (all great developers and kernels). Noticed today that Franco updated and decided to try it again. Wow, great kernel. Good performance and battery.

Using 192-1036. I/O settings from team Franco. Can't wait for this thing to settle and maybe even try osmosis undervolting
[Samsung Galaxy Nexus] kaluoshi:
:highfive: Thanks bro! Also loving the new app UI :)
[Samsung Galaxy Nexus] wavedashdoc:
New Franco 382 + Pa 3.60 + CrossBreeder 6.13.13 v3 = the smoothest my phone has ever been.
[Samsung Galaxy Nexus] Prasad:
Is it recommended to flash CrossBreeder on top of custom kernels like Franco and AK? Don't they already have such tweaks and would they not conflict?
[Samsung Galaxy Nexus] wavedashdoc:
I only use the entropy and DNS tweaks. Haven't had any issues. Make a nandroid and try for yourself.
[Samsung Galaxy Nexus] Prasad:
I have in the past, only to find more UI lag. This is precisely why I asked about conflicts.
[Samsung Galaxy Nexus] wavedashdoc:
There has been a lot of work, almost nightly releases. The newest v3 makes the nexus fly even more. Read up on the thread.
[Samsung Galaxy Nexus] 15israellai:
I was just struggling with some severe unknown lag when 382 came along.

Like a saviour.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] psyren:
Interesting read? :p
[Samsung Galaxy Nexus] Kappa Lamda:
It is a little off-topic but the differenxe is real? Are you sure it is not a placebo???

Because by default the first change is tha animations multiplier which takes tha 0.5 value. If you set it back to 1.0 there is no much difference here. Rasbean + 382
[Samsung Galaxy Nexus] wavedashdoc:
Yeah I revert the .5 animations and turn them back to 1. Still smooth as silk. I'd say your milage will very. I'm on pa 3.60 and it has improved DL speed and smoothness where before I was on mmuzzy and it wasn't needed. Only other tweaks is use the wining deadline tunables and change the build prop lines to 64, 384.
[Samsung Galaxy Nexus] shyamk:
Which is the best governor and scheduler for this kernel ?

Shyam
[Samsung Galaxy Nexus] The Gingerbread Man:
Bollocks accidental thanks...

Just leave as default settings but to answer specificly interactive and deadline
[Samsung Galaxy Nexus] thegtfusion:
And he needs to put the winning tunables of course.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] bigknowz:
BFQ

What are the winning BFQ settings? This is all I found
[Samsung Galaxy Nexus] Khrushy:
Back seek penalty = 1

Slice idle = 0
[Samsung Galaxy Nexus] vlc_marcos:
does any one have problems to start the game rr3? after i chage the kernel to franco with a full/clean installation i am not able to play it.

ideas??
[Samsung Galaxy Nexus] ChazzMatt:
reboots?

Flashed 382 last night, and this morning had a series of reboots much like many have had with the AK 250s kernel series. :confused:

So, back to 378 Osmod for now.

This weekend will clean flash my Slim ROM again and try 382 again... but for now 378 Osmod runs perfectly.
[Samsung Galaxy Nexus] Khrushy:
This is unfortunately an rr3 problem. The game looks at the GPU clock and decides it's a high powered system.

I think there's an rr3 patch for it, but it's not in this thread sorry. :(
[Samsung Galaxy Nexus] jerom87:
CIFS

hi Mrc527, can you repeat this with a version for 4.2.2?
[Samsung Galaxy Nexus] Spoderman:
Running flawlessly on 382 ;)

I think my device might be blessed, i only install Franco's Kernels, and don't mess with tunables, but i never got lag downloading a big file or while the play store was updating, i can't tell the difference between Franco Kernel 300 or 382, both are smooth either way, and i've tryed the osmod versions when i got the chance (378 osmod) and there was no changes at all :)

Never got random reboot, not even once!!! My wifi is great, it doesn't drop down when the phone locks, same for Bluetooth. I always get 3h+ of screen on time before 5% battery left.

My device is made for this kernel lol
[Samsung Galaxy Nexus] Blackcrx:
FYI: you can remove your accidental thanks. Just click on "expand" and on the far right side there is a "remove thanks" option

---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------

I dirty flashed slim 6.2 when I installed 382 and everything seems fine right now, but then again I came from Fancy kernel. Since you are coming from 378 os latest I don't think a dirty flash would be needed, but worth a shot
[Samsung Galaxy Nexus] SahilC:
Didn't work on Tapatalk :S

Free thanks for you. :p
[Samsung Galaxy Nexus] Milleniumlance:
Ondemand>Deadline>1.4Ghz....like butter no skipping at all thx franco!, if you are getting any skipping trying wiping cache partition and dalvik and clear app cache
[Samsung Galaxy Nexus] The Gingerbread Man:
You can if you go to the main xda site from tapatalk
[Samsung Galaxy Nexus] SahilC:
Thanks so much franco. Underclocked to to 1000, hispeed at 500. Super smooth, great battery life. :good:

Btw, my colors in case anyone cares:
[Samsung Galaxy Nexus] Prasad:
I'm loving the new kernel! Just one question about Trickster MOD: I applied a few changes.. but even after selected Apply on Boot, it reverts to defaults after restarting. Please advise. Also, what's the difference between Apply on Boot->Delay and Apply Grace Period?
[Samsung Galaxy Nexus] Stigy:
hispeed_freq at 537MHz?

Just looking to try some new settings, thx.
[Samsung Galaxy Nexus] SahilC:
Yep. Correct.

Inspired by [MENTION=2853378]Nephilim[/MENTION]'s settings.

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

Did you check Enable?

---------- Post added at 10:18 PM ---------- Previous post was at 10:18 PM ----------

Did you check Enable?
[Samsung Galaxy Nexus] Prasad:
I have, yes. Figured out it had to do with me having superSU and the ROM's default superuser app would grant root to superSU and superSU to everything else. This delay probably denied root to Trickster MOD at startup.

Now that it works, I have another question. All options are now being set as per my liking, except the 3 Reflex Controls being reverted to off ?
[Samsung Galaxy Nexus] bigknowz:
Hard Coded

Aside from deadline and bfq, i/o settings are hard coded . You can use the delay option in trickster so settings apply after kernel has set, it should let you overwrite the hard coded values. If not, you can use init.d script with a delay (wait for systemui).
[Samsung Galaxy Nexus] Prasad:
Thanks. Can't Trickster MOD write to init.d like Voltage Control can?
[Samsung Galaxy Nexus] mrdevil_25:
from what i read, the voltages are hardcoded so SR isnt doing anything - which is why they are off.
[Samsung Galaxy Nexus] swayjd:
My phone shuts down and its been like this since the past maybe 5 or 6 versions, I'm not the only one am I?
[Samsung Galaxy Nexus] thegtfusion:
That is really weird, I use franco for a loonggg time, never had a reboot, or shutdown or anything unstable.

:D :D :D
[Samsung Galaxy Nexus] xFuGiToiDx:
Never had an issue with any of Franco's kernel... Try flashing osmosis emergency kernel flash reset zip and then flash Franco's r382
[Samsung Galaxy Nexus] Prasad:
I dunno why SmartReflex control keeps reverting to off? Even when I haven't restarted..
[Samsung Galaxy Nexus] swayjd:
Hum, I have this for a very long time, If I flash AK I don't have sleeps of death. As soon as I flash Franco, 4 or 5 hours later, phone is off. I Like how franco feels better but its frustrating to have it off and not knowing.
[Samsung Galaxy Nexus] xFuGiToiDx:
Are u running stock 4.2.2 or custom ROM?
[Samsung Galaxy Nexus] kuyam:
I believe it's not in the kernel at this moment, so it would make sense.
[Samsung Galaxy Nexus] Sik-1:
Its stays off regardless of what you do. Its built that way, that's what is meant by hardcoded .

He turned it off for ppl complaining about undervolting and them not being able control the way the CPU is built with smart-reflex,

Personally it isn't required by the user to undervolt anymore, the savings are minute to what we already have established
[Samsung Galaxy Nexus] The Gingerbread Man:
I guess this small problem I had this morning could be app based or pure coincidence but I'll tell any way. So I was trying to watch a number YouTube videos and I kept getting YouTube not responding messages which was fine, then this morning had I not of had to wake up earlier than expected my alarm failed to go off at 6.30, no sound but there was a message saying clock not responding, I went to update fku and tapatalk and updating fku completely froze my phone, it got stuck at 'imstalling' I had to pull battery to force restart. So the apps in question, clock, YouTube, play store, and these issues probably aren't directly kernel related but I was wondering of this might have somethimg to low memory killer values perhaps? No log I'm afraid as had to battery pull.
[Samsung Galaxy Nexus] binlalo:
Does anyone have wifi issues with the latest release? I don't get any notifications until I unlock the phone. It looks like my phone sleeps too deep xD.

I'm coming from kubo kernel but flashed stock kernel and revert wifi drivers before flashing franco's. Any ideas?

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Sik-1:
Goto WiFi and make sure WiFi optimization is off in the advanced menu
[Samsung Galaxy Nexus] binlalo:
Wow, that was easy. Does it come activated by default in this kernel? Because I didn't activate it.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
It's default for the OS
[Samsung Galaxy Nexus] whitedragonz83:
I have the optimization on and only rarely have the same WiFi issues you described. It usually occurs when in try to turn WiFi off and on. Seems like it forgets to stay on when in am in sleep mode. Another on and off, or reboot, usually fixes it.
[Samsung Galaxy Nexus] hunterjackson92:
Hey Franco idk if this is just me or if this is a know issue but ever since you updated your the gui in your app it doesn't look to see what version of android your devices is running and automatically suggests 4.2.2 kernels. I run 4.1 and that's almost messed me up bad.
[Samsung Galaxy Nexus] sajty:
Hi to all.Can some,please,tell me,what are correct tunables values for CFQ?Talking about:

1) fifo_expire_async

2) fifo_expire_sync

3) slice_async

4) slice_sync

For 1),i see in franco commit 11,but my phone shows 335

For 2),i see in franco commit 42,but my phone shows 85

For 3),i see in franco commit 7,but my phone shows 54

For 4),i see in franco commit 8,but my phoe shows 62

Which numbers are correct?Thanks in advance.
[Samsung Galaxy Nexus] osm0sis:
They're all correct. That commit results in those tunable values. See here.
[Samsung Galaxy Nexus] DriftGT:
Its possible to change the gpu speed? With this kernel I cant play most wanted because game start with the maximum graphics because the 512 MHz Gpu and the game became slow. With ak kernel Its great.

I need a way to underclock gpu or change manually the graphics in the game
[Samsung Galaxy Nexus] swayjd:
CM
[Samsung Galaxy Nexus] DanielSanchez:
Just use search. Known issue.
[Samsung Galaxy Nexus] osm0sis:
And more the game's fault for using such a stupid method to determine graphics quality.
[Samsung Galaxy Nexus] DanielSanchez:
Most wanted sucks, so is actually more of a feature.
[Samsung Galaxy Nexus] xFuGiToiDx:
Are u using trickster mod to tweak the kernel settings?
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco would you consider changing min CPU speed from 192 to 256? I'm curious to see the effect of performance vs battery. Iv changed my min CPU speed to 384 which seems a little high and I changed it to help remove a few tiny little stutters in some scrolling areas like my contact list and SMS indox over view. These contain images and text and scrolling these areas is smoother with the higher speed but I'd be curious to try 256 as that's the next logical step between 192 and 384.

My step up for now is 384-1036mhz 537 hispeedfreq interactive with cfq. Its damn good on battery and very smooth overall
[Samsung Galaxy Nexus] DriftGT:
I try but I dont know what to search. Can you give me the tip to help me?
[Samsung Galaxy Nexus] MisterEdF:
Getting boot loops on v14. Had to drop back to 13.1.

Running Open Kang latest.
[Samsung Galaxy Nexus] Nebucatnetzer:
Are you using his first version? Redownload and try again if yes.
[Samsung Galaxy Nexus] Puzzlegirl:
I'm getting a signal loss every time the screen goes off. (I know this because I used Lightflow to set a sound when signal is lost.) As soon as I turn the screen on, the signal wakes up and comes back. Anyone else seeing this? Everything else seems to be working fine.
[Samsung Galaxy Nexus] aimetti:
well i stand corrected , no boot loops but i lose service completely after phone sits for a bit.
[Samsung Galaxy Nexus] Manya3084:
Definitely using the latest uploaded version.
[Samsung Galaxy Nexus] dwang:
Yep reported this a few pages back.
[Samsung Galaxy Nexus] chakra:
I am on CM9 kang and I had the bootloop lastnight with Francos 13.1, I have to use fastboot to reload the stock firmware, even my backups would work. I think it may have to do with the ROM, as I now have the most recent CM9 kand and Fracos new 14 adn I am doing fine today.
[Samsung Galaxy Nexus] dyndragon:
Running the CM9 kang with #14 last uploaded with no problems. I am UVing extra beyond the kernel defaults, hotplug enabled, 700/1200 conservative.
[Samsung Galaxy Nexus] dajmanjt:
14 caused permanent boot looping at the Google logo... Running open android 1.1.4. Cleaned everything before flashing and went to Constant boot loop immediately. I always flashed faux reset kernel before every kernel flash. Went back into recovery and flashed faux newest kernel and everything is running just fine
[Samsung Galaxy Nexus] samizad:
I wiped Dalvik cache before upgrading from #13.1 to #14. I have had no problems with the kernel. I am using AOKP Build 20 ROM. Could the problem be related to the Dalvik cache?
[Samsung Galaxy Nexus] aimetti:
I wiped all cache did a format all data factory reset and installed nandroid backup then flashed kernel and still lost signal on aokp
[Samsung Galaxy Nexus] samizad:
Sorry if I come across as a complete noob but did you wipe Dalvik cache again before flashing the kernel AFTER restoring your nandroid backup?
[Samsung Galaxy Nexus] franciscofranco:
People with problems before, can you test me this pls: http://www.box.com/s/p42kjlxj7xl035984yae
[Samsung Galaxy Nexus] Manya3084:
phone booted and seems to be working. i'll play around with it for an hour and see what happens.
[Samsung Galaxy Nexus] franciscofranco:
It didn't work before for you?
[Samsung Galaxy Nexus] optmkleung:
Fine, bootloop disappear. AOKP 20, Bootloop forever before.
[Samsung Galaxy Nexus] Manya3084:
couldn't even boot when i updated with the release 14 build. did a full wipe, was able to boot, then while during setup the phone froze and boot loops began again. this is with CM9 Kang 25/01 release.
[Samsung Galaxy Nexus] jhericurls:
Same here, signal died a few times. Checked my battery meter and it showed a few red marks on the chart.

also been getting the mystery voicemail bug.
[Samsung Galaxy Nexus] IINexusII:
yep, boots fine now :), signals seem fine too after locking the phone
[Samsung Galaxy Nexus] franciscofranco:
But now its fine right?
[Samsung Galaxy Nexus] nktje:
This is probably a PEBKAC case but has anyone else experienced SODs with 382? 378-osmod works just fine but 382 gives me frequent SODs.

The only f.ku settings I've changed are high performance sound and TCP congestion algorithm (westwood).

FWIW I'm running minco v7
[Samsung Galaxy Nexus] osm0sis:
We used to run 230 MHz if I recall correctly but we found that caused SODs? Not sure why 192 wouldn't too. :confused: I recall asking for 230 instead of 192 at one point too before we'd resolved a lot of the 192 stutter, but Franco didn't want to because the gap to 384 would too small to matter in terms of battery. I'm getting along okay with 192 overall min, but personally I'd still like to have a min screen off so that we could automatically use 192 min when we're idling but 384 min when screen on for smoothness.

Ezekeel's High perf sound and headphones volume boost are the buggiest interfaces in f.K. Enable only when needed. Content adaptive brightness in color settings has also been known to cause SODs one way or the other on some devices.

---------- Post added at 08:35 AM ---------- Previous post was at 08:18 AM ----------

Also here's a bfqv5 commit from fancy kernel that hardcodes the values [MENTION=4793042]pkgnex[/MENTION] (also?) came up with in his bfq quick-tune:

https://github.com/boype/kernel_tuna_jb42/commit/1d37568801f86b11d9076b5f6a7f8f8e76c3703c

And another that boype came up with on the kernel side to make my lmk whitelist script work better:

https://github.com/boype/kernel_tuna_jb42/commit/50ca6f84c54b79b9533c6a7ad77aeb57bf21f572

Should definitely pick these [MENTION=3292224]franciscofranco[/MENTION] :)
[Samsung Galaxy Nexus] sajty:
Yes,those values were recommended by pkgnex.I used them,test them and recommend to boype,who hardcoded them into his kernel.
[Samsung Galaxy Nexus] osm0sis:
Yeah.. I noticed. I'm going to request that the credit actually go to [MENTION=4793042]pkgnex[/MENTION] or Franco's Dev Team then.
[Samsung Galaxy Nexus] sajty:
Answered in fancy thread.
[Samsung Galaxy Nexus] osm0sis:
Thanks. We're good, man. :good:

Also boype is fast like the wind and just corrected it: https://github.com/boype/kernel_tuna_jb42/commit/60752bdbb8209536145fed1f68a29614a3499984

[MENTION=3292224]franciscofranco[/MENTION] pick this one instead please. :)

It's funny when "Franco's Dev Team" stuff makes it into other kernels before franco.Kernel. ;)
[Samsung Galaxy Nexus] garu12:
Man this kernel is a real performer. Feels perfect. Having problems though. Phone has froze completely 3 times so far. Screen on just frozen. Twice doing nothing really (web browsing etc) and once when launching the camera. No logs since had to pull the battery. Running cm r5 no tweaks at all default kernel settings. Had to flash off for now. Wish I had more info but thought I'd just weigh in.
[Samsung Galaxy Nexus] thegtfusion:
Weird. I use it for a long time now, and no freezes or any unstable ****. Which kernel app do you use? Maybe you have 2 kernel control apps installed which interfere which each other. Just a guess.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] garu12:
Na not a bad guess but only fk app. Also fresh installed everything (always do) to make sure. Yea I never had issues with Franco in the past either. Maybe its a cm/Franco thing.
[Samsung Galaxy Nexus] thegtfusion:
Hmmm.. Then I don't know. Maybe [MENTION=4544860]osm0sis[/MENTION] knows?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] The Gingerbread Man:
It did freeze for me once I'm stock rom updating an app from play store, only happened once for me though. I wasn't able to get a log as I had to battery pull too.
[Samsung Galaxy Nexus] osm0sis:
I'd say flash my emergency reset zip anyway just to be sure, and make sure everything in CM's Performance settings are disabled.
[Samsung Galaxy Nexus] gummie:
Im quite interested on the controversial BFQ values and wanna try it. Is that already hardcoded since r378 (yes I'm still in it) or its on r382 already? I wish to know the values for each i/o control.
[Samsung Galaxy Nexus] AndyGnex:
No they haven't hardcoded it yet.. But you can check out [MENTION=4793042]pkgnex[/MENTION] posts to see the recomended values
[Samsung Galaxy Nexus] gummie:
I quickly downloaded osm0d installer but it seems to not yet encoded on iosettings init.d script.
[Samsung Galaxy Nexus] osm0sis:
Nope it's a bonus. Should be in a future build here, (hopefully) soon. I didn't want to put it in 950io since it isn't a full tune of bfq, just a quick tune. pkgnex referred to those tweaks as "the low hanging fruit". :)
[Samsung Galaxy Nexus] marcocsh:
I think it's better to put the options of "Automatic flashing" and " Automatic data clearing" in the "franco.Kernel Updater" page. Anyone agree?:fingers-crossed::fingers-crossed::fingers-crossed:
[Samsung Galaxy Nexus] giorgis91:
Is there Hyper governor in this kernel?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Edward Stanbury:
nope there isn't sorry
[Samsung Galaxy Nexus] whitedragonz83:
Any idea why with the latest nightly and latest app I can not change my max CPU frequency and have it stick beyond that app screen? I cleared app data already from within the app.

Not sure why, but an hour or so later, I was able to adjust frequencies again.

I do not believe I changed anything in that time period as all I did was drive to work. No worries.
[Samsung Galaxy Nexus] AndyGnex:
Anyone used Hyper on other kernels? How does it perform, compared to our optimized interactive here on Franco's?
[Samsung Galaxy Nexus] thegtfusion:
Franco's interactive is better for me.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] AndyGnex:
At some point after I submitted the question, I was getting paranoid about getting governors and schedulers mixed up. :p

Anyway, im on latest cm10.1 nightly that has the memory leak fix (the fix was incorporated a few builds back).. still on cm's stock kernel to see how much the rom improved, coz im afraid flashing franco's might cover up any stutters with its awesome smoothness :good:
[Samsung Galaxy Nexus] bombadier:
Am trying BFQ with pkgnex's tweaks and have to say so far so good on 382, last time I tried BFQ got random reboots.

With setting raising_max_time to 0 it has naturally changed to 1391 seems smoother as well, setting raising_max_softrt_rate to 2000 has given me no problems after about half a days use so will see how I get on over the next couple of days
[Samsung Galaxy Nexus] bigknowz:
BFQ

Same here. 3 days in on 382 with BFQ. raising_max_time at 1301 for me. Will report if any issues.
[Samsung Galaxy Nexus] gummie:
I really got curious on those settings so I got to Fancy Kernel and tried out BFQ there and look for the changed values and collaborated them with pkgnex's posts. So here are the lines I added on the 950iosettings from osm0d.

elif [ $scheduler == "bfq" ]; then

# bfq tweaks

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty
echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 0 > /sys/block/mmcblk0/queue/iosched/raising_max_time
echo 2000 > /sys/block/mmcblk0/queue/iosched/raising_max_softrt_rate

Like osm0sis told, He did not include this lines as this are not full tune for BFQ. For those who wanted to try, just add those codes somewhere at 950iosettings script or set them on f.KU.
[Samsung Galaxy Nexus] nktje:
Disabling those two settings seemed to do the trick, cheers!
[Samsung Galaxy Nexus] pkgnex:
Thanks for the feedback on raising_max_softrt_rate=2000. Glad to hear everything is working for you.

I saw the same thing with raising_max_time, btw... adjusts up to about 1300-1400 range, then may drift down and back up, but stays really smooth!
[Samsung Galaxy Nexus] Efrenjr15:
Anyone have a link to these bfq tweaks I'm hearing about?
[Samsung Galaxy Nexus] bombadier:
Look at my post,have linked the original

Tapatyping
[Samsung Galaxy Nexus] njiki11:
What can I do if I'm coming from AK's kernel. Because every time I flash Franco's kernel my phone gets really hot and the battery life is horrible. I know Franco kernel is extremely good so what do I need to do to optimize this kernel?
[Samsung Galaxy Nexus] gpzbc:
Flash osmod's emergency reset zip found in his signature. That may fix your issues.
[Samsung Galaxy Nexus] Coolgoly:
3rd post of AK kernel thread, anarkia1976 wrote:

Do you want to restore old kernel or another kernel? Before flash you have to do:

Step1: Download script manager (https://play.google......scriptmanager)

Step2: Disable Wifi, Tethering ecc ...

Step3: Run as root /data/ak/recovery_wpa_hostapd.sh

Step4: Goto to recovery and flash your new kernel

or

Flash this ZIP from recovery:

ak.restore.OLD.WIFI.zip
[Samsung Galaxy Nexus] pkgnex:
Wow, what a PITA!
[Samsung Galaxy Nexus] parkson:
Just flash the restore file and new kernel in the same recovery session and you're good to go.