yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
None, just run it as it is ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Optimizing battery

What governor and tweaks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Never heard back from ya with that PM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
freelunch/deadline

undervolt by 25

modify brightness values @ various lighting to make smooth curve
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Very happy with freelunch!

---------- Post added at 07:16 PM ---------- Previous post was at 07:16 PM ----------

Didn't even start at full charge
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll do you one better. I've been working on fixing UKSM's misbehavior. It's behaving much better: completely turning off during standby, getting out of the way when other apps need the CPU, but tearing through memory when it gets the chance (I've been checking on it, and it's typically reducing memory use by 10% or so).

I took a look at GideonX's code, but didn't see any obvious differences that would cause anything like that. I'll look into it further when I get a chance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Thank-you :) Next build will be interesting, I'm always on my phone so if you need a guinea pig let me know. I use hangouts a lot so I'm easy to contact.

I believe one day you'll be able to dub one of your kernels "should-be-stable". For lack of a better word, but common sense is always a good thing to utilize if overclocking + undervolting your phone's CPU is of interest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can't wait to try the next version of dkp for TW
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxoooo:
+1

Great kernel, working perfect on i747m (tw 4.3) . Fast, good battery... :victory::victory::victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Is there a way to tweak charging current and does this kernel support that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Ktoonez just uploaded a 4.3 tw build with a ramdisk. I'm editing as we speak ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
Hi decimalman

Thanks for your reply - here is background and updated info:

background:

BT works fine with CM 10.2 (4.3) & CarbonROM with dkp

I am working on a catlog for you, but in the meantime.

How to reproduce problem (two cars, BMW and Hyundai)

After reboot - bluetooth connects to device (car) without issue.

When you leave the car - the connection doesn't close and remains open even though it's way out of range.

As a result, all audio is still connected to bluetooth and goes nowhere: no ringtones, can't play anything, everything seems to be routed to connection still.

Turning off bluetooth doesn't resolve the issue

Hitting vol +/- shows the bluetooth volume

Rebooting the phone returns to working state.

BMS Update: It's not perfect actually. I've found that after the first connect, every once in a while I have to restart bluetooth to get it to reconnect.

CM: I've have this consistently on CM since moving to KitKat.

Thanks again in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
It's not a kernel issue and this issue has been present since......... AOSP existed. Bluetooth has been very buggy on any Rom and kernel. I have had all these same issues you have since jellybean builds. Problem is we can not use the bluetooth drivers available in TW or any stock Rom for that matter. Until someone is able to make a perfect bluetooth state for AOSP, then we are stuck with a hit or miss Rom. Yes I have had a good Rom with bluetooth working as it should but like I said it's hit or miss. No one knows why this happens but it goes all the way back to the CM base. I have however heard rumour that Omni Rom has their own bluetooth base and it works. Nothing confirmed yet though.

By the way. If you want to turn off bluetooth without rebooting. Just go into your bluetooth connections and manually disconnect. It may take a minute but it will disconnect and then turn off bluetooth. Once you endure your car turn it back on then start the car. Works for me almost everytime. It's the automatic turning off and on of bluetooth that isn't working. Weird but sadly the truth in this matter. Hopefully this helps. I just didn't want decimalman to wreck his brain............ Unless he can create the fix ;p

Crack-Flasher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
+1 I keep trying to explain this in threads. It's true, we can't use touchwiz drivers. What's make it even worse is if this phone is like most Samsung phones the drivers are closed source because the chips are made by broadcom. They keep all their drivers closed source. Cm or someone would need to re-engineer a driver as far as I know. I might be wrong but it's no easy task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
Hi Guys,

Thanks for the feedback - I know it's partly in the ROM, but going back to BMS for a moment, following this change, BT stuff had been working solid on BMS for example. So I don't think it's entirely isolated to the ROM as different kernels BT implementations (?) work better or worse with ROMs.

Admittedly, I don't know the details as you both may - so I'll defer to you, but just thought I'd reference one example (maybe it will help):

from BMS 3.4 Build Changelog:

Build 2013-05-28

d2vzw/d2usc - http://goo.gl/TZT12

