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....
Related
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?
So get this, I was on the phone, using my BT headset. Suddenly the connection is dropped from the headset and the call is now being routed through the phone. After 2 minutes suddenly the call goes back BY ITSELF mind you, on the headset. 2 minutes after that back in the phone, then back to the headset then back to the phone and so on... Since it was an international call I didn't have time to get pissed, but I kept the phone in my hand and the headset on my ear and I would switch as the voice was being routed.
I've read all of the BT related issues out there as well as the possible solutions... nothing I've tried works for me.
I love the BA but this BT thing is ****ing frustrating!
Any light you guys can shed into it would be greatly appreciated.
Hi everyone,
so far i've been very happy with my new orbit, had it around a week now and all is good except for now my Motorola HS 850 isn't working with the Orbit as I'd liked..
This headset has worked flawlessly with the Exec, absoloutley no issues whatsoever, change the to Orbit and now, when pressing the button to pickup an incoming call, the other caller cannot hear me - I can hear them. I then press the switch to discontinue the call, close the flip to disconnect and then wait 5-10 seconds, open the flip so it re-connects and by that time the caller may call back and sometimes it's then good and a normal convo ensues and other times it still won't transmit my voice.
Frustrating ! - anyone else had this? know of any resolutions? tips? tricks? registry tweaks etc?!
Any pointers will be greatly appreciated!
Cheers! Dennis! West London UK!
I've had the same with my Wizard. The HS850 worked great with my old Motorola phone but when paired with the Wizard I need to scream until my lungs bleed in order for someone at the other end to hear me. Very frustrating. There were a load of suggestions over here.
I tried them all and it didn't help me but you're welcome to give it a shot. If you do ever crack this one, could you PM me with details (or a link to your posted solution).
See also here, here, and here.
Hi xda,
I have an issue where during a phone call i hear brief moments of silence whilst the receiver hears beeping, this happens around every 15 seconds and the duration of silence lasts around 2 seconds, it takes a good 10 seconds for the call to hang up.
I've checked the head phone Jack it seems clean and can play back audio flawlessly.
Running Pokemon charmeleon rom with franco kernel
Anyone else experiencing this problem?
Sent from my HTC One X using XDA
i dont know the solution to your issue!
trentoid said:
Hi xda,
I have an issue where during a phone call i hear brief moments of silence whilst the receiver hears beeping, this happens around every 15 seconds and the duration of silence lasts around 2 seconds, it takes a good 10 seconds for the call to hang up.
I've checked the head phone Jack it seems clean and can play back audio flawlessly.
Running Pokemon charmeleon rom with franco kernel
Anyone else experiencing this problem?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
For me sometimes when the headset is connected and I answer a call, there's no sound for a good 10-15 seconds and I keep saying "hello" like a retard and then I can hear the caller.
There is some sort of problem with headset compatibility for sure. Yesterday I was using this voice assistant called Skyvi with the headset attached, and after removing the headset my phone's mic wouldn't work at all! I had to restart to get my phone's mic working.
What I'm saying is there's a problem with headset detection or the software that makes the sound switch from the handset to the headset imo.
Further testing proves that this only happens when dialling out, not when the call Is incoming
Sent from my HTC One X using XDA
Damn strange! It has happened on incoming calls for me for sure.
There was this another "retarded" thing the handsfree did when I first got the phone, on pressing the button(twice) to change the music track playing, it called the last contacted person. I kid you not, I happened to call two people like that. But never happened after that day.
I have the exact same problem with my HOX, I'm thinking it's a hardware issue, because I have tried different kernels (Franco, faux & stock) and different versions of Revolution ROM by Mike... My phones serial number begins with HT23RW...
This is when I use the handset aka. The phone itself without bluetooth or headphones connected...
Hi guys, I did a search in this Arc forum for In ear Speaker problems and couldn't find anything, so I chose to start a new thread. Just know I DID try to find info for this phone but I only found a few other threads about different phones.
My in-ear speaker does not work in calls. It is extremely quiet, as if the volume is turned all the way down. Thing is, I try turning up the in-call volume during a call and it does nothing. But the weird thing is, I went into the service menu to test the hardware (using the *#*#7378423#*#* trick) and tested the in-ear speaker and it works fine! Loud and clear! But then immediately following that I'll try a call and still will hear practically nothing. Putting the call on speakerphone allows me to hear the other party, as well as putting in a headset, so I am stumped. Tried pulling the battery and have rebooted the phone many times and the problem is still persisting.
AND, on top of ALL of that, the damn thing was working just fine the other day. I switched to this phone last week and have been making calls successfully being able to hear the other party just fine. But suddenly today it's deciding to not work in a call. This is really weird.
Has anyone else had this problem? What else can I try to fix it? Any help or tips would be greatly appreciated. Thanks.
EDIT: Blah a hard reset fixed it. Feel free to delete this post mods!