One of the BEST hacks of the year: Dial-up Networking Through Bluetooth Under WM5 AKU3 / WM6: at last, it’s WORKING, thanks to X

UPDATE (11/02/2007): There's a version specifically meant for the T-Mo Dash is at http://forum.xda-developers.com/showthread.php?t=340762 . Also, if you have a MS Smartphone (as opposed to a Pocket PC), it MUST be application unlocked for the hack to work. See for example See for example http://www.pocketpcmag.com/blogs/index.php?blog=3&p=2004&more=1&c=1&tb=1&pb=1 for more links on application unlocking. Note that app unlocking is absolutely legal.

UPDATE (10/02/2007): there is an even better, easier-to-install and, what is more, even MS Smartphone (Windows Mobile Standard)-compatible hack. Just download the CAB file linked from THIS post (I’ve also mirrored it HERE, just to be on the safe side, should you not want to register at XDA-Dev to access the download), install it (by simply clicking it on your handheld), power down your device (if it’s a Pocket PC – in order to make sure the Registry changes are all flushed) and restart it.

This hack will add full BT DUN to both platforms. I’ve thoroughly tested it on both my WM6 HTC Universal (a Pocket PC) and WM6 HTC s710 / Vox (a Smartphone) and found it excellent. Note that the traditional, BT PAN-based Internet Sharing will still work alongside with the added BT DUN (tested on both devices).

Note that it has a minor annoyance. After you terminate the connection, you will still be unable to access the Net on the Pocket PC or Smartphone that you used as a modem (also see THIS and THIS for similar bug reports). The solution to this is pretty simple: instead of (lengthy and/or awkward) soft resetting your handheld, just make sure you tap either the data connection icon in Comm Manager (this seem to be sufficient with Smartphones) or, as with, it seems, with Pocket PC’s (like the Universal), just dis- and, then, re-enable the phone connection itself (or, alternatively, en-, and, then, re-disable Flight mode). This all makes this small bug easy to live with.

Finally, Smartphone users: remember NOT to long-press the Red dial button to lock your device – it’ll also terminate the call. Instead, use the standard lock menu accessible via the Power button.

There is also a tutorial on making USB connection work with Modem Link HERE, should it be messed up. Also, the entire thread might be worth giving a read, should you still have problems.

Thanks for FX Belloir for pointing out this hack!

(end of update, the now-outdated original article follows. This means you’ll want to prefer the new hack explained above, NOT the old one I still keep for historical purposes only. It's only the first sections, which explain what this is all about, are worth reading for casual users.)

Anyone having read my article New dial-up networking model of the WM5 AKU3 – a must if you use your WM phones as modems knows WM5 AKU3 (and, of course, WM6) has dramatically changed the way dial-up networking is handled – not necessarily in the good direction. (Please DO read the article if you don’t have a clue what I’m referring to and you have ever wanted to use your Windows Mobile handheld as a cellular modem!)

Microsoft, so far, haven’t really done anything to the problem, except for publishing an article (also discussed for example HERE). Therefore, hackers needed to concentrate their forces on solving the problem. After the first failed attempts (for example mine, as is explained in the first-linked article), at last, some excellent XDA-Developers folks have managed to enable this feature with a comparatively easy-to-do hack. I’ve developed the hack further, making it compatible with several handheld models and ROM versions (the previous version available at XDA-Developers doesn’t support the Universal, Wizard and, probably, several other models because it doesn’t do any forced Registry import – it might only be compatible with the P3600.)

The hack makes it possible to use most WM5 AKU3 / WM6 devices in the traditional (pre-WM5 AKU3) DUN dial-up method, in addition to the new, in WM5 AKU3 introduced Internet Sharing.

This means you can use BOTH technologies and can have the advantages of BOTH approaches. With the “traditional” DUN dial-up, you still have the freedom of NOT having to manually start / reconnect Internet Sharing AND the ability to use clients not supporting the BT Personal Area Network (PAN) profile required by the new Internet Sharing. And, as Internet Sharing is still supported, you can still have a real internet sharing approach, making it possible to use the Internet on both the Windows Mobile device acting as a modem and the client that connects to it (and can still have the other goodies Internet Sharing also offers: for example, the accessibility of the phone even with an ongoing Internet session.)

Again, it’s almost impossible to emphasize how important, how revolutional this hack is! If you’ve EVER tried to use your WM5 AKU3 / WM6 Windows Mobile phone as a modem you know Internet Sharing can be a REAL pain in the back, particularly if the client you’d like to use it from doesn’t support BT PAN.

Installation

Import THIS registry import file (via, say, the brand new, EXCELLENT desktop-side Registry editor of SOTI’s Pocket Controller 6) and copy the contents of THIS file to the \Windows directory of your Windows Mobile device. Soft reset your device and voliá: after this, clients discovering the Bluetooth services your device provides will also see it offering the DUN service (in addition to the PAN one) as can also be seen in HERE.

After this, everything will work just great – as in the pre-AKU3 days. Follow for example THIS tutorial on using DUN modems if you don’t know how it’s done.

Problems

  1. It’s incompatible with some HTC Wizard ROM versions, namely, the official AKU 3.3 T-Mobile ROM – see THIS. It, however, has no problems with mfrazzz's XDA Mobile 6 Release 2a Full at all.
  2. It seems it’s incompatible with WM6 MS Smartphones (Windows Mobile Standard). I’ve tested this on my HTC Vox (S710).

Compatibility

In my tests, it worked just great on my HTC Universal and HTC Wizard. A lot of people have reported other success stories; for example, with the AKU3 HTC Trinity (P3600).

Verdict

Again and again: if you EVER plan to use your handheld as a modem, this hack is a MUST!

UPDATE (07/29/2007): I've tried to extract the DUN-related files from my WM5 AKU3 HTC Oxygen (s310) smartphone and put them on my WM6 HTC Vox (they are available HERE; I've also provided two Registry import files in the archive. The first, SPRegImp.reg, contains the original S310 Registry contents; the second, SPRegImp2.reg, has a much bigger HKLM\SOFTWARE\ Microsoft\ATCIUI\ Connections section).

