View Single Post
  #23 (permalink)  
Old 11-11-2009, 09:17 PM
dishe's Avatar
dishe
Halfway to VIP Status
Offline
 
Join Date: Jul 2007
Posts: 684
Reputation: 1184
dishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on repdishe is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Bounty for working MS Bluetooth stack on TP2

Mike- interesting find... so basically, the delay has something to do with the data connection? Your solution may not be acceptable for those of us who rely on the data always being on for things like push mail, etc.

I don't have a TP2 myself (yet) so I can't test anything, but it sounds to me like the stack is simply telling the radio to terminate a session, assuming that session "x" is a voice call. Does the GSM version of the Rhodium have this problem as well?

Maybe someone with some radio protocol knowledge and a CDMA TP2 can look into this, but this is what I imagine is happening:
If you initiate a connection (be it voice 1x or data EVDO), it may dynamically name the session (lets call it session X). If a data call was initiated first, and then put on hold for another session (a voice call), perhaps it is given another name to reference the connection (lets call it Y). So, when the Widcomm stack sends the terminate connection command, it *may* be trying to end session "X", and not getting any response since the call is on hold.
If no data call was initiated first, and the voice call ends up being "X", than it works fine.

This would also explain why a GSM version possibly does not have this problem (again, I don't know, I'm just assuming since I haven't heard of this problem before now)- the GSM radio does not put calls on "hold", since voice & data can be operated simultaneously.

By the way, most people consider the Widcomm stack to be far superior than the MS one in many ways (I was following and even contributed to some of the initial efforts to port it to HTC devices in the days of the Wizard and Tornado because of MS stack quality issues). As far as I know, this marks the first CDMA device to use the stack, and therefore it is very possible that they were unaware of this potential problem. If this is really the only problem you are having, I think you'd all be better off fixing it than ditching the entire stack for the MS one. The Widcomm stack is more efficient on CPU time as well as battery (look at the side by side tests done at pocketpcmag), not to mention dramatic sound quality improvement with things like A2DP stereo.

Hope this helps...
__________________
Techcitement.com - I write for these guys pretty regularly. A Blog about tech that makes people excited.
Diary of a Mobile Enthusiast - My personal blog... haven't had time to update it.... *sigh*
Hey, if I've helped you in any way, click the ads on my blog so I can make some $$!!
Reply With Quote