Dear all,
May be of a newbie's question, but did any of you try sync XDAII using the bluetooth? I succeeded on making the bond b/w my xda and the desktop, but the connections always drop a few second afterwards. Anyone...Help....Me....Thanks in advance
I have no problem syncing via Bluetooth. Did you use the ActiveSync profile of the Bluetooth software of your Bluetooth dongle?
What operating system is your pc running? I had similar issues with Windows 2000, but since moving to XP it works fine. The commonly known problem is that activesync can't connect to COM port 10 or above. This might be the problem with W2000, in that your PC can't assign a COM port for bluetooth of less than 10. There are many posts out there.
Dear,
Thanks both of you. Now I have succeeded making BT connection using the XP flatform
Thanks again
Virtual port and Bluetooth Tools
I'm having trouble running ActivSync over BT. I've sync'ed the XDAII to my PC (XP) - that's fine. However, running ActiveSync and following the instructions on http://www.angeltowns.com/town/bluetooth/guide_e.html#ActiveSync I've hit a problem.
It mentions something about a virtual port and configuring XP and ActiveSync on the PC accordingly. How do I go about setting up this virtual port ?
Many thanks
Nutz
UPDATE : Fixed the problem. It appears that the ports we're not the same between ActiveSync (File>Connection Settings) and Bluetooth Configuration (local services tab).
I've been using Activesync 4.1 (on WinXP Pro) with WM5 (1.60c) with no problems for the past month on my imate (Himalaya). I was able to sync via USB, BT, and IR. Suddenly, syncing through USB (Cradle) no longer works! I can sync fine via BT and IR, but when I try to sync via USB, here is what happens:
* Placed imate on cradle
* PC network detects this and provides IP address for USB. At this time, I can ping the imate. Activesync (AS) detects the imate and and the AS icon in the PC's toolbar turns green and starts to rotate
* AS says "connecting"
* imate neither says or shows anything (i.e. NO moving or rotating arrows on top bar near signal strength icon, as would be expected during sync).
* Activesync on imate also shows that it is NOT connected and shows info about last sync date and time
* when I press the "Sync" button on AS in imate, it shows "connecting" for a split second, then goes away, but that does not help.
* Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB when it was working with no problems.
*It stays in this state indefinitely, or until I remove imate from cradle
Here is what I did to troubleshoot (Believe me, AS 4.1 has been a headache that caused me many long hours, days and weeks to solve. I had that dreaded 85010014 error that took weeks to resolve, so I was prepared to do all kinds of things to troublshoot this, but to no avail. I searched many forums, including this one, and googled to no end before writing this post):
* Although it was working with my e-trust firewall before (had it set up to OK all activesync programs), I turned it off just in case.
* Although it was working with my e-trust Antivirus before, I turned off realtime montoring just in case.
* On the imate, I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1)
* I pinged imate, and it responds fine
* I checked on my PC under "Network Connections" and it shows a Local Area Network for the Windows Mobile-based device
* I checked my PC hardware and found Windows Mobile-based device and is working properly
* I made sure that both AS on the PC and imate have the USB syncing option checked
* I exited XCPUscaler and unchecked PPC Profiles Pro from Today screen
* Doubting that this had to do with application of Darren Humphries' Activesync tweek, I reverted it back to default (see below).
* I unistalled the "Windows Mobile-based device" under Network Adapters, restarted PC, then re-attached imate.
* I unistalled the "Windows Mobile-based device" under Network Adapters, restarted PC, uninstalled Activesync 4.1 on PC, restarted PC, removed AS folder in program files, looked for rapi.dll (did not find it), deleted activesync related entries in registry, restarted PC, removed partnership from imate, soft-reset imate, reinstalled AS4.1, then attached imate to cradle.
* Basically, I did everything that was suggested so far, short of reinstalling WinXP on my PC or hard resetting the imate
Believing that AS should not suddenly stop working on its own (not sure if this is a valid belief!), I retraced my steps to see what changed since the last USB sync. Here are the changes (note: there were no WinXP updates made during that period):
On imate:
* Installed XCPUscaler
* installed PPC Profiles Pro (Brett Darnell's)
* Installed Toe's ScreenRotate Fix
* Installed MS Voice Command
* Applied Darren Humphries' performance tweek as follows: "In order to stop Activesync from periodically starting on it's own. To do so open Activesync on your WM5 device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right. You can now go to Menu>Options and delete the Exchange Server setting you just added. Now Activesync will not start when you cradle your device."
Could it be a hardware issue, i.e. USB connection on the imate connector not working (if so, then why would I be able to ping the imate with no problems through USB?). Please let me know if I am missing something.
Thanks!
KJ
Just to help isolate the problem, I installed AS 4.1 to another WinXP machine and attached the USB cradle connector to it. Same problem. Hence, it does not seem to be a PC issue.
So far, it seems to be isolated to either the imate or the cradle (and cable). Note that the PC recognizes the USB connection and does the networking thing just fine, hence the cradle should be OK (is there a way to check the USB connection on the cradle to make sure it is OK?). Pinging also works both ways and I see the 169.254.2.1 address on teh imate. So, the problem does not seem to be the connection. Rather, it seems to be with Activesync on the imate realizing that the imate is cradeled.
Recall that one of the changes to the imate I made right before this problem was the AS hack of a fake Exchange server so that the schedule is changed to "Manually", as described in my first post. I reverted back to original "every 5 minutes" but the problem persists. Are there registry keys that I can compare to make sure registry is correct? Note that I can sync fine with BT and IR and both of these have entries in AS Menu that say "connect via IR..", etc. in order to connect manually, but no "connect via USB" manual option.
KJ
I had a problem very similar to this.. it only appeared with 'guest' and no partnership..
Turned out my calendar/contacts file was corrupt.
activesync issue
my exec sync the first time allright did instale some software after that next day ,i've got this message alltime :twisted: To synchronize this device,you must install ActiveSync 4.0 or higher.....
i did unstale the active sync instal it again same pb .plz help anybody
i keep reading the forum nearley every day but seems only me got pb now with activesync???
i hope it's the roght place to put down this issue otherwise plz direct me
many thnx
activesync issue
sry i was bit quick in the posting
well i've got win xp sp2
i've done the same things as kj
ihad aswell that error 85010014,;and the server assigned IP adress issue
and after unistallig many reboot anr reinstallig active sync .........
it's basiclly frustrating .
I 'm give up slowly on it
any help will be very welcome or direct me in the right posting
Activesync 4.1 USB Issue (more info but still _not_ solved.)
Thanks for the suggestions and comments. I refrained from responding before I performed a thorough (re)investigation. I have the following updates: I just received a boxwave minisync retractable USB cable for my imate/XDAII/Himalaya to test out the theory whether the cause of the problem was a cradle problem (i.e. applied process of elimination on hardware). Unfortunately, the problem still persists. I can now safely eliminate the possibility that it was the cradle from my previous investigations. Therefore, I decided (having done all the investigation above) that it must be either of the following culprits:
A. Himalaya hardware
B. Himalaya software
I tackled the hardware issue (A) first: I checked the functioning of the USB hardware: My logic dictates that if I can connect the Himalaya to a PC using USB and conduct functions through that connection, then the USB hardware should be OK (except for perhaps any hardware switches or pin grounding the flat connector on the other end of the USB cable makes that activate the Himalaya onboard activesync program, as discussed below). So, I performed the following tests (some are repeats of what I already tried and wrote, just for good measure):
1. Connected Himalaya to my laptop (call that “PC1”, since recall that I tested on two separate PCs) via USB cable. It detects it fine and goes through the hardware detection and driver install process, creates a network adapter and connection and provides an IP address for the USB connection (169.254.0.1 for Himalaya and 169.254.0.2 for PC1). At this time, I can ping the Himalaya. ActiveSync (AS) on PC1 detects the Himalaya and the AS icon on the PC's toolbar turns green and starts to rotate, as before, but no reaction from Himalaya.
2. Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB back when it was working with no problems, so not sure if this is an issue (it wasn’t before).
3. On the Himalaya, I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1). I pinged the Himalaya from PC1 and PC1 from Himalaya, and the responses are fine both ways. This tells me that USB connection hardware must be working, otherwise, I would not have been able to pass ping packets back and forth.
4. I went one step further (just to be sure) and downloaded and installed Softik’s Card Export II v2.10 (yes, this version supports WM5, a nice piece of software). In “Card Export mode”, I connected Himalaya to PC1,which detected it as a USB Mass Storage Device, as it should. It installed the drivers and it worked just fine! I wanted to make sure that I am getting USB speeds, so I benchmarked the connection and got over 3Mb/s transfers from PC to SD card, steady. This tells me that at least USB, as a connection, is OK.
5. So, only thing left is to eliminate any possibility of a hardware issue, I looked into the Himalays flat connector pinout diagram. To simplify, the following are the pins relating to USB (excluding any grounds):
13 USB_VDD
14 (or 15) UDC+
15 (0r 14) UDC-
For those who are not familiar with the Himalaya flat connector, “UDC+” and “UDC-“ are USB data pins. “USB_VDD” is the USB power pin. USB_VDD when powered wakes up Himalaya and activates onboard activesync. I thought perhaps if this pin were defective, Activesync on the Himalaya would not activate. I assume that this pin is where the Himilaya gets its battery charge current when connected via USB, as pins 20-22 are “V_ADP”, which are used for charging only when connecting to a wall or car charger (please let me know if this is an invalid assumption). Hence, I wanted to check to see if the battery indeed charges through USB. I saw that when Himalaya was connected via USB, the battery charged just fine (light goes solid amber, battery monitor says “Charging”) and it charges the battery fully as expected.
With the foregoing, I can conclude that the problem is very unlikely hardware related (as in A, above). Since I already eliminated a PC problem (I checked on another PC with different hardware/software, as described in my first post), the only thing left to investigate is a software problem on the Himalaya itself. This is where I look for the developers in the forum to provide expertise: My analysis tells that when the Himalaya is connected via USB and the PC Activesync shows “Connecting”, while the Himalaya shows nothing, that the Himalaya is behaving as if it were not connected to USB, or is ignoring the USB connection, i.e. in Himalaya Activesync, under “Menu””Connections …”, as if the box next to “Sychronize all PCs using this connection:” is not ticked or the drop down list is not set to “USB”. I checked and unchecked this box and chose other connections (such as various serial speeds), just to see if this would change some persistent setting and set it back, with soft resets in between, but to no avail. Is there a registry setting that I can check to see if this setting is doing the correct thing? If so, where is it? It is here where my investigation trail runs thin and is where I am looking for insight in the matter. Appreciate your input….
Active Sync 4.1 on WM5
I had the same problem after upgrading to WM5 on BA (Xda iis)
But I finally found the resolution for this problem
If you can not sync with your USB try this:
go to the properties of the My Network Places
Plug in you device and you will see a new network connection
On the properties page on the new connection you will see that the internet protocol (TCP/IP) is not checked
Select the TCP/IP checkbox an then apply changes
The USB will start connecting to the device.
@kj
i have the same problem as yours sinds yesterday.
i think i happend just right after i've cleart the duplicate enteries from the events database. (check notification/scarybear)
do you use some sort of databse cleaner software?
for the record i've tryed with htc wizard (wm5) and htc himalaya with wm2003. when i sync with the himalaya then is everyhing fine. the wizard have the same problem as yours.
Re: Activesync 4.1 USB Issue
Thx all for the replies.
@ISR: Verified that TCP/IP was already checked. Note that if that was not checked, I would not have been able to ping the device. I really doubt this is a PC issue, although I realize that most people had problems with their PCs and Activesync (I checked this with 2 separate PCs with completely different configs, one with no virus checker or firewall). The problem is most likely the software on the Himalaya. When you say yours had the same problem as mine, do you mean that you were able to ping pckets through USB both ways, sync through BT, but when syncing through USB, only Activesync on the PC shows "Connecting" with nothing going on on teh Himalaya (most people have the opposite problem due to firewall and other TCP/IP issues)?
@Badboy18: No, I don't use a database cleaning software, unless one of the softwares installed on the imate already does so in the background. Same question to you as with ISR: When you say yours had the same problem as mine, do you mean that you were able to ping packets through USB both ways, sync through BT, but when syncing through USB, only Activesync on the PC shows "Connecting" with nothing going on on the Himalaya (most people have the opposite problem due to firewall and other TCP/IP issues)?
hi all,
just to add to the defferentes experience well, I've got as well a xdalli and i did use it with activesync 3.8;so when i bought the exec I installed the as 4.0,after that I did remove all the activesync with ther regestry key and defferent folders on the pc;fraiche install again ,well all the step donne by kj
and now I got thise message came as <to synchronise this device,you must install activesync 4.0 or higher on your desktop computer> ?????
and on the pc i've got AS 4.1.0(build 4841)!!
some times when I restart the pc and do a soft reset on the exec ;it does connect as guest????..sometimes :x :x
and the xdalli still can do a parternership with the pc even it's AS4.1,were in the forum it's normaly has to be with AS 3.8???
I believe very much the probleme is in the activesync software put on the xda exec (sry i'm not very technical to try defferentes things;it's just suggestion) thx for u everybody to try to get this exec to sync just dont give up
How to ActiveSync after deleting repllog.exe
try this link of any help
http://www.ppcsg.com/lofiversion/index.php/t53614.html
kj said:
I've been using Activesync 4.1 (on WinXP Pro) with WM5 (1.60c) with no problems for the past month on my imate (Himalaya). I was able to sync via USB, BT, and IR. Suddenly, syncing through USB (Cradle) no longer works! I can sync fine via BT and IR, but when I try to sync via USB, here is what happens:
* Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB when it was working with no problems.
I had this problem. Try config manually this:
In Settings/Connections/Network Cards :
Select Remote- NDIS Host ----> Use specific IP addrees
IP address = 169.254.2.1
Subnet mask = 255.255.0.0
Default Gateway: 169.254.2.2 or 169.254.2.1
I have this config and it is working now.
In your PPC Select In : My Network card connects to : "The Internet" and the same should be selected in your PC ActiveSync ---Connections Settings ---This computer is connected to: "The Internet".
Click to expand...
Click to collapse
Thx for suggestion. I tried that before, and again just now, but it did not work. As mentioned before, I can ping fine both ways, which tells me that DHCP worked and provided correct IP address for communication. Basic hunch is that the problem is with the device, i.e. Activesync on the _device_ ignoring the USB connection. All other software I tried that use the USB connection (whether pure USB, or through the TCP/IP stack) work. So, I am zeroing on activesync on the device, but have reached a dead end, as I don't know which registry settings and processes spawn on the _device_ when activesync starts a USB sync (perhapsone of them is not running).
KJ
kj,
Similar problem. Hard reset, problem now gone. Have you tried HR option yet?
I was planning to do a hard reset, as a last resort (I mentioned once that I wanted to debug the hard way first!). I will do a HR only if you think the problem will go away with a data-persistent HR (WM5 feature), rather than a clean wipe. The reason is that if I am to do a clean HR, I would rather do that when a new ROM is around for an upgrade (as you know the Himlaya ROM development is quite active). If you think a data-persistent HR would rectify this, please elaborate as to what options to choose with bootloader to make that possible.
Thanks!
I'm able to sync but I get the stupid "Unable to obtain IP..." via USB.
Everything is setup correctly and sync works, but the message is anoying and without a cause.
I used eramosipn solution - fixed IP - problem gone. Thanks dude!
I guess something is broken in the registry.
I sync with 2 different PC's and this problem occured on on both. Since the beggining I know this is a PPC problem. Just don't know what to correct.
Anyhow, with the fixed IP the stupid annoying message is gone.
Where can we found the correct registry settings related to USB activesync?
Activesync and Firewalls
I have a personal firewall in my pc (sygate).
I upgrade to windows 2005, everthing was fine.
Someday stop working.
After research I find that if I disable the Sygate Firewall service ( In Control Panel) it starts working.
Can this be the case for you?
Do you have any firewall in you system (including xp firewall)?
Try to disable or uninstall.
Hi
I am not sure if will help anyone but her goes.
Upgraded SPV M1000 to WM 2005 most recent 1.71a 64.
Upgraded desktop Windows XP and Company Lap with activesync 4.1.
I now have 3 different reactions from activesync.
1. No problems with Home desktop (outlook 2003 running in none exchange server mode).
2. Will not sync with comany laptop (Outlook in exchange server mode) while working at home offline (not connected to company server).
3. No problems to sync with Company Latop (Outlook in exchange server mode) when working online to company server.
Anybody found away to solve instance 2?
Thanks Mike
MTU problem?
I cannot recall where I read this, and cannot find any references via Google except for Sygate firewall MTU issue, but I did read somewhere that Activesync 4.x defaults to an MTU size of 8000 while the USB TCP driver starts having problems above 5000.
I used DrTCP to set the MTU much lower for every Windows Mobile Device interface (you will get one created for each independent USB port to which the Pocket PC is or has been connected). Currently I am at 2048 and connectivity for my Universal is much better than it was, although still far from reliable.
Hope this helps!
check this link
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm
it solves the 85010014 error in point 4 and below.... to be honest, it solves all ASync probs.
Hello everibody! Since ~ 1 year i’m a heavy reader, but i’ve never posted before, since i could find all my answers just reading…
But recently i bought a Universal wich i have unlocked and upgraded to WM6 – (Thanks thingonaspring, great ROM! ), and lost my AS connectivity (over BT). Kept on reading, but none of the provided solutions worked.
So, here is my 2 cents, hope, it will help for others too:
XP (from SP2!)
Basically, my problem was, that my Uni allowed as outgoing ports only COM0, 4 and 5. I use a really chep BT dongle from eBay wich came with Blue Soleil 1.x as driver and software, wich allows as incoming ports only COM11, 12. I’ve tried all of the Blue Soleil drivers wich i could find ont he net, even the most recent 5.x versions. None of them provided these ports to be opened.
My solution was thet i deleted all the custom Blue Soleil drivers, and let Windows to install his – generic – BT drivers. From here my problem was solved, since it doesn’t install any predefined ports, i can install them manually, as needed, and, since i know wich ports can be opened on my PDA as outgoing ports…
So, here are the steps from scratch:
1. Delete all BT related drivers, and let Windows recognize the New Hardware and install his Generic drivers for it, reboot if necessary.
2. Open My Bluetooth Places - Bluetooth Devices select COM Ports tab. Button, and we add port(s) til we reach the number we want (my case was COM4, so i’ve added ports 3 and 4, windows adds ports one by one, starting from the hardware ports. COM3 can be deleted aftrwards), as an Incoming Port. Ont he Options tab w eset this port as discoverable, save. Ok, now we have the necessary port, but we need an incoming connection too, ont hat port, so:
3. Start - Settings - Network Connections - New Connection Wizard.
4. The wizard starts, Next - Set up an advanced connection - Next - Connect directly to another computer - Next - Host - Next – we choose our port and save our settings, be careful, the PC should remain as dicoverable!.
5. Still not enough, our PDA would make now a Serial Port profile connection, but, we need AS to work, so:
6. Fire up ActiveSync, File - Connection Settings - Allow connections to one of the following - we choose our port, everything else is allowed and on Automatic. Save.
7. Ok, our PC is prepared, let’s see the Uni, it’s far more simple: at BT settings we pair our uni with the PC, and, as expected, we have an ActiveSync profile from the PC, wich we select.
8. ComPorts tab, New Outgoing Connection – we choose our port number (if it’s not there already), Save.
9. Start – Programs - ActiveSync - Menu - Connect via Bluetooth, and success, we can synchronise and we have network too!
On WinVista (i have Vista Ultimate installed):
as described above, with a few modifications:
- VISTA doesn’t recognize the hardware (at least mine isn’t recognised) , so it installs it as Unknown device. So, we have to „refresh” it’s „drivers” manually – we won’t let Windows to search for drivers, we select manually: Microsoft - Generic Bluetooth Radio, OK, now it finds the Microsoft Bluetooth Enumerator too.
- we don’t have to follow points 3 and 4.
- now we already can establish an AS connection, but, without network support. To enable this, we must select on our PC int he Microsoft Mobile Center – Mobile setting – connection settings NOT the Automatic connection, but the same as we have on our PDA at the Network connections, where it states „Programs that automatically connect to the internet should use… Usually My Work Network. The effect is immediate, we don’t have to restart anything.
- If i used VISTA, i didn’t had to add ont he PDA a new outgoing port (i didn’t have the possibility), but, it works without it.
One more observation: our PDA can have an AS connection over BT with only one PC, so, if we pair it with another PC, we loose our first pairing. So, it is advisable to leave our PC in discoverable mode.
Hope, somebody will find this useful.
I found this by googling, and successfully connected to my Vista Laptop.
Here it is solution:
Firstly, on your host machine, open Regedit and navigate to:
HKLM\Software\Microsoft\Windows CE Services\SerialPort
and change the value from Bluetooth to your incoming bluetooth COM port. Normally this is COM7 if you are using v5 of the Toshiba Bluetooth Stack (the Vista compatible version). Change the value to "COM7" (without the quotes).
You will need to restart your machine.
Now pair your Windows Mobile device with your host machine. You should see the ActiveSync service listed. If you've previously paired your device, then you would have seen "Serial Port" listed as a service (which isn't enough to get ActiveSync working). Instead go into the properties of the bluetooth device and select "refresh" to get an updated list of services that your host PC is advertising. ActiveSync should now be an option. Select it. Now, when using ActiveSync on your WM device, Connect via Bluetooth should work just fine.
I found second better solution. Then you can use Windows SideShow as well.
1. Uninstall Toshiba BT stack.
2. Go to Dev Mgmt.
3. Find Unknown device
4. Update driver
5. List all drivers
6. Find Cambridge manufacturer
7. install Generic Radio
Thats all.
I used many websites, a lot with very similar advice, but none specific to the HTC touch Diamond conundrum.
However, this is a very useful step by step guide:
http://www.inspectmygadget.com/2007/05/31/how-to-connect-your-wm5-device-to-wmdc-via-bluetooth/, which although provides advice for WM 5, is still the same principle.
The advice below is device specific
I use:
HTC Touch Diamond (with WM 6.1)
WMDC 6.1
Bluesoleil V6 Bluetooth Dongle
Although I had found the above advice on previous websites, and it had not worked I remained persistent.
I was able to find 'Activesync' as a service when, on my PC, changed the WMDC connection settings to COM 3.
However every time I tried to 'connect via BT' on my device, it said 'no partnership existed......'.
I therefore established some more com ports on my computer (in addition to COM 3, COM 4, COM 5 which I had taken authorisation off of):
COM 6
COM 7. Both without authorisation.
I then used the trial and error method to find which com port would broadcast 'activesync' to my device. It was still COM 3.
However, on trying 'activesync via BT'on my device this time, it began to connect!!!
I am not sure whether opening up the extra ports (COM 6 and COM 7) or whether my computer/device decided it was now the time to play ball since it realised I was about to take a cricket bat to it worked but it now syncs fantastically.
pa3x said:
I found second better solution. Then you can use Windows SideShow as well.
Click to expand...
Click to collapse
Dude! You're my hero!
pa3x said:
I found second better solution. Then you can use Windows SideShow as well.
1. Uninstall Toshiba BT stack.
2. Go to Dev Mgmt.
3. Find Unknown device
4. Update driver
5. List all drivers
6. Find Cambridge manufacturer
7. install Generic Radio
Thats all.
Click to expand...
Click to collapse
Thank YOU!!!!
pa3x said:
I found second better solution. Then you can use Windows SideShow as well.
1. Uninstall Toshiba BT stack.
2. Go to Dev Mgmt.
3. Find Unknown device
4. Update driver
5. List all drivers
6. Find Cambridge manufacturer
7. install Generic Radio
Thats all.
Click to expand...
Click to collapse
Plz elaborate as where to perform it?
i have i-mate JASJAR will it help to connect it to a desktop pc inwhich i dunt wanna use wire/cable connection USB???
am on WM 6.1
with Bluesoleil V6 Bluetooth Dongle on Desktop PC.