yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Samhain77:
I'm testing cfq too..... but I have no google play updates till 2 days so I can't confirm this... :(
[Samsung Galaxy Nexus] kevdliu:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Uninstall update for one of the system apps and update it
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

When we say cfq is next on the list we mean the extensive testing, tweaking, countless revisions and discussions that brought the deadline numbers you love, the better row and many more to follow

Franco r365

JBSourcery 4.5.5

---------- Post added at 10:19 AM ---------- Previous post was at 10:11 AM ----------

And we'd love to take the issues with Google play away. Some coding between Google's and Franco's and other kernels too is causing it. "Fixing it" may entail breaking franco.Kernel. we won't do that so it's gotta be fixed from the other side. Even so, some improvements have been made.

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Samhain77:
I've thought to do this... but I couldn't find where to remove updates...... Now I've found it (on the applications menu ;) )

Removed Google+ update and then reupdated from play store and no freeze at all!! So I think I can confirm that CFQ is good to avoid play store updates freeze..... still testing though
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I never had freezes while updating on cfq, deadline or row. What kind of Roms are the freezy people use? I'm on stock.
[Samsung Galaxy Nexus] slvrarrow:
Please dont ruin CFQ, for me its by far the most snappy and smoothest. Somethings happened to BFQ recently and deadline performs similarly to BFQ on CM10.1 - I was previously a big BFQ user.
[Samsung Galaxy Nexus] whitedragonz83:
Stock 4.2.2 ROM. Only CFQ felt like I could do something during an update/install from the Play store. Deadline/ROW (though I haven't tested past Franco defaults) both result in severe lag and required a battery pull once or ended up with a warm reset. Maybe just a device to device issue? If it matters, I have ~8 of 16 GB of space used.
[Samsung Galaxy Nexus] osm0sis:
Kind of a **** thing to say?

We would only be making it more snappy and smooth for more people. Because right now it's not. Nobody has touched bfq.

I'm on stock as well, and it definitely does choke a bit during installs. Best seen trying to scroll through My Apps > Installed Apps. Locks up the nav buttons briefly and everything. Thing is, it's happening on every kernel, so it's not what we're doing with the scheduler tunables on f.K that's causing it, in fact in our testing our latest ones help to at least mitigate the problem somewhat. For the record, I get the momentary lockups with cfq and noop as well, so neither are made of magic. ;)

If you truly can't reproduce the issue, out of curiosity, what is your read_ahead_kb?
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

The idea is to improve the overall user experience by optimising the values for speed and smoothness. If your fan of CFQ your input would be welcome if you played with some of the tunable values and posted here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] darrendm:
Constant data/radio drops with 13.1

Didn't happen on kernels prior to this and my ROM has not changed so it cannot be a ROM issue. (Milestone 2)

Requires me to restart my phone every few hours to get my signal back
[Samsung Galaxy Nexus] oli20021978:
Hi, just a short question. What for program do you use for current battery voltage? Maybe with alarm? Current widget doesn't get data on nexus.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jhericurls:
Not sure if this UV related but last night I managed to crash my phone after playing Modern Combat 3 for 10 minutes. I quickly up the voltage and run MC3 again, played for another 15 minutes without any problems.

When I exited the game it just froze on the reboot. It froze again after a few minutes just navigating the menu. On reboot the Google splash screen was all messed up like when you have a borked graphics card. I reset the UV to default but it still crashed a number of times.

So I had to reflash #12 and the problem seem to be solved. Then I reflash #13.1 and working ok now.
[Samsung Galaxy Nexus] slydog43:
I'm seeing the same thing, not sure if its the kernel or custom rom
[Samsung Galaxy Nexus] Simer03:
Nexus phones are made based off the software...the hardware fits the software! Its like having a dual core phone but having no software that uses it correctly (ie galaxy s2 with gingerbread) ICS is optimized for dual core!

sent from my Nexus Prime
[Samsung Galaxy Nexus] Roman-Kumori:
Sorry, I've mistaken.

Credits for abscence of lag goes to nova launcher that doesn't scroll live wallpaper. If it is scrolled, LAGs are here and with me. Sadly.
[Samsung Galaxy Nexus] ctbear:
More like a radio issue. Have you tried another radio?
[Samsung Galaxy Nexus] darrendm:
Doubt it is a radio issue. Been on XXKL1 for weeks and this problem only started with 13.1

ROM hasn't changed either (Milestone 2) so it cannot be that either unless it's slowly deteriorating on my device :p

Must be a (this) kernel issue (unless I am completely mistaken).

EDIT: WIFI also doesn't work. Sometimes it connects, sometimes it doesn't - however; either way data is not working and the bars go grey and nothing sends on WhatsApp and browsing stops.
[Samsung Galaxy Nexus] Nebucatnetzer:
I don't know what you guys with the bad battery life are doing but mine is phenomenal.

Build: 13.1

Rom: AOKP 19

55% left and 2h of screen on time.

Auto brightness

Wifi for ca. 95% of the time.

No power saving tool, app whatsoever except undervolting and frequency locked at 350Mhz while the screen is off.

https://picasaweb.google.com/107386...authkey=Gv1sRgCIDh-fv-ubushAE&feat=directlink
[Samsung Galaxy Nexus] nemolivier:
@franciscofranco

I can’t install your app from market. It say that none of my device can use this app :(

I have a galaxy nexus with Manhattan ROM.

Any idear ?
[Samsung Galaxy Nexus] aron7awol:
Right, but you probably also saw that nobody who said the UV battery gain is minimal has shared any data to back that up. I did some math using data gathered from real-world testing and came to the conclusion that the battery savings are likely huge. Which do you believe is more likely true? I'll go with real-world data over somebody's baseless opinion every day of the week.

Anyway, I know ro_explorer plans on using his multimeter setup to answer this question directly by testing power consumption at different voltages. Stay tuned for the final answer to this question...

Edit: Go Pats!
[Samsung Galaxy Nexus] rommel500:
I'm running 13.1 with the winner's CM9 Kang from 1/08 and I never see any radio drops and I am UV'd by ~ 75mv on all speeds.
[Samsung Galaxy Nexus] jan-willem3:
I also have lower singal strength and sometimes a data drop didnt happen on 12.

I think it has something todo with this:

https://bitbucket.org/franciscofranco/android-tuna-omap/changeset/6385aa3cfc50

Also because I found this:

http://stackoverflow.com/questions/7291940/what-may-cause-a-tcp-ip-reset-rst-flag-to-not-be-sent
[Samsung Galaxy Nexus] nic85:
Thanks for settings, work Also for me

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the links.

Try to use market enabler.
[Samsung Galaxy Nexus] asmodea:
I m a noob so I have few questions :

1. If I want to update both the Kernel and Rom of my phone, after I updated my kernel in ClockworkMod I must reboot and after that entering again in ClockworkMod i update the ROM ? or I can update directly the ROM after the Kernel update without rebooting ?

2 If I just want to update the Kernel and not the ROM too, I update the kernel and that s it ? I reboot and everything ok ? I can continue whit my old ROM and settings ?

Thanks.
[Samsung Galaxy Nexus] nikosrs4:
always first the rom and last the kernel.

you can flash only the kernel with the existing rom but only if your rom is 4.0.3!
[Samsung Galaxy Nexus] Optimusg2x:
I just bought the kernel updater app. What is the color setting is everyone using?
[Samsung Galaxy Nexus] aras1:
i got extreme battery drain with #12,#13 with #11 it was brilliant but then i updated to the newer once's at got strong battery drain
[Samsung Galaxy Nexus] c00king.c0w:
so do i, see http://xdaforums.com/showthread.php?t=1459181 for more info
[Samsung Galaxy Nexus] joelmonty:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That's a good idea will use that thanks.

Yeah , my headphones go through my shirt so the cord isn't long enough to reach my voice.
[Samsung Galaxy Nexus] Puzzlegirl:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

MoDaCo ROM has had freezes with Play Store updates and also at the point Titanium Backup starts its scheduled backup. Since I changed the IO Scheduler to noop, there haven’t been any freezes whatsoever :)
[Samsung Galaxy Nexus] slvrarrow:
Wasn't trying to be a ****! With 366 on BFQ/Deadline have had trouble switching between apps/bringing up the recent apps thing. Don't know if its anything to do with cm10.1 but CFQ doesn't have that problem at all for me. The others seem to "stick" when doing something intensive like switching apps or going back home.
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I guess I'm lucky. I don't get the play store freezes anymore. I think I only had one or two a while back, but I think that was during all of those supersu updates. I haven't been able to reproduce this freeze or lag on any kernel.
[Samsung Galaxy Nexus] osm0sis:
Yeah that's the other thing. SuperSU was causing some issues with Play Store awhile back, so hopefully everyone has already made sure they're on the latest version.

Edit: Actually SuperSU wasn't causing the issues. Google has their own su binary (which apparently doesn't follow any of the command/api structure of the other su binaries, and very little is known about it), and if I recall correctly, Play Store was triggering a call to su likely as part of some debugging that of course didn't make any sense and resulted in a freeze/reboot. If the device wasn't rooted (as intended by Google), those calls would be ignored; Chainfire just made SuperSU ignore those calls too to workaround Google's derp.
[Samsung Galaxy Nexus] cucisan:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

