Quote:
Originally Posted by hurdpcs
powinmo,
I ran the test as requested. I made a call while Opera was connected and on a non-cached page. I am running the current version of 29007 version of Energy Cookie 2.0 ROM. It is running as close to original install as possible with the exception of 2 email addresses and contacts restored from PIM Backup. The carrier is Sprint and it is provisioned correctly. The BT headset operated correctly except for the attempt to hang up. No matter how many times I pushed the button it would not hang up. After that the softkey would not hang up and the hardkey took several strokes. Yesterday I tried disabling Sense. After I did that it would hang up every time.
Thanks!
|
Noted. Can you please try this test again with that method you claim where BT hang up works for you?
Quote:
Originally Posted by puff601
I tried thame test and my bluetooth hung up fine. I have noticed that there is a 2-3 second lag sometimes but it always hung up.  |
@puff - could you please try that BT test I was asking some folks to try for me?
Post 30084
Basically I'd like folks that have a "working" BT hang up environment to try my test of data usage prior to making a call and using the headset to hangup.
If you are able to get the headset not to hangup, then do the following:
a. after doing data acesss...
b. go to the Comm Manager
c. disconnect your Data Connection
d. go to your dialer, make a call to voicemail or someone
e. try to hang up via your BT headset
f. does it work? if so, repeat one more time
A few months ago I flashed two Sprint TP2s to the last known good STOCK SPRINT ROM. I did this same exact test and was *NOT* able to get the headset to hang up reliably. As reported in various other threads, even the stock sprint roms were not immune. So the issue is not ROM specific, but the crappy WidComm BT stack IHMO.
I was prepared to send NRGZ a BT headset to help pin this down on CDMA (Sprint) TP2 units. After my testing, there was pretty much nothing he could do for me (at least Sprint TP2 users).
One crappy solution where I was able to reliably get BT to hang up when I initiated a call:
a. I always run the Tarkim keyboard controller on all my TP2s.
b. I mapped the send/phone button to do a data disconnect and then bring up cprog.exe (the dialer app on Sprint/CDMA TP2s)
c. make a call, and I can hangup via BT each and every time.
Issues:
a. this does NOT help on all incoming calls.
b. not a solution for a true #777 data suspend which is what the WidComm BT stack should be doing prior to allowing a switch to 1xRTT to take a call. I cannot find a way to easily force this mode versus doing a full data disconnect.
I do appreciate anyone's help that tries the BT tests and posts results. Sorry for the long post
