Hope someone can help. I have had an XDA IIi for a few months now, and apart from the daily crashing, I absolutely love the unit (crashing easliy remedied by quick soft resets). I now have one problem though- my O2 Blue headset connects OK, but any incoming calls are just silent when picked up (apart from a slight buzz). Replaced with another O2 Blue headset and problem persists. Headsets are OK with other phones (Nokia 6310i). This problem started 1 month ago and before then it worked fine. Any ideas?
i've had this with my car h.f.k, only way I've found to solve it so far, is a hard reset and then re-pairing
soft reset doesn't work
deleting pairing doesn't work
sorry
Related
I'm having several problems with my Qtek 9090
There's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off.
People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone.
I haven't been able to find a BT headset that works with it. They all have the same problem; The sound scratch so much they're unusable. I tried 3 different brands that all works well with my 2020!
The GSM link often "falls out" - even though there's plenty of link the phone doesn't work (nothing happens when I try to call someone). A soft reset solves this problem!
As you can see, I can hardly use the device as a phone at all I've had the device replaced once, but all the problems persists on the replacement.
Does anyone have similar problems?
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Try a Motorola HS810 headset... works fine for me.
harry_mb said:
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Click to expand...
Click to collapse
I've already tried Jabra Freespeak 250, which didn't work for me
No I haven't updated the ROM as I've been told by the supplier that no new version is available yet!
outz said:
Try a Motorola HS810 headset... works fine for me.
Click to expand...
Click to collapse
I also tried both a Motorola and a SonyEricsson BT headset, but I don't remember the specific models - they both scratched immensely
i use SE 60 and it works ok
As you said, the Jabra250 is pretty much unusable!
Crackling is not constant but goes in waves, even though I do not move.
Am at a bit of a loss what to do now... the device is great apart from this.
>> People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone
yes PBT read my other post
I have the same problem!!
it is scandalous to sel an device with this big defect!!
Sony HBH-660 works good for me.
People say that they can't hear me when I use the handset, but I don't have any crackling, etc with the headset and voice is clear. You just never know if the headset is going to connect when the phone rings though.
sound from screen
there's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off
Click to expand...
Click to collapse
I have this problem also, I was told to use the new rom but this has made no difference, Please let me know if you have found a solution
[/quote]
Guys,
the hissing coming from the screen is a power supply problem. keep swapping phones until it goes away! I used to build switching power supply and the hissing (in a system designed to operate well above 20kHz) is only able to be heared when unstable, inductor core or cap is broken. The hissing is very 'not normal'.
It appears that the Q9090 is standing out as having more problems than the MDAIII, one is the mic volume, most of the other phones are not complaining about this so there may be something with they way the Q9090 are updated or shipped.
With the Jabra 250, don't forget to pair it pressing BOTH the volume and phone button on the headset on discovery with the 9090.(On bonding, turn off headset, turn on again pressing both buttons)
Funny thing is, I had the cracking also. I deleted the headset in BT manager and paired it again as described above. Now it works ok.
Hi,
I bought a Qtek 9090 a few days ago and I also have the same problem with volume level. People can't hear me when speaking, either with the headset or base microphone.
Using a different headset doesn't help (that's even worse sometimes) but I didn't try a BT heaset (and I don't want to as it would raise potential connection problems). I'm going to contact Qtek for support on this...
Pierre
I too am having problems with the Jabra 250 BT headset and my SPV M2000. The Jabra 250 worked fine on the XDAII but is terribly crackly on the newer model.
This is even when pairing it with the enhanced pairing of pressing Volume Up and Phone button together to pair.
Any ideas?
qtek 9090 bluetooth problem
Hi All,
I have new qtek9090 with cellink bluetooth headset. It is work normal, but i am loosing connection to headset each time qtek go to stand by mode. I need to switch off/on the bluetooth in order to restore the connection. Any ideas?
I often get a message stating:
"The Bluetooth Radio failed to turn ON due to insufficient driver momory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."
Does your device also give you this message?
Is it also using the Broadcom "Bluetooth for Windows CE BT-PPC/PE Version 1.0.0 Build 2200"?
Interested to know if you have the same problems with the same bluetooth driver.
same problem
My qtek 9090 shows te same problem
This is a known problem with the Blue Angel, unfortunately, until they bring out a fix, all you can do is a soft reset.
upgrade
hi all,
how can i get updates from www.imateclub.com?
I can't register there, because I have qtek 9090 and not i-mate
thanks
O2 Sourced info on which BT headsets work
See: http://www.my-xda.com/downloads/Other_Bluetooth.pdf
Please help!
I am having problems with my blue tooth handsfree and my O2 XDA IIi.
The Xda recognises, connects and is paired with the headset and vice versa. However when connected, all I can hear is static through the head set.
I have tried the headset on another phone and it works fine, also have tried friends headsets on XDA and again only static can be heard.
Any advice would be gratefully received!!!
Ah hah! I'm back and a happy bunny!!! Managed to work it out all by my little self. - If you cold reboot the XDAii by holding down the power button at the same time as pressing the reset, when you restore, the handsfree kit works!!!
Probably really simple to some of you high techies out there but I'm proud of me!!!
In fact, what are you doing is hard reboot the PDA and cause all the program run into manufacturer setting and it will cost all your program and setting lost.
I'm facing this issues before. Whereby, all type of bluetooth is not functioning although that able to recognize by PDA. At the same time, when incoming call received, the ringing tone will like inconsistent/jerking.
It's due to database problem .....
Sorry if I'm posting a question that's been answerred before, but I haven't been able to find a thread to this problem:
sometimes my Nokia BH-102 will disconnect in the middle of a conversation in the car. The only option at that time is to pull the TP2 from it's holder and put it to my ear.
Whether it's the headset or the phone, I don't know, but it used to work in combo with the old Nokia E60 I used to operate......
Chances are it's the TP2, but how to fix it?
Only 'tweak' was to install tomtom, but without the 2 dll's which have been causing some problems.
Has anybody experienced anything similar?
Bluetooth visor problem
I have had problems with my headset - Supertooth Visor One Bluetooth Car Kit. Not quite the same as you though - the problems I have is that when I make an outgoing call, everything works fine but when I recieve an incoming call the audio stays on the handset rather than coming out of the bluetooth headset - which means I have to pick up the phone. I also have installed TomTom 7 and I had to do the 2 dll fix as my bluetooth was completely broken otherwise. So I guess maybe TT7 is responsible in some way. Only thing is, I dont want to do a hard reset to find out!!
I'd already read about the Tomtom BT-issue so I cleared the 2 dll's out of the cab prior to installation.
So the originals should still be in use. BT is/was working and I have been synching using BT. That's not the problem.
There should be threads out here pointing you to the original dll's. you could past them over the current ones and see if it helps.
I experiencing the same problem, and didn´t install tomtom.
So now it looks like it's a problem in the TP2 then.
Hopefully a BT-guru can investigate? This is way beyond my capabilities.
In the meantime I'll know what to do if and when it happens: take a chance on the cops seeing it and issuing a ticket.....
I'm having a similar issue, my headsets plural, have this problem. It will disconnect but what is happening is the headset is shutting down. If I hold the power button on the headset it comes back on and will work again.
If it was one headset I would think it is faulty but I've had this problem with three headsets and the Bluetooth in my car.
Is it possible that the phone is sending a shutdown command? BTW I am using the stock TMOUS 6,5 ROM and have tried some of the cooked ROMS with the same effect.
Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.
Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?
I have exactly the same problem as you
good to hear I am not the only one. Hope someone will come up with a solution for this.
I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.
Would a custom ROM be a solution for us?
I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?
I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.
My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!
Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????
bluetooth settings, advanced, enable beam data exchange,check the box
Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!
K this is getting old. A couple weeks ago while I was still running the stock install of my Sprint Galaxy Note II, after the update on april 28th ( or near there), my earpiece just quit working in the middle of a call. The speakerphone and bluetooth headset were still working but nothing out of the earpiece. I tried everything to get it working again, even so far as doing a factory reset and nothing worked. So I got a new one that worked for 2 days then the same thing.
SO I figure it was the software update. Rooted and put on [ROM][Team WHOMP!] Whompasaurus, which worked good for a week and now the same problem. I have seen one other instance of this happening to someone online but no solution. Any ideas would be much appreciated. Just so you know I have, rebooted, re-flashe the rom, plugged in headphones, rebound bluetooth, cleard cache and done everything short of a full wipe and restore... which I will not do every week.
Finally got it working
I finally got it working. I was just looking around the web and I found a forum that said to use *#0*# to test the functions on the phone and it worked after I tested the receiver. Could have something to do with the sequence I did it in so here it is.
1. Used headset for call.
2. Unplugged headset and used keypad to bring up consol *#0*#.
3. Tested "Speaker" then "Receiver" and earpiece started working normally again.
So glad I finally have some kind of a work around.
UPDATE:
That was also a temporary fix. Form what I could find online it seams that the problem was with the headphone jack and I had to have it replaced. Working for now so hopefully I won't have any problems with this one.