xda exec bluetooth browsing question

[daven]

hi i have an xda exec and i want to browse the files of another pda/computer/phone using bluetooth. i was wondering if anyone could help me as i dont know how to do it. Thanks.

[daven]

someone help me please

[adamdon89]

I've been wondering how to do this too.

[underwurlde]

Yo!

I have just done this on my Xda Exec.
It has taken me an ENITRE weekend of shouting at my PC - it has been an utter nightmare. :evil:

HOWEVER...

This is GOOD news for you two! Why? Because you won't have to go through the same SHIT that I have had to go through! AND, because my memory is so crap I have written (most) of it down, so here goes:

Oh, before I bore you to death, one guy on this forum was helpful beyond measure, so a shout goes to: simon_darley - Thank-you once again.

>deep breath<

Andy’s Bluetooth Blues Guide
11th March 2006
Reference links
http://forum.xda-developers.com/viewtopic.php?p=240575 << My original Thread in this forum re this problem
http://users.spark.net.gr/~yiapap/bluetooth.htm << Bluetooth Blues - bit of a rant by some dude, cheered me up!
http://help.lockergnome.com/lofivers...hp/t26563.html <<< HUGELY IMPORTANT!
http://thestaticvoid.net/drivel/180/...over-bluetooth << Follow the links

The WIDCOMM Bluetooth USB driver for PC
Thread discussing source & installation etc etc of latest Generic WIDCONN drivers, see here: http://www.gsmhosting.com/vbb/archiv.../t-238831.html

Get the latest ‘generic’ WIDCOMM drivers, v5.0.1.1200 (as of 5th December 2005) which does not require a licence key from here for both Win(x32) & Win(x64) platforms (and is hence 111mB in size):
http://www.megaupload.com/?d=DLTT1EFT

v2 Patch from here:
http://forum.gsmhosting.com/vbb/show...8&postcount=64

(Note:Patch is required if Bluetooth hardware dongle is non Broadcom based – thanks for that).


