Hi,
I have to use a special Bluetooth Tool for my Business. With this Tool I have to send and receive some Files, to make a malfunction detection on Electronic Devices. At my last PDAs, I paired my tool and my PDA at first, and then I create a Serial Connection. After that I have to assign a free incoming and outgoing Comm Port, to send and receive some Data files.
But now I have a Problem on my new XDA Orbit 2 (Polaris) PDA. `This is my first WM6 Device, and on this one, I cannot create an incoming Comm Port, because there is no possibility to create an incoming Comm Port. What can I do, to solve this Problem. Is it possible to add this Feature at the WM6 Bluetooth Stack?
Thank you for Helping!
Nobody with the same Problem?
Does nobody know to fix this Problem? Maybe we only need some File out of the Old WM5 OS, to create an incoming Come Port in the new WM6 OS?
Thank you...
How can any body offer any help without knowing this "special tool"
victoradjei said:
How can any body offer any help without knowing this "special tool"
Click to expand...
Click to collapse
Hi,
The Problem is not the "Bluetooth Stick" called tool. The Problem is, that it is not possible to create an incoming comm Port, on the newer WM6 Devices. But this incoming Comm Port is a necessary Condition, to receive Data from a disturbed machine, through this Bluetooth Stick, onto my PDA. This Data I need for a intelligent error evaluation.
I hope, someone can help...
Perazzi said:
Hi,
The Problem is not the "Bluetooth Stick" called tool. The Problem is, that it is not possible to create an incoming comm Port, on the newer WM6 Devices. But this incoming Comm Port is a necessary Condition, to receive Data from a disturbed machine, through this Bluetooth Stick, onto my PDA. This Data I need for a intelligent error evaluation.
I hope, someone can help...
Click to expand...
Click to collapse
It would be worthwhile to know the brandname of your hardware and specifications of it. There are so many products called "Bluetooth Stick".
---Alex--- said:
It would be worthwhile to know the brandname of your hardware and specifications of it. There are so many products called "Bluetooth Stick".
Click to expand...
Click to collapse
Hi,
The only specitfications about the Bluetooth Stick Tool I is, that it run only under "Master Mode", and not under "Slave Mode", because it` s more security for the Data. And the Master Mode would be work only with an"incomming Port". Sorr, but more Information I could not get from the Manufactor.
Thanky for helping...
Does nobody knows the Answer ?
I'd be intereseted if you ever come up with a solution. I'm trying to create an incoming com port so that I can use GPS2Blue with my car PC. No luck as of yet. I'll post if I find anything.
U cannot create incoming port on WM6 BT stack. But so far i didnt have any problems wits sending/recieving files, comunication with external BT GPS. Al u need 2 do is properly pair devices, properly configure external GPS settings & open outgoing port. Truth is i didnt test ext BT GPS with my Orbit2(o2 branded polaris), but i tryed it w/ Orbit & Universal (both WM6). I can try it today and i'll let U know
phsnake said:
U cannot create incoming port on WM6 BT stack. But so far i didnt have any problems wits sending/recieving files, comunication with external BT GPS. Al u need 2 do is properly pair devices, properly configure external GPS settings & open outgoing port. Truth is i didnt test ext BT GPS with my Orbit2(o2 branded polaris), but i tryed it w/ Orbit & Universal (both WM6). I can try it today and i'll let U know
Click to expand...
Click to collapse
I'm not trying to use external GPS. I'm trying to use a program called GPS2Blue to route the signal from my internal GPS to a car PC via bluetooth. I thought the WM6 BT stack does support SPP, but does not advertise it as a service, thus creating the difficulty in creating SPP connections. I could be wrong though...
u dont need to create incoming port - thats if U want to recieve some data from [another device] with TC data flows 2 TC(tc is recipient) in your case u need too create OUTGOING (TC is sender)
incoming port problem
well I cannot use my bluetooth handsfree for incoming calls on my T-Mobile Vario II.I can make outgoing calls. There is no option in WM6 for creating incoming part.
I have tried diffrent bluetooth sets but no joy.I had no problems with WM5.
Any help will greatly be appreciated.
regards
phsnake said:
u dont need to create incoming port - thats if U want to recieve some data from [another device] with TC data flows 2 TC(tc is recipient) in your case u need too create OUTGOING (TC is sender)
Click to expand...
Click to collapse
Wether a port is incoming or outgoing depends on which device initiates the connection, not which way data flows. For example, in your earlier example of an external BT GPS paired with a Pocket PC, the Pocket PC uses an outgoing connection to the GPS because it initiates the connection, not because data is flowing from the PPC to the GPS.
This is why I need to create an incoming port for my computer to see the PPC as an external BT GPS unit. The mapping program on the computer initiates the connection, then GPS coordinates are sent from the phone to the computer.
I've seen other programs that create their own virtual incoming port. Maybe that is what GPSGate does (I've heard it works for this use).
fairdeal said:
well I cannot use my bluetooth handsfree for incoming calls on my T-Mobile Vario II.I can make outgoing calls. There is no option in WM6 for creating incoming part.
I have tried diffrent bluetooth sets but no joy.I had no problems with WM5.
Any help will greatly be appreciated.
regards
Click to expand...
Click to collapse
incoming or outgoing port doesnt have anything to do w/ btooth headset. Either U have probs w/ Ur ROM or w/ headset.
bedoig: i know that but i didnt know how 2 explain it properly
incoming por
phsnake said:
incoming or outgoing port doesnt have anything to do w/ btooth headset. Either U have probs w/ Ur ROM or w/ headset.
bedoig: i know that but i didnt know how 2 explain it properly
Click to expand...
Click to collapse
well I have two Brand New MDA Vario 2 handsets with offical Tmobile windows mobile 6 rom. Mobile handset cannot be faulty.
As I said it was working fine when it was on WM5.
Bletooth headset work perfectly with other mobile phones including Vario 1 with WM5.
regards
I have Polaris(o2 orbit2) & MotoROKR S9(beckham ed) w/o any probs. but this thread is dedicated to polaris, maybe smth similar was already covered in vario II thread. Try to check there, or post it there.
I have an old Motorola H350 headset and it works fine both ways (incoming/outgoing calls)... so based on your descriptions the incoming port of my Polrais works...
For setting Incoming port you can just simply copy few registry entries from WM5 to WM6.
I have used it for my application smartWatchM. I dont know how it works, but it does.
http://forum.xda-developers.com/showthread.php?t=362218
moneytoo said:
For setting Incoming port you can just simply copy few registry entries from WM5 to WM6.
I have used it for my application smartWatchM. I dont know how it works, but it does.
http://forum.xda-developers.com/showthread.php?t=362218
Click to expand...
Click to collapse
Thank you. You are my Hero...
It`s exact that`s what I need. Now my Bluetooths Device is working fine, and the XDA Orbit2 (Polaris) is the best PDA for my Requirements.
And Greetings to "Schaggo" Member in St. Gallen... Thanks for your good Work.
Is there any chance someone could let me know what those registry settings are? I have the same problem with not being able to create an incoming com port but I don't have a wm5 device to reference at the moment.
Thanks in advance,
-TheXenocide
Related
Hi all,
I have just bought a tomtom bluetooth gps system, I can bond to the gps receiver ok, but it just wn't connect. There is deffinately a connection during the bonding process but that is it, it never connects again.
Any help would be greatly appreciated.
Thanks
Steve
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Puff The Magic Wagon! said:
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Click to expand...
Click to collapse
I think the problem is that the xdaII doesn't support a bluetooth serial port profile. I have tried virtually everything and had no luck.
Please keep me posted on how you get on, I really hope we can get this sorted or I will have a gps reciever paper weight.
Steve
Hmm
Due to the nature of yesterday, it wasn't until midnight (GMT) that I could get to have a play with my XDA II & EMTAC BTGPS (& I wasn't sober )
Installed TTN2 and tried to connect - not a sauasage
There "seems" to be something using COM6 and as such TTN2 can't use that as the path to the EMTAC - check box in the GPS options won't check. Turn off BT & you can check the box, but it won't connect as something else obviously can't use it either :? Dunno - I'm not a programmer but I'm going to have to check this out.
I'll speak to a contact @ EMTAC & see if they have been sucessful in bonding to an XDA II (HTC2?) & if so how. Otherwise I'll keep on playing with it & see what I can find out.
Anyone else got any tips or ideas what might be the way of resolving this?
Have you tried turning off the "receive incoming beams" under settings/connections, that may or may not free up the first com port.
I know someone with the same problem. O2 have told him that Tom Tom are working on a new version of software to fix this specific issue and it will be downloadable from the TT site. They couldn't say when.
xdaguru
Beam off did seem to allow me to connect to COM6 but not for my device Might be worth trying Steve because TT Wireless was one I could connect to.
IIRC from iPaq Bluetooth Manager, you had to bring up the device options once bonded and then select a serial connection. Pocket Loox as well. The BT Manager in the XDA II is very basic. So I do wonder if its a TT soluble solution or does it need an upgrade to the BT Manager?
If its a problem soluble by TT then I'm prehaps more hopeful
Sorry to go off topic but I wonder if this is the same PTMW that I know?
How you doin m8?
Hello Danny
Yes it is I
Can't be that many PTMW!'s about
All's well & I'll catch you on the other side one day
Yeah I guessed there could be only one PTMW
I take it you're lucky enough to have an XDA2 already? I always knew u were a gaget fan like myself. I have a month left on my XDA1 contract
Hopefully Tom Tom will have the problem ironed out by then as I have TTN2 aswell.
Pay us a vist on Scoobycity soon. Alots changed and we're alot bigger now
Any bluetooth GPS working with the XDA2 ??
Is there anyone who got the XDA2 working with a bluetooth GPS ? I am very eager to get one (both the XDA2 and a bluetooth GPS) but I would like to hear from some who got a combination working .
Thanks,
Marco
Its being looked into Marco
It may be that the BT Manager may not have various BT options enabled, so it may need a software update/patch from O2.
Spoke to O2 this morning.
They are "aware that not everything works with BT" and are working on a software update.
No timescale offered
I have an Emtac and was going to buy the XDAii to replace my Loox but without this bluetooth connectivity I will save my money. However interestingly it does say on the XDA website...
...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car
Click to expand...
Click to collapse
I'd say this is enough to get a refund if you want one. Page in question is located here...
http://www.my-xda.com/gps.html
TomTom and Bluetooth
The fault with the TomTom software and Bluetooth lies solely in TomTom's software. TomTom have recognised this and are aggresively working to fix the problem.
The TomTom GPS software doesn't know to read the details of the virtual com port. So give them some time to fix the problem....
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Hi
I too have just upgraded to the XDA II from the Ipaq 3970, and I also have an Emtac BTGPS.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
It would be very interesting to find out if any one has a TomTom BTGPS and can serial link it to the XDA II
Dom
TomTom and Bluetooth
mother said:
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Click to expand...
Click to collapse
The fact you're able to bond with the unit shows that bluetooth is working correctly.
The issue is that the tomtom software can't read com6: (which is where bt is hiding) or do anything with it, because of the way the software works.
This is because the Bluetooth manager on Xda II is from MICROSOFT, whereas on other devices it's manufacturer specific. As far as I know this is the first ever deployment of the MS Bluetooth stack directly.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
Click to expand...
Click to collapse
Then why do they say they support TomTom on their website? Seems like a few people at O2 dont really know what's going on?
I've not known that O2 has ever supported EMTAC BTGPS 'cos the XDA (1) didn't have bluetooth support :?
Surely it is the BT manager that is at fault? Not allowing the a serial connection from the manager to the Emtac?
TomTom is looking to read Com6 (when told to) but the info its getting is not sufficient or mapable.
I've run BTGPS with a TDK B/tooth card and it needs to be told (as do other managers) to make a serial connection to the BT device.
Test for someone (I'll try & do it too)
Find an alternate mapping software that *should* accept a BTGPS device & try to connect...
In reviewing the forums, I am unable to find a "straight" answer (at least one I can understand), about whether *ANY* BT headset with caller ID will fully work with the XDA II (or in my case, the IMATE PPC).
My configuration:
Imate PPC (XDA II)
ROM: 1.72.00WWE (3/15/04)
Radio: 1.14.00
Protocol: 1337.24
ExtROM: 1.72.800
I am running Pocket Bluetooth Tools V1012 (also tried 1100).
Can anyone tell me if the Sony-Ericsson HBH-660 or any other caller-ID enabled BT headset will properly display the caller number and/or name with the above hardware/software profile?
I know for sure that the Jabra BT800 will NOT. The headset works (actually, works great... good reception!), but the caller ID does not work.
Thanks in advance!
-Kevin.
Hi,
There are many ways to get the Bluetooth with Caller ID works on the PPC. The trick is that the Caller ID needs a Hands Free profile, which is not standard in the PPC. After using one of these ways, you will end up having the the caller number only appears, but no names. If this is what you want, I can tell you how it could be done.
Hi Waladany,
Yes, I would be very interested in knowing how to get it to work. A number (without name), is perfectly acceptable. I still have the Jabra BT800 headset for about 6 more days before I must return it for a refund, so I can use it to test.
Thanks in advance.
-Kevin.
Jabra BT800 and Caller ID and XDAII WM2003SE
I would also be VERY interested in how to get this to work... Thx...
Ok Guys, here are what i got.
You have two ways:
1- Install the merged rom made by sin (you can find it in the forum), as it includes the bluetooth fix. ( This is what I tried)
2-a- Install the Bluetooth Handsfree fix, I will attach it for you. After installing both updates, you should try to bond with the Headset. you should be receiving the message telling you that this is a Hands Free Device (Yes or No). You better say yes. If you said No, another message pop up twice asking if it is a Handset Device.
2-b- As a test, if you already have the headset bonded, you can go to the devices screen in bluetooth. Click and hold on the device, you should see a shortcut menu with the option "set as Hand Free". Try to select and test the Hands Free
waladany said:
1- Install the merged rom made by sin (you can find it in the forum), as it includes the bluetooth fix. ( This is what I tried)
Click to expand...
Click to collapse
I have the merged ROM by Sin, but still experience the same microphone issues. The CallerID works great, but the microphone on the headset is not active. Both the speaker and microphone on the XDA-II are operating.
waladany said:
2-a- Install the Bluetooth Handsfree fix, I will attach it for you. After installing both updates, you should try to bond with the Headset. you should be receiving the message telling you that this is a Hands Free Device (Yes or No). You better say yes. If you said No, another message pop up twice asking if it is a Handset Device.
Click to expand...
Click to collapse
Are you referring to the registry fix? I think that just makes you able to select hands-free at all. It doesn't fix the microphone problem.
The only thing I've heard that works is the 2.20 Chinese version. But I'm pretty happy with the Sin version. I wish we could find a quick fix for it.
If I've missed a new BT fix from Sin, please post the link here.
Thanks
bt
no way no how will BT CID work fully on even 2.20!! It sucks.
On 2005 it works FLAWLESSLY. But there are bugs on 2005, lack of mem, contacts and email database are new so will not work with many third party software, etc.
Even if you add the reg key "HadsfreeProfileOn", (Sins fix), or have any BT stack or even pray to the bluetooth God, your ****ed on 2.02 - 2.06.
2.20 is ****ty.. If I receive another call while using handsfree, even if I do not answer it, I loose all sound and mic ON BOTH until I click on Tools, Hands free off and then again tools hands free on.
Sometimes the mic - duel speaker things comes back and you have to reboot.
I wrote more here http://forum.xda-developers.com/vie...ghlight=&sid=a355793d319af7acb15784f153f9d7f1
Also, stay posted here, http://forum.xda-developers.com/viewtopic.php?t=19128 we may get help.
i have holux gpslim 236 and paired it with my XDA IIi then i started my tom tom navigator software and went to the device selection so i done the bluetooth one and tried every connection available in there and nothing it yet again says no gps device! :? i have no idea what i am doing wrong, i would love to see this thing work could anyone help me out pleaseeee.
is it the tom tom software??
the pda??
or the gps device ??
one thing i have noticed is when i go to bluetooth manager there is no incoming and outgoing connections for example its ment to show com ports, there is nothing can it be this?? please can someone explain where i am going wrong, thank you
Hi there,
Same hardware here. The GPSLim236 must be talked to using port COM6.
You might want to get GPS-Viewer, coms in handy when you need to diagnose GPS communication problems (it's there somewhere, can't make out where, Google knows I think ).
There's also a tickbox in the Bluetooth Manager regarding the SPP connection that says "Encryption" or something similar : make sure it is NOT checked.
Good luck !
In the connections tab click infrared and make sure "Receive Incoming Beams" is NOT ticked, If you have not already done it.
CHEERS guys, works now thanks for both helps
Hey folks,
I have a couple of questions regarding the bluetooth hands free profile and Caller ID and Contacts.
First issue: I use a Garmin Nuvi 760 as a speakerphone in my car via the hands free bluetooth profile. The 760 can't access the recent calls on my HTC Polaris (Touch Cruise) running the official WM 6.1 ROM...it just says, "no data available" when I try to access it. My old phone (T-Mobile MDA / HTC Wizard with the official WM 5 ROM) worked fine. The Wizard happily sent my recent call data to the GPS. If I remember correctly, the Wizard would prompt me the first time the GPS tried to access the call data, and then it just worked after that until I deleted the bluetooth device pairing. When I receive a call the Wizard also sent the name from my contacts to the Caller ID display on the 760, and my Polaris doesn't...it just sends the phone number of the incoming call.
Second issue: at home I use a XLink BT bluetooth hub to use my "land line" phones with my Polaris. It also uses the hands free bluetooth profile to connect to the phone and then emulates a "land line" for my other phones via my home telephone wiring. When I receive a call through the XLink I also don't get the caller name along with the Caller ID data...it just sends the phone number. I also have my girlfriend's 4 year old Motorola Razr v3 connected to the XLink hub and the contact name data comes through to the cordless "land line" handset just fine on the Razr.
I'm pretty sure these issues are connected, and I'm also pretty sure that there must be a setting somewhere on my Polaris to allow this to work, but so far I haven't been able to find it. Do any of you guys know of a setting or registry key that will allow me to enable this functionality? I'd really appreciate some advice.
Thanks!
Enable SAP Settings?
Hi
I think that this may be an issue to do with "SAP" or Remote SIM Access in bluetooth settings.
Cheers
andrew-in-woking
andrew-in-woking said:
Hi
I think that this may be an issue to do with "SAP" or Remote SIM Access in bluetooth settings.
Cheers
andrew-in-woking
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately Remote SIM Access is already on...I swear I've tried every setting I could find to try to figure this out.
Yeah, something is definitely just turned off somewhere (probably in the registry). I can dial from my phonebook from my nuvi via the handsfree bluetooth profile with my old phone (Wizard), but when I connect with my Polaris the option to dial from the phonebook is disabled (grayed out). Something is explicitly disabled somewhere...I just need to figure out which registry keys I need to change.
I'm really surprised I'm having such a hard time finding this info on the 'net.
Hi all,
Is it possible to turn my PDA (with Windows Mobile 6.1 Classic) into a bluetooth headset. So I can dial and receive calls on this PDA.
Or maybe there's software available to do this?
I know it possible to dial via bluetooth, but I also want to receive calls. And use the PDA's microphone and speaker. (Let the PDA act like a headset/carkit)
Thanks in advance
hehe. intriguing questions you have...
never heard of such an option.
I know you can receive calls thru your PC/MAC using your headset or device.. but i don't know of a pairing of 2 PDAs one acting as a headset..
I know its possible with PC/MAC and found software to do this, but couldn't find anything about doing this using a PDA.
I hope there is such an application out there.
If not, maybe someone can point me into a right direction on programming my own handsfree application.
Will I be able to let my application show up as bluetooth 'Hands free' service?
as i'm not a programmer i can't help you with that.. there are a few programmers around.. you can ask them.
l3v5y, supbro, oldsap, vijay555... PM one of them.. maybe they can help out a bit.