[HTC EVO 3D] agrabren:
Ok, let me go over a few things real quick, so people know what's happening and why...

1. Data connection - Yes, the GSM build definitely has a problem with data dropping, I've experienced it as well, haven't debugged it yet, but I have some suspicions on it.

2. Kernel issues - This is the tricky one to explain. Both builds (GSM & CDMA) have bugs with their respective kernels, which are different kernels. I'm trying to get this resolved quickly, since development against an unstable ROM is very difficult. Why have I stopped developing my own kernel? Because there are plenty of great kernel developers helping out for both devices, my skills are better served working on the ROM itself. While the pretty picture explaining what a kernel is may give a false representation of respective size, the kernel is by far the smaller component. Further, because the majority of the kernel is pure linux, most changes are directed only at drivers and board configuration, with a few changes going to well-documented interfaces for handling things like CPU frequencies. This doesn't mean kernel development is easy, it means that it has a much tighter area of focus and is 100% open-source. The ROM, on the other hand, has a cascading design which means that a change to one piece (such as audio) has far-reaching affects like camera and graphics. And many of the interconnects are in closed-source components, making it very difficult to debug or fully understand. Since we have quite a few talented kernel developers, I feel my knowledge of the whole stack is better served delivering AOSP instead of kernel improvements for now. And trying to do both at once leads to a lot of feature requests and time sinks on me that could be better used making the ROM better. But that transition has encountered a few minor hiccups and broke Bluetooth, as well as broke some CPU governor controls. This is making ROMs run too fast and cause reboots. So I'm working with the kernel developers to get stable builds that are AOSP-compliant and ready for Jelly Bean. This has to be my #1 focus, because I can't debug broken devices.

3. CDMA Support - I'm not officially supporting CDMA, but that doesn't mean I'm not fixing bugs. You'll notice that I have not created a CDMA thread for this ROM, and that I continually ask for CDMA users to please refrain from asking CDMA-specific questions in this thread. To be nice, I tossed WiMAX into the CDMA Jelly Bean builds, but don't really care to find the long-present bug of why it doesn't report "4G" in the bar. Mostly because my WiMAX coverage here sucks, so it's very hard to debug, and for little benefit. I'm sure it's trivial, but *finding* it isn't. Somewhere, there's a mismatch in how the current signal type is reported.

4. Trolling - Yes, I enjoyed my little explosion, but that doesn't mean it was right. Thankfully, the moderators are kind enough to recognize both that it's my first offense (although second time banned... Anyone who went to last years BBQ may remember the sign-up sheet for being banned. If they do it again, expect me to be banned again this year) and that I do try to contribute to the community. Sprint users in general should take some time reading around in the GSM threads and see how the "other half" acts and responds to developers. I wouldn't have believed the difference if I hadn't come over here myself to help GSM users.

5. Version Numbers - If there's anything important, I rev the version number. Otherwise, it's a pain in the butt and I don't do it. So if you really care for the latest cutting-edge, may not even boot build, you can check the timestamp. But otherwise, if the number hasn't changed, it's not worthy of upgrading.

Hope this helps.