yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Icecoldmeat:
I don't know, maybe because I multitask a bit. But with deadline everything looks a bit faster, it can be my imagination, but that won't be it I think.
[Samsung Galaxy Nexus] rebretz000:
Franco r281 is amazing. Great battery life for me. Only changed min freq to 230 or whatever the lowest is.
[Samsung Galaxy Nexus] mpokwsths:
r281 is great!

Static Interactive rocks!
[Samsung Galaxy Nexus] chugger93:
What I've really noticed about 281, is when you wake up your phone after x minutes...WIFI connects so dam fast. Love it
[Samsung Galaxy Nexus] Empty Hand:
(After su) Is that all typed in one line, or the echo 300 first, hit enter and then the rest?
[Samsung Galaxy Nexus] franciscofranco:
Ahahahah thats just awesome. Wait until I tell everyone what I did with Wi-Fi.
[Samsung Galaxy Nexus] momomok:
key in them all in A SINGLE LINE

if the edit succeeds, there will be NO feedback except the prompt at the beginning at the line
[Samsung Galaxy Nexus] yellowdie:
Well I'm gonna go out on a limb and guess you did nothing. lol.

So I reflashed r277 again, then flashed a new r281, still had the lag, echoed 300 and it's running better.
[Samsung Galaxy Nexus] punkeroso:
I would like that WiFi never disconnects, even if the phone has the screen off...
[Samsung Galaxy Nexus] osm0sis:
So to summarize the posts for r281:

- people who were previously lagging (CNA, JellyBro, etc.) are now faster.

- people who were previously faster (Stock, etc.) are now lagging.

:p
[Samsung Galaxy Nexus] ac3theone:
So far so good with r281

Sent from Galaxy Nexus running Rasbeanjelly
[Samsung Galaxy Nexus] renaud:
Probably nothing I would bet.
[Samsung Galaxy Nexus] yellowdie:
Yeppers! Franco's got some magic wizardy behind it alright.
[Samsung Galaxy Nexus] mariachi202:
My guess is you did absolutely nothing.

EDIT: 10 minutes too late.
[Samsung Galaxy Nexus] rodnar77:
dont know if anything changed... but stable and working great.... 1 day running all good... thanks again... now if you could only get this kernel to allow time travel.... that would be great..

THANKS!
[Samsung Galaxy Nexus] yellowdie:
He's close. You just need to overclock it to 1.88 and then set the GPU to 1.21 and you're good to go.
[Samsung Galaxy Nexus] schizophrenia:
anyone able to let me know how can I fix this?
[Samsung Galaxy Nexus] chugger93:
I can wait till u reveal the secret. I wake up my phone and BAM , 3g to wifi instantly. Soooo awesome
[Samsung Galaxy Nexus] Culex316:
He probably injected cocaine into the wi-fi drivers
[Samsung Galaxy Nexus] MizzouBrent:
Why wouldn't you just leave wifi on while the phone is sleeping rather than dropping to 3G? Wifi is much easier on battery life.
[Samsung Galaxy Nexus] chugger93:
I do, I always have my wifi on. All I'm saying is after I hit the power button on my phone from deep sleep (however many minutes it takes) I see my 3g icon real quick, then it goes away and my wifi icon comes up instantly. I don't remember it doing this before...and I've been using Franco's kernel for quite some time. He did something, I'm tellin u. 281 is in a class of its own
[Samsung Galaxy Nexus] chanceomatic:
Hi Francisco,

first thing: I bought your app a while ago. Nice work. Permanent updates!

Second: I had some wifi issues with the 3 or 4 previous nightlies. But they're gone with this one (281)!

I don't know what you changed, but battery life is insane on this one. Running Minco v4, with interactive and no power mode. 7 hours with not much screen time, but the line on the battery is nearly horizontal! 87%!

