yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] jfcooley:
I bought trickster among others when I was on the gnex. I like the boot loop preventer and its fairly easy to use. Free, but worth the pro key.

(Always support apps you like. Will donate here of I ever get paid...)
[Sprint Samsung Galaxy S III] grifforama:
Newest nightly is without doubt the smoothest snappiest I've had my phone yet.

Many thanks for this. It's amazing. Trinity's colors are the bomb as well.
[Sprint Samsung Galaxy S III] decimalman:
I don't have a GNex, so I'm not entirely sure about the color controls it has. Trinity colors is a fixed adjustment that makes the S3's srceen "pop" a bit more. Some people like it, others think it looks too blue ("smurf-mode"). Give it a try and see what you think.

You need a vacation. Working the way you have been takes its toll after a while. Why aren't you getting paid for the 6-day weeks you've been doing? That's awful!

I like trickster too, and it's really easy to develop for, since I don't have to dig through smali to see where it's expecting to find a setting.
[Sprint Samsung Galaxy S III] jfcooley:
I get paid. I'll just leave it at that. Its OK though, maybe a dumb move but I gave notice.

Now, if I can find a ROM I like. PACman was fine, but I don't need all those different ui thingymabobs.

On Carbon and its...OK I guess. Wish the 3.4 ran on it.
[Sprint Samsung Galaxy S III] st0neski:
I installed this with the liquidsmooth 4.2.2 rom. Now it boots to the samsung logo but then shuts off. Is there anyway to fix that?
[Sprint Samsung Galaxy S III] ksmullins88:
Thank you for the input, it is greatly appreciated. I'll have to do a couple tests with them both. Would I see the differences in a speed test?

If you don't mind, which I/O scheduler do you use?

I ran some tests and,so far, found sio and fiops to perform the best on my device .

Also, any plans for a new release for 4.4.2??
[Sprint Samsung Galaxy S III] decimalman:
You'd mostly see a difference in upload speed, since congestion control doesn't directly affect download speeds.

I'm personally not fussy about I/O scheduler, so I usually stick to deadline or sio. I've been meaning to add fiops for a while now (someone on VZW requested it), but I've been busy working on UKSM instead.

I'm actually working on a new build right now. CM threw me for a loop with the new unified kernel (no more variant builds on AOSP :)), but I think I've got everything working again. Since you reminded me, I'm going to look into adding a few requested options while I'm at it.
[Sprint Samsung Galaxy S III] ksmullins88:
:D:D

That's what I like to hear!

If you need a tester shoot me a pm, I'd be honored to help.

Thanks man you rock:thumbup::beer:
[Sprint 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.

I started working on pegasusq since it was requested, but it's not going well. It's designed for old-fashioned SMP where multiple cores share the same governor instance, so it needs some modification to work optimally. There's a lot of things that need to be changed for it to behave the way it should.

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)
[Sprint Samsung Galaxy S III] ksmullins88:
Whoop!! Thanks for the update. works wonderfully!

Just a note: I had an issue when I dirty flashed the kernel on beanstalk. My clock wouldn't update in notifications or status bar.

Rebooted to recovery and installed kexec kernel cleaner and reflashed kernel then cleared cache and dalvik.

Edit: still not updating time. :/

Edit:Also trickster mod shows it isn't going into deep sleep.
[Sprint Samsung Galaxy S III] upconvert:
New build is running great! Thanks!
[Sprint Samsung Galaxy S III] meyerweb:
Do you have a link to the kexec kernel cleaner? I've searched a bit and haven't come across it.

Thanks. :)
[Sprint Samsung Galaxy S III] Mr. Struck:
http://xdaforums.com/showthread.php?t=1800576

It's in this thread for the KT747 kernel, scroll down past the available downloads in the OP to where it says "here is a script for fixing cache, dalvik-cache, and permissions."
[Sprint Samsung Galaxy S III] ksmullins88:
Anyone having those issues or is it me?
[Sprint Samsung Galaxy S III] MikeWjF:
No, not on slimkat.
[Sprint Samsung Galaxy S III] johnnytraveler:
I had the time issue. Went into time in the status bar settings. Turned it off/on, Now time Updates automatically

Sent from my Cromix TF700T tablet.
[Sprint Samsung Galaxy S III] upconvert:
My status bar clock went away, but I went in to settings and toggled the display clock setting. It has stuck around and updated normally since then. I am on the 1/20 build of kk Carbon.

