I and using the AKU 3.2 rom.
and I find that is just work in a "short Distance" (around 40cm) in A2DP blueT. connection. otherwise, the sound will "pause" or "skip", is that normal?
Are you using the default MS stack which comes with it or the experimental Broadcom Stack ('WM5 Broadcom 1.7.1 Build 3400 Stack (Test)' thread)?
I couldn't even get A2DP to fly with the MS stack, but handsfree worked fine. On the other hand, A2DP was hassle-free with the Broadcom stack, but Handsfree was problematic.
But we did a test and we could spread around 5 meters until the sound started popping every now and then.
for the record, I am using Helmi AKU 2.6.
I have the same problem with A2DP on a 2003SE rom (1.40.00WWE). The connection is clear but very unstable; distances up to 2m are possible as long as there is line of sight, but the moment I turn my head so it blocks the antenna side of my headset, it starts skipping and pausing, even at a much smaller distance.
As far as I know, I don't have any metal plates in my head.
When the device is in my pants pocket and I'm walking, it also starts skipping everytime a part of my body gets in the way. Extremely annoying. After using the bluetooth headset for a couple of months, I just went back to the wired one because of this.
BT build 3900
Anycom stereo headset
Blue angel with A2DP bad range
i agree. i have the T-Mobile 1.42 Windows 2003SE Rom and the bluetooth range is extreamly bad. On A2DP the range is something like 1meter in direct range. if i cover the pda with my hands actually hear crackings, drops in the headphones...
Can we fix that? any firmware patch to increase the range? can as an extreme solution to build inside a small high gain antena?
i start to believe that all that is wireless in this device has poor range...
BR,
Invictus
Qtek 9090
Yeah would like a fix to
I have the same error.
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.
Take a look at the \Windows\Init_Rom_V316.bts file. It clearly states in the changelog comments:
- Decreased output power by 2db for added RF robustness for compliance with the 4db output limit throughout all conditions.
This cuts the output of the Bluetooth Radio by 2/3's, roughly!
This is called every time Bluetooth is turned on. Under: HKLM\software\widcomm\BRConfig\General\RadioPostLoadScript
Anyone have an older version of this .bts file that has the higher output? Of any of you reverse engineers able increase the Bluetooth radio power?
PS. For those of you using the 3900 Bluetooth patch, take a look at the RadioWLANCoexEnable/Disable keys in HKLM\software\widcomm\BRConfig\General They are calling a .bts script that I have never had on my machine, I removed the path to the .bts script and the Bluetooth Radio Memory load errors decreased dramatically, as did the time it takes to turn the Bluetooth off and on. The keys are blank by default and only populated when you install the 3900 patch, apparently the patch is missing some files.
Hope someone finds this info useful.
Hope we can find that
it is a good analysis step frpm you if you we find this file it will be greate.
What will happen
what will happen if we removed this entry from or make it blank.
HI,
i have the file called in the registry on my machine. Perhaps it helps to analyze. There are two files existing. One enables and one disbles a function it seems.
It seems that the attachment upload did not work
BroadCom BlueTooth Stack 1.6
Do anybody use Broadcom Bluetooth Stack 1.6 it has a very obvious performance change but when i use this bluetooth stack i hear a continuous beeb every 3 sec. and also it has the same registry entries as 1.0.3900
Re: BroadCom BlueTooth Stack 1.6
here i've attached all BTS files for BRF6100 chip I've found in ROMs of different devices. I've compressed them because forum does not allow BTS attachments.
Init_Rom_V316.bts - original file from 1.40 ROM. "Version : P4.12"
Init_Rom_V316_from_old_rom.bts - from one of the first PDA2K ROMs, "Version : P2.12"
BT_Init_with_Coex_v1.0.bts - HP h6300 ROM, "Version : P4.12"
BT_Init_without_Coex_v1.0.bts - HP h6300 ROM, "Version : P4.12"
TIInit_2.3.16.bts - MPX300 ROM, "Major Version : P4.13c"
all of these files except for TIInit_2.3.16.bts contain "Decreased output power" string. Someone can try all these files to check the best BT quality.
To use it - rename file to Init_Rom_V316.bts and copy to "\Windows" dir.
But I think the scritps from other devices would not work on ours.
Re: BroadCom BlueTooth Stack 1.6
here is one more file
With this file ActiveSync connects a bit quicker than with default file. I don't have BT headset here to check sound quality.
Re: BroadCom BlueTooth Stack 1.6
mamaich said:
here is one more file
With this file ActiveSync connects a bit quicker than with default file. I don't have BT headset here to check sound quality.
Click to expand...
Click to collapse
I try this file... Makes no different in BT Headset. Range and sound quaility is about the same.
Wow, I don't want to get too excited, but I think we may have a winner.
I used the TIInit_2.3.16.bts file in place of the Init_Rom_V316.bts from my 1.40.00 System, and I have noticed a large decrease in static. It is still there, mostly in the background, very low. Range seems much better too. I'll have to do more testing, but my initial tests were done in a location where I usually have a TON of static. I also held the phone the opposite side of my head, and still not much static. If my testing reveals better overall performance, I'll kit this up into a CAB.
Excellent work everyone!!!
-Chris
DAMN DAMN DAMN DAMN!!!
Ok, second round of testing is a complete failure. While the initial testing that BTS file looked great, everything fell apart in an actualy call. The sound quality is totally inaudiable...
I feel that we are so close....
-Chris
Do these stacks have the A2DP profile? I can't seem to get A2DP and Headset working nicely together.
wamatt said:
Do these stacks have the A2DP profile? I can't seem to get A2DP and Headset working nicely together.
Click to expand...
Click to collapse
Maybe it depends on your headset. I just got the Zonet ZUB8100 and I can connect to it using Hands-Free & A2DP profiles simultaneously. It works pretty well in A2DP mode for listening to MP3s, not so well as a phone headset. Haven't tried using it to answer a phone call while listening to a MP3 -- I'll probably try that over the weekend.
I'm running a SX66 with radio ROM 1.12, BT stack 3900, but not with the BTS fix mentioned upthread.
i found the answer
sell the xda2s and buy a palm treo 650 - what a great device, should have done it months ago
it is so reliable and crash free
The various WM6 version threads have become cluttered so forgive me for starting a new thread. Does anyone know of a way to check bluetooth stack versions on these various builds of WM6? For the most part bluetooth in WM6 is an improvement over WM5 save for the use of my HF850 car kit by motorola....it'll bond, it'll trigger voice command (but only route it through the phone speaker, not the car kit), and wont carry audio inbound or outbound. It worked relatively properly with WM5, but would drop / reconnect randomly, and of course BT VC didnt work. Any ideas? Anyone else having the same problems with the Hf850 or other bluetooth peripherals? I've read some threads about some Parrot kits now working that didnt before. Any input is of course appreciated.
I have noticed that when my X7501 is dormant (screen off, phone on, BT on), ie being charged while connected via USB to my PC (using WM5 Storage Program, 'Activate' setting enabled), the Jabra will occasionally light up as if being queried, or itself sending a query to the X750x.
This may happen every 5 minutes or so. This may be the reason why music skips during playback.
What does everyone think?
Are there any BT registry settings that can dictate how often the BT connection is queried?
Next time I play back music, I will play with some settings. For instance, turning off the phone - though this is hardly ideal.
Next searching the registry....
Keith Walker
After I upgraded to WM6 CE OS 5.2.1238 (Build 17745.0.2.3) almost all my BT skipping went away without any additional reg changes or patch programs.
I never see the condition you see.
That's the same version I have, it only skips every 5 min. or so. What blue tooth registry settings do you have?
"What blue tooth registry settings do you have".
Just what re-loaded after a hard reset. Any specific setting you might be interested in?
For instance my current settings are:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\A2DP\Settings folder:
Sample Rate: 48000
UseJointStereo: 1
there are other threads here, best to read them sequentially:
http://forum.xda-developers.com/showthread.php?t=313445
http://forum.xda-developers.com/showthread.php?t=308752
http://forum.xda-developers.com/showthread.php?t=262119
http://forum.xda-developers.com/showthread.php?t=310438
The last 2 threads may be the solution. Sometimes it is hard to find all the info with all these subforums here...
I made the changes to Sample Rate and UseJointStereo in my previous version of WM6 but neither of the items show up in this version of WM6 and I have not seen any reason to mess with the registery at this point.
Anything else I can look at?
I would say if you don't have problems, or you don't mind the skips; then don't change a thing.
Another issue, is trying to isolate the cause. I believe bluetooth like wifi is constrained by the FCC to accept outside interference by law. So many times the skipping issue may be unrelated to the hardware or software, or outside your control.
I've only had one problem in the last few weeks: A phone call came in and did not transmit to my BT but stayed on speaker phone. After about 1 second it switched over to my Jabra 8010.
When driving, my BT is in my left ear and the 7500 is on the right seat. Maybe that is enough to cause a short dropout.
Ive had useable audio (static but understandable) between my 8010 and 7501 with 50 feet between them and: a metal bathroom door, one solid wall with steel studs, and a dozen cube walls with lots of metal in them. So I doubt wearing it on the opposite side of your body is a factor. The BT antenna seems to be quite good on the Athena.
I get the same type of BT skipping on my MBR-100, it only happened sometimes when I was on PK 3.0, but now that I have upgraded it seems to happen all of the time. I also get audible noise if I charge and use the MBR-100 at the same time. The reciever is almost unusable due to skipping. I used to think that it was a memory issue, but evidently some of the theories here are a bit different. Any one have any thoughts on how to stop BT skipping beyond the links posted above?
REF:
http://www.amazon.com/Sony-Ericsson-Bluetooth-Receiver-MBR-100/dp/B000NWB0J0
Thanks,
Bob
I'm having issues with a bluetooth conflict.
My set up is as follows:
- AT&T Tilt - WM 6.1 stock ROM
- 2009 Toyota Camry XLE V6 paired to the Tilt with Hands free profile
- Motorola S705 paired to the Tilt with Wireless Stereo profile ONLY -- I don't pair with Hands free profile. The S705 is connected to the Camry via an aux connection.
I also have GpsGate running in the tray with a bluetooth GPS receiver, but that seems immaterial to the issues I'm encountering.
When I pair the phone as above, the music from the car speakers skips to the point where it will be inaudible for 2 - 3 seconds per 30 seconds of music...no hissing or popping...just silence. The 2 - 3 second pauses are not regularly distributed.
In order to resolve the issue, I go to bluetooth setup on the Tilt and select the Camry Hands free and select 'Set as Hands Free', which, paradoxically, does exactly the opposite...it disables the pairing with the car (until I restart the car). However, once I do this the Wireless Stereo connection is rock solid. Alas, in this configuration, I can't get dial or hang up, hands free, via the steering wheel buttons.
I'm tending to believe the issue is the Toyota since I can connect a Scala 500 as Hands free without issue when playing music in the car (FYI, at no time do I have both the Toyota hands free connected and Scala 500 powered on at the same time).
I'd love to know:
- How I can confirm the problem is with the Toyota, since it is likely they will simply point to the Tilt or the S705 and claim that it is the culprit? I would like software output that demonstrates the Toyota's bluetooth implementation is ill-behaved.
- If the issue lies with the MS stack instead. My understanding from another site is that the MS stack was hacked to allow A2DP. I wonder if the MS stack is simply performing poorly and the Camry bluetooth setup is simply doing what it ought to do. If I could replace the MS stack with the Widcomm stack, this might allow me to test this premise.
In searching I've found some other threads which deal with Kenwood stereo systems and different symptoms (restarting), so I'm not sure the problem is related
http://forum.xda-developers.com/showthread.php?t=442370
I've also searched and found information on replacing the bluetooth stack. No confirmation in the thread whether this will work with the Tilt
http://forum.xda-developers.com/showthread.php?t=449775
Options i'm considering:
- replace BS stack with Widcomm -- no confirmation on whether it works on Tilt
- installing JETware -- mixed results in other threads, Tilt isn't listed as compatible
- reverting to 6.0 -- mixed results in other threads, don't relish the idea of going backwards (HTCHome via cab, etc.)
Edit: That would be the BT stack, not the BS stack (freudian slip)
Does anyone have any experience with the same problem, suggestions as to what options will likely bear fruit or if there is a simpler option? I'd prefer not to do a hard reset and re-install everything I have on this phone if I can get away with a simple fix.
Thanks.
Im having similar issue
I purchased a new headset for my motorcycle helmet.
I can not get the hands free working..
I have another headset that works with the phone, this ended costing me shipping charges thinking the helmet headset was bad.
I have searched many sites and have come to the conclusion it is the phone.
I have not seen anything that gives me an indication that we will find a fix..