Guides to look at
http://home.comcast.net/~spam-target/index.html
http://web.belkin.com/support/download/download.asp?download=F8T003_v1<=1&mode=
http://www.logodesignworks.com/iPAQ-...ronization.htm
(from here: http://www.pocketpcmag.com/forum/top...?TOPIC_ID=2229)

PC Internet connection sharing on WinXP Pro: (Thanks: coldpenguin): http://forum.xda-developers.com/viewtopic.php?p=240435


OVERVIEW
This guide is based on Window XP Pro Operating System - it is a MUST that Service Pack 2 (SP2) is installed as well!
Also that ActiveSync v4.1 is installed.
Note: Some people have got Bluetooth working 'straight out of the box' no drivers, no setting up. This guide is for unfortunates like me!

Also note that I am NOT an expert - I have merely glued together many sources of information that has taken me literally DAYS to search out, sort out, discard chaff, faff & fart about & eventually record in these notes - there may well be things I've got wrong & missed out but I have tried my very best to correctly record everything here for everyone's benefit - please do NOT just BLINDLY stumble your way through these steps - read, understand, & then apply with at least some intelligence !!!!

OK. so what is Bluetooth: I have come to think of Bluetooth as not the ACTUAL connection between two devices, rather it is the 'medium' through which two devices can be connected. Note also that two devices can both have Bluetooth turned on, but are not 'paired' (notice I have avoided the word 'connected') - you must 'pair' or 'partner' two devices FIRST (using ActiveSync).

A device, once Bluetooth is installed correctly AND turned on AND is set as 'DISCOVERABLE' can be set up to offer 'services' (such as an internet connection) to which another 'partnered' device (such as the XDA Exec) can use. This is true for any device using Bluetooth that is to say both the PC AND the XDA Exec (which I shall be calling the 'PPC'). Services (Internet, Fax, Dial Up Networking [DUN]) are offered on set, preassigned COM ports that are given an unique number. e.g. The PC will offer a internet connection service on 'COM4' which the XDA PPC must connect to (COM4) in order to use.
Once a Bluetooth partnership is successfully initiated, this also means that not only can share a high speed internet connection, but also use other services if made available via unique COM port numbers such as PRINTERS! {Thinking about this, I wonder if a Mobile Phone Bluetooth service can be offered by the XDA & used by the PC???} Clever yes, implementation, could be simple - for some it is, for others, not quite the dream it should be.

Once your XDA Exec is connected to the internet then interesting things can happen:
Skype! FOR FREE!
Skype VIDEO calls!! FOR FREE!!
MS Messenger doing the same thing!!!
Browsing the internet on the bog!!!!


HOURS OF FRUSTRATION SAVED DUE TO DISCOVERY OF THESE BUGS:
Installing Bluetooth Internet connection to my PC was a bloody nightmare due to a series of rather well hidden, not too obvious bugs:
You MUST install ActiveSync v4.1
If using Windows XP Pro - You MUST install Service Pack 2 (SP2) (& Make sure it's Up to date using UPDATES)
The BIGGEST Bug: COM port numbering: On the PC, you can assign COM ports from COM1 to COM256, HOWEVER, due to a BUG, the XDA Exec ActiveSync can only use COM ports from COM0 to COM9. This would be OK if it were not for the fact that:
I could not use the standard windows Bluetooth driver & had to install the WIDCOMM ones BUT YOU CANNOT DIRECTLY CONTROL COM PORT NUMBERING: So if you accidentally go past assigning COM9 on the PC, YOU CAN'T BLOODY WELL GO BACK AND AS A RESULT YOU'LL >>N E V E R<< BE ABLE TO CONNECT TO THE XDA !!!!!!!! (Guess what happened to me, fortunately there IS a way out of this).
- PC: "Allow other network users to connect through this computer's Internet connection" - actually finding that option
Another BUG (possibly): When creating an ActiveSync Bluetooth partnership, a password (that must match on BOTH devices) is requested. ENSURE THIS IS 8 (EIGHT) CHARACTERS OR MORE, even though it allows you to use less than 8.
BUG - Once that Bluetooth connection is working DO NOT, I REPEAT D O N O T REMOVE THE DONGLE FROM THE USB PORT - if you do, good old Windows in it's Plug&Pray wisdom will come along with a big cheesy toothy American smile on it’s chops & undo all your hard work!



Phantom / Ghosted COM Ports:
While the port overloading technique may work, the REAL solution is to rid your XP system of the phantom COM ports. These ports have been created at some time by an app or hardware that is NO longer present, but XP is holding the COM ports as valid but hidden. MS ActiveSync (even v 4.1) will ONLY see single digit COM ports per design, so you HAVE to get those Bluetooth COM port assignments into the single digits. Here is the link the MS site that describes how to rid your XP system of the phantom ports:

http://support.microsoft.com/default...b;en-us;315539

This is what it says to do:
SYMPTOMS
Device Manager displays only non-Plug and Play devices, drivers, and printers when you click Show hidden devices on the View menu. Devices that you install that are not connected to the computer (such as a Universal Serial Bus [USB] device or "ghosted" devices) are not displayed in Device Manager, even when you click Show hidden devices.
WORKAROUND
To work around this behaviour and display devices when you click ‘Show hidden devices’:

1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2. At a command prompt, type the following command , and then press ENTER:
set devmgr_show_nonpresent_devices=1
3. Type the following command a command prompt, and then press ENTER:
start devmgmt.msc
4. Troubleshoot the devices and drivers in Device Manager.

NOTE: Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.
5. When you finish troubleshooting, close Device Manager.
6. Type exit at the command prompt.

Note that when you close the command prompt window, Window clears the devmgr_show_nonpresent_devices=1 variable that you set in step 2 and prevents ghosted devices from being displayed when you click Show hidden devices.

In Device Manager, Go to ‘Ports (COM & LPT) Tree, expand & REMOVE ALL THOSE BLOODY ‘Standard Serial Over Bluetooth links!
In Device Manager, Go to ‘Bluetooth Radio’ tree and remove any ghosted ‘Microsoft Bluetooth Enumerators’!

To allow ghosted ports to be viewed all the time, set this environment variable globally: In Fact, do this anyway!!!

1. Right-click My Computer.
2. Click Properties.
3. Click the Advanced (tab).
4. Click the Environment Variables (tab).
5. Set the variables in the System Variables box. Click New: Variable name: devmgr_show_nonpresent_devices, Variable Value: 1
6. Reset PC.

Once you follow the process you will be able to delete any port in the device manager including the phantom ones (i.e. those greyed-out). Once you are back to ONLY the real ports on your system (& hopefully back into the single digits, if you uninstall Bluetooth and then reinstall the Bluetooth COM port assigned will be single digits and then ActiveSync will see the port.

Also I suggest that you go ahead and setup the environmental variable as per the process described in the above link so that in the future, you can just launch Device Manager, select view and then show hidden devices and you will be able to see what ports are phantom and which are not.

TACKLING COM PORTS ON THE PC THAT ARE > COM9
(& Hence unavailable to the XDA Exec PPC) – Here just for reference.
http://help.lockergnome.com/lofivers...hp/t26563.html

Do this if you get stuck with COM ports if you've installed the WIDCOMM driver (supplied USB Driver for your Bluetooth Dongle). (Best mention this section first) To do this, you've got to uninstall the driver & replace it with the generic driver that comes with Windows XP SP2:

o Firstly, remove the WIDCOMM drivers and return to the native WinXP driver (WIDCOMM drivers won't allow you to change the COM port allocation, the native does). Do it thus:
Start > Control Panel > Performance & Maintenance > System > Hardware (tab) > Device Manager:
Expand 'Bluetooth Devices' Tree: Uninstall the WIDCOMM driver (Right Mouse Button, properties on device name to see which one is the WIDCOMM one).
For me the WIDCOMM Bluetooth Device driver was called 'CSR Bluetooth Device'.
Remove any program files thus:
Shutdown Outlook if it is running
Start > Control Panel > Add Remove Programs > Scroll down to & Select WIDCOMM Bluetooth Software & hit Remove (it may be necessary to remove the Dongle during the un-installation process, if so remove it). May also get a ‘cannot find BTW.MSI’ error during the un-installation process, this is because the original install files cannot be found.
Turn the PC off.
If it exists, rename C:\ Progam Files \ WIDCOMM to WIDCOMM_OLD
Now, find a suitable, free USB port. Plug the Bluetooth dongle in AND DO NOT EVER REMOVE IT (so choose a free USB connection wisely). If you do, you will be going through all this crap again.

If Windows XP SP2 doesn't install any Bluetooth drivers, try updating the driver in device manager - WinXP's SP2 included new Bluetooth drivers so in the absence of the WIDCOMM’s they should be available to install:
. the SP2 driver details are:
. Driver Provider Microsoft
. Date 03/08/04
. Version 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

. But rather than search allow XP to install the driver itself:
. Right click your My Computer (icon) > Properties > Hardware (tab) >Device Manager:
. Expand the tree to be able to see Bluetooth Radios
. Right click Generic Bluetooth radio: Properties > Driver (tab) > Update driver
. And the above driver should be installed from your SP2.

By now you should only see the following WinXP Generic Bluetooth drivers in place:
Start > Control Panel > Performance & Maintenance > System > Hardware (tab) > Device Manager:
Expand 'Bluetooth Radio's' tree: You should then only see:
. Generic Bluetooth Radio
. Microsoft Bluetooth Enumerator

Expand ‘Ports (COM & LPT). You should see a new port that has been added:
. Standard Serial over Bluetooth link (COM3).

>>>>>>>>>>>>>>
>> OK. The stage we are now at is that ALL unused and ‘ghosted’ COM ports are FREE. Now we can install the better WIDCOMM Bluetooth driver:
>>>>>>>>>>>>>>

GETTING WIDCOMM BLUETOOTH DRIVERS TO INSATLL UNDER WINDOWS XP SP2

Overview
Note: This section is also for those who installed the Service Pack 2 for Windows XP and are experiencing problems with the WIDCOMM Bluetooth software..

If you install the WIDCOMM (1.4.2.10 - may be true for other versions) Bluetooth software on Windows XP SP2, you will get the following error as soon as you double click on the blue-red system tray icon: "Your Bluetooth Software license does not include use with this Bluetooth Device [6]"

After that you will be asked to point to a valid license.dat file. However if you select the license.dat that came with your manufacturer's driver (be it on CD-ROM or downloaded from the manufacturer's website) it still won't work.

The reason for this problem is:
In the Service Pack 2, Microsoft included a generic Bluetooth driver, naturally being
WHQL-certified -- it's directly from Microsoft. The WIDCOMM Bluetooth driver however is not
WHQL-certified, so Windows XP continues using the generic driver. This interferes with the
WIDCOMM Bluetooth software resulting in the above error.


Preparing your PC:
Disconnect your Bluetooth USB device & reset PC.
Make sure you are logged onto Windows with a user account that has Administrative rights.
Disable anti-virus software.
If you have a firewall running on your PC, disable it.
If you have a USB or a PCMCIA / PC Card Bluetooth device, please disconnect it. If you have a laptop / notebook or other device with Internal Bluetooth that can be "turned off" please turn it off.
Download and extract the files: Latest ‘generic’ WIDCOMM drivers, v5.0.1.1200 for both Win(x32) & Win(x64) platforms (and is hence 111mB in size). This is latest version of WIDCOMM available (as of 5th December 2005). By using the latest WIDCOMM drivers, the Internet should work on your mobile, almost like the PC, but it depends upon the quality of the Bluetooth Adapter used. The new WIDCOMM driver also enhances the Audio Quality. There are other advantages to using it as well.
Available here: http://www.megaupload.com/?d=DLTT1EFT
Or from here: http://www.megaupload.com/?d=A8EG3C3Y
v2 Patch from here:
http://forum.gsmhosting.com/vbb/show...8&postcount=64


Install Latest WIDCOMM Bluetooth Drivers
To force Windows XP to use the WIDCOMM driver, perform the following steps:

o Don't plug in the Bluetooth device yet.
o Uninstall Any previous Soleil software
o Uninstall Sony Bluespace software
o Uninstall XTNDConnect Blue Manager software
o Uninstall Microsoft Patch Q323183
o Uninstall Any drivers that were supplied with your existing Bluetooth device.
o Uninstall Microsoft IntelliType and IntelliPoint software for Bluetooth mice & Keyboards.

o Also remove and associated programs using Control Panel > Add Remove Programs
o Install the Generic WIDCOMM BT v5.0.1.1200 Bluetooth software (Gotta hit that 'Continue anyway' nag about 50 friggin’' times).
When it asks you to 'plug in the Bluetooth device and click OK', DON'T, click 'Cancel' instead. When done hit 'Finished'.
o When the WIDCOMM setup has finished, plug in your Bluetooth device and let Windows install the driver. (There should be two Bluetooth icons in the system tray; one blue-white and the other blue red (i.e. deactivated).
o Now go to the Device Manager > Expand the Bluetooth Radios tree: right click on the "Generic Bluetooth Radio" and select "update
driver". Don't let Windows XP connect to the internet, then select 'Choose software from a list'
or specified location". In the next window, select 'Don't search, but select the driver to install'.
o In the next window, activate 'Show compatible hardware' (if it isn't activated already) and
select your manufacturer's driver instead of the "Generic Bluetooth Radio" driver (this is the WinXP one).
o Click next until the new driver is installed.
o Unfortunately the driver software may need a patch (good indication of this is a red instead of white system tray icon ) in order to work with non Broadcom based dongles:

(Thread reference: http://www.gsmhosting.com/vbb/archiv.../t-258449.html )
Download v2 executable licence patch executable from:
http://forum.gsmhosting.com/vbb/show...8&postcount=64

(Or download the patch files from here: http://www.megaupload.com/?d=GBW7GLHW )

Power off the PC, remove the Bluetooth dongle. Restart the PC in safe mode (Press ‘F8’ as the PC boots up) & then run the patch file: ‘WIDCOMM Licence Patcher v2.exe’. The files the patch executable needs to patch are found here:

C:\ Program Files \ WIDCOMM \ Bluetooth Software \ BTStackServer.exe
C:\ Program Files \ WIDCOMM \ Bluetooth Software \ BTTray.exe
C:\ Windows \ System32 \ BTNeighborhood.dll
C:\ Windows \ System32 \ wbtapi.dll

Once successfully patched, replace the dongle & restart the PC as normal.

Don’t know about this next bit, but reference is made to doing this:
One of these files needs altering, open up the file ‘SvcPack.ini’ in a text editor and
add the following lines (after the section of text that starts with the line: ‘SourceName4=btneighborhood.dll’)

SourceName5=btins.dll
DestinationName5=btins.dll
DestinationFolder5=2
DestinationSubFolder5=
OS5=15
CopyOnlyIfExists1=Y

Save & then close the text editor.

It may now be necessary to ‘Start the Bluetooth Device’ by right clicking on the blue system tray icon. Finalize the installation process by clicking on the blue-white desktop icon & following the instructions to configure any PC Services you need over Bluetooth, skip services from other devices.. Now the WIDCOMM system tray icon should be blue-white indicating it is activated and ready to use! Hurrah!!!

Right-click on the blue-white system tray icon: ‘Explore my Bluetooth Places’ and the click on ‘View My Bluetooth Services’

You should see a whole bunch of icons that represent all the services that your PV can provide!!!

>>>>>>>>>>>>>>
>> Right, the PC is now using a good WIDCOMM driver & COM ports below the range of COM9 are available for use. In fact the serial Port on COM4 should be available.
>>>>>>>>>>>>>>


CREATING AN INTERNET SERVICE ON THE PC
Ensure your PC is actually connected to the internet (yes boys & girls, I actually FORGOT to do this bit).
Find some way of accessing the properties for your internet connection:
My preferred way is to right-click on the connected icon for your internet connection, click status, then click properties.
On the advanced tab, click the box that says:
"Allow other network users to connect through this computer's Internet connection"

With Bluetooth (WIDCOMM drivers) up & Running on the PC
Right click on the blue Bluetooth task bar icon > Advanced Configuration:
General (tab): Your PC should have a name (e.g. HOME-XP-PC) & a type.
Accessibility (tab): tick: 'Let other Bluetooth devices connect to this computer' Allow: All devices.
Discovery (tab): tick 'Look for other devices' (Try experimenting with these settings)
Local Services (tab): Bluetooth Serial Port NOTE THE COM Port Number!!!!!.
Local Services (tab): IF there is no Bluetooth serial port: Click 'Add Serial Device' > COM Port: I Chose COM4
(Note: A lot of people out there suggest using COM9, don't know why, just go with the flow)
Tick: 'Startup Automatically' UNTick: 'Secure Connection'
Client Applications (tab): I added a Bluetooth Serial Port on COM4. (IE a Service FROM the XDA Exec PPC) < not sure if you need this?
Click OK

Now make your internet connection service available on the above COM port:
Clickity-click on the blue Bluetooth task bar icon:
View My Bluetooth services:
Right Click 'My Bluetooth Serial Port' > Enable
(PS PIM = Personal Identification Manager)

NOW CREATE A PARTNERSHIP
Hopefully there are no partnerships, if so remove them.
Turn off the XDA Exec.
Reset the PC.
Fire up ActiveSync:
File > Connection Settings:
Tick: 'Show status on Task Bar'
Tick: 'Allow USB Connections'
Tick: 'Allow Connections to one of the following': COM4 << Hurrah, our PC's Internet service connection on COM4!!!
'This Computer is connected to': The Internet.
Tick: Open ActiveSync when my device connects.
(Do not close ActiveSync 'Connection Settings' window yet

>> The PC is now ready to rock & Roll.

Fire up your XDA Exec PPC.
Turn PDA on & enable Bluetooth on it:
On PDA: Start > Settings > Connections(tab) > Bluetooth (icon): Tick: "Turn on Bluetooth", Tick: "Make this device discoverable to other devices"
COM Ports (tab) > New Incoming Port > Assign a new incoming port on COM9 (i.e. the Bluetooth’d internet service from your PC via ActiveSync!)
Security (tab): I UNTicked Beam Authentication (This is something else I'm sure it does not make a difference).
Devices Tab: Click 'New Partnership...'

Tap to search for your computer on the next screen, and if it doesn't find it straight away, try going into File ... Get Connected on your PC's ActiveSync. I had to try a few times before it found the computer and connected properly, so keep trying.

DONE??
Hopefully now, if you try Internet Explorer on the XDA, it should pick up on your home PC's internet connection.


Phew!

It may not be complete or accurate, but I hope all this helps,

If it's all crap & makes things go wrong, I can only apologise!!

Andy

[daven]

wow. thanks, great guide. but how would you view the files on another mobile phone, e.g K700i from an exec.

[underwurlde]

Hi,

Of course I've not done this, but theoretically I guess it can be done:

First off I'd install a neat little program called VM Net Browser: It's basically Explorer and some :wink:

Then try something like:
Start > Settings > Bluetooth
Create a new bluetooth partnership with phone #2
Once created, on the Xda, tap & hold the new phone partnership name in the Devices (tab)> edit: and tick 'Serial Port' under 'Select Services to use from this device'. Hit refresh...

Perhaps now it will show up in VM Net Browser.

Pure guess work of course but that's a possible avenue to take.

Andy

[daven]

unfortunatly it doesnt work, thanks for your help tho

[underwurlde]

I have since dicovered (even) more issues with regards Bluetooth.

Once you crack it by installing the correct WIDCOMM Bluetooth drivers on your PC, the rest shoud follow.

The Major discovery made was with regards an obscure Microsoft 'tweak' that allows you to see something called 'Ghosted' ports. Also, it was a MAJOR pain in the arse getting hold of LATEST generic WIDCOMM drivers.

Anyway I will update the original stuff above, so look for a big change there in the next couple of mins..

Andy.

PS the only thing I've got to suss now is why my Bluetooth range is utter shite - I mean I go into the next room & I loose the connection! May as well use a fuckin' cable!!!!

[ajacker]

Just as well get a WAG354G and cut out the PC all together!! They are fetching peanuts on ebay these days.