When I install Pocket Bluetooth Tools 1.1.0.0, and set the timeout option off (ie, leave BT on all the time), my iMATE (XDA II) never turns off. If I use the timer feature (auto off after 60 seconds), it turns off correctly.
Anyone experience this or know how to work around it? 1.0.1.2 works fine, except that with my BT800 headset, it doesn't properly answer the calls on the headset, so I must use 1.1.0.0
Help!
Thanks.
-Kevin.
Hi,
I use a BlueTrek earpiece (bluetooth) to enable handfree calling with my Qtek9100. I Also use TomTom Navigator.
When TomTom starts it enables the BlueTooth connections (if not allready active). This is usefull since I use a BlueTooth GPS with TomTom.
However, if I exit the TomTom Navigator application it is also disabeling BlueTooth, resulting in loosing the connection with the earpiece.
Does anybody know if this can be changed?
Perhaps a registry key I can change to solve this small, but annoyng, problem.
Gert-Jan
Turn on bluetooth before you start TomTom, then when you quit it should stay on. Does on my xda IIi anyway
The same on my magician. TT5.1 returns BT in the state it was before starting TT. TT5.0 however always shuts down BT on close.
Regards, M
I tested this last week, but came to the sam conclusion.
No matter what the state of BT, TomTom always disables BT on exit.
Gert-Jan
Ditto with my XDA2i running TomTom5 with a Qstarz BT-Q880. Slightly annoying.
However, if I press one of the hard buttons (such as the Contact List button), when the new window is brought up TomTom is minimised. Then, I can Switch (from hfrmobile.com) to Close All - and while this disconnects the GPS device, I've doublechecked and it doesn't disconnect my bluetooth headset, nor does it turn off the Bluetooth itself.
So, that in itself is a quick-and-dirty workaround hack, but I've not come up with any other solution thus far. Currently scouring the registry and the configuration files (what few there are) for a fix - it may be that someone with infinitely more coding ability needs to hack the TomTom .exe to disable this switchoff, though that's no mean feat.
You will probably find that if you reconfigure your GPS reciever in the Tomtom preferances as an "other wired receiver" select an appropriate baud rate, then select a Bluetooth com port, it will still work with a bluetooth GPS receiver but will completely leave your Bluetooth alone.
This does also mean it wont start it automatically if it's not allready on.
That doesn't work - the only way my Qstarz will work is if I configure it as Other Wired NMEA GPS and then run it on Bluetooth COM6, setting the baud rate appropriately (the Qstarz will accept any rate from 4800 to 115500 anyway, so that's rather irrelevant). Even if it's set as other wired GPS, the bluetooth is still disabled upon TT exiting.
This is also the info advised by the TomTom website if you're having problems getting your GPS to run with the software, so I'm guessing it's the only way. I'll have another look round the TT web site when I'm not so pushed for time.
What Tomtom version are you guys using? After a little play with mine I can say that with GPS setup as a bluetooth device. If bluetooth is on when I start Tomtom it stays on after I exit.
I use version 5.2 for Pocket PC
Well, small update - after having TomTom pop up the Bluetooth Manager box every time it starts up, and asking me which device I'd like to use as default, I managed to select the Qstarz Serial Port Connection shortcut which I created (had to manually create the link after setting up the device pairing) - I checked the option to Use this connetion by default, and now TomTom leaves the Bluetooth turned on after it exits!
Smashing stuff, means I can now use my headset and TomTom simultaneously in the car.
This is with TomTom 5.000 (4890) with GPS driver v1.20 and using the Great Britain Plus Map (v571). Bosh!
I get something different on my QTEK S100. When the QTek starts receiving the GPS signal (via bluetooth), TomTom freezes the screen for about 2 seconds and then closes TomTom.
Any ideas about this problem?
Is it because I had "MagicButton" installed? I uninstalled it, did soft reset... but the problem is still there. I can I know if it is MAgicButton doing that?
Thanks
DoubleW
Hi,
When I switch on both devices they connect fine, and I'm able to make calls etc, but the stereo connection doesn't appear to be established. I then have to go to Comm manager>Settings>Bluetooth, tap and hold my bluetooth headphone in the list, then choose 'Set as Wireless Stereo' from the list that appears.
As soon as I do this, the stereo connection is achieved and indicated by the headphone icon appearing in the top bar.
Is anybody else having this issue with stereo bluetooth headphones?
Is there a solution to this?
Aleemz,
I've just bumped in to this post - I have solved this on mine by writing a mortscript to automate the manual steps above.
It works pretty well, switching on the BT, waiting for the headset to connect, and then switching off the BT when the headset disconnects.
Here's the script (with thanks to another poster who gave me the starting block for this):
#power up bluetooth
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueon")
#wait for something to connect, but only for 30 secs
SleepMessage( 30,"Connect Headset", "waiting for headset" , True ,RegRead("HKLM", "System\State\Hardware", "Handsfree") = 1 )
If (RegRead("HKLM", "System\State\Hardware", "Handsfree") = 0 )
#headset isn't connected, so switch off bt & give up
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueoff")
exit
endif
#if we get here, then bt is on & the headset (or something) is connected
#may want to add logic here to decide what to do based on what device has connected
#run up the settings page
Run "\Program Files\MortScript\bluetoothcpl.lnk"
#wait for the settings page to load
WaitForActive ( "Settings",20 )
If (WndActive("Settings"))
#Great - it opened
#set the device
#may well have to add some logic here later to detect which BT device has connected
#This works if the BLuPhones are the 1st in the list
MouseDown Settings,60,125
Sleep 1000
MouseUp Settings,60,125
Sleep 500
SendDown
SendDown
SendDown
SendCR
Close "Settings"
#now we're all set up
#Now just wait for it to disconnect
#loop watching for bt headset disconnect for 4 hours, checking every minute
timcount = 0
while (timcount < 60*4)
timcount = timcount + 1
If (RegRead("HKLM", "System\State\Hardware", "Handsfree") = 0 )
#headset has dis-connected, so switch off bt & exit the apps
Call CloseAppsAndExit
Exit
endif
sleep 60000
EndWhile
#timeout after 4 hours of waiting, and shutdown media player & bt anyway
#do this in case it's been left on accidentally
Endif
Message("Closing down bluetooth now","Bye")
Call CloseAppsAndExit
Sleep 2000
Exit
Sub CloseAppsAndExit
#Close all apps we ran & exit
#close BT
Run ("\program files\vijay555\vjvolubilis\vjvolubilis.exe","-blueoff")
#close all apps -
Call ("CloseApp","GSPlayer")
Call ("CloseApp","Windows Media")
#this is the name of AVRCP I think
Call ("CloseApp","TCPMP")
Call ("CloseApp","S2P")
#and this is my guess at S2P
EndSub
Sub CloseApp
if (WndExists(argv[1]))
close(argv[1])
Endif
EndSub
I have a problem with my car bt (Blue&Me Fiat by Microsoft)...The pda is capable to connect with the car bt without any problem but after some minutes the connection falls down...I think it depends by the pda bt that goes in stand-by mode.
It only reconnects if I manually make a search of the devices with the car bt but the connection falls down again after some minutes....It's very frustrating....!!!!!
Is there any possibility to keep the bt connection between the pda and the car kit in some manner?!? Maybe a setting that avoid the pda bt to go in stand-by mode when connected with a car kit....?!? Boh..Help me!
Thank you a lot, and compliments for this forum!
Hi
I got a prob. on my Omnia while I'm connected with my BT Handsfree in my car the Omnia turns always on even when I turn it off with the power button.
A lot of people got this prob. . The manif. of my BT Handsfree told me that 'cause of the permanent data transfer (battery status....).
Is there a possibility (in the reg) to avoid this ???
With my HTC Trinity I didn't got this prob. on the same Handsfree. (custom WM6)
greetings to all HTC users ( once I was one too)