Unfortunately, while, as opposed to the original case of trying to apply the PPC files, where not even the DUN service could be discovered, it seems it doesn't work: while the DUN service is already visible (as opposed to the original case using the PPC files), on my Vox, connection attempts fail with the same message as not importing the (original) Registry file on the Pocket PC.

I continue playing with the hack; hope I manage to achieve something. I still give you the extracted files so that you can also experiment with them. It MIGHT be working on your non-Vox Smartphone.

UPDATE (08/28/2007): no solution to the MS Smartphone platform yet. Do NOT apply the patch to them - it will NOT work!

Cross-posted to (might be worth checking out for additional info / discussions!): PPCT, AximSite, XDA-Developers, FirstLoox, BrightHand, HowardForums, SPT, MoDaCo, XDA-Dev - 2.

Will this work on the T-Mobile Wing? The wing is an HTC Hermes from what I understand even though it's predecessor was the Tmobile MDA or HTC Wizard. I've never quite understood the naming conventions and wonder if it will work on my device. Thanks!

Werner Ruotsalainen's picture

I am pretty sure it will

It does not work with O2 Xda Flame

Werner Ruotsalainen's picture

Mikhail, are you sure the registry import was successful (this was a problem with another user, who tried to use the non-Regedit5-compliant PHM Registry Editor which, of course, failed to import them)? Can you check the existence of the imported values?

Yeah! But having some trouble to get it to work. Imported the registry, added the files, soft-reset. Available services now say Dialup Networking. However, when trying to connect, I noticed that it's prepending a "0" in front of the phone #, ie. the phone will say "Connecting 0*99***1#"

Tried re-pairing, but getting same results. Any ideas? Thanks in advance!

Werner Ruotsalainen's picture

This must be a dial-up problem - a 0 is being added as the international dial-out number. Does it work the same with other DUN-based dial-ups (with, for example, "dumb" DUN phones)? How did you configure your client? Is it Windows XP?

Can't get this working on my HP 514 Mobile 6 platform. I think your article explains that this is expected but any news when a Mobile 6 smartphone fix will be available?

Has anyone tried this on a HTC Mogul (Sprint PPC-6800)? If so, thanks for sharing the info! I've never used the default Internet Sharing app in WM6 yet but will give it a shot after this hack.

Hi, Meneisyys
You're really a PocketPC God! Your findings just work fine on my HTC Universal through "Celular Line". Would you know whether there would be any chance for the modem call to go through my embedded Voip provision instead or not?

I have noticed that, although my phone pad shows my Voip provider name, the modem call always go trough my celluar carrier instead, depite the dial plan which should be used when my Voip provider is active.

Thanks anyway.
Best regards.

I have a cingular 8525 with Windows Mobile 6 installed. (ROM 2.15.502.3 and Radio 1.40.30.0)

I believe I followed your suggestions, but I still can't seem to connect to my Nokia 770.

Is my phone one of the ones that may not work?

Thanks

