yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] BigBake88:
I get the same jittery feeling as you do on 3100. On running 192 min as well @700mv. I'll change to bfq and bump it to 384 min and see what happens. :highfive:
[Samsung Galaxy Nexus] crimmylol:
Franco can you fix flac shuttering on the latest nightly? ROM CNA.
[Samsung Galaxy Nexus] franciscofranco:
230Mhz wont undervolt as much as 192Mhz and I really doubt 42Mhz will help as much as you think. Its all a trade-off: more battery savings wont turn the device into a buttery experience. The defaults 1228-384 are enough to provide that smoothness, but I really cant do any miracles if the cpu frequency is lower. A big problem in the GN is the memory bandwidth, it bottlenecks everything. Increasing memory clocks wont help much though.
[Samsung Galaxy Nexus] slvrarrow:
How come? Have you tried upping the memory clock Franco?
[Samsung Galaxy Nexus] dracon6ai:
Liquids RC5

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] ajm786:
To follow up on this as well as my previous post in this thread: downgrading to 290 fixed the issue.
[Samsung Galaxy Nexus] drose6102:
Glad to see others are experiencing the same lag speed bumps. They were driving me crazy, I knew it was kernel related because I haven't flashed a rom on downloaded any new apps.

Yes I did set the 192 min step awhile ago but didn't think anything of it. Switch to back to stock 384 and everything looks to be back to normal. Thanks guys.

And as always thank you Franco.
[Samsung Galaxy Nexus] franciscofranco:
I'll see what I can do.
[Samsung Galaxy Nexus] RoscoeDpG:
such a good thing bad thing with latest kernels.....they run so good im happy but run so good that slows down updates lol the crack flasher starts to kick in
[Samsung Galaxy Nexus] franciscofranco:
True that. A new nightly should be ready sooner than I wanted though, some small adjustments and fixes are needed.
[Samsung Galaxy Nexus] osm0sis:
Yeah, I know it won't undervolt as much, though actually when I downgraded to r290 to check out the jittery scrolling in the browser I forgot and left my init.d UVing enabled, so now we know 230MHz can handle 725mV fairly well, though I'd up it to 745mV to be safer. :p

Also I realize the 38MHz difference between 192 and 230 shouldn't make much of a difference, but I think it really does with this weird little browser scrolling business. I'll probably run 384 min from now to still have things feeling smooth where I would have run 230 before and had it feel roughly the same.
[Samsung Galaxy Nexus] RoscoeDpG:
nice, u know we are ready lol
[Samsung Galaxy Nexus] sk8oldschool74:
Ready for the next milestone... ;):D:D:D:D
[Samsung Galaxy Nexus] Controvrsy046:
Franco changed the default from BFQ v5 to Deadline for the scheduler. Anyone have any recommendations for the scheduler giving people the best performance on r295?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Well first of all, do you think Franco would pick a scheduler with ****ty performance as the default? No. deadline works great now.

Search the thread for 'scheduler' and you'll find a few opinions. I think they're both excellent choices now, with virtually no difference, but for the moment my opinion is that bfq is just a hair smoother for in-browser scrolling.
[Samsung Galaxy Nexus] Tarun95:
While scrolling page 3100 on 295 it was lagging a bit. Then I went back to 290 and tried the same and it doesn't lag.
[Samsung Galaxy Nexus] osm0sis:
Right but did you make sure you had the same settings in both builds? r295 has different governor tunables by default, a different lowest min you could set and a different default scheduler. What did you use?
[Samsung Galaxy Nexus] Tarun95:
I tried franco 295 settings and Google default settings. Tried both schedulers as well. But on 290 I don't get those speedbumps. 384 was minimum.
[Samsung Galaxy Nexus] osm0sis:
Okay so you're running 384MHz as min across the board? That was sa good idea, removes the variable.

You tried the r295 settings (6/7/6/3+deadline) on r290 and still didn't get those speedbumps?