Edit: I spoke too soon. Clock sync is a little messed up. I have to rotate to update time.
[Sprint Samsung Galaxy S III] MikeWjF:
Actually mine hasn't shown any deep sleep stats either now that I've checked.
[Sprint Samsung Galaxy S III] joeyddr:
same here no deep sleep and BBS says that the wireless is on and its not....
[Sprint Samsung Galaxy S III] MikeWjF:
I just rebooted and lost wifi for no apparent reason.
[Sprint Samsung Galaxy S III] marcran75:
I've been having stability issues with my WiFi for some time. Believe I mentioned it a while back and did not get a response. [MENTION=4932679]decimalman[/MENTION] ...are there any plans for updates for TW 4.3? Didn't want to but unfortunately I was forced to move to another kernel due to the WiFi problem.
[Sprint Samsung Galaxy S III] MikeWjF:
This is weird, I dirty flashed the rom to get back to the stock kernel and I still can't get WIFI working.
[Sprint Samsung Galaxy S III] enzoevo:
I've tried other kernels for tw, this one is the best for my phone. Every other gives me fits. Undervolted and underclocked stable as hell.
[Sprint Samsung Galaxy S III] MikeWjF:
Tried everything, the only thing that got WIFI back was doing a fresh install of the rom...
[Sprint Samsung Galaxy S III] remotehugger:
did you try your nandroid ?

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] MikeWjF:
Yeah, I was starting to worry. Dirty flash, nandroid etc. Nothing. I've never seen anything like that before.
[Sprint Samsung Galaxy S III] ksmullins88:
My clock is updating on fresh install but still no sleep. Maybe it's beanstalk related??
[Sprint Samsung Galaxy S III] sinisin:
Im having time issues on new kernel too. Its also breaking Google Play Services. Although I believe its related to the date/time issue. I've tried all fixes listed in the last 20-30 posts to no avail. Reflashed 12-26 and time is back to normal.
[Sprint Samsung Galaxy S III] decimalman:
Interesting. I haven't seen any reports of the clock acting up on other carriers. I don't think I touched anything that would affect it, but there's been a zillion commits from CM that touch a lot of stuff that could cause it. Thanks for reporting it. :good:

The deep sleep issue is a known problem. It's most likely an oversight in the new wakelock code in the wifi driver. I'll try to get a fixed build out later tonight.

I don't run TW, so it doesn't get as many updates. Your issue is on my radar, but the wifi driver is close to 90,000 lines of code, all of which is unfamiliar to me. I'm working on wrapping my head around it all (hence the commits while I play with the code), but it'll take a bit.
[Sprint Samsung Galaxy S III] wallythander:
I had all the issues listed above, time wouldn't update, at various points I lost data completely, Wifi and LTE. I tried reinstalling several times, dirty installing rom over my previous install and then install kernel, no dice. Clean install Rom, clean install kernel, also no dice. I repeated these once each, still no go. However, only with the dirty flash did I lose LTE. I never got the clock to update/receive from carrier properly, the year went to 1969. I use SlimKat. This is the one and only time I have had any issues with this kernel, thanks for your hard work Decimalman.
[Sprint Samsung Galaxy S III] decimalman:
Good news: I found and fixed some bugs in the wifi driver that are causing the runaway wakelocks. I might have also figured out what's keeping the clock from updating.

Bad news: Now that the wifi driver isn't preventing deep sleep, it looks like some of the recent updates from CM shook something loose and deep sleep isn't happening anyway. :mad:

Will someone flash this and let me know if the clock is updating again?

It's in the ramdisk (initlogo.rle if you're curious). The easiest way to get the stock logo back is to reflash your ROM (dirty works fine).

Thanks for reporting this. I'd like to get the wifi and clock stuff sorted out first since it's affecting so many people, but I'll see what I can do about this as soon as I get a chance.
[Sprint Samsung Galaxy S III] sinisin:
No. Still breaks time. On clean installs.
[Sprint Samsung Galaxy S III] wallythander:
I installed the 1/23 kernel, it seems like everything is working, all my radios are working again. The clock is right too. I am only 30 minutes in though, so maybe I haven't noticed something yet.

edit: the kernel defaults were odd, 540 min 540 max asswax governor.

Edit yet again: sometimes the clock stops updating, sometimes it shows the correct time.