Keep up the good work, tried your sp system out on a samsung I600 but no luck, I hope you can sort this lack of DUN problem out.

Werner Ruotsalainen's picture

JL, did you manage to import the registry file? Are you sure it was imported OK?

Werner Ruotsalainen's picture

Carlos, frankly, I don't know - I've never used non-GPRS dial-up connections on newer devices, only some 8-10 years ago and can't test them either, having no such dial-up subscriptions.

Werner Ruotsalainen's picture

Craig, Paddy: still don't know when MS Smartphone support will be available. Sorry.

Thanks for responding so quickly.

Maybe I didn't import registry file correctly.

I am trying to understand your instructions. You indicated:

Import THIS registry import file (via, say, the brand new, EXCELLENT desktop-side Registry editor of SOTI’s Pocket Controller 6) and copy the contents of THIS file to the \Windows directory of your Windows Mobile device.

I don't quite follow. You're saying import the registry file and copy the content of zipped file to the windows directory mobile device. Import the registry file to where? If you would provide step by step inst. that would be very helpful.

I apologize for not understanding something that should be very obvious.

Thanks again,

JL

Werner Ruotsalainen's picture

JL,

1, get and install Resco File Explorer. Make sure you also install its Registry Editor component.

2, start the latter

3, transfer the provided registry import file to \My Documents

4, select Menu / File / Import and select the registry file

This should work.

PS Doesn't the zipped file contain registry file with diff. values than the registry file that I am supposed to import?

Werner Ruotsalainen's picture

