yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] drawde40599:
That works fine here no force close with new version ( i just went threw every single setting within the app no issues! ) but it did just tell me I didn't have supersu installed but I've been using supersu since Be4 it was cool ;)
[Samsung Galaxy Nexus] hiarc:
I am getting the same issues on my phone. At first I thought maybe I messed something up because I was working on something, but after clearing the data/cache and re-installing same problem occurs when I try to go to OC/UV or Settings tab. I am using 9/26 RasBeanJelly.
[Samsung Galaxy Nexus] CADude:
Confirmed on my Rasbeanjelly 9/26 with latest SuperSU :(
[Samsung Galaxy Nexus] leets4uc3:
I have tried like 8 TCP algorithms and for every only I get about 200 down and 1200 up in speed test. I have no idea what's going on. Usually in my house I I get like 2k-4k down and 2k up. I am in Arizona if that matters. Any thoughts?
[Samsung Galaxy Nexus] !crazy:
Could you tell a little more about what changes did you make?

Also, what for is the 'boost' variable? I see it is disabled per default.
[Samsung Galaxy Nexus] Kappa Lamda:
Same issue reported on previous page for me. Latest franco.updater and on OC/UV tab when I chose governor control I get FC.

I am on 26092012 rasbeanjelly
[Samsung Galaxy Nexus] drawde40599:
AOKP build 4, your app ( today's update) working flawless not having any force close issues like others, went threw whole app changed and used everything possible trying to get to fail and it did not

277 running flawless with stock settings. Thank u
[Samsung Galaxy Nexus] Astug:
Same here. :( Running Bugless Beast (27th september nightly) with r277, app opens fine and quick but when I switch to the CPU speed tab, it force closes.
[Samsung Galaxy Nexus] J-Hop2o6:
I had that once! Yea the first time I rebooted or upgraded with my first use with PGM. I think I had to battery pull. All fine after that.
[Samsung Galaxy Nexus] lucas4ever:
r277 running fine without any errors on RasBeanJelly. No FC.
[Samsung Galaxy Nexus] !crazy:
Stock JB, no PGM no FC. SuperSU 0.96.

edit:

Ok mentioning PGM was stupid.
[Samsung Galaxy Nexus] mrm43:
r277 running flawless here with stock settings too. No fc. Xenonhd rom used.
[Samsung Galaxy Nexus] Antob125:
Same here weird

Sent from my Galaxy Nexus

---------- Post added at 05:51 AM ---------- Previous post was at 05:36 AM ----------

Hey Franco. Great kernel and great app. I did some reading for the new TCP feature you added on wiki. I'm not to good in understanding what it does. But from what I read it seems that each setting handles Internet speed differently? Cubic is default and it seems Westwood or Westwood+ are the fastest? How do we know which option to choose? Just try out each one? And how can we test which is the best? I'm just trying to figure it all out.

Sent from my Galaxy Nexus

---------- Post added at 05:52 AM ---------- Previous post was at 05:51 AM ----------

Hey Franco. Great kernel and great app. I did some reading for the new TCP feature you added on wiki. I'm not to good in understanding what it does. But from what I read it seems that each setting handles Internet speed differently? Cubic is default and it seems Westwood or Westwood+ are the fastest? How do we know which option to choose? Just try out each one? And how can we test which is the best? I'm just trying to figure it all out.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Fenvarien:
New app version is running stable und without any fc here (MiNCO ROM and r277,512).
[Samsung Galaxy Nexus] osm0sis:
Just a guess, but depending on how you rooted, you might have SuperSU installed as Superuser.apk, causing the confusion.
[Samsung Galaxy Nexus] RevengeFNF:
What TCP Congestion do you guys prefer?
[Samsung Galaxy Nexus] OMFGNuts:
Westwood

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] osm0sis:
So far, veno and westwood+ feel the fastest.

Edit: I also tested cubic, vegas and illinois since these were the 5 that caught my eye in my reading. Definitely leaning toward westwood+. :good:
[Samsung Galaxy Nexus] reflexr:
Look at the First Page ( at the end) . There are some Informations about each Mode

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Yup. I know. ;) Throughput isn't everything though, we've got to go by "real world feel" over Cell and Wifi both and weigh that with throughput to find the one we like best.
[Samsung Galaxy Nexus] franciscofranco:
Programming for Android can be a little ungrateful sometimes. I tested the app in 4 different devices and 0 FC before I released. I'll fix whatever needs to be fixing soon.
[Samsung Galaxy Nexus] derPianist:
But when you can't reproduce the Problem, how can you fix it then?

Seems pretty hard to me... :D

via Google Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Because I can see the sent logs to my Developer account on Google and if there is some wacky code I can guess whatever is ****ing up.
[Samsung Galaxy Nexus] ChazzMatt:
That's why he's so good. ;)