Keep up the good work!
[Samsung Galaxy Nexus] punkeroso:
I would like to know how to do it...
[Samsung Galaxy Nexus] joaquinf:
:eek: screenshot or never happened :p
[Samsung Galaxy Nexus] leets4uc3:
I'm on dark PA and 281. Still haven't need to do change the cache pressure. Everything is fast and smooth.
[Samsung Galaxy Nexus] qsec:
Enter wifi where you see the wifi hotspots, hit menu, advanced.

Keep wi-fi on during sleep, Always.
[Samsung Galaxy Nexus] nyjohn:
Pretty sure its under WiFi settings advanced and there will be an option to keep WiFi on during sleeping and it comes disabled for most ROMs.
[Samsung Galaxy Nexus] qsec:
Double check wifi sleep settings under advanced so that it is set to 'Always'
[Samsung Galaxy Nexus] zenzip:
Up

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] J-Hop2o6:
He said "7 hours with not much screen time". So 7 hours UP, maybe 1-2 hrs Screen ON so far. I had to re-read it also :p
[Samsung Galaxy Nexus] chugger93:
Why would you set that to always. That's a horrible choice. I did that once and my battery dropped like 30% overnight.
[Samsung Galaxy Nexus] franciscofranco:
I'll be honest, I have no idea, but probably not.
[Samsung Galaxy Nexus] Zantiszar:
With which clock speed ?
[Samsung Galaxy Nexus] yellowdie:
I have never used anything OTHER than 'Always' because I use wifi 95% of the time. My battery drops anywhere from 0.5% to 2% per hour over night. So I highly recommend always setting it to Always. :)
[Samsung Galaxy Nexus] osm0sis:
As long as you aren't getting nasty wlan_rx_wake locks keeping your phone awake, wifi sleep policy set to 'always' is better on battery since otherwise switching over uses battery and the policy itself deciding when to turn wifi on/off does too. If you ARE getting those wlan_rx wakelocks then turning off wifi when the phone sleeps will be better. Really you should track down your rogue apps, but if you can't figure it out or its an app you can't live without, the sleep policy will help your deep sleep %.
[Samsung Galaxy Nexus] jonstrong:
Been using 281 for a few hours with CNA 3.6.5. Seems incredibly smooth, and battery life seems good: after 3 hours screen time, I still had 29% battery left. BUT...I had the phone plugged in for a while, and it barely seemed to charge. I'll have to experiment and see if I just wasn't paying attention to the time, etc, but my impression had been that with 277, the phone would charge incredibly quickly -- but also expend power faster when in use and running on battery. With this, it seems to make better use of battery, but for some reason doesn't seem to be taking on a new charge as well.

Could all be my imagination, as these are all after-the-fact observations, with absolutely no controls or basis for consistency. I'll keep observing and report back whether this seems consistent or was just something I imagined.
[Samsung Galaxy Nexus] yahyoh:
Hmm not bad

this the first time i can run 512 gpu without artefacts :cool:

i hope the 512 will not affect too much on battery :fingers-crossed:

btw 281 run very smooth on latest cm10 nightly
[Samsung Galaxy Nexus] TheMan0790:
Are the wake locks only caused by rogue apps? I had this problem even before any apps were installed on my phone. Also, I only notice wake locks when others connect to the network I'm on...if I'm the only one on the network, I don't see this problem.
[Samsung Galaxy Nexus] punkeroso:
I do have the WiFI policy set to "Always" but, randomly, when I wake up the phone, I see that it's not connected.

Read here http://xdaforums.com/showthread.php?t=1625705
[Samsung Galaxy Nexus] yahyoh:
Also wifi signal seems better and wifi seems more stable i had some disconnects with 277
[Samsung Galaxy Nexus] tarekh020:
Thank you Franco for the awesomness

It's also happened with me while i was sleep , after i woke-up i found the battery drained from 55% to a turned off phone in about 7 hours ,when i made the choice " Always " :silly:

