yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] mkasick:
Would you folks mind making two kernel configuration changes?

First, to enable /proc/config.gz support (CONFIG_IKCONFIG=y, CONFIG_IKCONFIG_PROC=y), and second, to compile TCPMSS support into the kernel (as opposed to a module, CONFIG_NETFILTER_XT_TARGET_TCPMSS=y). If you do, you can also remove the xt_TCPMSS.ko module from the initramfs and the insmod call for it in init.rc.

Attached is a patch against defconfig that does this. I've been running with TCPMSS support built-in (which it was in DI18) for a week and haven't had any issues. I'm not sure why Samsung even changed it.

I ask because, WiFi Tether v3.0-pre5+ includes support for MSS clamping, but the option to enable it only appears if it sees CONFIG_NETFILTER_XT_TARGET_TCPMSS=y in /proc/config.gz. If it does, then an "MSS clamping" option appears under "LAN" in the WiFi Tether Settings menu.

I've been encouraging MSS clamping support for a little while now as a precautionary measure. However, in the past week folks have been reporting trouble with WiMAX tethering in certain (typically recently-deployed) markets, where it appears that fragmented packets are dropped by the network.

The common symptom is that tethering works fine on 3G, but on WiMAX most pages don't work. Google sites typically do, but this is expected as Google sites are often not very data heavy and tend not to result in packet fragmentation. It's confirmed that there's an MTU mismatch, and in one case it's confirmed that MSS clamping resolves the issue. Hence the issue is a bit more pressing than it was previously.

As a bonus, this means that SyndicateROM Frozen can boast having better WiMAX tethering support than the official Hotspot client.
[Epic 4G Android Development] BeerChameleon:
Will this help the reboot issues that wifi tethering 3.0 versions has as well? That would be sweet.. :D
[Epic 4G Android Development] mkasick:
Unfortunately I don't think it will have any affect on that problem.
[Epic 4G Android Development] BeerChameleon:
Damn!! Do u have any mad skills to figure out whats causing that issue, i mean you have been so helpful with all your fixes. ;)
[Epic 4G Android Development] yogi2010:
Have you guys noticed your wifi signal dropping out a lot? I will see the wifi icon dissappearing, then coming back, dissappearing, etc. And it happens even when I have full

Signal and am sitting right next to the router. Does the setting for Static IP have anything to do with it? Just wondering if anyone else is noticing this.
[Epic 4G Android Development] musclehead84:
Ive noticed this as well.

Sent From My Evo Killer!
[Epic 4G Android Development] churro7:
Considering before the kernel I was on genocide. 3 and I had no problem then

Sent from XDA app with 2.2 powered Epic 4g
[Epic 4G Android Development] caspertodd:
I actually had this same problem on Genocide. So really, it probably isn't the kernel. Try turning on debugging on your phone, plug in your phone, unplug it and turn off debugging. Then try it again. This worked for me.
[Epic 4G Android Development] DevalB:
Has anyone else had a problem flashing SetCPU using this kernel? I get an error through CWM3.
[Epic 4G Android Development] Rodderik:
setcpu is an application (apk file)....you install it...not flash it
[Epic 4G Android Development] DevalB:
Yep...that just dawned on me...this is what happens when you're at work and try to do 10 things at once.
[Epic 4G Android Development] chris41g:
The battery charging when off people keep sayin is a cwm3 problem but it only happens with this kernel..
[Epic 4G Android Development] churro7:
Just to be clear when plugging into USB port on PC the prompt asking mass storage or charging does not appear nor does it appear on pc

Sent from XDA app with 2.2 powered Epic 4g
[Epic 4G Android Development] insanity213:
I had that issue intermittently as well. I didn't really test much, I just went back to my old kernel. Depending on your ROM, you may lose root if you flash a different kernel, just run the CWM one click again and root will be restored.

