Does anyone else have this problem...?
I've just got an HBH-662 for the Universal and it pairs fine and can make calls, but answering calls it doesn't work properly.
The headset recognises incoming calls and rings okay, but when you press the button to answer the call, it doesn't put the sound through the headset, only through the phone.
Maybe it's a setting I'm missing, but it's a tad annoying!
F.
I'm not sure I can help much, but I have no problems with my HBH-662 and my Jasjar.
Brett
I too have no problems with the HBH-662 and answering calls.
Will give it loads of testing later and see if i can get it to act the same as yours
I have been using HBH-662 with JJ for few weeks and in general I have no problem. I just wish that the Caller ID issue (the ability for the JJ to send contact name to the BT headset instead of number only) is resolved very soon.
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
How strange. It seems to have sorted itself out!
I paired my old BT330 to compare it, it worked fine, so I removed the Akono and re-paired it and it seems to be working.
Thanks for the comments folks, it's useful even though you didn't get the same probs!
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
And who really remembers the numbers of their friends these days?!
F.
fergusstrachan said:
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
Click to expand...
Click to collapse
It does provide CallerID name... but only with certain phones WM phones being among those that don't provide name information. It's my understanding that the problem lies in the bluetooth stack on the phone and not with the headset. I did see a post a short while back that suggested the issue was being worked on and would be resolved in a ROM update, so I have hope... but I'm not holding my breath.
Brett
Hehehehehehehe.
Microsoft 'working on' the bluetooth stack...
hehehehehehehehe. Sorry. I just find that really funny. The idea that MS are actually working on anything to do with the BT stack on WM!
I don;t really understand why it takes so long to program a bit of BT to provide something like that (or, say A2DP!). I mean, how hard can it be?
Well I'm not a programmer so I won't moan.
F.
Splatt! said:
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
Click to expand...
Click to collapse
Any more comments if Sony Erickson Akono BT headset HBH662 really clashes with magic button and handy menu?
Related
I apologize if this has been discussed, but I'm hoping someone can point me to the thread or re-cap the workaround.
Every so often my HBH-300 drops the outgoing audio during a call. It usually happens 30-60 seconds into the call. Basically, I can continue to hear the person on the other end, but they can't hear me.
I'm using the recent 1.33.51 ROM with Radio 1.08 and BT3900 drivers. I've tried the 1.10 Radio and still experienced the same one-way audio issues.
Any suggestions would be greatly appreciated! Thanks in advance!
Same problem here, it is not the headset as it works fine with a XDA II.
By the way mine only does this when the screen shuts off, as long as I keep the screen active (tap on it from time to time) then it doesn;t happen...
A fix would be nice, but don't hold your breath for Imate/XDA (HTC) to fix it, they never got BT working right with their previous phone/pda either....
Hello. My first posting. I have looked to see if this has already been asked.... After using mute or vibrate function on my XDA 2s unit, and then switching to making a call or trying to receive a call I can't hear the dial tone, or the other person on the other end of the call. I can only make and receive calls once I soft reset the unit. This is becoming a regular occurence. Any ideas would be much apprecaited.
Craig.
same problem
I also have same problem. my XDA IIs often have a problem with the incoming/outgoing calls which is I can't hear the tone nor the person's on the other end of the call (but the person on the other end of the call could hear my voice). It often (not always) happens without the device had a recent setting change or running program so on one occassion it just handles the calls perfectly and suddenly the problem happens and I also have to soft-reset it to make it back to normal, and it is becoming regular.
This is unfortunately a well known bug that none radio upgrade could solve so far...
Look at : http://forum.xda-developers.com/viewtopic.php?t=40417
The problem seems to occur only when Bluetooth is off... So the solution is to turn Bt On (and then off if you wish so) and it's ok without soft reset...
The best way to avoid it is to let Bt ON but to uncheck "Allow other devices to detect me" (forgive me if the english translation is not accurate but my PocketPC is in French) in the Bt parameters to avoid power consumption.
It worked for me so have a try
Hi All
Im wondering if any of you guys can help me.
I regulary use TomTom on my XDA Orbit and also use the speaker phone to talk on the phone as I drive. I have a problem when I receive an incomming call wilst running TomTom. The notification appears on the bottom of the screen telling me the is an incomming call, but Its a bit difficult getting from TomTom to the phone screen to switch on the speakerphone, without either dropping the call or quickly answering the call, then quit tomtom, then activate the speakerphone. I dont want to use the supplied headset and i dont have a bluetooth headset. Can anyone give any tips? Maybe a taskmanager wich cyles through the active programs using one of the buttons on the side of the phone??? Clutching at straws now maybe??
When a call is incomming, press the green answer button, quickly, and then press and hold it again.
Thanks for your reply. I will try this and let you klnow how I get on.
Cheers
Works a treat. I Have now also mapped the VJPhoneShortut ("Speakerphone ON") to the GPS Button on the handset which gets rid of the 3 second hold (not always easy when driving). Thanks again.
Folks,
I have a Samsung WEP-500 bluetooth earpiece, which I keep various pockets. The problem is that I must keep catching the button which automatically redials the last number in the phone book. I have tried all things but which every pocket, I still keep catching the redial button. I presume that I could just empty by 'last received' calls from the phone but this is just a little too drastic.
Is there any ideas how to stop this behaviour with a setting or registry key? I have MS Voice Command and cannot do with this. Holding the same button for a longer interval enables me to place a call verbally. It just the single click that bugs me.
Thanks for taking the time to read this and any suggestions welcome. Thanks.
Tom (UK)
Hi Guys,
Does anyone have a solution for the problem that the call button on bluetooth headsets won't work anymore with the TP2?
I use it in combination with Voice Command which worked flawlessly with the Touch Diamond, it's also been set to the same (and only) hardware key as the diamond but it won't work on the headset!?
It works fine when you press and hold the call button on the phone though...?
thanks!
jan
redsunpost said:
Hi Guys,
[...]
It works fine when you press and hold the call button though...?
[...]
Click to expand...
Click to collapse
When you say it works fine, do you mean through the BT headset, or just through the speakerphone?
P.S. I had an opportunity to talk with someone at Microsoft, and the response I received was "it's a known problem" and "wait for the next update or next version".
Alas...
i've edited it..
Strange problem cause the diamond had the same windows mobile version?
redsunpost said:
i've edited it..
Strange problem cause the diamond had the same windows mobile version?
Click to expand...
Click to collapse
It's nothing to do with the WinMo version, it's a different BT Stack.
I have been playing with it today and will post an update in the tweaks thread once I have it patched.
Cheers,
Beasty
Its not the BT Connection with a headset in general. That function works fine. I've tested it with my bt headset. Pressing the button I can accept the call and/or redial.
The problem lies within Voice Command itself. Once installed it gets assigned to the one and only hardware button configurable (hold call button for 3 seconds). The problem with that is when I do that with my BT headsets (normal and motorcycle one). They get powered off by pressing them for 3 seconds (same button). xD
I disabled Voice Command though due to the ringtone volume bug. Every 2 seconds the ringtone gets low for an announcement that you don't hear. Still waiting for a proper fix without all the work of replacing files.
I was looking for the original voice dialing function. But it really isn't there on the TP2. Voice Command is much better though. But damn that bug.
ChriX84 said:
Its not the BT Connection with a headset in general. That function works fine. I've tested it with my bt headset. Pressing the button I can accept the call and/or redial.
The problem lies within Voice Command itself. Once installed it gets assigned to the one and only hardware button configurable (hold call button for 3 seconds). The problem with that is when I do that with my BT headsets (normal and motorcycle one). They get powered off by pressing them for 3 seconds (same button). xD
I disabled Voice Command though due to the ringtone volume bug. Every 2 seconds the ringtone gets low for an announcement that you don't hear. Still waiting for a proper fix without all the work of replacing files.
I was looking for the original voice dialing function. But it really isn't there on the TP2. Voice Command is much better though. But damn that bug.
Click to expand...
Click to collapse
Sorry to disappoint you chrix, but the same hardware button (also hold) is used with the Touch Diamond.
Like I said they both look the same but with the TP2 it doesn't work, i'll be looking out for your patch beasty!
Another suffering TP2 user!
Hi guys,
I am also suffering with this issue as well. I did try and see if an old registry hack worked (changing HKLM\Software\OEM\VoiceCommand path=\Program Files\Voice Command\VoiceCmd.exe) but it didn't unfortunately. As previously pointed out in this forum, I think that this issue is more down to the fact that HTC seemed to have replaced the Bluetooth stack with their own proprietary version which isn't bad by all accounts, but does seem to lack this functionality. I might try and contact them to see if there's an update to resolve this but if someone does manage to create a patch for it, I'm sure there's a number of us who would be interested!
Cheers,
Barry
I installed voice command as well.
I'd already used the send button to put my lock on so it gave me another button (see attached).
Any body Know where the button is.