Conversely, have you tried the r290 settings (10/5/6/2+bfq) on r295?
[Samsung Galaxy Nexus] Tarun95:
Wait I'll try that now on 290. But still Google default gives speed bumps on 295 and not on 290
[Samsung Galaxy Nexus] osm0sis:
Hmm alright, well that might help narrow it down for Franco to look into then, considering there were only 11 commits in between. Who knows, might be same thing ****ing with FLAC playback. :good:
[Samsung Galaxy Nexus] Tarun95:
And yeah those settings are not causing lags on 290
[Samsung Galaxy Nexus] BigBake88:
Good, then I'm not crazy lol. 290 scrolling did feel smoother, although I do have to say I bumped up from deadline 1036/192 to bfq 1305/384 and everything does feel much better.
[Samsung Galaxy Nexus] Tarun95:
OK one more report. I was playing subway surfer on 290 with 6/7/6/3 it gave me micro lags while collecting coins but with 10/5/6/2 no lags. Something has to do with the hispeed load. May be 70 is too high. And above_ hispd_delay if lower should give better performance. I don't think timer rate could affect much. Think 50 is the best hispd load.
[Samsung Galaxy Nexus] osm0sis:
50 is the best depending on what the others are. ;)

Sounds like you've got a good method to figure things out though.. Reproduce your r290 lag with 6/7/6/3 and then mess with one isolated tunable at a time (ie: Try 10/7/6/3, then 6/5/6/3, then 6/7/6/2). See if you can pinpoint which exact one helps. :D:good:
[Samsung Galaxy Nexus] Tarun95:
Hispd load is the one causing those lags. 50 I don't get any lag. Even timer rate I think when set at 30000 causes a little in fact very little lag. 20000 does make it little better but can't tell for sure. Above_hispd didn't make any difference. 10 and 6 gave me same results.
[Samsung Galaxy Nexus] osm0sis:
Interesting results. Especially since all the go_hispeed_load dictates is when it jumps to hispeed_freq. You'd think, since you're running a game, that it would be at or above hispeed_freq (729MHz) already so it shouldn't make a difference. above_hispeed_delay is the one that tells it to wait before going to frequencies above hispeed_freq so, lower should feel better. Very interesting.

Since you like timer_rate at 20k, try 60k/60/50k/20k please. And if that doesn't work I guess lower go_hispeed_load from 60 to 55 and see if that helps. Basically by lowering above_hispeed_delay we wanted to make it stay lower a little longer to keep our battery use balanced, hence >50. You could also try lowering min_sample_time to 40000 or raising it to 80000 and see if that makes any noticable difference. :):highfive:

Thanks for the help. You and this game sound like a good stress test for the tunables. ;)
[Samsung Galaxy Nexus] Tarun95:
OK u are right. The above_hispd when changed to 60k made things smoother. 100k it was skipping few frames. Load at 60k caused few frames to get skipped on 55 and 50 no problems at all.
[Samsung Galaxy Nexus] osm0sis:
Hmm. How about the min_sample_time ones I also suggested? Any difference there? Try above_hispeed_delay at 80k see if it still skips; if we're going to have load way back down at 55 then I think we'll want to have the delay a bit higher again to compensate. Again, thanks a lot man, this is all really great stuff. :D
[Samsung Galaxy Nexus] Tarun95:
Yup 80k made things a little smoother. Very few frames were skipped.
[Samsung Galaxy Nexus] osm0sis:
Whoa now, be specific. ;) You mean between 40k, 60k and 80k for min_sample_time? Or do you mean the 80k I suggested for above_hispeed_delay just now?
[Samsung Galaxy Nexus] Tarun95:
Min_sample = 80k. Hispd delay is the one which made a huge difference. I was wrong at first. And the jetpack part in the game lagged a bit with 40k as timer rate and 20k it didn't lag. Might be a problem with game also.
[Samsung Galaxy Nexus] osm0sis:
Yeah we wouldn't want timer_rate over 30k really. Alright so from all that back and forth and awesome feedback from you we've got 80k/55/80k/20k, 60k/55/80k/20k, or 80k/55/60k/20k. :good: Which of those 3 works best for you? :D:
[Samsung Galaxy Nexus] Tarun95:
OK here goes. Above_hispd 60k best. Hispd load 55 at times causes micro lags whereas 50 doesn't. I don't know how an increase of 5 could make a difference but yeah overall 50 is better. OK again I tried min_sample 60k seems to be better because at times it may require to go to 1036 and 1228 but the sample time makes it wait longer at 729 which caused little lag. Timer rate 20k. So it is 60k/50 or 55/ 60k/20. So only above_hispd_delay made a big difference.
[Samsung Galaxy Nexus] despard:
6/6/6/3 is good for me. 1420/192 with BFQ and Westwood.
[Samsung Galaxy Nexus] Tarun95:
I think the best for overall battery and performance will be 60k/55/60k/30k
[Samsung Galaxy Nexus] osm0sis:
Really. So even though you just said you liked min_sample_time at 80k you find it better back at 60k? And you're back up to 30k for your timer_rate, how come? Haha well this was fun. Ended up roughly at defaults but with a quicker bump above hispeed_freq. So we came to 60k/50/60k/20k, but that might be hard on battery, so I see you've come to the same conclusion that 55 would be better if we're going to lower above_hispeed_delay to 60k. I suppose we can try them out over a few days and see if that's the case. Cool. :)
[Samsung Galaxy Nexus] Tarun95:
Cool. U also try these 60k/55/60k/30k