or switched to koush's opensource "clockworkmod superuser" ;)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Yeah, no thanks. It's got plenty of bugs right now too. ;)

SuperSU works fine now. Chainfire fixes it very promptly.
[Samsung Galaxy Nexus] J-Hop2o6:
LOL

Overall, how do/did you feel about CFQ's performance? It's my first time really using it and its been good so far. Any tweaks to it soon?
[Samsung Galaxy Nexus] osm0sis:
It feels okay with the JDQ39 defaults, though not as good as our tweaked row or deadline (see malaroth's sig for the latest). No tweaks yet, we've got some documentation to read through before we kick anything off there. The defaults are in the iosettings script as placeholders for now. :)
[Samsung Galaxy Nexus] Edward Stanbury:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Getting amazing battery life ! :)
[Samsung Galaxy Nexus] lightingcloud:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I just experienced a freeze while updating OfficeSuite. It solved by itself, instead of pulling battery I just left the phone by itself for 60 second or less and it started working normally. I'll try doing this from now on and see if it happens again.
[Samsung Galaxy Nexus] Zadeis:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

When it has come to freezes when installing apps office suite has consistently been the one app that has caused a freeze for me. Luckily it doesn't update to often.
[Samsung Galaxy Nexus] osm0sis:
Those office suites are like 20mb+ too, so it would stand to reason they'd be a bit more prone and severe. Large games with big downloads I'd expect as well.

