yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mixtapes08:
Or just reflash your rom? Way better than that..

-3StarsAndaSun
[Samsung Galaxy Nexus] klobkelosh:
Or just dirty flash your ROM + gapps then install kernel
[Samsung Galaxy Nexus] osm0sis:
Clean flash would be the better choice since dirty would leave some of the AK stuff behind, active or not.
[Samsung Galaxy Nexus] pkgnex:
BFQ and Deadline Tweaks (until hard-coded)

Nothing new in this post... but I've seen enough questions lately that I thought I'd put all the values in one place for reference, rather than scattered across many:

Deadline and BFQ Tweaks

courtesy of Franco's Dev Team (RoW and CFQ tweaks are already hard-coded into the kernel as of r378):

Deadline:

read_expire=250

write_expire=2500

writes_starved=1

front_merges=1 (important)

fifo_batch=8

BFQ - will work with v5 (current franco) and v6 (some other kernels):

back_seek_penalty=1

slice_idle=0 (really, really, important)

raising_max_time=0 BFQ will then auto-tune this value higher and smooth out)

raising_max_softrt_rate=2000 (most report improvement, if you have issues, revert this to 7000 and post in franco.kernel thread)

Feel free to pass these along, but also please make sure to credit Franco's Dev Team as applicable, as a lot of effort went into nailing these down!
[Samsung Galaxy Nexus] klobkelosh:
Really? I confess,I don't have a copy of an ak kernel to check it out, but I believe his kernel only pushes junk to /system and not /data so anything installed would be wiped by the ROM install script which should format the system block. All that said, osmosis would know better than me...
[Samsung Galaxy Nexus] AndyGnex:
After these guys are hard coded, i suppose we will get a new nightly and a testing phase to determine which one works best for most people and the prefered scheduler will be default in the milestone?

Or we will get a milestone and let people choose for themselves :highfive:
[Samsung Galaxy Nexus] szale9001:
Just out of curiosity. Why is front merges = 1 for deadline marked as important?
[Samsung Galaxy Nexus] Blackcrx:
AK kernel pushes files to data folder also
[Samsung Galaxy Nexus] klobkelosh:
D'oh...
[Samsung Galaxy Nexus] Khrushy:
Because front merges = 0 murders your SDCard transfer rate. We found that one out the hard way.

Edit: wait, no, that's no_merges = 1 in VM settings that murders the sdcard. Front merges in deadline was just a consistently smoother setting.
[Samsung Galaxy Nexus] The Gingerbread Man:
Deadline will probably stay as default but your free to change at any time just like how have the freedom of choice now. I'm really hoping next release deadline and bfq will be hardcoded. I notice also 3.0.82 Linux kernel version has been released so perhaps Franco could squeeze a cheeky one out with these changes ;)
[Samsung Galaxy Nexus] pkgnex:
Yep, this:

"Front merges in deadline was just a consistently smoother setting."

Nearly every data though-put test we ran on both Tuna and Grouper showed improvement with front_merges=1.

Franco seems to like Deadline, so if I had to guess at a default i/o scheduler in the milestone, that would be it. The great thing is, if you like one of the other schedulers better, you'll have plenty of really good options!
[Samsung Galaxy Nexus] DoesntPostAThing:
AK kernel pushes 3 init.d scripts as well as the /data/ak folder. The data folder is annoying. You have to manually delete everytime you switch from AK to another kernel, but AFAIK all that junk does nothing and you can delete them even if using AK kernel.
[Samsung Galaxy Nexus] AutomaticFailure27:
I really wouldn't worry about it. Most of the stuff that is pushed is scripts that made it easier for his users to pull bug reports or activate hidden governors. Best thing to do is clear out the init.d folder, flash the ak.restore.OLD.WIFI.zip, dirty flash your ROM, and flash kernel.

I came from AK, did just that, and have seen not one issue.
[Samsung Galaxy Nexus] MaLiXs:
Clean flash will always be the safest and easiest way to get the best results

Send from my Pure Franco GNex
[Samsung Galaxy Nexus] Idrito:
a wallpaper i made for this kernel :D

