yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] decimalman:
New 3.4 test builds coming out soon! I'm still playing with compilers, so today's compiler nerd-speak is: Linaro GCC 4.8.1-dev with graphite. :p

What's new:

Linux 3.4.40 (not many changes that affect us, but why not?)

New CM/CAF commits

Reworked some cpufreq code to be less ugly. The performance governor is only useful for benchmarking, so now it locks core 2 online.

Fixes to the overclocking code, plus a small fix for msm_thermal when overclocking

New, hopefully more obvious naming system for test builds: dkp-3.4-(device)-(date)-(time)-(branch).zip

Compiler bragging rights! :D 3.4 finally benchmarks the way it should.

There's two more things I want to add to 3.4, and I'll backport some fixes and features to 3.0 and release new stable builds.

Edit: clarified the performance governor thing.
[T-Mobile, Samsung Galaxy SIII] ckisgen:
been running dkp-3.4-d2att-d2tmo-20130417-013455-linaro481 on the latest 4/17 CM10.1 nightly since this morning without any issues so far..

it did seem fairly jumpy/laggy at first .. so I bumped up voltages on the lower freq's and flashed the vmin add-on zip and its been smooth sailing since then .. just switched over from interactive to free lunch gov.

liking what I'm seeing .. keep it up :thumbup::cool:
[T-Mobile, Samsung Galaxy SIII] ayysir:
If i could just nail down how to compile a toolchain lol. Hope you know 3.4.41 linux version has released on kernel.org
[T-Mobile, Samsung Galaxy SIII] decimalman:
I don't check often. I just git fetch from kernel.org occasionally. There's rarely any changes that actually affect us anyway.

I think I know what the problem with the toolchains I sent you was. I'll send you a new one once I get GCC built statically.
[T-Mobile, Samsung Galaxy SIII] _MrAwesome_:
any screen shots before i download it?
[T-Mobile, Samsung Galaxy SIII] ayysir:
Screenshots of a kernel? Why?
[T-Mobile, Samsung Galaxy SIII] decimalman:
New test builds are going up for anyone that flashes the newest CM nightly (and other nightlies as the CM commits eventually propagate to other ROMs). There aren't any major changes on my part, and ROM support is needed, so don't upgrade unless your ROM won't boot with the 4/17 test builds.

Edit: It has come to my attention that not all carriers got a new CM nightly with the changes included. The new builds will not work on nightlies from 4/17 and earlier.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Wouldn't surprise me. Even with the wifi wakelock fixed, I lost an unusual amount of battery last night. I was hoping everything would settle down once I reverted the alarmtimer stuff, but it's never that easy.
[T-Mobile, Samsung Galaxy SIII] sonosam:
So you're saying I should hold off on installing the new build then?
[T-Mobile, Samsung Galaxy SIII] decimalman:
Nah. There's enough bugfixes, updates and improvements to justify giving it a shot. If you do run into unusual drain, let me know--I live in an area with spotty signal, so I'm never sure what's a new bug and what's just poor signal.
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
Hey decimalman, can I flash the kernals in the folder marked "d2"? I know, obvious question.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Yep. CM managed to consolidate all the carrier-dependent stuff, so now a single kernel will work for all US S3s.
[T-Mobile, Samsung Galaxy SIII] kingston73:
I'm using cyanfox 4.4 and flashed the latest kernel last night. I can't say anything about how well it will work with use but the idle drain overnight was pretty good, ten hours of idle and it was only at 92% this morning. This was the one with "strategic" changes or whatever the title was.
[T-Mobile, Samsung Galaxy SIII] 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
[T-Mobile, Samsung Galaxy SIII] CooLoL1999:
Just updated mine. So far I feel like I get smoother frame rates when I play games (GTA: SA). Smoother overall. I really love this kernel man! Thanks!

Edit: I also get stronger Wi-Fi signal too!
[T-Mobile, Samsung Galaxy SIII] Adreaver:
[MENTION=4932679]decimalman[/MENTION]: FYI, devhost keeps opening a new tab and trying to sneakily download something called mobogenie.apk every time I try to download your kernels. Usually not an issue, but today it stopped my download of the 1/23 build. Had to download on PC, wouldn't work on mobile.

You may want to talk to devhost about this so people don't think mobogenie is part of your kernel.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
I blocked it with adaway, it's not just his devhost, it's them in general.

