yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
For CM, grab the more-reverts build from a few days earlier. Apparently, some phones don't like the newest build. There haven't been any 4.2 kernel changes from CM since they started work on 4.3, so compatibility isn't an issue.

As for TW, I've been meaning to update. I'm not aware of any bugs like that though. Care to provide some more details?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for your quick response.

AOSP: As per my knowledge, the last update on 4.2 was the 8/18 build. Can't find anything newer. The screen flicker was so terrible, I have to flash another kernel within seconds. The screen was unreadable.

TW: I posted this couple of pages back. The mobile does not boot after installing the last DKP TW Kernel:

http://xdaforums.com/showthread.php?p=44711293&postcount=260

http://xdaforums.com/showthread.php?p=44730597&postcount=264
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Init.d

I have a quick question that I hope someone can answer or point me in the right direction. When flashing this kernel, after coming from LeanKernel (but in general, most kernels after a flash), I notice that there are left over scripts in the init.d directory. I haven't been able to find much information regarding what problems can be caused with these left over files. Do they need to be deleted? Are they ignored? I've never really had any issues, but I want to know if these can cause any problems. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
If you have left over initd scripts from other kernels then just go ahead and delete them with root explorer or your app of choice. They shouldn't cause issues at all but if I had lk files left over I would delete them and reboot. Same goes if you come from any kernel. Just delete the old files and reboot. Will not cause issues of any kind. Initd are just add ones provided by the dev to add a specific feature or to control something in a easy specific way.

infected sgh-t999
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Thank you, I really appreciate the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
You can expect an update right now. :) After this, I don't plan to continue 4.2 work, since CM isn't updating the 4.2 kernel. Compatibility shouldn't be an issue since there aren't likely to be any further kernel updates from CM, and I don't expect to make any earth-shattering changes in the near future.

New 4.2 stable builds are going up now.

Changelog since last stable build:

Fix OC frequencies not sticking.

Fix UV interface for a few apps.

Fixes for automatic auto-hotplug.

A handful of optimizations.

Lots of CM commits.

Merge nanolunch back into freelunch.

Fancy new compiler.

The flicker in recent test builds should be gone. If not, let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks man, time to flash the rc2 again. You rock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] firefreak664:
Hello I'm on tw rom s3rx 2.2 test build I'm getting very bad screen flicker when I flash this kernel. I can use the phone but not for very long before I get aggravated and flash back to stock. If there's any fix or anything I can do please let me know everyone else seems to love your work I would love to try it out more. Thank you in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
4.2 stable build is working perfectly on 10.1.3 RC2, running for the past 24 hours no issues whatsoever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I didn't think the TW drivers would suffer from the flickering, but looks like I was wrong. :( I'll revert the stuff that's causing it and get a new build out soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
so I am "testing" out this kernel with PA3 3.99 on a I747. Anyone have problems with apps being closed down for no apparent reasons? I am running exactly the same apps prior moving from Ktoonz's kernel to this one... the only thing is that I am using Android Tuner instead of Kweaker ...

EDIT: NVM... Android Tuner has this thing with Active Task Killer... stupid...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Question: Does this kernel support screen off mhz limits?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I do not think so. I haven't seen it anywhere.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Anyone notice this kernel kills aggressively in lowmemory situation or OOM situation? After a long day of no reboots, almost all my apps are killed, even ones that has notification icon enable for those apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Eagerly waiting for the next TW release, just moved back to Stock TW ROM couple of days back.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
Any updates in the pipeline for 4.3? Love the kernal so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Not currently. It looks like some apps should support setting it, so I'll look into adding it at some point.

I haven't touched the low memory killer stuff, so there shouldn't be any differences between this and other kernels.

