Quote:
Originally Posted by Monfro
Tom Tom: Installing Tom Tom "broke" bluetooth in Rhodium NRGZ rom.
|
TomTom on any HTC device with the WidComm stack gets busted by a TomTom cab install for the past few years... esp since development on TT7 stopped sometime ago. Those files it installs by TomTom assumed the MS BT stack on target device. That's why I just stopped using TT and went with the iGO products, or Garmin for old times.
Quote:
Originally Posted by mdphoenix
The ONLY huge problem I have left - My Bluetooth headset. I cannot hang up from it. And trying to hang up from the hard key takes three or four presses. I'm going to read through this thread to find the solution as I've noticed others have had the same issue. Hoping there's a fix in the Wiki.
Thanks for all of your help on this. I hope my input is useful as well.
|
Quote:
Originally Posted by kyderr
28244 has been fastest for me as well. I like it, and it will be nice to see a new sense on that sys build. Hangup issues SUCK. It's the stack.. There is no hope. (Sniff)
|
Quote:
Originally Posted by kyderr
I gotta disagree there. I been having hangup issues (not hanging issues) related to BT on every NRG rom I have used for the last year. And I tried them all.
Are you thinking hanging issues? This is why I do not use CHT2.0 and I wish there was 1.8.5 still being cooked.
|
As pointed out in previous posts I wrote up: I installed the last known good STOCK SPRINT ROM on my TP2s a few months ago with task29 before each flash. I installed no apps and restored no prior contacts, settings, etc - as virgin as I could get it. I performed my data connection (IE page view or install Opera), make a call, then BT hangup test. I was never able to reliably hangup. Others in plenty of other BT threads saw the same thing.
It is the crappy WidComm BT STACK - not any particular custom ROM or combination of some CHT version or not. Just like kyderr mentioned. Even another user here was able to replicate this same issue a few days ago (search for the discussion within this thread).
For complete disclosure I tried these tests on a Jawbone Icon and BlueAnt T1, so headset did not seem to matter.
If you are able to BT hang up, it is likely because you have the right conditions of your device not being locked in to an active EVDO data mode when the call was initiated and was able to switch over to 1xRTT (#777 data suspend mode) for the BT command (hangup) to be recognized by your TP2. *edit* The main issue being, IMHO, the #777 does not seem to take effect all the time.