Unfortunately the rs232 port (that the USB cradle uses) is in use by system services all the time. Either the PC suite client (mRouter client) tries to connect to the PC suite through it (this is when you set the control panel->Cable to PC), or the modem command parser is listening on it (when you set the port to Modem). There is no way to programmatically kill any of these services and free up the port for dial-out.

However, there is a special AT command that terminates the modem command parser (it is AT*ESYN=3). Unfortunately this has to be externally issued. Afterwards it is fairly simple to set up the connection. Unfortunately this command is not always available. A firmware update could help (P800 users may definitely need it).

Instructions for windows

• Go to the phone control panel, connections tab, Cable, and set it to 'modem'. You should choose 460800 baud (8 databit, no parity, 1 stopbit, CTS/RTS flow control).
• Connect the USB cradle to your computer. Right click the PC suite icon, go to the Properties, and uncheck the COM port for the USB cradle. (Note the port, e.g. COM8.)
• Put your phone into the cradle.
• Launch HyperTerminal, select 'Direct COM8', configure the port settings to 460800 baud, (8 databit, no parity, 1 stopbit, hardware flow control).
• Now if you type the command 'AT' (without the quotes, followed by ENTER) into the terminal window, you should see what you type and get a response OK.
• Type the command 'AT*ESYN=3' (without the quotes, followed by ENTER). Again, you should get an OK for response. Now you should not see any more the characters you type in the terminal, and not get an OK response for the command AT. That means you successfully stopped the modem command parser.
• Close HyperTerminal (save the connection prefernces you just set). Go to the properties of PC suite and re-enable the COM port for the USB cradle.

• Launch GnuBox and select 2box Cable.
• Congratulations, you are ready! Set 'Bt' as the default internet connection in your favorite application and enjoy fast&free browsing via the USB Cradle.

Instructions for linux

• Plug in the USB cradle. You should see a new usbserial port appearing. (You will need the usbserial and FTDI FT232 serial converter driver module.) Note the device the driver is attached to (most probably /dev/ttyUSB0 (/dev/usb/tts/0 if you have devfs) if you have no more USBserial devices)
• Go to the phone control panel, connections tab, Cable, and set it to 'modem'. You should choose 460800 baud (8 databit, no parity, 1 stopbit, CTS/RTS flow control). Put the phone into the cradle.
• Fire up your favorite modem application (like minicom) on /dev/ttyUSB0, baud 460800, 8N1, and issue the modem commands seen in the windows section.
• In the Bluetooth linux instructions do the internet connectio sharing setup (two commands like 'echo 1 > /proc/...' and 'iptables -t nat -A ...') and create the file /etc/ppp/peers/dun with the required contents.
• Execute the following command as root:
  
  pppd /dev/ttyUSB0 silent persist call dun
  
  
• Launch GnuBox and select 2box Cable.
• Congratulations, you are ready! Set 'Bt' as the default internet connection in your favorite application and enjoy fast&free browsing via the USB Cradle.

Support and setup instructions for Nokia phones

Thanks to Schuon from the forum for parts of the following tutorial.

You can read the original tutorial by Schuon here. There is another tutorial on the forum by Umit here.

First and most important choice: what software to use on the PC side:

Under windows, the choice is a bit difficult.

• You can use mRouter server on the PC. Even if the client is not installed on your phone. This gives you an alternative that is easy to set up. However, the mRouter server gives the nokia phone an IP address from the range of 169.254.1.x. Nokia phones do not allow the internet gateway to have such an address! Thus they will route no packets that are destined to the internet through your interface. This is true even if the phone has a default route towards that interface. Thus you will only be able to access your own computer from the phone. This is all right if you set up a HTTP proxy server on your computer, and start that proxy. (You can find an HTTP proxy for free.) This will allow you to browse and download things, but it will probably not allow you to use IM applications and possibly e-mail sending-receiving. (Unless you set up custom TCP proxies for that applications.) This proxy setup may be tedious, but at least you can always see what's happening, you can debug the connection, and you'll have a quick success at start.
• You could use WIDCOMM's Network Access server. Unfortunately I have never seen that properly functioning. The phone connects, but no data is transferred. I tried to call it from linux, no success either. It gets stuck somewhere in the PPP setup phase. I have no idea how to get it working. Though it would be a very simple and easy-to-setup possibility! If you know how to get it working (even if it has nothing to do with smartphones, but for example how to call it from linux), post to the forum!
• Finally, the best results you can get is via the Windows XP dialin feature. With this properly set up you can get full, unproxied, unrestricted network access. However, there are some difficulties you have to overcome until that. If you can give the phone an IP address that is valid outside your computer (for example on your office LAN or home network), then you can easily get it up and running with plain IP forwarding on the windows. If you cannot, then you can achieve this the easiest way with buying a broadband router for your internet connection. Finally, it may work with windows Internet Connection Sharing (ICS). But that probably needs the cryptic netsh blahblah... commands that you find in all the other tutorials about GnuBox. Furthermore, this ICS may not work with DSL or dial-up connections, only on ethernet connections.