Min_sample is 60k so 30k timer rate won't make a difference. Because then it'll check twice in the time it spends on one frequency than checking thrice. That should help battery :) the difference was very little between each change so it took time before I could figure out which is best. :)
[Samsung Galaxy Nexus] osm0sis:
I wouldn't overthink the multiples thing too much, just go with whatever feels the best. :)

I was hoping these findings might help us kill the jitteriness/speedbumps in browser scrolling. Sadly, no such luck, but I'm seeing if a variant of them might help.
[Samsung Galaxy Nexus] Tarun95:
By browser u mean chrome or stock ?
[Samsung Galaxy Nexus] osm0sis:
Stock here, I think that's the one everyone is seeing it in. Chrome I know has scroll lag issues people have been complaining about for some time. What I'm talking about is something people seem to be tracing to the nightlies after r290.
[Samsung Galaxy Nexus] Tarun95:
On stock I have no scrolling problems whatsoever.

Edit: never tried the stock browser with 295 so no idea. But 290 no problem.
[Samsung Galaxy Nexus] osm0sis:
Well it's not fast scrolling that's the problem, it seems to be when the transition from the fast fling-scroll to slow-scroll takes place near an image you get a "speedbump"/microlag. Check back in the last 7 pages or so, a few of us have been discussing it. Pg 3100 of this thread seems particularly good at exhibiting it when viewed in the stock browser, especially when that transition is over tetrakinitis' avatar pic.

P.S. tetrakinitis, if you're reading this, it's a good pic bro. :laugh::good: Sorry. Just needed a place where I could send people to reproduce the issue. :cyclops:
[Samsung Galaxy Nexus] tgyberg:
r295 the stock browser rocks for me, no lag. Stock gov control settings, 1228 max
[Samsung Galaxy Nexus] Tarun95:
No man no lag on 290
[Samsung Galaxy Nexus] osm0sis:
Nobody said there was lag on r290. Everyone's saying the lag goes away when they go BACK to r290.

5 people reported this over the last 2 days.

Either way, I can't seem to find any combination of tunables that fully fix it, only help it to a point or make it worse, so there must be something else. Oh well, that's enough of that for tonight. I'm off to bed. Have fun! ;)
[Samsung Galaxy Nexus] shawnaye:
Thought i'd chip in to all the development, so far having no problems whatsoever running r295.

