yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] countryfolk07:
I've had this to on the Google keyboard. I'm on 4.3.1 though, so this may be a keyboard issue, IDK, just a thought. I am using dkp though so that is also a common factor. What governor and speeds are you using? I'm on freelunch, under clocked to 1350. Stock voltages. SIO scheduler.
[Verizon Samsung Galaxy S III] thelangosta:
I'm on freelunch/row with the cpu at 1458 and whatever voltages the kernel comes set to. Actually now that I think about it my phone might have been plugged in last night when I noticed the keyboard thing. For some reason it is not nearly as smooth/responsive while plugged in.

Sent from my Transformer TF101
[Verizon Samsung Galaxy S III] countryfolk07:
I notice this also! LOL.
[Verizon Samsung Galaxy S III] decimalman:
As long as I'm playing with the LEDs instead of doing anything productive, there's a new AOSP 4.4 test build on the way.

The new softkey backlight settings can be changed in /sys/kernel/dkp for now. Eventually, I'll try to get Trickster to show settings for them.

Changelog:

Animated the on/off transition on the softkey backlights. It's glorious. :D

Added customizable brightness for the softkey backlights

Changed how a few things come out of standby

Fixed a few small issues in the graphics drivers
[Verizon Samsung Galaxy S III] beepea206:
Flashed the 12/15 build and all is well. :)
[Verizon Samsung Galaxy S III] Mystique:
Anything that you think might benefit the 4.1.2 TW build? ;)
[Verizon Samsung Galaxy S III] countryfolk07:
I flashed on 1.7 SlimKat and lost my IMEI. Grrr. First time that's ever happened. I tried to restore using my NVBackup and went into a bootloop. [MENTION=4968667]BeePea[/MENTION]206, what did you flash this on?
[Verizon Samsung Galaxy S III] xSharpi:
Any recommended settings for TricksterMod with this kernel?
[Verizon Samsung Galaxy S III] decimalman:
New TW 4.3 test builds are on their way! I fixed most of the problems I've been hearing about. Dead Trigger 2 still doesn't work, so there's probably still a couple bugs left in the video drivers.

Changelog:

Added a fancy blacklist that prevents thermald and mpdecision from modifying your min/max frequency when they shouldn't.

Fixed up some CPU power management stuff. mpdecision should stop whining and do its job.

Added fancy animations for the notification LED and softkey backlights.
[Verizon Samsung Galaxy S III] beepea206:
Aww, that sucks, man. I'm on the 12/13 build of Gummy.

SlimKat... man, I want to like that rom, but I have data issues and the nightlies are just brutal with issues. I had issues with custom kernels and reboots on that rom. Gummy 12/8 and 12/13 are the most stable for me... 12/15 has some commits I'm not too keen on that might get reversed.
[Verizon Samsung Galaxy S III] decimalman:
New TW 4.3 and AOSP 4.4 test builds are up! Bugfixes all around.

TW changelog:

Softkey backlight settings actually work

Fixed a silly bug in the rotator driver

AOSP changelog:

Cleaned up the softkey animation code and fixed a small glitch

Cleaned up the notification LED animations

Fixed a silly bug in the rotator driver
[Verizon Samsung Galaxy S III] decimalman:
Four new test builds are going up (AOSP 4.3 & 4.4, TW 4.1 & 4.3). Clearly, I've lost my mind. :p The new builds should fix the sleep of death bug and the strange softkey behavior. The notification LED and softkey backlights are a bit wonky on TW, but they shouldn't be severely broken. If there's still any major bugs, let me know.

Changelogs:

AOSP 4.4:

Synced up with CM

Fixed a few bugs in the suspend/resume code

Adjusted the softkey animation a little bit

AOSP 4.3:

Added notification LED and softkey backlight animation

Reduced UKSM's default aggressiveness

Optimized and stripped a few drivers

New toolchain, cleaned up compiler optimizations

TW 4.3:

Fixed a few bugs in the suspend/resume code

By request, brightened the notification LED (makes the animation smoother too!)

Adjusted the softkey animation a little bit

TW 4.1:

Added notification LED and softkey backlight animation

Fixed up the frequency control interface and fixed a bunch of bugs

Enabled a few extra TCP congestion control algorithms

Reduced UKSM's default aggressiveness

Optimized and stripped a few drivers

Patched in and switched to XZ compression

Removed a ton of bogus stuff

Fixed a zillion compiler warnings and a few obvious bugs

New toolchain, cleaned up compiler optimizations
[Verizon Samsung Galaxy S III] countryfolk07:
Is there any weird date thing I should be aware of on the 4.3 version? Running Carbon 11/17. Thanks. I just know here lately there's a lot of don't flash this after this date, etc. LOL.
[Verizon Samsung Galaxy S III] decimalman:
I didn't check for updates from CM, so if the previous build is working, the new one should, too.
[Verizon Samsung Galaxy S III] countryfolk07:
I LOVE what you did with the backlight and LED animations. Decided to finally jump to 4.4. Loving it! Thank you for the great kernel decimalman!
[Verizon Samsung Galaxy S III] TotallyAnxious:
The 12/21 build for 4.4 is the most stable kernel I've had since switching to 4.4+. 0 reboots (been using for 2 days), almost zero lag. Great job!
[Verizon Samsung Galaxy S III] Mystique:
Thank you for the expanded selection of congestion controls..

net.ipv4.tcp_available_congestion_control = cubic reno bic westwood vegas veno illinois

If I could suggest TCP_CONG_YEAH..

Not that my 3G/4G link gets congestion but the way that YEAH handles long fat networks.. (imho) I find works well for VZW and wifi..

(congestion algorithms whitepapers are interesting to some people..)

linux seems to always default to cubic, which is decent for wired (copper/fiber)..

M$ used to have ctcp as an option all the way into server 2008r2, but ctcp is no longer available in win8/2012

2012 Servers use DCTCP by default. Client computers use NewReno. For information about NewReno, see RFC 3782 (http://www.ietf.org/rfc/rfc3782.txt).

Data Center TCP adjusts the TCP window based on network congestion feedback based on Explicit Congestion Notification (ECN) signaling. DCTCP may improve throughput on low latency links.

Which again ecn is great for wired, not so much for wireless..

I would hardly consider 3G/4G (and many wifi cases) low latency links.. (ymmv) RTT and queuing and all..

Abstract—In recent years, several new TCP congestion control

algorithms have been proposed to improve TCP performance

over very fast, long-distance networks. High bandwidth delay

products require more aggressive window adaptation rules, yet

maintaining the ability of controlling router buffer congestion.

We define a relatively simple experimental scenario to compare

most current high speed TCP proposals under many metrics:

efficiency, internal fairness, friendliness to Reno, induced network

stress, robustness to random losses. Based on the gained insight,

we define Yet Another High-speed TCP, as a heuristic attempt

to strike a balance among different opposite requirements.

Index Terms—High Bandwidth-Delay Product Network, TCP.

All this being said.. (If I had a cyanogen device..) I would see what their stock kernel is pushing these days

Last I remember they were a 'veno' advocate..

[some init script..]

busybox echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control

Thanks for reading and thanks for the kernel update with the mods.. ;)

Confirmation number: 27C241939C4894937.

Is this anything?

E/lights ( 727): write_int failed to open /sys/class/leds/keyboard-backlight/brightness
[Verizon Samsung Galaxy S III] omair2005:
Yeah same here! Are you using default settings?
[Verizon Samsung Galaxy S III] Mystique:
E/MP-Decision( 1495): CPU[1] has been hotplugged outside MP-Decision.

E/MP-Decision( 1495): MP-Decision will be stalled until enabled.

E/MP-Decision( 1495): Enabling MP decision for CPU[1]

(again TW 41)

Started seeing these on the 12-21..