I haven't had access to my computer for the last week, and don't anticipate that changing until this weekend at the earliest. :( I'll get new builds out once I get a chance.

Going entirely by memory, I think I had a few changes planned. I'll be reverting a few things on TW that should improve compatibility and smoothness. I don't remember what I have planned for AOSP, but I'll at least sync up with CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Thanks! Your kernel runs awesome for me! Only kernel that I can get 4 hrs or more of screen time. Thanks again & looking forward to an update!

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New 4.3 and TW builds! I'm calling both builds stable this time around. TW is long overdue for a stable build, and there (mostly--see changelog) don't seem to be any bugs left. CM hasn't been making dramatic changes to the kernel lately, so I think it's time to call the AOSP 4.3 build stable as well.

Between being out of town for a week and having a few other projects on the back burner, I haven't made many changes lately. The changelogs are pretty short, but new releases were overdue.

TouchWiz:

Reverted some video driver stuff that should fix flickering for those who are seeing it.

Temporarily re-enabled some ugly code that I plan on rewriting sometime soon. It should make everything smoother. Unfortunately, this code causes the bug where minimum frequency shows up incorrectly in tuner apps, so beware.

AOSP 4.3:

Merged lots of CM changes: some CAF stuff, Linux 3.4.60, and a few odds and ends.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
You rock man, two builds in single day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Touchwiz build not booting with fresh clean install, stuck at s iii screen.. Same problem with last build..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
Having that same problem, running s3rx 2.2. Really like this kernel, excellent battery life and smoooooth, but that issue is forcing me to stay with the ktoon kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Tw kernel not booting is since last two builds only... The 3rd last builds works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Strange. I haven't heard anything about this from the other carriers. :confused:

I think I know what's causing the issue though, and I'll put together a new build when I get home this evening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
Hey love the kernel, running latest touch wiz one. What's the syncthing governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
For aosp kernel do we require to disable mpdecision or this is required of freelunch is used?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Oops. I wasn't supposed to include that. It's an experiment I've been playing with. I don't remember how broken it is at the moment.

Not required. Disabling mpdecision will switch to auto-hotplug. mpdecision and auto-hotplug will be suspended automatically when freelunch is being used.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rocknmj:
I just flashed this this morning after the 4.3 build was declared "stable". Seems great as long as I don't try to OC. If I increase the max frequency at all, system will lock up and I have to reboot. I'm guessing it has to do with the voltages. So I'm just leaving it as is until I get time to play around a little more. Even at the stock 1512 max, it seems snappy and very responsive. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Some devices can't handle OC too well, and I believe the kernel comes with the voltages lowered than stock so if it locks up while OC'ing try upping voltages at the same time as well. If it still doesn't behave well then your device probably can't handle it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rocknmj:
Thanks. I'm thinking it is the lowered voltages on this kernel because I have used other kernels on other ROMs that oc'd just fine. I have to say that my battery is loving this as is right now and it seems very responsive. I'll play around with the voltages and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Same here, freelunch works wonders for me. Not OC or UC my device still doesn't handle the lowered voltages well so I had to up them. Good luck :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Anyone want to help me track down the issue preventing TW builds from booting? I threw together a build that should help narrow the issue down. It's available here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
Downloading now, will let you know how its working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
So far, so good. I have rebooted the phone with every combination I can think of, on charger, off charger, automatically with both tasker and titanium backup, using the reboot toggle in the dropdown, and using the physical power key. It has not hung at the splash screen yet. Only problem I see is the one you mentioned, where the minimum frequency is not being reported correctly. Using Performance Control, and both max and min freq says 1512.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Hooray! Thanks for testing for me. :good:

A new (fixed) stable TW build is up. There shouldn't be any noticeable changes compared to the previous stable build, except that this one should actually boot. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Hey man great kernel, loving it so far. I appreciate the hard work put into this. I have one question though, how do I change Trinity colors? I was using ktoons kernel and his tuner app came with it. I installed trickster mod but I don't see any color options, and I know it hassupport for it? Is there another app I should try? Thanks in advance.

Running pacman 9/23 nightly build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Trinity colors are supported, but it's not as easy to set as with KT's app.

Color settings are still available in advanced settings, but CM decided to remove the advanced stuff from the settings screen. If you're using Apex or Nova, you can create a shortcut to the advanced settings activity (Add->Shortcuts->Activities->Advanced settings->Advanced settings) and set color temperature to "Cold" (which is equivalent to trinity colors), and the ROM should take care of it for you from then on.

I think I can convince Trickster to set it as well. I'll look into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New 4.3 test builds!

Changelog:

Trickster setting to adjust color temperature*, since CM hid the advanced settings screen (which will still work, but is harder to get to than it used to be). The new enable setting doesn't actually do anything, but Trickster won't show the screen without it.

Prevent thermald from overriding OC/UC settings.

Touchscreen driver cleanups.

Synced up with CM.

* The setting in Trickster actually adjusts the intensity of the trinity colors adjustment, similar to how the advanced settings screen used to. 20 = "Cold" = trinity colors, -20 = "Hot".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Went back to 10.1 because of the recent stable release 10.1.3 and noticed that there are recent updates in 10.1 kernel since last dkp release for 10.1 branch.

Can we have the last update for 10.1.3 as this could be the last 10.1 CM release? Surprisingly, CM is committing on the 10.1 branch after 10.1.3 stable release, maybe 10.1.4 may come in near future
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Anyone have a mirror to the latest test 4.3. build (sept24) ? Devhost is completely down for me :( If no response I will just wait till it's back up, so no worries.

Edit: According to their twitter it was (and currently is) down indefinitely for everyone. Something to do with the datacenter. Hopefully its back up soon :good: https://twitter.com/DevHostOrg/status/382949598819414016
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarkSRT:
Sorry for this noobish question but is there a good read for customizing settings via trickster mod? I'd like to see what settings do what.. I've tinkered around a bit with trickster and So far the battery life is great with dkp aosp 4.3 stable and the newest nightly pacman ROM just trying to see how far I can push things.. Thank you for all the hard work :thumbup::thumbup:

Sent from my SAMSUNG-SGH-I747 Rockin' the newest PACman ROM Nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Ignore last post lol

Here's my battery so far...I used Firefox beta for over an hour with many addons too and listened to music for almost 40 minutes.

Pacman 9/23 nightly

Dkp 9/20 build, haven't flashed the test yet(wanted to see battery life on 2 cycles)

CPU at 1134mhz, Modified freelunch govoner, and UV'd decently with a rev0 CPU lol

I also use build.prop and init.d tweaks I nitpicked from ROMs I came across. :thumbup:

I also use greenify non-donation version to end all user apps when the screen is off. If you notice in the middle section of my battery stats it kind if dips down even tho the screen was off, I forgot to greenify some apps.

Not to bad and still have nice smooth performance except with emulators :p

And I'll probably get another 45 minutes screen on time with the remaining battery life.

Sorry for the long post I'm ocd big time haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It looks like it's just a small change for compatibility with newer devices. I'll get an update out sometime soon.

Dev-host is back up. It figures they'd go down while I was away from my computer and couldn't mirror the builds anywhere else. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Is it just me....dev host still not working

Never mind...I'm an idiot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Works for me. Are u trying to get to it on your phone?

Edit: dat ninja edit tho
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Lol thanks. I don't know what i did the first time. Long day I guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
Is anyone having an issue with audio making a cracking noise during playback?

I just installed the 9/24 stable tw version. I am running SRX 2.2.

Edit: I Installed the enable vmin hack and that resolved it. I want having reboot or crash issues even though I have a rev0 device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The last TW Kernel build is giving the best battery which i was not able to get even on stock kernel. Thanks man!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyanox:
I get superior standby battery performance on freelunch. Operational gives me superior performance on games and cpu demanding apps. I have noticed i keep getting random lockups and reboots, but i suspect my voltages are off.

Do you know of any good tuning scripts that will autotune voltages / speeds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I keep everything stock. What you mean by autotune?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stew1411:
Not sure if this a slim ROM problem or kernel problem. As it started after I flashed the kernel, I'm assuming the latter. Certain apps will max out the volume, and the volume control has no effect. Google music was one and most other music players also. The only usable media player that doesn't have this problem is vlc. Only a few games have this problem. Also adjusting DSP manager settings has no effect on sound. What do you think could be causing this?

Edit: using the 06/14 build. Using slim ROM 4.2.2 build 8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Edit: Snip, found 9/24 changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyanox:
For instance maybe a script that can start with testing voltages per each processor speed setting, start stock and drop by small increments, then run math or some sort of cpu intensive process, lets say crc verification. When the verification fails, you've found your lowest voltage allowable?

If that doesn't exist, I've just found my next project :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Now that you mention it, I think it's pretty common (possibly more so on rev0 phones?) for lowered voltages to cause audio problems. Some help I am. ;)

If you figure out the lowest voltage that doesn't cause it (you'll have to reflash dkp to undo the vmin zip), I have a fancier vmin zip that will set a custom minimum voltage. Let me know if you want it.

Update your kernel! There was a change to the audio configuration a while back, and if your ROM has it (Slim build 8 does) and your kernel doesn't (6/14 build doesn't), it'll cause this.