Both of you: what is your read_ahead_kb set to? You could try different values (128, 256, 512, 1024, 2048):

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;

Also, please try going to another scheduler and then to deadline in f.Ku (resets to defaults), then setting front_merges 1, and also from Terminal Emulator:

echo 0 > /sys/block/mmcblk0/queue/nomerges;

if that doesn't help, then maybe

echo 1 > /sys/block/mmcblk0/queue/nomerges;

or

echo 0 > /sys/block/mmcblk0/queue/rq_affinity;

After changing the above, uninstall OfficeSuite and reinstall it to see if the freeze has improved. Also try any combination of the above and see if you can come up with anything that helps.
[Samsung Galaxy Nexus] Zadeis:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I will try my best to do this tonight before I go to bed. I can't do it right this moment since I have to get a little work done but I will try what you mentioned here.
[Samsung Galaxy Nexus] J-Hop2o6:
I tried the row tweaks, but still had the serious slow down when updating apps. CFQ handled a big game install pretty well and quickly, unlike row and others.
[Samsung Galaxy Nexus] Samhain77:
Are you telling me that settings script I put in my init.d it's just setting the default settings for cfq?????:laugh::eek:
[Samsung Galaxy Nexus] osm0sis:
tweaked deadline, tweaked row, default cfq until we start adjusting things since adjusting in the app and then editing the script to try them for a few days is generally how we operate.
[Samsung Galaxy Nexus] lightingcloud:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'll try tomorrow, by now I'm on tweaked deadline and 512 read_ahead