Edit for the third time: Beautiful Widgets and the Dashclock lock screen clock keep the correct time. Just the status bar clock is wrong
[Sprint Samsung Galaxy S III] sinisin:
I reinstalled again after reading the last post. Still breaks my clock. On CM11 and I run Kernel Cleaner before and after.
[Sprint Samsung Galaxy S III] ksmullins88:
Newest build still not updating clock, also breaks net flix.
[Sprint Samsung Galaxy S III] decimalman:
Good news, then.

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
[Sprint Samsung Galaxy S III] ksmullins88:
Thank you!

PS, I really love your LED animations. No other kernel has them.

I'll be donating soon.

Edit: Half hour in and everything is working normally. She is sleeping, time is updating, Netflix works. Good job!!

Edit:: Scratch that part about sleeping. Still seems to not want to hit deep sleep. Its OK though. I'm still using.:thumbup:

Edit::: Figured out source of deep sleep deprivation. Had to do with build.prop of my ROM. She's sleeping over 90% now. All is perfect.
[Sprint Samsung Galaxy S III] MikeWjF:
Latest release running great, so far no wonky wifi shenanigans.
[Sprint Samsung Galaxy S III] joeyddr:
getting an error flashing the 1-23 test set_perm: some changes failed (status7) installation aborted.
[Sprint Samsung Galaxy S III] upconvert:
What recovery are you using?
[Sprint Samsung Galaxy S III] joeyddr:
latest philz touch
[Sprint Samsung Galaxy S III] marcran75:
Decided to revert to a buckup I have of CM 10.2 stable and thought I would try your kernel on it. Flashed numerous versions of aosp 4.3 and all of them got stuck at boot screen. Do I need to revert to MD4 for these to work?
[Sprint 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
[Sprint Samsung Galaxy S III] marcran75:
Smooth sailing so far. Much appreciated:thumbup:

Edit: Testing for the last hour and can definitely notice a difference. Seems much more responsive. The changes you made to the WiFi driver make a huge difference. Super snappy while gaming over WiFi.
[Sprint Samsung Galaxy S III] remotehugger:
man this kernel looks and sounds awesome - I wish someone running VM S3 TW 4.3 (MK5 build) could weigh in on if this works for them - I really want to try it but just not sure - I think someone has said it is compatible but can't remember - anyone with input would be extremely appreciated -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] marcran75:
I'm running MK3 on my VM GS3 but [MENTION=4932679]decimalman[/MENTION] has told me before that it is compatible with MK5 as well:good:
[Sprint Samsung Galaxy S III] remotehugger:
OK thanks - mite gonna have to give it a whirl - id use the spt/vmu one correct ??

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] marcran75:
Yessir
[Sprint Samsung Galaxy S III] ChoznJuan:
Could you share what you adjusted? I'm running Liquid Smooth and am noticing that my phone hasn't gone into deep sleep either.
[Sprint Samsung Galaxy S III] enzoevo:
Installed latest version for TW and phone promptly began behaving badly. I tried going back to previous, but continued with the behavior. FCs and spontaneous reboots.

I flashed vmin-enable. Flashed ramdisk. Didn't help.

If I flash stock kernel, everything is cool.

I've been setting voltages with Trickster. Left them at stock.

Prior to flashing the latest I was running 54-1512 at 800-1050 with no issues. Is it possible I wasn't really at 800-1050?

I am now running latest version, no ramdisk, 162-1512 850-1200. Can't get any lower with this or previous version dkp.

Any ideas on what may have changed? Maybe I wasn't really running that low to begin with? How can I verify?
[Sprint Samsung Galaxy S III] cbrox:
First off, thank you for your hard work and effort in providing us kernels for TW 4.3!

My setup is as follows:

D2SPR

Modem: MK3

Rom:Wicked 4.3 MK3 v0.4

Kernel: dkp-tw43-2014-01-26-testing

Recovery: PhilZ Touch v 6.07.9-d2spr

CPU APP: Trickster

Running smooth WiFi is working excellent.

The only issue i've found so far is that it will not deep sleep;

no matter what settings I use, even with the default kernel settings.

Cleared caches, re-installed several times, same result.

Thank you!

cbrox

Edit: re-installed dkp-tw43-2013-12-26-testing with default kernel settings and it deep sleeps fine with no issues.

But i'm gonna re-install dkp-tw43-2014-01-26-testing and stick with it. I like the smoothness and overall responsiveness and the wifi upgrades!

