I got my S200 back from a repair and it was also upgraded form G3 to G4.
Everything seems to work fine, except my Jabra BT500 head set. After pairing with my S200 I got a very cracking sound.
So I checked my Jabra with another mobile phone and it worked very well. I checked another head set with my S200 and again a cracking sound.
Does anybody knows how to solve this or do I have to return my S200 again for repair?
Hi, I have excatly the same problem, it also occurs with the bluetoothof my car...anyone can help us?
I have returned my S200 to QTEK today in order to have it repaired (again).
I have tested it (in my car) with 2 other Bluetooth headsets and there was no problem. There was also no problem when I tested my own headset on another phone. So this proves that my S200 has some kind of defect.
The sound is very crappy ?
Or is the soud quite ok, but experiencing high frequency glitches, kind of metallic parasits?
Because in that case, there is nothing to do, It's due to the MS bleutooth stack which has a very poor encoding librairy... and since there is no widcomm stack for S200 (and some other qtek too, a lot of people is yet trying to malke it work), then evey bleutooth headset will have bad sound in A2DP with the S200 :'(
One of the main reasons why I want to change for a widcomm stacked pocketPC (shame on MS!!!!!!!!!!)
For me, the quality is very bad. At the beginig I use it only on my car and it was working perfectly, since I try to connect to the bluetooth headset or to my computer the sounds became very very crappy. I have Dopo ROM, which rom do you have? what ROM do you advise? Thank you
I have tried the LVSW, Jester and shipped ROMS and all these ROMS have the same problem. So I think that it is not related to the ROM but due to bad hardware components.
it's strange because it was working for me before I use other bluetooth device. I will try to upgrade the rom to the official QTEK ROM
I have the same problem. As if the bluetooth signal were cut per moment.
it's not linked to roms, but to bluetooth stack, so since the bt stack is updated (but I doubt it), changing roms won't help
I could fix it, I update the ROM, delete all pairaing on my cars... I change the "hsotname" of my QTEK on "settings - Owner information" I recreate the pair and it works fine on my car, now crappy sound anymore. Just to test it again, I try to pair my "fujitsu laptop" to my qtek, since I did it, the sound is again very crappy. So I will flash again and pair it only with my car. If I return it to Qtek it takes 1 months... If someone can fix this that would be great.
Related
I have purchased an O2 XDAII in Oz which is loaded with the 1.66 ROM. I have tried connecting two headsets to the phone over bluetooth with many problems.
Both seem to bond ok and work initially but later they fail - the XDAII doesn't respond to anything I press on the headset. Or the XDAII does respond (answer or end call) but no-one can hear me either through the headset or the phone.
Deleting and re-bonding seems to temporarily solve the matter. But if the XDAII goes to sleep and comes back on it stops working. Will also just stop working for no reason after a call or two is made or received.
I have tried installing the bluetooth tools which is cool because the XDAII can recognise some of those extra headset profile functions (like redial) but I still get the same problems as above.
Tried Plantronics M3000 and Motorola HS801
What can I do? Is it this Bluetooth stack problem from MS I have read about? Do I need a ROM upgrade? Do I need Widcomm something installed on the XDA II? I don't know how to do any of these myself. Any kind advice from a pro is appreciated in advance.
When you installed bluetooth tools did you delete any bonding and pairing of devices beforehand? it can make a difference if you havent done this.
Yes. I tried it twice thinking that maybe I might guess a way to make it work.
First I deleted the bonds after installing BT Tools and then rebonded.
Then I deleted the bonds before installing BT Tools and then rebonded.
I spoke to my Telstra dealer again today and they received a list from Brightpoint (a distributor) that matches various headsets against various PDA's available in Oz.
Not all BT headsets will work competently with all PDA's. The M3000 is marked as NOT compatible with the O2 XDA II available in OZ. So was the Motorola too.
I am now using a Hello II headset which so far is fantastic (very small and comfortable to wear) and is working with no modifications to the XDA. I will post back in a week with a fuller review. I'm going to re-install BT tools and see if that make a difference with the available functions.
Anyone else wanting to test these out in Perth, WA, (Australia) - they are available from Communications Plus.
Help
I can stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
Help
how can I stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
I had a problem with my Plantronics M3000 too so I called Plantronics themselves who said that the problem is with the phone, not the headset. It's a compatibility issue with the software.
Unlikely to be any fix, at least not in the near future.
These stacks I believe are newer than the Widcomm 1.5.0 series
I think Broadcom reset the version 1.0.0
These are Broadcom 1.0.0.3000 and Broadcom 1.0.0.3500
Build 3500 is slightly unstable but newer.
These came from an i-mate patch for a PDA2K.
DO NOT USE on an i-mate PDA2K (get the orginal unhacked ones from Club i-mate).
I removed files specific to that phone and basically left just the BlueTooth stack.
Recommend a HARD RESET before installing.
I've tested theses patches on a Sprint PPC-6601 (Blue Angle CDMA phone).
Do not do a restore of a backup before or after installing this because it may restore incompatible configuration files that may crash. Build 3100 is more robust against this problem.
Hey Bro
These two are for the Qtek 9090/Xda IIs or Xda II?
I am running 2.20CHS translated with Radio 1.18 and have been unable to get this stack to work. Has anyone tried it?
The ones I posted above are hacked by me to work on the CDMA version (Namely Sprint PPC-6601).
The ones referenced in this reply below are the original patches I started with that came from i-mate club. The offical phone name that the patches are for is "i-mate™ PDA2k" (GSM Slide out keyboard). I don't know how well they would work on the Qtek 9090.
Build 3500 http://www.blueridge.net/dereck/bt/PDA2k_Bluetooth_Fix.CAB
Build 3000 http://www.blueridge.net/dereck/bt/new/OEM_WWE_122_008.sa.CAB
Yes, good link but already bad quality with all bluetooth headset.
It's a shame.
It's a shame you don't give more details.
Which phone, which patch and what happened.
Works great on my phone.
I'm using the 3100 patch from the first post in this thread on a PPC-6601 with a HBH-300. Installed on top of a HARD RESET. That has Build 1.0.0.2200.
It's almost working perfect. Once in a great while if I go out of range for a long time I just toggle bluetooth and it reconnects immediately.
Dial Up Networking and Active Sync all work.
No static. No dropouts. Will go to sleep and wake up and still be connected.
I think that the "shame" was not for you but for imate as their patch don't solve all the issues. Maybe only a bad english ?
Tried on Himalaya_SE 2.06...
I'd merged the files from 2.02 and 2.06 and get a fairly stable handsfree, but I saw your files and got greedy... :twisted:
hmmm, it didn't work though. The installation freeze at splash screen after i cold reset the device.
I believe that there are still device specific entries in the cab files, but it's beyond me at this moment. :?
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
Note that I attached to the first post of this thread Build 3500 release 124 of the i-mate patch stripped down for use on PPC-6601 and VZ6600.
BT problems
Just installed the 3500 fix.
It improves slightly on the Jabra 250, but not enough to actually use it.
It Stabilized the connection between my Holux GR230 GPS and the Qtek 9090.
Hope there will be a better fix.
Try to look at the connection, problem with the Jabra is that it fluktuate from just right to zero every other second.
Nice to pay 800 Euro for something that do not work :shock:
I've added new patches to this the start of this thread.
They work primarily on PPC-6601. Read the attached notes.
Hi mswlogo,
Can you help me if you know which version works on a win2003se translated from chinees on himalaya?
Thanks
That phone is quite different.
I think some other folks are working trying to get this stack working on other phones like yours.
Most of the patches above have registry scripts run in them that will very likely not work on your phone.
The other patches assume you are already running late version BroadComm Stack.
I have HP hx4700 and the Widcomm version is 1.5.0 Build 2000
which one is newest?
That's a really good question.
I'm amazed to see BroadComm on 1.5 instead of WidComm.
What are the dates on the bluetooth files \windows\bt*.*
They are generally around 12/9/2004
It's hard to say what BroadComm and the venders are doing here.
Bluetooth stack on h6315
I just found a new bluetooth stack from:
http://www.ppcw.net/?itemid=2210#cmt9543
Installed on my t-mobile h6315. Device was previously inoperable with bluetooth headset. Device would go into power standby mode, and if bluetooth was running when it went to sleep, it would freeze requiring a soft reset. Now device wakes on power button, with bluetooth running, as it's supposed to. Device also wakes on incoming call, reconnects headset in less than 1 second, and allows me to answer call on the headset buttons. All other headset functions are working as designed, and sound quality seems good. My headset is plantronics 2500. Also, this stack adds a profile in the list for A2DP (??) high quality stereo headphones. Don't have any of these headphones, so don't know if this works on the h6315. Also, don't know if this is the same Broadcom/Widcomm stack you guys have been working with.
Installation is straightforward - put it on the device and tap it. Reset, delete existing device pairings, re-establish the device pairings, and you're ready to test.
All that patch is supposed to do is add two new bt profiles to the pda2k.
* High-Quality Audio support (A2DP)
* Keyboard support (HID)
I'm slightly suprised you got a performance gain out of it.
h6315
It's definately fixed the problems with my device hanging when it goes into standby with bluetooth running and the headset connected.
Now my question is should I install the build 3500 for the 6315 listed above? It appears to be a newer release than this. Any thoughts as to the differences? I'm having a hard time following from the thread as to all the other changes that are in this .cab, and why they are there? Can any one help summarize that?
Hi
I just got my new BMW 330 (E90) with Navigation and Bluetooth. I can pair my MDAc but that's it.
When a call comes in, My BMW signals it. Sometimes I can get the call with the button in the steering wheel. Sometimes not. Sometimes I can but the connection breaks down in the middle of the call.
I see the reception of my MDAc in the display and when a call comes I also see the number of the caller.
I cannot make a call (dial out).
I read a lot but did not find a solution yet. Has anyone experience with BMW carkits or any advice what to change in order to get it going. I sort of refuse to have another handy...
BTW I have the latest T-Mobile Update (1.12) but I did not install everything from the extended ROM.
I have exactly the same problem with Audi bluetooth, with my Nokia 6230 works perfectly, with my S100 I have the same problems you have experienced. I have an old ROM 1.06, but I see that even with 1.12 the problems are not solved.
I tell what I tried: I've installed various BT stacks (Toshiba, Widcomm, Bluesoleil also with crack). Toshiba pairs but does not find any service, Widcomm does not run, Bluesoleil does not have the needed profiles.
I have installed the CAB from VCABT project (see the thread in this forum), I can answer from the car I can call using the car voice command but I can't use the S100 buttons.
Hope that somebody could help us.
dgv
fdigianv, have you tried the new A2DP Stereo BT Tool to see if it works better with your Audi.
I just upgraded my JAM to 1.12 and have yet to try it with my Audi A6 4.2 2005 MMI BT System.
I'm tired of waiting for Audi to fix anything. It seems like the only fixes or upgrades they offer come in the form of a new car release.
I like you can call out from the Audi, but those on thger other end of the call complain about sound quality.
I'm getting ready to make a move to the new Treo MS Mobile device, or a smartphone that works better with my Audi.
I spoke to BMW this morning and they claim has more to do with the version of Bluetooth installed on the phone than BMW's implementation of Bluetooth.
BMW supports Bluetooth verson 2 and up.
Hi All. i've got a qtek 9000 and i can't use my bt headphones.
I bought this one with the ipaq and than i succed using it also with my qtek 9090
right now i can't with the new 9000 and i have no idea how to do it
please can someone help me?
Please be more specific as to where the problem is. You say you got it working on the 9090 but not on the 9000. Exactly what part of the pairing process does the difference come out?
Ops, i miss it!
I installed on the 9090 an audio driver that add a new voice in the bt connection manager.
The high quality stereo headphones. This driver couldn't be installed on the new wm5 because was designed for pocket pc 2003
so rightnow i can pair the device but no service is offered when i try to discover device services.
So even if i have paired the device i can't use it because no service is found.
i hope i've explained the problem
tnk u 4 your support
Barinight.com said:
Ops, i miss it!
I installed on the 9090 an audio driver that add a new voice in the bt connection manager.
The high quality stereo headphones. This driver couldn't be installed on the new wm5 because was designed for pocket pc 2003
so rightnow i can pair the device but no service is offered when i try to discover device services.
So even if i have paired the device i can't use it because no service is found.
i hope i've explained the problem
tnk u 4 your support
Click to expand...
Click to collapse
You mean it cannot be paired without running a particular software? Yikes... So when you put the Bluetooth headset to discoverable mode, then try detecting it from the Universal, it sees it but there are just no services available, am I right?
So it seems that the one at fault is the Bluetooth stack installed in the Universal... In that case, I cannot help you... SOrry
The Universal does not support A2DP or what HP calls High Quality Stereo, as such it does not support your headphones. A2DP is suppose to be part of what is included in the MSFP update but i-mate has chosen not to include it. Until someone releases A2DP support your headphones will not work. Now if you happen to read German I understand their is a German ROM that supports this feature.
Otherwise it just a question of waiting till someone releases this update, if they do.
i think that is the stack but the question is:
the 9090 doesn't support the high quality too but installing the driver things changes so i won't belive that thare isn't a driver for the 9000
i tried to find something from Widcom (i hope is the right way to write!) nut i dind't find anythink
so i hope that someone can help me because i've payed 120€ the headset and i will love to continue using it!
I've just got a Orange SPV M3100 and paired it with my BMW OEM bluetooth carkit, all goes fine and paired no problems.
It manages to connect to the phone and display contact details on the radio display and make calls.
But leaving it a couple of hours and coming back, the phone will not reconnect back to the car. I've tried resetting the phone without success.
The only way to get the connection back is to re-pair the devices.
I had a Imate Jamin before and it worked without a problem, connects every time.
Is anyone else experiencing problems with their carkits?
Do you think the problem is specific to the Orange ROM, would flashing it to a Imate or TyTN ROM help or resolve the problem?
Any advice would be greatly appricated.
Hi, I got a problem similar like yours...
I´m from Spain and I have an ´06 Opel Astra(Vauxhall in UK) with the BT handsfree carkit from factory.
If I make a hard reset to my Vodafone S200 (Orange SPV M600) and leave the machine with the factory settings it works fine with the carkit, but it recognice the carkit like a headset handsfree. But if i restore a back up with the TomTom 6 installed... wow, then start the problems... the handsfree conect with the S200 but after a few seconds the connection is over...
I don´t know if have you got some kind of navigation system, but in my case the problems starts when I install the TomTom... I´m sure it changes some drivers of the BT and this makes the don´t works propertly.
I don´t know what to do...
PArrot Car Kit
I have the same problem with Parrot Car Kit and I have the latest TYTYN ROM
2006 BMW 3-Series Bluetooth
My car doesn't have bluetooth, but I had a loaner car while my car was under the knife. The loaner car was a 2006 3-series w/ Bluetooth. The first pair was perfect, but after a few hours.. What a POS.
I have the latest ROM on my phone, and that didn't make a difference.
No issues on my 5 series, but I have one of the first ULF modules in mine.
From reading TyTN Bluetooth issues around the net and on this forum, it seems to be an issue with the TyTN having some kind of power save mode which turns the bluetooth off after some time.
Kinda stupid, anyone know some registry crack to turn any power saving off?
I have a Parrot CK3100 in a BMW and a brand new SPV M3100. All was working well with my M600 but as soon as I swapped the phone for the M3100 last week I've had problems as described by the OP. Bluetooth keeps switching itself off on the SPV. It works well enough to start with and then suddenly it disconnects. Re-pairing works and it's worth going to bluetooth settings and turning it back on again before you try re-pairing.
Surely there must be an easy fix for this problem - I'm just really pleased I'm not the only one with this fault.
............
Your all quite lucky it works at all..mine doesn't do anything
My Ford Fiesta has been waiting for an 'software upgrade' since October !!
Promised it would be available before Xmas but nothing happened.
lifterus said:
Try and replicate the problem with a different phone if possible. One that BMW supports. If can replicate it, then they'll update the firmware on the BT unit in the car. This happened to me. But I had to prove my case using my girlfriend's RAZR before they'd listen and stop blaming my phone as the cause.
Click to expand...
Click to collapse
I dont think it is a problem with the BMW carkit as it worked fine with my SPV M600 (Prophet)