II only update the changelog in post #2 for "stable" builds. I'm lazy and it's a pain to update 4 threads for every build, so I usually just post a quick changelog when I announce the test build.

Do it! I don't know of any scripts to automate the process, so you should make one. I'm sure it would get plenty of use. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
I definitely want it. I will re-flash and raise the voltages to find the lowest without the problem.

What does the vmin fix raise it to?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Stock and unmodified CM kernels would normally run many phones with a 1150 mV minimum voltage, but on dkp it's reduced to 700 mV to make undervolting possible. The vmin zip resets it back to the stock minimum.

It looks like dev-host is planning on going down soon, but the custom vmin zip is here. I still haven't learned how to use AROMA, so the new zip uses a sneaky trick instead: change the XXX in the name, and it'll apply that as your minimum voltage (e.g. "dkp-vmin-1000.zip" would apply a 1000 mV minimum voltage).

Also, it feels like time for a new 4.3 test build.

Changelog:

Improvements to the color temperature setting in Trickster. Also, the enable setting actually does something now.

Removed tons of debug stuff from the wifi driver.

Some housekeeping and bugfixes. Nothing dramatic, just tidying up.

Synced up with CM (mostly), merged Linux 3.4.65.

EDIT: Clarifications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
I reinstalled the 9.26 stable TW version and the custom vmin at 900 and the clicking sound was still heard. I raised the voltage in 25mv increments until the clicking sound stopped at 950.