I can live without the deep sleep!
[Sprint Samsung Galaxy S III] zune70:
does this kernel have support for 128gb sd card? [MENTION=4932679]decimalman[/MENTION]
[Sprint Samsung Galaxy S III] tomcat1974@aol.com:
Does this kernel support custom boot animations/splash screens? I read somewhere those abilities may be kernel specific. Thanks.
[Sprint Samsung Galaxy S III] wyelkins:
Flashed newest version on Sunday. My battery life has been incredible ever since. No problems at all. I was running the one from December before that. I was running MOAR 7.1

Flashed MOAR 7.2b2 last night and then flashed the new DKP on top on of it for today.

Plan to try it with MOAR 8 tomorrow.
[Sprint Samsung Galaxy S III] marcran75:
After running latest update for 2 days my WiFi issues have returned. Keeps telling me I have no connection while WiFi is on.
[Sprint Samsung Galaxy S III] tlrsax54:
Installed latest few days ago, no issues whatsoever... I set free lunch through scripts so now all I do is flash and don't worry :) love this kernel.
[Sprint Samsung Galaxy S III] wyelkins:
Love this kernel. Running MOAR 8 with no issues. Got to do some more testing on Wifi. But, other than that, no issues at all.
[Sprint Samsung Galaxy S III] decimalman:
Jeez, this thread has been busy.

There was a couple crazy bugs in the 1/22 build that should have been fixed for 1/23. Are you getting a lot of wlan_wake, or just not getting deep sleep?

You have the absolute weirdest phone. :cyclops: Crazy problems with the ramdisks I posted a while back, and now this bizarre misbehavior. I'm stumped.

If you have a nandroid from before you flashed the latest dkp, you can restore it and check what voltages were actually applied. Using a root file manager, take a look at /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table and /sys/kernel/dkp/vmin. Any voltages lower than the number in vmin will be raised before they're applied.