But if left settings at default , the battery is great and last like for ever with the latest impressive nightly 281 :good:

I lose about 1% every an hour approx.

The best combo till now : maguro AOKP JB Build 4 + franco 281 = snappy , fast and smooth phone with immortal battery :good:

Great work from a big dev
[Samsung Galaxy Nexus] zenzip:
Lol immortal battery...

Pls share your complete setting :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Pkt_Lnt:
There is a new app named Better Wifi on/off, being developed by @chamonix, author of Better Battery Stats, that addresses this as well.

http://xdaforums.com/showthread.php?t=1801284
[Samsung Galaxy Nexus] franciscofranco:
Ok I've had my laugh for almost 24 hours, time to tell whats all about that Wi-Fi.

It's fairly simple really and I think this can be a lesson for everyone that uses my kernel or any other kernel around here. Our brains are some ****ing little jokers, they see what they want us to see. When I release a kernel and say "200% performance boost" or "immortal battery life no need for a charger anymore until the ends of time" it tricks our brains and we actually see those improvements because thats what we want to see. Thats one of the reasons why I ask for feedback about real world usage and not benchmarks etc.

About Wi-Fi drivers... remember before I changed the drivers, when we actually used stock drivers, most of you were on about weak Wi-Fi signal and lost connections etc. Then I merged some newer drivers from Google and you got all excited and saw over 9000 Wi-Fi performance boost. Then I merged some newer drivers again which broke WEP routers connectivities. Those drivers were actually ****ing awesome, I saw some real world improvements but without having 100% compatibility they were a no go. I then reverted to the other newer than stock drivers and up until now we've seen some 50-50 reports. Some are good, some aren't - but before when I had them in the kernel people were very happy with them. Then I decided what the **** I'll return to stock Wi-Fi drivers and see the reaction. So there you go. Easy psychological work, problem solved :)

About the rest of the kernel I actually changed some stuff around. I enabled a Sync mechanism that was disabled by default that facilitates hardware synchronizations specially on the GPU side thats why most of you noticed better gaming experience.

Thats pretty much it :) I had some laughs so thank you all for that :D
[Samsung Galaxy Nexus] chugger93:
so 281 is on stock drivers? Good enough for me. Works better in my case. Nice psych work you nutter.

I still think 281 is good lol
[Samsung Galaxy Nexus] emd2009:
To answer my own question, finally figured out that you are using the FragmentPagerAdapter to create the tabs :good:
[Samsung Galaxy Nexus] franciscofranco:
Exactly stock Wi-Fi drivers. I only merged a patch inspired from one patch from Entropy to reduce/remove wlan_rx_wake wakelocks, but that doesn't interfere with any signal strength or connection losts.

Sorry I missed your post. Yes thats what I use :)
[Samsung Galaxy Nexus] 5nickers:
Your best joke till now. I already thought it was some kind of joking because normally you post a changelog :D

Good guy franco ;)
[Samsung Galaxy Nexus] tarekh020:
Nothing Special everything at it's default except for governer Dyinteractive with a turned off gps ,bt , mobile data, and the brightness is 25% with sound at max and vibration when ring or touch and lockscreen i wonder why i use vibration a lot but didn't find-out :cyclops:
[Samsung Galaxy Nexus] chanceomatic:
Yeah. I that is the reason I mentioned it.
[Samsung Galaxy Nexus] chanceomatic:
I expected something like that. The stock wifi drivers are perfect for me... No problems at all.
[Samsung Galaxy Nexus] Culex316:
lol I knew it was some sort of mind****...but to be honest, all of the wifi drivers you have ever put in your kernel have worked fine for me..in fact..I do not even notice a difference between any of them...it's like you never changed anything lol.

What about the vfs_compression thing you told us to change? Is there any tradeoff/drawback to increasing the value above 100?
[Samsung Galaxy Nexus] qsec:
Because i almost always use wifi. I had this set for always since Cupcake days.

