yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] decimalman:
It looks like the issues with the dialer are still caused by the voice processing chip and its buggy driver. I fixed one issue shortly after 4.3 was released, but it's not the only problem. As soon as the chip reports an error, the driver reboots it (which takes as much as 15 seconds), and the dialer has to wait around for it to reboot.

I'm working on rewriting the driver from scratch to handle errors (more) correctly. The chip isn't easy to work with though, so it's slow going.
[Sprint Samsung Galaxy S III] remotehugger:
OK I see - I do have the delay issue, but I also have sound issues as well - it got much better after un checking the noise reduction option but its still there - I'm sure its extremely time consuming to rewrite drivers - I can't even imagine - but either way, am definitely looking forward to your next 4.3 release -
[Sprint Samsung Galaxy S III] decimalman:
Can I get you to test something for me (assuming you're running TW 4.3 right now)? The new voice processor driver seems to be mostly working, but I don't want to officially release it without a little more testing. Will you turn noise reduction back on, flash this test build, and try placing and/or receiving calls? I'm interested in a) whether the dialer still lags like crazy, b) if call quality is improved any, and c) if anything crazy happens.
[Sprint Samsung Galaxy S III] remotehugger:
yea, hang on a few - will dwnld on my PC and flash - well, gotta do a backup first, but wont take long - let you know in a bit -

Edit : Ok, flash went good - got the light bulb splash screen - when first opening my dialer i had about a 30 second freeze up but it finally opened - after that it opened instantly - dialing was fast and it connected quickly and call quality seemed better with noise reduction on - powered off phone and after restart got the light bulb splash screen again, and it looped once before finishing boot - took dialer another 30 plus seconds to open again but after that was instant - also got a "messaging has stopped working" and "hangouts has stopped working" toast notification - but they are in fact working fine -

did anpther reboot and got all the same thing as before - light bulb splash screen - one loop before finishing boot - long delay on opening dialer and toast notifications of those 2 apps not working -
[Sprint Samsung Galaxy S III] decimalman:
Thanks for testing! I was hoping the new driver would behave better than that, but I guess it's a start. Do you have a terminal emulator app installed? The new driver does a lot of extra logging, so a dmesg ("su -c dmesg >/sdcard/dmesg.txt") after the notifications, a call, and/or the dialer freezing would help a lot to track down what's causing problems.

The splash screen gets picked when flashing. Unfortunately, there's just not enough room in the ramdisk to pick a different splash screen every boot.
[Sprint Samsung Galaxy S III] remotehugger:
Tried to get log with Ron Toolbox Pro but it said "c not found" ?? Did I do something wrong ? Should look like this rite ? -c dmesg >/sdcard/dmesg.text

Edit : lol - just rebooted and didn't have any issues - lol - dialer opened almost instantly -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
Of course the problem just disappears as soon as you try to debug it. :laugh:

Looks like you're missing the "su" in front? "su -c" executes a command as root.
[Sprint Samsung Galaxy S III] remotehugger:
Yea, I was typing su then pressing enter, then the rest of the command - got it now - when/if it happens again, I will def. get a log - but yea, of course it stops when it knows I want a log - lol -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] 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.

Skipping the "-c" bit and entering it as two separate commands works too. Of course, I'll have to break something first. How does a new TW4.3 test build sound? :laugh: I fixed a few issues and the hardware is complaining a lot less, so it might work better. Either that, or it's broken completely. :p

Looks like a few other people grabbed the build I posted earlier. Any crazy dialer bugs to report?
[Sprint Samsung Galaxy S III] remotehugger:
Just dwnld test2 - gonna flash now - haven't had any other issues on first build - haven't rebooted though either - lol - will report back after flashing test2 - and thank you - :thumbup::thumbup:

Edit : just flashed test 2 - no loop this time - no freeze up when opening dialer - sound still seemed to be better - I did have a toast notification that hangouts stopped working - I got the log from rite after it happened but don't know how to post it here for you ?? Oh yea, got the gears splash screen this time !!!!

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
YGPM

Sounds like things are moving in the right direction. :) I guess I should reinstall Hangouts so I can actually test it.