https://plus.google.com/112361011528566307846/posts/hm6MfFenFdP
[Samsung Galaxy Nexus] Blackcrx:
If you dirty flash the ROM you don't need to do the wifi revert
[Samsung Galaxy Nexus] osm0sis:
Depends if the ROM script wipes system before it writes, or if it just overwrites. Not all the zips work the same, as far as I know..
[Samsung Galaxy Nexus] AndyGnex:
is there a time frame for bfq autotuning raising_max_time parameter? i've been using bfq for half a day and it seemed to max at 256 for now.
[Samsung Galaxy Nexus] XxStechxX:
I don't want to seem ignorant, does this kernel work on a vzw phone? I'm running off the rails between work & my wife handing over our newborn as soon as I walk in the door. Haven't had much time to read
[Samsung Galaxy Nexus] Empty Hand:
Yes, been happily running Franco kernels for over a year on my VZW GNex. Good luck with the newborn. It gets easier...eventually.
[Samsung Galaxy Nexus] XxStechxX:
Thanks
[Samsung Galaxy Nexus] nitsua98:
For some reason turning off CAB got rid of some lag I was having...
[Samsung Galaxy Nexus] DoesntPostAThing:
382 is great! Also no overheating if controlling using FKU.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sym_m:
+11111

undrclock + r382 Best kernal with Cataclysm rom
[Samsung Galaxy Nexus] bunnahabhain:
ARHD here and with Franco Kernel It runs perfectly. Much better than any AOSP or Cyanogenmod Rom. I think for Android 4.2.2 the Stock Images are the way to go

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] DoesntPostAThing:
Supernova ROM is good too.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] supernova_00:
Franco backed out the patches for BFQ v6 so that is why you aren't having reboots anymore.

http://xdaforums.com/showthread.php?p=41240006#post41240006
[Samsung Galaxy Nexus] whitedragonz83:
I'm excited for milestone release so we can see his new interactive tunables! If that was the Mako ports he was bringing here. Doubt it would be anything with his hotplug driver as it sounded like with Mako you always wanted at least 2 cores always.
[Samsung Galaxy Nexus] Efrenjr15:
On the osmosis emergency kernel reset how does one flash it.

Wipe cache and dalvik then flash emergency reset then flash the latest nightly?
[Samsung Galaxy Nexus] osm0sis:
Milestone is going to have the current tweaked-out interactive. After that things will get experimental again. ;)

Just flash it. Doesn't matter if it's right before or a week after the kernel. Also, it clears the dalvik and cache for you.
[Samsung Galaxy Nexus] Efrenjr15:
im coming from Fancy kernel, would i flash your .zip first then franco?
[Samsung Galaxy Nexus] osm0sis:
If you want, it's more for kernel apps and init.d interaction problems. Fancy, like AK, has some WiFi mods, so most importantly you should make sure you have undone those first if they modify system or data.
[Samsung Galaxy Nexus] ciprianruse88:
This kernel is the best kernel on every device that is supported by Franco. Used it on gnex on 4.1.2 and later on 4.2.2 last period and now using it on nexus 4 and it's simply amazing.fast,stable and super battery life...absolutly perfect! Cheers guys !:beer::thumbup:

Sent from Inferno
[Samsung Galaxy Nexus] garu12:
So checking back in. Clean flashed Rasbean (was on cm) and within an hour got another lock up. Screen on stuck. Had to battery pull. No tweaks at all completely stock settings. Lol I must have crappy luck or something cause this kernel hates my phone. Runs so good besides that but its kind of a deal breaker. Nobody else?
[Samsung Galaxy Nexus] Sik-1:
Try turning off CAB in fku or trickster
[Samsung Galaxy Nexus] garu12:
Hmmm you think that's it? Was thinking maybe its the bfq io. I never use that ever but left it being the default
[Samsung Galaxy Nexus] marcusva79:
Where is cab? Couldn't find it.
[Samsung Galaxy Nexus] bombadier:
Colour Control dude :victory:
[Samsung Galaxy Nexus] creeve4:
Content Adaptive Brightness

In Trickster it is on the Specific page.
[Samsung Galaxy Nexus] DoesntPostAThing:
Where is RABS in FKU?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lightingcloud:
Yesterday night I was "let's try deadline" and this morning my gnex was like "play store freeze lol" and now I'm back to ROW.
[Samsung Galaxy Nexus] Sik-1:
The deadline tune is currently not in this kernel build and if u wanna try deadline download osmosis's init.d script and flash it then run deadline again, we'll see if u go back to ROW lol
[Samsung Galaxy Nexus] lightingcloud:
The winning aren't still in the kernel? I thought they were o_O well, I don't think I'll try, I'm fine with ROW.
[Samsung Galaxy Nexus] mrdevil_25:
are you referring to the 950iosettings script from os' signiture?
[Samsung Galaxy Nexus] pkgnex:
Did you reset that parameter to "0" in f.Ku or via a script?