Considering it was the third app update in a row I can consider myself lucky.

But I think I can "say" a lot revealing that when I wake up I usually turn my phone on and leave it alone for about 10 mins. When I'm back everything is fine and updated.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

:laugh: I was just going to edit out the cfq defaults from the script so nobody could say our "tweaks" were messing things up. They are default. You're already running them.

On a side note, with the drastic improvement overall users are experiencing with the tweaked deadline and row values perhaps those of you with problems might check other apps you have installed. And if you seriously don't like the tweaked values we come up with stick to default. This IS what "fixing the problem" is all about. Find a solution

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] kevinzone:
Gpu speed?

What clock is the gpu, i'm at 1420 mhz and in beach buggy blitz , i kinda lag. So i just wanna know what clock this is?
[Samsung Galaxy Nexus] reysonance:
http://xdaforums.com/showpost.php?p=38661568&postcount=39779
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You don't need to overclock to play games,the result will be overheating and thermal throttle activation. Instead,try playing at 1036 MHz to avoid most overhating and still have great performance

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] arhung:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Can I use the Franco kernel updater and the trickster mod at the same time?
[Samsung Galaxy Nexus] spupuz:
yes but not so useful :)
[Samsung Galaxy Nexus] shreddintyres:
you can use them but you will run into added bugs, since your phone doesnt distinguish or give priority to one over the other, unless you have every setting the same in both (which is a pain) id stick to one or the other. I use f.KU over trickster to help support development and its the only application gauranteed to work properly with Franco kernel, trickster may work on somethings but not all who knows.

- Cheers
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes you can... make sure to set the same values for CPU and governor, color settings, etc. in both apps. As to the previous post as to being "not so useful", THAT was not so useful. Trickster has other functions which Franco currently does not or will never have. I use trickster if I'm setting hostname i.e. android id, to check my CPU MHz up time and deep sleep. There's more to trickster than just frequencies and voltage. But if you use 2 different apps that have the same function, you should set the same values to each

Edited for correct quote

Franco r366

JBSourcery 4.5.5
[Samsung Galaxy Nexus] spupuz:
i have bought both actually i removed franco cause i'm using AK kernel, anyway if he set the same setting can be good but in fact Trickster Mod is way more complete.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

My point to you is that a more complete explanation would be helpful, especially seeing that you aren't running the Franco kernel nor using the app. WE are still running and testing Franco.kernel.

Franco r366

JBSourcery 4.5.5
[Samsung Galaxy Nexus] spupuz:
it's just because franco actually has bought if i'm not wrong a nexus 4 so update on his galaxy nexus kernel are less frequent than before but in fact it's a very good kernel, i also like to try new things and in fact i also like so much anarkia AK kernel and he also is italian like me.. nothin more else :)
[Samsung Galaxy Nexus] Zadeis:
OK finally got around to trying what you suggested and here are my experiences. A no merges settings of 1 and a rq_affinity setting of 1 seems to yield more responsiveness while using my phone while office suite is installing. I tried each setting of 1 and 0 in each combination and read ahead was set to 512 the entire time I was testing. I had no full on freezes this time around which is good so maybe setting read ahead helped though I am not sure. I tested responsiveness while office suite was installing by typing out a text message to see how it responded to each key press and the results I stated earlier seemed to have yielded the best typing experience.

If you want me to test things differently or if I didn't do something correctly just say so and I can try again.
[Samsung Galaxy Nexus] osm0sis:
Scheduler deadline like I suggested? Try again with read ahead at the other values I suggested to see which works best. :)
[Samsung Galaxy Nexus] Zadeis:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt 4.1