Sounds like a splash screen from [MENTION=4011253]ZDeuce2[/MENTION]. Head over to the TMo thread and give him a few thanks!
[Sprint Samsung Galaxy S III] cbrox:
Thanks decimalman!

TW4.3 test build 2 working excellent so far, running it with Daze's 4.3 v4.

Deep sleeping with no issues.

Hangouts is working for me without any issues.

Once again thank you for your hard work and efforts!
[Sprint Samsung Galaxy S III] rdavis429:
Tw4.3test build 2 is working great on MOAR 8.0!
[Sprint Samsung Galaxy S III] remotehugger:
YGPM ?

I'm beginning to think hangouts is my issue and not kernel related - even though it says it stopped working, I have no issues with the app at all - and been running test2 since release last nite with no issues at all -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] ksmullins88:
You've got a private message...

Aosp test kernel working wonderfully here. Installed last night and had a hiccup but all is well and battery life is through the roof.
[Sprint Samsung Galaxy S III] decimalman:
"You've got [a] private message." Looks like you already saw it.

Hangouts shouldn't be using the voice processor at all, but you never know what Google's up to. The log you sent me doesn't show the driver exploding and taking Hangouts with it, so it might just be Hangouts acting funny.

Just to be clear, does "no issues at all" include the dialer and sound issues you were having before? If they're fixed for you, I'm going to link to the test build in the Q&A thread about the call delays. With any luck, it'll work for them, too. Again, thanks for testing for me! :good:
[Sprint Samsung Galaxy S III] remotehugger:
YGPM - DOH !!! Lol - but yea, no issues includes dialer and call quality - almost no delay at all with dialer and call quality definitely seems better - could be a placebo effect but I don't think it is - and like I said, I'm thinking hangouts isn't being wonky from your kernel, its just being plain wonky - if you need anything else checked out, just let me know - glad to be a part of it and help in any way I can - :D

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] upconvert:
You know, you can add d2vmu to your signature. Your kernel works great on my Virgin Mobile gs3!
[Sprint Samsung Galaxy S III] marcran75:
Decided to give the newest test build a go and I'm not getting good results. Kept getting ramdom freeze ups and reboots. The short amount of time that my phone was functioning properly I kept getting constant "unfortunately........" msgs. Had to revert to a nandroid because my phone was unusable.
[Sprint Samsung Galaxy S III] decimalman:
Strange. I haven't changed much that would cause problems, so there's two possible explanations: either SELinux is acting up again (I disabled a workaround for the current build) or the new toolchain isn't working well with TW (it wouldn't be the first time a new toolchain caused problems).

I'm running TW at the moment, and assumed that the instability I was seeing was from removing a few too many system apps. I'll try a few things later today to see if I can get it working better.
[Sprint Samsung Galaxy S III] marcran75:
Thought it might be due to my tinkering but I was using the same settings that I'm using with 1/26 build.
[Sprint Samsung Galaxy S III] cbrox:
Mine ran good overnight with TW4.3-test-build2, but this morning when i rebooted to recovery to transfer some files from my pc to my phone and then booted back up the freezes started. Though I have to say even with the freezes it's still getting good battery life. Better than what i got with 12/26 and 1/26 TW versions
[Sprint Samsung Galaxy S III] rdavis429:
I've also had the random freezes and lockups. I just reflash and reset all my kernel settings. Will see if problems continue.

Uodate: Flashed back to 01/26. After I made my last post, the phone rebooted on me again. :(
[Sprint Samsung Galaxy S III] remotehugger:
Yea, I just started have some issues too - I noticed some stuttering so I cleared caches and rebooted - tons of freezes, lots of "stopped working" toasts including "Touchwiz Home has stopped" - and got the "preparing network" notification in my pulldown bar at the top - usually only get that when updating prl and profile - gonna restore my nand - will gladly test anything you need tested - also, haven't touched any CPU settings - no OC or UV - I was using so/freelunch if that matters -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] rdavis429:
I was also getting "This process has stopped" message.
[Sprint Samsung Galaxy S III] ebildude123:
No problem with DKP on 4.4 carbon. Thx.
[Sprint Samsung Galaxy S III] remotehugger:
Is that a TW ROM ?

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] rdavis429:
Nope, AOSP.
[Sprint Samsung Galaxy S III] remotehugger:
I was thinking it was but wasn't sure - thank you -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
For anyone having issues with the TW test builds from last night, does this build work any better? I haven't gotten any FCs or random freezes in the couple minutes I've been running it.