If not, then maybe BFQ has determined 256 is right for your device and current settings since the auto-tune is dependent on hardware and other items. For example, if you are underclocked or have low available memory left it might not ramp up much. We didn't really test too much outside the stock kernel settings and stock-ish ROMs, so I'm not sure what to expect if you're running something unique.
[Samsung Galaxy Nexus] mrdevil_25:
for whatever reason my battery life with 382 isn't very good. The phone normally last me the day with moderate use (music, a little bit gaming and lots of chats) with around 3 hours screen on time. 18-24hours total time on battery.

with recent update to 382, i've been getting been getting around 15-18 hours of total battery time but only 1 hour screen on time.

something i've also noticed is idle drain. usually overnight drain is around .8% or so per hour. with 382 it is sitting at 1.2-1.4% per hour.
[Samsung Galaxy Nexus] osm0sis:
Not the case here. Did you update any apps recently? I'm at 0.2-0.4%/h, ~1d on battery and still my usual 3h+ screen on..
[Samsung Galaxy Nexus] mrdevil_25:
Thanks for the reply. I probably update my apps once every 3-4 days so yea, some of the apps have been updated since 382 came out. But for me its been pretty consistent as far as the battery performance is concerned.
[Samsung Galaxy Nexus] AndyGnex:
It was 256 for a couple of days, maybe its because i didnt do much in that period, mainly just some messaging and calls.. now i've been doing more browsing, and a couple of games more than i usually do, the value now is 1646 :p

what does it do actually? i mean the parameter? How does it help the system run smoother? My phone was just a little bit jittery when when i first tried bfq, but now it seems to be on par with cfq, whether it is better, i really cant tell.
[Samsung Galaxy Nexus] pkgnex:
Well, here's from some BFQ documentation:

"max_budget: the maximum amount of service, measured in disk sectors, that can be provided to a queue once it is selected (of course within the limits of the above timeouts). According to what we said in the description of the algorithm, larger values increase the throughput for the single tasks and for the system, in proportion to the percentage of sequential requests issued. The price is increasing the maximum latency a request may incur in. The default value is 0, which enables auto-tuning: BFQ tries to estimate it as the maximum number of sectors that can be served during timeout_sync."

So, the "auto-tuning" of this parameter is basically BFQ attempting to find the best trade-off between maximizing overall throughput whilst minimizing latency... this value obviously changes over time, I'm assuming depending on the status of your device and the load that is / has recently been on it. I do not know the time constant or averaging period it uses or any more basic details at this time, though... just that it seems to do it's job fairly well.
[Samsung Galaxy Nexus] Raijin:
Using Galaxy Nexus with stock Android 4.2.2 and Franco Kernel r382.

This afternoon, my Galaxy Nexus had a freeze when I pressed the return button in the navbar. Some times my phone freeze when I press virtual buttons. This can happen every 3-4 days. Nothing strange.

Well, I just pull the battery and reboot, like usually. The phone started and, after 2 minutes, another freeze. Then the phone can't start. It stucks in Nexus logo bootanimation.

Bootloop restarting to Google and padlock of bootloader unlocked. Then again bootanimation, and etc.

I felt the area around camera so hot. I left the phone without battery, started the air conditioning and waited.

Finally it could start. I could enter Franco app and saw the CPU varying between ~74-82º, and the room was cold. Shortly after, another freeze.

I flashed the Osm0sis kernel emergency reset zip with no results. I remember having freezes in recovery.

At a time, phone could not start. I tried to flash Yakju JDQ39 (4.2.2) and phone stucks and reboot in bootanimation. Even I tried to flash Cyanogenmod 10.1 latest nightly with the same result.

I get the message "Fastboot Command Read Error -2147483647" in the bottom of Fastboot screen. Tried multiple USB cables and ports and it doesn't leave.

Now I will try to install the USB drivers in my laptop and flash the firmware there. If it doesn't work, I will send my phone to SAT.

Someone else had this problem? I'm thinking to buy a Nexus 4 and sell my Galaxy Nexus when phone returns from SAT because I can not be without phone.

EDIT: Tried in laptop and still getting -2147483647 error. I have been able to start phone in some moment, and after entering PIN, screen off and shutdown again.
[Samsung Galaxy Nexus] AndyGnex:
Thanks for the explaination....Hmmm, if BFQ continues to be as smooth as it is now, i think i'll just stick with it :laugh:
[Samsung Galaxy Nexus] osm0sis:
Hmm that's bad luck there man... :(

I'd try OMAP flash, then fastboot the stock ROM if you get that far.
[Samsung Galaxy Nexus] Bosio91:
I'm having the same issue, maybe worse. My average battery drain when the phone is locked without using it is 3-4% per hour. When I'm using the device normally, it goes up to 17-25% per hour drain, using simple apps like Phone, Whatsapp, and Tapatalk.

