Hi,
I have a strange comportment of my Diamond when I try to pair bluetooth devices whitch have pairing code different of 0000.
Everytime I try to give the pairing code of the device (1234, not changeable), the enterred code in cleared when choosing the "next" button.
(assuming then that code is not needed or is 0000).
Has anybody a solution for this problem ?
Diamond is with original firmware from HTC (the one dowmloadable on there site).
Thanks in advance for your answers
Bouhboulle.
More of the same
I have the same problem (posted earlier). My car's hands-free requires a random code provided during the pairing process, and pairing never succeeds. I understand the Diamond tries 'standard' codes - 0000, 1111, 1234, etc. is there a way to disable this?
Me too
The same for me using Diamond from Vodafone with Vodafone 3D touchflo. I can't pair with any BT device. Please help from anybody.
Thanks a lot.
I do not have this issue.
I can pair with any code on laptop. And my carkit (parrot) just pairs perfect with 1234
BUT
When entered the code, just WAIT, and don't fill it in again. I often see the 'code' field again, and want to enter. Pairing twice gives error etc. Just ignore the empty field, when paired it dissapears.
Think its a tiny bug.
Still the same...
Hi Riel.
There is no option to enter the code twice, once you press next automatically deletes the field and acts as an enter.
BUT, surprisingly, I have installed a cooked ROM and the same again... I now have my doubts about the BT application, I think is the original one from the OS and not an cooked accessory.
I hope that anybody reading this could put some light on it as is one of the strangest behaving I've seen around PDAs in many years.
Thanks for any help.
Its strange my diamond works fine with parrot kit but not with my bt kit
anyone knw why,
Here is the solution
Go Start/settings/connections/bluetooth/right down press security tab and uncheck passkey
Doesn't work, for me at least...
turboss said:
Here is the solution
Go Start/settings/connections/bluetooth/right down press security tab and uncheck passkey
Click to expand...
Click to collapse
Thanks for the answer but I have tried and doesn't work. On the screen says this is for infrared connections, or am I lost?.
Cheers.
EDIT: I got it finally but the only way is to flash the original ROM and later the one you like. Also remember that some devices does not support more than one pairing partner, this happened to me with a Nokia BT headset, I had to refresh it.
Good luck.
Related
Hi guys,
I am at the end of my tether... I just bought a JVC head unit with on board bluetooth, so I can use it as a car kit. But I can't get my Treo 750 to pair with it! It just locks up after I enter the passkey... and the car kit just says "error" after a certain amount of time. I'm running a vanilla (extended ROM removed) version of the 3 Australia ROM.
So, I rolled back to Windows Mobile 5... same problem... UNTIL I went into the Bluetooth settings and setup an incoming COM port. Then it paired up perfectly and all was well.
So I've reinstalled WM6, but it doesn't have the option to create an incoming COM port. That's really annoying. I've googled a heap, and searched these forums a fair bit too, but haven't been able to find any sort of workaround. Is there a registry hack, third party program, or some other way I can tell it to allow an incoming connection from the car kit?
Thanks in advance!
Has anyone had any ideas on this? I have a real issue now, as I rolled back to a WM5 ROM which I found on these forums but I'm having awful problems with it - it drops calls all the time and sometimes they just go silent..... the call stays connected but I can't hear the person on the other end.
I really need to get either the original Telstra WM5 ROM, or a way of getting WM6 to work with my car kit! Any ideas... anyone??
Okay... now I really feel like I'm talking to myself but anyway.... thought I'd give an update.
After heaps of trial and error, I managed to install the Universal version of the Broadcomm bluetooth stack onto my device. And it pairs - hooray!
However... when I make a call, no sound comes through the speakers
No other version of the Broadcomm stack will run on my Treo, I just get the memory error that lots of other people have mentioned.
Chalk another person down who's royally annoyed with Palm for putting such a dodgy implementation of Bluetooth into these devices. It's my one and only bugbear to date.
I have exactly the same problem when pairing my WM6 Treo 750 to a Parrot MK6100 carkit. After entering the passcode on the Treo, the device just hangs. The carkit says it has connected succesfully, but nothing happens. After restarting it does not recognize the carkit at all.
Did you find a solution yet? I am also looking for a different Bluetooth stack that is guaranteed to work with the Treo.
Good to see I'm not the only one. No, I haven't found a solution yet unfortunately
The closest I've come is that hacked Broadcomm Bluetooth stack. My only hope is that some nice developer will help us develop something that works!
Hi Ben,
I solved my problem yesterday. I tried two suggestions.
1) Leave the passcode field blank (do not enter '0000') and press next
2) Install http://www.jetwaremobile.nl (fully functional 30-day trial)
After that pairing succeeded in a couple of seconds and all is working well. Let me know how it works out.
Thanks very much MattMax!
I had tried the Jetware software previously, and it didn't help. But I hadn't tried leaving the passkey field blank. Did that this morning... it popped up with a connection dialog asking if I wanted to allow the connection... went back to the passkey screen, I entered 0000 and away the sucker went. How simple was that!!
I just upgraded to the latest ROW2.23 WM6 ROM the other day, so I'm not sure if that made any difference either. But it's now paired and (seems to be) working well, just need to make and receive a few calls to make sure.
Thanks very much for your suggestion!
Good to hear that it worked out!
I had exactly the same experience, leaving the field blank, after that entering '0000' and it worked. I had just installed Jetware Mobile, but apparently that is not necessary for the solution.
Hi ALL,
Yesterday I updated my T-Mobile MDA II with the WM6.1 from c_shekhar, the 6.1.1b16CS ROM. Everything seems to be fine so far, except the feature I need first of all - connecting my GPS mouse "HOLUX GPSlim 236" via Bluetooth. The PDA just does not want to pair with the mouse. I do not talk yet about tomtom or other software... I'm just doing "Add new device" in Bluetooth settings, the mouse is found, I specify 0000 as passcode and after ~15-20 seconds PDA says "it can not pair because of an error or passcode wrong". The passcode is 0000. If I specify a different passcode, the PDA answers just immediately "can not pair". Bluetooth is turned on of course. The WM6.1 setting "Manage GPS automaticaly" is turned off (I have read that this might be the case). So, is it a kind of Bluetooth defect of this ROM Image on Tmobile-II? Does the WM6.1 have kind of logs or traces to see what happens during "trying to pair"? I applied no other tools after the image upgrade, so the WM6.1 is the only software I have. With my previous Win2003 the GPS mouse worked fine of course. Will appreciate any help. Thanks in advance!
Try clicking on the "managing gps automatically". I'm using the same rom and gps unit and it sure works for me.
Thanks, yes, I tried that option. Does not help.
Actually I noticed why it happens. Turned ON mouse blinks with the blue LED (indicating that bluetooth is active). Now trying to pair with the mouse, I'm forced to specify the passcode 0000 on PDA. At the moment of "authorisation", the blue LED on the mouse STOPS blinking. Why could that be? No idea... Turning the mouse off and then on right away (during pairing) - the LED starts blinking again, but it does not help to pair anyway... I assume that a kind of authorisation protocol has been changed in WM6.1... Any other ideas? Thanks in advance.
Hi, i have similar problems with pairing.
For me it works when i don´t type in a pass code instead the necessary "0000".
After 10-20 Seconds of happening nothing a message pops up that the BT antenna wants to connect with the Pocket PC (very strange, never had before). If you type "No" the device asks a second time and then i say "yes" and it works.
Dont no why but it works.
Another strange thing: when i pair my headset first, which works withoutany problem, pairing with GPS works in most cases very fast - but not every time.
Strange thing
I am having this EXACT issue. gpslim 236. Ive had it for years. For the past to roms ive used, it has been sketchy, they were both 6.1 roms, pdaviet and binkys. I will try a 6.0 rom tonight to see if that fixes the issue.
Im on a hermes by the way, but this was the case for me, until i reverted back to a 6.0 rom. Pairs without issues now, like it used to, like it should
Just updated to Helmi WM6.1 ROM and same problem with GPSlim 236.
worked great on 6.0, enter 0000, paired, no problem. Now, as you said, 0000 tends to fail, then I get prompted that GSPlim wants to pair. Even if I get it paired, com port set, gps viewer still can't find the gps.
Seems a problem in the 6.1 rom.
Ah, noticed that having GPS viewer open gps on the port I set causes bluetooth gps connect confirm to pop up. something very wrong in this new ROM!
Perhaps you should read the wiki about connecting external GPS devices for Himalaya. I use bluetooth for everything, including with an external GPS device, and this is the best rom for it.
I would be very surprised if the problem was caused by the rom.
Appreciate that it works for you, but it doesn't work for me and the others here.
stock WM5 & WM6 Helmi worked fine. WM6.1 does this weird thing where the proper passcode of 0000 doesn't work.
Connects fine with my jawbone & my PC. it's just our GPSlim236
Hi @all!
I know there are many BT issues concerning TyTN II and WM6. But this one is new, I think:
After pairing my Kaiser (WM6.1) with my BMW E46 handsfree unit, the first call I make immediately after pairing works fine. But after terminating this first call, there is no sound at all. Neither my Kaiser nor the handsfree unit utters a sound, though my Kaiser displays the small handsfree-icon, that confirms the connection is established.
I tried so many things to solve this problem. I tried different radios and different ROMs. But nothing worked till now.
Does anybody have an idea?
-------------------------------------------------------------------------
I soved the problem on my own!
First, the BT extension software "JETWARE" didn't help. But then I changed the JETWARE settings - and voilà: this was the thing. In advanced options I selected "Phonebooks", "Query status indicators", "Update status indicators" ang "Hang up/ swap to incoming call". All other options in advanced options I unselected. Then in phonebook options I selected all categories to sync, opened the "menu" -> "set limits", selected "Exclude Fax numbers" and "Limit how many numbers to sync" and set all options to 0.
Then I hit "Done", "Done" and one more time "Done" and connected my Kaiser with my BMW Handsfree unit (E46 ULF). And what happened was unbelievable. It worked perfectly suddenly.
Maybe this workthrough can help anybody else.
My conclusion: JETWARE solves the silence problem, you just have to choose the right options in JETWARE settings!
Greets to all active board users!
Here are some specs:
HTC Kaiser
ROM: Official HTC WM6.1 Professional 3.03.405.0 WWE
Radio: 1.64.06.04
Protocol: 25.70.40.02W
Do a search for "Unexplained volume drop to zero".
It's an ongoing thread about this exact problem.
My problem is different, I think, because after turning bluetooth off in comm-manager, sound works fine again immediately.
Any ideas?
I have a similar issue when I pair my Tilt with the Parrot MK6100. It will work for a while and then I can try calling someone or receiving a call. It shows connected, but I do not hear anything. The far end cannot hear anything either. What works for me is to reset the Parrot by turning it off and then back on.
I would be interested in a fix for this.
Tried to solve the problem by turning off htc home. but no success. i'm getting mad ...
BMW bluetooth problem
I had a similar prblem with my BMW 740 e38, which uses teh same ULF box. I cured it by disconnecting teh battery. Note, if your radio uses a key code, check you have it before disconecting teh battery!
Good luck.
Richard Racer
I have the same problem with my Audi, I think it is the Bluetooth in the car rather than the handset. I get this problem with several handsets. You might want to see is BMW has an update.
Diconnecting the car battery (for more than 30 minutes) didn't solve the problem.
Nobody out there who can help?!?!?!?!?!?
I'm getting mad ..................
mynameisrabbit said:
Nobody out there who can help?!?!?!?!?!?
I'm getting mad ..................
Click to expand...
Click to collapse
Try Jetware, it is a 30 day trial but I think it is the BT software in your BMW. Check some BMW forums and see if there is an update.
Bluetooth Issue
Hi guys,
it is definitely the TyTy II and not the Bluetooth in your car!
I have a Parrot MK 6000 in my Honda and had NO issues with my previous HTC TyTn in combination with the Parrot or any other bluetooth hands free.
After every phone call the phone looses bluetooth connection and re connects after a minute or so.
Really annoying! I'm thinking to get rid of the phone if there is no update very soon.
jetware doesn't solve the problem.
is ist possible that the protocol is the reason?
first, i supposed, the reason for that annoying problem could be the number of contacts in pocket outlook.
but in fact i really have no idea till now.
anybody out there who can HELP??????????
SOLVED
Look at my first post!
mynameisrabbit said:
Hi @all!
I know there are many BT issues concerning TyTN II and WM6. But this one is new, I think:
After pairing my Kaiser (WM6.1) with my BMW E46 handsfree unit, the first call I make immediately after pairing works fine. But after terminating this first call, there is no sound at all. Neither my Kaiser nor the handsfree unit utters a sound, though my Kaiser displays the small handsfree-icon, that confirms the connection is established.
I tried so many things to solve this problem. I tried different radios and different ROMs. But nothing worked till now.
Does anybody have an idea?
-------------------------------------------------------------------------
I soved the problem on my own!
First, the BT extension software "JETWARE" didn't help. But then I changed the JETWARE settings - and voilà: this was the thing. In advanced options I selected "Phonebooks", "Query status indicators", "Update status indicators" ang "Hang up/ swap to incoming call". All other options in advanced options I unselected. Then in phonebook options I selected all categories to sync, opened the "menu" -> "set limits", selected "Exclude Fax numbers" and "Limit how many numbers to sync" and set all options to 0.
Then I hit "Done", "Done" and one more time "Done" and connected my Kaiser with my BMW Handsfree unit (E46 ULF). And what happened was unbelievable. It worked perfectly suddenly.
Maybe this workthrough can help anybody else.
My conclusion: JETWARE solves the silence problem, you just have to choose the right options in JETWARE settings!
Greets to all active board users!
Click to expand...
Click to collapse
I will try your settings with my 2005 X5 tomorrow...but as I can see in the set of settings you have chosen, there is no contacts transfer, no last dialed, no sms can you please confirm?
rabbit,
i have the same exact problem (lose sync with phone immediately after a call, then re-initiates contact a minute or so later), but is getting yet another app the only solution?? is there any other solution that fixes the WM6.5?
Hi!
Let's see if someone can shed some light on this.
I flashed my Diamond to 6.5 yesterday, l3v5y's clean rom to be more specific.
I'm really happy with it except my new bluetooth headset also arrived yesterday and it just wont pair.
The headset is a sennheiser vmx100, which is generally quite troublesome to pair with mobile devices. I've had one before which worked great with wm 6.1.
The main problem with the vmx100 is that sennheiser's engineers appears to have a screw loose or something since the headset doesn't have a passcode for bluetooth. The manual specifies 0000 but that never worked on my old headset with 6.1 or with this new one on my computer, you just enter a blank passcode or none at all and everything just works.
The only problem is wm 6.5, or at least l3v5y's version, has two separate passcode windows. The first one accepts a blank passcode and then asks you if you want to add the headset to the device list. Then comes another window asking for a passcode again, and this one does not accept a blank code. On wm 6.1 it did if you entered something and then erased it but this one just don't.
Does anyone have a good idea on how to solve this?
Edit: I might add that i've tried the trick detailed in another thread where you enter a blank passcode first and the 0000 and unfortunately it does not work.
Cheers
Same problem here,
sennheiser vmx100 with htc touch pro WM6.5
The trick with blank passkey does not work anymore (in the last ROM i upgraded)
did you manage to pair it?
Hello friends,
I have been unsuccessfully looking for a solution for two problems I have with my Diamond2 and the Bluetooth carkits of my two cars. I have found several threads with similar scenarios but I have not found a solution.
My Diamond2 is running the latest ROM available in HTC assistance page (RUU_Topaz_S2_HTC_SPA_2.53.412.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe) without any modification apart from some applications installed (TOMTOM, TotalCommander, ...)
Problem 1
=======
Scenario: 3 years old opel/vauxhall carkit
Everything works, the phone pairs with the car and I can make calls. The problem is that the Bluetooth of the Diamond2 turns off randomly and I have to switch it on to make it work again, which is quite annoying while you are driving.
I have found a CAB called BTrestore.cab that checks the Bluetooth and turns it on if it is off. This works, but the problems is that this software discharges the battery very quickly. There are also some registry tweaks that are supposed to solve the problem, but I tested them with no success.
Problem 2
=======
Scenario: Latest SKODA/VW rsap carkit (Skoda Columbus with Bluetooth premium)
Everything works, the phone pairs with the car and I can make calls. The problem is that sometimes when I leave the car and the Dimaond2 disconnects of the carkit, it loses the phone signal and the only way I have found to recover it is restarting the phone. This does not happen always, only occasionally, but if I forget to check if the phone is working after leaving the car, I end up missing calls.
I would appreciate it so much if someone could help me to solve these problems.
Thank you in advance and best regards,
Javier
Set Turn off Visible mode - Never
I have the same problem with my HTC Diamond II and a Opel Corsa with integrated bluetooth handsfree. The bluetooth on my phone turns itself off all the time, I can turn it on again and after 2 or 10 min. it turns off again. I have upgraded the car with the latest sofware, but no improvement.
andonov said:
Set Turn off Visible mode - Never
Click to expand...
Click to collapse
Thanks for your answer Andonov. Sadly, that setting does not solve any of my two problems .
Try the attached solution i made for the same issue. It does not drain the battery and works like a charm. You need to install mortscript. Copy the toggle app to your card and change the script to point to your SD card( i had mine for the Diamond 1)
ghosty7 said:
Try the attached solution i made for the same issue. It does not drain the battery and works like a charm. You need to install mortscript. Copy the toggle app to your card and change the script to point to your SD card( i had mine for the Diamond 1)
Click to expand...
Click to collapse
Thanks Ghosty7! I'll try it.
I am also trying two workarounds but it is not clear to me yet if they work:
* For the first problem, it seems that disabling the rsap option of bluetooth makes the connection last longer, but I haven't done a long trip yet to test it to be sure of this. Nevertheless, without rsap, I have seen the connection to last more than 10 minutes, what was unbelivible before.
* For the problem two, I have manually configured GSM connection, I mean, I have set the GSM band and "protocol" instead of leaving it as automatic.
I will tell you if something of all this works.
Sorry to butt in here, but I have another issue with BT and car kits, which someone may be able to help with.
With many of the latest cooked ROMs, when I pair my Topaz with my car kit, and I get to the page where you input the pairing code, the keyboard changes from a QWERTY to a numeric keypad. From that moment on, I have lost access to any form of keyboard other than the numeric one. On the keypad options pop-up, I can select Full QWERTY, Compact QWERTY, but there is no change to the numeric keypad.
I did find a cab file many months ago which cleared this and restored the keyboard choices. But this seems to cause issues with the hardware buttons, which stop responding.
Does anyone know a safe way to reinstate the keyboards after a car kit has caused the keyboard to premanently change to a numeric kepypad?
Thanks.
Hissing Syd said:
Sorry to butt in here, but I have another issue with BT and car kits, which someone may be able to help with.
With many of the latest cooked ROMs, when I pair my Topaz with my car kit, and I get to the page where you input the pairing code, the keyboard changes from a QWERTY to a numeric keypad. From that moment on, I have lost access to any form of keyboard other than the numeric one. On the keypad options pop-up, I can select Full QWERTY, Compact QWERTY, but there is no change to the numeric keypad.
I did find a cab file many months ago which cleared this and restored the keyboard choices. But this seems to cause issues with the hardware buttons, which stop responding.
Does anyone know a safe way to reinstate the keyboards after a car kit has caused the keyboard to premanently change to a numeric kepypad?
Thanks.
Click to expand...
Click to collapse
Have you tried SIP change?
Bruce Inman said:
Have you tried SIP change?
Click to expand...
Click to collapse
Thanks for that. I'll give it a go.
Hi,
I have the same problem number 2 with my vw premium carkit. I wrote to the HTC support regarding this problem. First they asked me to send them the photo of the phone screen when the problem occurs. After that they sent me btspy and sked me to make some logs, however, the btspy does not want to run on my phone (something about missing certificates and/or files). Replied to them I can't run the program and no reply for over 2 weeks. I'm staring to think I'm gonna lodge a complaint to them and ask to repair the issue or replace the phone with a one where the problem won't appea, it's still on the 2 year guarantee