Like I said, I didn't test much or debug anything at all, so I'm not sure if the ROM or kernel was to blame, but my ROM seems to play well with kernels I built off of the Genocide source.
[Epic 4G Android Development] mkasick:
Also, here's a new version of the RNDIS/ADB bug fix patch. Attached is a diff against Twilight commit 788fbc5, as well as a diff against EB13 stock if you prefer that. Here's the changes against the old version:

Use USBSTATUS_VTP instead of USBSTATUS_RNDIS: In DI18 it was unclear what Samsung's intention for USBSTATUS_VTP was, so I added a new RNDIS mode. In EB13 Samsung uses VTP for tethering, so this patch does as well. This way things like the USB indicator icon work as intended.

Remove "rndis_enable" sysfs switch: Samsung implemented their own "tethering" switch which Wired Tether now uses, making the old switch redundant. The latest Wired Tether release doesn't check for it anymore.

Remove "oldusbstatus": The core of the fix is the same as before, get out of VTP (RNDIS) mode using the same protocol as ADB, switch to "UMS" mode and check if the gadget driver was really in a different mode previously. This removes the only use of "oldusbstatus", so the variable is removed entirely.

Also, "currentusbstatus" is kept as elsewhere the driver checks it to see if it's in UMS, ADB, and VTP modes to set the USB indicator icon and tethering debugging statements accordingly.
[Epic 4G Android Development] tanimn:
While I was building and testing this kernel I was on rfs with a stock rom and never once had the battery full freeze bug. I did not have the redirector installed with cwm 2.5.1.0.

Once I installed cwm 3.0.0.6 with the redirector, the VERY NEXT POWERCYCLE I got hit with the bug. It's been catching me now and again ever since. I'm planning to reload the rom tonight and see if the bug goes away, confirming it's the redirector and not cwm3 itself.
[Epic 4G Android Development] tanimn:
Thanks mkasick. It's adjusted and ready for the next build. :)
[Epic 4G Android Development] Aluminous:
Just flashed! I'm looking forward to 1.3ghz (1.4?) in the future. On my Palm Pre, before the Epic launched, I had a kernel with the ability to set custom voltages in real time, which was great because I was lucky enough to have a particularly undervolt-able CPU. :D Any chance of seeing support for something like this with this kernel?
[Epic 4G Android Development] snowmanwithahat:
I searched but couldn't find any info in this thread...

Is it undervolted at more than just 1ghz? or is it only occuring at the 1ghz step so far?
[Epic 4G Android Development] k0nane:
1.0ghz is undervolted, and 1.2ghz is stock 1.0ghz voltage.
[Epic 4G Android Development] snowmanwithahat:
Are there any plans in future releases to undervolt other steps such as the 200mhz, 400 and 800mhz steps?

I'd be willing to test if there's a lack of testers. I realize from my cpu overclocking experience that this is goin to be a game of testing stability and it's very tedious, I'm willing to help if you guys plan on doing this and need more testers
[Epic 4G Android Development] hazridi:
What about voodoo audio support?
[Epic 4G Android Development] blu9987:
I dunno if its the kernel but i have a bug where it freezes while charging if the phone is off.
[Epic 4G Android Development] musclehead84:
Wow......how many more times is thus question gonna be asked or brought up. If you look like 20 posts up you would see that it was talked.

Sent From My Evo Killer!
[Epic 4G Android Development] odub303:
I am basically cross-posting this from my post in the Syndicate Frozen thread, where I haven't seen a response yet. Is anyone else having memory management issues (running Twilight Zone 1.0.1)? After the phone has been up and running for a while, it averages about 45-50 megs of free ram, which is normally fine. The problem is that Launcher Pro constantly restarts when I exit out of apps, even though I have the option enabled to keep it in memory. Other apps that should be staying alive in the background, such as Folder Organizer, also close and restart, resulting in delays in opening folders. Not sure whether this is unique to my setup, but I didn't have the problem on Stock EB13 with the same exact setup.
[Epic 4G Android Development] Dulanic:
/smacks self on head
[Epic 4G Android Development] Blankrubber:
I absolutely love this kernel so far. I haven't seen battery life close to this since the Phoenix kernel on Eclair, but to couple it with the speed it bring? Truly brilliant.