d2att/d2tmo - http://goo.gl/eieVu

d2spr - http://goo.gl/29Y52

Merged latest CAF updates as of today (AU_LINUX_ANDROID_JB_2.5.04.02.02.040.330)

Linux 3.4.46

Linux 3.4.47

Frandom module is now supported http://billauer.co.il/frandom.html. This allows for the Crossbreeder mod to work. If all you want is to do is test out frandom, you can use this BMS frandom zip that contains the script needed to enable it. It will load a init.d script as well as place a testfrandom script in your system. You can open up terminal emulator and type in testfrandom to see if it worked. If you are seeing < 1s completion times, you're all set. (Credit to Eli Billauer, Ryuinferno and f1vefour and whoever was involved that I may have missed)

>>>>>Reverted some commits to fix BT connection issues

192Mhz slot removed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
You realize this kernel is months old and for jelly bean. KitKat once again is a completely different beast. They need to back port or re-engineer a driver for KitKat. No easy task and things are going to break. Yes figure, it took them until may of this year to get Bluetooth working right on jellybean. It might be a while. Buckle up and enjoy the ride :thumbup:;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
This works well in the meantime. I was able to disconnect manually even after I was out of range. phew. better than a reboot.

---------- Post added at 11:16 AM ---------- Previous post was at 11:07 AM ----------

Yes of course. As I said - it was an example used to illustrate that changes in the KERNEL can also effect Bluetooth. ;)

Yes of course. Sadly it seems we're back to square one. Good thing there are awesome developers out there to make it all work! Can't thank you guys enough for this. :)

Thanks for your feedback. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Can't wait for an aosp update....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Funny, I was about to PM you this test build with all the UKSM stuff I've been working on.

I'm curious how much the UKSM changes have helped. I changed a lot of things to make it stay out of the way and eat less CPU, as well as a few that make its scanning substantially more efficient. Among other things, the new scanning routines (written in hand-tuned assembly) are something like 3x faster than the old ones. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Need a new tw build lol, kt always seems to break my gps ur kernel gives the savings on battery n plays nicely
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Anyone by chance using this rom S3Rx 3.0 [TouchWiz 4.3 base Non-AROMA 12/18/13] with this kernel?
[AT&T, Rogers, Bell, Telus 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)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Great Kernel...thanks for your hard work!!!

Nice to see the frequent updates and attention to detail!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
I am unable to get deep sleep on newest 4.4.2 kernel and liquid smooth beta iii. Going to reflash

