Quote:
Originally Posted by sfaure03
The habit of checking for new feature/application cross checks requests. I'm working solely on the bt issue ponicg. The comment was not intended to be rude, only that I saw you're request, and rather than just blowing you off, figured i'd tell you that i wouldnt persue it. I had responded to you before that I was not focusing on testing this kind of feature implementation, and you returned again asking me to again test it. I simply cannot "get into the habit" of cross checking against other issues especially when they are features that the original rom did not support.
You're comments that "this would only take a couple seconds" NEVER turn into a couple seconds, indeed they often take up days once you start down the path, and I need to stay as focused on this as I can.
Sorry you took it wrong. I do NOT think this is the only problem with the ROM, but i DO think it is a SIGNIFICANT ONE, and it is the ONE i am trying to find a fix for, and what we're addressing here.
If this fix also has the side affect of fixing other issues, yes i would like to see and hear about that. But its not my INTENT to track down every possible combination people come up with. This approach and focus has been stated and restated in the thread many times. The "habit" i cannot get into is to be distracted by other requests. Sorry you took offence, it was not intended as such.
|
Shawn,
My apologies then too. I took offense to it based on tone - In retrospect(hindsight
is 20/20... bleh) I should have realized that internet posts have no tone and not read into what you wrote. I also could have responded differently. I appreciate the apology and offer my own apology, as well as an offer to help in any way I can. I write .NET software for a living, and have been dabbling recently in the .NET CF. Perhaps if we determine that the bluetooth issue is related to comm manager, I can help build a replacement, depending on how easy it is to touch the drivers w/the .NET CF.
The only reason I felt that my issue was related to yours is that they both related to the bluetooth stack on the device. Regardless of whether they're inter-related, it really would have been a two-second check. You'd click the COM Ports tab, and read that 30 word page for the word "incoming" - If you didn't see it, you'd know that it wasn't fixed. I had someone else check it, and indeed it does not fix this issue. I still intend to install it tonight and see what happens.
-George