Is there a way to check the voltages in real-time similar to observing the clock frequency in SetCPU? I'm simply curious is all. Or, if you guys happen to know what the stock voltages are set to for each frequency, I'd appreciate that as well =). Thanks.
[Epic 4G Android Development] Toast95135:
I've been using Twilight Zone for a few days and:

- battery is quite good, and the on demand setting works very well (no occasional lag or stuttering) even clocked at 800.

- I get large checkerboarding when scrolling in the browser, I didn't have this on Genocide.

- it seems to run out of memory a lot, ADW EX and Beautiful Widgets restart when I go back to the homepage (mostly bw)
[Epic 4G Android Development] HeisRisen:
Tanimn, maybe we could update the OP with known bugs. That would stop people from having to read all the posts ... maybe even link to the solution if there is one and the original response within the thread that best describes the bugs.
[Epic 4G Android Development] MysteryEmotionz:
good idea but the problem is not everyone reads the op. They download, flash then ask questions
[Epic 4G Android Development] jirafabo:
When jumping into a new ROM or kernel, I always check the OP and first few posts, then the last 5 pages or so for known bugs and problems. Once the thread is over 15-20 pages, it's a bit much to be expected to read 100s of posts. Remember, not everyone chooses a ROM/Kernel from the beginning, and follows it throughout it's life cycle, so it's understandable when others aren't updated on all happenings, bugs, etc.

Anyhow, I think it should be common practice for the OP to keep an updated bugs list. I know it might scare some people away, but it's better than having to deal with them after they have it installed.

It's amazing how quickly the ACS ROM and kernel have exploded to thousands of posts. Obviously shows how popular ACS work has become. I myself had never tried it but was waiting for a 2.2 version to come out because I saw how popular the 2.1 version was.
[Epic 4G Android Development] odub303:
I am also having memory management issues. For me, it's Launcher Pro and Folder Organizer giving me the noticeable restarts, which causes major delays in navigation when returning to the home screen.
[Epic 4G Android Development] jirafabo:
Which governers are available in this kernel and which is reccommended?
[Epic 4G Android Development] musclehead84:
My apologies to you tanimn for doing that in your thread. Thank you for all your hard work.

Sent From My Evo Killer!
[Epic 4G Android Development] professoroak:
Got some beautiful battery life today at school and around town with this kernel. I'm actually using midNIGHT (BYOR) 4.1 and not Frozen, but it's still awesome. Simply running 100MHz-1.00GHz conservative, with 100MHz-400MHz conservative screen off.

After 14 and half hours since unplugging, still have 32% with fairly decent usage. A little over 2 hours of screen on, and I had 4G and GPS running during that time and a little bit more when it was off. Other than that, I turned off 3g, gps, and 4g when not in use.

Usually around this time I'd be running fairly low, maybe around 10-20% depending on heavier usage. Excellent kernel!
[Epic 4G Android Development] k0nane:
Glad you like it! :) Watch for more updates coming soon.
[Epic 4G Android Development] tanimn:
We're actively hunting this issue down now.

If you aren't desperate for an overclock, this interim kernel has been reported to resolve the issue. If you try it, please confirm or deny for me via PM. Thanks.
[Epic 4G Android Development] stir fry a lot:
I know running 1.2 will make the phone a bit snappier but is there anything that it can do that 1.0 can't? An example being if I am using a N64 emulator or maybe multitasking will it smooth anything out at all?

Great work by everyone involved btw.
[Epic 4G Android Development] burgerpimp07:
1.2?

