[G2 and Desire Z Android Development] Vlad83:
Come to think about it, I believe you are onto something. I never took into consideration the variable of holding the phone in a completely different manner… for the last month so. So the fact that my phone doesn't lose signal in my garage any longer should clearly be disregarded… even if it coincides with the radio upgrade. I also think I overheard the engineering professors talking about reducing the RF interference in the lab upstairs… This should explain the reason my phone has had signal in class. Oh and how could I have forgotten to take into account that HTC mostly likely changed the dBm reporting algorithm in the last couple of radios… this would explain the sudden spike. Last, and this completely escaped me, the fact that up to this point software radio upgrades by phone manufactures have had no impact on signal strength, data throughput, or voice quality… it’s not as if they send us a new internal antennae…

You are beginning to sound desperate as your arguments thin. The fact that I have reception in my 24 floor building garage which I previously had not; or that my signal has since become intermittent in class, whereas I had no signal prior to upgrading, is a clear indication of signal improvement. Furthermore, I took dBm measurements in a roughly 10x10 area in 3 different places. The mean and the median were both higher in all 3 places. Albeit, roughly 3-8 dBm but this still significant and warrants further research.

Now let me draw attention to your findings or lack thereof and the basis of your flawed argument. You conclude that a Sense radio should not be used with the libhtc_ril included in T-Mobile OTA or CM. However, in the OP of this thread where the MD5 hashes are compared, the Sense radio 26.04.02.17 uses the same libhtc_ril as does T-Mobile and CM. Furthermore, as schaggo pointed out, the radio 26.03.02.26 which is known as the T-Mo radio is included in RUU 1.34.405.5, which in turn makes it a Sense radio.

Moving on, your post #110 which takes a snippet of ril.h in Android’s git does not prove anything conclusively. To elaborate, ril.h is just a set of functions and variables that may be used by any vendor to create a radio specific libril_XXX.so On the other hand reference-ril.c is a generic, non-radio specific protocol using Hayes AT command set to communicate with the radio (any protocol can be used). Having said that, we all know libhtc_ril is the proprietary libril made by HTC to communicate with its radio that we have no source for. So here I beg the question, how can you determine what is in libhtc_ril or the radio itself by looking at a couple of variables? Sure, you would be operating within reason to make an educated guess, but you can also be wrong. This isn’t indisputable evidence here.

So now we arrive at your statements such as: “You are *not* ok switching radios, in fact, everyone needs to be running a t-mobile radio right now, with CM (and other non-Sense UI roms)….”, ”Look, it's not theory at this point any more…”… and I won’t even bother quoting your desperate last post.

First, let me make something clear; the latest libhtc_ril wasn’t playing well with almost all radios. Cyanogen(who himself was using 26.04.02.17) reverted back based on users’ reports. From the time I joined this conversation March 16 or so, I politely objected to you regarding your theory as an indisputable fact. I told you that further investigation was needed. I am strictly referring to flashing radio’s, not the libraries. Clearly, based on members’ reports experiences vary. It is a stretch for you to make such strong declarations in regards to flashing radios.