About your battery drop it had to be some rouge app causing it.

My phone drains about 4-5% over 8h sleep with standard sync on.
[Samsung Galaxy Nexus] nuwan32:
No wonder. My performance in gta 3 improved tons. Getting way better fps. Awesome. And I never notice the difference between Wi-Fi drivers lol
[Samsung Galaxy Nexus] franciscofranco:
Oh yes. before r281 I always had init.rc to set vfs_cache_pressure to 300. For testing I removed that line on r281. Just try and see what feels best for yourself. Theres plenty information on Google about that tunable which should explain better than me what it does, but its basically putting more or less pressure on cache.
[Samsung Galaxy Nexus] simms22:
youre in a better mood, 12 stars instead of letters in the post.. im happy for you :)
[Samsung Galaxy Nexus] yellowdie:
Dang, now my wifi sucks! I didn't change anything, it just stopped working. AH! Stock sucks!!!

lol. jk jk. :):D:laugh::good:

So what's the highest it goes? Is 100-300 the full range? Or can you push it to 600? Is higher or lower theoretically better?
[Samsung Galaxy Nexus] franciscofranco:
Touché!!

Don't know whats the maximum value allowed, or if there is a maximum, try it and tell us!
[Samsung Galaxy Nexus] yellowdie:
init.d, here I come!! We're bumpin' our junk to 3000!!!!! (Prayin' it works! lol)
[Samsung Galaxy Nexus] SUTHRNFRIED:
Placebo effect. Nice. :)
[Samsung Galaxy Nexus] zenzip:
This is called "user experience" for me.

the psychological factor is an important part of user experience, for kernel, smartphone, pc's etc....

Placebo effect docet, first of all Apple sells millions of devices using the same concept (for marketing).

That's my opinion.

Franco respect you!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
200% true.
[Samsung Galaxy Nexus] osm0sis:
Hopefully someone fixes those.. they were the only ones I saw a real difference with for JB connection strength/losses.

Will you be changing the cache pressure setting back for the next build or maybe add it to the updater? :D
[Samsung Galaxy Nexus] nuwan32:
Do the color multipliers affect battery? Because 51% of my battery usage goes to the screen apparently
[Samsung Galaxy Nexus] Serious_Beans:
The reason 51% goes to the screen is because we have a huge screen. That's what usually kills the battery, screen usage.
[Samsung Galaxy Nexus] yellowdie:
Okay. So I took an extra dose of stupid placebo pills this morning. I see very little differences whatsoever between setting the pressure from 100 to 3000 and everywhere in the middle (300, 600, 1000). It was definitely slower when I set it between 1 and 50. I would say the best was probably when I used 500. I used init.d files to set it (cleared cache when I rebooted just to test) and I changed them manually (and then waited five minutes). No difference between the two methods.

So final conclusion: It's all the same (but I'd still settle on 500). Placebo pills at it's finest. Way to go, Franco!

:):D:laugh::good:
[Samsung Galaxy Nexus] The Gingerbread Man:
#251 was definatly best WiFi for me too. Not tested 281 but will flash it when home

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
I agree. I was testing the strength this morning (before the Big Reveal) and I was getting -70 to -60 when I was getting -50 to -40 with the other drivers. I'll do some screen shots when I get home to prove it. :)
[Samsung Galaxy Nexus] nuwan32:
Yea but 51% seems a bit too high. I use auto brightness. Does everyone get this high of a usage for screen?
[Samsung Galaxy Nexus] JarGnex:
I actually had a problem with my WiFi. I turned WiFi off as I was watching a video (WiFi is too slow for HD videos) and the phone just wouldn't connect to Google servers and the video never loaded. So I had to restart my phone :/