Using CPU Tweaker from 3c..
[Verizon Samsung Galaxy S III] TotallyAnxious:
I use freelunch and cfq. Everything else is default. What about you?
[Verizon Samsung Galaxy S III] countryfolk07:
[MENTION=4932679]decimalman[/MENTION], is there a way to lower the brightness of the menu and back keys without compiling a kernel? Is there something in one of the directories you mentioned I can just change? Thanks for any info.
[Verizon Samsung Galaxy S III] decimalman:
If you're on the 12/21 build, take a look at /sys/class/sec/sec_touchkey/touchkey_brightness_level.
[Verizon Samsung Galaxy S III] bmeek:
I tried this kernel with a recent cm11 nightly, but the ROM's settings menu option to turn off the function key backlight was ignored. I'll need to reflash and get a look

I usually keep the function key backlight off, since I don't want it flashing on for n seconds every time I touch the screen... I would like the keys to light up for a few seconds when I touch one of the function keys, but not the screen.

Does your configuration file allow for this?
[Verizon Samsung Galaxy S III] omair2005:
I was using default settings
[Verizon Samsung Galaxy S III] decimalman:
Changing the number in the file I mentioned to 0 will disable the backlights, but won't stick after a reboot. Currently, there's no way to change what triggers the backlights. The ROM controls when the backlights turn on/off, so it would be much easier to change it there, instead of in the kernel.

The code really wasn't designed to support animation, and it misbehaves in a bunch of bizarre ways when the on/off transition isn't instant. The most obvious symptoms of this is the lights ignoring the ROM's setting, but there's a few more subtle bugs as well.

mpdecision does that when something turns on the second core. Usually, it's a tuner app turning it on to apply new settings or read the old ones. I think mpdecision even whines about this when it's frozen, but it shouldn't do any harm.

Incidentally, if mpdecision stops working (e.g. an app turns on core 2 and never turns it back off), auto-hotplug should take over after a few seconds.

I tested a bunch of different algs a while back, hoping that YeAH or Hybla would perform substantially better than cubic. They did, but IIRC Westwood outperformed them both (on Sprint 3G anyway). Extra algs don't take up much space, so I'll enable YeAH in the next build.

I don't think that file has ever existed, so I'm not sure why anything is trying to write to it. If everything is working, I wouldn't worry about it.

Thanks for the donation! :good:
[Verizon Samsung Galaxy S III] beepea206:
I think that might shore up the wifi/Lte issues some have with the cm kernel in custom roms. I'd love to test and see if I still have congestion with slimkat like I did.
[Verizon Samsung Galaxy S III] omair2005:
so far the best kernel for 4.4.x! thanks for this!
[Verizon Samsung Galaxy S III] countryfolk07:
I concur! Great work decimalman. Thanks.
[Verizon Samsung Galaxy S III] decimalman:
New test builds are up for all four active versions. I haven't made any dramatic changes, but the softkey backlights should behave much better now. If they're still acting funny, let me know.

Changelog:

Fixed the softkey backlights again

By request, enabled TCP YeAH
[Verizon Samsung Galaxy S III] Mystique:
Boots and running.. tw41..
[Verizon Samsung Galaxy S III] TotallyAnxious:
The soft key backlights turns on and works fine when you turn the phone on with the home button but turns on and immediately off when using the power button. Doesn't bother me at all but thought I'd let you know. I'm on 4.4.2.
[Verizon Samsung Galaxy S III] Mystique:
Yeah congestion working out great..

I do have to recommend that if you have never tried the asswax governor, you need to.

My wife got a nexus 7 and I found that the custom kernel for that has a fiops scheduler..

From what I could find that would also be able to be used on our device as well..

Can I put in a suggestion for that scheduler?

Although zen and deadline seem to be great as well..