EDIT: Also, thanks to xstefen for generously providing hosting for dkp! No more ads, no more bogus APKs downloading, and super-fast downloads. :)

EDIT 2: Okay, still ads, but hopefully no more bogus APKs at least. xstefen is looking into the ads. :good:
[Sprint Samsung Galaxy S III] ebildude123:
Still ads lol :)
[Sprint Samsung Galaxy S III] decimalman:
Oops. I guess I should turn off ABP before I say things like "no ads." :o

EDIT: xstefen removed the ads. :D
[Sprint Samsung Galaxy S III] rdavis429:
Testing now

Update: So far so good. I flashed, let it set for about 10 minutes then applied my favor settings and waited again. Rebooted the phone again, settings stuck and so far no lag or lockups.
[Sprint Samsung Galaxy S III] marcran75:
Running test 3 now. The issues I was having with test 2 started immediately after boot and even though I've only been using test 3 for about 15 mins I'm not having any of those issues. Will report back after it's had some more time to settle.:good:
[Sprint Samsung Galaxy S III] decimalman:
Test 3 has the old SELinux workaround enabled again. I was really hoping it wasn't needed anymore, but it sounds like it is. :(
[Sprint Samsung Galaxy S III] enzoevo:
So is the permissive ramdisk included along with init.d and boot animation? Sorry if this is obvious.
[Sprint Samsung Galaxy S III] decimalman:
The new installer isn't fancy enough to do that yet. Right now, it just does splash screens.
[Sprint Samsung Galaxy S III] ksmullins88:
Best battery I've had on Kit Kat. No errors or reboots. Running the aosp test on beanstalk.

Kudos
[Sprint Samsung Galaxy S III] decimalman:
I had to leave a job that was doing similar things to me (mandatory overtime is legal and unregulated here), and it's absolutely not a dumb move. Seriously, it was the best choice I've made in recent memory.

The nightlies should still be on 3.4, and 1.6 (but not 1.6.1) was 3.4 as well.

Hmm. Let me grab the ROM and see what's going on. I do some sneaky things to avoid having to build my own ramdisk, so it's possible that I need to make a few changes in order to support Liquid.
[Sprint Samsung Galaxy S III] st0neski:
I was able to install the cyanogen nightly rom and it booted fine, then I just re installed liquid and it got pas the boot problem.
[Sprint Samsung Galaxy S III] jfcooley:
I'm on 1.6.1