Everything else is perfect I'm using the 512gpu
[Samsung Galaxy Nexus] nemotheblue:
@Franco, I've done some Googling to learn more about vfs_cache_pressure, and so far everything I've found seems to fly in the face of your recommendation of increasing its value. There are posts and guides all over advising Android users to reduce the value to the 5-20 range, in order to improve performance - these include Imoseyon's blog, AndroidForums and even some "How to" guides about tweaking performance like this one. On the other hand, XDA user _thalamus seems to think it makes no real difference in practice.

I don't claim to have any experience with sysctl myself, and I wasn't able to find a definition of the vfs_cache_pressure that wasn't just someone paraphrasing, but I'm curious what convinced you to go in the opposite direction?
[Samsung Galaxy Nexus] tobitronics:
As i read this whole placebo story: it is probably not a good idea to switch back to franco from trinity alpha? I'm not so impressed with it but i dont want to get a bad first user exprience when returning to franco ;)

Beamed from my Paranoid Google Nexus 7
[Samsung Galaxy Nexus] galakanokis:
I agree, I have never had wifi issues but I did see a noticeable difference in performance with the newer drivers. There were a few places that I couldn't connect to but they were unimportant.
[Samsung Galaxy Nexus] punkeroso:
@franciscofranco

I'm on stock rom, do I need to flash some sort of init.d support in order to correctly run this kernel? If yes, which one?

Thanks
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope flash the kernel and that's it, the kernel does the rest. You might want to concider buying the franco.kernel app to easily manage various settings but its not compulsory but I'd highly recommend it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Marcb:
:cool:

+1!

I've never had any problems with wifi, no matter what driver the kernel was using, but that newer wifi driver, from r251 was definitely the best one...

I hope the bugs can be fixed so we can use that one again!
[Samsung Galaxy Nexus] kyokeun1234:
Flashed the latest kernel and I don't feel any lag. Good job! :thumbup:

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] yellowdie:
Interesting find. I'll look those up when I get home as well. But from my experience 1-50 felt more lag than 100+. I didn't see much of a difference in the high numbers, but I did in the really low ones. Stange. Lol
[Samsung Galaxy Nexus] nuumuun:
i usually get between 60% and 70% screen battery usage.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mikeandjaimie:
Same.. My screen on usually takes about 70%of my battery with 2.5-3hrs screen on.. Always thought that was normal since it drains almost nothing in standby
[Samsung Galaxy Nexus] OMFGNuts:
Just got 6 hours screen time. 13 of total usage

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] kyokeun1234:
That's crazy... tell me your secret :p

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] Savant:
Screen shot or don't believe it.
[Samsung Galaxy Nexus] nuwan32:
Alright then thanks. I'm actually using 1000 in vfs cache pressure lol. Doesn't feel any different from 100 imo.
[Samsung Galaxy Nexus] danielvc:
Yeah sure, reading ebooks with a black background. n1
[Samsung Galaxy Nexus] Savant:
Pictures would be nice because when people say they got that , they are usually charging in between.
[Samsung Galaxy Nexus] happymonk:
I was charging my phone. The phone was left switched on overnight running airplane mode.. I'm running stock Jelly Bean ROM with the latest franco.Kernel Nightlies 512GPU. I realized that my CPU is constant at 729 MHz. Is it normal?
[Samsung Galaxy Nexus] Antob125:
Franco, if nothing else changed besides the wifi drivers then what we're all the reports about people experiencing lag? You even gave out a command line to run to fix the problem? Where's the lag from if all you did was mess with wifi?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yahyoh:
screenshot or
[Samsung Galaxy Nexus] slvrarrow:
I've had 5hr30 to 6hr if im inside on wifi all day browsing with probably every kernel from 240 ish onwards using cm10
[Samsung Galaxy Nexus] OMFGNuts:
Oh, Just remembered that i actually was chargjng [ from friends notebook during univercity

My bad, sorz guys

View attachment 1373968

View attachment 1373969

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] osm0sis:
You must have missed the post where he talked about changing the init.rc that set the vfs cache value to 300... so now it's the default 100.. hence his command. I just ended up switching to 512GPU to fix the lag, though I prefer to not overclock.
[Samsung Galaxy Nexus] franciscofranco:
I explained below the Wi-Fi text what I changed besides the drivers ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm stoked for the next release already :D I prefer the other WiFi drivers (stock works fine but just preference seems faster to me) and this sync thing what ever it is seems to make things a little smoother but reverting this cache back to 300 would be better I reckon for ultimate butter smoothness

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slvrarrow:
Have you got any wizardry to come Franco or are you reaching the limit? Somesstuff from the 3.6 Linux release regarding network tweaks looked cool big improvement in Web page loading time. No idea if stuff like that is even relevant.

