I don't know if this is a bug or what. But, when i am on my bluetooth "Jawbone Icon" for about ten minutes, give or take, my Bionic drops the bluetooth connection and switches over to handset. I can still hear my conversation through the bluetooth. But, I need to talk into the handset to be heard. To fix the problem I have to switch from "bluetooth" to "handset" and back to "bluetooth" to reconnect. Anybody else having this problem or similar??? Otherwise "Love my Bionic"
Related
Is anyone else experiencing this? My Jawbone headset randomly disconnects from my Kaiser during the middle of a call. I have to press the button to reinitiate a connection. I am trying to determine whether this is a compatability problem with the Jawbone and my HTC-labeled Kaiser. If you have experienced this, please post, particularly if you know of a fix.
i dont have this problem.
Using Jawbone, all day, every day since getting Kaiser, no issues like this.
Thanks for the quick response. Are you guys just using the built in Voice Dial or did you install Microsoft Voice Command?
I am using VC1.6 and have had no problems as you describe.
The only thing I saw is that sometimes, I am unable to initiate calls from the BT HS when the Kaiser goes into that weird "half asleep" mode after a call. But that has happened only twice and I have held 30min+ talks on the Kaiser + BT so far. No disconnections.
i have voice command installed and the only problem i have is if I get a sms or email it will drop the connection then i have to tell it to turn on headset again.
I'm running into a somewhat frustrating problem with making bluetooth calls on my AT&T Tilt.
(For reference, my Tilt has been reflashed with austinsync's 145mb bigstorage ROM, but the problem I'm going to describe ocurred on the original stock ROM, as well)
Periodically, when I make outgoing calls, the call will disconnect within the first minute. Upon watching the problem closely, I realized that my bluetooth kit (Acura HFL, preinstalled) always showed the calls as "Connecting" and not "In Use" when the problem ocurred. Any time the display said "In Use" I found the calls were not disconnected (unless I hit an actual dead spot)
What I've concluded is that the Tilt is not consistently setting the bluetooth flag that indicates that a call is in progress but, instead, conitnues to transmit that the call is connecting. For many bluetooth headsets, this is an irrelevant distinction; however, some handsfree kits (such as myself) will disconnect on their own if a call is not connected (or reported as connected) within a certain time. A variation of this problem has occurred with random calls initiated from my handset - in those cases, the call gets transferred to my handsfree only if I initiate a "transfer" command from the bluetooth kit; however, if the "call in progress" flag is not set corretly, the handsfree kit assumes that there is no call to be transferred.
In all cases, when my outgoing call was answered, the Tilt, itself, displayed that I was connected, and began running the timer. The problem seems to be limited to having that status transmitted via bluetooth.
I've already tested my handsfree with several other phones; the anomaly appears to exist with the Tilt only.
Incoming calls appear to be immune from this wierdness.
Has anyone else encountered this issue? I'm assuming this isn't a hardware problem but, instead, a bug in the BT stack. Any thoughts on a workaround? Anyone try Jetware with the TIlt/Kaiser? Any guess if that might solve the problem?
Thanks for any thoughts on this!!!
AMG
Spent an hour on the phone with AT&T and then HTC today - they were able to replicate the problem - So I guess there's a fighting chance of getting this resolved somehow, some day... Anyone here think there's a chance of a homegrown fix from this community??
BMW i_Drive has this problem
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on, and it stays that way until I do a soft reset. It also seems to freeze the BMW system. It is not every time, but often enough to be frustrating.
We W8z I guess
No issues on my 2003 5 series BMW. I'm running the HTC TyTN II ROM however. I wonder if this makes a difference...
Camstech said:
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on,
Click to expand...
Click to collapse
I've noticed an intermittent failure to connect on bluetooth on my Honda too. If I soft reset the Kaiser - I get a BT connection no problem.
Odd!- Lets hope some brightspark in these forums fixes it ASAP! I'd been blaming PhoneWeaver - Ooops
Graham
I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.
fermin said:
I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.
Click to expand...
Click to collapse
No luck. Whether it's connected to the power or not, screen off or on, no change in behaviour.
I"d like to chime in on this but I know I probably shouldn't, mainly because I haven't used the phone to make a call in my car long enough.
I had an '04 TL and my Tilt paired and worked fine on it. In the 3 weeks I had the phone, there was only one instance where the phone dropped its BT connection and I had to pick up the handset. All of my calls have been anywhere from 1 min. to around 5 min. I can't recall making any calls longer than that.
Just recently, I traded my '04 for a '07 TL. It paired up easily, voice recognition is a lot better, and my calls come in more clearly than in my older TL. Again, no conversations longer than 5 minutes. I may try to have a longer conversation on my drive home today to see the response.
Thanks for the heads up. I'll definitely keep an eye out for some of the symptoms you're experiencing.
I too have this exact problem. I have an '07 TL Type-S, and an AT&T Tilt. My phone worked fine until the 2nd official WM 6.0 release back in February, then it started exhibiting these exact symptoms. I'm now using Dutty's WM 6.1 and it is still happening but not as much. Hopefully we can get this fixed someday!
Does Bluetooth relate to the radio version? I wonder if I could get a WM 6.1 with an older radio if that would fix the problem?
Hi!
I have an ATT Tilt with the standard ROM, no ATT bloatware. I've installed Kaiser Tweaks & Phone Alarm. I also route Bluetooth sound to my mono headset.
My Problem is that when I don't have a cell signal, which is quite often, the bluetooth headset has a small beep every 10 seconds or so to inform you that there is no signal. This can get VERY irritating after a while. Is there any way to disable that beep? Phone Alarm has it's own warning, which I've disabled, but the stock beep keeps coming through.
I know it sounds silly to use the phone with no cell signal, but that's use is why I bought the phone. I use WiFi and VOIP to call home from overseas, along with the Garmin GPS program to get around.
I have googled and searched extensively, and I can't find anything.
Thanks in advance for any help I can get on this!
Hi everyone. I have had my Tilt for 4months now and it has given me a lot of joy. I have flashed and reflashed with no problems at all. I am currently using Schap's 4.31 Rom with 1.27.12.11 radio.
About a month ago i installed a new car stereo that has bluetooth connectivity with my phone - worked like a charm, paired very easily and generally appeared to be working with no probs.
Then i noticed that if i was in a bluetooth conversation and somebody else was calling (on call waiting), if i switched calls i could not hear anything, and if i ignored the second call, when the person on call waiting hang up, both conversations were terminated. I thought it was odd, but i just deactivated call waiting and thought, "let them try calling me later".
The other, a lot more serious problem, is that sometimes, randomly as far as i realised, the phone will go totally silent - incoming calls won't ring, and when i try to make a call, when i press "talk" then phone does not make that beep that it makes when an outgoing call is initiated. Should the person i call pick up i cannot hear them at all.
A soft reset takes care of this problem, but it has happened to me 3 times already, and i think it was after a bluetooth call.
Has anybody faced this problem before? I need to be available on the phone 24/7 due to my work and i really need to find a solution for this. Yesterday afternoon i took a nap for 45 minutes and had six missed calls that i never heard cause the phone never rang.
The phone is always on "ring" and at full volume.
Any ideas would be welcome.
Thanks
Alkis
Same issue
I'm assuming since I also am facing this same problem that it is not uncommon. It seems to me that it happens after a bluetooth device is turned off. Somehow it sets the volume on everything to mute. I thought only a soft reset would fix it until I discovered that it was just shutting off the volume. Still annoying, though.
Tilt problems with phone going silent
This problem has occurred with my phone every since upgrading to the WM 6.1 and it is related to a bluetooth device being hooked up. Often when someone calls the ringer will go from vibrate to on, but the volume turns all the way off. It will then cycle to off completely. The cycling occurs when a call comes in or when I hang up. I can stop this problem from happening by disconnecting the bluetooth head set. I have tried three different headsets and the problem occurs with all of them (Jawbone I, Jawbone II, and Plantronics) so I know it is not the brand of headset. HTC said to try a download of a screen dimmer problem, but have not done that yet. Anyone have any better advice?
did u guys ever find a solution to this?
its quite annoying missing calls because my phone decides to go silent for some reason
Same issue with GPS
I have the same issue, even when using software that accesses the GPS via bluetooth port. Muting is irritating, but at least voicemail catches messages. What really bothers me is that sometimes the mute is turned off and the volume up, especially when in a private meeting where we do not want interruptions
Gregg
HTC Tytn II bluetooth causes silent setting
I too have had the issue where my phone will go into total silent mode after using my bluetooth stereo hands-free feature. It doen't happen after using my bluetooth headset though.
It happens pretty regular that after using the bluetooth hands-free of my JVC car stereo that when I take the phone elsewhere it is totally silent. no ringer, no alarm (Ptravel alarm is what I use), no audio if I make a call (or receive a call).
It also will cause the phone to be silent on subsequent calls on the bluetooth stereo hands-free: ie: I take a call, hang up and another call will come in and I can answer it but have no audio.
My Tytn II is running the HTC (AT&T) WM 6.1 upgrade. The only thing I have done is use the Advanced configuration manager and the Kaiser tweak to change a few settings for performance and visual enhancements.
I see others are having the same problems.....Has anyone else used the tweaks and maybe that is root of the problem?
Has anyone discovered a fix (really important). My only options are to soft reset every time I get out of the car or not use the JVC bluetooth capability (which is why I replaced the stock radio in the first place).
Thanks
Hi rrackman,
I'd advice for you to look at the following thread:
http://forum.xda-developers.com/showthread.php?t=438457
It's quite long, so better subscribe to it and wait for responses. Several people with Tilt's have the same problem. Myself I have a JVC NX-7000 and an unbranded Kaiser (HTC TyTN II). It works fine with WM6.0, but I have the same issues you mention with WM6.1. First advice while we're searching for the solution: downgrade to WM6.0...
Regards,
Nika.
Is there a solution to this problem?
Try WM6.0 ROM - check out the thread I mention in my sig.
Regards,
Nika.
I did indeed take a look at the thread you linked earlier. Sorry for making the quick post earlier, I should have mentioned that this is regarding the "unexplained volume drop to zero" symptom, not the NSI symptom. Fortunately I don't have the NSI problem, just the drop to zero problem.
Of course downgrading to 6.0 would be the key solution, was just hoping to find a way to avoid doing just that. My phone never had the problem prior to 6.1 and was running the exact same list of applications and settings.
Weird issue with new HTC ROM (version no. below) - anyone else got it or know a fix?:
If I make a BT call with WiFi on, the BT crackles and flits every second.
If I turn off WiFi it is perfect.
If I set WiFi to 'Best Performance', all BT devices are lost and disconnect.
If I set it to 'Best Battery' or the middle setting, BT devices reconnect.
VoIP calls via Bluetooth now crackle themselves to death, because such calls use BOTH Bluetooth AND WiFI simultaneously - shock horror!
(Updated post above with VoIP issue)
i was having the same exact problem, took me couple days to realize it was the wifi. Only thing ive been able to do(motorolla s99 stereo) is make sure my headset is FULLY charged before pairing. And (no fix here) i shut the wifi off when im in the field. There is a bug there for sure. Is it just too much for the phone to track the 3g, wifi, and duplex on the BT?
CJSnet said:
Weird issue with new HTC ROM (version no. below) - anyone else got it or know a fix?:
If I make a BT call with WiFi on, the BT crackles and flits every second.
If I turn off WiFi it is perfect.
If I set WiFi to 'Best Performance', all BT devices are lost and disconnect.
If I set it to 'Best Battery' or the middle setting, BT devices reconnect.
VoIP calls via Bluetooth now crackle themselves to death, because such calls use BOTH Bluetooth AND WiFI simultaneously - shock horror!
Click to expand...
Click to collapse
I have exactly the same problem. BT works great with my headset (Plantronics 8XX) and has good range and is very clear. My WiFi works great and has a good range BUT if I have both turned on my BT is useless. BT devices are not visible more that 30cm away and there is a major crackle even at less than 30cm. Took me a while to work out why my BT headset would not pair with my TyTn II and Plantronics could not help. Used to work with my previous TyTn II OK, so I did a hard reset and then BT paired fine. Then I realised it was simply that hard reset turned off WiFi so I wasted my time doing hard reset when turning off WiFi was solution.
I called HTC and they can't or won't help but they did say they would log it and look into it (do we believe them? ;0).
The BIG PROBLEM for me is using SIP/VoIP as this uses WiFi of course but because of front speaker issues on TyTn II it is very hard to use without a headset and sound it just not good enough most times to use on my unit. So BT headset is the answer but can't work due to this WiFi/BT issue.
I am going to try flashing various different radios this afternoon as some members said this may help but from what I have read on this forum it does not solve problem completely.
If not then it's back to my wired headset and looking like an 80's teenager when I am using VoIP.
Also I wanted to install Navizon and earn points driving around with my WiFi on but this would mean no BT headset so I can't do this.
This really is an annoying bug.
If anyone has a fix or has found something searching the forums that my searches have not found then pls let me know.
Thanks.