Does anyone know how to pair a device with no passkey on WM5?
I need to pair my Panda device with a bluetooth printer adapter.
Is there a registry entry to modify to bypass this step?
Thanks in advance.
That would kind of defeat the point of the passkey system, would it not?
But still ... I cannot understand why there is no unsecured BT connection.
If you want security ... ok ... if you don't ... well ... knock yourself out!
I want to connect my devices without bothering for keys pairing etc (of course my BT is NOT always on).
I'm agree,
the printer adapter not require to establish a relationship, need to set only a specific com port outgoing for bluetooth, but my device (Panda) cannot allow me to do this without passkey!
Instead I can do this with any HP pda (that are more and more easy to configure!).
How can do this with my device?
Thanks.
try settings /system/ connections/ bluetooth/ security/ and untick (beam authentication) setting - might be slightly different on wm5
Doesn't work, because the option was already unchecked.
Any other suggestion?
Thanks
Related
What does Beam on these Kaisers do I have it on mine and Have no idea what this feature is,
thx in advance
It's supposed to be for IRDA transfers, but without an IRDA port in the Kaiser I think it's now used for 'beaming' files to another device via Bluetooth.
Having it on enables other devices to send data to your phone thru bluetooth,try turning on your bluetooth and sending something to your device with the beam function off,you can't,no wonder it was called "Beam receive" in the past.
Thanks guy very helpful, I always wondered lol
It's just for to allow receiving of incoming bluetooth transfer, but I miss the IR port, remember those universal remote control software we used to be able to install.
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D88". It comes up in the list but under disconnected. So i'm like eh whatever, and setup the outgoing com port to COM0 as per the instructions, and make sure its unsecure.
I go back to devices, highlight BT-GPS371D88, click it. Check off "Serial Port" in select services to use, and save. Then heres where everything goes wrong, I hit connect, and it gives me the following message "Your device did not connect with BT-GPS371D88. The connection failed or the passcode is incorrect." I've been tinkering with it all day, searching various forums to no avail. Even downgraded my 6.5 rom to 6.1 thinking it was maybe incompatible with something so new.
Now i'm stuck, I really want to get it working so i can use it for a trip thats coming up in a few days. Has anyone else had such a problem? is there like a quick fix that i'm over looking, or is it simply not compatible with the fuze? I managed to get it paired up and connected fine to my blackberry curve just to see if the gps unit was defective (did buy it off ebay). Any Ideas guys? Not sure where else to turn now.
Oh yeah btw my current rom that i'm using is
At0mAng Fusion Power V 5.X ROM Series
Windows Mobile 6.1 (Build 21051 1.6.4)
Located @ http://forum.xda-developers.com/showthread.php?t=537501
jimshepp said:
So I picked up an external GPS receiver off ebay. It's the Globalsat BT-359C (http://www.usglobalsat.com/p-214-bt-359c.aspx). Turned it on, everything went fine as far as my fuze finding it. I'd goto add new device, it'd pull up "BT-GPS371D88", i'd select it, put it the four "0" 's, and it'd give me the message "your pocketpc is now connected with BT-GPS371D
Click to expand...
Click to collapse
have a BT GPS for my Dell axim x51v, got some trouble too getting it to connect, but eventually did
here are some pointers:
1) Delete all pairings and com port pairings on the device
2) Pair the device (make sure that you put 'request authorization' or something... this ensures that you need to put the 0000 code to connect)
3) you need to set up at outgoing port on your device, to the BT GPS... COM 8 is norm
4) External GPS setting in the Start>Settings tab
hardware port is where you put the outgoing port in (3)
software port is where you put for your GPS software... COM4 is norm
third column where WinMo will manage GPS, say yes
This worked for me:
I have a Hermes (WM6.5) with a holoux bluetooth GPS, but the GPS was not connecting for me properly either. It seems to be a problem with the way WM6.1 pairs with bluetooth devices.
I managed to get mine to work without reflashing by downloading this alternative bluetooth manager:
http://forum.xda-developers.com/showthread.php?t=353774
Hope this helps.
Not trying to bump up an old thread for no reason, but I figured this info would be helpful for people utilizing searches.
After lots of research and frustration the past week I have gotten my external GPS (USGlobalSat BT-368i) to work with my HTC Fuze! Below are the steps I followed that have worked for me. Note that I still have the phone configured to use the internal GPS if the program is set to "Let windows manage GPS settings".
1. Pair the device using Bluetooth.
2. Under the devices tab select your external gps device, and check the box to use "Serial Port". Then choose Save.
2. Under the Bluetooth settings choose "COM Ports" tab.
3. Choose "New Outgoing Port", and then select your device and click next. Choose your port and preferred "secure" option. Then click Finish. (I have configured mine to use COM0 & Secure Connection)
The device will still show as "Disconnected", and you will not be able to connect it under the Bluetooth manager. It will give you an error saying unable to connect.
To use the external GPS device you can simply select the outgoing port you configured above in your program, and most likely you will use a baud rate of 4800. Once you enable the GPS in the program it should connect itself via Bluetooth to your device and begin using it.
You should also be able to configure it to automatically use your external GPS instead of the internal one under the "External GPS" settings, but my current ROM has the hardware portion of External GPS manager broken @ the moment. Therefore I have not configured this, and cannot confirm it.
Hope this helps someone!
Hi All,
I'd like to share GPS data from my ASUS P750 (running on WM 6.1) over bluetooth to other device (my PC).
I seareched the network and forum and the only possibility I found is GpsGate. I'm looking for alternatives.
Does anyone have any idea how to:
- create outgoing port for GPS and share to that port data from internal COM (GPS).
Thank you in advance for any ideas.
cyklon said:
Hi All,
I'd like to share GPS data from my ASUS P750 (running on WM 6.1) over bluetooth to other device (my PC).
I seareched the network and forum and the only possibility I found is GpsGate. I'm looking for alternatives.
Does anyone have any idea how to:
- create outgoing port for GPS and share to that port data from internal COM (GPS).
Thank you in advance for any ideas.
Click to expand...
Click to collapse
http://users.skynet.be/hofinger/GPS2Blue.html
Thank You for quick replay.
The tool is nearly perfect.
The only thing I miss in it is automatic incoming bleutooth COM port configuration, i.e. after instalig and configuring the GPS2Blue it doesn't work automatically (at least on my WM 6.1). To make it working you have to manually add incoming BT COM port. So for those who don't want to spend time on Google.
To add incoming COM port add to your registry following entries (found in other thread):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Serial\Ports\Incoming]
"RemoteDCB"=dword:00000000
"KeepDCD"=dword:00000000
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Server"=dword:00000001
"Port"="COM6"
(For lazy ones attached Add Incoming COM6.zip)
Greetings
cyklon:
What do you mean by "automatically"? I just tried out this piece of software, and I'll be pairing it with a Bluetooth receiver on a camera. At some point, I would like to implement a shortcut on my phone which launches this program, opens a port, and automatically starts sending the data (rather than clicking through things). Is that what the registry setting below does for you, or are you talking about something else?
Austin519
Hi Austin519,
I don’t get what is your goal.
This tool among others allows you to get data from internal GPS device and send it to other COM port. For example you can use it to forward your internal GPS data to other phone or computer over Bluetooth COM port. In the tool you set the source COM (which is assigned to you internal GPS) and destination BT COM port (this port needs to be created by manually as incoming BT COM port).
I hope it help if not please describe what you want to achieve and what devices you wish to use.
Hi, hopefully someone can help me with the following question :
I just flashed my Polaris100 to Android 2.2, which works very good now. I'd like to use this device with the XCSoar navigation program, which normally gets its GPS data via the built in GPS.
During winter I'd like to connect my polaris to my Mac via Bluetooth using the serial port service, so that XCSoar can get it's NMEA data from my soaring simulator (SilentWings). So I need to transfer NMEA data from my Mac to my Polaris. This helps me to practice during the winter period. In WM6.1 this was easily done, because:
a) the serial service was build in
b) all used com-ports were shown in the settings menu or could be hacked to show/be edited.
So my questions are:
a) how can I activate the serial service in Android
b) how can I see which com-port is then used for my polaris BT connection (I need to set this port in XCSoar as external device)
I could not find a workable solution on the www or on this forum. I mean "workable", because most solutions or discussions are written in very technical terms and code, but I am an end-user and not familiar with all these terms. I do not know terminal commands as well...
Thanks for your help, Reno
I've never used Bluetooth, I connected to the computer through USB
Eh... what do you suggest by that? Although USB stands for Universal Serial Bus, it isn't recognized by the GPS app as a com-port. As I understood in that case I need a usb-serial service on both my mac as my android, right?
So can you be more specific and tell me how to do it with a usb connection?
Thanks, R.
Did you end up buying a OBD2 Wifi (not bluetooth) interface for your car, noticing android got some problems with ad-hoc connections and can't connect that easy, that you may have thought?
Well, if so, I'm at least not the only one
In my case I wanted to have a look at my engine stats etc. You might also be happy about checking the vin stored in the cars ecu with the one you got on paper, when buying a used car or else. Anyway I did not want those crappy bluetooth thing for some bucks. I wanted it to use wifi and also to be able to connect via usb to a laptop, if neccessary.
I got mine from eBay for about 80$. There is a bunch of these things avaible everywhere. I can't really tell you which one is better in which way. Most of them come out of china and are built pretty cheap, just like mine
BUT at least they work the way the should, once configured right.
IN GENERAL --> without any kind of workaround you shold keep in mind:
BT OBD2 is used for android devices. No Problem
WIFI OBD2 is usually used for iDevices, as they're not allowed to share BT with non-iDevices.
I didn't really make up my head about the second part, as I'm using android on every device I personally own.
Here's a tutorial on how I solved it anyway:
1. Buy yourself some OBD2 interface with wifi and the software you desire. Didn't test anything else but torque pro; no guarantee that other apps support these android-wifi-adhoc-obd-interface-workarounds
2. you need a rooted phone, in every possible case afaik.
3. Plug in your OBD interface and look, if you can see it in your wlan list.
In my case...I couldn't^^
If you see it jump to Number 4.4, if not, just keep on reading.
4. Getting my device, which is a HTC Sensation, with ARHD 6.6.7 - 4.0.3 ICS, connected to it required some effort:
4.1. I used a different wpa_Supplicant, to be able to see adhoc networks
I got this one: http://forum.xda-developers.com/showthread.php?t=1549065&highlight=adhoc also attached in the Thread. Full Credits go to the dev, although I don't know who it was exactly.
4.2. REMEMBER TO BACKUP YOUR ORIGINAL WPA_SUPPLICANT AND SWITCH WIFI OFF BEFORE!
It's stored in system/bin; so you'll need a explorer (mount R/W) for your phone's file system. I always used the root explorer. Worked flawlessly everytime. (mount R/O afterwards).
4.3. Flash the attached file in recovery -> I did at least find the adhoc network after it. Remember that some wifi off, wifi on sometimes solves problemes with this. This was at least the case for me. Reboot.
4.4. Now that you can see the OBD interface in your wlan list, you propably tried to connect, didn't you?
For most of us, this won't work, that easy, as your OBD interface doesn't work as a DHCP router, so you're in the need of taking a static IP.
Therefore it always depends on which IP range your interface is networking. In the most cases this will be 192.168.0.X
Picture #1 is a screen of the config tool, that came with mine so I can modify these values. (What is not really neccessary, cause you're doing this with your phone.)
Picture #2 are my stats. You can edit yours by long pressing on your desired OBD device in your phones wifi list and pressing "edit network". After that, change to advanced configuration and choose static IP.
4.5. Save your preferences and try to connect. Again I think my wifi needed a reboot to work with the values set now. So just swith it off/on again.
5. You're done. More or less. Because this is just what made me able to connect but drop my connection to the OBD after trying to access it via torque. It did connect (as seen on adapter status in torque), but lose connection after some seconds. It just didn't really work for a longer period of time. There also used to be connecting errors with my home wifi.
5. After hours of testing and experimenting with this whole topic I came to the conclusion my home network didn't work anymore or rather my phone couldn't keep up the connection. What you have to do is switch back to your old wpa_supplicant. Don't worry, your OBD interface should be saved and is still accessable afterwards.
5.1. SWITCH WIFI OFF. Navigate to system/bin via root explorer or similiar. (mount R/W) locate the wpa_supplicate and delete/rename/remove it and put the original file back in it. (mount R/O afterwards). Reboot.
(Picture #3 shows how it looked on my device after switching back to the original file.)
5.2. You're finally done.
Remember not to forget that wrong permissions could lead to errors. Refer to my attached screenshot or your original file, if neccessary.
where you found the configuration tool??