The couple of times I've seen you say you're reaching the limit you go beyond... It's brilliant
[Samsung Galaxy Nexus] gaich:
These are my setings:
[Samsung Galaxy Nexus] osm0sis:
You upped the voltage on 230MHz to 825mV?
[Samsung Galaxy Nexus] gaich:
I don`t use this slot now and don`t remember what was the built-in voltage, but it seems to me it was more than 825...
[Samsung Galaxy Nexus] osm0sis:
Ahh okay. That slot is now not SR calibrated (it used to calibrate to 840mV), and defaults to 820mV just so you know. :)
[Samsung Galaxy Nexus] goTouch:
r281 is already updated to 3.0.44?

Enviado do meu Galaxy Nexus
[Samsung Galaxy Nexus] JBNex:
What's default algorithm for latest jb kernel for tcp
[Samsung Galaxy Nexus] Wynnded:
My WiFi signal strength indicator shines brighter with the stock drivers. ;)
[Samsung Galaxy Nexus] xeonyxorich:
Cubic I think
[Samsung Galaxy Nexus] RoscoeDpG:
First full cycle with 281 and ran smooth and no lag and everything with WiFi was perfect batt life was nice too, i know not many screen on time but had long convo on phone and was mostly on 4g and sync was on
[Samsung Galaxy Nexus] digweed4me:
wow 281 is very snappy and i am getting almost 5 hour screen on time with stock battery.

can anybody explain me what is tcp congestion avoidance algorithm?
[Samsung Galaxy Nexus] Pkt_Lnt:
Read back to this time yesterday, it has been discussed in great depth with many research links posted. I doubt they want to type it all again.......
[Samsung Galaxy Nexus] Wynnded:
https://en.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
[Samsung Galaxy Nexus] thisguy23:
Edit: btw thank you Franco for all your work. This is the only kernel I've used since I've had my gnexus.

Got a serious question folks... When running several different types stress test, and why does the processor not stay at max speed? How does it bounce down to 384 & 729?

To restate, when running something that ask for 100% of the cpu power, why does the app not get 100% all the time?

Thermal throttle: I get same results with this checked or unchecked. Phone refuses to break 74c or stay at 1.5 for very long. It stays @1.2 90%

My settings are attached.

Also it's not that I want a nuke reactor in my hand, for when I want to play with the settings to see what my phone can do, I want to see what it can do!
[Samsung Galaxy Nexus] 11768:
I notice this too sometimes during heavy load where the CPU usage is 100% but the step jumps around the max (for me is 1305) and the lower's one such as 1036, 729, and 384 causing lag/freeze.

I am using interactive governor.
[Samsung Galaxy Nexus] shreddintyres:
Franco absolutely phenomenal job with this kernel getting impressive battery life with 281, nearly 2 hours screen on with 50% remaining thank you for all your hard work
[Samsung Galaxy Nexus] Culex316:
Franco thanks to this new nightly all my games seriously run better than ever, asphalt 7 runs perfectly and it even helps the play station emulator I have run a tad bit smoother thanks!
[Samsung Galaxy Nexus] nuwan32:
this never happened before, but after a full days used i gotta a LOT of wake clock issues on r281. anyone else have this?