Nope, they are, technically (in the way they're imported / copied) independent. that is, you need to:

1. import the .reg file to the Registry and
2. copy the (decompressed) contents of the .zip file to \Windows

Hi Werner,

Just a quick question is it going to be a case of a hardware problem with the smartphones or just a case of waiting for the service providers to say yes to allowing us to get DUN and the software being written.... I guess what I am trying to saying "Is a DUN hack even possible for smartphones with WM6"

Cheers Paddy

I finally imported the registry file. The problem was that I was using firefox and it gave no option to save or open.

Bad news is that after all that, it still did not work. I get the same message on my Nokia 770 "selected phone does not have services that can be used..."

I tried step by step process offered by xda developers with the same result.

Thanks to Microsoft, I just wasted incalculable # of hours. Hope to see WM6 with dun reinstalled or Nokia 770 update with PAN. It's a shame.

Thanks for all your help.

JL

ps is there any way to reinstall windows mobile 5 that came with 8525 so that I can bring back dun?

Werner Ruotsalainen's picture

Paddy,

1, in general, my approach to this (being DUN, more or less, a "black box" - I haven no access to its source code) is "trial and error". That is, I extract the related files & registry entries from DUN-enabled (older but still WM5) Smartphones and try to make them work on newer ones. This is why it's impossible to say whether I will ever be able to come up with a solution - or not.

2, it's because of the mobile operators' objecting to it that Microsoft is not allowed to release their own version (see their statements confirming this HERE). However, as I'm not a MS employee and, more or less, independent of Microsoft, I'm free to do things unless it's a (C) infringement.

Finally, as I really hate the really restrictive approach many mobile operators take (removing DUN, disabling call recording / answering machine features, removing Wi-Fi support, forcing their users to use their sometimes very buggy cursom ROM's, refusing to give their customers ROM updates, while HTC does etc.), I'm only too pleased NOT to obey their Microsoft-centric rules :)

Werner Ruotsalainen's picture

JL, the fact that your 770 doesn't see any services clearly shows it's not the Registry import that failed.

In general, TRYING to downgrade a ROM can't do any damage. In general, downgrading is very safe. I've done it numerous times when, for example, I needed to downgrade the ROM of my phones to see how a given (previous) ROM version behaved in some respect. That is, nothing will be messed up - unless you use for example external USB hubs or USB cable extenders.

First, give a try to any *official* 8525 ROM. Their installer will complain right at the beginning if you can't downgrade.

If none of the (usable) official ROM's work, you will need to use alternate (not-so-official, "cooked") ROMs. This, however, isn't in any way official and I am not allowed give you any links pointing to these ROM's either.

Hi Werner,

Many thanks to your clear explainations, I am truly glad that you and the folks over XDA forum are trying hard on behalf of all the users who are having hardships with this problem. I wish you every luck in finding the magic solution, if you need a tester for any smart phone updates please feel free contact me via XDA forum or modaco.

Keep up the good work

paddy (macpad)

Has anyone tested this on a Samsung Blackjack?

Has Anyone gotten this to work on a Hermes, TyTN, DoPOD or 8525? (al Hermes models).

I am running a TyTN which was upgraded to WM6 (Black 2.5).

LJ

I just loaded this on the Hermes (HTC TyTN)and it works great! My phone syncs with my TomTom 910 again!

I agree this is the most significant hack in a long time! This was a constant frustration on an otherwise good OS and platform

Thanks!

LJ

A comment in regards to the 7/29/07 update...

I'd love to get DUN working on my Samsung Blackjack. Tried many things, including PDAnet and other hacks. I was excited to see mention of getting this to work on a Smartphone here, but sadly must report that it did not work on my AT&T branded Samsung Blackjack. I will eagerly await some sort of hack to re-enable this. Until then, I'll be sticking with my Samsung Sync that fully supports DUN.

Werner Ruotsalainen's picture

LJ, thaks for reporting this - this means it should work on TyTN's.

I don't know why it, then, didn't work with JL's (see his/her posts above) Cingular 8525 - maybe another Cingulr dumb-down?

This also mean JL should consider flashing his/her TyTN to a non-Cingular ROM. (Of course, the usual "legal" stuff applies here: make sure you don't lose your warranty before flashing, do it on your own responsibility etc.)

Can someone confirm if this works for the Hermes 2 at all?

Thanks!
Nick

Brilliant. Bloody brilliant!!! I was just about to send back my O2 xda-Trion (HTC Hermes) in despair as I use TomTom traffic a lot. This fix worked first time (I didn't need to set up a modem).

I would have happily paid for this!

Werner Ruotsalainen's picture

Dunno about the Hermes 2 compliance. Give it a try. If you feel unsure about it, backup your device first with a capable backup tool (SKTools, Sprite Backup 6 etc.)

Tried it on my HTC MTeoR / Breeze. Unfortunately it doesn't seem to work. Laptop sees only PAN, TomTom sees no DUN... Unfortunately now my Bluetooth Activesync connection doesn't work anymore either, any thoughts?

PS. Can I simply remove the registry entries and the /Windows files I've added? Or do I have to change the registry entries?

Werner Ruotsalainen's picture

Gijs, probably - I haven't tested this.

BTW, did you make a backup before applying the patch?

I know that I should have made a backup... but I haven't. I was too enthousiastic about a possible solution. It would have made life easier to roll back via a backup... any suggestions, besides the obvious "reset to factory defaults"?

Werner Ruotsalainen's picture

Try removing the given files and the Registry entries.

Two questions:

1. Should I remove the whole folder (i.e. select the ATCmdInt folder in HKEY_CURRENT_USER\Software\Microsoft\ATCmdInt and delete it?)

2. Could it be that for some reason the registry entries where not imported properly. i.e. at [HKEY_LOCAL_MACHINE\Software\Microsoft\BTHATCI] the DWORD value is not set and I can find the folders[HKEY_CLASSES_ROOT\atciuiapp and [HKEY_LOCAL_MACHINE\Software\Microsoft\ATCIUI].

I have imported the settings via the Resco file explorer and got the message that it was imported successfully.

Werner Ruotsalainen's picture

I don't think it's because the Registry not havng been imported that DUN doesn't work.

So far, noone has ever managed to make it work on any Smartphone models - with successful registry imports too.

Has anyone tried this on a Palm TREO 700wx????? Thank's

Hi,
Does this hack work on HTC Touch (3450, using WM6).

Thanks !

What is a Hermes 2?

Werner Ruotsalainen's picture

LJ, it's the Kaiser (P4550)

I am delighted with this fiz ( and that's quitte an understatement)

Eddy

Will this work for DUN via USB?
Thank You.

Mike,

It works fine on the PPC-6800. I've now got my TomTom 910 talking to my Mogul thanks to this hack. Thanks Werner!

Fantastic Tutorial

Just set up my TomTom 510 with my XDA Orbit and I can now use Traffic Updates!

Thank you very much indeed!

Werner Ruotsalainen's picture

Guys and gals, a Smartphone-compliant hack is out!

Does the new Smartphone hack work with WM5?

Werner Ruotsalainen's picture

Mario, I couldn't test it as my WM5 Smartphone (the HTC s310 / Oxygen) is a pre-AKU3 one; that is, it uses BT DUN.

Backup your phone (just to be on the safe side - I don't think the CAB file will mess up anything, but it's still the best to have a backup file around), and give it a try.

Well nuts. Doesn't work on WM5 and I don't have much hope of a WM6 upgrade any time soon. :-(

Syndicate content
 

Flash®