Hi together,
I have a problem of worse BT and WLAN range.
WLAN only finds a router when nearer than 5m and with BT
it is much worse. In my car with build in BT I even have to
put the Kaiser directly on the radio to get a clear connection.
Even turning the Kaiser lasts to some kind of scrambled
voices.....
BTW: WLAN and Bluetooth are not used same time
and always switched of the other one.....
My ROM: M-Diamond V1.3 German
(tried before: L26 V12 and L26 V?
Radio: I have tried: 1.58.25.17 / 1.71.09.01 and now 1.65.16.25
(all with the same problem....)
Really looking for help...
regards
LCS
Edit/Delete Message
Related
There are a couple of standalone updates around but not too much information about any improvements or otherwise with the Blue Angel variants. So lets post our results and see if these updates are worth upgrading to. My XDA IIs is running
latest rom 1.31
bt patch 3900
radio 1.06.02
Bt upgrade seems to have made minimal changes, maybe a touch louder but thats all, no other changes noticed
Radio 1.06.02; cant say i notice any changes here as i didnt have any calling problems with ver 1.02. I upgraded cos of a problem with wifi which is still there
Anyone have anything to note about the wlan patch? If there are any other patches i missed please post what they are and what effects it has had
Hi.
I have spent a while looking for the patches. Can you point me in the right direction?
I actually went back to the Dangaard BT stuff...version 3500 and patch. This worked better for me with my Logitech BT Headset.
I upgraded the radio also to 1.06.02...can't really say it made a difference, but hell, it didn't hurt either...
BT Build 3900
Hi.
Upgraded to Build 3900 from 3500, found on the FTP server.
Only dif. is that my SE HBH 300 is now faster do disconect a call when pressing the on/of switch.
I was fooling around alot with my BA the day i installed the Build 3900, and right after installing the patch i tested it without a Soft Reset. I got a perfect connection without any crackling noise and a really good distance.
After a Soft Reset it was back to the old crackling noise and poor distance.
And i just cant recreate the scenario i had that day
Radio, dont know. Dident have any troubbles with the old one.
Wlan patch, wating for others to tell.
I upgraded my radio rom to 1.06.02 and BT Stack 3900 and found the Bluetooth still crackled on my old jabra bt 200.. just bought a BT800 today and it appears to work better even the caller display works.. with the radio stack upgrade i have had quite a lot of problems connecting to known wifi access points even when all the correct details were in. I also could not connect to BTOpenzone when standing under the access point (and yep i do have an account on it) so I re flashed the radio rom back to 1.06.00 and bluetooth 3900 with high quality audio patch and it all back to normal with abit mor BT Stability :roll:
Jabra BT800 worked straight out the box with no patch needed and has good loud audio 8) and a range of 10 meters ish still a bit crackly at 5 meters though
Marqnet said:
... so I re flashed the radio rom back to 1.06.00 and bluetooth 3900 with high quality audio patch and it all back to normal with abit mor BT Stability :roll:
Click to expand...
Click to collapse
So what you are saying is that radio version 1.06.02 interferes with WiFi somehow....that is interesting... :shock:
Do you remember what happened with your WiFi strength when you turned of BT, or have you not tried that?
Cheers,
HappyGoat
Hi as far as i am aware so far there has been no real issue with the Bluetooth and wifi interfering with each other or should i say i have not experienced any problems. the i ssue was just around using wifi and its connectivity problems i have had with open and unencrypted access points and encrypted ap,s the radio could see them but not connect. my xda came with 1.06.00 as standard and i was curious to see what the latter radio rom would offer. so as i didnt work for me i decided to go backward on step and all seems weel now. will agree interesting one and after trying a number of different 1.06.02 files as i thought the first was corrupt i just decided to revert back to a known to me working rom.
radio version difference
what is the difference in radio version 1.02 v 1.06?
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 all,
first wanted to say that it is a great forum.
I just came across it couple days ago, and there has been many things that I found here that improved my Qtek 2020i.
but there is one thing that i havent found in here.
I use tomtom 5.21 with a bluetooth GPS receiver. it worked fine until I bought a bluetooth headset. If im using TT to navigate and answer a call via bluetooth headset it works fine, but when i hung up the call, then Qtek looses connection to GPS, then picks it up again in about 10 seconds but runs with a big delay. I have to restart tomtom and then it is back to normal (quite annoying when driving thru town)
any of you have that problem??
thanks for help.
Hi there,
My problem might be related : the device seems unable to use both the headset and the GPS (with TT) at the same time. I don't know why. I've got a Qtek ROM at the moment, I'll see if the latest O2 ROM with upgraded radio stack does any good.
See you.
Right. Just switched to PUG's .162 ROM with O2 stuff stripped.
Alas, it comes with Broadcom stack and there's no SPP inside so I can't connect to my GPS ... Pug if you read this, help
Cheers !
seems strange: I replashed my stock O2 bloatware & buggy 169 Rom with pug's flavour, to give me the 162 rom and Radio version 1.04.
My GPS bonds fine tihe BT, and I can use TomTOm and a BT headset at the same time. Did you flash the Radio to the (far better) 1.04) when you upgraded the Rom?
I've heard quite a few people say on these forums that for Alpine, one of the most stable & speedy setups is the 1.10 WWE Main Rom, the .162 Pug rom with the O2 stuff stripped out, and the 1.04 Radio.
Joe
Yeah actually it works fine now. I made another post while I was looking for help, because the Alpine wouldn't find the SPP service when interrogating the GPS. I simply switched the GPS off and back on, and the problem was gone. I wish I'd tried that before the dozen ROM combinations I spent the afternoon testing
And indeed, I'm now running 1.11WWE/1.04.00/1.11.162 PUGS w/o O2 stuff, and finally TT accepts to work with the headset while using the GPS. What a trip !
Cheers !
My previous phone HTC TyTN (Hermes) worked perfectly well with my car OEM Bluetooth HF (BMW X3 '05) using varios ROMs and Radios, starting from the original VM5 to many cooked VM6 editions which I tried.
Now I purchased a brand new HTC TyTN II (Kaiser), which seems to have serious problems with the car Bluetooth. It pairs ok, but immediately when the actual bluetooth communication starts, the phone always reboots itself.
I have made a log of the communication using JETware Hands-free Extension. In the attached log you can find a row with strange character causing immediate reboot to the phone. The problem is not caused by Jetware, because the phone behaves exactly the same without Jetware.
From another forum I have found out that this seems to be a common problem also with another phone model which is T-Mobile Dash (HTC S620).
http://www.jetwaremobile.com/forums/forums/thread/394.aspx
http://www.jetwaremobile.com/forums/forums/thread/282.aspx
Any ideas how to sort this out? Which component on Kaiser should I start flashing upgrade/downgrade?
--
Mika
Kaiser ROM 1.56.414.2 Radio 1.27.14.04 Protocol 22.45.88.07H
Update to my situation, tried so far:
- Flashed Sleuth's V3.0 with Radio 1.64.08.21. The problems persists, phone pairs ok with BMW HF, but reboots itself immediately when actually connected.
- Tried to install Widcomm Bluetooth Stack which is duscussed in this thread, but could not get it really work in my Kaiser. After solving low memory issue by changing bitrate to 115200 it started, but it was not able to find any bluetooth devices at all.
I just wonder if this could be a hardware issue not solveable by any software updates? What could be fundamentaly so different between Hermes and Kaiser bluetooth implementations, that one works fluently and the other keeps rebooting itself even with different roms and radios (WM6.0 and WM6.1)?
What might be going so badly wrong in a bluetooth conversation that Kaiser decides to reboot? The AT-commands conversations starts just fine, but ends to a long string with odd characters. (please see the attached log file in my previous post).
Anyone, any ideas, please? I have done so much searching on this subject lately that I probably can no longer see any trees in the wood.
--
Mika
ROM: 3.0 Sleuth WWE
Radio: 1.64.08.21
Protocol: 25.74.40.02H
Updated car software
Now I upgraded my car computer software to the newest version as adviced in the x5world site here, the problem persists.
I've had my tilt since June and bluetooth was working great on my BMW and my Lexus. Then about two weeks ago every time I used my tilt on either my BMW or Lexus the bluetooth connection was extremely garbled. My other phones with bluetooth worked flawlessly in either car. My tilt which was upgraded to WM6.1 was the obvious culprit. I tried a soft reset, hard reset, going back to WM6.0, and then back to WM6.1 but always within a day or two my bluetooth connection between the tilt and either car became garbled. I even tried another tilt but same symptoms. So that brought me back to software, radio code, or configuration. Considering that I used both the WM6.0 Rom and the WM6.1 Rom and both didn't work the only answer was configuration. Last night after getting a replacement Tilt I resynced with both the BMW and the Lexus with no problems. This morning on my way to work again the bluetooth connection became garbled. Now I'm extremely frustrated, then I noticed a red light came on in my BMW which is what happens when the bluetooth connection fails. For some reason I turned off my wifi and immediately the red light went out. I tried a call and every thing was working great (nice and clear). I made several calls and bluetooth again was working flawlessly. Then I remebered that one of my settings was to change the wifi card to maximum performance instead of maximum battery since this makes a huge difference in wifi performance. I'm going to perform some more tests this afternoon but I think the extra wifi power is severly affecting bluetooth.
yea same happens with me when I have WiFi and bluetooth on. also my friend who has tilt has same problem. I think this is common problem with tilt. so far I tried few different radios and roms but noting helped. I could not find fix for that anywhere.
You need to try different radios. I found radio 171091 worked well with a lot of the 6.1 ROMS. I am now using 1652436 with Athine's ROM and both of these allowed me to Bluetooth Stereo, Bluetooth Phone and WiFi. The biggest problem I have ever had with these Radio's is when I drive around and pick-up different WiFi spots, the Bluetooth audio will cut out for up to 1 second.
Great, I never installed radio code before. Is it similar to changing the Rom?
same process
I'm using AthineOS v3.2 rom with a Tilt Radio Version 1.71.09.01 Same thing.. everytime you use Bluetooth and Wifi it craps out if there is a lot of data transfer between either of the technology.
Worse off, it takes down my Wifi at home for 30sec-1min. All my devices that is on Wifi loses signal