You mean kernel 1.0.1? It unlocks 100MHz, in version 1.0 the lowest your cpu runs at is 200MHz, hence, saving you battery.
[Epic 4G Android Development] spitefulrain:
He means running 1.2ghz, not v1.2 of the kernel :p
[Epic 4G Android Development] spartanhooah:
I installed the Twilight Zone kernal today, but quadrant is still giving me the same benchmark score of ~750, as opposed to the claimed 1150+. I do have setcpu installed, 1200 max/100 min with ondemand scaling.

Another thing I've noticed is that when it boots, I get a sideways (i.e. landscape) android logo flashing on top of the Sprint and Galaxy S logos, and boot seems to take considerably longer than normal (and often gets stuck on the www.samsungmobile.com screen).

Relevant info:

Epic 4g

Froyo.EB13

Twilight Zone v1.0.1 - Hisako

CWM 2.5.1.0.
[Epic 4G Android Development] stir fry a lot:
I've gotten the landscape Android logo before as well even with CWM3 just for reference.

I also noticed that using the CPU Benchmark app that I am consistantly getting faster scores running it at 1ghz. Is this normal? I'd love to have it be underclocked and still be be faster that 1.2ghz.
[Epic 4G Android Development] k0nane:
Are you using the On Demand governor at 1.2ghz?
[Epic 4G Android Development] cheema:
Is there an easy way to get CIFS support for this kernel?
[Epic 4G Android Development] DCRocks:
This is caused by added support for boot animations.

The boot animation in the kernel (animated android) is playing along with the stock boot animation (sprint 4g animation).

You can delete the 3 files files of the stock animation, which will just leave the Android animation, or you can install a custom boot animation update, that removes the stock one, and installs a custom one.
[Epic 4G Android Development] camarojones:
Would these 3 files be the boot* files under /system/media?
[Epic 4G Android Development] k0nane:
bootsamsung.qml, bootsamsungloop.qml, bootani.qmg.
[Epic 4G Android Development] MeetFace:
While running this kernel, I was able to simply replace bootanimation.zip with one of my choosing, and all works well.

Hehe, the ACS boot animation reminded me of one of the old-school D.A.R.E. logos =]
[Epic 4G Android Development] gitit20:
I thought what I'd do was, I'd pretend I was one of those deaf-mutes...

I love it Ghost In The Shell Best Show ever... i know its off topic but had to say...
[Epic 4G Android Development] Rodderik:
this is untested but you can try this cifs module by "insmod cifs.ko" in terminal emulator or an adb shell

download: cifs.ko

the module is compiled from EB13 source with debug headers disabled (or else it would be 2.3MB instead of 320KB)

i'm not sure if there are some other things needed for cifs support but if it works for you then i'm sure k0name or some one can help you make an init.d script to insert the module on boot

if you try it and it doesn't work then let me know and we will get it working for you
[Epic 4G Android Development] GucciPilot:
This made the hardware keyboard unusable, very slow and laggy
[Epic 4G Android Development] bondosho:
Just an FYI: When clocked at 1.2ghz, the camcorder will record and then error out at somewhere between 20 seconds, and 4 minutes. If you want to do some recording, change it back down to 1ghz, and you can do a full 45 minutes.
[Epic 4G Android Development] camarojones:
It does this to me on the stock eb13/kernel, and also with this kernel at 1gHz.
[Epic 4G Android Development] black06c230:
can i use this on DI18?
[Epic 4G Android Development] Rodderik:
no update to EB13 first
[Epic 4G Android Development] bondosho:
Interesting. I was having all sorts of issues. At first I thought it was the ACS rom, so I restored back to Dameon's version of EB13, then I remembered I was overclocked. Switched to 1ghz, was able to record a 20 minute video.
[Epic 4G Android Development] MДЯCЦSДИT:
Title doesnt say 1.0.1 just to let you know
[Epic 4G Android Development] yogi2010:
hi Taninm, i imagine the new kernel will be posted here in this thread soon? can't wait to try it :D
[Epic 4G Android Development] jazzneel:
If I rooted my phone with the 2.5.5 rooting thing, can I still use this kernal? I have stock everything, but rooted with the above to get wifi tether. I didn't use the clockwork 3.0 thing.