Correct. I switched to another scheduler and switched back so it had the defaults and then changed the one tuneable you said to. I will try other read aheads tonight though I will probably use the settings I had found earlier in combination with the different read ahead settings.
[Samsung Galaxy Nexus] osm0sis:
Perfect. Let us know how it goes. :)

---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------

Also, please try rebooting to get the f.K deadline tweaks, then changing only the read buffer to see if it still works better.
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Malaroth and osm0sis, for some reason, the all in one script doesn't work for me (at least the tweaked row settings). When I separate the row tweaks into its own script it works fine. I did change permissions. Any thoughts?
[Samsung Galaxy Nexus] Zadeis:
Would you like me to use the latest init.d tweaks for deadline? Then change the read ahead to see what happens? Or no?

Edit as of 6:42: well I'm going to go ahead and use the latest deadline tuneables. And try what you suggested.
[Samsung Galaxy Nexus] Zadeis:
Upon my testing 128 and 256 were not very pleasant to use and 1024 and 2048 were even worse. 512 definitely seems to be the preferred spot. This was with the latest deadline tuneables and both no_merges and rq_affinity set to 1. I did not use the current settings of 2 in malroths scripts.

All through this testing I did not experience a complete freeze which is frustrating to say the least as I don't think we really got anywhere because of it :/
[Samsung Galaxy Nexus] osm0sis:
Make sure you're using the latest script.
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I was using one I downloaded today. I had a similar issue with an earlier version. I ended up taking the first portion out and creating a "920" settings for those initial commands, then a separate "950" row settings script. Seems to work, but I am hoping there's something obvious I'm doing wrong so the all in one would work for me. Thank you!
[Samsung Galaxy Nexus] arhung:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have the same question but I'm gonna lost, may I ask where are the file locations? Thx!
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I believe it's in malaroths signature. If your on your phone you probably won't see it, so use a computer.
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

They are in malaroth signature. Press menu > web view to see the signature
[Samsung Galaxy Nexus] Khrushy:
First check - are you setting the file permissions correctly - should be 755 (rwx r-x r-x)

Secondly - the All-in-one script just applies tuneables to ALL the schedulers (well, Deadline, ROW and CFQ for now), it never actually *sets* your scheduler, and just relies on your correct scheduler being set by whatever app you control your kernel settings with.

One thing I found is that if you have multiple apps that can set various "on boot" attributes, then maybe one of them is always resetting your scheduler to defaults upon each boot, and over-writing the tuneables set by your init.d script.

For me, it was "Performance Control" in AOKP, and it was constantly resetting my scheduler back to deadline - for you it might be something else. My solution was to just freeze all those "set on boot" apps and let the init.d script do everything.

As a suggestion, if you want to set your scheduler as part of your init.d you can include the line:

echo "row" > /sys/block/mmcblk0/queue/scheduler

in the init.d (obviously, change "row" to "deadline" or "cfq" if that's what you want).

Cheers
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Been doing my own playing using Rom Toolboxes SD benchmark and noticed all schedulers (except for CFQ and Noop) perform poorly on writes and awesome on reads. I've set the test up for 150mb and ran it for the 128, 512, 1024, 2048 presets. On BFQ, deadline, and ROW i literally had on average 0.74mbs on writes for all and between 28mbs-32mbs for all depending on SD buffer size. Now for CFQ and Noop i noticed that on 512 and 1024 I've gotten 1.74mbs reliably on both for writes and still around the 28-32mbs range for reads. I've stuck with 1024 CFQ because it averaged higher on every test. Now not only have I noticed differences in play store updates (less lag) but one app I've been using to test is FxGuru. Using BFQ, deadline, or ROW makes that app process video at a snails rate. So slow that android usually asks if I want to close the app since its not responding to process video (which it eventually does). On my CFQ set-up i can get the video processed alot quicker and never get the annoying "this app is not responding" message. Hope some of this helps.

Laziness is nothing more than the habit of resting before one gets tired!