[Verizon Samsung Galaxy S 4] Dubbsy:
1. While I will recognize and say that most if not all 4.3 aosp kernels will work on this rom, I can't provide support for them all. I'm just too busy. Feel free to post about it here though because others team members or not may know workarounds or whatever.

2. When android updated to 4.3 from 4.2.2 it killed damn near every audio and video app out. This is 4.3.1_r1 which while minor update from 4.3 is still a whole new version. If it wasn't they would have made it 4.3_r3.2 as that would have been logically next in line.

2a. That update for sure killed everything that had an assert that was looking for android build number "4.3"

2b. The reason I know that is I use that assert in my GAPPS that I make for the team and whoever wants them who beta test our builds prior to being aromized. The solution for my problem was simply changing the assert to "4.3.1". For apps, it may be a lot more difficult or depending the language it's written in they could use "4.3.*" or just "4.*" because 4.4 is coming soon. But from my understanding 4.4 is bring a whole new structure similar in how ICS and JB are similar but totally different development wise. I'm hoping it's not a drastic change and rumor that I've heard is that 4.4 is a button up type release. Basically a solid milestone of what they've been doing all these micro releases for.

3. I haven't had any lockups and I run mine pretty hard, in fact I remote into our devbox a lot on it and build straight from my phone. I've installed almost every xposed module that looks like it should work, to test if it does work so I can write up a list later. That in and of itself has been runniing it pretty hard also. Throughout everything the worst I've gotten was a delayed screen on button press.

Let me be the first to say, I've tried every recovery with the exception of the new philz. The only one I have not had a single glitch with has been 2.5.0.2. 2.6.3.0 got close...but the hang is not just the volume hold. Reboot to recovery from rom has nothing to do with the volume button. It's ashame because the wipe commands and general processes in 2.6.3 are far superior. But I need a flawless recovery for some constant for troubleshooting.

I am not a fan of CWM, as I've stated thousands of times. This is not because it doesn't work. It's not because it can't get the job done. It is because the layout has desperately need updated since the droid 2/x days. After a rom flash or kernel flash or freaking any flash you should wipe cache and dalvik... Put them on the same damn page as the back button. OR better yet, just do it automatically. But having neither of them on that page, or even on the same page makes it the worst for someone who is inexperienced. I am confident I can flash in any recovery and have no problem...I am not confident in the end users(no offense to those who are competent enough to handle it)

After all the extra oct settings I was planning to build a new Oct_TWRP recovery that is how I would do it. I've threatened it for awhile in talks with hlx/grom/trek but it's getting more necessary. It'll have a few themes and basically be laid out how it would make it ideal for a serial crack flasher. And it'll have the best wipe and clean scripts I can muster that could make even the dumbest user be able to flash a rom.

Not so much bad....but the hang is killer. The 2.6 wipe scripts are superior in every way... The fact that 2.5 and 2.6 backups arent compatible sucks some serious donkey wang though

Yep, freezed screen pisses impatient Dubbsy off

The volume button has nothing to do with a command given in the ROM to boot to recovery. Don't touch buttons lol.

Poweramp can be related to a number of things. the audio repos, the kernel revision number, the android version, really anything. without logs nothing is going to change it though