Thank you again for your work..
[Verizon Samsung Galaxy S III] jdog94:
so will this work ok with [TW 4.3]VRUCML1_Stock_Root_Deodex (12.31.13
[Verizon Samsung Galaxy S III] lexluthor:
Isn't that file packaged with this kernel by default? When you install that file, this kernel will automatically be used as far as I can tell.
[Verizon Samsung Galaxy S III] TotallyAnxious:
So when I reboot my phone it gets stuck at the kernel logo, if I pull the battery the same thing happens. It occasionally works to a full boot and runs fine. However I've noticed not having my sd card (64gb from samsung if that matters) in makes my phone boot fine every time. Since it gets stuck on the kernel boot logo thingy I figured it was kernel related. Anyone have any ideas why this happens? I'm on the 12/21 4.4 build.
[Verizon Samsung Galaxy S III] kurtazz:
Sorry for the stupid question in advance. The TW 3.4 Verizon mentioned a rotate fix. Is there anyway I can reflash if I did the ota update? My problem posted here http://xdaforums.com/showthread.php?t=2586036 indicates Im hosed until the unlocked is "fixed".
[Verizon Samsung Galaxy S III] decimalman:
Last night, I finally got old&slow a dkp boot.img to package into his ROM. I think dkp is the default for the time being.

If you run "pgrep mount.exfat" in a terminal emulator, does it display anything? If ROMs aren't using in-kernel exFAT, disabling it should fix the hangs. I'm also not using the same exFAT code as CM (they use the leaked and not-entirely-GPL code which I refuse to touch), so that might be further complicating things.

I'm on Sprint and don't really keep up with other carriers' updates. As far as I know, you're stuck with a locked bootloader and all the misery that it entails. :(

I'll take a look at the sensor thing. It's possible that there's a fix, and you provided a lot of info in the post you linked. :good:
[Verizon Samsung Galaxy S III] TotallyAnxious:
I ran "pgrep mount.exfat" and nothing was displayed. So I'm not sure if I need to disable something or not. It's not a huge issue for me, just a little annoying pulling the battery and card out every time I need to reboot (which isn't that often).
[Verizon Samsung Galaxy S III] decimalman:
Nope, I was just hoping there was an easy fix on my end. Since nothing was displayed, in-kernel exFAT is probably being used, so I shouldn't disable it.

I'll take a look through the exFAT code for anything that could be causing problems.
[Verizon Samsung Galaxy S III] golfslicer:
moved
[Verizon Samsung Galaxy S III] decimalman:
[MENTION=2036424]golfslicer[/MENTION]: Try the Themes and Apps forum

Any chance this build helps? It fixes an issue that was too obvious to actually be the problem.
[Verizon Samsung Galaxy S III] TotallyAnxious:
2 consecutive normal reboots. I think you fixed it.
[Verizon Samsung Galaxy S III] MrBrady:
Would this enable ExFat support for oldandslow's TW 4.3 VZW build?

Thanks!
[Verizon Samsung Galaxy S III] prdog1:
The kernel in it supports exfat. Works fine on mine with TWRP. If using CWM that is the problem with exfat. :cool:
[Verizon Samsung Galaxy S III] TotallyAnxious:
The phone still gets stuck at the kernel logo, it happens less frequently though, so whatever you did helped.
[Verizon Samsung Galaxy S III] lexluthor:
I'm using this kernel as it's packaged with this GS3 TW 4.3 ROM

http://xdaforums.com/showthread.php?t=2591895

The kernel feature notes indicate a feature called "fast charge without unplugging". What exactly is that and how do we use it?

Also, what are the "Glorious LED animations" that are listed as another feature?
[Verizon Samsung Galaxy S III] TotallyAnxious:
Fast charge is a feature to help make car chargers to work faster. You'll need to download an app that allows you to turn fast charge on and off. Most of the time you need to unplug and replug when toggling fast charge. Feel free to correct me if I'm wrong.
[Verizon Samsung Galaxy S III] BrokenWish:
[MENTION=5377398]JennyLikesSka[/MENTION] with dkp u dont have to unplug b4 u turn on fast charge but yes most kernels u do
[Verizon Samsung Galaxy S III] beepea206:
TricksterMod (https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod) is my go-to.
[Verizon Samsung Galaxy S III] mandiw777:
/sys/kernel/fast_charge/force_fast_charge

1 is on

0 is off

I run a script that enables fast charge at boot.
[Verizon Samsung Galaxy S III] decimalman:
I knew it was too easy to be the whole problem.

Looks like fast charge has been covered pretty well. The LED animations refer to the animation of the notification LED blinking and the softkey lights turning on/off. The lack of animations always felt out of place on an otherwise slick phone, so when I figured out how to animate them, I was pretty excited (hence "glorious" :p).
[Verizon Samsung Galaxy S III] mandiw777:
I am using xposed to fade my nav bar buttons and have the capacitive lights timed perfectly so they fade at the same time pretty slick. I also turn the brightness of the capacitive buttons down to about 40 so I can't see them in the light but aren't too bright in the dark. Thanks Decimalman! Freakin awesome!
[Verizon Samsung Galaxy S III] TotallyAnxious:
Take your time with fixing it. It's not a huge deal for me. But I do appreciate you taking your time to fix it!

And is that why the led on my phone seems so much smoother than usual?
[Verizon Samsung Galaxy S III] lexluthor:
Appreciate the reply, but I'm still not getting what you are saying. What do you mean animation of the notification LED blinking? The notification lights up when I have a notification. Other that that, what animation is it doing? I'm using Lightflow and I can control the length and frequency of the blinking for each app with that.
[Verizon Samsung Galaxy S III] decimalman:
I should make the animation length adjustable. Of course, the timing in the existing code is embarrassingly inaccurate (off by 20-30%, at least), so I'd have to rewrite it.

No problem.

It surprises me that it's so problematic, since it's almost exactly the same code that Samsung is using on TW. Oh well, stranger things have happened.

From what I gather, Lightflow doesn't use the standard blink or pattern interfaces, so the animation won't work. Without Lightflow, the LED smoothly transitions on/off instead of blinking.
[Verizon Samsung Galaxy S III] Mystique:
decimalman..

tcp veno for the win..

Using ten or so people at work.. For the past few days..

They all noticed when veno was the default and could tell when it was removed..
[Verizon Samsung Galaxy S III] decimalman:
New AOSP 4.4 test build is on its way. It's in the "d2" directory since all variants now use the same kernel on AOSP 4.4.

Changelog:

Merged a zillion commits from CM, including a fix for the freezes during boot, updated wifi driver, and a huge CAF update

Linux 3.4.77

By request, added FIOPS I/O scheduler

Tons of UKSM optimizations and improvements: dramatically faster scanning routines (something like 3-5x faster), much improved CPU limitation, less intrusive scheduling, better compatibility with Performance Control, new default tuning

Optimizations in the wifi driver, including much more sensible wakelock behavior

Modified the notification LED animation slightly

A few small bugfixes and one big bugfix for the updated wifi driver

Disabled in-kernel exFAT (AFAICT, all AOSP ROMs are currently using exfat-fuse, so in-kernel exFAT isn't needed)

EDIT: Looks like wifi is causing runaway wakelocks. I'd suggest waiting for a fixed build.
[Verizon Samsung Galaxy S III] decimalman:
As much as I've enjoyed working on the newly broken alarmtimer code from CM, I've decided to revert it. New AOSP 4.4 test build is up. It's actually getting (and correctly reporting) deep sleep, and should also correctly update system time/date.

EDIT: I'm dumb and didn't enable the new alarm driver.

Changelog:

Reverted the recent alarmtimer commits from CM

Fixed the berserk wifi wakelock

Prevented CM from slowing UKSM down to a crawl
[Verizon Samsung Galaxy S III] countryfolk07:
Thank you decimalman. I was wondering what was going on with the system time. I had just switched to ART when I flashed the 1/22 build and thought that had maybe done something. I love your kernel. Simple, yet effective. The little tweaks make it nice too. Like the notification light animation and such. Thanks again.
[Verizon Samsung Galaxy S III] OMG_VTEC:
what exactly is the system time thing? i feel like ive had issues where the clock didnt update a few times unless i rebooted but im on tw.(beans 20)

is it an issue that far back or is it just a kitkat thing?
[Verizon Samsung Galaxy S III] decimalman:
It's just a KitKat thing. CM made some changes to the system timekeeping, and it's causing problems for some people.
[Verizon Samsung Galaxy S III] TotallyAnxious:
The latest release fixed all my boot issues. Thanks!

Also, would it be possible to add the sioplus scheduler? I use sio now and sioplus obviously sounds like it would be an improved version. I've tried to find some info on it for you but this all I could find, http://xdaforums.com/showpost.php?p=41436011 BMS added it and from when I used to use bms, I liked it (freelunch is the main reason I switched). Anyways thanks again for the latest build.

The new led animations are fantastic btw.
[Verizon Samsung Galaxy S III] decimalman:
TW is finally getting an (untested) update. 4.3 is going up now, and 4.1 will follow shortly.

Changelog:

Lots of improvements to UKSM: less disruptive behavior, much more efficient scanning, etc.

A few optimizations to the wifi driver

By request, added sioplus. fiops needs some extra work to work on Linux 3.0, so it's not included yet.

A few small bugfixes

EDIT: JennyLikesSka: sioplus is already merged into AOSP. The next AOSP build will include it. I'm not sure how differently it behaves from sio, but the link you posted is accurate.
[Verizon Samsung Galaxy S III] Mystique:
On TW 4.1.2 I am zen/1024 Zram enabled asswax/54/1350 included UV and of course veno/congestion.. Incredible battery life and very responsive

Thank you for your time and efforts.. Greatly appreciated.

4.1.2 test build available now..

For those running the latest Philz with the update-binary issue.. The build includes a working binary.. So no manipulation is required.

Booted up just fine no issues so far..

Does anyone know how to enable zram from an init script?

I currently use trickster simply for the zram and cpu tweaker for the governor and scheduler.
[Verizon Samsung Galaxy S III] Interflop:
I love this kernel but I have one issue. I'm running a TW4.1.2 based ROM (JellyBeans R20). Streaming audio over my car's radio through Bluetooth produces some relatively loud crackling noises. Flashing Lean Kernel eliminates the problem so I assume it's a kernel issue I'm having.

Any ideas what could be causing this?
[Verizon Samsung Galaxy S III] vmancini3:
I believe by default on this kernel the voltages are already lowered....you could try to start raising them little by little until the crackling stops....IIRC, LeanKernel by default, uses the stock voltages across the board, 1150mv.
[Verizon Samsung Galaxy S III] TotallyAnxious:
There is a zip in the 1st/2nd post that restores the voltages to stock. I think dkp is lowered 50 by default. Here's the link from the post http://d-h.st/4iK
[Verizon Samsung Galaxy S III] Mystique:
My daughter just had an accident and totaled the wife's car.. Insurance company got us a rental till all that is cleared up.. Kia Optima hybrid which has bluetooth powered by a Microsoft system..

Running a hybrid bonestock rom and latest dkp.. No bluetooth problems with streaming audio. Phone and music all play loud and clear.. #first-bluetooth
[Verizon Samsung Galaxy S III] lieffring:
Has anyone had a problem with your phone locking up when your screen sleeping? Because I've been getting it a few times a day what could this be from?
[Verizon Samsung Galaxy S III] beepea206:
That's generally from your voltage being too low. Increase by 25 and you should be good.
[Verizon Samsung Galaxy S III] Mystique:
Anyone else check their entropy? Mine seems to dwindle down a little each day.. (feels like a memory leak..) and a clearing of all running apps does not seems to fix it. Reboot however, does..