Related
In my article Getting the MAC address of your Wi-Fi unit/card, I’ve already elaborated on getting the MAC address of Wi-Fi cards / units in Pocket PC's. Now I’ve received the same question regarding Bluetooth units.
If you have a Widcomm / Broadcomm Bluetooth stack -based device…
Just go to Bluetooth Settings / Accessibility; you’ll see the MAC address right under the “Name” text input field at the top. Examples: PL720; Widcomm-hacked x51v; iPAQ hx4700 and iPAQ 2210.
If you have a Microsoft Bluetooth stack-based device…
Then, it’ll be a bit more complicated because you can’t directly get the BT MAC address of your PDA right on it. This means you’ll need to connect (at least pair with) it to some other Bluetooth device to find out its BT MAC address. In the following section, I discuss all the possible scenarios:
If you have a Widcomm / Broadcomm-based desktop computer, go to Entire Bluetooth Neighborhood (or, if you still haven’t paired your PDA with the computer, Find Bluetooth Devices). There, all BT MAC addresses will be listed. In this screenshot, you can for example see that my Plantronics 590A (the highlighted icon) has the MAC address 00:03:89:5f:60:f1.
If you have another Microsoft BT-stack based desktop OR Pocket PC OR Smartphone device, first, pair it with the MS BT-stack based PDA you’d like to find out its MAC address of, fire up Regedit (on the Pocket PC, for example, Resco Registry Editor – see for a complete overview of all alternatives here) and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Device\. In there, there will be a separate subkey for all your paired Bluetooth devices. For example, with my 590A headset with the MAC address 00:03:89:5f:60:f1, there will be a subkey named 0003895f60f1 (note that it’s generated directly from the MAC address, by just leaving the colons); that is, the entire key name will be as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Device\0003895f60f1]
This means the Plantronics 590 with the MAC address 00:03:89:5f:60:f1 will show up in the Registry like this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Device\0003895f60f1]
"trusted"=dword:00000001
"class"=dword:00240404
"name"="590Plantronics"
If you don’t have many paired BT devices on the other PDA / desktop, then, you’ll find your device very quickly based on this. If you, on the other hand, have many paired devices, check out the “name” String value in each subkey until you find the right one.
Finally, in the Widcomm / Broadcom BT stack running on a Pocket PC, after creating at least one service shortcut to the MS BT stack-based device, tap and hold the icon and select Properties. Then, the device address will be displayed right under the device name.
(Incidentally, in the registry, it’s at both HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devices\ (with all paired BT devices) and, if you you’ve also discovered the services of the device and also created shortcuts to them, you’ll directly see them under HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections\<serial number>.
Examples of this:
Paired devices:
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devices\00:03:89:5f:60:f1]
"LinkKey"=hex:72,F0,08,9D,BD,70,AE,6E,7F,72,4D,75,0D,2F,54,A2
"TimeStamp"=dword:00000000
"Features"=hex:BF,EC,01,00,18,18,00,00
"DevClass"=hex:24,04,04
"Name"=hex:35,39,30,50,6C,61,6E,74,72,6F,6E,69,63,73,00
"TrustedMask"=dword:00000000
Note that “name” is in hex; therefore, with a simply registry export, you won’t easily find it; with a registry editor with hex -> ASCII conversion, you will.
With discovered services (with shortcuts):
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections\0001]
"PluginProfile"="AV"
"Shortcut"="High Quality Audio on 590Plantronics"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000001
"LocalDirectory"="\\My Documents"
"BDName"="590Plantronics"
"BDDevClass"=hex:24,04,04
"BDAddress"=hex:00,03,89,5F,60,F1
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{0000110B-0000-1000-8000-00805F9B34FB}"
"Name"=""
"SecurityId"=dword:00000012
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"UUID"=dword:0000110B)
Great howto but nog applicable for a HTC Wizard.
Any ideas how to do this on a Wizard?
mauce said:
Great howto but nog applicable for a HTC Wizard.
Any ideas how to do this on a Wizard?
Click to expand...
Click to collapse
Please elaborate. You're trying to get the MAC address of a Wizard (you WILL need another BT device to do this), or, are you trying to find the MAC address of another BT device on your Wizard?
Menneisyys said:
Please elaborate. You're trying to get the MAC address of a Wizard (you WILL need another BT device to do this), or, are you trying to find the MAC address of another BT device on your Wizard?
Click to expand...
Click to collapse
Sorry for not being clear.
I'd like to know the BT MAC of the internal BT-device of the wizard.
mauce said:
Sorry for not being clear.
I'd like to know the BT MAC of the internal BT-device of the wizard.
Click to expand...
Click to collapse
Use an external BT device - see the tutorial above. You can't get it directly in the MS BT stack.
Now that there already are some AKU3 devices (mostly MS Smartphones) on the market (for example, the HTC Dash (see for example this excellent Smartphone Thoughts review), and I, as I know quite much about Bluetooth, network sharing (I’m the author of the one and only POST-capable, free HTTP network sharing proxy for the Pocket PC) and connectivity issues of Windows Mobile devices, have been receiving a LOT of related questions (see for example this), I have decided to update my well-known Use your Pocket PC Phone Edition as a modem for your other Pocket PC's” tutorial so that it contains AKU3-related information and to also explain why dial-up connections in the latest, AKU3 version of WM5 behave completely different from earlier operating system versions.
This article will be of extreme interest to anyone using their Microsoft-based phones (let them be either full Pocket PC’s or “just” MS Smartphones) as cellular (GPRS / EDGE / UMTS / HSDPA etc.) modems because it explains everything about this subject, including the changes over the old model.
1. The most important changes, connectivity-wise
There are major changes in the connectivity model of AKU3 when it comes to serving clients that would like to use a Windows Mobile phone as a modem via either Bluetooth or infrared. In the following two subsections, I elaborate on both connection forms.
1.1 Bluetooth: No BT DUN profile any more
In AKU 3+, the Bluetooth DUN (Dial-up Networking) profile is no longer supported at all, only the PAN (Personal Area Network). Now, it’s via BT PAN’s that cellular-only network connections are shared and you have no access to DUN functionality any more.
This means clients discovering AKU3-based Windows Mobile phones will NOT see as modems, unlike with operating system versions prior to AKU3. This means that instead of seeing this (Microsoft BT stack) and this (Widcomm BT stack), you will see this (with the MS BT stack as clients) and this , this and this (three Widcomm-based clients (iPAQ 2210, hx4700 and the Pocket Loox 720)).
The latter screenshots, in essence, show you won’t be able to use Windows Mobile phones with Microsoft BT stack-based clients as the latter have no BT PAN support at all – along with a lot of other types of devices. That is, not so many “client” operating systems (“client” refers to devices that would like to use Windows Mobile phones to access the Net) support the (quite advanced) BT PAN profile as the “traditional” BT DUN dial-up method.
In the following subsections, I elaborate on the PAN compatibility issues both desktop and handheld OS’es. After that, I elaborate on other, related issues like port forwarding and convenience issues.
1.1.1 Desktop OS’es and BT PAN compatibility
On Microsoft Windows desktop PC’s, there is no difference: even the MS BT stack supports joining already-existing BT PAN networks as has been explained, say, here.
On Linux and Mac OS, however, the situation is vastly different: in some cases, only DUN is implemented in some Linux distributions; so is the case with the different Mac OS versions as far as I know as is also pointed out here.
1.1.2. Handheld OS’es and BT PAN compatibility
As far as Pocket PC’s are concerned, the situation here is far worse than that of the desktop Windows case. Here, it’s only the Widcomm/Broadcom BT stack that has always supported BT PAN. The Pocket PC-based Microsoft BT stack doesn’t have any kind of BT PAN client support as can also be seen in this screenshot. This shows PPC MS BT stack clients don’t see any profiles that would make it possible to access the net via AKU3 Phone Edition (or MS Smartphone) devices. Opposed to this is the pre-AKU3 case where DUN was still visible as can be seen in this screenshot (from the already-linked pre-AKU3 article “Use your Pocket PC Phone Edition as a modem for your other Pocket PC's! - a full tutorial”)).
Non-common Bluetooth stacks (like the ones that come with old BT cards – for example, see the original drivers that come with the Belkin F8T020 card – see this for more info) don’t support PAN either (they only support DUN).
Other (non-Windows Mobile) clients that can only use the DUN profile include Palm OS devices (the Palm OS’ BT PAN capabilities are really bad – Lan Access is, theoretically, supported via BT, but not in practice), some (not all! For example, the Sharp Zaurus has BT PAN support) Linux devices (for example, the Nokia 770), some mobile devices with proprietary operating systems (for example, some Garmin GPS units/computers) etc.
1.2. What do you need to know about infrared support?
It, unfortunately, no longer exists in the new Internet Sharing program, as opposed to the old Modem Link.
Right now, on some pre-AKU3 devices like the Wizard (but unlike, say, the Universal, which also has Wireless Modem (WModem)) Modem Link is the only way to use a PPC PE device as a modem over infrared (IrDA). Unlike “traditional”, “dumb” GSM phones, while these devices are also seen as “modems” for other IR devices when Modem Link isn’t active (I’ve elaborated on this, say, here), they can not be used as modems for actual dial-ups without explicitly starting the Windows Mobile phone in infrared modem mode.
The new Internet Sharing only works via USB / BT PAN as can be seen for example in this screenshot of Internet Sharing – the IrCOMM in the drop-down menu is gone, as opposed to that of Modem Link.
By completely abandoning Modem Link, this only way to connect to the outside world via infrared will also be gone. This means you will no longer be able to use AKU3 devices as infrared modems that don’t have additional programs (for example, Wireless Modem) to be used as infrared modems.
Note that some other PPC PE devices (for example, the HTC Universal) have the IrDA-capable WModem, which, currently, is almost the same as Modem Link (except for some fancy receive / send “LEDs”) and, again, still in pre-AKU3 times, seems to be quite redundant (“why double the functionality?”). This redundancy won’t, however, be the case after moving to Internet Sharing (if and when the Universal receives an official AKU3 upgrade) any more, when it’ll be the only phone app with IrDA capabilities.
What’s the point in sticking with IrDA, you may ask? Why not USB or BT instead? The answer is simple: many, for example, Microsoft BT stack-based Pocket PC devices only have IrDA to communicate, even high-end devices like the Dell Axim x51v (if the latter may not use BT DUN any more because of the lack of the BT DUN support in the modem). The same stands for pocket-sized computing platforms like many Palm OS, Linux and Symbian devices – if they contain BT at all, they are unlikely to support PAN.
With the switch to AKU3, none of these non-BT PAN / non-USB-capable clients will be able to access the Net via a PPC PE / MS Smartphone modem any more via infrared either on devices that only have Internet Sharing and not additional connectivity apps like Wmodem.
1.3 Port forwarding issues, running server-side / like apps
With a decent mobile operator (about 20-30% of them are like so; for example, in the UK – see this), which doesn’t use a proxied (“hidden”) networking approach but assigns the connecting client device a “real”, unique, connectable-from-the-outside-world Internet address, you can use so-called “server-side” applications. Don’t be afraid of this, this isn’t geeky stuff: these include absolutely common programs; for example, FTP clients (with non-passive FTP transfers), IRC applications (DCC send from a device only works with server-like devices), RealOne stream playing, incoming remote controller (Pocket Controller, VNC etc) connections etc. Using (or at least trying to use) these are all very common with non-geeks too.
(Please also see this and this for more info on these questions. I also recommend this for a list of what I mean by “server-like” applications on Pocket PC’s – there are quite a few of them which are REALLY useful even on PPC’s, let alone PC’s.)
This means eliminating server-like functionality support on a PC (or even a Pocket PC) connected to the Net via a PPC PE device certainly isn’t welcome. Therefore, it’s a very important question whether a connected Windows Mobile phone forwards all the incoming requests to the connected client, as was the case in pre-AKU3 times.
While Internet Sharing (that is, the new program that makes it possible to share mobile connections with BT PAN clients) doesn’t offer any kind of configurable port forwarding capabilities, unlike the built-in Windows XP Internet Connection Sharing (ICS) I’ve elaborated on several of my ICS-related articles, Microsoft – very wisely! – has paid special attention to properly implement this functionality.
When an AKU3 device shares its Internet connection (over USB, BT PAN and infrared if the given phone has the Wireless Modem / WModem applet), it puts the client to a DMZ (“DeMilitarized Zone”). Then, all incoming requests will be forwarded to the client. I’ve tested this with both playing RealOne streams over GPRS (on a client Pocket PC) and sending DCC files on IRC from client Pocket PC’s and desktop XP’s (to test the USB connection with the latter).
Note that when internet sharing is active, you won’t have server functionality on the phone itself, “only” on the connected client. This is much smaller a problem than the complete lack of using a DMZ (if Microsoft hadn’t implemented port forwarding via using DMZ); with the lack of DMZ’s, no server functionality would be accessible on the client at all. Of course, when you disconnect the client from internet sharing, on the phone, you will be able to use server-side functionality (listening to RealOne streams etc) again. It’s only when Internet Sharing is actively sharing the connection that all incoming connections are auto-forwarded to the client that uses the phone as a modem.
I’ve also tested the DMZ in “leaked” (XDA-Developers) ROM versions (for the Himalaya, Wizard and Universal – click the links for more info). DMZ works with them too via both USB and BT PAN.
1.4 Convenience issues because of the changes in the Bluetooth networking approach
In addition to the above-explained difference in using Windows Mobile-based phones as modems to access the Net, there are some new convenience issues you must be aware of when using AKU3 via Bluetooth (but not via infrared / USB ). These can be pretty annoying if you’ve always liked the “you don’t need to touch the modem at all when you want to dial in to the Internet” in operating system versions prior to AKU3.
Every cloud has a silver lining, though. In some respects, the new, AKU3 connection model is far easier to use through USB. I’ll elaborate on this in the last subsection.
1.4.1 BT convenience issue one: Firing up Network Sharing on the phone
First, let’s have a look at how the old model (prior to AKU3) supported dialing in the Internet via Bluetooth.
When the PPC PE device is used through the standard (pre-AKU3.0) DUN profile, you don’t need to do anything to the PPC. You only start dialing on the client device and it just connects to the Net. (Of course, if you use it via USB or infrared, you must explicitly enable these modes on the Pocket PC in either Modem Link or Wireless Modem, if the latter exists.)
With the new model and the new Internet Sharing, however, the situation is vastly different (again, only when using Bluetooth - with USB / infrared, the situation remained the same as has been before.) You must power on the PDA, fire up Internet Sharing and start the connection by clicking “Connect”. This means a LOT of additional, manual powering up / clicking you didn’t need to do in pre-AKU 3.0 times.
Unfortunately, you must repeat this (power on the phone, go to Internet Sharing and click Connect) every time you’d like to reconnect to the Net on your notebook or other (PAN-compatible) Bluetooth client devices. That is, the “Connected” state changes to an unconnected one as soon as you disconnect the client. In this respect (too), the new model is a bit more inconvenient to use than the old DUN-based one.
1.4.2 BT convenience issue two: Excess clicking needed on the client that uses an AKU3 Windows Mobile via Bluetooth
As BT PAN connections are not treated the same way as BT DUN connections, on clients that use BT PAN to connect to the Net, you
• generally need more clicks to establish the connection, let it be either the desktop Windows or Windows Mobile clients. (Under mobile/desktop Linux clients, in general, you don’t need more clicks.)
• can’t rely on the auto-connect features of the operating systems under desktop and mobile Windows client OS’es. (Unlike under mobile/desktop Linux.)
For example, on desktop Windows, instead of either relying on the auto-connection OR just putting a dial-up link on your desktop (one double-click to start it and, then, just a single click on Dial ), you must (with Widcomm-based clients) click the My Bluetooth Places icon, then, the Entire Bluetooth Neighborhood icon, then, the given device and, finally, the BT PAN icon for the BT PAN connection to be established. (All clicks must be double-clicks!)
(A quick tip: you can reduce the number of clicks needed to fire up the Net connection. To do this, start up Explorer, go to My Bluetooth Places / Entire Bluetooth Neighborhood / the given device and right-click the BT PAN icon; select “Create shortcut”. It will be created – not on the desktop but under My Bluetooth Places. Now, if you just double-click My Bluetooth Places on your desktop, you’ll be able to double-click the new shortcut icon in there as can be seen in here.)
On (Widcomm-based) Windows Mobile clients, you must click the Bluetooth icon on the Today screen, click Bluetooth Manager and double-click the BT PAN icon of the given modem. All this instead of, say, just relying on the auto-connect feature of “real” BT DUN connections. Pretty annoying, eh?
1.4.3 The good: USB is more convenient than before!
In pre-AKU3 operating systems, you must
install the USB modem driver for the phone (and hunt for it if you don’t have it – for your convenience, I’ve mirrored it, along with the HTC dialer app, here should you ever need it) upon the first connection. This is unlike with the pre-AKU3 case, where you must supply USBMDM.INF to it when it prompts for a “Generic Serial” device. In AKU3, upon the first connection, the “Windows Mobile-based Internet Sharing Device” USB driver will be automatically installed by Windows XP
Note that, for this to work, you'll need the latest, 4.5beta2 ActiveSync on your desktop. With earlier AS versions (I've tested this with version 4.1 - it prompted me for the driver for "PocketPC USB Sync"), the driver isn't included (and the Windows auto-update database doesn't contain it either).
the same stands for the HTC dialer (USBModem_Dialer.exe) – you won’t need it at all in AKU3, unlike in previous OS versions. Upon firing up Internet Sharing, starting the USB mode and connecting the USB cable, the client desktop PC will automatically notice the new network. No desktop-side clicking is necessary.
That is, the new, USB-based connectivity schema is far better and more covenient than the old one.
1.5 My wishes…
While the current model is compatible with the majority of desktop Windows-based clients, clients using other operating systems may encounter problems or full inability to access the Net via AKU3 devices because of the…
lack of infrared support in Internet Sharing (as opposed to Modem Link), if the given model doesn’t contain Wireless Modem (or something similar)
lack of USB support on the client side (the case with all non-desktop (mobile) clients (show me a Windows Mobile, Symbian or mobile Linux device with USB host that is also able to use Internet Sharing via USB!) and even Linux or other operating systems on the desktop)
lack of client-side BT PAN support
Therefore, my recommendation for Microsoft is bringing back the DUN profile in addition to keeping the new BT PAN profile. Both have their place under the sun. Use BT PAN with clients that do support it and use the “fallback” DUN with clients that don’t support it or need convenience (see the previous, 1.4 section on the convenience issues on both the client and the phone of the new, PAN-based model).
I also have some other remarks that would make the new approach far more flexible and usable with very little additional coding need. I really hope the excellent folks at Microsoft reimplement DUN in subsequent AKU upgrades and also consider extending the Network Sharing functionality as explained in the following two subsection so that it is able to share any kind of network connections, not only mobile phone-based ones and, at last, offers almost real BT PAN, not only for accessing the Net.
1.5.1 Let’s share any kind of connections, not just mobile phone-based ones!
Internet Sharing could be made MUCH more useful by letting for sharing any kind of connection, not just the ones present in the Connections. Right now, it’s not possible to share for example Wi-Fi connections (a lot of people are asking for Wi-Fi connection sharing all the time; I answer at least one every week). This is a really big problem and could be easily fixed by, for example, just eliminating (or making it optional: if the user only wants to share a given connection and not the current one) the drop-down “Network Connection” menu in the new Internet Sharing applet and just share the current Internet connection, independent of its type.
1.5.2. What do you need to know about the new BT PAN? Can you use it was a REAL Bluetooth PAN network for, say, messaging and playing?
The answer is YES, which is very good news for all MS BT stack users that have long been longing for BT PAN support for its excellent messaging / playing capabilities. Please DO check out my BT PAN-related articles on all these questions; for example, on 4Talk (chat – see this), MS Portrait (chat, file sending) or BT PAN-compatible games (please see the Multiplayer Pocket Game Bible for some examples).
This all means the BT PAN network in AKU3 is a real network as it uses local IP’s (as opposed to DUN) in the network. This means all LAN-based, BT PAN-friendly applications / games work with it as can also be seen in the screenshot I’ve taken with the great multiplayer game Gold Rush (which worked just great over the AKU3 BT PAN – something not possible with pre-AKU3 devices). That is, the basics are already there: it’s just the interface that could be (slightly) modified by Microsoft, of which I’ll elaborate right now.
Unfortunately, the BT PAN support, while it, basically, works, is a bit more limited in AKU3 than in Widcomm-based Pocket PC’s:
You MUST connect to the internet in order to be able to create a BT PAN network between two devices. If you don’t have an Internet connection (or you, for example, supply a connection connecting to a bad APN name), BT PAN won’t work either.
Second, not as important as above, only one client can connect to an AKU3 device, unlike with the Widcomm BT stack, where the number of connecting clients isn’t restricted
AKU3 lacks the BT PAN client mode (so that a AKU3+ device can (also) join BT PAN’s, not (only) host them). This, along with the second bullet, aren’t very important though as can be very easily circumvented (and it’s in very rare cases that you would need a BT PAN network with more than two devices in it – some mass BT PAN multiplayer games like Gold Rush.)
All in all, while the BT PAN, in some respects, does what it’s supposed to (the internet connection sharing does work as expected, except for the convenience and compatibility issues I’ve already elaborated on), the BT PAN support itself could be made independent of “plain” connection sharing. First, making the BT PAN capabilities independent of connection sharing (that is, decouple PAN from Internet Sharing or, at least, make it available for “generic”, non-sharing purposes) would be very nice. The ability to have BT PAN between devices without an actual Internet connection would really enhance the functionality of the BT PAN as there are a LOT of tasks that can be done via local, internet connection-less networks and require no (in cases, non-existing or very expensive) Internet connection. Hope Microsoft also considers this for future AKU versions.
2. Comparison chart
The following chart (only for advanced users / geeks!) compares AKU 3+, pre-AKU3 and Widcomm / Broadcom-based Pocket PC’s (the latter may also have AKU3 – as Bluetooth is not that of Microsoft, with them, the exact AKU version isn’t important) in three areas:
in how they support all (not just plain Internet sharing) the capabilities of BT PAN: can you connect to a given BT PAN server with more than one clients at a time; can you use the given implementation as both a client and a server, is the given BT PAN a “real” PAN network and, finally, is any kind of Internet connection needed for the BT PAN network to work. Note that I’ve already elaborated on all these questions earlier.
dialup-related: how dial-up (accessing the Net from other devices) is done (via DUN or BT PAN); is it possible to use the device as an infrared modem, can you run server-like apps on the client and, finally, is any manual intervention needed for (re)connection (again, in pre-AKU3 times, nope via Bluetooth DUN – this was also a real strength of the DUN-based approach)
internet sharing-related: what protocols work over the sharing (at this, AKU3 really excels as it shares EVERYTHING, as opposed to third-party, non-OS-level solutions used before as is also explained in “Can I share the Internet connection on my Pocket PC through Bluetooth/Wi-Fi? That is, can I make my Internet-connected Pocket PC into some kind of a Wi-Fi/Bluetooth Access Point?”) and the class of collections that can be shared (in this, AKU3’s solution is definitely inferior to “real” ICS, which can share any kind of connection including Wi-Fi, not only mobile phone-based ones.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you can’t see the above chart, the chart is here as HTML
3. Verdict
While the new model exhibits some serious compatibility (and, with Bluetooth connections, convenience) problems, I consider it a very good step in the right direction.
I do hope Microsoft reimplements Bluetooth DUN (which isn't at all complicated because it did exist in previous operating system versions - they will only need to insert back the code used in there) and, preferably, infrared connection in the new Internet Sharing program or, at least, forces Pocket PC manufacturers to supply the Wireless Modem program with all their AKU3 ROM upgrades (also on models that, traditionally, didn't have it - for example, the Wizard) / new models so that infrared dial-in still remains possible.
Also, I hope they go on extending the functionality of Bluetooth PAN so that the Microsoft BT stack, at least BT PAN-wise, becomes a decent alternative to the Widcomm BT stack.
4. Other, recommended links
Use your Pocket PC Phone Edition as a modem for your other Pocket PC's! - a full tutorial - (this explains the pre-AKU3 case)
Can I share the Internet connection on my Pocket PC through Bluetooth/Wi-Fi? That is, can I make my Internet-connected Pocket PC into some kind of a Wi-Fi/Bluetooth Access Point? - this article explains how ICS must be done on pre-AKU3 devices.
UPDATE (11/13/2006): in the meantime, I've scrutinized whether you can "hack" DUN support to the AKU3 MS BT stack with "simple" registry hacking.
Unfortunately, it doesn't seem to be possible for the following reasons:
The subkeys under [HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Bluetooth\ Services] isn't actively used (and can even be deleted) when clients discover the services of a MS BT stack device.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD, which is a dword with the value 00120114 in AKU3 and 00100114 in pre-AKU3 only describe for clients what kind of a BT device is (is it a phone? A PDA? A desktop computer? A headset? Stereo headphones?), and not the services it offers. This means using the old 00100114 as its value in AKU3 won't help either.
It seems the list of the provided services are returned from the BT-related DLL files, which can't be hacked easily.
Feel free to chime in and to point out if you know a way of (re-)enabling the DUN profile under WM5 (without, preferably, getting rid of BT PAN!)
Discussions of this article: HowardForums
Any idea what has to be done to allow linux to use the AKU 3.3 rom's via usb? Theoretically PAND will work under linux but I could never get it to work.
Connecting Fedora Core 6 to the Internet using HTC P3600 Compressed Tutorial
Of course that it will work on any Linux ! Of course that with any WM5 AKU 3 device !
The stages are as simple as 1, 2, 3 !
1. Go (on the WM5 AKU 3.x device) to Internet Sharing, select your network, select BT-PAN profice and click Connect.
2. Open a console on Linux (root) and start writing:
root# pand -s -r PANU
root# pand -Q10
(optional, to test) root# pand -l
root# ifconfig bnep0 192.168.0.2
root# route add default gw 192.168.0.1
root# echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0
3. READY !
Notes upon the implied commands:
a) pand -s -r PANU // starts the PAN daemon (server) in the PANU mode and puts it to listening mode
b) pand -Q10 // performs a 10sec search for the HCI address of a PANU and connects to it
c) pand -l // view if you have connection : bnep0 00:17:83:01:38:6B PANU - in my case
d) ifconfig bnep0 192.168.0.2 // sets the IP of the virtual network interface. Please do veryfy on your PDA that the PAN interface has 192.168.0.1 already seted up. Of course that you can use other IPs, but stay in the same network !
e) route add default gw 192.168.0.1 // sets the WM5 device as the gateway for IP packets. Certainly that you can change the address for originality, but remember that it must be the IP of the PAN interface on the WM5 device !
f) echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0 // assigns a DNS server to be queried. Of course that you can use any DNS IP that you want.
g) REMEMBER: On Fedora, IP forward is already activated. On Debian it is not. Thus, before command number e, you must activate it by typing "echo 1 > /proc/sys/net/ipv4/ip_forward" (without the quotes).
Cheers !
PAN on OS X
It now works in OS X as of 10.4.9! I tested on both my Dulie G5 and my MacBookPro.
Here are the steps I took to make it happen, pretty simple. But it took some playing around to get it.
-----------
Open the Bluetooth Preference Pane, Click Devices, select your device and click Configure.
It will scan your device; Click 'Continue'
It should then display the Conclusion screen that will contain "Use as personal area network"
Click Quit
Click Settings and be sure "Show Bluetooth status in the menu bar" is Checked.
On your WM5 device connect your network using the Internet Sharing application.
Back on your Mac go to the Bluetooth icon in the menu bar, click and select "Join Network on <devicename>"
Your on! Oddly on my Macbook it shows under the Network prefs as a Ethernet Adaptor, but on my G5 it shows as Bluetooth PDA.
Thanks for the update Apple!!
Great! Will post an update to everywhere!
moucha said:
Of course that it will work on any Linux ! Of course that with any WM5 AKU 3 device !
The stages are as simple as 1, 2, 3 !
1. Go (on the WM5 AKU 3.x device) to Internet Sharing, select your network, select BT-PAN profice and click Connect.
2. Open a console on Linux (root) and start writing:
root# pand -s -r PANU
root# pand -Q10
(optional, to test) root# pand -l
root# ifconfig bnep0 192.168.0.2
root# route add default gw 192.168.0.1
root# echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0
3. READY !
Notes upon the implied commands:
a) pand -s -r PANU // starts the PAN daemon (server) in the PANU mode and puts it to listening mode
b) pand -Q10 // performs a 10sec search for the HCI address of a PANU and connects to it
c) pand -l // view if you have connection : bnep0 00:17:83:01:38:6B PANU - in my case
d) ifconfig bnep0 192.168.0.2 // sets the IP of the virtual network interface. Please do veryfy on your PDA that the PAN interface has 192.168.0.1 already seted up. Of course that you can use other IPs, but stay in the same network !
e) route add default gw 192.168.0.1 // sets the WM5 device as the gateway for IP packets. Certainly that you can change the address for originality, but remember that it must be the IP of the PAN interface on the WM5 device !
f) echo "nameserver 194.102.255.2" > /tmp/resolv.conf.bnep0 // assigns a DNS server to be queried. Of course that you can use any DNS IP that you want.
g) REMEMBER: On Fedora, IP forward is already activated. On Debian it is not. Thus, before command number e, you must activate it by typing "echo 1 > /proc/sys/net/ipv4/ip_forward" (without the quotes).
Cheers !
Click to expand...
Click to collapse
What has to be done different to use the direct usb connection under linux? I run suse and was able to get an ip address but could never get it to go to a website.
Thankyou!
Just wanted to post a comment saying thankyou so much for this guide - it's amazing, so detailed and very, very useful!!!
Much appreciated!
I send that - I'm just about to go to AKU3 and use the USB connection method for modem use. Excellent stuff!
USB No worky
I'm having some really strange functionality with the internet sharing on AKU3.5 that I've built and installed on my Verizon XV6700.
I have everything working 100% from the phone side. Picture and video messaging. Internet browsing checking email you name it.
When I fire up Internet Sharing with the Bluetooth PAN option I can connect with my laptop and I'm actually posting this message over Internet Sharing via Bluetooth PAN. But when I use USB no worky.
I'm running Windows Vista Ultimate (so I have the latest and greatest Active Sync). When I plug in Windows DOES detect it as a network card. For the longest time it was only getting a 169.x.x.x IP so it was like it wasn't fining anyone home on the other end. After several iterations of setting my USB from Serial to RNDIS and back again and editing settings in the RNDIS adapter in connections I now have an IP getting correctly configured.
When I was not getting an IP Windows would say that I had "Limited Connectivity" on the network card. Now that there is a good set of IP's I get "Local Only" access. The phone says it has 192.168.1.1 my computer has 192.168.1.100 (its normal local address) but it does have 192.168.1.1 setup as its gateway. All seems correct in there. Essentially it seems like the phone is a firewall and someone forgot to put the MASQ rule in there. Its talking to the phone it just seems like the phone isn't routing the connections outside. Which seems REALLY odd being that BT PAN works so well.
Any insight would be greatly appreciated.
Figures... Right after I post this I figure it out. I've been workin on this for about 2 days now...
When going to start -> settings -> connections -> wifi
then going to the network adapters tab.
I noticed that Bluetooth PAN was in there. It had a use specific IP setting in it to 192.168.0.1 NETMASK 255.255.255.0. My RNDIS adapter was configured to use auto assigned IP's. I just changed the RNDIS to use the same specific IP settings that the BT PAN adapter did and plug and chug.
Click bang whirr and we're up and running!
Speed tests seem to be a little faster with the USB cable. Wonder if the BT connection is a bottleneck with respect to the EVDO connection.
Anyway hope this helps someone....
Problem fixed; see http://forum.xda-developers.com/showthread.php?p=1400709
Menneisyys said:
Unfortunately, the BT PAN support, while it, basically, works, is a bit more limited in AKU3 than in Widcomm-based Pocket PC’s:
You MUST connect to the internet in order to be able to create a BT PAN network between two devices. If you don’t have an Internet connection (or you, for example, supply a connection connecting to a bad APN name), BT PAN won’t work either.
Second, not as important as above, only one client can connect to an AKU3 device, unlike with the Widcomm BT stack, where the number of connecting clients isn’t restricted
AKU3 lacks the BT PAN client mode (so that a AKU3+ device can (also) join BT PAN’s, not (only) host them). This, along with the second bullet, aren’t very important though as can be very easily circumvented (and it’s in very rare cases that you would need a BT PAN network with more than two devices in it – some mass BT PAN multiplayer games like Gold Rush.)
Click to expand...
Click to collapse
sorry for the (probably dumb) question but could you elaborate a little bit on the possible workaround to connect an aku3 device as a BT PAN client to a BT PAN server on another aku3 device ?
Here is the scenario I am interested in : having a HTC Universal (no sim card) connected to the internet thanks to another aku3 device. This other device (probably a smaller device like a HTC Wizard) is connected to the internet through its wan connection and keeps its full internet functionalities.
Thanks !!!
pierro78 said:
sorry for the (probably dumb) question but could you elaborate a little bit on the possible workaround to connect an aku3 device as a BT PAN client to a BT PAN server on another aku3 device ?
Here is the scenario I am interested in : having a HTC Universal (no sim card) connected to the internet thanks to another aku3 device. This other device (probably a smaller device like a HTC Wizard) is connected to the internet through its wan connection and keeps its full internet functionalities.
Thanks !!!
Click to expand...
Click to collapse
I referred to installing the (hacked) Widcomm BT stack (see http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1649&more=1&c=1&tb=1&pb=1 ), which is available for many (but not all!) MS BT stack-based models.
Thanks Menneisys for your answer.
So another (probably also dumb) question :
If I buy an Universal and just want to use it as a PDA connected to the internet through, say, my Wizard. Is there a reliable (& not too hard) way so my Wizard also has full internet features enabled at the same time ??
Thanks again !!!!
PS :
I could go for the N800 which has BT PAN client already integrated but I'd like a keyboard and MS Exchange access ...
pierro78 said:
Thanks Menneisys for your answer.
So another (probably also dumb) question :
If I buy an Universal and just want to use it as a PDA connected to the internet through, say, my Wizard. Is there a reliable (& not too hard) way so my Wizard also has full internet features enabled at the same time ??
Thanks again !!!!
PS :
I could go for the N800 which has BT PAN client already integrated but I'd like a keyboard and MS Exchange access ...
Click to expand...
Click to collapse
So, you need to use Internet Sharing on the Wizard, so that you can also access the Net on it? Then, install the Widcomm hack on the Universal. See http://forum.xda-developers.com/showthread.php?p=1115973
Menneisyys said:
Then, install the Widcomm hack on the Universal. See http://forum.xda-developers.com/showthread.php?p=1115973
Click to expand...
Click to collapse
Awesome, I have missed this thread and didn't know the widcomm hack was so advanced on the Universal
Thanks a bunch !!!!
PS :
Now I just need to go on ebay and buy myself a cheap Universal ...
pierro78 said:
Awesome, I have missed this thread
Click to expand...
Click to collapse
Just make sure you follow all my articles - I've also advertised this thread in several of them
I’ve elaborated on the approach of WM5 AKU3 / WM6 when it comes to internet sharing and dial-up (modem) functionality via Bluetooth (BT). In there, I’ve told the Microsoft folks to decouple at least the server (Network Access Point, NAP) functionality of their BT PAN (Personal Area Network) implementation so that you can connect to a Windows Mobile phone running the MS BT stack even when it doesn’t have an active (mobile) net connection. Again, as with the other hacks of late (true DUN and true Wi-Fi access hack) it was hackers and programmers that implemented this; namely, XDA-Developers user mrpotter, in THIS thread.
The hack is really useful if you need BT PAN functionality. And, you will need it in several scenarios – for example, remote controlling a media player on your desktop PC; remotely accessing its desktop; playing multiplayer games; chatting, speaking over Bluetooth etc. Now that the BT PAN functionality is decoupled from the Internet dial-up access, you can use it on phones that don’t have the latter (because they don’t have a phone card inside, you haven’t subscribed to a cellular Internet plan or don’t want to use any to keep costs down), which is pretty much similar to the case of the Widcomm BT stack. (The Widcomm BT stack has always been vastly superior to the MS one but, alas, almost all current models contain the latter and there are pretty few models that you can “hack” the Widcomm BT stack on.
Compatibility
It’s compatible with all WM6 MS Smartphone (WM Standard) and Pocket PC Phone Edition (WM Professional) devices. It seems it is NOT compatible with WM5 AKU3 devices (that is, late WM5 devices with already Internet Sharing on them). It’s not compatible with non-phone Pocket PC’s either.
Installation, Usage, Hacks
Just download the wm6btpan.exe file from the home XDA-Dev thread (EXE file mirrored HERE), put it anywhere on your phone and start it. After this, any BT PAN-capable client will be able to connect to it, assuming you’ve configured them to receive static IP’s until you reset your phone. (Note that you’ll be able to connect to it even when it’s suspended.)
Doing the latter (that is, giving clients static IP’s) isn’t very complicated. I only explain this for Widcomm-based Pocket PC clients. On post-WM2003 ones (that is, WM2003SE / WM5 / WM6),
Go to Settings / Connections / Network Cards (on WM2003, Settings / Connections / Connections / Advanced / Network Card and, on the latest WM5 AKU3 / WM6 versions, Wi-Fi instead of Network Cards) and click the item in the list that has the word “PAN” in it (WM2003 iPAQ 2210 screenshot, WM5 HP iPAQ hx4700 screenshot). Now, select the “Use specific IP address” radio button and fill in the “IP address” field with an address; for example, 192.168.0.2 or 192.168.0.3. (iPAQ 2210 screenshot). Click the second row (Subnet mask); it’ll be auto-filled as in here (h2210) and here (hx4700). Now, you can connect to your phone.
Note that, should you want to connect more than two devices together (for example, in order to play mass BT PAN-compliant multiplayer games like Great Gold Rush), you will also need to set HKEY_LOCAL_MACHINE\ Comm\BTPAN1\ Parms\ MaxConnections to a higher value; for example, 10. I’ve provided a registry import file accessible HERE for your convenience. I’ve tested the reliability and speed of the BT PAN networks using multiple connections (via Great Gold Rush); encountered no problems, neither with the HTC Wizard (running mfrazzz’s XDA Mobile 6 Release 3) nor the HTC Universal (running WM6) acting as the server for two Widcomm BT PAN clients (the hx4700 and the h2210).
BT PAN client functionality
There are some posts (for example, HERE) asking whether the Registry hacks listed in THIS Registry import file would be sufficient for the phone to be able to connect to PAN networks as clients. The answer is, unfortunately, no. (A quick warning: the above-linked post contains a ServiceId, which might be different in your device (so was in mine). Should you overwrite your original one, you won’t be able to connect to your PAN service any more – that is, only import the file I’ve provided, NOT the one in the linked post.)
Restrictions
Let me present you a list of the restrictions as a summary and quick recap:
there are no dynamic client IP’s, as opposed to the case of using Internet Sharing (which does use DHCP on the server side). That is, if a client connects to a MS BT stack-based BT PAN server, the client must be explicitly defined to use a static IP address. Fortunately, this is a one-time configuration only, requires few taps and has no effect on other ways of connections (as the different network adapters have entirely separate and disjunct IP configurations).
it can only be run on PPC PE and Smartphone devices – no phoneless but MS BT stack-based models like the Dell Axim x51v (or the x50v with the WM5 upgrade) are supported. (Time to install the Widcomm BT stack hack if you haven’t already done so.)
it seems it’s only compatible with WM6 – it refused to start on my official, non-cooked (!) T-Mobile WM5 AKU3.3 Wizard. With mfrazzz’s XDA Mobile 6 Release 3, it worked flawlessly.
Final words
It’s just great! If you’ve ever wanted to use BT PAN, now you can – assuming the other device(s) you try to connect to (all) have BT PAN client capabilities.
Doesn't work on wizard WM6
ROM version: 10.1.0.811 WWE
ROM date: 8/11/06
Radio Version: 02.25.11
Protocol version: 4.1.13.12
Hi. My HTC 8125, flashed as posted up there, doesn't start the wm6btpan application. I have used another wm6 ROM (sorry, didn't write down the ROM data) and a wm5 ROM, but none of them is able to start the application.
Is this application compatible with HTC 8125?.
By the way, The ROM version that I'm using seems to support PAN as a built-in feature.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There you can see that three services are supported by the 8125: DUN, PAN and Voice Gateway
However, I'm unable to stablish a bluetooth PAN via this shortcut, either.
Do you have any idea? Thank you
Try flashing a newer WM6 ROM.
I think you may be on to something here... Cooking your own ROM or OEM cabs may be difficult for the inexperienced. So is identifying the proper content to import into the registry. Nevertheless, tweaked up geeks are also prone to making mistakes. We must especially avoid relying on knowledge of the available tools, resources, etc. without double checking the work of others. Something that worked for one device or associated ROM (official or not) may not work for another. Risk of frying your device is bad enough, but it is especially frustrating when it comes to something like the not having the correct ServiceID! It is not uncommon for the average poster to contribute something without providing sufficient detail. That could have been the information that you were needing. Always start troubleshooting with a clean testbed!
To make matters worse, I have noticed having become either too impatient, incapable of waiting, or both. We all hate how providers like AT&T have had ample time to release their (i607UCGI3) Official WM6 ROM and don't. It may not be worth complaining, but I need to regain the ability to tether my iPAQ/Laptop/GPS back to my handset. After lurking in plenty of the Samsung BlackJack SGH-i607 and HP iPAQ hx4705 forums (namely herekozhura's thread and here 'Blackjack WM6 update on At&t forums!!!') I can attest to the value of a "Do-it-yourself" mentatlity.
I still find myself having to go back to the Embedded portion of MSDN for more!
Menneisyys said:
BT PAN client functionality
There are some posts (for example, HERE) asking whether the Registry hacks listed in THIS Registry import file would be sufficient for the phone to be able to connect to PAN networks as clients. The answer is, unfortunately, no. (A quick warning: the above-linked post contains a ServiceId, which might be different in your device (so was in mine). Should you overwrite your original one, you won’t be able to connect to your PAN service any more – that is, only import the file I’ve provided, NOT the one in the linked post.)
Click to expand...
Click to collapse
I've been in the same boat some time with the hx4705 and the BlackJack, i've gotten it to pair and work for short periods of time in WM6 april i607UGB4.. the good news is someone claims to have i607UGI3 now on HoFo, i'm hoping to be able to walk them through a ROM extraction to get it available to us.
PAN Client working
Menneisyys said:
BT PAN client functionality
There are some posts (for example, HERE) asking whether the Registry hacks listed in THIS Registry import file would be sufficient for the phone to be able to connect to PAN networks as clients. The answer is, unfortunately, no. (A quick warning: the above-linked post contains a ServiceId, which might be different in your device (so was in mine). Should you overwrite your original one, you won’t be able to connect to your PAN service any more – that is, only import the file I’ve provided, NOT the one in the linked post.)
Click to expand...
Click to collapse
I get this to work on Windows XP by using ICS. I can use DHCP on the WM6 client don't even need to setup ip address since ICS takes care of it. Browsing internet w/ Pocket IE is working by this PANU connection.
Steps:
1. Here is the registry on my Tytn II before and after:
Before:
[HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms]
"PublishSdpOnBoot"=dword:1
"MaxConnections"=dword:1
"Description"="Bluetooth NAP Service"
"FriendlyName"="Network Access Point"
"ServiceId"="{00001116-0000-1000-8000-00805f9b34fb}"
"AdapterType"="NAP"
"ProtocolsToBindTo"=multi_sz:"NOT", "NDISUIO"
"AcceptConnections"=dword:1
"ConnectionTimeout"=dword:7530
"BusType"=dword:0
"BusNumber"=dword:0
After:
[HKEY_LOCAL_MACHINE\Comm\BTPAN1\Parms]
"PublishSdpOnBoot"=dword:1
"MaxConnections"=dword:1
"Description"="Bluetooth NAP Service"
"FriendlyName"="Network Access Point"
"ServiceId"="{00001115-0000-1000-8000-00805f9b34fb}"
"AdapterType"="PANU"
"ProtocolsToBindTo"=multi_sz:"NOT"
"AcceptConnections"=dword:1
"ConnectionTimeout"=dword:7530
"BusType"=dword:0
"BusNumber"=dword:0
2. Run the "WM6BTPAN.exe" which can be found here: http://forum.xda-developers.com/showthread.php?t=335125&highlight=PANU
3. On Windows, enable ICS (you will see the drop-down menu if you have more than one selection)
4. Then create the PAN connection thru Windows and you are good to go.
The next questions are:
1. How do we initiate the connections thru WM instead of from PC?
2. How can we make both PANU and NAP co-exist on WM? WM6's ICS require BTPAN1 to be set as NAP in order to work. I create a similar registy entries as [HKEY_LOCAL_MACHINE\Comm\BTPANU1] but does not seem to work.
jackleung said:
The next questions are:
1. How do we initiate the connections thru WM instead of from PC?
Click to expand...
Click to collapse
That's the good question. I can create a network PAN with this software, but the ppc doesn't seem to see this connection as a connection for internet for instance (no icon appears instead of 3G or GPRS as we have when we use the wifi).
How can we resolve this big problem ?
Thank's
yx37 said:
That's the good question. I can create a network PAN with this software, but the ppc doesn't seem to see this connection as a connection for internet for instance (no icon appears instead of 3G or GPRS as we have when we use the wifi).
How can we resolve this big problem ?
Thank's
Click to expand...
Click to collapse
I've the same problem, the bluetooth interface perfectly works, I tested it using vxUtils, but the pda can't recognize it as an internet connection and the programs like internet explorer try to start a gprs connection. I eliminated the gprs connection from the connection manager but the result is "no available internet connection".
I've no idea how to resolve this problem. Someone knowns how?
Hello and thanx for great h4ck, it works for me, well, problem is, i can only initiate connection from my PC using double-click on my PAN adapt. in network connections, it connects like a charm and everything works, PC to PPC and PPC to PC too. I can see PPC PANU Ad-Hoc network service/adapter form my PC
but cant see anything in BT service list in my PPC
any idea how to fix this? So that i can initiate connection from my PPC.
Hi all...
i downloaded wm6btpan and i copied in my storage card, but when i try to launch it it gives me a "text": 120 (and nothing else)
I used the rom found in a post here in the forum...i tryed al the two rom you posted in that thread, but i had the same answer
Now i use my HTC S310 with:
Windows Mobile 6.1
CE OS 5.2.1711 (Build 19202.2.3.0)
Blackdragon_860
Radio version 4.1.13.20_02.41.90
RIL Version 2.002
wm6.1?
any one found a solution for wm6.1 devices? this don't run on my xv6900 or maybe I'm missing something
Hey, I have found a solution for my Xperia X1 (WM6.1) which doesn't need the application to activate the BT PAN.
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\pan]
"ActivateOnBoot"=dword:1
I am new to Windows Mobile, but I'm just curious: why the mobile browsers don't see the connection? I've uploaded PocketPing on my device and it can ping the outside world.
Have You tried to make PAN connection? It's working?
I tried for many hours, but nothing worked.
Is there anyone which played multiplayer games on MS BT stack?
Yes, it works for me. But, again: it is only BT PAN server which is supported. You can only establish a connection from your PC dongle or another device which supports BT PAN client functionality.
So, will it then work with a BTAP?
Sorry, I don't understand what BTAP is
It's working
Wow, I have just tried this registry patch by jackleung, and now I can use my PC's Internet connection on my X1!
xvro said:
Sorry, I don't understand what BTAP is
Click to expand...
Click to collapse
BTAP = Bluetooth Access Point
If you can connect to your phone from BTAP side, it will work. Unfortunately, it won't work the other way round.
xvro said:
If you can connect to your phone from BTAP side, it will work. Unfortunately, it won't work the other way round.
Click to expand...
Click to collapse
Point-2-Multipoint sessions (and this is any Access Point, regardless of WLAN or BT) will only accept connections from client side.
What you are doing is peer-2-peer connections between a PC and a mobile phone, which is different in connection behaviour.
Thus, one cannot establish a session from the access point side, but only from the phone side (client).
Can you please explain, why it should not go the other way round (connecting from client to BTAP), when both parties are talking the same protocoll?
Hi folks,
I'm new to this forum but from what I've seen so far it is very informative. Well this is my first post and I would like to start with a "how do I" question.
I have been using Route66 navigation software on my Omnia i900 with no problems communicating with the phone's internal gps. However, in order to improve satellite reception I would like to use an external bluetooth receiver (Holux M1200). My other gps applications work fine after setting up the baud rate and ports but there are no such settings in the Route66 application.
This what Route66 support said:
I kindly inform you that the ROUTE 66 Navigation software does not offer any options regarding the configuration of an external GPS Bluetooth receiver.
However, all Bluetooth GPS receivers that meet the following requirements can be used with ROUTE 66 navigation software:
- Protocol (minimum): NMEA-0183 v2.0 (RMC)
- Protocol (recommended): NMEA-0183 v2.0 or higher (RMC, GSA, GSV)
- Map datum: WGS84
In order to use the GPS option in the ROUTE 66 navigation software, the GPS device must meet the following requirements:
- The protocol used by the GPS device must be fully NMEA-0183 2.0 (or higher) compatible.
- The minimum protocol requirements are that the RMC and GSA sentences have to be sent.
- The MAP DATUM used in the ROUTE 66 program is WGS-84.
- The baud rate is 4800 - 38400 bps.
I just don't understand where to go from here
Welcome to the forum
As this is an HTC devices only forum you won´t get too much atention.
However there is a thread in off topic section regarding samsung (not sure if your model) but there you´ll have more chances to get help.
Good luck,
Hello,
I am new to the forum and also the owner of an HTC Fuze. I have been playing around recently with the GPS on the phone and got me thinking. I live in NY and we have a CORS network of gps base stations that are fed by the use of ntrip.
I was wondering if their was any way to use the gps signal on my phone and the connection to this CORS network to give me sub inch accuracy on my phone...then not sure what I would do with it then. But I do live on a farm and I would like to see some type of precision agricultural use.
I guess I need a way to have the GPS on the phone talk with the GNSS internet radio and then give me spot on guidance and such.
Please let me know your thoughts or if I need to explain better.
Thanks,
Clayton
bump
bump. Any ideas? Anyone
Great idea cwrisrey !
That will save the cost of a geodetic device, which is many times the cost of a Fuze. Further, it will lead the accuracy of the buildin GPS into millimum class.
Not dig into this further, would you go further to tell these:
Is that CORS data encrypted?
Is that accessible through public internet or VPN?
Is there copy right or intellectuall property right issue involved? (I don't think so, but better make it clear first)
Once again, great idea. Please do remember to update this thread once you got any progress. Thanks.
More info
Hello wg5566,
This site would probably answer alot of your questions clearer than I could:
http://www6.nysdot.gov/spiderweb/frmIndex.aspx
* Is that CORS data encrypted?
-I don't believe so, I think that it is just a form of compression, to distribute across the internet.
* Is that accessible through public internet or VPN?
Yes, the NYS CORS anyway. It accessible from the public internet (although they require you to register with them) But I believe there are other free streams. I also believe it was modeled after being able to be sent threw GPRS.
* Is there copy right or intellectuall property right issue involved? (I don't think so, but better make it clear first)
-I believe the ntrip is based on a GNU, I think the source code is available. http://igs.bkg.bund.de/index_ntrip_down.htm
Windows CE version:
http://www.ilmb.gov.bc.ca/crgb/gsr/downloads/installGNSS.CAB
Please, let me know your thoughts...
Thanks,
Clayton
My fast thoughts:
First make sure there is no satisfied freeware currently available for WM.
If so please ask a moderator to move this to the development & hackings section. And Add tyis sentence on the title: Call for developers for revolutionary GPS app!
I'm sure somebody here can develop this. You know the geodetic device was invented many years ago with very weak profiles comparing to current WM devices. The hardware on our phone should be capable to deal with these calculations, and the WM Pro platform should be capable to support such an app. Anyway it should not be a biggy for many masters here. But it is a biggy for gps users with high accuracy demand for any reason.
Edit: Did you try install that wince cab on your phone? I think some of WINCE apps can just run on WM. Please backup your data first.
Edit2: I tried to install it on my device, at first it did not show up in start menu, then I found the cab just put files and shortcut in the folder names in French. But there is no registry involved in the cab. Only three files. And then program UI itself is in English. Just run the executable from the folder will go right out of the box. So please try it. I did not try to connect & loggin yet, due to not registered account.
Edit3: Looks like the cab is only access the data from internet, convert the data format and export the data, but we still need a geodetic/gps software to process/use the data.
Disclaimer: I attatched these three files for the only purppose of exchanging software developement infomation. Anybody if download it please do not use it for any purppose other than this. Thanx.
Some thoughts on the subject
Hi All,
The idea of using NTRIP to make a Windows Mobile GPS device sub-meter accurate crossed my mind. After some research I found this thread.
Unfortunately, I haven't been able to find any software capable of doing this. My idea is that it should be possible to accomplish this goal, using a combination of existing tools (which would be really cool!).
As wg5566 notes, there is a (WM) tool called GNSS Internet Radio, which is capable of downloading NTRIP corrections. It turns out this software works, but does have some flaws. Someone wrote another open source tool which is better (?), but unfortunately it isn't built for Windows Mobile (see: http://lefebure.com/software/).
More searching revealed a (dead?) project on codeplex: SharpGPS. It's an unfinished demo. It does however seem to be designed to do exactly what we're suggesting in this thread.
My idea: Completing the WM version of SharpGPS with parts of GNSS Internet radio / lefebure NTRIP client should result in a tool that's capable of upgrading a WM devices' gps signal to sub-meter accuracy through RTK/DGPS corrections over NTRIP.
Any ideas / suggestions about this?
It's already been done for the commercial market
Land surveyors, construction companies, and farmers use RTK GPS and RTK GNSS correction services on a regular basis. Some are free and some are paid subscription. They can be either NTRIP protocol with casters or individual TCP or UDP connections. Examples of software available are Carlson SurvCE and MicroSurvey. Read Carlson's support site for how they deal with the data flow using such networks on SurvCE (Windows Mobile and CE).
I have worked in land surveying using such equipment, and it generally requires dual frequency receivers, RTK corrections, and high quality antennas to achieve 1-2cm 95% CI horizontal precision. The current GPS chips in cell phones are only single frequency and so the best you could expect under ideal conditions is 2'-3' precision using some form of differential correction like WAAS or beacon or DGPS via NTRIP. Under average conditions, the precision will likely be in the 10-20' range. The dual frequency receivers take care of the large errors caused by radio waves traveling through the ionosphere.
Due to the limitations of batteries, antennas, and space for more chips in cellphones, the future of location accuracy will likely include some combination of GPS/GLONASS and cellular radio signal frequency timing calculations from cell towers. True Position, with its U-TDOA technology, is one example of measuring the time differences of cell phone radio waves using cell towers with known coordinates. Rumors (from surveying journals) have it that there are current patents in place that can allow for sub foot precision using such methods when sufficient cell towers are present for multilateration.
Has anyone found success on this topic? WM or Android...
Would be very interested, since there is a free NTRIP feed available in Switzerland... anyone?
*bump* it up
Been there still trying. Problem is no carrier phase off internal gps.
Grimli said:
Hi All,
The idea of using NTRIP to make a Windows Mobile GPS device sub-meter accurate crossed my mind. After some research I found this thread.
As wg5566 notes, there is a (WM) tool called GNSS Internet Radio, which is capable of downloading NTRIP corrections. It turns out this software works, but does have some flaws. Someone wrote another open source tool which is better (?), but unfortunately it isn't built for Windows Mobile (see: /lefebure.com/software/).
Click to expand...
Click to collapse
Lance lefebure is a really cool guy I'm sure he wouldn't have any problem building a wm version but it is going to takea lot more than that to get rtk to a cell phone.
Very good ,thanks.
Ed hardy bikini said:
Very good ,thanks.
Click to expand...
Click to collapse
If you are confused just ask questions and I will do my best to answer them. I am in the ag industry and deal with RTK networks and different ways of connecting them and tons of different gps units on a daily basis.
Look at this:
http://stakemill.wordpress.com/2010/07/19/ashtech-mobile-mapper-100-supports-esri-arcpad-10-0/
and this:
http://www.ashtech.com/-2359.kjsp?RH=1272644205746&RF=1270806507068
Is that still a phone !?
wg5566 said:
Look at this:
Is that still a phone !?
Click to expand...
Click to collapse
Nope PDA with support for external GPS with a builtin reciever that even sees glonass satellites (russian constelation). That was made specifically to do RTK mapping. It does have a GSM radio for data to connect to the cors.
Phone positioning using CORS
To perform a CORS (Network Reference correction we need a GGA stream from the GPS in your device. This allows us to remove the anomalies and provde the correction stream. As phones use a sirf II chip or similar they do not have input capability to output the NMEA stream to achieve this.
This one works great! it will connect to an Rtk receiver and get the nmea string from it or will use the internal GPS to be able to register on the CORS network. It will then stream the corrections over Bluetooth to a receiver or even a repeater radio. It won't however correct the internal GPS. http://antrip.dyndns.biz/Home/DownloadTrial