*edit* reflashed with only gapps installed. Still no deep sleep. Just sits at my lowest clock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Same here on Slim. Also noticed, using Trickster, with Ondemand governor, the frequencies aren't being reported correctly. Trickster shows CPU0 pegged at 1512, but with warp on, it's switching seemingly. Oh, and my GPU frequency is missing on the info tab, so I can't monitor it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a brand new bug that completely prevents deep sleep from happening. Also, there's a bug (which I'm sitting on a fix for) that causes runaway wakelocks from the wifi driver. I'm working on getting deep sleep working again, but it might not happen tonight.

EDIT: Deep sleep was happening, but not being correctly reported.
[AT&T, Rogers, Bell, Telus 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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] condor97:
Been waiting for this one, thank you and great job!:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Latest 4.4 kernel (1/23) prevented wifi from turning on. I'm on Quantum rom 3.15(4.4.2 rom). I reverted back to the 12/26 kernel and it's fantastic!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
ROMs from before 1/13 or so are bound to have problems with the new wifi driver. Updating your ROM should fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Decimalman awesome work on AOSP 4.4 1/23 test kernel. Running d2att with Vanirs Nightly 1/23 build and things are smooth and quick.

Flawless

Thank you sir.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
[MENTION=4932679]decimalman[/MENTION], can you give me a set of steps to reproduce the problems you had with my alarmtimer commits? They appear to work in all my testing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Great work on 1/23! Working awesome on 4.4 liquid smooth. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
I may be blind but where is the download? All I can see is 12-26 in the AOSP 4.4 testing folder...

EDIT: NVM, forgot about the cm merging all devices :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Hello. Look In the folder that says d2. That's all it says. Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's two issues:

First, time spent in deep sleep isn't reflected in system uptime or BBS. This happens reliably, whenever the system enters deep sleep. I'm guessing that CLOCK_BOOTTIME isn't being advanced like it's supposed to, though I don't actually know what I'm talking about here. Obviously, this is a relatively minor problem, but it's still not ideal.

EDIT: I'm having trouble reproducing this consistently.

Second, several people have reported that the system clock isn't updating correctly. I haven't been able to reproduce it. It's only been reported on CDMA variants, most commonly Sprint. From what I gather, system time is being reset to 0 (i.e. Jan 1 1970) instead of the carrier-provided time. This is a huge problem, since it breaks HTTPS and any other certificate-based security schemes.

EDIT: I'm able to reproduce this by pulling battery for long enough for the RTC to reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Thanks! Will download updated rom when I get home and try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
*Update* works like a charm! Much appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Are you working a TW update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synthetic.Nightmare:
I don't have these issues. BBS is showing everything fine on my builds with the alarmtimer commits... On d2tmo & att at least.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jballa15:
Bluetooth is a bit buggy still. Randomly freezes up connecting to my car or jawbone era. Have to remove battery because all buttons are functionless when it happens. Everything else is phenomenal!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I just finished merging everything for TW 4.1 and 4.3. It'll take a bit to build everything, but I should have new builds up sometime tonight.

Strange. d2spr seems to have more problems with this than the other variants. Someone mentioned having bizarre clock behavior in ktoonsez's d2spr thread as well.

Once I get some new TW builds up, I'm going to restore all the alarmtimer stuff and take a better look at what's actually happening. I'd like to get the new alarmtimer code working, since it has a few advantages over the old code.

You don't happen to have adb set up on your computer, do you? A logcat (and possibly a dmesg) would help a lot in identifying what's going on.
[AT&T, Rogers, Bell, Telus 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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Seems to be working smooth for me so far! on latest 4.3 Deadly venom. Thanks for the update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I'm sure I'm going to regret this, but here goes:

Upstream at CM we're almost sure BT problems are all userspace related right now.

I've added some more alarmtimer commits for your amusement, along with a recent userspace change this allows alarm power on from charging mode, I'm still trying to figure out why it doesn't work from power off, my best guess is either we're not triggering the irq properly (might try loaidng the qpnp driver) or MSM8960 doesn't support it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
That was my thought as well--everything I've heard about BT sounds like userspace not handling connections properly.

I'll give the new alarmtimer stuff a shot. Thanks for working on it in spite of my whiny posts. :good:

EDIT: So at least one of the bugs I've been seeing was a spectacularly stupid mistake on my part. Apparently, I elected not to update the defconfig to enable the new alarm driver when I merged the alarmtimer stuff. Face. palm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Courtesy never hurt anyone. I'm still in the "Ehrmahgerd people in my thread, flashing my stuff!" phase of being a developer, and I'm not cocksure enough to chew users out for asking questions or reporting issues. I'm honestly grateful for all the positive feedback I'm getting though.

I've never sat down and looked for ideal settings for gaming. My first suggestion would be to increase hispeed_decrease. A LOT. It's probably too low to begin with, so I'd start at 75000, and try working your way up to 150000 or so. Increasing hotplug_down_cycles to as much as 10 will also keep freelunch from disabling core 2 excessively. I'll get a description of all the tuners posted eventually, and hopefully some gamers can come up with good settings.

Edit: I overlooked the most obvious change: lower interaction_hispeed. 1188000 generally keeps screen transitions pretty smooth, but for games, you'll never know the difference if you lower it.

More edit: another obvious change: decrease interaction_overestimate_khz. 125000 seems reasonable, but it's probably possible to go lower.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Thanks for the recommendations. I want it to keep core 2 as much as it does, so I'll try the first thing you mentioned.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
One of the goals I had for freelunch was for it to be able to take core 2 offline if it will save power, even during load when other governors would usually leave it on. The default settings are good for light usage and should save power, but for gaming I suspect they force too much work onto core 1 and end up using more power than they should.

On a mostly unrelated note, I wanted to mention is that I'm considering modifying a few other governors (abyssplug and pegasusq are the likeliest candidates) to support dkp's interaction and automatic mpdecision features. I haven't been keeping up with the latest and greatest governors, so if anyone has a favorite, I could look into it as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
so far freelunch is the best i've used on 3.4. On 3.0 there is a governor called asswax that was crazy good. Other than that, the only ones I know of that may be woth it would be intellidemand or interactiveX
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'll look into them. I'll need to give some thought to how exactly they should handle interaction, but hopefully I can come up with a general way that will work for most governors and merge a bunch without a lot of effort.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Decimalman,

I have tried everything to get your kernel to work but once the screen goes off, it never comes back on. I've tried flashing stable, exp, vmin.zip, raising voltages as high as +100, nothing works. Flashed the file you posted most recently as well. The funny thing is the phone is still working just the screen doesn't come on. I can even connect to my pc and see my internal/ext cards, transfer files, ect. I can feel my haptic feedback and back key lights turn on. And there is no logcat or last kmsg because the phone thinks it's working fine just no screen. I don't know if I'm explaining myself correctly and I apologize if I'm not making any sense. I'm on the newest deviant xone rom linux 3.4. BMS, Tasks underwear, kt's kernel, all work fine and don't give me this issue. What else can I do so I can help you figure this out? Would like to try out this kernel as my bud Ryan Mead has great praise for it. TIA!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
PM on its way shortly. I'll see what I can do to get this fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
i hope this thread stays like this. such a breath of fresh air.

Edit: and not by you hopping on bugs, just the positive vibe. I reread that and realized with your quote it kinda seemed like that's what I was referring to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Having same problem as SK. TIA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Cut me some slack! None of the bugs have caught anyone's phone on fire yet. :p Seriously though, I'm doing this because it's a lot of fun and I enjoy it. Having a civilized thread like this just makes it all the more enjoyable.

I'll send you a PM shortly. Hopefully I can get this sorted out tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobstradamus:
This Kernel is amazing. Thanks for giving us all this gift. Currently at 40% with 2.5 hours screen time and 18.5 hours time on battery. I've been scared to try the Trinity colors version and ruin my battery luck I'm having haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Nice.

The Trinity builds were basically the same as the stable ones. Unfortunately, I caught a recent bug that I'm still working on and panicked and took down all the experimental builds. Oops. I should have new ones up with Trinity support (and bug fixes and a few new toys) in a day or two.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Damn, I've been running that build with no issues. Can't wait to see how a "fixed" build with new toys runs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegreatscott:
Ditto. This is one of the few 3rd party kernels that my phone will run. I love how decimalman put the vmin. tweak. I think that was a big help. Trinity colors is pretty nice too.

Thanks brudda!

Edit: 'put' not 'but'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I knew the adjustable vmin would be useful. :) When I add features that people (or their phones) might not like, I make sure that they're optional and easy to change. The vmin and trinity zips actually just change some initscripts, and a the overclock code doesn't make certain changes that might be unstable/dangreous until the processor is overclocked.

My first priority with dkp is for it to be stable and bug-free on everyone's devices. There's still a bug or two that only affect a few users, and I'm working with them to get everything sorted out. If I think there's a bug I missed, I'll take down any builds that I think are affected (like I did with the trinity-colors and tuner-fixes experimental builds recently). Maybe it's just me, but I think this is the best policy--I want everyone to have a positive experience flashing my stuff. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Thats a great policy decimalman.

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] helushune:
Using the 3.4 stable version with Zerospeed8's AOKP builds and everything has been rock solid. If I ever get the screen display bug I'll help you debug it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New 3.4 experimental builds are going up!

governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.

gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.

Edit: I'm building a 3.0 kernel with trinity colors support and GCC 4.8.0 now. It should be up shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Does the new experimental have trinity baked in or is the trinity version also updated?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Trinity is included. If I don't hear complaints about a feature I add to an experimental build, I merge it in so all future builds will have it. If you dirty flash, you probably won't even need to reflash dkp-enable-trinity.zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
Download page were very picky

I couldn't see any stable for d2att. At least old..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
What do you mean... I don't understand what you're trying to say.