I'm on takju 4.2.2 (stock) and franco r382, using [MENTION=4544860]osm0sis[/MENTION] settings.

Any idea what could it be?
[Samsung Galaxy Nexus] osm0sis:
I've heard Whatsapp is kind of a problem app as far as wakelocks go.. Either way, it's pretty much always apps. Hang out in the BBS thread and post your logs. If things are sleeping correctly there is no difference in drain between any of the recent builds.
[Samsung Galaxy Nexus] Bosio91:
Thanks osm0sis, you're always of great help :)
[Samsung Galaxy Nexus] bigknowz:
Stuck at Nexus Logo

I had the same issue on Monday. Had to flash factory image, radio, and bootloader to get my phone back. If you can't do it manually, try one of the toolkits out there.
[Samsung Galaxy Nexus] ReMuSeR:
[MENTION=4544860]osm0sis[/MENTION] hi mate im using Purrity with your Franco Kernel settings omosmod

my phone gets really hot when i use it so is there any voltage i should change that my phone dosnt want or so is there something i can do to test and see if i can fix :)

thanks...

sorry for bad english
[Samsung Galaxy Nexus] osm0sis:
Flash my emergency reset zip and see if that helps. People have reported heat issues when there are several control apps competing.
[Samsung Galaxy Nexus] Tex99:
I have r382 and franco app. If I check the option CAB, when i reboot the phone, and appears the lockscreen, if i wait that the screen go off, i have a reboot, also the second time ecc

Sorry for english :D

Ah and for scheduler it s better deadline (with your tunables settings) or bfq ? Thank you

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah that's a bug, a fairly rare one. I don't think there's anything that you can do apart from not use it
[Samsung Galaxy Nexus] pkgnex:
Or, of course, the other obvious work-arounds:

1. Do not wait for your screen to timeout after reboots before unlocking it.

2. Uncheck CAB before rebooting or powering down, recheck it after start-up.

As for Deadline vs BFQ, you will have to try for yourself.
[Samsung Galaxy Nexus] jackyhk02:
I also got this problem. So I try to use an init.d script to disable CAB on boot instead of using the franco app, like this:

#!/system/bin/sh

echo 0 > /sys/class/backlight/s6e8aa0/acl_set;

(dont forget to set permission to 755)

in the franco app the checkbox of "disable CAB" is still unticked, but when you check the file it correctly shows 0 (i.e. CAB disabled) and the screen does not become dimmed when I am viewing white websites/gmail. So I guess this works.

and the reboot problem no longer exists, even if I do not touch the screen after the screen timeout :fingers-crossed:
[Samsung Galaxy Nexus] ReMuSeR:
Im using osmod settings 1 more thing when phond vibrates it so hard i hear a wierd noise inside its like kickkk can i lower vibration i see no option on this kernel but is it possible somehow
[Samsung Galaxy Nexus] bunnahabhain:
I ran into really strange problems in the past days...

Installed Android Revolution HD from scratch and paired with Franco #382. As soon as i install apps with a greater footprint the phone freezes. No matter what govenor/scheduler. I left it stock, fixed permissions, cleared FkU's cashe and data, rebooted, diabled CAB via init.d script (as a last attempt), changed ROM to Purity, and my system continues to hang itself. That is very disappointing for me since i need a stable phone and i really like Francos Kernel :)

I am on Fancy Kernel now. It is not as fast as Franco #382, but the freezes are gone...
[Samsung Galaxy Nexus] The Gingerbread Man:
[MENTION=470754]Franco[/MENTION],

This is post of the month
[Samsung Galaxy Nexus] bunnahabhain:
I know i can't provide any logs or infos for you guys. I really like what all of you do to improve this kernel and i don't get tired to mention that.

I don't know how to help, but i know how to set up a clean system and exclude potential mistakes many others make and made by dirty flashing... so i figured i'd share that i ran into problems. The freezes that occur during installs from play store are not new, i know that as well. But as far as i am concerned, i never had such deep system freezes with earlier iterations of Francos kernel. I had to pull the battery for three times in a row today. That is really unusual. Just wanted to point that out. So don't get mad and give my post a label that it doesn't deserve.
[Samsung Galaxy Nexus] The Gingerbread Man:
Sorry, I actually quoted your post in the thread and not getting mad I was more making a joke but it clearly wasn't funny. It would be helpful if you were able to provide some logs so we could see what the issue actually is. Generally proc/last kmsg is the preferred one. I can see you have tried some trouble shooting, all I would suggest is is its a rom issue as on stock rom this runs fine and no boot looping problems here. Look back over the thread for osmosis kernel reset zip and flash it to see if that helps. Also this kernel, at least any if the recent ones are all for 4.2.2 not older android versions if you happen to be on an old build
[Samsung Galaxy Nexus] bunnahabhain:
Re-reading my post i know what u wanted to make a joke of. It seemed that i am one of countless guys that have problems that were discussed earlier while providing zero additional information. I am reading those guys as well. I follow this thread carefully and i tried to minimize mistakes on my side by changing parameters subtle. I even flashed a stock ROM and changed that to another stable one after having those issues.

