Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Checked in another phone and the current message only has valid ASCII chars, but the ads change over time can't remember if they use non-ASCII chars, guess not.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

i used a "NAM" N900(usa product code)...didnt have the problem...
dialled *2273

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

How to install this?Please help

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

I just thought, that NOKIA would include ussd in their firmware (I just don't know when). So dial pad would be unneeded. But command line tool and widget should still be useful.
May be the package should be combination of command line tool which does everything and different style gui: application and widget?
P.S. I didn't knew, that last number in reply is encoding number. I just found in internet how to decode messages from russian operators. My version works with UCS-2 encoding.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Yes, they plan to include USSD in the firmware, but apparently not yet in the next release. Not all numbers with * and # are USSD. Some are said to work in the next firmware release, but not yet USSD codes.

How is the garage project registration doing? Having a common SVN would be best to join efforts. :)

Learned so yesterday, too. It's two nibbles (4 bits). high nibble tells about the used alphabet and compression stuff while the low nibble tells about the language. I found these PDFs to be useful:

http://www.mobilecity.cz/doc/GSM_03.38_5.3.0.pdf
http://buildhost.automated.it/refere...cs/atnokia.pdf

There may still be some timing issues in the pexpect stuff because I don't always see an response from my carrier.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Download the .deb file and put in "N900" (real path is /home/user/MyDocs/ but the N900 hides this from the user, and just names it "N900" in the file dialogs).

Open the application manager and look for rootsh, install it.

Quit the application manager. This step is important.

Start X-Terminal.

Enter exactly like this and don't press [Enter] yet:
Then push on the [Tab] button on the bottom of the screen. This will expand the complete filename.

Now press [Enter]. It's installing and you will find it in your applications menu from where you can launch it.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Same here, but this happens with all my phones so far, seems that sometimes the carrier sends invalid/empty replies.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Hm, I'm getting RuntimeError: could not create GdkPixmap object errors as a result of an assertion fail right after the MESSAGE line and no other response :) :( Will post the exact output here when I regain connectivity on my N900...

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Yes, I have seen that, too. It's still a little buggy and I think this Runtime error comes from not getting a reply from the carrier. I'm still investigating this.

Re: Missing USSD functionality: N900 can't dial numbers beginning with # or *
 

Here is garage project and my deb
https://garage.maemo.org/frs/?group_id=1219
What is done:
Files are placed in appropriate places (may be excepting config file)
Command line utility which would understand if encoding is 72 (used by Russian operators) and handle it properly. In other case no conversion one.
Home widget - button, which executes query and shows it as a text on it. Pressing button would execute query again.
GUI configuration (press on configure button in layout mode)

Known bugs:
GUI configuration would work after
chmod 777 /etc/ussdWidget.conf
On some systems it would break desktop layout mode: in layout mode pressing on menu which normally sujjests what to add to desktop would stop working. The same code on my device works. I think, that some dependences are missing.