Hello!
First of all i want to apologize if i posted in the wrong place. I have an HTC Touch Pro which is running with a 6.5 cooked version (qsqa). The problem is with the headset HTC RC E100 which from this morning behaves strangely.
Before upgrading to a cooked version i had 6.1. The headset worked fine on both versions (though only one day with the cooked version). I said strangely because:
- the phone recognize it as headphone *(though not all times)
- the phone does NOT recognize all of the buttons on the headset (call, end call, volup, voldown, play, mute, hold, next, prev)
Please help.
Desperately yours, Gabi
Related
I have bought a Plantronics M3000 bluetooth headset for my QTEK 2020. I have no problems pairing, calling and answering. However the headset just shuts off after a few minutes of conversation. It doesn't just cut the conversation but shuts off. I can make multiple short calls but nothing longer than 3/4 minutes. It works, however, without problems on my wife's Ericsson T68. Anyone can help ? Thanks.
Marek
Hello,
I have the MDA2 (same as QTek2020) and a Plantronics M3000 and It's been working just fine.
The problem you describe it's very weird since you mentioned that the headset works fine with your wife's mobile, and that makes me think that your QTek has some sort of problem with the Bluetooth stack or hardware.
It may be well worth to try (if possible) another headset just to make sure that is not the M3000 fault.
Do you see any type of error or message on the screen at the time of disconnection?
Does it always cut the conversation at the exact same moment?
Does the problem match the time the QTek takes to power save?
Any other clues?
Thanks.
I did not have the occasion to test another BT headset on the Qtek. When it shuts down there isn't any message displayed.
I have no problems with the BT stack (with the Pocket Bluetooth Tools patch) when using it with a BT GPS (Emtac) receiver, it works for hours.
However, your suggestion that it might happen when the Qtek goes in energy saving mode is interesting. I will check that tomorrow.
I'll post the result.
Hi
I seem to have a similar poblem after installing pocket bluetooth tools!.
I use a Jabra BT 250..and I noticed that the headset just mutes during the call..
I am generally used to switching off the display of the XDA after placing the call to power save ...
So I discovered that the headset would mute whenever i switch off the xda after making the call (which it never did prior to installing PBT)!
any thoughts on that?
maybe it has to do with the auto switch off plugin?
Actually I just experienced that too...
If I place (or answer a call) the next time I try to use the phone via the BT headset I notice the BT headset was turned off... Yeah, it could be related to the Powersave feature on the today plugin that PBT installs as a plugin... :roll:
Need to investigate...
Best regards,
Rayan
Both my bt headsets have stopped working since installing pocket bluetooth tools latest version, I have reverted back to version 1005 and everything is fine. I have a sony-ericsson EBH-65 and a skypower clip on headset.
my platronics does the same also its annoying you cant even transfer the call back to the device you have to hand up turn off bt and then turn it abck on and headset mode back on it also does the same on my pc
when im on msn using it as a headset it just d/c and i have to turn it off and turn it back on again
dont see what the problem is
btw the range on the xda2 and platronics is amazing i had it on my bedrooms desk and i went outside it passed through the living room wall and the patio window and i was stood 5m down my garden im sure it would of been over 10m and it was still working if i kept still when i moved it went crackly but ah well lol
just hope someone sorts the prob out
Hi,
I was having the same problem with the M3000. I just had confirmation from Plantronics that this problem is a bug in the product that occurs with the XDA II. I am currently in the process of returning the product.
Regards...Mike
Same problem M3000 doesn't work. Give up now before too much frustration makes you feel ill.
Try the Hello 2 headset. Work with my Aussie XDA2 and is very small and lightweight. Even had a neck chain to carry it around like a USB drive.
Hi all.
Well, having updated to Darkforce rom and radio 1.15, I have *nearly* been convinced to switch to WM6 permanently. However, one issue is still plagueing me, and has been the same in all WM6 roms, no matter what radio I have installed.
When I get an incoming call, my headset will not reconnect. I hae to manually press the headset button to get audio to the headset, then again to answer the call. This does not always work. In WM5, my headset (Blutrek G2) can be in sleep mode, but the UNiversal always wakes it up for an incoming call.
Anyone have any ideas?
Thanks muchly.
Darkforce wm6 & radio 1.15 & sony hbh660: incoming and outgoing calls perfectly working without any button push.
Thanks for the reply. I've decided to ditch the Blutrek. Bought a Sony HBH-PV700 today and all is fine. Voice dial working as well
Hi All,
I just had a brand new Car with Bluetooth. (Citroen C4 Grande Picasso)
With this Bluetooth I should have the abbility to to connect, answer, and scroll trough the contacts, of my phone. I'm using a Wizard G3 with WM6 (Dutch) IPL/ SPL 3.08 and Radio: 1.08. (Radio will be updated soon)
Probelm is: stuff is not working! I can connect the phone to the car with Bluetooth and it is recognizing it. When I make a call or one comes in, the Car sees it and mutes the audio. But that's all. I do not hear anything and I can't be heard. Also the button (on the steering wheel) for contacts doesn't work; meaning: It says: there are no contacts.
Who experienced the same pproblems and more important who solved these?
Hi Jedeve,
I have the same problem with the same car. It worked for me when I first started TT and then automatically my bluetooth GPS mouse was connected and all was working fine. Strnage but true. It looks like if a channel is set open when connecting to the bluetooth GPS mouse and stay open so evrything is working. I also have looked into registry setting son bluetooth if I can find differences by using diff but no strange differences where found.
I also talked to the Citroen dealer and they told that it might be possible that new telephones with the newest software are not able to work correctly with the carkit.
I have a Wizard (I think a G3) with Octavoi 9.2 on it, IPL/ SPL 3.08 and Radio: 2.71.11.
Hi,
same car and same problem here.
It seems worked with WM5 and problem showed after upgrading to WM6.
Calling/answering from car controls ends with total silence most times.
I've noticed that if a call is answered from phone it works most times.
Also car phonebook seems support only latin characters and any contacts with non-latin ones(cyrillic in my case) do not appear on car.
Would appreciate any suggestions/solution to above problems.
Hi,
I have same problem, with same car! with TNT wm6 Roms!
With new TNT 6.1 did not try yet...
Now I have Slim wm6.1 ROM and no problem! With NTS wm6 rom not problem too... works fine!
Well, this is not really a question or problem. But just a headsup that the Diamond works just fine with my Nokia CK-7W.
However it would also be nice to hear from you guys (and girls) as well, since I can't imagine I'm the only one with succes!
You might wonder "Why the hell do you post this?!". Well, that's simple because when I wanted to find out whether that Nokia carkit would work together with the Diamond I coulnd't find anything.
And since my experiences with Nokia carkits and HTC phones weren't all that good (read: BAD, lots of echo and weird connection problems) I was pretty anxious to give this a try.
After testing it on another CK-7W, which was already built in a car, I figured it worked perfectly so I took the plunge and got one for my car.
(Before you ask, why no parrot or other brand? I was able to get my hands on this one really cheap.)
The only problem I got was the first time I wanted to pair the device. Every time after entering the 4 digit passcode I got a message saying the passcode was incorrect. Instantly, not even trying to connect. After leaving it all alone for 10-15 minutes and I tried to connect again it suddenly worked without any problems. And it's still working with no issues at all.
ROM I use:
SWIFTBL WWE DIAMOND ROM V7.5
OS Version: CE 5.2.20755 (Build 20755 AKU 1.4.0)
Base ROM Version: 1.93.405.1 UK WWE
So.. more succes stories here? Or problems?
Hi
I have the same setup, Nokia CK-7W in my volvo s60 connected to my MDA Compact IV running swiftbldade 7.5.
It all works perfect.
I even have MS Voice command setup with it and it annonuces incoming callers and messages perfectly and voice dialling works perfect as well.
Call quality is very good as well.
Shaks
Hey - I've got my CK-7W working fine too, except I'd like to also enable wireless stereo... but the option doesn't seem to exist... I bought the CK-7W off a friend, and he was able to use wireless stereo, but I cn't - has anyone else had any success...?
Relly something I want for using TomTom, etc...
Hi i have CK-7W car kit and I am having problems getting my Diamond to pair can you please advise how you guys paired your ones?
Can't say anything more than I just used the normal way to pair, go to bluetooth settings, search for device and select the carkit + enter correct passcode.
I did however have some problems in the beginning. It would find the carkit but after entering the passcode it said pairing failed.
But when I tried later again it went without a problem, and it paired everytime without a problem ever since.
I dont think the ck-7w supports stereo audio. There are however apps that can route the audio over the carkit. BTAudio is one called if I remember correctly. That way you can have the tomtom over the carkit, but quality isn't that good really.
And some say that using that audio routing also gives 'problems' sometimes, as in it sometimes seems like there is audio (e.g. the car radio is muted) but you don't hear anything for a few secs. So that can be quite annoying.
hmmm??? My diamond wont even pick up the car kit during the search!
I had some problems pairing in the first place...
Don't try to search for the car-kit using the phone, just have your Diamond on BT visible to others, and the car-kit will try to connect automatically... I think you might need to hold the button on the car-kit down for like 10 seconds for it to search, but definately let the kit find the phone, not the other way around...
I fitted one of these to my brother in law's car the other day. Tested it with my diamond, but i expected it to be cross compatible.
Bit offtopic, but what's the advantage compared with a just as pricy parrot system?
Hi Y'all,
I am using my Diamond with the nokia CK-7W and it works fine as well. Paired up without much fuss....
Riel said:
Bit offtopic, but what's the advantage compared with a just as pricy parrot system?
Click to expand...
Click to collapse
Eh.. none? I find the quality better compared to my old ck3300 parrot carkit. However, this one doesnt have a small lcd display or something. Not that I missed the lcd screen though, but sure was a nice feature.
Best thing about the parrot was that it's possible to put a new firmware on it. Could make them a little bit more 'future-proof'.
Nokia CK-7W with HTC Touch Diamond2, VITO VoiceDialer
Pairing the device was easy. In coming calls are working. Push on the carkit button and I can answer the call.
The problem that I have is that I can't do a voice call. If I push on the carkit button nothing happens. I would have expected that the VoiceDialer app would be started and I could make a voice call. The VoiceDialer app works without bluetooth.
Has anyone an idea how I get voice dialing working?
Remark:
With my pervious cell phone Motorola L6 was this possible. Pushed on the carkitt button, wait on the beep, say the name, when recognized it repeats the name and the number was dialed by the phone.
Hello everyone,
I have a somewhat cryptic and annoying problem here. I use an HTC Touch HD (Blackstone) with a hama BSH-240 BT stereo headset. The headset is a four-button one (play/pause, stop, vol up, vol down) with long presses and dual-presses serving as extra keys. It's about one year old, and I used it with my iPAQ rw6815 before switching to Blackstone. Always worked perfectly.
Call me a perv, but I rather like TouchFLO 3d, and it, too, worked for me just fine for two months. Then, SUDDENLY.
Well, not so suddenly, actually, because I did a few things with my phone the day before I ran into the problem: uploaded a few more tracks onto my card, built a new playlist in WMP, and tried a wired headset (since I wanted to listen to a certain radio show).
The first sign of trouble (not sure if it's related at all) was that HTC Audio Manager didn't see my new WMP playlists - I tried it building a new one a couple of times to no effect. I simply started playing from the All Music list (fine by me, that's what my primary playlist is anyway), but then I noticed that the Audio Manager no longer responded to the Play/Pause button on my headset. All other buttons worked fine, and I'm pretty sure it's not a hardware problem, since the long press on the same button works okay (it's 'repeat last call').
The usual rain dancing didn't help at all (remove/add the Audio Manager tab, re-pair the headset, soft reset) and looking through the TouchFLO/WMP/WM options gave me no clues either.
I googled for hints and searched the forums as well, but didn't find anything of relevance.
I do not expect a magic solution for this, but perhaps someone has run into this problem before me and can give me some hints?
Sorry if I'm missing something obvious, could be a dumb moment on my part.
Thanks in advance
Sorry for bumping this, but I have some new information about my problems.
First of all, I made sure the hardware is okay by digging up my old iPAQ and pairing my headset to it. Everything works top-notch.
Moreover, when WMP is running on my Touch HD, all the headset controls work in it. (This means the device is fully usable after all, but I really like the Audio Manager a lot more.) I have a weird feeling WMP somehow hijacked AVRCP from HTC Audio Manager.
Any ideas on how to fix it, perhaps?