Thanks!
[Epic 4G Android Development] camarojones:
Thanks k0nane! I renamed the files to *.qm_ and rebooted. It boots MUCH faster now!
[Epic 4G Android Development] tanimn:
New kernel

Version 1.0.3 is up and linked in the OP

Click Here if don't want to trudge all the way back to the first post. ;)
[Epic 4G Android Development] Jacoby6000:
Soo... what exactly was 1.0.2?
[Epic 4G Android Development] Gersonian:
Thanks for putting up 1.0.3. Every time I flash the kernel independent of a ROM (flash ROM then flash Kernel over it) it seems to eliminate the TWS bug. Not sure why, but it just does.

Thanks for a great kernel.
[Epic 4G Android Development] caspertodd:
With 1.0.3, should we be able to run at 100mhz on conservative in SetCPU?
[Epic 4G Android Development] tanimn:
The short answer: no.

My focus is up, not down. Idling at 100mhz instead of 200mhz saves you NOTHING, and in fact makes for a net loss over the course of a day. Have you ever tried to unlock your phone at 100mhz? Imagine how many extra hours of cpu idle time you could get in trade for all that screen time while you wait.

You can safely ignore that error, as long as it's just one of them.

The purpose of the 800mhz speed at boot is to force the cpu to back off during an intensive process. The origional kernel just stomped on the gas and popped the clutch straight up to 1.2ghz, which caused many handsets to fail to boot. Using the conservative governor is just a way to ensure the 800mhz tables are used until the system takes over the clock.
[Epic 4G Android Development] caspertodd:
Yeah, that makes sense. Just wanted to check. Thanks!!
[Epic 4G Android Development] iamchocho:
So is 1.0.3 what's included in ACS Frozen 1.0.1? Wondering if I flash this over that or if its already included. Assuming it is since my build shows TZ Frozen 1.0.3
[Epic 4G Android Development] jazzneel:
Anyone?? (10 char)
[Epic 4G Android Development] Gersonian:
As long as you are EB13 you should be able to flash this.
[Epic 4G Android Development] Gersonian:
1.0.3 is in use the FROZEN ROM. You do not need to flash this in addition to the ROM, but for some people, myself included, flashing just the kernel after flashing the ROM has provided some improvements.
[Epic 4G Android Development] ecooce:
So ondemand seems to be the best setting in setcpu now,in this mode it scales to 100mhz. This is a test I do when in setcpu; Change to conservative,now rub your finger in the bottom right of the screen,,,It should scale to 800 and 1000 (I dont OC atm) and it will scale to 200mhz at idle... Now change to ondemand,watch as you rub your finger in the bottom right area,it scales to maybe 400mhz and 100mhz at idle... Hope that helps someone.
[Epic 4G Android Development] burgerpimp07:
The download link on the main page is for v1.0.1 :x
[Epic 4G Android Development] burgerpimp07:
I never had any problem waking up from idle. When the kernel could run at 100MHz, it spent 70-90% of time in 100MHz without any setcpu profiles.

The only time I saw a slow wake was when I set a profile to run ONLY at 100MHz while screen was off.
[Epic 4G Android Development] readermo:
Hehe. Well, what can I say... I love the genocide kernel too. I just think the name is in poor taste. That's all. The devs on both kernels have done amazing work, and I'm grateful for them, however good or bad their choice of a name.

So, you see, I'm not a complete asshole. Partial asshole, sure. :P
[Epic 4G Android Development] chip!:
my phone didnt boot past the black samsung logo.

was on EB13 stock (samsung flasher)

wiped 3x (all), flashed SyndicateROM 1.0.1 and then flashed 1.0.3 kernel.