I'll live. The 3.0 works well enough. I can't (and shouldn't) complain.
[Sprint Samsung Galaxy S III] Jimmy_Christ:
Thanks for the feedback. I bought the trickster pro key.

Sent from a van down by the river.
[Sprint Samsung Galaxy S III] das_webos_transformer:
To clarify,
[Sprint Samsung Galaxy S III] ksmullins88:
I'm running liquid in the newest nightly with this kernel. Works fine for me. I keep going back to it.

Ps. Can you link me to trinity colors? I'm trying to find it but that would awesome.

Do I have to download that app for 3 bucks?
[Sprint Samsung Galaxy S III] decimalman:
Check the OP for dkp-enable-trinity.zip. All the 3.4 test builds and at least the newest 3.0 test builds support it.
[Sprint Samsung Galaxy S III] ksmullins88:
I grabbed that. And the latest nightly. I flashed the vmin, trinity, and then the test build.

Is it enabled now? And can you adjust it?
[Sprint Samsung Galaxy S III] decimalman:
Trinity should be enabled, but vmin needs to be flashed after the kernel. You don't want vmin enabled unless you really need it though. Depending on your processor, it'll increase voltages and possibly disable undervolting.

You can turn trinity on and off on the fly, but there's not an easy way to do it. If you have a terminal emulator app, enter:

su
echo X >/sys/class/mdnie/mdnie/trinity_colors

where X is 0 to disable and 1 to enable. You'll have to turn the screen off and back on or adjust brightness before it takes effect.
[Sprint Samsung Galaxy S III] jfcooley:
Finally on the 3.4, with my beloved so/free lunch combo

Hoping Carbon gives me the same battery life I got with BB8.

Toying with going to tw. I honestly can't give up this kernel though.

Day off tomorrow. Spending with daughter, but will run this thing into ground to see how it holds up.

Benches nice though.

As always, thanks.

Edit: been playing and it seems trickster won't hold settings on the 3.4 test kernel. Is it just mine?

Edit 2: seems setting delay on boot to around 20-25 seconds fixes the set on boot. (Found on Trickster g+)
[Sprint Samsung Galaxy S III] ksmullins88:
thanks decimal. I'm sorry about all the confusion. I got it to work. And it really does look amazing.

I thought there would be controls like how voodoo used to be :rolleyes::rolleyes::thumbup: my bad for being a noob

Mine holds settings just fine. Only set delay to ten seconds.
[Sprint Samsung Galaxy S III] 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.
[Sprint Samsung Galaxy S III] cbond007:
What can I do to stop my music from stuttering when the screen is off?

Sent from my Paranoid Android
[Sprint Samsung Galaxy S III] jfcooley:
What player are you using? I know power amp has a setting to fix skipping.
[Sprint Samsung Galaxy S III] cbond007:
Player pro

Sent from my Paranoid Android
[Sprint Samsung Galaxy S III] jfcooley:
I'd have to download that later and see if I skip as well.

No issues with power amp, but check pp settings and see if there is a buffer setting. Increase it a little and see if it helps.
[Sprint Samsung Galaxy S III] Papa Smurf151:
FYI invade you wanted to update your op...pacman only works with your test kernel right now. We have incorporated the new drivers that cm pushed the other day

XDA Moderator
[Sprint Samsung Galaxy S III] decimalman:
I added a note about it to the OP. Thanks for keeping me updated! :good:
[Sprint Samsung Galaxy S III] jfcooley:
Think I'm going back to BB8 and the 3.0.

I can't get trickster settings to stick after boot and with carbon nightly its too choppy.
[Sprint Samsung Galaxy S III] CNexus:
Late, but they both look awesome :D
[Sprint Samsung Galaxy S III] rdavis429:
Just got my first random reboot and then bootloop. :( It took awhile for it to happen though.
[Sprint Samsung Galaxy S III] decimalman:
The new build definitely still has some issues. :( I'm going to look into it sometime tomorrow.
[Sprint Samsung Galaxy S III] rdavis429:
You're still awesome! 01/26 will carry me till a more solid version pops up.
[Sprint Samsung Galaxy S III] wyelkins:
Has anyone had problems with the 4.4 version? Not me.
[Sprint Samsung Galaxy S III] marcran75:
Test 3 still running great for me. I haven't gotten the "no connection" msg while on Wi-Fi yet either.

Edit: Spoke too soon. Just got a few freeze ups and "app stopped" msgs have started again:(
[Sprint Samsung Galaxy S III] starlightfox:
I've been running it since Tuesday and have had two random reboots. Once while using navigation and once while the screen was off and in my pocket. Both stuck at the DKP screen and had to pull battery and turn it on again for it to boot properly.

Other than that though, running smooth and great battery life with freelunch. :cheers:
[Sprint Samsung Galaxy S III] sinisin:
I have the same issues even on stock CM kernel. It's not kernel related unless it's in the kernel source. Either way I don't think it's related to this kernel or any other devs kernel either. It's a CM on the S3 issue.
[Sprint Samsung Galaxy S III] remotehugger:
flashed test 3 last night and have same issues as before - dialer and call quality still good but still freezing up and getting "stopped working" notifications - and again [MENTION=4932679]decimalman[/MENTION], thank you for all the time and effort you are giving this - I'm sure you will get this hammered out - :thumbup::thumbup::beer:
[Sprint Samsung Galaxy S III] wetbiker7:
No issues at all with the newest 4.4 AOSP build. It's running great with both Carbon and CM11. I've been running it hard since the kernel came out and it's performing nicely.

Sent from my SPH-L710 using Xparent Purple Tapatalk 2
[Sprint Samsung Galaxy S III] upconvert:
+1 to that. The 2/13 AOSP kernel has been rock solid for me with Carbon.
[Sprint Samsung Galaxy S III] Mr. Struck:
Agreed, same setup-newest dkp kernel on Carbon, newest build for d2spr. Super smooth and fast!
[Sprint Samsung Galaxy S III] remotehugger:
Wonder why TW is so different ??? I'm sure there isn't an easy explanation for that question - lol -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] marcran75:
I've actually got 2 S3's. One I use and one I have as a backup. Running CM11 on the backup phone and AOSP run great with it. Haven't had a single hiccup with it since I started using DKP. TW 4.3 has been giving me all sorts of issues.
[Sprint Samsung Galaxy S III] remotehugger:
Yea its odd, TW just play nice yet -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] rdavis429:
TW I've notice is a special kind of monster.
[Sprint Samsung Galaxy S III] decimalman:
Yup. It's still based on a version of Linux from almost 2 years ago, and the age difference is making it progressively harder to move code between AOSP and TW. It also seems much easier to break than AOSP kernels.

Before I go crazy and revert a bunch of things, let's see if this TW 4.3 test build works any better. I switched back to the Linaro toolchain I was using for previous builds.
[Sprint Samsung Galaxy S III] rdavis429:
Downloading now. Will let you know how it goes. :)
[Sprint Samsung Galaxy S III] remotehugger:
Also dwnldg, can't flash till after 3 but will report back then -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] cbrox:
Flashed TW.4.3 test 4 , so far everything running smooth. No issues yet, running it with wicked 4.3 v4. Dropping in and out of deep sleep with no issues. Overall a smooth ass ride!
[Sprint Samsung Galaxy S III] rdavis429:
UPDATE: Been running smooth since download around 3 and it's now almost 6 and still no problems. Just applied my preferred settings and will report back soon.
[Sprint Samsung Galaxy S III] 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.
[Sprint Samsung Galaxy S III] remotehugger:
Is this the same build as test4 ? Been running it for only about an hour but so far it has been OK - dialer still good and cal quality still good - but if the new builds going up are different I will move to that one - and ty so much for all your hard work !!!

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] decimalman:
Nothing is dramatically different. I swapped out one of the splash screens and built with a slightly newer compiler.
[Sprint Samsung Galaxy S III] remotehugger:
OK thanks - I'll still grab it since its the latest - easier for you if anything should happen - also, what app, if any, would you recommend for CPU/UV/OC manipulation ? Been using RTBP but sometimes settings don't stick - just curious if there is a preferred app -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] marcran75:
He says in the open "I go out of my way to support Trickster Mod" and it works well for me too.
[Sprint Samsung Galaxy S III] remotehugger:
thank you - i honestly wasnt sure what the Trickster Mod was - lol - i had heard of it but never checked it out - gonna have to do that now though -
[Sprint Samsung Galaxy S III] rdavis429:
[/COLOR]Deleted
[Sprint Samsung Galaxy S III] remotehugger:
Been running newest TW 4.3 since posted - no problems so far - dialer and calls still good - can I ask what most use to check battery stats like wake locks and such ? Not sure but seems like I'm getting some battery drain - not sure but would like to monitor it for a bit - haven't messed with CPU settings but am running sio/freelunch -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] tmcwilliam01:
New TW working great for me. The 1-26 was also good for me. I had no issues with call lag or sound. This one does appear to be sleeping better though. Thanks for the TW love.

I've got MOAR!
[Sprint Samsung Galaxy S III] remotehugger:
Been running latest since last nite - all seems good - I am curious about entropy levels though - mine are at 0 according to the entropy checker from play store (see screenshot) doesn't seem like that's rite - and it doesn't move at all, it stays at 0 - any ideas ?

From my GSIII - jd's Stock/Rooted/Deodexed 4.3
[Sprint Samsung Galaxy S III] remotehugger:
And the reason I checked entropy was because I'm noticing some stutter when swiping through my home screens -

From my GSIII - jd's Stock/Rooted/Deodexed 4.3