The bug that I thought I fixed in AOSP doesn't seem fixed in the latest TW. You're not the only one having problems. It's probably related to the changes I made to the wifi driver, and shouldn't be terribly hard to fix. (I'm going to regret saying that, just watch.)

I still haven't figured out what's causing this. I haven't made any changes to the wifi driver that I would expect to cause problems (wakelocks aside).

Probably. The major problem with >32 GB SD cards is that they use exFAT instead of FAT32. The TW builds include an exFAT driver, and AOSP takes care of exFAT without a driver, so 128 GB cards should work fine.

Splash screens are supported regardless of kernel. All kernels (even stock) use the same file in the ramdisk. Since I don't touch the ramdisk, splash screens will even stay intact when flashing dkp.

Boot animations need either a modified ROM or modified ramdisk. Unlike other kernels, I don't touch the ramdisk, so I can't explicitly support boot animations. For TouchWiz 4.3, there's some modified ramdisks I made on my Dev-Host (you probably want the permissive one) that add support for boot animations and fix a small bug on older (i.e. non-KNOX) firmware.
[Sprint Samsung Galaxy S III] ChoznJuan:
It looks like OKJ doesn't play well with your kernel and was preventing deep sleep. I uninstalled OKJ and getting deep sleep again UC'ed to 54mHz UV'ed to 650. Hope to see impressive battery life
[Sprint Samsung Galaxy S III] enzoevo:
Looks like 950 is the lowest I can go after testing. I've tried flashing dkp-vmin-950.zip. It says it has set the min voltage to 950, but when I check the vmin file it's always 1150. Is that right? Is something else changing it? How do I get it to stick if not.

I'm using latest Phil's recovery. 12-26 kernel with permissive ramdisk.
[Sprint Samsung Galaxy S III] decimalman:
The configurable vmin zip is probably going crazy. I haven't tested it on a remotely recent recovery, so it might be misbehaving.

/system/etc/init.d/00dkp-vmin configures vmin during boot. If vmin is showing 1150, it probably got deleted. You can create it yourself (be sure to set its permissions so it's executable):

#!/system/bin/sh
echo 950 >/sys/kernel/dkp/vmin
[Sprint Samsung Galaxy S III] marcran75:
The problem I'm getting with the WiFi is intermittent. Sometimes it will connect without any issue and other times I have to retry several times and then there are times when it won't connect all and I have to turn WiFi off to get a connection.
[Sprint Samsung Galaxy S III] enzoevo:
I wrote a init script to echo 975 > /sys/devices/system/cpu/cpufreq/dkp/vmin.

Does your script ultimately set the value in /sys/devices/system/cpu/cpufreq/dkp/vmin?

Looks like I have to bump up to 975. I couldn't get the lockscreen to respond this morning. Assuming it's a voltage issue. :(

Edit: Not sure if init.d isn't working (I have flashed the ramdisk), but 00dkp-vmin isn't creating the file.

Edit2: Switched back to .../cpufreq/dkp/vmin and that works.
[Sprint Samsung Galaxy S III] GreyCelt:
Just wanted to let you know that on the latest aokp 4.4 kernel I was getting random freeze-ups where I would be in an app and the screen would go black and the phone wouldn't respond at all. I tried holding the power button to force a reboot and even that wouldn't respond. I would have to do a battery pull to reboot. I tried getting a logcat but, because it was random, I couldn't reproduce it when trying to get one. ?

I'm on Virgin Mobile s3 running CM11 latest nightly. I have not changed any voltage settings and I was not underclocked.

I reverted back to my Nandroid backup with the 12-26 kernel and have had no problems since.
[Sprint Samsung Galaxy S III] tomcat1974@aol.com:
Thanks for the info....im curious though....when i use ROM Toolbox's animations they work well. Does ROM Toolbox use some kind of app specific modification for boot animations that i could use or is it out of my league (which is very possible)?
[Sprint Samsung Galaxy S III] GreyCelt:
So, I think I may have found a possible culprit to my previously posted problem of random freeze-ups on the latest aosp 4.4 kernel.

I was unaware, until now, that the Xposed Framework cannot work on the ART runtime and automatically reverts your phone back to dalvik if you run Xposed.

Since I thought I was running ART and not dalvik, I was not wiping dalvik cache when flashing anything.

Does anyone think this could have caused these problems? I'm surprised I didn't brick my phone!
[Sprint Samsung Galaxy S III] tlrsax54:
I never wipe dalvik cache.
[Sprint Samsung Galaxy S III] GreyCelt:
Interesting. I've heard a few other people say this from other threads too. I wonder when that changed because, going all the way back to my Samsung Intercept with Froyo days, it was always SOP to wipe cache and dalvik cache whenever dirty flashing an update to a ROM or a kernel.

Anyway, I reflashed the 3.4.77 dkp from 01-23 after wiping cache and dalvik cache this time and, so far, no problems.
[Sprint Samsung Galaxy S III] tlrsax54:
I heard that too and I used to wipe as well, but I think I saw either Gideon or DKP said it doesn't really matter so I quit doing it and never noticed a difference...even Decimalman's install instructions in the OP don't mention wiping anything...but whatever works I suppose :D
[Sprint Samsung Galaxy S III] Liner81:
That's exactly what I'm seeing... Solid performance, snappy and responsive. Haven't seen any errors or problems with WiFi, it looks like it wants to deep sleep, but getting tons of wlan_wake reports.

That's with 4.3TW, MOAR 8.0, 1/26 version.
[Sprint Samsung Galaxy S III] meyerweb:
Kernels and ROMs are two different things. Dalvik, to the best of my knowledge, has nothing to do with Kernels, so it's makes sense that DKP said there's no point in wiping it when flashing his Kernel. But I think it's definitely advisable to wipe it when flashing a new ROM. It might not make a difference in some situations, but it could in others.
[Sprint Samsung Galaxy S III] tlrsax54:
I figured when installing a new ROM, a full wipe included dalvik, but yes I would agree.
[Sprint Samsung Galaxy S III] meyerweb:
I would recommend wiping Dalkvik even when doing a dirty flash.
[Sprint Samsung Galaxy S III] remotehugger:
I would too - I always wipe both cache's no matter what I flash - I think purely out of habit now - even when flashing a mod - not sure if it matters but it certainly doesn't hurt -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] MikeWjF:
I used to not think twice about wiping both caches, but now with 4.4, or maybe it's ART, it takes forever to optimize all the apps on boot.
[Sprint Samsung Galaxy S III] noles4life50:
It's ART and since it's not fully optimized on android yet I just stick to dalvik for now
[Sprint Samsung Galaxy S III] MikeWjF:
Do you feel that performance/battery life is better with dalvik? I'm pretty new to kitkat.