:?: Can someone point me to the location of the download of the blue tooth tools file please ...ive looked for ages with no joy
Here it is.
http://bluetooth.i-networx.de/index_e.html
And heres the cab file, just copy to your phone and execute there.
Anyone tried BT Tools 1.1 on WM2005 ?
You don't need BT tool on WM2005. He has better BT manager and you can you it instead of BT tools.
Rico
I've tried it on Buzz's 1.6 version of wm5 (Himalaya) and before I upgraded my radio ROM from 1.14 BT Tools loaded and worked as per the old version (like a charm). While it may not be necessary owing to certain improvements in wm5 it still had features I liked (BT auto power off when idle for 60s).
Once I've upgraded to 1.17 it loads but nolonger appear on the today screen. Then when I bond with a new device I get the BT Tools profiles screen. I have then been able to use the Activesync profile to sync with Outlook 2002 on my PC via BT. I can't however access the two power/light profiles nor the BT auto shut off feature (I really liked that function for power saving) or at least not yet.
I'm going to try Radio ROM 1.08 and 1.18 as per suggestions in other forums (as I'm hanging when I now sync using the cradle) and will let you know if anything changes.
Regards - Mallow1
NB I'm using Version 1.1.0.0 of BT Tools not 1.0.1.2 (the one downloadable above). See the actual site for details of the differences:-
http://bluetooth.i-networx.de/index_e.html
Upgraded to Radio ROM 1.18, BT Tools now appears again in the Today Screen but is completely inert re autoshut off (the only feature I'm now interested in given the ROM enhancements). So I'm unloading it and will serach for another BT manager with the same auto BT on/off feature.
Hope that was of use.
Mallow1
PS didn't try 1.08
I'm gald that you got the BT Tools to work for you. When I upgraded to WM2003 se and tried to set up my Jabra BT200A back up, it was no go. I could hear the caller, but the headset mic was non working, only the mic on the device. So I tried the BT Tools, to no avail.
The proverbial cake icing was that BT Tools made the device speaker phone quick working as well. Un-install BT Tools, and I get the speakerphone back, but still woe is me, no practical functionality out my trusty Jabra.
Any thoughts?
BTH tools 1.0.1.2 run just fine under WM 5.0 ROM 1.60c.
Especially ActiveSync via BT with several other computers works like a charm.
BTH tools 1.1.0.0 do not function correctly. Both profiles do exactly the same, either auto-switch or not and ActiveSync over BT does not work properly.
Sascha
Thanks SaBo,
I'll give it a whirl as it would be nice to have the auto BT on/off back again.
Chelms,
I trust SaBo's comments work 4u too. If not the only thing I can suggest (not being a jabra200 user myself) is to surf the forums. I know a lot has been written about getting the jabra BT800 working properly with HTC kit (Jabra state that it isn't compatable but I think the BA forum have been chasing it as a bit of a Holy Grail). I can't recall if they definitievly got there but I think they did. You may find something on your headset too. You can also try Buzz's forums on a similar search since he has been the one to work WM5 magic (http://buzzdev.net/). Further afield you might try Howard's Forum (http://www.howardforums.com/)
Regards - Mallow1
For all those still using Pocket Bluetooth Tools in WM5 (not for its BT profiles as they aren't needed any more but for the functionality of BT auto on/off and the two power/ screen saver profiles via the Today screen) FYI I'm currently running TofClock WM5 1.71a (working like a charm) and BTHTools 1.1.0.0 (which is also working like a charm.... NB the cab version as oddly enough I couldn't get the PC exe version to work). Just ensure that after installation your registry has theses settings entered under:-
HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\Bluetooth Tools
then add new values of:
Type Name Data
REG_SZ DLL BTHToday.dll
REG_DWORD Enabled 1
REG_DWORD Flags 0
REG_DWORD Options 0
REG_DWORD Order 32
REG_DWORD Type 4
NB Order is just the position number in the Today screen list so just tweak it via WM's start\settings\personal\Today route or type a number which suites you directly when entering the values above.
Regards - Mallow 1
PS anyone know a similar program (not the BT profiles part just the auto BT on/ off amd with a taskbar icon... like an enhanced version of BTIcon.exe.... In fact BTIcone.exe with auto on/off would be perfect... of to try another search)
FYI BTTools 1.1.0.0 cab works under TofClock's "WM5 2.01a 64 WWE" but not under the clean WM5 ROM posted by Buzz (i.e 2.00a).
Related
Because of all the expected mssing around with my original T-Mobile 1.60.00 ROM combined with a Bluetooth GPS, I decided to upgrade. It all works now, just let me share my findings with you:
I wanted the 1.72WWE and 1.14 Radio ROM, no Beta, but also wanted to keep my Dutch T-Mobile custumisations.
I took the recently released QTek 1.72 ROM
Unpacked it
Threw the extende rom file away
Changed the 'country code' from qtek to tmobile (see link on xda-developers mainpage)
Backed up my device using Activesync backup
Started the upgrade
UhOh: 'USB 1.03' on screen and nothing happening
Restarted upgrade
Went smooth all along
Hard reset: YES!! 1.72.00WWE / 1.14.00 radio with all my beloved Dutch T-Mobile customisations (ext rom 1.60.38)
Performed restore. THIS probably wasnt the smartest idea, because right after that my device was quite unstable. '
So: Did a 'permanent save' backup
and a Hard reset again.
Rock steady since then!
To get Bluetooth & BT GPS working frightened me a bit: getting that to work should be proof of the pudding to justify my upgrade.
Fiddled around 2 hours (com ports, gps viewer software that accompanied the GPS and what have you got . . .), until I tried the simple stupid method:
Switch on Bluetooth
Bond the BPS
Start TomTom GPS
Select NMEA 0183v2 9600 and Bluetooth GPS
I am very happy!!
For those that are still lokking for a decent cheap BT GPS: Search on ebay for DCONNEX. They sell for around 80 euros + 28 euros shipping. The DCONNEX DC-230 is in fact a rebadged Holux GR-230. Works like a charm, and for the price of a wire solution!
Works!!!!!
even imat v1.72 works great with BT GPS with no added BT tools
gazzaman2k said:
even imat v1.72 works great with BT GPS with no added BT tools
Click to expand...
Click to collapse
Is the same ROM.
Eelco is right
As long as you look just at the os & radio roms both QTek 1.72 and IMate 1.72 are the same.
Difference is withing the extended rom.
because I liked to keep the Duthc T-Mobile customisations (well not all, but most of them) I re-used my old extended rom.
Hello,
Help with 1.72 ROM set up.
I'm very excited about how you have set up your device, but I'm not fully certain how to do the same.
I have looked for the ROM unpacker, but the only thing I see on this site is the ER-Edit.
I currently have the T-Mobile UK Beta 1.72 on my device, and I'm not real happy with it.
If you can and if it is not too much trouble, could you please provide me a little more specific directions on how you accomplished your set up. I'm in the USA, and I upgraded from 1.60.36, which I was not very happy with either. I liked 1.60 better.
My major concerns lie with the country id error, and using parts of different extended roms and radio stacks, but I'm willing to try.
Thank You, Ed
Well since you now have 1.72 on the device its really quite simple.
(You might as well consider upgrading to the non-beta 1.72 from imate or Qtek, i used Qtek)
Foor the external rom customisations:
Unpack an update (like the 1.60 you mentioned) using winrar
Using the directions on thsi site determine your current çountry id FOR THE EXTENDED ROM
using the directions on this site (xda2nbf) change the country id for the extende rom file (ms_.nbf)
remove the other .nbf (nb and radio) files
Upgrade your device
Cold reset
Yopur device should now be a bit in the right direction
Install the extende rom-unlocker found in this forum
unhide & unlock the extended rom
Now you can add/remove programs from the extended rom.
adding goes like:
1. place .cab file of program to be installed in extended rom
2. add CAB line in config.txt just before the current last line
removing goes like:
1. remove cab file of program you dont like
2. remove accompanying line in config.txt
Dont forget to lock you extended rom afterwards so the contents is kept during any reset.
hope this helps.
also : search the forum on the topics extended rom unlock
edsub,
Thank you very much. Your response is very helpful, and sends me in the right direction. The winrar was the missing peice that I did not have.
I'm familiar with the extended rom part, but I have not played around with the .nbf, nor the rom locking.
The UK beta 1.72 I have does not seem real stable to me. I'm thinking of going with the iMate or Qtek 1.72, as you suggest.
Thanks again I'll see what I can manage.
Ed
hey all, im on o2 in uk, my current settings are :-
Rom version :- 1.60.00WWE
Rom date :- 12/03/03
Radio version :- 1.10.00
Protocol version :- 1337.18
ExtRom version :- 1.60.50
i knw this mite sound abit basic...but what difference would it make in me updating to this 1.72 rom ?
is there any point ?
edsub said:
i used Qtek
Click to expand...
Click to collapse
Maybe off topic but where did you get the QTEK ROM from?
Can you share the URL.
Thanks,
Mark
Hi all,
I've recently bought a DC-230 GPS BT, but I cannot use with TomTom3
I have:
ROM VER 1.72.00WWE
Radio 1.14.00
Ext 1.72.104 (with some cabs added by me)
And a XDA 2 (rom is a Qtek 2020)
I've tried:
Hard reset - no BT Tools - Bond GPS - Success with GPS Viewer (that is in boundle with DC) on COM5 9600
Started tomtomGPS, no success (with or without START GPS with GPS Viewer).
I've tried
- NMEA 0183v2 9600 on COM5 and on Bluetooth
- NMEA 0183v2 Bluetooth on COM5 and on Bluetooth
- SiRF 9600 on COM5 and on Bluetooth
- SiRF Bluetooth on COM5 and on Bluetooth
I've removed bond with GPS.
So i've installed BT Tools 1.1. Bondend and added profile on COM7
GPS View didn't see the GPS
TomTom the same (i've tried the same drivers)
Any suggestion?
Thanks
Fabio
try changing to nmea 4800 on the same port that the gps view is showing, make sure gps view is closed when starting tomtom. Alsi instead of choosing from the upper drop down box in tomtom, look in the lower drop down, you may find your gps is announced/listed there.
cruisin-thru said:
try changing to nmea 4800 on the same port that the gps view is showing, make sure gps view is closed when starting tomtom. Alsi instead of choosing from the upper drop down box in tomtom, look in the lower drop down, you may find your gps is announced/listed there.
Click to expand...
Click to collapse
no success
I don't know why doesn't work
GPS View found my GPS... TomTom GPS no
Is the right version of TomTom GPS? (down right i see V2.09 305/393)
In the lower drop down box I see only com/irda/bt ports...
Thanks
You should have totmtomgps V3.02. It is available on their site.
Downloaded TomTom GPS 3.02...no success
But is correct that GPS Viewer when i push on Start GPS show
Date: 2002/11/10
Time 01:01:xx
Long:
E: 0'0'0.0''
Lat
N: 0'0'0.0''
Dop: 50.0
Aciring: no fix
Direction NE 0
Alt 0m
Speed 0km/h
PDop50.0
And i get a red point on the N on the map...
news...
With BT Tools installed i've tried GPSDash and MapSonic...
They connect to com7, but I get Satellites in use: 0 of 1 sats
Quality of Fix: no fix / n.a.
What's meaning?
Thanks again
I cannot use any sats..whats wrong ? is the gps broken ?
Aehm....uhm...
Er...is possible that it is low of battery? I put on charge and now I see 7 sats..
Bluetooth authomatic activation problem
I am sorry to jump in this discussion, but I had a BT problem, I couldn't connect to a GPS (Leadtek), and I did almost the same thing you are talking: I upgraded my QTEK2020 to 1.72.00WWE/1.14.00/1.72.602.
After the upgrade I installed the Pocket Bluetooth Tools and after some bondings/"unbonding", the COM7 profile appeared and everything worked fine from that moment on.
Now, there are 2 things I want to share:
- first, in order to have a diferent Bluetooth serial connection to the same or another port, I had to kill the the bond I created with the Leadtek GPS, then bonded again without activating the serial profile and then killed that bond again. Only after this series of actions, with a soft reset between all of them, I was able to bond with a diferent GPS bluetooth (I think it was from Globalsat), using the Com7 serial profile.
- second: my Qtek activates randomly the bluetooth by itself...
Does anyone know how to solve the authomatic random activation of the GT?
Try to activate in start/settings/system/bluetooth settings the extended port com 5. This helps with leadtek and emtac bluetooth antenna's for tomtom, and alturion.
Cheers
Why are you using Pocket Bluetools with rom 1.72??
NO NEED TO!!
Just use native MS BT Stack.
Bond the BT GPS, say yes when asked to assign COM port.
Let GPS software use COM5
Settings for TomTom3: NMEA Bluetooth GPS / COM5
Works flawlessly
I do appreciate all the great mind here working together to put in a wonderful WM2003SE ROM for the XDA II. I too have nightmares with the bluetooth implementation and the difficulties in doing soft reset.
I have managed to solved one of the above issue, Bluetooth Headset, I was using the 1.72 previously and have a workable Bluetooth bonding and response, hence have export the Bluetooth registry from the 1.72 and imported into the new WM2003SE, guess what it works perfectly without anymore problem.
I have attached the Registry file from my 1.72ROM for general sharing, anyway, I have one paired device, my trustworthy HBH660, you may delete it and add your own device.
I have tested this with the headset profile, it works without any hassle.
DISCLAIMER - I am not responsible for any mishap, please backup before trying.
Thanks for posting this setting bro...
The bluetooth registry entiries from 1.72 was able to fix not only the headset profile but also bluetooth file transfer from pc to ppc....
I checked out the default setting of SE2 upgrade
It had only four listed entries on services... while the one you posted has nine including the file transfer protocol from pc to ppc...
I wonder if the rest of the entries work...
By the way i have the asian edition rom by zeroextreme
It was a great fix...
one thing though, how can i turn this registry setting to self extract to the registry so that i can add it in the extended rom...
Thanks!
Going through the development forums I discovered this thread http://forum.xda-developers.com/showthread.php?t=353774 .Someone posted a link to download a better bluetooth manager , after downloading and started installing it, the installer said it was helmi universal stack.And after looking around I discovered helmi was testing this new stack he was porting to htc universal and had headset and a2dp profiles working.So after installing I rebooted and the icon showed at the bottom so to test i clicked start bluetooth and to my surprise IT WORKED !! on my x7500 runnin the official wm6 from htc.On helmis thread he noted that it might work for apache but I confirm it runs on athena.Anybody else have feed back?
!!!!! BACKUP AFTER FURTHER READING SOME FOLKS HAD PROBLEMS IN TERMS OF TOM TOM AND AUDIO MESSUPS AND LOCKING SO BACK UP FAIR WARNING!!! THIS FOR PLAYING WITH IF YOU BACKED UP OTHERWISE YOU CAN MESS UP UR PHONE!!!! I TAKE NO RESPONSIBILITY AS IM TAKING A RISK MYSELF WITH NO PROBLEMS THUS FAR ON MY PHONE.
you can download it from
http://rapidshare.com/files/78498277/Broadcom_Bluetooth_Manager.CAB
helmi universal broadcomm stack thread here,also tells how to restore msft stack
http://forum.xda-developers.com/showthread.php?t=291639
supported profiles is avrp,a2dp,obex,sap,handset.bt dun,pan,serial.
THIS IS NOT MADE BY ME I SIMPLY FOUND IT IN THE FORUMS.I KNOW THIS WORKS FOR MY DEVICE (X7500 Running Official WM6 From HTC) .ANY OTHER DEVICE OR CONFIGURATION I DONT KNOW CHECK RESPECTED FORUMS FOR POSSIBLE SOLUTION
SPECIAL THANKS TO HELMI FOR PORTING THIS WONDERFUL STACK SO CHECK OUT HIS THREAD ABOVE.
How have you got on with this? BT is really the last bit of the Athena that I am not 100% happy with.
It's seems to work.
Installation with no problem and the bluetooth start.
But i think there is probleme with serial port.
I want to pair a bluetooth barcode reader (Opticon OPL2724). The dongle's driver installs a serial port on the PDA X7500 wich is used by the barcode reader to transmit the data.
I can connect the barcode and i can see in bluetooth manager that the barcode reader is connected (ingoing connection). Just like with my asus P535 with a native widcomm stack.
But I can't receive any data from the barcode reader
Is there a problem with registry setting for serial port ? This stack is for Universal and maybe there is some fix for X7500 especially for the serial port profile.
Please M. Helmi, can you help me. I would love to have this stack working with serial port and my barcode reader !!!
Hmm - just tried this to see if it fixes the problem with my Style-i going out of range all the time and although it shows as connected and I get the headphones on my Athena nothing I do on the Style-i Gets sent to the Athena and music playing comes out on the Athena not the Style-i - so it's just like it isn't connected really!
Oops - went to uninstall it and my phone hung - rebooted and it didn't - after first splash screen it just went bright white. Had to reflash.
Oh well, it probably needed it anyway!
Is there an impact on the GPS? The earlier post mentions possible problems with TomTom
Mrsums said:
Is there an impact on the GPS? The earlier post mentions possible problems with TomTom
Click to expand...
Click to collapse
Yeah I found out later on the stack is configurd to the free ports on universal but on athena it conflicts with gps.Gps port is com 5 ,but the bluetooth stack uses com 5 as outgoing serial port.What i did in registry is simply change the gps comm port in registry to comm 9 then configure progs to use that for gps port and it works.Using builtin gps option doesnt work because gpd0 keeps using comm 5 and I believe thats coded in a dll somewhere.
In my original post I mention if you wanted to uninstall the stack to check out that helmi thread because it explained how to do so and it even had a activate ms stack cab there.I Did say backup before install.
Also found out that if you have stack running and reset it deletes connection settings, activesync settings and hides phone setting tabs ( I used schaps tools to fix that)
For now I dont use this stack anymore untill helmi or someone who has the knowledge to make a few simple fixes ( I GUESS MOSTLY REGISTRY) to get this working 100 percent on athena.
the file is expired, could someone who has it post it with a little bit more details about installation process
thansk
I would like to see this as well
I used the older Helmi stack on my Universal and it was much better it's the only one that works with the Chainpus/Random branded Bluetooth Gamepad as their MS Stack drivers does not work with their own product but generally seemed a better stack overall. I'm tempted to give this one a whirl and see if it behaves as the older one was a bit buggy when I tried it before and had to do the whole hard reset thing.
Hopefully this will be the topping on the cake now I have AP4 up and running
Has anyone had success beaming contacts or appointments to another XV6800 after the DCD 2.3.2 upgrade? I can not connect with my wife's XV6800 - her's has the stock ROM still.
IF IR is hosed - is there a way to do this with Bluetooth?
SOLUTION - The only change I made to the 3.0.0 ROM was to modify (thanks azclown) as follows:
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
Then I found out that Pocket Informant 8 was the rest of my issue. I can beam now and send contacts or appointments via bluetooth. The option to send via bluetooth is no longer displayed on the PI8 menues, but just select beam - then when the beaming dialog comes up it will first try to find a IR beaming partner - wait and it will start selecting bluetooth devices next - pick the one you want and voila!
j-squared said:
Has anyone had success beaming contacts or appointments to another XV6800 after the DCD 2.3.2 upgrade? I can not connect with my wife's XV6800 - her's has the stock ROM still.
IF IR is hosed - is there a way to do this with Bluetooth?
Click to expand...
Click to collapse
When stock, I was able to beam files from my laptop to my phone using the laptop's send-file-over-BT utility. I can no longer do this under DCD 2.3.2. Perhaps our issues are related. The radio itself works (BT headset functions fine), so it's something in the new software.
Guys, I think he has IR Beam disabled....
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
this should enable beaming and IR.... I'm not 100 percent on this so if someone else knows better please speak up.... All I know is that I can xfer files using Beam..... edit this using any standard reg editor....
No dice...
azclown said:
Guys, I think he has IR Beam disabled....
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
this should enable beaming and IR.... I'm not 100 percent on this so if someone else knows better please speak up.... All I know is that I can xfer files using Beam..... edit this using any standard reg editor....
Click to expand...
Click to collapse
I made this change, recooked the Rom in the kitchen and no dice. My souped up XV6800 can't connect with my wife's standard ROM XV6800 (no small amount of teasing going on over this!)
Any other ideas?
im dealing with this same thing. just wondering if anyone else had any more insight
Same issue in DCD 3.0.0
I'm using the kitchen almost stock from DCD, I switched to Verizon, anded the HTC X key and adobe reader, but that was it. The only other change I made was that listed in my previous post to enable beaming. That does not seem to do it. Is there, perhaps, some other item in the kitchen that DCD removed that further disables beaming?
i am just using the base image that dcd compiled the time before the kitchen came out. i think its 2.3.2. when i went into that registry setting, my enable was already set to 1. i hate to say this (never thought i would) but i really need my IR haha
Had this same problem but finally got it to work out last night. I'm using DCDs 3.0 rom. 1st make sure under HKLM\software\microsoft\obex IsEnabled is set to 1. Next make sure under comm manager settings ---> bluetooth ---> mode tab ---> turn on bluetooth and "make this device visible to other devices" are both checked. Also check and make sure under settings ---> connections tab --->beam ---> receive all incoming beams is checked. That should do it. I got it working fine last night on 2 different moguls.
liemydude said:
Had this same problem but finally got it to work out last night. I'm using DCDs 3.0 rom. 1st make sure under HKLM\software\microsoft\obex IsEnabled is set to 1. Next make sure under comm manager settings ---> bluetooth ---> mode tab ---> turn on bluetooth and "make this device visible to other devices" are both checked. Also check and make sure under settings ---> connections tab --->beam ---> receive all incoming beams is checked. That should do it. I got it working fine last night on 2 different moguls.
Click to expand...
Click to collapse
Using 3.0.0 also - I tried that change to the obex IsEnabled key - and still nothing.... did you include anything else in the 3.0.0 kitchen?
Guys you do not need to mess with the registry to enable OBEX. Just go to the comm manager and enable Beam and also go to the connection settings and enable the beam from there. Make sure you able visible in bluetooth also.
I did this and was able to send files using the OBEX through bluetooth.
Try it out.
edit. you will notice that once you do this that you check the settings in the registry that obex will go from 0 to 1 in the registry.
my bluetooth works perfect. what i need is the ability to IR. any insight on the IR problem specifically?
Mills00013 said:
my bluetooth works perfect. what i need is the ability to IR. any insight on the IR problem specifically?
Click to expand...
Click to collapse
IR uses OBEX i believe. And when you want to send something through OBEX it uses the same protocol for bluetooth and IR. (Beam Feature)
What exactly is wrong with your IR. Because I tested mine and it works when i sent a document to my old Moto Q.
[email protected]$ said:
IR uses OBEX i believe. And when you want to send something through OBEX it uses the same protocol for bluetooth and IR. (Beam Feature)
What exactly is wrong with your IR. Because I tested mine and it works when i sent a document to my old Moto Q.
Click to expand...
Click to collapse
Carlos - did you include the enterprise section or some other section from the kitchen - maybe that is helping you because I do have all of those settings as you described and still can not beam or set up for obex bluetooth transfer.
j-squared said:
Carlos - did you include the enterprise section or some other section from the kitchen - maybe that is helping you because I do have all of those settings as you described and still can not beam or set up for obex bluetooth transfer.
Click to expand...
Click to collapse
No I did not include the Enterprise Settings, but I will on my next ROM (other reasons)
So you made sure that you enabled beam on the Comm Manager and on the connections settings for "beam" turned on bluetooth and made your device discoverable?
From there where you able to pair with a bluetooth device? such as you enabled the required authentication tab on security and connected to another bluetooth device?
P.S. What exactly are you trying to OBEX to? Are you sure that the computer or phone has OBEX enabled or that the settings are set the same to yours?
From there when you try to beam a file or receive a file what errors do you get?
I dont get any. I just right click an object select beam and make sure that the other device is visible and i send it to the device.
I think I found the problem....
I have beaming and bluetooth working now. The settings didn't change from my previous post, but I wnet back to my old Ipaq 4350 and beamed and sent appointments to my xv6800. Then it occured to me - the Ipaq is running on Pocket Informant 7 not the new version 8 in my xv6800.
I tried sending files via bluetooth and IR beaming from Resco file explorer and it works fine - so I think my issues are with PI8. I'll head over to the web-is forums for that....
solved
See first post - I added solution there.
I've connected bluetooth GPS to 3125, seemed to be OK (it asked about pin and after that info about equipment beeing connected).
Unfortunatelly GPS software doesn't communicate with GPS equipment. It is searching for bluetooth GPS but doesn't find it. I tried to set connection (port, baud rate) manually but I don't know which COM port is assigned to bluetooth
Is there any way to check this on ?
P.S. I've installed WM6.1 standard by Erofich
try 6.1 pro
I found that bluetooth is using COM6.
The biggest problem was in finding properly working GPS software
hi bchrubas,
Which GPS software are you actually using on WM6.1 standard?
I tried WM6.1 pro for a while but found WM6.1 standard more handsome since I manly want to use my phone simply as a phone
Anyway I'm still missing a good GPS program for navigation which is not intended for touch screen devices.
For now I stucked with Sygic McGuider (http://www.sygic.com/)
It doesn't need touch screen and StarTrek (or At&T 3125) is on the list of compatibile devices. MCGuider runs on STK quite fairly, I didn't noticed any major errors, maybe if it was little faster? (I know that it is possible to overclock this phone but i'm not quite sure about it
Anyhow, I'm stiil searching for some simple GPS track loging software
I looked around a bit and on smartphone-freeware.com I found these two programs:
gpsVP
chtiGPS
both seem to be able to do the loging. And the first one might even be worth trying as a navigation software for me.
not bad, especially this gpsVP
if it really support Garmin format maps it could be very useful