Infamous, the dynasty of development.
[T-Mobile, Samsung Galaxy SIII] spartan268:
Latest build from d2 section for kitkat.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
I was going to open a support ticket with them to complain, but I've got a better idea. I've been meaning to switch to a more reliable host for a while now, and I think it's time I pulled the trigger.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Well, my first day of use was great but after a recharge overnight it wouldn't go into deep sleep. Trickster says it was staying at 384 without any sleep, I can't figure out what was causing the wake lock so I'm back on the 12/26 build.
[T-Mobile, Samsung Galaxy SIII] wyldkard:
So far so good on one day after a full charge. Not sure if its just kitkat or the kernel but this runs better than I remember it running on 4.3 roms
[T-Mobile, Samsung Galaxy SIII] ppgregory:
I was on the new 4.3 kernel with the same issue. 12/26 goes deep sleep, no problem.
[T-Mobile, Samsung Galaxy SIII] pp085ster:
I don't know if this is going to help you [MENTION=4932679]decimalman[/MENTION] but here are some BBS screenshots and a network log from the latest TW4.3 kernel that is suffering from deep sleep issues mainly related to wlan wake locks in my case. Good luck finding the culprit! :highfive: and thanks for the great kernels by the way :D
[T-Mobile, Samsung Galaxy SIII] madunix:
i tried installing the kernels from att-tmo and from d2, they all failed on me. i'm using twrp latest recovery.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I already know what's going on, but this bug was supposed to be fixed. I'll dig through the TW sources and see what's going on.

Error messages?

I hear it's time for a new updater-binary, but I haven't had any problems yet. Of course, I'm running PhilZ from a few months ago.
[T-Mobile, Samsung Galaxy SIII] thelazy8:
Had this problem briefly myself. Don't have enough expertise to know why but after I wiped system and reinstalled the rom I was using (slimkat) the kernel zips started flashing again (also using TWRP latest).
[T-Mobile, Samsung Galaxy SIII] Bitcloud30:
[MENTION=4932679]decimalman[/MENTION] in faux 4.1.2 :Dmy cpu governor setting was Intellidemand which i like the most. Here in your 4.3 kernel what cpu governor is closet to that kind of build in your kernel?:) :D:D:D
[T-Mobile, Samsung Galaxy SIII] decimalman:
After resisting for ages, I think it's time dkp got a fancy splash screen. I don't have any design flair whatsoever, but I'd love for someone to contribute something. If possible, it should be a 720x1280 PNG. Anyone interested?

I don't follow faux's work very closely, so I'm not really sure. Sorry.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Something quick I threw together... if you want to change anything feel free, or if you have any ideas let me know...

Infamous, the dynasty of development.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I don't have anything in particular in mind, and I'm definitely not qualified to go and change anything. Plus, yours is leaps and bounds better than what I had. :p
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
Well, if you like that one, I'll mess with it and give you some options. And see what else I can come up with.

Infamous, the dynasty of development.
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
More...

Infamous, the dynasty of development.
[T-Mobile, Samsung Galaxy SIII] decimalman:
I was originally leaning towards minimal, but like where you're going with these. :good:
[T-Mobile, Samsung Galaxy SIII] ZDeuce2:
A little more minimal...

Infamous, the dynasty of development.
[T-Mobile, Samsung Galaxy SIII] spartan268:
Love your kernel. Can't wait for the next update!

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
It's finally time for the new AOSP test build I've been teasing! I'm pretty excited about the new installer: it allows on-the-fly splash screen generation, ramdisk tweaks, and it's multi-threaded so it doesn't take forever to cook the new ramdisk.

There have been a lot of splash screens posted in the last couple days, and I can't pick just one. I rolled eight into this build, and the installer will pick one at random every flash. I'm thinking about changing the lineup every couple builds, so keep the splash screens coming. :good:

Downloads aren't going to the usual location! Dev-Host has been pretty unreliable, and when I heard that they're sneaking bogus APKs in with legitimate downloads, I decided I'm done with them. Downloads are up on Mediafire. I haven't been able to find an ideal file host, but Mediafire seems less awful than most. EDIT: Mediafire is acting up already. :( Direct link is here.

Changelog:

Ermahgerd splersh screrns*!

Updated to a toolchain based on GCC trunk (i.e. GCC 4.9 development)

Linux 3.4.79 and oodles of CM updates

Stripped a few useless bits from the board file

Fixed the power key not rebooting

By request, added simple GPU governor

Changed the default minimum voltage back to stock**

Lowered absolute minimum voltage limit to 600 mV for the few phones that can undervolt below 700 mV

* I included eight splash screens, one of which will be randomly picked at each flash. If you'd prefer, you can switch to a custom splash screen: extract the initlogo.rle from a splash screen zip to dkp/splash.rle in your internal storage, and it'll be applied automatically whenever you flash. Copying a PNG to dkp/splash.png also works, and I'll add support for JPEGs soon.

** The stock defaults are back. Too many of the issues being reported are (probably) caused by the lowered default voltages. There's a new (fixed) custom vmin zip here to lower the limit, Trickster's "Override Minimum Voltage" still works, and the old (lowered) default will carry over until you flash a new ROM. I'm considering adding an addon.d script so that a custom minimum voltage setting will carry over after ROM updates, but I haven't gotten to it yet.
[T-Mobile, Samsung Galaxy SIII] dynas7y:
Sorry, but can you explain where exactly I'd place the PNG to replace the splash screen? Thanks for the great kernel!
[T-Mobile, Samsung Galaxy SIII] decimalman:
Internal storage > create a folder named "dkp" > save as "splash.png"

The image converter isn't as fancy (yet) as it should be. It can't resize images (so ideally they'd be close to 720x1280 to begin with) and it doesn't understand many file formats. Still, custom splash screens. :D
[T-Mobile, Samsung Galaxy SIII] dynas7y:
Gotcha, thanks. Aside from the (great) performance, this new feature in addition to the LED animations just make this kernel the best!
[T-Mobile, Samsung Galaxy SIII] spartan268:
Would be great if someone could post all the splash screens, so we can see which one we like and flash until we get it.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] kingston73:
I can't post it right now but my first flash has a robot track runner-type picture. Only been using this newest kernel for a few hours but so far it's great, none of the wlan wakelock reports like I was getting with the 1/23 build. With freelunch gov it definitely seems smoother than the other kernel I was using as well. Thanks for a great job:good:
[T-Mobile, Samsung Galaxy SIII] dynas7y:
You can always extract the .zip and you should see all of the splash screens immediately. If you then find one you really like, you can create a "dkp" folder in your internal storage and take whichever one you like, rename it to "splash.png" and place it in that folder... then you'll get that one every time you flash thereafter
[T-Mobile, Samsung Galaxy SIII] Slypnslyde:
Thanks for the bad ass d_man it does wonders for the new aosb build
[T-Mobile, Samsung Galaxy SIII] spartan268:
Edit: nevermind it was late at night and I mest up. Figured it out thanks.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] decimalman:
There's a new AOSP 4.4 test build up on Mediafire. I haven't changed much, just fixed two silly bugs that might be causing problems with wifi wakelocks.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Thanks for this, I was going crazy trying to figure out what was going on with my battery drain. Hope the new one works, great kernel and thank you.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
The new AOSP test kernel won't flash. Get a failed message in twrp 2.6.3.1. Tried downloading via xda app and browser.

Any suggestions?
[T-Mobile, Samsung Galaxy SIII] decimalman:
What errors is it giving you? The new installer is doing a lot of work behind the scenes, so there's a lot that could fail.
[T-Mobile, Samsung Galaxy SIII] animefans:
nuke those bluetooth wakelock plz!

decimalman

thank you for your work

your latest kernel seem to kill lots, of not all, of the wifi wakelock

can you do your magic and kill those bluetooth wakelock as well?
[T-Mobile, Samsung Galaxy SIII] :
decimalman,

I've flashed your latest 4.4 kernel build on CM11. Using WIFI and Bluetooth together - no problem. For some reason, when I use headset and mobile data, I seem to get a lot of "deleted_wakelocks" listed as a Kernel wakelock in BBS.

So, I cleared cache and dalvik and tested again - sure enough, the wakelock appeared again using mobile data and bluetooth headset.

I've attached a logcat.

---EDIT--- Never mind...it appears to be ROM related. Updated to the latest CM nightly and it's taken care of the issue.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
https://www.dropbox.com/s/gttpbscc0ouuw1l/recovery.log
[T-Mobile, Samsung Galaxy SIII] decimalman:
deletede_wakelocks shouldn't ever keep your phone from sleeping. It's just for record-keeping, so wakelocks that don't exist anymore can still show up in the wakelock stats. The wifi wakelock is the most likely culprit: whenever you turn off wifi, deleted_wakelocks absorbs its wakelock statistics.

Looks like TWRP couldn't open the zip file, which probably means a bad download. Mediafire has been all kinds of awful. :( Future builds will use private hosting (kindly donated by xstefen :good:) to avoid all the usual file host BS.
[T-Mobile, Samsung Galaxy SIII] :
That explains why they were so high street switching to mobile data. Thanks for the clarification.
[T-Mobile, Samsung Galaxy SIII] decimalman:
New TW builds are going up! I think I fixed the misbehavior that was holding this build up, though I haven't heard back from all my guinea pigs yet. If this builds still misbehaves, let me know.

