From reading this thread, unless I've missed something, there's not a reason to keep the rilphone.dll paired with the radio it came with. It seems that the rilphone.dll really needs to be paired with the individual person's carrier?
If that's the case, it makes sense to document which carriers/features are supported by a particular dll. Are a few of them are friendly with more than one carrier? Obviously nobody needs to stick with the carrier specific dll, but it seems to offer the best compatibility.
If this is all accurate, then in most cases, it seems reasonable that a user should have the most recent version of their carrier's dll, and then experiment with different radios.
If the radios are essentially universal by design (previously stated that they support all features but just need the rilphone.dll to call them), then what reason exists for keeping the dll and radio paired up?
If this logic carries out, it seems the radio thread should have both radios and rilphone.dlls separate, with notes on carriers/features supported.
This raises another question, while we all know that radios from a few other phones will work on our Raphs, has there been any examination of using different rilphone.dlls? Is it possible/reasonable/stupid to take a blackstone dll, paired with a radio from the diamond, all together on the raph (I know it's possible, otherwise we probably would have discussed this much sooner). I'm pretty sure I know the answer to this also, but I don't see a reason that the rilphone.dll should have a problem with a security locked phone, so experiments there may have positive effects for them as well (since many people still aren't rushing to do the security unlocks).
