DUN Problem…

My phone pairs with my new N800 (WooHoo) just dandy, however…
My company supplied phone and data plan require the string “s=2” be used as the “Dial-up number”.

When attempting to enter this string in the appropriate dialog box I find that most of the characters on the keypad are grey-ed out. In fact the only letters that can be accessed are the “W” and “P”.

I have tried the simple solutions like cutting and pasting the string from another text dialog, or using handwriting recognition as an alternate input method. Although the needed “s=2” characters are recognized, the DUN dialog box does not accept them.

I am looking for a solution for this dilemma as it is the only hurtle left for me before making the otherwise superb, N800 my preferred, pocket device.

BTW… Please be gentle with me as I am a reasonably intelligent but s-l-o-w learner who has just recently realized what most of you already know… after being M/S’ed with for most of my computer literate life, open source is the way to go.

I do not have a dedicated Linux box yet and was hoping that integrating the N800 into my daily life would be my motivation to do so. I have d’loaded and installed the Maemo VM for my WinTel box from ThoughtFix’s helpful write-up. The VMWare Player with the “ubuntu” guest operating system runs well in XP however, this is as far as I have gotten.

Ok this is just some weird hack that you could possibly fiddle with until someone else comes along who actually uses dial-up DUN (I don't)..
If you have osso-xterm+becomeroot installed and know how to use the 'vi' editor you could try just entering something that's allowed and you will recognize, then look in the file
/etc/osso-af-init/gconf-dir/system/bluetooth/device/xx:yy:zz:xx:yy:zz/%gconf.xml
(where xx:yy.. is your phone's BT mac address).
If you can find the value you just entered you could try substituting it with your s=2 value, save, and see if it'll let you connect. Or, alternatively, it'll brick your device.. see, I told you it was a dubious hack..

Thanks for pointing to that file TA...
I figure I have another 19 days of "Brick insurance" before the purchase return period runs out, ... And, i am not ethically opposed to do doing this (for duty and humanity of course ) because connecting with my phone was one of the reasons that I used to justify the purchase expense.

So now it is the and that are required for me to edit this file

Can you or someone else elaborate on this for me please.

Links would be helpful since I am slow like that.

Ok, I'll try to help.

First of all, you must learn to become root. And once you know that, we'll try to edit the file with vi. So, I'll show you a link, you follow instructions there, and as soon as you're able to become root, please send a post to confirm and we'll go on with the process:
http://sebas-nokia770.blogspot.com/2...nokia-770.html

Salut.
Sebas.

Thanks. I am now @:

/#
in Xterm

Ok, now comes the difficult part. I don't know about DUN stuff, so I'm going to guide you to follow TA-t3 instructions...

As root, type:
# cd /etc/osso-af-init/gconf-dir/system/bluetooth/device/xx:yy:zz:xx:yy:zz/%gconf.xml
(where xx:yy.. is your phone's BT mac address).

It's a ****ing task, but you may get help of TAB'bing. That is, you may type, for example:
# cd /etc/osso-af
and then press TAB at the virtual keyboard, then it automatically displays:
# cd /etc/osso-af-init/

Then you type a little bit more:
# cd /etc/osso-af-init/gc
and then press TAB at the keyboard, then it automatically displays:
# cd /etc/osso-af-init/gconf-d

And so on, till you arrive to:
# cd /etc/osso-af-init/gconf-dir/system/bluetooth/device/

As you may not know your BT mac address, you don't type anything and just press TAB at the keyboard, then it automatically displays two options, one of them is your BT mac address. You just type the first number, for example 1:
# cd /etc/osso-af-init/gconf-dir/system/bluetooth/device/1
and then press TAB at the keyboard, then it automatically displays:
# cd /etc/osso-af-init/gconf-dir/system/bluetooth/device/11\:\22\:33\:44\:55\:66/

Now you type ls, and it displays:
# ls
%gconf.xml

Before editing the file, it would be a good idea to MAKE A BACKUP COPY OF THE FILE (por si las moscas).

To do that, just type:
# cp (without typing ENTER)
then press SPACE, and then press TAB, so that it automatically displays:
# cp \%gconf.xml
now type the name of the backup file:
# cp \%gconf.xml gconf.backup
and now you can tap ENTER, and the file is copied.

IN CASE THINGS GO WRONG, you may restore your backup file typing as root (at the same path where you found the original file via cd):
# cp gconf.backup \%gconf.xml

Notice that "\%" is VERY IMPORTANT.

Now you may safely edit the original file. To do that you must type:
# vi (without typing ENTER)
then press SPACE, and then press TAB, so that it automatically displays:
# vi \%gconf.xml

Now you press ENTER, and vi application starts.

This editor is very simple, and hard to work with at first. You need to navigate over your file. To do that use the arrow buttons to the left (not the virtual keyboard, but the real physical buttons). Up and down arrow buttons let you move to the line you're looking for. Due to how vi works, when you go down a lot of lines in the file, you may notice your xterm screen gets weird. To solve this, press ESCAPE button (to the left of the device: it's the third to the top starting at the bottom, and it's drawn like a circle arrow) several times if needed. No problem, you don't close vi editor with that operation.

More or less at the end of the file you find what I think are the desired lines, where you find the name of the device and DUN options. To change a word in the line, press the arrow buttons till the cursor is over the word you want to change (or add). Remember to press ESCAPE when the screen gets WEIRD.

Then tap "i" into the virtual keyboard. Now you're in INSERT mode. Everything you type is going to be edited into the file.

Now you must use the options of your virtual keyboard, though arrow physical buttons still work for navigating into the file.

Once you have written, changed, or added all you need, you may save your work and close the editor.

To do that, you must FIRST press the ESCAPE (physical) button (several times if you need to be sure), and then tap at your virtual keyboard:
SHIFT : w q ENTER (without spaces and lower-case)
If you think you've done something wrong, just press:
SHIFT : q ! ENTER (without spaces and lower-case)
then vi editor will close without writing to disk. And then start again till you get it.

WOW... Thanks Sebastian. :haveadrin:

I am going to try this in the AM. Good night amigo and thanks again.

In preparing to attempt this bit it occurred to me that I would have to repeat it every time I paired a device that requires this dial up string...

I am currently involved with J2ME development for these iDEN devices and I change phones quite a bit... ( http://www.howardforums.com/showthread.php?t=956723 ).

Can the dialog box itself be hacked to allow access to all the keyboard characters or, more importantly, the edit box allowed to accept these characters?

I don't know, but maybe it's easy to create a shell script to automate that task. Nevertheless you should first show that it actually works

I've been waking up brain cells I haven't used for 15 years, lol.

***

It took me 2 days to figure out that I wasn't inserting a space after "cd"

Everything in your instructions went well until...

when I got to "...../device/" and pressed tab it imediately gave me my mac addy

"# cd /etc/osso-af-init/gconf-dir/system/bluetooth/device/00\:\17\:E2\:49\:CC\:58/"

At the end of that ^ line I typed "ls" then tab…. Then nothing

If I hit enter it gives me:
“/var/lib/gconf-dir/system/bluetooth/device/00\:\17\:E2\:49\:CC\:58/ #”
Then when I type “ls” and TAB I get:
“\%gconf.xml
/var/lib/gconf-dir/system/bluetooth/device/00\:\17\:E2\:49\:CC\:58/ #”

I’m sure I’m doing something wrong and will figure it out eventually (I told you I was slow like that, lol)
...until then any hints or encouragement will be greatly appreciated.

Thanks :haveadrin