Downloads are on a new host generously provided by xstefen. I'm in the process of moving things over, and more downloads will appear in the coming days.

Changelog:

Splash screens!

By request, added simple GPU governor

Fixed (hopefully for good this time) the wifi wakelock going crazy

Wrote a new a2220 (voice processor) driver to fix some major issues plaguing Sprint. If it causes any call-related misbehavior, let me know.

Lowered the minimum voltage to 600 mV for anyone crazy enough to UV below 700 mV

Restored the stock (1150 mV) minimum voltage, you'll need to change it manually to undervolt effectively

To adjust the minimum voltage there's a new custom vmin zip here; rename it something like "dkp-vmin-700.zip" and flash. Trickster's "Override Minimum Voltage" still works as well.

It's msm_serial_hs_dma that causes the most trouble, right? I don't use BT enough to keep tabs on its wakelocks.
[T-Mobile, Samsung Galaxy SIII] animefans:
sometimes it's msm_serial_hs_dma

sometimes, like now, it's bluesleep

somtimes it's PowerManagerService.WakeLocks
[T-Mobile, Samsung Galaxy SIII] decimalman:
I can't do much about PowerManagerService (that's controlled by the ROM), but I'll look into the other two.
[T-Mobile, Samsung Galaxy SIII] animefans:
Here's 2 screenshot from BBB

I will see if I can easily reproduce them

In general, this is how i setup/use my bluetooth

i keep bluetooth off at home

when i am in my car, i switch on bluetooth, and the phone connect

when i shut down my car, bluetooth disconnect automatically, and I turn off bluetooth

These bluetooth wakelock SEEMS to come up once I made a connection with bluetooth, BUT did not disconnect from the phone itself

If I never connect bluetooth (ie after a reboot), I don't think I see these bluetooth wakelock at all...
[T-Mobile, Samsung Galaxy SIII] NexusS4gFreak:
can i use this on t999n metro? looking for a kernel that can possibly fix my wifi
[T-Mobile, Samsung Galaxy SIII] Adreaver:
I'm using this on t999L tmo, which is identical to t999N metro, with the exception of bloat and apns.

So yes, but nandroid first and all that jazz.
[T-Mobile, Samsung Galaxy SIII] decimalman:
Wow. That's some spectacularly bad behavior from the bluesleep driver. The bluesleep driver is pretty straightforward, so hopefully it won't be much trouble to fix this.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Think that could have any other potentially beneficial side effects? There are major connection issues with no apparent cause. One day I can connect to car Bluetooth and the speaker at work fine, the next just the car, day after that just the speaker, day after that no connectivity at all despite multiple reboots/re-pairs, then the day after that everything is fine again.

My hunch is that an improper disconnect (like shutting off the car or walking out of range) isn't correctly closing the connection, so it isn't available to initiate a new connection. But this is just conjecture.