I just can't imagine what causes these freezes. Seems i flashed my Gnex too often and i have bad blocks or something like that.

I'll wait for the new Purity, will flash osmosis's emergency zip prior and try it yet another time with #382 or milestone 7 ... If that won't work i'll have a serois coversation with my Gnex ;)

Thanks for understanding me Gingerbread Man - have a nice day - i'll go to ivestigate further :)
[Samsung Galaxy Nexus] DroidOnRoids:
Is undervolt broken for the Gnex? I know it is for the Nexus 7. Please forgive me but I went back to the Gnex. Thanks!
[Samsung Galaxy Nexus] The Gingerbread Man:
Not really broken but voltages are hard coded for now and can't be easily changed. This was cos too many people were being stupid with it and then complaining their **** was going wrong (much like nexus 4 right now) so Franco made it so we can't and suddenly 90% of the bull **** stopped

[MENTION=3159649]bunnahabhain[/MENTION]

This is actual post of the month as voted for by Franco on nexus 4 forum, at least you were able to provide more info than this chap and appolagies if I offended you it was just meant as some light hearted humour :)
[Samsung Galaxy Nexus] osm0sis:
You could roll back f.K versions until you find one that works too. That would be invaluable help.

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

That happened but then he gave us back UVing a few builds later. It works 100%. Only SR is hardcoded disabled. [MENTION=4374757]Edward Stanbury[/MENTION] and I even methodically UVed our GPUs and IVAs recently. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Thanks! I did not know that, I thought it was still disabled and must of missed your posts regarding that
[Samsung Galaxy Nexus] bunnahabhain:
Thanks, i'll consider that. Your osmods were very decent mate. The thing is: #382 is so so good and smooth, i'll try some other things to keep it first.

@ Gingerbread Man:

Haha thanks for the quote from N4 forums. I didn't take any offence in any way. I know you because i read a lot of your posts and couldn't determine unreasonability. I just didn't want to look like a fool and annoy people that are working hard to improve the kernel and helping users. So i tried to clear things up a bit :good:

Now back to work, i don't want to take such a big part in the thread :p
[Samsung Galaxy Nexus] osm0sis:
That's because r382 is the latest osmod. ;)
[Samsung Galaxy Nexus] bunnahabhain:
:o

okay that is why it's so smooth hehe. I just thought franco added 2 interactive patches and merged up to linux 3.0.82. But my memory doesn't seem to be the best these days :cyclops:

Thanks for the heads up!
[Samsung Galaxy Nexus] osm0sis:
Yeah CORE and IVA are super tricky to UV because there's no way to isolate the frequencies. I actually downgraded to 4.1.2 so I could run the last f.K build that was 384MHz max GPU, so that I could get that middle number properly done. The lowest will outright crash, or make your screen red/green after awhile if you're borderline, the middle and max you can crash eventually but well before you get that low there's a frame rate drop in Nenamark2 when you've gone too far.

Similarly I have no obvious effect from changing any of the IVA voltages except for the lowest frequency. For that when you've gone too far the audio in Nenamark2 and any played video will sound like it's breaking your speakers. ;) And for the others I just based them on what SR calibrated them to in AK kernel. Probably should have grabbed that from 4.1.2 as well, but I hadn't thought of that at the time. SR ended up with 860 and 974 for the bottom two, and then I was able to push the lowest down to 825, so I lowered the others to 925, 1025 and 1125 as well.

If anyone knows a way to stress test IVA better let me know, since I can also lower the upper three to like 275mV and it doesn't seem to make any difference. So either it's not budging from the lowest IVA freq, even with HD video, or UVing may actually not work for those upper three IVA frequencies.

---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------

Nope. Everything I had in r378-osmod made it in too. :D

Only thing that isn't one hundred percent working in r382 (and that's my derp) is the lmk whitelist script. Weirdest part is that the exact same script works flawlessly on the N7. Got a better revision of it that I'm testing out now. :)