Basic setup instructions on Nokia for v1.1 beta

1. Create a full backup of your phone. Remember, this is beta stuff. You may need to format your phone if something seriously goes wrong.
2. Install GnuBox. Take the .SIS for your phone in the download section.
3. If you want to enable debugging, create a directory named c:\logs\gnubox. THe detailed event log will appear in this directory if it exists. The log will be named c:\logs\gnubox\gnubox.txt, and the new events will be appended every time you run gnubox. It it gets too big, you can delete it and it will be re-created next time you start something loggable happens.
4. Open GnuBox. Do not mind any errors 'No rec...' you may see on the screen. Select Options|Debug|Dump Full CommsDB. Allow it to run a few (ten) seconds. After it has finished, look for a commsdb.txt in C:\nokia. Copy this file to you phone and save it for future reference. At any stage of the install/operation if you do a new full CommsDb dump and compare the resulting file with this you save now, you will be able to see all changes GnuBox has done to your phone.
5. Exit GnuBox with Options|Exit.
6. Go to the phone control panel and create an internet access point. Name it 'Bt' (without the quotes, take care that case may be significant). Make sure you set it to use 'Data call' as the bearer. (It may be named 'CSD' or 'Dial-up' on your phone. This is the opposite of GPRS.) Set the number to call to something that cannot be called (e.g 321).
7. Start GnuBox. Now you should see on the screen that the DialOutISP record is found, and the phone number you just entered is printed on the screen. However, the ModemBearer should still show 'No rec'.
8. Select Options|Install|Create records
9. Exit gnubox with Options|Exit. (It is not enough to switch to another task and then back to GnuBox.) Start GnuBox again. Now you should see on the screen that the ModemBearer is shown and the 'No rec' error is gone.
10. Create the bluetooth pairing between your phone and the computer. (If you have already used PC suite via bluetooth then this is already done. If you don't know what pairing means and how to do it, refer to the manual of the phone and the bluetooth software/dongle you use on how to pair the PC with the phone and/or how to use PC suite or the phone as a modem via bluetooth connection. Some )
11. Set up your bluetooth software to allow incoming connections for serial port service. This is described in the SE phones section above for the different bluetooth softwares I have seen. Also find out the COM port of the incoming BT connection. Example: under WIDCOMM, go to Advanced configuration (either right-click the bt icon or from the bluetooth menu of my bluetooth places). Select the Local Services tab. Look for Serial port service. Make sure it is set to 'Start automatically'. Set it to require encryption. Mark the COM port written in its line. In the following steps I assume it is COM5.

I will quote something like the adapted versions of those tutorials here, merged with my changes to the application and Schuon's and Umit's experiences from the forum.

Setup instructions for mRouter based method

1. Install mRouter on your PC. You can do so by installing the (separate) mRouter (3 beta) you may find on the internet, or if it is not anymore available (at the time of this writing the production code is not downloadable, but the beta is removed), then install the SonyEricsson PC suite for P910 software, it contains mRouter 3. You can download it from SonyEricsson's website. You won't use the phone related stuff, only the connection manager.
2. Right-click the Phone connector icon on the tray, select Properties. If you have an early version of mRouter (2.x), then you will see a list of COM ports available. Check the COM port that your bluetooth software is listening on (in my case COM5). Close the window. If you have later (3.x) mRouter, then this will be a multi-tab dialog box. On one of the tabs (I forgot which...) you can select which methods to allow for connecting to the phone. Note that you must not allow bluetooth connection. You have to find an advanced button to select that COM port to accept connections. Afterwards the list of connection methods will include COM ports and under that your COM port (COM5 in my case).
3. Install a proxy server on your computer. Note the port it is installed on! (for example 3128). On the phone set the connection to use a proxy. For proxy host set 'wsockhost.mrouter' or '169.254.1.68', and set the port properly. You may need to set this in the browser application (NetFront or Opera).
4. On the phone make sure bluetooth is enabled (discoverable is not needed). Launch GnuBox and select 2box bluetooth->Serial port. On the upcoming device selection dialog, select your computer, and in the question about encryption click Yes (or OK if you only have that).
5. Enjoy browsing the web. (Use the access point 'Bt' to connect to.)

Setup instructions for the Windows dialin based method

1. On the computer go to Control Panel->Telephone and Modem settings. Select Modems tab. Click Add... Select 'Do not detect my modem. I will select it from a list.' Click Next.
2. Select 'Standard modem types' on the left and select 'Serial communication cable between two computers' on the right. Click Next. Select your bluetooth port (COM5 in my case). Click Finish.
3. Create a new user. The name is unimportant ('btdialin' for example). Assign it a password. On the phone open the properties of the connection Bt, and set the username and the password to what you have just created. Save the connection settings. If you do not want a normal user to be created, you will have the chance in the next point to create the user only for the dialin (this is recommended).
4. On the computer go to Control Panel->Network connections. Click 'Create new connection'. Select Next, then 'Create a special connection', then on the next page select 'Accept incoming connections'. In the following page check the 'Communication cable... (COMx)' modem you have just created (at me its on COM5). Then deny VPN connections. On the following page check that particular user you have just created (or much rather create a user here just for this purpose). (Alternatively you need no username/password if you check the box allow local users to access the computer without a password.)
5. On the following page click TCP/IP and click Properties. Select 'The caller may access the local area network'. If there is a DHCP server on the network, you can either use DHCP to assign IP address to the phone. Alternatively you can set an address range manually. Make sure it works on the network you are connected to. (e.g. if you have a broadband router that assigns addresses with DHCP then you are just fine. If you assign addresses manually, e.g. your computer has an address like 192.168.0.4 then setting a range like 192.168.0.110-192.168.0.120 is fairly safe. In the case when you manually set the addresses, you may need to set the DNS server address on the phone control panel (in the properties of accesspoint Bt) to the DNS address of your provider.) Close this dialog box, then click Next and Finish.
6. Activate routing on your computer. Open up the Registry editor by clicking Start -< Run and type 'regedit' (without quotes) then OK. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters . Here you'll have to change the value of 'IPEnableRouter' from 0 to 1. (If there is no such element, select Edit|New|doubleword value or DWORD value. Enter the name 'IPEnableRouter' (without quotes, take care for capital letters) and a single 1 in the value field.) Reboot your machine to apply the settings!
7. Now go to the phone, launch GnuBox. Select Install->set RAS login script. Then select 2box bluetooth->Serial port. On the upcoming device selection dialog, select your computer, and in the question about encryption click Yes (or OK if you only have that).
8. Enjoy browsing the web. (Use the access point 'Bt' to connect to.)

• You should set to assign IP addresses manually. Set it to a private range, e.g. 192.168.23.10-192.168.23.20.
• You do not need the registry edit. Instead enable Internet Connection sharing on your internet connection. There may be nontrivial steps, please consult Mika Raento's page (see the links).

Using this gnubox you don't need to do that. The Ericsson phone's telephony server module (ERIGSM -- you see this on the display) dials the phone number specified if it finds any. This is independent from the Port, CSY setting of GnuBox (all it does is to modify this setting). Thus to use your phone with a normal data call, just specify a phone number (in the properties of that access point). GnuBox works hard for you to clear the phone number from the respective field if you select any 2box option.

If this is not the case for you, you can circumvent all GnuBox's settings by choosing 'auto unset modem ID'. (See this question.) Or you can go the old way, and select 1box phone from the GnuBox menu.

Can I use my phone for SMS sending/receiving after using GnuBox?

Can I use my phone for ordinary voice calls after using GnuBox?

I have a Nokia 6600, 7650, 3650, etc. phone!

Due to many requests I have ssen I decided to try and port my changes back to Nokia Series60. I was (mostly) successful. The application has not yet been thoroughly tested though. It is in beta stage, and unfortunately the Nokia phones have a serious limitation that makes install much more troubleful. I compiled a tutorial from many user feedbacks, but as I do not have a Nokia phone, I cannot test it myself.

The instructions and issues are described in the Support and setup instructions for Nokia phones section.

For owners of older Series60 devices:

6600 and 7650 users: go to Mika Raento's page http://www.cs.helsinki.fi/u/mraento/symbian/bt-ap.html

Users of even older devices (Series60 V1, based on Symbian 6.1) may try the original GnuBox found in the CVS. http://www.symbianos.org/cgi-bin/viewcvs.cgi/gnubox/ (look in the attic for .SIS file).

In any case looking at forums (Google for 'gnubox 3650' for example) usually brings up some stuff. If your phone is NOT based on Symbian OS (e.g. Series 40 devices), then GnuBox will never work for you.

I have an unsupported Symbian smartphone!

Support status of 6630, 6680 and 6681

The usage instructions are exactly the same as in any other series60 tutorial, with the following exceptions and limitations:

• You cannot set the accesspoint 'Bt' to Data call when creating. You have only the option 'GPRS'. Set it to GPRS.
• You don't have to enter a phone number while creating the accesspoint.
• If you need to enter DNS or IP address manually, these settings are ignored bu default. You can click on Install|copy from GPRS to activate these settings. Do this only after the entire setup (but for sure after createrecords).
• If you need to set a proxy, make sure you enter this information when you create the accesspoint Bt.
• After clicking Install->Createrecords in gnubox, the accesspoint will disappear from the settings->accesspoint menu. It won't be available anymore. If you need to change proxy or DNS settings, do the following: click install|set to GPRS. Then go to the phone settings|accesspoints, apply the necessary changes. Then go back to gnubox, click install|createrecords. You need then to click install|copy from gprs unless you only changed proxy settings.
• Builtin applications cannot access the accesspoint Bt (and thus use the bluetooth internet connection). The internal accesspoint selection dialog never lists the accesspoint Bt. There are other applications which can use it, including for example IM+, Opera (go to the second page of the settings, select 'Connect to default accesspoint' and select Bt from the list there), putty, vnc client, etc. See the next FAQ entry for application support.

I have a 6630, 6680 or 6681 and my favourite application does not list the accesspoint Bt when I try to use it! How can I use bluetooth internet with it?

One of these inconveniences is that the builtin accesspoint selection dialog shows only the GPRS/3G accesspoints! So when an application tries to access the internet, you cannot select Bt and thus use GnuBox's connection.

While this behavior of the builtin accesspoint selection dialog cannot be modified (it is flashed into the firmware I believe), there are workarounds which might help get an application up and running with the Bt connection.

• In Opera, go to the second page of the settings, set Connection to 'Use default' and then set 'Default connection' to Bt (I have a screenshot about it). Then Opera will use Bt without asking for accesspoints.
• You can initiate the connection with GnuBox via Debug|Bring up IF. If it is up, an application might use it without asking for another to be established (and by this question restricting you to GPRS accesspoints only). So try to click Bring up IF in GnuBox, then launch your application.
• Sometimes an application can memorize which accesspoint you want it to use and use that without question. If you click on Install|set to GPRS, then Bt will appear in the selection dialog (though you won't be able to connect to it, as Bt does not work in GPRS mode). Make your application memorize it and not ask you next time. Then go back to GnuBox, click createrecords (this will switch Bt back to the normal GnuBox operation). Afterwards launching your application might bring up the Bt interface properly. This method works for the builtin Web and RealPlayer apps (in the settings set default conn to Bt).
• Sometimes an application might be set to use the system global default accesspoint without asking you. In this case, you can make Bt to be the global default AP with GnuBox using Install|change default AP. Unfortunately this is currently an irreversible operation. As soon as I can get some time I'll do something to revert it.

It's easier: creating the internet access point 'Bt'.

You may have seen in other guides (for example on Mika's page) that you need to go to special settings and type a login script character-by-character into the respective field.

This is not needed.

The instructions for Nokia phones guide you to use the dial-in connection of windows XP. The dialin connection needs a modem, and they suggest the builtin null modem (Direct cable connection between two PCs). This 'null' modem has a specific initialization sequence that the phone must emulate to successfully dialin.

However, we will use the standard PC suite program, and not the windows XP dialin feature. The PC suite does not need to fake a windows modem which would use this initialization sequence, thus works 'out of the box'.

Why don't I need to specify password in the phone connection settings?

What is 'auto set/unset modem id'? This is not present in other versions of GnuBox!

Devices based on Symbian 7.0 and up can have multiple modems in the MODEM/MODEM_BEARER table of the Communications Database (CommsDb). GnuBox works by modifying the active entry in the MODEM table, so the question is: which is the active entry? Mika's hack has a hard-coded modem name 'Nokia CSD' or something similar. He discovered that his 6600 uses this modem name. Well, SonyEricsson phones obviously have a different modem name, that's why the UIQ ported GnuBox was not working at the first place.

The SymbianOS chooses which entry to use in the CommsDb by two global settings: ModemForPhoneServicesAndSms and ModemForDataAndFax. These could be queried for the active modem ID instead of hardcoding something like 'Nokia CSD'. (By default both of these point to the same modem, id 6, named 'GSM Mobile Phone via cable')

But we only need to change the DataAndFax behavior, and keep everything intact in ModemForPhoneServicesAndSms. Thus we do not modify the default modem entry, instead we set the global setting ModemForDataAndFax to something different, a yet unused modem entry in the MODEM table. (In fact tha name of this unused entry is hardcoded into GnuBox: 'Null Modem 115200bps'.) And modify that entry in the MODEMS table.

This has two advantages: First, we do not break SMS functionality as GnuBox occasionally does (for example on Nokia N-Gage). Second: if we screw up the settings for that unused modem, then everything can be changed back to original by changing ModemForDataAndFax back to the same modem as ModemForPhoneServicesAndSms. That is what 'auto unset modem ID' does. This unset operation circumvents all the changes GnuBox has done, so if something goes wrong, you can get back to normal operation with this. Or you can toggle GnuBox on and off using this instead of '1box phone' and keep the Bluetooth configuration intact.

Note that 'auto set modem id' and 'auto unset modem id', as explained above, is a switch. This switch is independent of the 1box and 2box* settings. Also this switch is persistent, it remains in the same state whenever you restart your phone, etc. Thus it makes no sense to click more than once on 'auto set modem ID' unless you clicked on 'auto unset modem ID'.

Why don't I need to configure Internet Connection Sharing on my computer using the mystic commands 'netsh route...'? Why don't I need to setup direct serial cable and accepting incoming connections?

Once the phone is connected, your computer will have (at least) two network connections: one towards the internet, and another towards the phone. Your computer must forward all the request from the phone connection to the other (and do some address mangling). This can be done by windows ICS on any ordinary network connection.

However, if you connect to PC suite, then the phone connection will be served by Intuwave technology's mRouter server, and completely hidden from windows. Also the connection sharing stuff is done by mRouter, automatically. You will see all the phone's connections as requests originating from 'MRouterRuntime MFC Application' if you have a firewall (of course you have to enable these connections). I must admit, Intuwave did a great job with mRouter.

My firewall shows outgoing connections from 'MRouterRuntime MFC Application'!

Please read the previous question.

What is the difference between Bluetooth->Auto and other entries in the Bluetooth submenu?

The mRouter client software in your phone creates a bluetooth serial port service in the phone. This is used to initate PC suite connection to your phone. If anybody connects to this service using bluetooth, then the connection gets terminated instantly (this is normal), the mRouter client software sets up BTCOMM::0 port to 'callback' to whatever bluetooth device and service just connected. Then it opens BTCOMM::0 thus effectively calling back.

Thus if we use BTCOMM::0 then we do not need to setup the bluetooth communictions. This is easier and this is why it asks no questions about device or encryption. However, the config will be changed by mRouter upon an incoming bluetooth connection to the serial port service! That will be source of problems. Thus using the manual device, service and encryption selection (as required for 'BTCOMM::5') gives more stable results, while Auto selection is quicker but can go wrong time by time. Although it is fairly easy to fix by initiating a PC suite connection (once you recognize that it has gone wrong).

To migrate from Auto to the fixed settings, you should probably choose 2box Bluetooth->Serial port, select your computer and set encryption properly.

Note for later Nokia phones: Nokia has dropped the mRouter based PC suite connection method somewhere after the 6600. If you have a newer phone, then you probably do not even have a Serial port on your phone. This means there is nothing to connect to that would setup BTCOMM::0 to call back to your computer. Thus you can not use the 2box bluetooth->Auto method to connect. You always have to select from the other three 2box BT options and specify the device by hand.

I understand Bluetooth->Auto, but other versions of GnuBox use BTCOMM::0 and still ask the bluetooth device to connect to!

In some other guide for linux I read commands like 'rfcomm bind ...' and 'echo x > /dev/rfcomm...'. Why don't I need them now?

In some other guide for linux I read commands like 'sdptool add ... SP'. Why don't I need them now?

In some other guide for linux I read I need to run the dund command with param --msdun!

Change the etc/ppp/peers/dun file so that you replace 'noauth' with 'auth' , and add a few lines: 'require-pap' or much better 'require-chap' or something like (see 'man pppd'). You should add a line 'name mycomputername'. Then add a line to /etc/ppp/pap-secrets or /etc/ppp/chap-secrets (respectively) reading

myusername mycomputername "mypassword" 192.168.1.2

Set myusername and mypassword on the phone. If you used PAP, you may need to enable clear-text authentication in the special settings. Look at /var/log/debug, /var/log/messages, /var/log/syslog for reasons if the thing is not working. If it is stable and working, you can remove the debug option from /etc/ppp/peers/dun.

Troubleshooting

When I launch GnuBox the display reads

settings...
DialOutISP
  No rec
...

When I launch GnuBox the display reads

settings...
DialOutISP
...
Modem
  No rec

for v1.0 (UIQ) version: Your phone is not supported by this version of GnuBox! The unused modem name is hardcoded (see this question in the FAQ) but it does not exist on your phone. Do a full CommsDb dump and post a message to the forum including:

• What kind of phone do you have
• What Firmware/interface version it has
• An url where we can download your CommsDb dump.

for v1.1 beta (Series60) version: There are two possible reasons:

• The modem record has not been created. Select Options|Install|CreateRecords. Then exit GnuBox with Options|Close. (Note that switching to an other task is not enough! That will not close GnuBox, just force it into the background.)
• It is possible that you did not close GnuBox after clicking CreateRecords. Exit GnuBox with Options|Exit. Then re-start GnuBox. If the problem persists, try to turn your phone off and back on. If the problem still persists, you may try CreateRecords again (it should be safe to click it twice) and do the off-on cycle again. If it still does not go, you may not have the latest release of the SIS installed. If that still does not help, post a bug report on the forum.

My phone dials!

Look at the DefaultTelNum field. It should be empty. If it isn't then you may have gone into the properties of the internet connection Bt and forced to enter a dialup number upon exiting.

Re-select the 2box option you want to use. Afterward the number should be empty and the phone should not dial.

(Are you using the connection 'Bt' for internet access?)

My phone connects via Bluetooth but no data is transferred. The PC suite shows the COM port to be 'Connecting...' but never gets to 'Connected'.

When I connect to Linux using Bluetooth the Bluetooth connection goes up but soon I get 'Unknown error' message.

When I connect using Bluetooth I get a 'Not found' error message.

(Trivial problem: check if you have Bluetooth enabled!)

When I select Bluetooth->Auto I don't get a dialog to select my computer to connect to!

When I first try to connect using bluetooth it asks for pairing (PIN codes), but before I could enter them, the dialog goes away and I get error message.

I want to use PC suite for sync with WIDCOMM but cannot get the callback connection do anything. The phone connector shows Connecting... but never gets Connected.

When you connect to the serial port service on your phone from my bluetooth places, the connection is initiated with no encryption. So the phone learns this, and calls back without encryption. However, the incoming serial port connection on your PC is set to require encryption. Pitfall. The solution is to right-click the phone's serial port service, go to properties, check Encryption, then connect to it. Afterwards the callback will be encrypted and work properly. (Another solution would be to disable encryption on the incoming serial port service, but that is obviously the less secure solution.)

Bluetooth is not working at all! The phone cannot see my computer when trying to Add it in Bluetooth properties, and/or the computer cannot find the phone when searching for devices, and/or the (WIDCOMM) Bluetooth icon shows red (no hardware detected).

If you want to discover the phone from the computer, check 'Allow other devices to discover' on the phone. If you want to connect from the phone to the PC, then check 'Allow discovery' in the Configuration of your bluetooth drivers.

For Cable connection: when I open HyperTerminal and select Direct COM(number) it sais Port is in use and cannot be opened.

For Cable connection: When I open HyperTerminal, the screen gets slowly filled with lots of cryptic characters and/or with '~mRouter - Are you there?~'.

For Cable connection: When I open HyperTerminal and issue the command 'AT' I don't see these letters and get no response.

I used GnuBox over Cable connection. Now when I try using my phone as modem, I get error messages about the modem not responding.

Changelog

• 2004-12-26 17.20 CET:

  I am rewriting the commsdb dump as it currently dies for some reason, but the old code is available.

  I know for sure that it does not work on the UIQ, but I am close to understand why. I also see why some people (with 7.0 symbian smartphone) loose sms functionality after using gnubox. I hope i can avoid the same problem with the uiq version. (And even backport it to nokia.)

• 2004-12-26 17.46 CET:

  I corrected the segfault in the Full CommsDB Dump option. It should now work, and dump _everything_ in the CommsDB. (The old code dumped a hand-selected set of parameters.) The source code and the SIS was updated.

• 2004-12-26 18:48 CET:

  Now I finally reached the point where I can disrupt the operation of the dial-up ISP. The problem remaining is to guess the correct TSY, CSY, Port names. Source code and SIS updated.

• 2004-12-27 19:38 CET:

  I finally found the problem. It is true there is only one available TSY on the P910, that is ERIGSM.TSY. If there is a phone number, this TSY will do a GSM data call on port MUXCOMM::0 indepentently of the Port and CSY setting in the CommsDb. The problem is that gnubox has code for clearing the phone number setting when a "Direct" option is selected, but the system writes "123" instead of the actual empty string. It turned out that upon writing NULL or empty string into a field value, the respective field's value of the default (ID 0) record of table DIAL_OUT_ISP is entered. This is true for any method, I even tried circumventing the CCommsDatabase interface and directly manipulate using sql DML commands. The solution came with zeroing the default entry's telephone number value.

  SO IT NOW WORKS!!! The source and SIS above was updated, but this is a non-release version. See the last point down in the Usage part.

  Why it is not release:
  

  • I need to do a lot of cleanup. For example I have rewritten the bluetooth device selection code twice to avoid the lockups I encountered. (The Bt device selection dialog did not come up except once if you have just restarted the phone.)
  • Also the default entry zeroing code should be added to the Bluetooth Direct option.
  • The default-zero code is pretty ugly, it uses low-level SQL commands. We should be able to do it using the commsdb access.
    
  • I should remove the possibly dangerous options to hand-select the ModemForDataAndFax and ModemForPhoneServicesAndSms options. Also an "Undo set modemID" option could be added that can quickly and easily circumvent any changes gnubox has done to the CommsDb.
• 2004-12-28 17:58 CET:

  I did some of the todo list. I removed the dangerous menu options "manually set modem ID"s. They are in the source though, if you need, re-enable them in gnubox.rss.

  I have rewritten the actual CommsDB write. It was big and ugly. Now all options clean the DefaultTelNo field of the default record, so you should not need to set it to 'Infrared Direct' anymore.

  I also added an "auto unset modem id" option. This resets the ModemForDataAndFax to the hopefully original value that equals to the ModemForPhoneServicesAndSms. This effectively circumvents any changes gnubox has to your modem table (Port, CSY, TSY). Thus it should be possible to quickly disable and enable the changes of gnubox using the "auto set modem id" and "auto unset modem id" options. Though this is probably not needed, as gnubox does not influence your normal data calls (i.e. thosa having a non-empty telephone number field) anymore.

  The debug options were collected into the Debug submenu. The undocumented 'use mRouter' options simply installs a default route to the mRouter connection if it finds any. This is really unnecessary (i just hoped it would make all other changes unneded), but it cannot hurt -- at least a phone reset cancels the effect.

  I did some more testing and found myself being unable to connect to my PC. Looking into the problem it turned out that the bluetooth setup part (which was commented out earlier, remember?) screwed up something and encryption was not turned on properly. Now it works with encryption (hope you can set your computer to support it). The symptom was that the phone brings up the bluetooth connection but no data passes, the Intuwave mRouter server just stayed in the 'Connecting...' state forever.

  I also found out that the Bluetooth Direct and Bluetooth Dialup tries to connect to different profiles of the remote device. (LanAccess server and Bluetooth dial-up networking, respectively.) You can usually bind different com ports to these services on your computer. So you should be able to differentiate in what the phone is trying to do when it connects to your computer. (is it gnubox, or an mrotuer callback, or some remote control application?) This calls for a possible enhancement: select the BT profile by hand, and maybe we should not clinch the telephone number clear/non-clear setting to the BT profile, eh?

• 2004-12-28 21:06 CET:

  Again an update... with two major changes.

  • The bluetooth part now uses port BTCOMM::5. The original BTCOMM::0 interfered with the PC Suite/mRouter setup; any device that connected to the serial port profile of the phone received a callback from mRouter using BTCOMM::0, thus screwed up the configuration of gnubox. Now gnubox is totally independent of what mRouter does. This has advantages: not requiring reconfiguration all the time, but disadvantages: mRouter properly sets up the connection, while we may not...
  • One possible pitfall of setting up the bluetooth connection is encryption. The original code (commented out, remember?) had a bug that made it not to enable encryption. But sometimes encryption cannot be enaled, as the remote end does not expect it. So after the device selection GnuBox now asks if you want encryption or not. Note that PIN authentication is always performed.
• 2004-12-28 23:59 CET:

  Following lots of tests with different bluetooth stacks on windows, i concluded that gnubox _does_ need the possibility to use bluetooth Serial Profile. Thus I restructured the 2box menus. The dialup options went away, as they don't do anything due to ERIGSM.TSY. The infrared (direct) remained as a separate menu, while bluetooth has now three options for three profiles: serial, LANAccess, and dial-up networking. Not that if you were using 2box direct->bluetooth then you need to set it to LanAccess server to get the very same behavior. (Unless your connection was reconfigured by mRouter, in which case you probably want to experiment with bluetooth->serial.) As a rule of thumb, bluetooth->serial is the most probable to work.

  SIS and source updated.

• 2005-01-02 23:00 CET:

  Long since there has been no release :)
  I did a lot of cleaning and rewriting. I eliminated all the huge switches and the phone specific stuff from gnuboxContainer.cpp. All the settings for the different 1box, 2box* things are read from a static array. Thus it should be very easy to change a conneciton mode or add a new mode.

  I added a new connection mode '2box Direct Cable'. Needed a lot of hacking, as the rs232 port (which is used by the usb cradle) is in use all the time - either by mRouterClient or the modem command parser, depending on the setting for 'Cable' in the control panel. The solution is to set it to 'Modem' and issue the command AT*ESYN=3 from the computer. This stops the modem command processor. Thus the port is free, the nontrivial thing is that the rs232 port is called COMM::4, even though ECUART.CSY reports the highest available comm port to be COMM::0. Unfortunately freeing the comm port must be done after each device reset. (reset restarts the modem AT command processor.)

  I added a new connection option to the 2box bluetooth menu, which is direct bluetooth/Auto. It is meant to do the very same thing that Mika's gnubox did for option 2box Direct->Bluetooth. That is, to use the target for the last mRouter connection over bluetooth. This is a bluetooth 'callback', it connects to the last device and service that opened a connection to the bluetooth serial port service on the modem.

  I experimented with the comm port settings. There is now a debug option for dumping serial info.

  All options set the speed of the modem to 460800 bps, whatever modem means (needed for cradle, probably ignored by bluetooth, IR was never working).

  I did some benchmarks. I get practically 460800 bps (something around 38-45 kbytes/sec) on the cradle and bluetooth to my windows WIDCOMM drivers. Strange, but I get half the speed (something like net. 192 kbps) when connecting to linux. However, if I connect from windows WIDCOMM to the very same config of linux, then I again get 460 kbps. No idea why! Cradle on linux yields 460800 bps.

  I had also fairly bad results with the Fujitsu Plugfree bt stack on windows. The data transfer rate was very unstable, ranging from 1 kbyte/sec to 35 kbytes/sec on the small scale, and between 300 kbyte/min and 1000 kbyte/min on 1 minute intervals. This is also very strange!

  I have rewritten this info page thoroughly (until the usage section).

  Source and SIS updated.