[T-Mobile myTouch 4G Slide] cj chitwood:
Apparenty the BBCode in this forum doesn't permit tables, at least not that I've found. I tried a couple variations on the code I was able to Google (look at that, I actually do know how to do research) but they didn't work. They just showed up exactly as typed -- code.

Strapped, please accept my personal apology. I did not intend to offend you. I was, again, not meaning to read negatively. I was merely providing a suggestion that might prevent other people from asking that very question, "what's broke". I've noticed a tendency for devs to post lots of information basically advertising the ROMs' great capabilities and looks, but no real information on what is and is not working (unless you read the whole thread from the beginning and take notes). Sometimes a ROM thread's first couple posts will show one or two things not working, but if you want to know what's really not working, you really have to read the thread from beginning to end ----- which I myself have done from the beginning on this and about seven other threads. Even then, I still tend to forget what's currently working and what's not, and there's no way now I could go all the way to the beginning.

About the only thing I know for sure is that anything not based on Sense 3 and Gingerbread 2.3.4 will not allow me to use all my phone's hardware because nobody has drivers for the newer kernels to run stuff like WiFi tether, FM Radio, or 1080p video recording.

I remember the days when there were but a handful of Android devices even available to the public, when ROM devs -- like EZTerry, Roalex, Cyanogen himself, JesusFreke and a slew of others -- would actually update the first or second post to keep users abreast of changes to the ROM so they didn't HAVE to read the ENTIRE thread to see that oh, yes, the keyboard LEDs are fixed now. It was a kind of unspoken rule, a simply expected thing. I'm not a dev, and I noticed it. I'm not saying you don't do this, admittedly I don't check back on the first post that frequently (because once I try a ROM I just keep up with the thread to know what's working) but when I *do* go back to the first post and I see a buglist that's months old and has never been updated, or worse, doesn't list any at all when I know there are some (not yours, mind you)...

I'm sorry, but when I'm trying a different ROM that someone else suggested, the first thing *I* do is read posts one through "great work! downloading nao!" to see what's working or not. Then I try to read the full thread (unless it's over a hundred posts then I just catch the last 30 or so and lurk for a while before commenting). Then I download, flash, try it out, and if something's broke, I search the thread for other people with the same problem. Then I go back and read the buglis---wait, what buglist?

And actually, I'd love to develop a ROM and be like you guys who -- believe it or not -- I do highly respect. You people do in your spare time what would take me weeks to learn even the basics of, while using up all the time I could possibly find to do it, forget being as good at it as you.

But I do want to help, any way I can. I'd donate money -- that's the easiest -- except my employer doesn't pay **** and my bills are right there at the same level as my income. So that's out. If it wasn't for my in-laws, I wouldn't even have this phone -- I'd still be on my broken G1.

I'd offer to do development, except I can't dev yet (I do plan to learn eventually, as I do have some c++ and Java experience, just nothing recent) and don't have the time (more like the environment without distractions and clutter) to learn how. So instead of producing ROMs, I do what I'm capable of doing, which isn't much: trying out a ROM, finding out if it works or not, offering up my observations on battery life and functionality, and offering my advice for improvements from the perspective of a user.

I'd commit to help with thread maintenance if I knew I'd be able *TO* commit, but honestly, I never know when I'll have half an hour, five minutes, or all day to do anything, so I never make such plans.

Look, don't take my word for it, people love you. Look at all the one-liners about how "this rocks!" and "I can't wait to flash this when I get home!".

But you're right. I'm ungrateful, apparently, because I dare offer an idea that suggests something other than exactly what you're already doing. Forgive me for insulting you, it was certainly not my intent, but one thing I won't do is blow smoke where it don't belong to kiss up. If you don't like my comments, fine.

I've seen an increasing tendency among developers in the open source community -- not just Android. They seem to get a kind of god complex, where they think everyone beneath them should bow down to their greatness. They ask for input, they ask users to use their software, then they ***** when we say "this doesn't work as expected, that doesn't work as expected".

I damned sure don't want to piss off the very damned few devs we have for this device but I'm not going to kiss your ring to make you feel good. When you put your work out there for the public to see, some people may offer critique. It's NOT A BAD THING unless you make it one. I for one choose to take it as advice, or hell, even a feature request.

Thank you anyway. You've been great, you really have, and I actually do appreciate it and I still respect you. Good luck in your future endeavours.