Related
Hi all,
Dunno about you guys but my new XDA2s is pretty paff when it comes to bluetooth. Scratchy sound, erratic volume, headset disconnecting randomly, poor range, etc etc.
I have used an old O2 G2 headset, a new O2 Bluetrek headset and most recently a Nextlink Bluespoon AX headset. All of them were nearly as bad as each other - except the volume on the AX is far less erattic. However, using them with my PC proved no problem so the XDA2s is at fault here!
I did find that forcing the headset to use headset mode rather than hands-free made a significant difference on the older models, however I cannot manage to force the AX to headset mode in any way (still waiting for tech support on that). The AX is let off though as its hands-free mode is as good as the headset mode on the older models, I just hope it will be even better when I force it to headset (if anyone knows how let me know!).
So - I have tried the following builds with my AX:
Radio 1.06.00 BT 3500 - BAD
Radio 1.06.00 BT 3900 - BAD
Radio 1.08.00 BT 3500 - Better volume and outgoing call, but bad for person on other end of the phone.
Radio 1.08.00 BT 3900 - Pretty much the same, small imporvement for me, no imporvement for other end of the line.
I am hoping we can keep a track of various radio and BT version in this post and try between us to figure out a good combination.
There is an extra audio dll
There is an extra audio dll for bluetooth that fixes some problems posted somewhere else in this forum.
This one fixed bluetooth headset enormous here.
I believe the dll you are talking about adds the high-quality bluetooth protocl, allowing stereo bluetooth heasets to be used for music etc. Does this make any difference to the normal bluetooth headsets though?
R
Hi,
Not sure how I got mine to work but I am using a Jabra 200 headset and it works great.
I am using a custom image of WM2003SE with the optional BT drivers and so far no problems - I found when I originally had similar issues I had to pair the headset again and then everything was okay (I noted the XDAII asked if I wanted to enable the headset support).
I get the odd problem where the headset icon disappears from the today screen but I found that its still there, just doesn't refresh so you have to tap the area and it comes to life.
The headset answers the calls after 3 rings (the headset creates beeps in time with the ringing) and when I dial the headset switches on after a second of making the call. The only thing I have noticed is that I cannot redial when pressing the button on the headset however it does hangup an existing call.
Cheers,
Godz
Hi finalzero - you say XDAII, do you mean IIs or are you using the II? My old XDAII worked fine - it is just this new XDAIIs that is giving me problems.
R
Bluetooth
Hi ,
same problem for me ,
Radio 1.08.00 BT 3900 - slightly better but not the best wit Jabra 250 V & Qtek 9090 ,
I installed BA_OEM_AudioGW CAB , downloadble somewhere around , but still problems .
When all of this will end ? Bluetooth is a nightmare !
I've had an XDA2 (several actually and got fed up of them being rubbish so insisted on an upgrade) now got XDAIIs. The bluetooth manager is aweful! Can't connect to my O2 headset, does't work well with TomTom3 and is generally crap!
Logged on to find out if anyone else is having trouble so please it's not just me, now all I need to do is find out how to fix it. I'm not a mega techie (but not too bad with the right support) and wondered if it's possible to use the bluetooth software from the XDA2?
Bluespoon AX
I have the same sort of combination Orange M2000 and Bluespoon AX and have the same nightmare sound quality - using Radio 1.04.00 and BT 3900. The AudioGW patch makes no difference (as posted above it's for headphone solutions).
Would be interested in the info you get back from Nextlink on the way to force the mode of the device if possible. Otherwise it's a complete waste of money as it crackles at both ends.
Nothing back from NextLink - have sent 2 emails. With radio 1.08 it sounds fine to me but the user on the other end reports it still quite bad. Gonna do 1.10 soon and see if that helps...
Rich
XDAIIs Bluetooth - upgrade to a Jabra 250
I had similar problems with my bluetooth Jabra 200 so I upgraded to a 250 (the black one) and I didn't have any further problems. The vibrating alert is really neat... 8)
bluespoon AX
while we're waiting for Nextlink's reply - can anyone advise me as to whether an upgrade to the Radio version (I'm only on 1.04) requires a hard reset (and full software re-build) or not? If not - are there instructions on another post that say how to do it??
Upgrading to radio ROM 1.08 or 1.10 may improve your BT performance significantly -- I updated my SX66 to 1.08 a couple weeks ago and my Bluetrek G2 headset now works much better.
Radio ROM upgrades do involve a hard reset & software re-install; this thread is devoted to the 1.10 upgrade -- there's another one in this forum for the 1.08.
Hi BA people,
I've spoken with my friend that has a Hymalaya (QTEK 2020) device, and he was joking me about all the trouble I have with the BA. It has a perfect bluetooth device that works with a lot of headset without noise, WM2005 already installed and working, very rare softresets, and spend less money than me. Amazing thing, I don't use wifi and so...
Franky, it seems to me that this device is a fake.
No people is working anymore on bluetooth that is dead by month and month, stopped at BT3900 and after 6 month I'm still unable to use my motorola HS801 headset that is lying in a corner with a lot of dust.
I was wrong when I buy this QTEK 9090, the older model was better. I think that I will not make the same error another time. Bye Bye HTC.
Sorry to hear that
I'm sorry to hear that you are not satisfied with BA. I'll admit that it has some bugs, but I'm happy since I use WiFi far more than Bluetooth. I almost bought a Treo 650 or Xda Mini, but WiFi was the deciding factor for me.
Hope they fix the Bluetooth problems with headsets though. I had a Nokia headset from my old phone and I couldn't use it with my IIs. At least sharing files through Bluetooth isn't a problem anymore.
contrary to the first poster..
i actually bought this phone knowing its problems...
Solving the problems one by one through the forums is one of the fun things that an xda2s / BA owner can do..
Everyday , I am discovering something new about the BA device.
I guess if I wanted a regular phone that already worked as it should...
I'd have sticked with my Nokia 6600.
Now I have a BA device which has inherrent problems, which forces me to read up the forums here and get really technical about the phone..
This actually made me love the phone more...
Hey guys,
It's so strange...
I know a lot of people aren't satisfied with the Phone or BT on a BA.
I have an SX-66, two weeks now, and it's working so well.
I can pair up with my BT GPS device 100% of the time, with NO problems at all. No need to repair when I turn off unit, etc. etc.
I used to have lots of problems with my HP.
The SX-66 is great.
Also, in terms of a phone, I am also truly happy with it.
I am in my basement and get 40% or 20% signal strength, and I can actually talk on it.
With my old cell phones T-616, Motorolla 720,... no way they would work in the basement.
Very strange how people have so many problems...
This device is 100% great in my books.. (and I am very very fussy!)
Also, since I installed MS Voice Command 1.5... WOW... it is easier to use than any Cell phone i had in my life!
M
I agree with the first poster - I too have a Motorola HS801 which I can't get working properly on my O2 XDA IIs. Highly annoying, but I don't want to risk buying another BT headset in case it doesn't work either!
I have had mine for almost a year now and I have had great success with it! It does have it's issues,but at least we are able to "fix" them ourselves. I use both the b/t and the wifi on a daily basis without any real problems.Btw,I use a motorola hs820 and it works very well for me.I have very few if any resets with the new radio.If I have any complaints about it,it would be with the Truefax.
simopimo said:
I agree with the first poster - I too have a Motorola HS801 which I can't get working properly on my O2 XDA IIs. Highly annoying, but I don't want to risk buying another BT headset in case it doesn't work either!
Click to expand...
Click to collapse
I have been using a Sony Ericsson Akono 660 Bluetooth with the pda2k BT3900 radio 1.12 and firmware of 1.40 for the last 2 months and I have paired it once. It works really well. I have a coverage of about 10 feet from the pda2k in line of sight and about 4 to 5 feet if the pda2k is in the car and I am outside etc.
For those of you who are not aware of which BT headset to use. I had compiled a thread on www.clubimate.com sometime back which lists those headset (reported by users) which seemed to work and do the basics, ring when call comes in, answer or hang up the call etc.
I would suggest they you review this list before making a decision on buying any BT headset. I also believe that iMate has released a list of officially tested BT headsets known to work with pda2k etc.
good luck
I was considering the Jabra BT800 because their web site states that it's supported with the XDA IIs, but after seeing some comments from others in these forums, it's so hard to work out what to go for.
therock112, I'm sure we're all looking forward to seeing that list!
I have tried the various ROMs with my PDA2K and the BT headset (tried HS810 and 820) are so inconsistent. The BT headset is a great idea but poor with this PPC. I wonder if the Samsung i730 is my next hope.
also disapointed
yes guys to my regert i have to admit that the ba is quite a failer in all the meaning
whaen you pay for device around 700 us$ u expect a little more then we get
the bt the wifi and the problem that seem far far away to be solve so what the solution is just to show our finger up againt ba product what ever
the name is and if the manfacture and microsoft will not improve we shuld decide and if somebody want to have fun by solving problem each day he can use a simple math book!!!!!!
Hi albnigxda!!!!
Do not get nervous....I hv used PPCs since 1997, all that HP and compaq stuff,XDAI/II/IIi/mini/HP6365/ and now BA(PDA2K)
and I can assure that BA is the best....
I use SE HBH 65....no problems
Couple of times use Wi Fi at some malls and cafe shops...Just wonderful with battery and speed.
My BA has become more stable after installing latest O2 ROM and choosing the particular band frequency(1800 MHz in my case) and no bad signal problems...
Use lot lot of applications with 512 MB SD card....
With all the above and 120 calls per day on avrg with 1 hr of GPRS usage My battery lasts for 26-30 hrs(Of course, during day time I keep OFF the backlight, as I use MS voice command and it tells who is calling)
So keep.up and go ahead...u hv the Best Handset of the World....
I can tell u as I hv also used Sony Ericson p8xx/9xx Almost all Nokia symbian phones to the latest 6681.....and I can tell u none can match the preformance of BA...
I hope, this will encourage you.
Good Luck
Have pda 2k latest rom off imate site have gotten 40 feet line of site , out of site is not so good. us a jabra bt800 am on it all day i have more problems with blue tooth on my laptop then my phone have had 3 other ppcs before this one its the best by far.
Ever since upgrading to the new roms first 2.17 then 2.25 it seems that I cannot hear on my moto650 bt headsets. I downgraded to 1.8 (ship rom) and it is back to beeing almost to loud I actually have to turn it down. I have another friend with the same problems after upgrades .I know that the moto headsets aren't known for being to loud but why does the rom lower the volume?
I wish I had the answer for you. I have an issue with hearing with my bluetooth headset on the MDA as well. I have tried 3 different headsets and none were acceptable. They all had plenty of volume on my other phones.
I have done research and tried a lot of stuff, mostly in the HKLM\Software\HTC\AUDIOGAIN directory of the registry. No luck what so ever. I have also found that the BT range is relatively poor (1 meter) on the MDA. My other BT phones could get nearly 10 meters.
Hopefully someone that has a solution and will feel our pain and reply.
are there any programmers out there that will compare these registry setting from 1.08 to any 2.0 < roms
get a sonyericsson HBH-608. I have no problems with that. I also did not have any problems with the Moto H700, plantronics 640. But I like the Sonyericsson the best
along with MS voice command and the reg hack I am able to use voice command and listen to my mp3's or any audio streamed to my BT headset. :lol:
any way to print the registry so I can compare the two.
The one thing I truly hate about my T-Mo MDA after 6 months is the difficulty using BlueTooth. I had an HP6315 (also T-Mo) which, despite all its other problems (like crashing everyday) had a far more sensible BlueTooth tool.
I don't have an issue with changing the stack--once I'm connected to a device I'm pretty much good, but the connection process is a serious pain in the patoot.
Before the impatient pros tell me "why don't you do a search before you post?" let me say that I have, and nobody I've found addresses this.
It's a really simple thing: every other device I own or have owned that uses B/T peripherals has a "Connect" choice. It doesn't matter if it was my 6315 Ipaq, my laptop computers, a Motorola cell phone or Samsung D-820/T-809 cell phones. All have the ability to force the connection. But the MDA doesn't, as far as I can tell. It either connects automatically, or you (frequently) have to delete the device and initiate a new search for it.
Am I missing something? Is this just the way the MDA is? Is there a piece of software or a registry hack that allows you to force it to connect?
I'm also curious as to why a regular telephone headset won't play back from Windows Media or BetaPlayer. It would very nicely on the 6315 Ipaq and still functioned as a phone. Any ideas? And, the reason I like to do that is I have a long commute and like to listen to Pimsleur language CDs (ripped to MP3) in the car. They work through the wired headset, but I can't stand wired headsets. I can imagine books on CD would also be enjoyable that way.
Thanks!
Yanktar03 said:
I'm also curious as to why a regular telephone headset won't play back from Windows Media or BetaPlayer. It would very nicely on the 6315 Ipaq and still functioned as a phone. Any ideas? And, the reason I like to do that is I have a long commute and like to listen to Pimsleur language CDs (ripped to MP3) in the car. They work through the wired headset, but I can't stand wired headsets. I can imagine books on CD would also be enjoyable that way.
Click to expand...
Click to collapse
You can do this. Get BTAudio.
Its not tmobile it the windows bluetooth stack. i have no problems but most people like the widcomm stack because its simple and easy. you should also try a bluetooth stereo headset its good thing to buy if you dont like wired headsets but advise to buy when having extra cash or look for a low price. prices are going down for some reason where i live
I DO have B/T stereo headphones, a pair of Jensens and a pair of IO gear. The latter list for around $150 or more, but a friend bought 2 pair (accidentally) off the 'net for about $35/per. That's what I gave him. The Jensens cost a little more but not much. Both make the HPs look like junk and are far more comfortable.
The problem is in my state it is VERY illegal to wear headphones while you drive. You can wear them on one ear, but not both.
Next, if you use them (not while driving) you are forced to use them as either stereo OR as a mono telephone headset--check the B/T settings.
It never fails to amaze me how if M/S has 5 or 10 choices, they will ALWAYS choose the most difficult to use (and idiosyncratic), the least useful, and the least reliable.
I was responding to this part:
Yanktar03 said:
I'm also curious as to why a regular telephone headset won't play back from Windows Media or BetaPlayer.
Click to expand...
Click to collapse
rpodos said:
I was responding to this part:
Click to expand...
Click to collapse
Thanks, I appreciate your responding.
I found a problem with my kaiser phone last night. The problem is that if I listening to music with my bluetooth headset I am not able to connect to my WiFi at the same time. This problem is specific to A2DP because my headset can be connected to my phone and I can not browse the web with WiFi. Has anyone seen this problem before? Has there ever been a resolution for it?
stevencage7 said:
I found a problem with my kaiser phone last night. The problem is that if I listening to music with my bluetooth headset I am not able to connect to my WiFi at the same time. This problem is specific to A2DP because my headset can be connected to my phone and I can not browse the web with WiFi. Has anyone seen this problem before? Has there ever been a resolution for it?
Click to expand...
Click to collapse
I've seen this too -- when using A2DP, the WiFi connection goes down & won't re-establish itself until I turn off A2DP. I haven't found a resolution yet -- not that I'm looking for one as I almost never use A2DP, and when I do, I'm in the car, where WiFi isn't too useful.
See my post here which may be a related problem. I assume you have the same new HTC ROM: http://forum.xda-developers.com/showthread.php?t=396409
I have a similar issue. If I am streaming music, from my HP media server, over wifi and using my Plantronics 590A bluetooh headphones, after each song I am asked to log back onto the network and as each song comes to an end my device starts to search for a network connection. I don't have this issue when I use wired headphones. Clearly there is an issue when both bluetooth and wifi are used at the same time. I don't know if it's hardware or software but I'm not happy about it.
akey
HTC TyTN II (Kaiser/P4550)
Rom ver: 1.82.707.0 WWE
Rom date: 11/03/07
Radio ver: 1.27.15.32
WM 6 Professional
CE OS 5.2.1620 (18125.0.4.2)
It's normal. Without going too technical, WiFi and Bluetooth operate on the same frequencies. They will live together if they're not using too much bandwidth, but if the usage is heavy there will be problems.
A BT stereo headset represents a lot of data to send and thus bandwidth usage, which means the BT will use the spectrum heavily, stepping over the Wifi. Due to the many packet losses the Wifi connection cuts.
Other way around, if Wifi is under heavy load, Bluetooth might drop.
Nothing we can do, that's what happens when you pack 2 radios operating in the same frequency band so close to each other, or even maybe sharing the same antenna which might be the case in today's phones.
It is absolutely NOT normal. The reason I know this is that VoIP over WiFi has been running almost perfectly on my TyTN II for a year, until I installed the latest ROM by HTC which broke it.
I used to get no crackle on Bluetooth calls with WiFi turned on. Now I do.
I used to get great quality VoIP. Now it is beyond unusable.
Simply, their new ROM broke it. BT and WiFi used to live in harmony, until their buggy ROM came out the other day. I think there are many users who know this, and who expect a hotfix soon.
You're talking about calls, I assume using the BT headset profile, while the other people in the thread are using A2DP wireless stereo. They're very different in terms of bandwidth.
On mine the headset with WiFi is also fine, but not A2DP. You're apparently not having the same issue than what is mentione in this thread. Yours might be due to the ROM, but the A2DP thing is more likely to be related to what I explained. I could myself experience it with several ROMS (all WM6, never tried a 6.1).
kilrah said:
It's normal. Without going too technical, WiFi and Bluetooth operate on the same frequencies. They will live together if they're not using too much bandwidth, but if the usage is heavy there will be problems.
A BT stereo headset represents a lot of data to send and thus bandwidth usage, which means the BT will use the spectrum heavily, stepping over the Wifi. Due to the many packet losses the Wifi connection cuts.
Other way around, if Wifi is under heavy load, Bluetooth might drop.
Nothing we can do, that's what happens when you pack 2 radios operating in the same frequency band so close to each other, or even maybe sharing the same antenna which might be the case in today's phones.
Click to expand...
Click to collapse
My old TyTn II worked fine with BT and WiFi on at same time - never a problem. I always had WiFi on at home for emails etc... and always have my BT headset (Plantronics 8XX mono) working as I hate holding phone to my ear and get a lot of calls.
I recently bought another TyTn II and then unlocked it using advice form this forum (many thanks to all BTW!) and installed latest HTC rom and WM6.1 etc... Now I love many aspect of the new ROM but I can't use BT and WiFi at same time.
So from my experience it MUST be the new HTC ROM software issue.
Okay, chalk me up as another victim of this Wireless + A2DP = Crap Reception. I've tried three other Radios and the effect is the same.
I was using a rom I got in about April, and I could stream music from the internet over wireless listening to it on my Pantronics 590A's over bluetooth no issues (other than battery lol). Now with a rom I got this month, I can listen to music over bluetooth no problem, surf using wireless no issue but as soon as you mix them both it's all bad. Also, I need to re-pair my headphones whenever I want A2DP, where previously I could just turn on the headphones and have them connect. Also, no headset icon in the taskbar.
It's not a CPU issue as there's no excess usage when you both have them enabled. Personally I'm going to point the finger at the bluetooth stack here.
As far as I remembered when I first purchased the ATT Tilt with my Plantronic Voyager 855 I WAS able to stream via Wifi (Winamp Remote) and use my bluetooth without a problem. It's when I started to put cooked roms in the Tilt that it stopped working correctly...
Besides, I use a Macbook Pro via Wifi only and I listen to my Itune via my Plantronic Voyager 855 everyday. If it's true about WiFi overloading Bluetooth on the frequency. Why does it work fine on the MBP?
And Finally.... to make my point...
I also have an AT&T Fuze. Works fine there. Matter affact. I'm currently connected via bluetooth to my Fuze with my Voyager 855... turned off 3G/HSPDA on the Fuze. WiFi on the Fuze using Winamp Remote to connect to my PC streaming from there. Explain that....
Has anyone fixed this problem?
I'm experiencing the same problem on my kaiser aka xda stellar. When Wifi is turned on bluetooth A2DP stereo connection is dropped.