Related
I bought my qtek last week and trying ever since to get it connected with my carkit..
Sometimes this works and I can hear and talk through my carkit. Other times it only rings through my carkit and when i pick it up it disconnectw with the carkit and goes back to the qtek. Or it doesn't connect at all.
I've tried several things..
-first I wanted to try the new bluetooth patches.. this works a little better for example without switching on the qtek and turning the key, they automatically connect. Not all times but ik works a little better.
-trying to put a new ROM version on my qtek, got a country id error.. Got rid of it using the xda3nfbtool.. then got a radio image file checksum error.. Don't know how to bypass this because it has to do with the passwords in the xda3nfbtool.exe..
So now I'm here, hoping that some wizzkids know how to get a permanently good bt connection...
Who dares??? Or has suggestions??
Thanks in advance,
Sorry my english isn't my main language
BMW BT with Blue Angel
Same problem here. Have tried all available patches. the 3500 BT version works with the least amount of trouble. But even with this one I never know how long it will take to get it working and wether I will hit a tree in the meantime.
A Friend of mine uses the Motorola Carkit with no problem. I think the BMW System is too complicated with i5s address-book synch to work. By the way, how many adresses do you havein your qtek?
Hi,
I do have at least a very similar problerm with my Audi BT. I can connect, it works just fine when I make a call, BUT it looses connection after picking up an incoming call...
I tried all stacks I could get my hands on from 1900 thru 2400 till 3500 and even 6600...
Anyone with an idea!?
TIA
PEACE AND B WILD!
Re: BMW BT with Blue Angel
jofeuerstein said:
Same problem here. Have tried all available patches. the 3500 BT version works with the least amount of trouble. But even with this one I never know how long it will take to get it working and wether I will hit a tree in the meantime.
A Friend of mine uses the Motorola Carkit with no problem. I think the BMW System is too complicated with i5s address-book synch to work. By the way, how many adresses do you havein your qtek?
Click to expand...
Click to collapse
Don't know how many adresses, about 150... But at this time I have none in the PDA, just to test if the BT connection will work... But it has to do with the connection and not the adress book... I just found out that different models of BMW could have different model of BT carkits. And BMW uses a siemens carkit according to a mechanic from BMW.
I hope someone has the brains to pull this of.. Because how is it possible to get a only sometimes connection. This means that it could work, or is that just my postive attitude.
bmw car kits
by wot i understand bmw are about 100000 years behind with there software on the car kits 6600 t610 v600 etc all work but your new one dropn in and out all the time
Blue Angel and BMW Bluetooth Blues
at Denis123: thanks. I have 4000 adresses on the PDA and thought the problems come because the BMW tries to download them ... if you have the same problems with 150 adresses, then the adresses are not the cause. At the moment with the BT 3500 (+ this small fix on the download section) the paring works and connecting the MDA when I get into the car works mostly. What drives me nuts is that it doesn't work ALWAYS. Sometimes i have to tinker for 15 Minutes while driving until it works. But once the connection worked, it functions very reliably ... until the next time I get into the car.
So the best I can recommend: Latest ROM version plus BT 3500 + this funky extra fix which I don't know what it's good for.
Re: Blue Angel and BMW Bluetooth Blues
jofeuerstein said:
at Denis123: thanks. I have 4000 adresses on the PDA and thought the problems come because the BMW tries to download them ... if you have the same problems with 150 adresses, then the adresses are not the cause. At the moment with the BT 3500 (+ this small fix on the download section) the paring works and connecting the MDA when I get into the car works mostly. What drives me nuts is that it doesn't work ALWAYS. Sometimes i have to tinker for 15 Minutes while driving until it works. But once the connection worked, it functions very reliably ... until the next time I get into the car.
So the best I can recommend: Latest ROM version plus BT 3500 + this funky extra fix which I don't know what it's good for.
Click to expand...
Click to collapse
Can you tell which type of BMW you drive?? And if it's not to much trouble then mention the ROM, Radio version etc you have on your PDA... That is what I (and maybe others) would like to know.
Thanks in advance..
You say that sometimes it takes up to 15 min to get a connection! Maybe this could be due to the phonebook.. I don't no for certain, but if you're BMW tries to take over the adress book of your PDA that could take a while with 4000 entries.. What you could try is, if you're synchronising with your computer leave out the adresses in active sync. So that there are no adresses in your PDA. Then try to pair with the BMW and see what it does... Maybe then it works faster... I'm curious if you get a good connection between the PDA and the Beemer.... Please let me know.
Greetz
Have just installed:
ROM version 1.22.00. WWE
Radio version 1.06.02
ExtROM version 1.22.557 WWE
Tried it AGAIN in my BMW...
First time connection --> connection failed, BT BMW says erfolgreich (succeeded)
Switch contact on/off --> everything works I can phone, and incoming calls also work.. That's how it's suppose to be
Switch contact on/off --> There is a pairing, but as soon as I get an incoming call the phone goes off in the car, but when I answer afther a few seconds the connection is gone.
Switch bluetooth on/off on PDA --> It works again??!!?!
So a early conclusion is that the bluetooth has to be totally switched off when the PDA is off.. If phone rings PDA switches on and connects to carkit.. Does anbody know if this is possible, then I will try it out???
Thanks
I think I have found a solution. I'm not sure but so far this works..
Now I need someone to help with the following...
The bluetooth on the PDA must be switched of when you turn the ignition.
Then when you have your car running you switch on the bleutooth on the PDA... They pair and connect... I've tried it several times and it works...
Now when you switch of your car and turn it back on again the pairing will work but there is no connection. So in my case the phone rings in the car but when i pick it up it switches back to the PDA..
Conclusion; Only when the PDA is switched on the Bleutooth is allowed to switch on... So when you're being phoned, first the PDA goes on and a few seconds later the carkit is active and you're able to pick up through the steering wheel..
SO THIS IS IMPORTANT..
Is someone capable to make a prog. or to delete something in the original bluetooth prog. in PDA that the bleutooth function isn't always ON, only when you put on your PDA...
I really hope someone can help??!?!?!?!
Thanks
Re: Blue Angel and BMW Bluetooth Blues
jofeuerstein said:
at Denis123: thanks. I have 4000 adresses on the PDA and thought the problems come because the BMW tries to download them ... if you have the same problems with 150 adresses, then the adresses are not the cause. At the moment with the BT 3500 (+ this small fix on the download section) the paring works and connecting the MDA when I get into the car works mostly. What drives me nuts is that it doesn't work ALWAYS. Sometimes i have to tinker for 15 Minutes while driving until it works. But once the connection worked, it functions very reliably ... until the next time I get into the car.
So the best I can recommend: Latest ROM version plus BT 3500 + this funky extra fix which I don't know what it's good for.
Click to expand...
Click to collapse
What is the "this small fix on the download section)" Can't find what you mean?
@tbd: forget the fix. It was an older version that I mistakenly downloaded ->my mistake
@dennis123
In the meantime I use:
Ext. Rom 1.22.01 GER
ROM-Datum 10/26/04
Radio-Version 1.06.02
Protokoll Version 1337.38
ExtROM 1.22.182
Bluetooth 1.0.0.3500
Yesterday morning I went to my car with BT OFF, turned the car on, turned BT on and it worked flawlessly.
Yesterday evening I went to the car with BT ON, turned the car on, and the BT paired, but during the first call it dropped the connection.
Same today. => I have at least one reproducable way to get the darn thing working. I can't say that satisfies me, but i will stop wasting time with this ;-)
Has anyone tried this with BT 3900 ?
PS: Somebody asked what kind of BMW: The car is an X5 build in 9/04, with the Bluetooth interface and without navigation.
Hi,
I've trawled the forum and I've followed all the TomTom setup procedures. The Problem is they seem to be for people who can't get TomTom working at all. I can get it working, just awkwardly.
Once I pair with my GPS receiver and go into TomTom i can get a connection. However when i quit TomTom and turn off the GPS it seems to forget. Next time I turn it on I don't get a connection.
The way I understand TomTom is that it seems to wait for the GPS receiver to contact the phone. This seems odd as I would have thought the phone would be the one to initiate contact.
Anyway my GPS receiver just seems to forget what phone it was connected to. TomTom obviously isn't forgetting the port, windows obviously isn't forgetting the pairing. But Every time I use it I have to re-pair the receiver (thus reminding the receiver of the phone it's supposed to be bonded to). It's beginning to drive me a bit insane.
Anyone else have this issue? Perhaps it's to do with my incoming and outcoming ports? Hopefully someone has already solved this? Not seen any references to it anywhere.
Lewis
Hello,
Which version of Tomtom are you using ? The last one (5.21) ? If not, try to upgrade and try again.
Yep 5.2 latest release.
I was hoping upgrade would fix it but alas no.
Lewis
BigDamHero said:
Yep 5.2 latest release.
I was hoping upgrade would fix it but alas no.
Lewis
Click to expand...
Click to collapse
Don't mean to be picky, but 5.2 or 5.21?
I've held off installing TTN on my Wizard, as it works fine on my iPAQ 4700, I have a cradle for that, and according to ttcode, my current device is actually my old 3970, not the current iPAQ... Last week, I had a couple of hour drive to do, so I thought I'd give it a whirl. After an email exchange with TomTom support (who were more helpful than I'd originally given them credit for), I had a new activation code for the Wizard. Here's what I did, from a fairly recent hard reset with no previous TTN install whatsoever. Skip the mail if it doesn't look helpful, but I'll detail my steps in case it helps anyone else...
Although I believe the PC install is mended in 5.21 I copied the map and voice cab files from the CD to my SD card and installed them from there. The GPS drivers and main app I installed from the download I got from the TomTom support site by running the setup util on my PC. Once everything was installed, I moved the maps which seemed to finish up in a sub-directory on the card to the root of the card.
I paired the GPS (my old Emtac BT one) and selected serial port profile. I tried all the offered serial ports in the "Other BT GPS" list in TTN but none worked. Then I went to 'COM Ports' in Comm Manager/Bluetooth Settings and selected "New Outgoing Port". I picked the GPS from the list of paired SPP devices, and it created a new BT COM port on COM6. That definately hadn't been in TTN's list of BT com ports before, but is now there in the list with about half a dozen others. I selected that in the "Other BT GPS" list of BT ports, and TTN connects to the GPS each time.
As I said, I'd recently hard reset the device to try and prove a problem with my BT car-kit soit's quite possible the clean install was the secret, but try creating a new outgoing COM port against the GPS and see if TT remembers that...
Dox
BigDamHero said:
Hi,
I've trawled the forum and I've followed all the TomTom setup procedures.
Click to expand...
Click to collapse
Which?
There are 2 general ways to set it up, 1 works 100% (i use it so know it does ) 1 i dont use and have never tried so may well work in the reverse direction and be causing you errors.
The way i set up tomtom; pair the BT GPS. Open an OUTGOING port to the BT GPS, set my GPS as OTHER (wired/cable) NEMA device (NOT bluetooth) in TTN5. now my tomtom connects to the bluetooth, not the otherway round. This method has thrown up no errors for me at all.
If you have followed the reg edit/hack to show the GPS page in connections then i dont know how the settings differ and the possible results this could have on connection issues.
Let us know which way you are going
I have the exact problem as BigDamHero. Each time I wanna use TTN, I need to delete the previously paired BT GPS and then pair it again, otherwise the TTN will just say No GPS Device. I use TTN v5.21 and Wizard with Windows Mobile 5. I tried my BT GPS device on my brother's PDA which runs on Windows Mobile 3, and it connects like a gem every time. I am also looking if anyone has solved this issue, cos it is tedious re-pairing every time.
Had the same problem until 5 mins ago! Found an explanation in another thread, but only in Dutch..
Here's how to do it:
Turn on GPS
Activate bluetooth on device, go to BT parameters, delete previous pairing like you're used to
Create new pairing, choose GPS, enter passkey, check Serial port in services, go to COM ports and add outgoing port (e.g. COM6) like you're still used to :roll:
Add an incoming port too (e.g. COM7) <-- Here's the trick!
Set your GPS apps to use COM6 (the outgoing one)... and here you are! This time it will work, you can turn off GPS and device bluetooth, turn on again and it will connect by itself.
If you want a bit more you can activate GPS panel, set program port to COM8 (then you will have to use this in your apps) and COM6 as hardware port.
Everything works fine now!
hey man, wot a coincidence....i also just read that post which had the dutch explanation.....BUT however, it's not working for me.
toneslee said:
hey man, wot a coincidence....i also just read that post which had the dutch explanation.....BUT however, it's not working for me.
Click to expand...
Click to collapse
I did everything in the list except for creating the incoming port and it still works everytime (I know that's no consellation to you). I wonder if something else you've installed, or the way you installed the app is causing the problem? Is it worth a hard reset and trying the entire install on a clean wizard?
Dox
A friend didn't need the incoming port either. I believe it has something to do with the GPS, as he has a different brand than me.
With mine, before adding the incoming port if I started an app without erasing/redoing the pairing before I would get a notification saying "Navman GPS wants to connect" and asking me to pair. It would keep coming every 10 seconds whatever I did.
BigDamHero, what brand / model of GPS is it?
Maybe we can see if anybody here, or over on pocketgpsworld has been able to make the same combination work and if so, what they had to do to get it to fly...
Dox.
well, tomtom was the very first thing I installed when I got my new vario. it was only after I got tomtom fully working (but still need to re-pair everytime), then I installed a couple of simple Card games.
toneslee said:
well, tomtom was the very first thing I installed when I got my new vario. it was only after I got tomtom fully working (but still need to re-pair everytime), then I installed a couple of simple Card games.
Click to expand...
Click to collapse
A quick glance at pocketgps suggests others are having similar issues. There's a thread here that suggests leaving it a while, and I seem to remember other GPS issue threads saying power up the GPS and let it get a fix before starting TTN. A more detailed probe round the forum will probably show more of the same.
Dox
I've just flashed my Qtek 9100 to a new ROM, (the O2 one), and since then I've been getting this same problem. With my previous ROM everything worked fine. I was able to turn of either my PDA or GPS, and they would always auto-reconnect in a few seconds. Looks to me like something broke during one of the ROM changes. Which ROM versions does everyone with/without this problem have?
By the way, I have a BT77 GPS.
Hey sorry for the total lack of reply. Been snowed under with exams.
Ok I tried most of what you guys said but didn`t work. BT ports aren't available to select as hardware ports.
However I have managed to solve it. The key was to pair the GPS, and create an UNENCRYPTED OUTGOING port. That's all. Previously I had encrypted ports outgoing and incoming. My GPS applet in control pannel is set to none so it,s nothing to do with that.
I don't know what my GPS is. Its unbranded. One of the cheap common ones.
Hope this helps some people with the same problem.
Lewis
I searched and didn't find any previous postings regarding an issue with Parrot and Audi Hands Free (Bluetooth) car kits and the TyTn.
This issue is only with the TyTn and the Wizard devices work fine.
It seems to pair fine with the car kits but 5 minutes into usage...the TyTn turns the bluetooth off on the device.
Then about 1 min later, turns Bluetooth on again. The cycle then begins Off and then On ....
Here's a link on the Parrot forum.
http://www.parrot.biz/forums/english/viewtopic.php?id=2667
I've got the same problem with my Seat Leon (new model) bluetooth carkit !!!
I think it's the same module as in the Audi (all VAG related cars).
It's very irritating !
I hope they will fix it soon....
http://forum.xda-developers.com/viewtopic.php?t=58789&highlight=
:wink:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Pyranwolf said:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Click to expand...
Click to collapse
I'm going to try this !
I hope that it works.
Thanks anyway.
What kind of Leon do you have ?
I've got an A6 with BT kit and am having this problem. I cannot make/receive a call whilst running my BT GPS device & TomTom, although from reading this the issue may be the Audi kit anyhow.
Are there any fixes available - be it HTC or Audi? Or are there any work-arounds, such as add-on software for the TyTN??
Please help - it is driving me mad. Spoiling what is otherwise a great piece of kit.
I have been having this exact problem with my Audi A4 with Audi Bluetooth.
I did wonder if it was in some way connected with the phone going into sleepy mode as it is being powered by the phone battery.
Also, the bluetooth stops responding after 5-10 minutes, but if I am continously using the phone, it seems to be ok.
Therefore, I think I need to buy an in car charger, and see what happens...
Has anybody else tried this that can confirm it works?
Markee
Just a quick note to Paul_o
My Audi A4 / SPV M3100 / Tom Tom / Bluetooth GPS work fine together.
If I am in Tom Tom, and get an incoming call, the little call window pops up over Tom Tom, Tom Tom carries on and the phone audio is routed through the speakers - the only irritating thing is that the Tom Tom lady keeps interrupting... :wink:
Mark
Hi,
I'm using Vario 2 with Audi Bluetooth and also having the BT ON - BT OFF issues.
These are my findings.
- Without JETWARE software:
- BT goes ON and OFF in the car regardless of the VARIO 2 being on or stand-by, or the phone being battery powered or connected to the car.
- Once a conversation is started the BT connection seems to be remain ON.
- With JETWARE software
- If I leave the screen always on the BT connection stays always ON. Only backlight automatic switch-off is selected
- I have tried several screen toggle programs (which claim that they only power down the screen) but the BT goes OFF in the car after a few minutes.
I'm happy to test any other proposal.
Cheers,
C
What version of JetWare are you running, they have a beta which has settings for the Audi kit, this may help, there is also a registry setting that is meant to change the power settings when bt is connected. An extract from an email conversation with Jetware...
We have also addressed the power issue, but this fix requires a registry change. Please create a DWORD registry value in HKLM\Software\JETware\AGExt named InSessionPower with a value of 0 (valid values are 0-4, with lower values indicating greater power availability). This will tell the OS that the Bluetooth device should stay at full power while it is in a Hands-free session.
Not sure if this will help, my Hermes is ariving on Monday, I'm was hoping that all the problems i've had with my magicain and the audi kit would go away with the Hermes, but maybe not.
Give the key a go and let me know
Hi dh,
thanks for your reply.
I haven't installed the Beta version yet. However I have changed the registry setting and will test first thing tomorrow. If this doesn't fix the problem I will try the Beta version with the Audi setting.
I'll keep you posted.
Cheers,
Carles
Hi dh,
I have tested the two proposals (Change in the registry and the Beta version + Audi settings) without much luck. The BT connection with the car keeps going ON and OFF when the phone is running on battery.
Have you got your Hermes? any luck?
Thanks,
Carles
Got my Hermes (Orange M3100) a couple of days ago. I've installed the JetWare extention, and without the InSessionPower set the connection is dropped. So far with the setting applied it has stayed connected. I have had other problems like not being able to make calls etc, which is a bit of a issue. I need to do some more testing, as i've been messing with the phone a bit.
I'll update here in a couple of days
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Hi dh,
You will see from my previous postings I have had the same problems too.
It should be noted, though, that the Vario (wizard) worked flawlessly with the Audi A4 Bluetooth without Jetware software.
Has anybody been able to prove there is no problems if the phone (SPVM3100) is powered whilst in the car?
Cheers
Mark
I have a factory fitted hands free system in my Vauxhall. Every other phone you can think of works with it...EXCEPT my XDA mini. It seems to pair up, but there is no signal showing from the carkit. It might work for a minute and then it drops out. Is it the XDA or Vauxhall that's at fault? It seems that nobody knows the answer and I paid serious money for this bit of car kit. I like the phone, it really is annoying. I have tried another XDA mini as well and that doesn't work either. Does anybody else have a Vauxhall with the same built-in system and not connecting?
Markee
I've had the phone plugged in without the registry entry and it seemed to be ok. If I can get to a stage of a working solution i'll test again without the registry entry and with external power.
dh said:
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Click to expand...
Click to collapse
I'm guessing that since they went from BT1.1 to BT2.0 they had to make a new stack.
My Wizard worked PERFECTLY on my Parrot, my TyTN is almost useless on it.
you make a very good point ScottC, that'll be what it is.
Just driven home and could not make a single call with Jetware installed. Removed it and i could at least make a call, but i didn't get any status info or phone book. I didn't get a chance to leave it connected without Jetware for longer enough to see if it disconnected without external power, i imagine it will. I will test some more later/tomorrow. I'll also send an email to Jetware to see what there thoughts are regarding bt v2.0 and their product
Hello,
I have an Audi A3 with the factory fitted Phone kit but without the Audi Craddle so I'm using the Bluetooth connection.
I have tried the Vario (Wizard/QTEK 9100) and Vario 2 (Hermes/TyTN) and had similar problems with the two of them. Once the connection is stablished I can make and receive calls without problems. The issue is that the BT connection goes ON and OFF without an apparent reason.
The only thing I have seen is that when the Vario is kept on (only the backlight is off) the BT connection normally stays ON, regardless of the phone being powered or not.
I have tried Jetware, the Beta version, the registry entry, programs to switch off the screen...but haven't seen any real difference.
I have bought a bluetooth USB stick and will do some test at home to see if the problem is with the car or the phone.
I called T-mobile and they said it was a faulty phone, but I don't think so.
Keep the postings, we might end up finding a solution
Cheers
C
Try upgrade the BT software. I had the same problem after that i upgraded de Parrot software. Now i have the version 4.16
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Yep, got exactly the same on my BMW 630....
Can t find any tweak but....
I am a heavy email user (thru BlackBerry connect) and I noticed that
the higher the number of messages stored, the higher disconnections appears.
At the same time, the TyTn is slower and slower....so my idea that this is related to some timeouts somewhere....
For your complete info, the MS bluetooth stack in my previuos S100 have able to.....immobilize my 630 !!!!!!!!! yes, incredible...
The MS stack messed up with the BMW bt ...and this later would stay ON for ever...even after switching car s power off.
This was sucking the car s battery untill the car would start !...
BMW could not reset the BT module unless disconnecting battery....but...then the active steering had to be re adjusted with the proper BMW computer...
This is a real story.
johnmclean said:
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Click to expand...
Click to collapse
I have the same problem with a CK3100 kit, don't have a solution, but would like one, didn't have this problem with a Jasjar nor Wizard
TyTN bluetooth | random disconnect when using car handsfree - more details
Thanks for the replies so far.
Although the following thread did not help me with my problem, it might help one of you. If you're having problems mostly related to issuing voice commands using M$ VoiceCommander, I think there *might* be a solution in that other thread for you.
Just to reiterate my problem; my TyTN keeps randomly connecting and disconnecting from my car's built-in hands free bluetooth device.
There was a time when if i managed to made a call after first starting the car - before the first random disconnect - the phone would remain connected until the next time I started the car. That no longer appears to be the case.
-jm
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Has anyone tried a ROM with aku 3.3?
jasonrhcastle said:
Has anyone tried a ROM with aku 3.3?
Click to expand...
Click to collapse
Yes.
And on my CK3100 I now no longer get disconnects. I did have to uninstall jetware as it wasn't reliable. My TyTN now connects perfectly and no longer drops.
One thing I did find is that the TyTN hates it when more than one handsfree device is in its trusted list. Make sure that the ck3100 is the only handsfree device paired.
http://forum.xda-developers.com/showthread.php?t=247520&highlight=bluetooth+keeps+disconnecting
ajax007 said:
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Click to expand...
Click to collapse
I've tried changing the automatic switch off setting and it made no difference on my SPV M3100 (with Parrot CK3100) - I reckon that the external power is what fixed your problem (this has worked for others too).
Sadly it's not a convenient fix as I like to leave my phone in my pocket when I'm in and out of the car. Orange say there is no 'issue' so there's no sign of a ROM update but HTC know of the problem but I have to wait for Orange to release their ROM update. I can't use the HTC update. If only us Orange users could tell them enough times they might listen now that some AKU 3.3s are being released. Orange technical department won't speak to end users like me - they have actually refused to discuss it with me and just pass messages back and forth from customer relations. Any other ideas?
A solution - thanks to Parrot
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
587dan said:
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
Click to expand...
Click to collapse
If you use the Jetware BT software you can do the same thing e.g. beam the whole contact list in one go and then set the Parrot to not sync by choosing the Ericsson No Sync profile. This is how I have mine set up, also with the Jetware software it sends over the Service Provider, Battery and Signal strength settings to the Parrot, something which the native stack doesnt do.
Solution for this
Hey all, i have purchased a parrot 3100, the software in it was 1.6, i had the same problems but it's greatly and successfully solved using the new jetware 1.3 . i don't know if i can post some linx here, but here you go, if this is illegal for this site please remove them
http://rapidshare.com/files/30296941/JetWare_1.3.rar
http://www.megaupload.com/?d=PL5UX5KC
Hi @ all,
just got my HD2 with german ROM and one of the first things I tried out was to get a connection to my car (Audi A6) through the remote sim access profile (SAP, rSAP) - but it didn't work...
Does someone use the HD2 in his car using the sim access profile, as available in Audi or VW cars?
I have
- Audi A6 Avant (model 03/2008)
- using the "Audi rSAP Adaptor" in the car cradle, located in the arm rest
- everything in the HD2 is activated for Sim Access
Result:
HD2 and car are connecting, I have to put the 16 digit security code in my phone, but after that the SAP mode does not start, and so I have no access to my phonebook. It seems that I only have a "normal" bluetooth handsfree connection, because the HD2 still shows that he is booked into the mobile network - and when rSAP is active, the phone itself disconnects from the network and "falls asleep".
I restarted my HD2 several times, also the rSAP-Adapter by turning ignition of the car off and on until the adaptor switches off, deleting the connections, creating new connections, but nothing helps...
Any comments or experiences from other users are highliy appreciated
Finally, I have to remark that my HTC Snap, which I just upgraded to WM 6.5, works very good im my car with the rSAP - no problems at all, I get all my contacts in the MMI.
Thanks in advance,
Jolig
Just got my HD2 and am having the same problem.
I'm trying to connect with a 2009MY Skoda Superb with the rSAP bluetooth kit.
This works fine with my E71 and my HTC Touch Cruise.
I've been told that there used to be an issue with OBEX authentication on previous versions of Windows Mobile. Apparently, it was important to disable this authentication. However, I can't see the checkbox in the version of WM that the HD2 is running.
Does anyone know what registry entry this checkbox might have been changing?
Thanks,
Bagpuss.
Thanks Bagpuss,
who gave you this information?
I hope someone can solve this problem....but I fear we have to wait until we have more HD2 - owners
-----------------------------------------------------
EDIT:
I just have read something about the "Schaps Advanced Configuration Tool" where someone with similar problems activated OBEX (but it was an older Win Mobile device, and some months ago) - perhaps this could help?
But I just installed version 3.3 of this tool, but it doesn't work on my HD2...
Hi Jolig,
Check out this thread:
http://briskoda.net/superb-ii/howto...us-rns510-using-non-compatible-mobile/131709/
on Briskoda.net.
One of the guys there had lots of problems getting his WM phone to work, and posted the fruits of his labours.
From what I can tell, we can't use the CAB file he mentions, as rSAP is built into the OS version that the HD2 uses.
I've actually logged this issue with HTC, and am awaiting their response. My company is considering the HD2 as our next standard handset, and we won't go for it unless the rSAP functionality works with all VW/Audi group cars.
I'll let you know if they get back to me.
Bagpuss.
Thx Bagpuss,
and yes, in my opinion it's a mess that the rSAP is apparently VERY unimportant for most people or manufacturers...otherwise we wouldn't have this trouble....
I will come back too if I should find some news.
Had the same problem, tried lots of stuff but none of my WM devices is able to work with the rSap protocol. Gave up on it and then my Skoda Columbus system was stolen.
Replaced it with a JVC 7000 with detachable front. Disabled the rSap carkit and am now using the JVC BT carkit wich is working great. The problem is in the MS BT stack. It is not supporting the rSap the way it should. Only phones that work flawlessly are Nokia's I'm afraid...
The lack of rSAP support is what made me ignore the iPhone this time around.
I was hoping that the HD2 would be a viable alternative, but sadly, it doesn't look like this is going to be the case.
As I bought it over the phone, then I've got 7 days in which to return it. If I can't get it to work, then I guess I'll be getting an N97 or N97 Mini (which will definitely work). :-(
Bagpuss.
@ Bagpuss,
otherwise, as I wrote, I can recommend trying the small HTC Snap (or also called Maple?).
Ok, this one has no touch screen and also a very small screen - but I can confirm he works with rSAP and is not too expensive. I will keep this one, although I now have the HD2
As to Bagpuss' information concerning the OBEX, I tried the following:
- installed the newest .NET framework version
(that was necessary to get Advanced Config Tool v 3.3 running)
- install Schap's Advanced Config Tool
- in the menu "Bluetooth", I enabled OBEX
- after that the config tool does a soft reset
...still no success....no SAP and no phone book
I also wrote an email to HTC - it's really annoying, having SAP in the phone etc. and nothing works.
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Hi Binks821,
Binks821 said:
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Click to expand...
Click to collapse
Can you confirm if your Golf has the premium bluetooth preparation?
There are two different versions of factory bluetooth kit for the RNS510, one which simply acts as a handsfree device, and the other (premium) which is a complete GSM phone.
It's the premium kit which uses rSAP, and which seems to be incompatible with the HD2.
You can tell if your Golf is using rSAP by checking to see if the signal strength meter on the HD2 shows any bars when connected to the car. If it does, then it's not using rSAP. If you see the signal meter with a little x in the corner, then it is using rSAP.
If you do have rSAP working, then I'd really like to know which firmware version your RNS510 is running, and also which firmware version you have in your HD2.
Thanks,
Bagpuss.
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Hi Binks281,
Thanks for the confirmation.
I've now done some further testing in my car, and managed to have some success.
This is what I did.
In the car:
1) Remove all device pairings from the bluetooth system in the car.
On the HD2:
1) Perform a hard reset.
2) Turn on bluetooth. Make HD2 permanently discoverable.
3) Make sure rSAP is enabled (it is by default).
4) Turn off SIM pin (turns out this isn't necessary, but I wanted to make things simple).
So, at this point, I have the car system with no paired phones, and the HD2 with factory settings and no personal data (contacts etc.). I also made sure there were no contacts on the SIM card.
Back in the car, I perform a device search, and it detects the HD2.
I select the HD2, and the car displays the pairing password (1111 2222 3333 4444).
On the HD2, I enter the password.
I then get a prompt saying that Skoda_rSAP is trying to connect to the remote sim access service. I say allow, and also tick the box to allow all future connections.
After about 10 seconds, the maxidot in the car says 'New SIM card recognised', and prompts me to create a new user profile. I called it 'HTC_HD2'.
After about another 15-20 seconds, the car should extract the SIM details from the phone and the phone name, network and signal bars should appear in the car display.
You can now make calls, but there is no phonebook.
Given what others have said about the phonebook access, I'm pretty sure that this is what was stopping the pairing from working the first time I tried it. I've heard various stories, some which say that the phonebook access only works with SIM card contacts, some which say it only works with OBEX authentication switched off and so on.
If you look at the paired devices screen in the phone, then you can see connections coming into phone. First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
I'm still trying to work out what is causing the problem with the phone, but I have done the following things:
1) Told the car to only sync phone memory contacts. By default, it's set to sync both SIM and phone memory. You can configure this on the car by going to Settings -> Phonebook -> Select Memory, and choosing 'Mobile Phone'.
2) Created four contacts in phone memory, one with only 1 mobile number, one with 2 numbers (mobile and home) and another two with three numbers (mobile, home and work). I've then gone into Settings -> Phonebook -> Upload and sync these across to the car.
So far, this has worked fine and disconnecting and reconnecting to the car works without a hitch.
I'm now going to try syncing a small subset of my contacts with ActiveSync to see if this also works.
If it does, then I'll gradually increase the number until it either works, or fails.
I'll report my progress here.
Bagpuss.
Thanks Bagpuss,
sounds interesting!
I think tomorrow I will try this also:
- remove all paired phones in the car-system
- delete all contacts
- disable SIM Pin
Temporarily I am not sure if I will do a hart reset in the first step because I've already installed so much... When the work fails, I thing I must do it
I will report what happened.
---------------------------
EDIT:
Ah, come on...TV this evening nothing interesting, wife in bed...I tried it, including hardreset
No success.
Bagpuss, what I detected:
First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
Click to expand...
Click to collapse
This connection to the Sim Access Profile I see also, but only for one second, then it dissappears and then the connection "Handsfree" comes up - and this one remains....
I do not know else what to do.
I now reconnected my beloved HTC Snap/Maple, and now I will start installing my apps on the HD2....
Hi Jolig,
Sorry to hear that it didn't work.
By the sounds of it, the Audi system is somewhat different to the VW/Skoda one. From what I can tell, your system also appears to support using phones in handsfree mode (I'm guessing that the iPhone works in your car).
In the VW/Skoda cars, you can either have a car kit that acts as a handsfree device or one that uses rSAP, but not both.
It could just be that the HD2 isn't responding to the rSAP request quickly enough to satisfy the MMI. In that event, it falls back to using handsfree mode.
When it shows 'handsfree' on the HD2, can you use the MMI to make calls?
This whole area seems to be a bit flaky on the HD2, as I still can't work out why mine didn't work when I first tried.
Bagpuss.
Binks821 said:
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Click to expand...
Click to collapse
Hello Binks821,
I believe that I have the same hardware situation like you but I can't get my HD2 started on my VW Passat with the Premium FSE. The problem is, that I can go through the whole "finding and connecting process" and can save the PIN but then the Connection gets lost between the HD2 and the PFSE. If seems that the PFSE can't connect to the Network (E-Plus) but why the BT-Connect gets lost in this case.
Maybe you can help me to get it work. Thanks a lot!
Negropo
Hello everybody,
maybe I found a solution that work for every sap-handsfree-set. I tried the hint was given on the german car forum "motor-talk" for the connection problem between a vw pfse and the htc touch diamond with wm 6.1 or 6.5.
The trick is that you have to disconnect the HD2 from the pfse by manual when the car first want's to connect automatically. You have to go to the BT-Setup to the tab where are the connected devices listed. If you click on the "+" right of the name of the device you should be seen the tab "Remote Sim Access" or in german "Sim-Zugriff". When the car connect's to the HD2you have to stop this by pressing disconnect in the right below corner of the HD2 screen. Then the connection is terminated. Now you have to start the connection manual over the menu in your car. In a VW you have to press only "connect" in the MFA. And then the HD2 should connect without problems. I don't know why it works but it does. Maybe there is someone here who can explain it and find another "automatic" solution for this problem.
Regards Norman
Well, I don't have a VW but an Audi with an rSAP-Adaptor in the middle arm rest. I fear this also doesn't work for me.
The problem is that this Tab "Sim Access" only appears for just one second, so I have no chance to make anything whithin this single second....and after disppearing of the tab "sim access" another tab "handsfree" appears - and stays. So it seems my Audi only recognizes a handsfree profile. I don't know why,
Temporarily I am happy that I still have my HTC Snap, which is working very fine with rSAP
@ Negropo, can you tell me in which thread at motor-talk you found that?
Thanks,
Jolig
Hi guys,
rSAP works fine with my Audi A4 BTA. I made the HD2 discoverable for any device and I activated the SIM access in the HD2 BT settings. Then I start searching for Bt device on my Audi BT and initiated the connection with the HD2.After inserting the 16 character pin everything works fine.
By the way ... the connections seems to be very stable. With the Touch Diamond I had from time to time connection interrupts where it was necessary to reset/restart the Touch Diamond again.
Best regards,
Matthias
@ Matthias,
"BTA" means that you have the built-in phone with rSAP, right? Is it a brandnew A4?