Min 192 (uv'ed to 780 cause my silicon sucks) Max 1036. Max screen off 384, everything else as franco defaults

Facing no lags whatsoever. So once again, i'm completely stoned whenever you guys mention about lags.
[Samsung Galaxy Nexus] schizophrenia:
for some reasons, with the updated v7.1.4, the app randomly asks for root permissions while I was using other apps. the app used to ask for permission only when I adjust some kernel settings.

I am on CNA3.8.0
[Samsung Galaxy Nexus] nuwan32:
Franco said he realized this. It's a bug, will probably be fixed in the next release. Bear with it for now.

And I've been trying 6/5/6/2 been best performance so far and don't really see a difference in battery no matter how much I change these
[Samsung Galaxy Nexus] schizophrenia:
Thanks. Sorry I didn't have time to read the last pages.
[Samsung Galaxy Nexus] SahilC:
Anyone using HoloWeb browser?
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm either doing it wrong or can't reproduce this using Chrome with 192-1228 interactive 295 governor control how it came but using BFQ and Westwood TCP.

295 is amazing for me, great performance, fantastic battery life and working very well indeed with minco v5

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gaich:
No need to reply all this permissions requests. Just set right the SU.app and you`ll never see these requests anymore.
[Samsung Galaxy Nexus] tetrakinitis:
My pleasure bro! ;)

Sent from my SmoothCriminal
[Samsung Galaxy Nexus] dominatore22:
Hey franco, here i'm using xenonhd rom and i flashed your r295 kernel version. I've set min freq to 192 mhz and max 1228 all with stock voltages. I' ve set too screen of max freq to 384 mhz. I tested it for 4 battery cycles and i noticed that when the phone is in deep sleep the battery drain it's not bad. I' ve maked the cpu sleeping for all the night. From 23:00 to 10:00 am and it used 7% of battery. But when i waked the phone and started using it turning on wifi and do some web browsing the battery it's draining so fast. Like 1% every 60 seconds :eek: ?? What's wrong with my settings? :confused:

Here cpu spy log.
[Samsung Galaxy Nexus] Shadow-Nexus:
I'm guessing that happens to everyone

Its either great battery or great performance
[Samsung Galaxy Nexus] dominatore22:
After i was on milestone 6 and battery drain was better :/ i think that i'm going to flash it back
[Samsung Galaxy Nexus] aimcr7:
Good battery life today (first cycle)

Moderate use, UV -150, 192-1228, interactive 6/75/6/3

Kernel: r295

ROM: darkPA 2.52

Sync always on, data always on.
[Samsung Galaxy Nexus] gm007:
Lower your screen brightness.
[Samsung Galaxy Nexus] billykxda:
For me, 295 runs great, but battery life is just so-so. Other kernels, like Faux for instance, are able to put my GNex into deep sleep quicker and longer during idle times. When actively using the phone, battery life is just slightly worse with Franco, but performance is better.
[Samsung Galaxy Nexus] tetrakinitis:
After all this conversation the last days about the tunables of interactive, i want to share my experience with you. From yesterday night i'm using the "high octane" settings 3/5/9/3 with min 729/max 1228, hispeed_freq 1036, input_boost_freq 1036, i/o scheduler bfq, screen off 729 mhz. I'm try almost all these settings you post but this is the best combo for me on r295! No speedbumps, no microlags, nowhere especially in browser around my avatar pic like osmosis said! :D.The scrolling around homescreens and drawer is perfect. But the best of all that i have to suggest to all of you is to try these settings with milestone 6, you'll get the smoothest and fastest experience on your Gnex until now! :cool: (I want to believe!). Don't ask me about battery, i dont now yet! At last i want to thank all you guys for contribute to this, especially osmosis and yellowdie. And of course our kernel wizard Franco :thumbup:

Sent from my SmoothCriminal
[Samsung Galaxy Nexus] dominatore22:
It's auto :/

---------- Post added at 01:59 PM ---------- Previous post was at 01:56 PM ----------

What do you mean with 3/5/9/3? :/ where are this settings?
[Samsung Galaxy Nexus] tetrakinitis:
Check this post http://xdaforums.com/showthread.php?p=33161912 and try it! ;)

Sent from my SmoothCriminal
[Samsung Galaxy Nexus] JBNex:
The 6/2/4/5 things don't work on dyninteractive
[Samsung Galaxy Nexus] billykxda:
If there are any tweaks I can do in Franco's app to improve battery on 295 a bit, I'd appreciate hearing about 'em.

Thanks!
[Samsung Galaxy Nexus] BigBake88:
That's because dynamic interactive dynamically changes tunables based on usage and load. Using interactive and they will stick :good:
[Samsung Galaxy Nexus] Savant:
I smell bacon coming from Franco soon.
[Samsung Galaxy Nexus] shawnaye:
I wonder if it's possible to speed up Boot-up times.

Would that be kernel related or ROM related?
[Samsung Galaxy Nexus] timbck2:
I used to always run at 384/1305, but now I've lowered to 192/1228 and I can't tell the difference!
[Samsung Galaxy Nexus] Bl4ck3urn:
The "BootService" from your app always runs in the background since version 7.1.4

Is it normal?
[Samsung Galaxy Nexus] BigBake88:
Yes, he acknowledged it and will release a fix soon.
[Samsung Galaxy Nexus] franciscofranco:
No its not. I just pushed a fix for that.
[Samsung Galaxy Nexus] Dany16v:
I have random reboot problem, how can I see what is the source of my problem? (a lot of page ago I read the solution but now I can't find it)

Thx
[Samsung Galaxy Nexus] Hero_Guy:
For those using r295 and getting insane battery life, are you guys using any power modes? I tried it out and while the speed was amazing, battery life suffered and had to go back to m6 and I did check out that guide that was posted a bit back.
[Samsung Galaxy Nexus] trueblueram:
peculiar problem

i am on siyah(Galaxy s3,Paranoid android) now. i dont seem to be able to flash this kernel. it flashes all right in recovery, says its installed, enjoy n all; when i boot up it still shows siyah. am i doing this right?
[Samsung Galaxy Nexus] franciscofranco:
What? I dont even...
[Samsung Galaxy Nexus] nuwan32:
This kernel is for galaxy nexus go find the one in s3 development

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

Yea exactly lol
[Samsung Galaxy Nexus] osm0sis:
Are you trying to flash a GNex kernel on your S3? You're lucky franco's flashable zip is GN specific or you would have ****ed your device.

Edit: Haha :laugh: Franco and nuwan32 beat me to it. ;)
[Samsung Galaxy Nexus] trueblueram:
uh oh :) Guess i was in my own reality distortion field, having seen posts on how good this was :):cowboy:
[Samsung Galaxy Nexus] Fenvarien:
The fix works great, thanks for the update! :)

GNex with franco.Kernel / MiNCO ROM v5
[Samsung Galaxy Nexus] shawnaye:
what in the world..
[Samsung Galaxy Nexus] osm0sis:
It is good. But I'm sure the S3 one Franco makes is also good, and that one will actually work on your device*. :rolleyes:

* - provided your device is an International Quad-Core S3; otherwise you're SOL.

;)
[Samsung Galaxy Nexus] Bl4ck3urn:
The fix works flawless! Thx franco :cyclops:
[Samsung Galaxy Nexus] dominatore22:
I have a question for you guys. What is tcp congestion avoidance bla bla bla?? :/
[Samsung Galaxy Nexus] billykxda:
Similar to my question on the previous page. Would like to know if I can tweak 295 to provide better battery life, especially during idle.
[Samsung Galaxy Nexus] osm0sis:
Google knows.
[Samsung Galaxy Nexus] max4wdc:
My battery life with r295
[Samsung Galaxy Nexus] ChazzMatt:
It's the Time Travel Activation algorithm. Otherwise known as Time Control Protocol. ;) Shhhh.... It's a secret. Yes, Franco is that good, he turns our Galaxy Nexus into Time Machines. :silly:

But when you find out what it really is, "Westwood" is the best. :good: Choose that one.

Look at the speeds posted by Franco at the bottom of this post:

http://xdaforums.com/showpost.php?p=28152737&postcount=2
[Samsung Galaxy Nexus] ericaraj:
Franco + BB

I tried both M6 and r295 and they lagged horribly on Bugless Beast. Loading times for everything (Play Store, web pages, etc.) were really bad. Quadrant dropped to around 1300 on both (not that quadrant matters much).

It seemed like the cpu was locked at it lowest clock speed, but I checked CPUspy and it showed activity in the higher clock speeds. Does anyone else have this problem? Is there a fix?
[Samsung Galaxy Nexus] franciscofranco:
Sorry but no one has that problem, quite the contrary. My guess is that somehow you managed to turn off cpu1 by some miracle.
[Samsung Galaxy Nexus] RoscoeDpG:
try to do a clean install because i used BB 10/10 build and M6 and got amazing batt life and smooth as anything i have had
[Samsung Galaxy Nexus] michi_1983:
is it on purpose that in latest franco app version in the backup/restore section it says 'clicky on backup' when you click the backup button? :) not important at all, I know, just a hint
[Samsung Galaxy Nexus] OtavioMalzone:
Issue + question + question.

1- milestone 6 and 295 are giving me freezes and reboots when OC about 1.8ghz

BUT, when I was using milestone 5, i could run it in 1.8 withought any problem.

ROM codename android btw.

2- what is the stock config of interactive in stock 4.1 kernel?

3- a question for Francisco:

the configs of interactive aren't too agressive?? omg it run like a bat out of hell, so as the battery...
[Samsung Galaxy Nexus] Controvrsy046:
Dude your opinion on which scheduler is giving the best performance at the moment is all I asked for. Your comment about thinking Franco would implement a ****ty scheduler is not needed and answers like that do not help anyone and don't fit in with the helpful purpose of these forums.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SUTHRNFRIED:
Thanks to Franco and the great advice and support of this thread...I'm finally in the 4hr club with gsm stock batt. I can relax now :)
[Samsung Galaxy Nexus] BigBake88:
But, nonetheless he did answer your question, no?
[Samsung Galaxy Nexus] osm0sis:
Sorry, but not sorry. franco.Kernel is a masterpeice and doesn't need any tweaking really. People always coming and being all "OMGz wHATZthe best Setrings for PERFORMANCe and OR basterry?" is retarded. It's perfectly balanced the way it is, has powermodes to cover that exact ****, and if you want to get to the nittygritty of tweaking all the resources in the world are available to you in this forum for a start by reading back the last 5 pages at any given time and failing that with a click of the search thread button at the top.

The powermodes are a good start, but in the end there are no "best" settings for any of it, you need to figure it out for yourself because your device and your usage is different.
[Samsung Galaxy Nexus] JBNex:
Anyone using Supercharger with this kernel? Is it working well?
[Samsung Galaxy Nexus] Savant:
Using super charger is not worth it on jellybean, but you can try it and see if there is any difference.
[Samsung Galaxy Nexus] BigBake88:
Franco has mentioned many times that this script is basically worthless for our devices being 1gb of ram. We do not need it.
[Samsung Galaxy Nexus] joeyfong:
@franco, pls push at AndroidPIT too, I need the update.
[Samsung Galaxy Nexus] Wynnded:
I'm guessing that you're new to this thread and are unfamiliar with how helpful osm0sis (among others) has been to the progression of this kernel. Actually, he is quite deserving of being referred to as "Dude". And he's Canadian for Pete's sake, some of the most polite folks on the planet.
[Samsung Galaxy Nexus] franciscofranco:
Its on purpose, leaves a small smile in my face when I read "clicky" instead of "click".

1 - Too bad, **** happens. I don't give any support for overclocks and undervolts making a device unstable. If it doesn't work for you, use a lower frequency, problem solved.

2 - I think its 100ms above_hispeed_delay, 50 go_hispeed_load, 60ms min_sample_time and 20ms timer_rate.

3 - Not really, been getting tons of awesome battery reports, people hitting 4h screen on and they couldn't before. All depends on users usage.
[Samsung Galaxy Nexus] cpom1:
What settings do you run franco if you dont mind me asking?
[Samsung Galaxy Nexus] franciscofranco:
I run the same settings that come by default in this Kernel.
[Samsung Galaxy Nexus] timbck2:
Deleted.