also tried various combinations, just flashing the rom, to no luck. just had to odin back to the beginning.

edit: do you have a version that is not overclocked & undervolted?
[Epic 4G Android Development] Coriolis3ffect:
This happened to me on my first flash. I just restored my nandroid backup, then reflashed the kernel... worked fine afterwards.
[Epic 4G Android Development] zman0900:
I am also missing the 100 step on conservative. With 1.0.1 I used to run a profile for screen off of 100-200 conservative. Never had any lag waking up and could even stream pandora with the screen off with no skips. My main screen on settings were 100-1000 conservative and it spent most off its time in 100, and more in the other steps below 1000. Phone was still very responsive.

Now with 1.0.3 I've had to switch to using on demand if I want to get down to 100, but that causes the phone to spend much more time at 1000, seeming to mostly ignore the middle options.

Could you please add the 100 step for conservative back in the next version? Even if its not on by default, it would be nice to have the option with setcpu.
[Epic 4G Android Development] stir fry a lot:
+3

>>>>>>>
[Epic 4G Android Development] ecooce:
Add me to that list,I agree 100%.
[Epic 4G Android Development] burgerpimp07:
To be honest, the link posted on the 1st post is 1.0.1 :)

I just downloaded that and flashed over SFR 1.0.1
[Epic 4G Android Development] camarojones:
The 1.0.3 is listed just above the 1.0.1

So far, nothing but good stuff with 1.0.3, but when will the keyboard fix be reapplied?
[Epic 4G Android Development] k0nane:
ASAP. tanimn and the team are working on some nice things for the next version.
[Epic 4G Android Development] formula84:
Ha, i thought i was crazy started to notice the missing keys again on sfr 1.0.1....guess i know why.
[Epic 4G Android Development] k0nane:
It is listed in the changelog. The updated toolchain brings a number of good things - but the fix will have to be tweaked!
[Epic 4G Android Development] camarojones:
Good stuff. One thing I noticed since .3 showed up, is that data connectivity is a little...touchy...when having a weak signal. Did the kernel have any changes to the radio interface?
[Epic 4G Android Development] Rivas123:
So how much can our cpus be undervolted? I wouldn't mind trying something crazy lol.
[Epic 4G Android Development] Anon9mouz:
Does any one make sbc kernels for epic?
[Epic 4G Android Development] algorhythm:
So is the keyboard fix no longer in the 1.0.3 kernel? I am looking to migrate over from Genocide 1.3 but only really for the keyboard fix...
[Epic 4G Android Development] razorseal:
is this compatible with the latest bonsai?
[Epic 4G Android Development] MysteryEmotionz:
Yes it is but not recommended
[Epic 4G Android Development] Anon9mouz:
I guess no one knows about sbc kernels for epic
[Epic 4G Android Development] k0nane:
It appears that consensus on SBC is "it's harmful". We're not interested in it.
[Epic 4G Android Development] MeetFace:
Good read on SBC kernels:

http://xdaforums.com/showthread.php?t=909763
[Xoom General] Pitnefor:
A lot of the games that use the gyroscope (or whatever it is), where you tilt the xoom and it makes the game turn left or right or something, is all jacked up for me on my xoom.

For example, the game Jet Car Stunts, I have to tilt the xoom up and down to turn left and right, instead of like my droid x where I tilt right and left (like it should be)

And the labyrinth game, if I tilt left, the ball goes right, and if I tilt right, the ball goes left.

Is this normal?!?
[Xoom General] Lars1967:
Try turning it over.:D
[Xoom General] Pitnefor:
its right side up already (camera at top) landscape
[Xoom General] Pitnefor:
its weird cause some racing games (like raging thunder) work fine
[Xoom General] Pitnefor:
i found a review where someone was having the same problem as me. kinda lameo
[Xoom General] muyoso:
Did you try calibrating the sensor?
[Xoom General] Pitnefor:
yea its wack