I have a rev0 device, so hopefully this will work for others as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Woohoo! A new-new build!

I'm still on Quantum ROM&Kernel but I'm really considering flashing dkp yet again...I was running it on an earlier version of Quantum and wasn't too happy with it but I feel like the feedback i've read lately may make it a different experience this time around...just need to learn how to tweak right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
@decimalman

May I ask why the voltages are inverted?

The highest frequency has a voltage of 900mV

And the lowest frequency has a voltage of 1350mV

Just curious :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'm guessing you're using SetCPU? I didn't test it, and it's the one app that expects the voltage table listed in a specific order. I'm working on getting several tuner apps working correctly, and I'll have a test build up sometime tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Yes. Since its one of the few that has screen off profiles.

No issues. Just had a hot boot if I tried to change the voltages.

Thanks on the quick reply :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New test build should get SetCPU working properly. If you get a chance, will you try flashing this test build and letting me know if it works for you?

The new test build also allows Voltage Control to set voltages, and keeps Kernel Tuner from hanging up when entering the CPU screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Voltages are now normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Do your stable builds support faux and trinity? On the exp builds phone boots fine. I can use it fine but once the screen goes off my display never wakes up.

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Read back for Faux and Trinity question ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Faux yes, trinity no.

Are you running Liquid as your sig suggests? I was seeing this not too long ago (on Carbon, as it happens), and my impression was that it was a ROM issue. A clean re-flash fixed it for me, and I didn't get a chance to properly debug why it was happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
OK after flashing the experimental on AOcP I also was not able to wake up phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I read every single post bro. Its kind of confusing because I thought only the test builds had the support for trinity and faux. So you uploaded new stable and exp builds to support the aforementioned?

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2

---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------

My bad im on the newest deviant xone.

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Ugh. Sounds like I broke something then. Is it the tuner-fixes build that's causing issues, or does the trinity-colors build do it too?

Edit: I rarely upload new stable builds. Both current stable builds have had faux support since before I started this thread, but the trinity support happened in an experimental build last night.

Two different phones with two different ROMs? This doesn't sound like a ROM issue anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
It was on the tuner fix, well the one that I flashed that didn't let me wake.

I would give you a log cat but no PC :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I made some pretty invasive changes to some things that I should know better than to touch. :o I'm not exactly surprised that it's causing bugs. I'll get a new test build up shortly that shouldn't break everything, and will still support Voltage Control and SetCPU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Awesome!

Take your time man!

Looking forward to the fix :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Give this build a try. It doesn't touch any of the CPU code. If it works, then I have a pretty good idea what I screwed up, and I'll deal with it tomorrow. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
That did the trick