OK, that too.
[Samsung Galaxy Nexus] Fenvarien:
+1

Westwood+ seems to be working very well.

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] franciscofranco:
I just pushed v6.9.1, hope Google adds it fast :)
[Samsung Galaxy Nexus] gaich:
My system does not show westwood+, there`s only westwood. Is it normal?
[Samsung Galaxy Nexus] exzacklyright:
Same within the app no Westwood plus
[Samsung Galaxy Nexus] yellowdie:
:good:
[Samsung Galaxy Nexus] KJW979:
Mentioned a few posts back that shows up as Westwood but actually is Westwood+.
[Samsung Galaxy Nexus] styr:
v6.9.1 of the app fixed my FC issues, thank you.
[Samsung Galaxy Nexus] ChazzMatt:
TCP congestion avoidance algorithms

Westwood+ vs New Reno vs Vegas

Westwood+ comes out on top in the paper's conclusion, comparing 3 of the popular TCP congestion avoidance algorithms:
[Samsung Galaxy Nexus] Culex316:
I a unfortunately still having the same force close problem with this new update :(.

I sent a bug report vía the force close window.
[Samsung Galaxy Nexus] franciscofranco:
Just pushed 6.9.2, should fix everything, thanks guys﻿
[Samsung Galaxy Nexus] Antob125:
So from what I read on wiki, TCP controls data speed? Is that right?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joeyfong:
AndroidPIT please.
[Samsung Galaxy Nexus] Astug:
It didn't for me. Still force closes when I go to the CPU speed/governor tab. :(

I've tryed clearing cache.

I use SuperSU.

Edit: .2 fixed it! Thank you.
[Samsung Galaxy Nexus] nuwan32:
Nope it says supersu.apk in system/app
[Samsung Galaxy Nexus] six_dfx:
TCP is the underlying protocol for a vast majority of internet services, it's resposible for in-order delivery of data and loss tolerance via retransmits.

Different TCP congestion management algorithms were developed to get the best of many different connections types with highly varying bandwidths and latencies.

So it's more or less like that: for a given connection speed / latency / packet loss / burst length / ... there is one TCP algorithm that will give you the best speed.
[Samsung Galaxy Nexus] Antob125:
So what's the best way to test each one to see what's best? Speed test? Or data drops? Or something to that nature?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pkgnex:
six_dfx is correct. Also, for what it's worth, I have found over the last couple of days that on my home wifi network, Westwood yields the fastest upload/download speeds by a small margin (5-10 %) over the next best algorithm, and while on Verizon's LTE network in my home or workplace, Illinois yields the fastest speeds by a very significant margin (20-25%). Since I'm generally most data speed-conscious while out-and-about, I've settled on TCP-Illinois as my default.
[Samsung Galaxy Nexus] osm0sis:
Wow! Great find! I wonder how it does against veno (vegas+reno hybrid), and illinois.

Also I wonder if DD-WRT is using westwood or westwood+.. they only include vegas, westwood and bic for options.
[Samsung Galaxy Nexus] Culex316:
The new update fixed the issue, thanks!!:D

Edit: is it just me or is the TCP congestion algorithm swapping interface not in the app at all? I looked everywhere... (using latest version 6.9.2)
[Samsung Galaxy Nexus] Wynnded:
It's not under Setting>Kernel Setting within the app? It is in my 6.9.1 as the Play Store hasn't updated for me yet....fwiw.

Edit: Updated and it's there if you scroll down a little.
[Samsung Galaxy Nexus] Culex316:
I gotta agree, I just tried out Westwood and my Nexus hit 8.78Mbps download speeds on T-Mobile HSPA+ for the first time EVER!! This is great!

---------- Post added at 12:48 PM ---------- Previous post was at 12:38 PM ----------

I'm on 6.9.2. and I do not see it under kernel settings (the same window with wifi pm_fast, battery life extender, high performance sound etc.....under which one is it supposed to be in? I stared at the screen for like 5 min already looking for it..
[Samsung Galaxy Nexus] !crazy:
Here it is below Battery Life eXtender...
[Samsung Galaxy Nexus] franciscofranco:
Gotta love Android and its fragmentation. The issue is pretty simple: if the command to list the algorithms return null (means that the command was unsuccessful) the interface to change algorithms hides itself to prevent an Null pointer exception FC. In your case I believe you dont busybox installed correctly or the PATH is incorrectly set up. Not saying its your fault but rather bad rom implementation of the binaries.
[Samsung Galaxy Nexus] Zantiszar:
Well first time having FC on Franco's app and its whenever I scroll to where the clock adjustments are. Never happens before >_< I'm running miui atm could it be that ?
[Samsung Galaxy Nexus] ChazzMatt:
Somebody else asked that in a

DD-WRT thread,

and the answer he got was yes -- in DD-WRT, Westwood = Westwood+ and Reno = New Reno. It's also where I found the link to the paper.
[Samsung Galaxy Nexus] franciscofranco:
Update to 6.9.2.
[Samsung Galaxy Nexus] Zantiszar:
As a matter in fact I just did the update and all solved ;) thanks your da best
[Samsung Galaxy Nexus] supernova_00:
Franco, there appears to be a bit more in the newest Linux 3.6 then you hit on a day or so ago when someone asked you about it. See here for the changelog but here are some highlights that I see (who knows if they are kernel related or not but figure I'll point out some changes):

TCP Fast Open (client side)

"Fast Open" is a optimization to the process of stablishing a TCP connection that allows the elimination of one round time trip (RTT) from certain kinds of TCP conversations. Fast Open could result in speed improvements of between 4% and 41% in the page load times on popular web sites

Bufferbloat fight: TCP small queues

TCP small queues is another mechanism designed to fight bufferbloat. TCP Small Queues goal is to reduce number of TCP packets in xmit queues (qdisc & device queues), to reduce RTT and cwnd bias, part of the bufferbloat problem. Without reduction of nominal bandwidth, we have reduction of buffering per bulk sender : < 1ms on Gbit (instead of 50ms with TSO) and < 8ms on 100Mbit (instead of 132 ms).

Various core changes

•process scheduler: Remove broken power estimation (commit)

•cpuidle: add support for states that affect multiple CPUs (commit)

Memory Management

•Allow swap readahead IOPS to be merged, it improves throughput and at the same time lowers CPU consumption

Networking

•tcp: implement the RFC 5691 3.2 mitigation against Blind Reset attack using RST bit (commit) and SYN bit, RFC 5961 4.2 (commit)

•Add support for 40GbE link (commit)

•Add 802.11ad (60 GHz band) support (commit)

•Speedup /proc/net/unix (commit)

•wireless: remove wext sysfs

Now I don't want to pretend I know what all of that means but some of it sounds it could be great for us.
[Samsung Galaxy Nexus] schizophrenia:
Franco, I know you or some other members are going to bash me for asking but I have a weird situation here.

I cleaned flash CNA 3.6.5 the day before together with your r277 and the phone just seemed very laggy. So i decided to keep it for a day and see if it improved eventually but it did not. As discussed with momomok as he also uses the same rom and same franco nightly, we decided to switched back to r276 and the lag seems to have gone. Just a few hours ago I went to r277 again to make sure there was not any placebo effect and noticed (confirmed) that r277 does have very laggy effect on CNA3.6.5 but not on r276.

I know you put on changelog that the differences between r277 and r276 are just some voltage differences and "TCP Congestion Algorithm".

Please note that r276 has been running smoothly on CNA3.6.0 and the nightly thereafter and now on CNA3.6.5. It is just r277 is laggy.

Is there in any way that you may have an idea why there is this lag coming out of nowhere?
[Samsung Galaxy Nexus] Culex316:
You know what it was? A bad busybox install. There are two apps that show up on Google Play when you search for "busybox install", one is Busybox installer by Jrummy Apps inc and the other one is Busybox by Stephen (which is XDA-recommended).

I had originally installed busybox with the Jrummy Apps installer and that somehow did not set up the path correctly, so whenever I wanted to do a busybox command, I had to enter "busybox" followed by the command instead of just the command itself (busybox sysctl vs. sysctl) in the terminal emulator.

well, I deleted that puta program and got the Stephen Busybox installer and now all it well again (paths are set up correctly and the TCP congestion option now shows up in your app):good:

I'm using Stock Jelly Bean too btw.
[Samsung Galaxy Nexus] sk8oldschool74:
Hey franco I bought and installed your app been having some problems w/ it causing my phone to freeze. I know it is a work in progress so no complaints but was wondering if you could send me a pm to the link to your kernels? So I can download them manually Thanx keep up the great work :) withdraw request lol Thanx to big baked 88...
[Samsung Galaxy Nexus] yellowdie:
I have CNA 3.6.5 with r277 and my phone is flying fast. I'm not saying its your fault or you're doing anything wrong, I'm just saying it's not necessarily that combo causing issues. I used r276 and didn't have any issues--actually I've used every single release (except for the wifi tests) and have never had any issues. Just throwin' my two cents out there. :)
[Samsung Galaxy Nexus] BigBake88:
Right in the OP dude! :laugh:
[Samsung Galaxy Nexus] schizophrenia:
Thanks for the quick reply....

odd.. because both me and momomok have the same situation.

and we have a hard time figuring out what has been wrong

you using "interactive" on your r277?

I also have been using every nightly from franco except those "test" ones and never really got any problems unless those franco knew they were buggy (if there are any)...

but this is the first time I am seeing some really odd situation that r276 is smooth and r277 is not in the same rom...

always cleaned cache/dalvik cache already and had clean installed the rom.
[Samsung Galaxy Nexus] timbck2:
Which Busybox install are folks using? I'm using JRummy with no issues, but I didn't know there were two to choose from. I take that back, I do have one issue with JRummy Busybox - it often tells me there's an update available but the version number is the same as what I have installed. Anyone else seeing that?
[Samsung Galaxy Nexus] yellowdie:
Humor me: try downloading r277 again--maybe you got some bad download or something? And are you using 384 or 512? I've always used 384 up until r277, I decided to try 512; so maybe give that a shot. My phone ran fine on 512 but had funky artifacts, so I never pushed it. But when Boss Man fixed the voltages and took out SR for the Core/GPU, I decided to try 512 and have been running fantastic with it. HUGE plus for me! I don't really see any battery drain because of 512 (still got almost three hours of screen time yesterday).

To recap, download a fresh 384 and 512 and copy them both to your SD manually:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/franco.Kernel-r277-384GPU.zip

http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/franco.Kernel-r277-512GPU.zip

And give them a try that way. :):D:laugh::good:
[Samsung Galaxy Nexus] franciscofranco:
You say you flashed CNA 3.6.5 whats that rom change log?
[Samsung Galaxy Nexus] schizophrenia:
although I came from CNA3.6.0 nightly 0926 which worked fine with franco and now CNA3.6.5, I can only find changelog from CNA 3.6.0 to 3.6.5

Codename Android 3.6.0 – 3.6.5 Changelog http://goo.gl/Tau7p

———

[additions]

* new Codename(Android) wallpapers -

(Codenamedroid, LordGarlicbeard, Paranoid Android)

* custom navbar icons - (Zaphod-Beeblebrox, modified to work with CNA)

* notification wallpaper - (xoomdev, modified to work with CNA)

* statusbar transparency - (Paranoid Android)

* re-added navbar color

* added force tablet and dpi change

(dagr8 - Settings -> Interface -> Gerneral UI)

* added alternate signal layout

(Zaphod-Beeblebrox - Settings -> Interface -> Status bar)

* added IME switcher and Ring/Vibe toggle as navring target

(Boris Bershadskiy)

* added IME toggler as Navbar target (Boris Bershadskiy)

* increased themeability of the statusbar (Zaphod-Beeblebrox)

* added the advanced calulator features from cm

* add alow mock sms to developer settings (jruesga)

* new command line tools:

htop, lsof, powertop, nano, vim

---------- Post added at 02:07 AM ---------- Previous post was at 02:05 AM ----------

Thanks and i will try that again then.

I have always been using 512 without any problems at all so I was using r276 and r277 with 512

EDIT: r276 works very snappy on CNA3.6.5 right now but not r277
[Samsung Galaxy Nexus] Antob125:
So best way to check which TCP setting is best is run a speed test for each one?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Pretty much YMMV
[Samsung Galaxy Nexus] notreally:
I had the same impression from CNA 3.6.5 + Franco r277, no hard data just my gut feeling.

Not sure if this matters but I did a full wipe for the first time to 3.6.5+277 had anything to do it with it vs. my first ever custom ROM flash of 3.6.0 + 276, dirty over the stock OTA update.
[Samsung Galaxy Nexus] schizophrenia:
actually you and I and momomok are probably not the only one as I recalled someone or two from CNA thread also had the same thing when momomok asked but I can't find too much data from them now
[Samsung Galaxy Nexus] Antob125:
Veno and Highspeed TCP settings are the fastest for me in NY.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] J-Hop2o6:
Here's my test results at work. YMMV. I will test again at home which is a better area. This test wasn't much of a speed test, but more of a stability test depending on varied ping and speed drops.

More Stable:

Cubic

Reno

Hybla

lp

Mid Stable:

Illinois

Highspeed

HTCP

Vegas

Scalable

Less Stable:

Westwood

Bic

Veno

Yeah

I think my favorite right now is Reno and Hybla. Will keep testing.
[Samsung Galaxy Nexus] nuwan32:
TCP algorithms dont affect data, only wifi, so i think your increase in data speeds was just luck.
[Samsung Galaxy Nexus] kendoori:
Bluetooth Alert Tone Control, Possible?

I have a special need regarding bluetooth alert tones. I wear hearing aids and have a BT phone clip that sits between my phone and hearing aids. Works amazing well, but the standard bluetooth confirmation tones are very loud, in spite of having turned down every possible control on the phone. I was suggested elewhere to suggest this feature... I'm running r266 on my GNEx.
[Samsung Galaxy Nexus] schizophrenia:
tried downloading and flashed again, no luck....

still lagging here and there vs r276 runs snappy
[Samsung Galaxy Nexus] Culex316:
ah I see, thanks for the heads up then.
[Samsung Galaxy Nexus] osm0sis:
But how does cellular data work if not through TCP? I mean it's got to become TCP at some point. :confused:

Edit: http://en.wikipedia.org/wiki/GPRS#Protocols_supported

"When TCP/IP is used, each phone can have one or more IP addresses allocated. GPRS will store and forward the IP packets to the phone even during handover. The TCP handles any packet loss (e.g. due to a radio noise induced pause)."

Sounds like it should work?
[Samsung Galaxy Nexus] J-Hop2o6:
Really? I guess disregard my tests from earlier since those were Data tests.
[Samsung Galaxy Nexus] Antob125:
For real? See that's what I asked earlier and got no response. Damn. So I guess speed test on wifi to see what's best?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] J-Hop2o6:
I always wondered, but what the hell is busybox? I know most custom roms has them, but what's the purpose of it?
[Samsung Galaxy Nexus] franciscofranco:
Its a binary pack.
[Samsung Galaxy Nexus] punkeroso:
Wifi High Performance

Hi franco,

first of all I would like to thank you for the great work for this phone; I found you kernel really awesome.

I only have one issue that I also had with other kernels: I can't get wifi active when the screen is off, even with the "wifi high performance" enebled.

I mean, it seems to remain active but, randomly, when I turn on the display, I see that it wasn't.

I'm on stock JB.

Thanks for your support!
[Samsung Galaxy Nexus] creeve4:
Source?

Interesting reading
[Samsung Galaxy Nexus] osm0sis:
The linux command set is limited on Android so busybox is used to bring it up to par with a full-blown linux terminal.
[Samsung Galaxy Nexus] J-Hop2o6:
Sorry, but what does it do? All I get from the description is "binaries" and "paths". Not sure what it all means, lol.
[Samsung Galaxy Nexus] franciscofranco:
I really don't know what to say... Its a set of binaries mostly created by GNU. Most of them are useless for daily use, others are just legacy ****.
[Samsung Galaxy Nexus] J-Hop2o6:
Haha thx.
[Samsung Galaxy Nexus] datsyuk:
I noticed in nightly #10 the first opening of the app drawer lags a bit every once in a while unlike it did in #9.2. What ROMs are you guys running with the kernel and are you guys doing anything special after flashing the kernel (Governors, programs, tweaks)?
[Samsung Galaxy Nexus] rsantana:
kernel 10

I know this is a stupid question but I read earlier on another forum a cache wipe isn't required. I'd like to get it straight from source, should I do a cache or Dalvik cache wipe, both, or none? Thx for any support.
[Samsung Galaxy Nexus] jan-willem3:
Don't have that problem only thing I noticed is that my wifi speeds are really low somehow and this wasnt on the stock rom. When I am infront of the router I get 950 kb per sec while with stock this was something like 1.7 mb per sec. Data speeds are really good actually. Checked dsmeg and logcat didnt saw something intresting this issues are always hard to catch it can be a config changes or something else who knows.
[Samsung Galaxy Nexus] bebolf:
Need some help here..

I put a script in init.d folder to enable hotplug on boot but it's not working :confused:

#!/system/bin/sh

echo 1 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled
[Samsung Galaxy Nexus] franciscofranco:
I tuned some tcp settings in the boot.img, maybe its that.

Isn't working? It is for me. You didn't give me any aditional information so I can't help you more than asking if you set the correct permissions.
[Samsung Galaxy Nexus] jan-willem3:
I tried exactly the same also in this form. But didnt make a difference maybe I need to create the file on the pc dont have a clue.

echo "1" > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled
[Samsung Galaxy Nexus] bebolf:
I've even set the permission to 777 just to be sure. I'm running nightly #10 and AOKP 14.

No other scripts are in init.d

Edit:

What I did..

- put script in /system/etc/init.d/ with 777 permission

- reboot the phone

- go to /sys/module/omap2plus_cpufreq/parameters/ with root explorer and check the value in "hotplug_enabled"

- can't seem to set it to "1" after a fresh reboot

Let me know if I'm missing any detail :P
[Samsung Galaxy Nexus] franciscofranco:
So as far as I can understand /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled ain't changing even with the init.d script right?