Any testing I can do to help let me know, I have access to a few different BT devices that I use regularly. (Car (phone and a2dp), headset (phone only), and speaker (media only, I think its a2dp cause there is no display but I suppose it could be avcrp).
[T-Mobile, Samsung Galaxy SIII] decimalman:
I know exactly nothing about BT, but the impression I've gotten is that the connectivity problems involve more than just the kernel. With that said, you never know what kinds of bugs will turn up while I'm looking through the drivers.

I'll keep you updated. I've only got one BT device handy, so I'll probably need you to test some things for me eventually.
[T-Mobile, Samsung Galaxy SIII] pp085ster:
Here are some basic splash screens that I put together:

https://www.dropbox.com/sh/iw8gzxqs3d614n1/cf2yYfSaNn

I take no credit for the images since they are just Google image searches. I hope you guys like them :D

REMEMBER:

Here are some previews, download from dropbox though for better quality:

View attachment 2585627
[T-Mobile, Samsung Galaxy SIII] tacomaguy20:
I've followed these steps but maybe there is something that I'm missing. I still get the blue dkp letter splash screen when I start up. Any idea what I'm doing wrong? I put the dkp folder on the internal memory and then saved the splash screen as splash.png. I did make sure the pixel size was right and I converted the picture from a jpeg to a png in photoshop.
[T-Mobile, Samsung Galaxy SIII] dynas7y:
Once that is done you'll need to flash the kernel again, then it should show up
[T-Mobile, Samsung Galaxy SIII] tacomaguy20:
Oh ok cool. Thanks
[T-Mobile, Samsung Galaxy SIII] :
+1 on bluesleep - killed 25% of my battery overnight. I ended up creating a Tasker exit task that, after I disconnect my phone from the car, it shuts of bluetooth for 10 seconds, turns it on again for 1 minute, and then turns it off again. That seems to clear the connection to the car and stops the bluesleep issue.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Experiencing high battery drain because of deskclock wake lock.. Please help
[T-Mobile, Samsung Galaxy SIII] tdotdot:
The wifi on the latest TW build kept my phone up for quite a while. Lost about 15% in 5 hours because of it. Is this a known issue? I noticed somebody else had posted about this with BBS screenshots.
[T-Mobile, Samsung Galaxy SIII] roly17:
+1. I think that I'm having the same problem on the latest AOSP (2-13). Haven't used Wi-Fi at all today.

Going back to 12-26, works the best for me.

sent from the INFAMOUS S3 Anthem
[T-Mobile, Samsung Galaxy SIII] tdotdot:
That's the new wifi location option. Not really a problem and some people say it probably helps battery.
[T-Mobile, Samsung Galaxy SIII] roly17:
If it's an option, can I turn it off? Also could you tell me how it helps battery out point me in the direction of how you know this?

Thx

sent from the INFAMOUS S3 Anthem
[T-Mobile, Samsung Galaxy SIII] tdotdot:
http://howto.cnet.com/8301-11310_39...-4.3-from-always-scanning-for-wi-fi-networks/
[T-Mobile, Samsung Galaxy SIII] tacomaguy20:
I love this kernel because it is saving me so much battery life right now. My only problem so far is that when I play music, the music cuts out for a split second like when a cd skips. I am using the trickster mod as suggested. I lowered the voltage -25, I put read ahead butter for 512, using freelunch and zen. Zram on. Those are the only changes I made but I'm kinda new to this so any suggestions on what to modify to fix this would be helpful. I would still like to keep my battery life close to what it is now so the less I can change to get the music working, the better. Thanks in advance.
[T-Mobile, Samsung Galaxy SIII] tdotdot:
Increase the read-ahead and see if that makes a difference. I play a lot of music and didn't experience this skipping.
[T-Mobile, Samsung Galaxy SIII] pp085ster:
Is this a normal amount of wifi wakelocks?
[T-Mobile, Samsung Galaxy SIII] tacomaguy20:
I adjusted some settings and that seemed to help. I actually think it might have been my Bluetooth messing up but it seems to work well now. Now I seem to be having trouble with the screen going off and not coming back on. Not sure whats going on with this. I think I might have messed with the GPU governor settings and now Its acting up.
[T-Mobile, Samsung Galaxy SIII] tacomaguy20:
Oh a new version of my Rom came out, installed it, reinstalled the Kernel and now all is good again. Thanks
[T-Mobile, Samsung Galaxy SIII] MrTallboy:
I'm running the 12/26 TW 4.1.2 kernel with S3Rx ROM and it seems like I have some funny wakelock behavior. Although I'm not sure if it's real cause battery life is good still.

In the attached pictures I let the phone sit overnight unused. It was in a crappy signal area. Normally it drops .8%/hr overnight, this time it was 1.2%. Still not bad.

The "Other" tab says Awake time was 38 minutes, but the "Partial Wakelocks" tab says UlrDispatchingService held 52 minutes worth of wakelock.

On the "Kernel Wakelock" tab PowerManagerService held 17 minutes of wakelocks. I always thought PowerManagerService service was supposed to be the sum of your partial wakelocks, but that's obviously not the case here. I'm guessing the 17 minutes is right, but the 52 minutes and maybe other partial wakelock numbers are bogus.

Looking on the android battery monitor shows the phone waking up very often. I would expect this to result in poor battery, but that's not the case here. Wondering if this could be UlrDispatchingService not playing nice with DKP?

I'm pretty sure UlrDispatchingService is related to Google Now location reporting cause when I disable it the wakelock disappears.

And if I switch back to the stock ATT MG2 kernel the UlrDispatchingService wakelock is only a few minutes out of 8 hours. This is what made me think I have something funny going on and can't just blame Google location reporting this time.

So Decimalman, do what you want with the above info. I realize 4.1.2 isn't too high on people's radar these days but I thought I'd report anyway.
[T-Mobile, Samsung Galaxy SIII] :
S3Rx is a 4.3 ROM. Try the 4.3 kernel.