Jan Derfinak | 2 Mar 15:27 2008
Picon

Re: AW: gnokii error message

On Sat, 1 Mar 2008, Julian Hagenschulte wrote:

> Is gnokii not correct installed or why don’t I have the libmysql.so file?

Yes, it is incorrectly installed.

jan

-- 
_______________________________________________
gnokii-users mailing list
gnokii-users <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/gnokii-users
Irfan Acar | 5 Mar 17:19 2008
Picon

Bugs in gsm-encoding.c

Hello,

In gnokii-0.6.23/common/gsm-encoding.c, char_def_alphabet_ext_decode() 
should return gsm_default_alphabet[value] instead of '?' in the default 
branch of the switch statement.

See the note following the GSM 7bit default alphabet extension table in 
GSM 03.38 version 7.2.0:

"In the event that an MS receives a code where a symbol is not 
represented in the above table then the MS shall display the character 
shown in the main default 7 bit alphabet table in section 6.2.1"

Also, the following case should be added to the switch statement:

	case 0x1B: return ' ';  break;

See Note 1 following the GSM 7bit default alphabet extension table in 
GSM 03.38 version 7.2.0:

"This code value is reserved for the extension to another extension 
table.  On receipt of this code, a receiving entity shall display a 
space until another extension table is defined."

-irfan
Andreas Siegert | 7 Mar 10:37 2008

Workarounds for Nokia 6120 classic address book access

Hi,

my old 6310i suddenly died, got a 6120Classic as a replacement.
I do have the old phonebook in an ascii file from xgnokii.

As the 6120c is not working with Gnokii according to what I could see in
the archves, I am looking for hints on how to get my old phonebook into
the new phone. 
Any pointers/how-tos appreciated.

thx
afx
--

-- 
atsec information security GmbH, Steinstrasse 70, D-81667 Muenchen, Germany
      Phone: +49-89-44249830  /  Fax: +49-89-44249831  /  Web: atsec.com
          HRB: 129439 (Amtsgericht München)   /   Geschäftsführer:
    Salvatore la Pietra, Staffan Persson, Christian Wahl, Martin Freiss
Pawel Kot | 8 Mar 00:36 2008
Picon

Re: Workarounds for Nokia 6120 classic address book access

Hi,

On Fri, Mar 7, 2008 at 10:37 AM, Andreas Siegert <afxml <at> atsec.com> wrote:
> Hi,
>
>  my old 6310i suddenly died, got a 6120Classic as a replacement.
>  I do have the old phonebook in an ascii file from xgnokii.
>
>  As the 6120c is not working with Gnokii according to what I could see in
>  the archves, I am looking for hints on how to get my old phonebook into
>  the new phone.
>  Any pointers/how-tos appreciated.

IMHO the best option would be to use opensync capabilities. In your
case that would be 2-step process:
1. Convert phonebook backup file into file-sync format (it's vCard
afair, verify against opensync documentation)
2. Use opensync to synchronize phonebook between file-sync and syncml
(your phone should support it) plugins

take care,
pkot
--

-- 
Pawel Kot
Mohammed Abdelalim | 7 Mar 16:13 2008
Picon

Graduation Project


My name is Mohammed Abdelalim and I've a graduation project with the following details:

Testing Pocket (TEMS pocket )
The objective of this project is to develop a software mobile application that can measure and record network air interface parameters (signal strengths from cells, cell ID, etc) and display it. It also has to develop a replay tool for the record files .

Objective:
- Develop software GUI on commercial mobile to be used for testing GSM/UMTS mobile network. It can be connected by Blue tooth GPS (or use mobile based GPS like N95) to give the testing point and record it.
- Display the parameters on Mobile GUI
- Give the user the ability to force the test into cell or SC or technology
- Replay tool is needed to check the recorded data
- Calculate some GSM/UMTS KPIs (Key performance indicators) based on recorded parameters
Network Air Interface parameters required:
Carrier number, MS RX Level in dBm, Received signal quality, MS TX power level, C1 (Path loss criterion, used for cell selection and reselection), RTL (Radio link timeout), Timeslot, Indication of the transmitter status, TMSI (Temporary Mobile Subscriber Identity), Cell identification (Cell ID, Number of cells being used), MCC (Mobile country code), MCN (Mobile network code), LAC (Location area code), Ciphering (On/Off), Hopping (On/Off), DTX (On/Off), Discard cell barred information.

Commercial Programs looks like our project:

TEMS Pocket: (SonyEricsson Phones)
TEMS Pocket is the most advanced and powerful hand-held tool on the market for verification, maintenance, and troubleshooting of mobile networks as well as for basic cell planning tasks. Its new design is able to serve on several technologies and markets covering GSM/GPRS/EDGE and WCDMA. Website: http://www.ericsson.com/solutions/tems/realtime_diagnostics/pocket.shtml
 
Nemo Handy: (Nokia phones)
Nemo Handy 2.40 introduces support for the Nokia N95 US edition. Nemo Handy 2.40 features also a base station information display, measurement file upload via Bluetooth, time synchronization based on GPS, detected set measurements with N95 and N95 US, and conditional scripting with the application's integrated script editor. Nokia N95 US operates on WCDMA 850/1900 MHz and GSM 850/900/1800/1900 MHz frequency bands. Website: http://www.anite.com/network-measurement-news/nemo-handy-2.40-with-support-for-nokia-n95-us-rel.html?Itemid=62

NETWORK MONITOR
There is a hidden menu inside your Nokia phone. If you want to activate it, you'll have to re-program some chips inside of your phone. There is some technical details about an old version of this program attached in this mail.


Expected Support:
We have tried to reach the desired data using J2ME or Symbian C/C++ languages on Nokia phones but there is no APIs support these data. But your project have already connect to some modem drivers of the handset. So, we hope you to explain these modem drivers and how did you get it.

Finally, the project belongs to Cairo University – Faculty of Engineering graduation projects and it's sponsored by Vodafone.

_______________________________________________
gnokii-users mailing list
gnokii-users <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/gnokii-users
Peter Valdemar Mørch | 8 Mar 20:47 2008
Picon

Can't --writephonebook on Nokia 6500 classic. --getphonebook works and write works on an "older" 6510

Hi,

I've just purchased a new Nokia 6500 classic. When I try to write the
phonebook, I get:

Write FAILED (Command failed.): memory type: Internal memory, loc: 1,
name: Test Contact, number: 1234

Any ideas about what to do now?

Peter

Turning on debug, I get:
...
Writing phonebook entry Test Contact...
Message sent: 0x03 / 0x004e
00 01 00 0b 00 01 01 00 00 10 02 05 00 01 00 00 |
00 00 00 00 00 03 07 00 00 1e ff 18 00 54 00 65 |           ÿ  T e
00 73 00 74 00 20 00 43 00 6f 00 6e 00 74 00 61 |  s t   C o n t a
00 63 00 74 1e 00 00 08 ff 06 00 55 0b 00 00 12 |  c t    ÿ  U
ff 00 00 00 00 08 00 31 00 32 00 33 00 34       | ÿ      1 2 3 4
Message received: 0x03 / 0x000e
01 5c 00 0c 00 01 0f 00 00 08 3d 00 00 00       |  \        =
Received message type 03
response 0x10 error 0x3d
Write FAILED (Command failed.): memory type: Internal memory, loc: 1,
name: Test Contact, number: 1234
Serial device: closing device
...
(see full debug output in link below)

I've tried with model=6510 and model=series40, and the debug output for
these two is exactly the same except for the model= line.

I'm running with 0.6.23 and I'm using this command:
cat testcontact.txt | ./gnokii --writephonebook -f
and testcontact.txt was created with --getphonebook -r on the new phone.
  I then deleted the one contact and tried to save it on the phone.

My previous phone is a 6510, and I *can* --writephonebook the contact
from the 6500 classic to the 6510 phone.

http://demo.capmon.dk/~pvm/nokia6500/ contains: gnokiirc testcontact.txt
6510.debug series40.debug (the last two are almost identical)

--

-- 
Peter Valdemar Mørch
http://www.morch.com
Pawel Kot | 8 Mar 23:43 2008
Picon

Re: Can't --writephonebook on Nokia 6500 classic. --getphonebook works and write works on an "older" 6510

Hi,

On Sat, Mar 8, 2008 at 8:47 PM, Peter Valdemar Mørch
<4ux6as402 <at> sneakemail.com> wrote:
>  I've just purchased a new Nokia 6500 classic. When I try to write the
>  phonebook, I get:
>
>  Write FAILED (Command failed.): memory type: Internal memory, loc: 1,
>  name: Test Contact, number: 1234
>
>  Any ideas about what to do now?

It is really hard to say. There are lot of experiments that can be done:
 - try to save an entry without a number (but for example with the
other subentry type)
 - change the number type
 - read phonebook entry and compare the frame content with the one you
get with failed write request.
These I would say are the first experiments that should be tried.

take care,
pkot
--

-- 
Pawel Kot
Jon Boede | 10 Mar 05:01 2008
Picon

Nokia 2610 vs 6133

We want to be able to have our systems in the data center cry "help" when things go wrong.
 
Gnokii and a cell phone seems like a really good way to do this.  Is this still a true statement?
 
T-Mobile sells the 2610 and the 6133 as entry-level (read: cheap) Nokia phones. 
 
The Gnokii Wiki doesn't list these phones explicitly... does anybody know if they've been tried?  Anybody have a preference? 
 
I'd prefer a cheap cable over BlueTooth -- the 2610 seems like the better bet but the Wiki hints that the 61xx series may have better support.
 
Thanks much,
Jon
_______________________________________________
gnokii-users mailing list
gnokii-users <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/gnokii-users
Pawel Kot | 10 Mar 15:10 2008
Picon

Re: Nokia 2610 vs 6133

Hi,

On Mon, Mar 10, 2008 at 5:01 AM, Jon Boede <jonboede <at> hotmail.com> wrote:
>  I'd prefer a cheap cable over BlueTooth -- the 2610 seems like the better
> bet but the Wiki hints that the 61xx series may have better support.

Where exactly? Besides 6133 is NOT 61xx series.

pkot
--

-- 
Pawel Kot
Peter Valdemar Mørch | 10 Mar 16:24 2008
Picon

Re: Can't --writephonebook on Nokia 6500 classic. --getphonebook works and write works on an "older" 6510

Hi!

Thanks for your answer, Pawel!

Pawel Kot gnokii-at-gmail.com |Lists2| wrote:
> It is really hard to say. There are lot of experiments that can be done:
>  - try to save an entry without a number (but for example with the
> other subentry type)
>  - change the number type
>  - read phonebook entry and compare the frame content with the one you
> get with failed write request.
> These I would say are the first experiments that should be tried.

I think what is going on is that the 6500 has "First Name" and "Last 
Name" fields as well as the contact name. The older 6230i I have only 
has a "Name" field.

I filled out an entry in the 6230i where "Name" is "First Last", no 
number, and email is p <at> njd.ad. When I "--getphonebook ME X Y -r" I get 
this string returned:
First Last;;ME;112;5;8;0;2;p <at> njd.ad

On the new 6500 phone, I created two entries, both without number and 
both with p <at> njd.ad as the email. In one I filled in both first and last 
name, and in the other I only filled out the first name. When I 
"--getphonebook ME X Y -r" I get these strings returned:

First Last;;ME;1;5;70;0;0;First;71;0;0;Last;8;0;3;p <at> njd.ad
First;;ME;2;5;70;0;0;First;8;0;3;p <at> njd.ad

This is the packet containing the First and Last Name (first entry 
above) as recieved from the phone:

Message received: 0x03 / 0x0076
01 5c 00 08 00 01 01 00 00 10 00 05 00 01 00 00 |  \
00 b3 00 00 00 05 08 00 00 18 03 12 00 70 00 40 |  ³           p  <at> 
00 6e 00 6a 00 64 00 2e 00 61 00 64 00 00 07 00 |  n j d . a d
00 1c 3f 16 00 46 00 69 00 72 00 73 00 74 00 20 |   ?  F i r s t
00 4c 00 61 00 73 00 74 00 00 2f 00 00 08 00 3f |  L a s t  /    ?
80 01 46 00 00 14 02 0c 00 46 00 69 00 72 00 73 |   F      F i r s
00 74 00 00 00 00 47 00 00 10 01 0a 00 4c 00 61 |  t    G      L a
00 73 00 74 00 00                               |  s t
Received message type 03

Note the 70 (First Name) and 71 (Last Name) fields that are included in 
the output of the 6500.

Now, when I try to send the first string from the new phone (The one 
with both First and Last name elements), they are not included in the 
Message sent to the phone:

Writing phonebook entry First Last...
Message sent: 0x03 / 0x004e
00 01 00 0b 00 01 01 00 00 10 02 05 00 02 00 00 |
00 00 00 00 00 03 07 00 00 1a ff 14 00 46 00 69 |           ÿ  F i
00 72 00 73 00 74 00 20 00 4c 00 61 00 73 00 74 |  r s t   L a s t
1e 00 00 08 ff 06 00 55 08 00 00 16 ff 10 00 70 |     ÿ  U    ÿ  p
00 40 00 6e 00 6a 00 64 00 2e 00 61 00 64       |   <at>  n j d . a d
Message received: 0x03 / 0x000e
01 5c 00 0c 00 01 0f 00 00 08 3d 00 00 00       |  \        =
Received message type 03
response 0x10 error 0x3d
Write FAILED (Command failed.): memory type: Internal memory, loc: 2, 
name: First Last, number:
Serial device: closing device

So I found the spot where the FirstName and LastName were excluded:

 > diff -wu orig/common/phones/nk6510.c 
gnokii-0.6.23/common/phones/nk6510.c
--- orig/common/phones/nk6510.c 2008-02-15 10:20:58.000000000 +0100
+++ gnokii-0.6.23/common/phones/nk6510.c        2008-03-10 
15:46:11.000000000 +0100
 <at>  <at>  -2472,8 +2472,8  <at>  <at> 
                                 case GN_PHONEBOOK_ENTRY_StateProvince:
                                 case GN_PHONEBOOK_ENTRY_ZipCode:
                                 case GN_PHONEBOOK_ENTRY_Country:
-                               case GN_PHONEBOOK_ENTRY_LastName:
-                               case GN_PHONEBOOK_ENTRY_FirstName:
+                               /* case GN_PHONEBOOK_ENTRY_LastName:
+                               case GN_PHONEBOOK_ENTRY_FirstName: */
                                         break;
                                 case GN_PHONEBOOK_ENTRY_Number:
                                         if (j < i)

And tried again:
Writing phonebook entry First Last...
Message sent: 0x03 / 0x006c
00 01 00 0b 00 01 01 00 00 10 02 05 00 03 00 00 |
00 00 00 00 00 05 07 00 00 1a ff 14 00 46 00 69 |           ÿ  F i
00 72 00 73 00 74 00 20 00 4c 00 61 00 73 00 74 |  r s t   L a s t
1e 00 00 08 ff 06 00 55 46 00 00 10 ff 0a 00 46 |     ÿ  UF   ÿ  F
00 69 00 72 00 73 00 74 47 00 00 0e ff 08 00 4c |  i r s tG   ÿ  L
00 61 00 73 00 74 08 00 00 16 ff 10 00 70 00 40 |  a s t    ÿ  p  <at> 
00 6e 00 6a 00 64 00 2e 00 61 00 64             |  n j d . a d
Message received: 0x03 / 0x000e
01 5c 00 0c 00 01 0f 00 00 08 3d 00 00 00       |  \        =
Received message type 03
response 0x10 error 0x3d
Write FAILED (Command failed.): memory type: Internal memory, loc: 3, 
name: First Last, number:
Serial device: closing device

So now the First and Last name are sent. But, alas, same error.

This is the default clause of the switch statement that gets hit when I 
apply my "patch":

j = strlen(entry->subentries[i].data.number);
j = char_unicode_encode((string + 1), entry->subentries[i].data.number, j);
string[j + 1] = 0;
string[0] = j;
count += PackBlock(entry->subentries[i].entry_type, j + 1, &block, 
string, req + count, GN_PHONEBOOK_ENTRY_MAX_LENGTH - count);

Does that look sound also for first and last name? Does it sound to you 
guys like I'm on the right track?

Any new ideas? Do the FirstName and LastName fields need to be 
"prepared" or massaged somewhere else? Any other ideas?

Also I got it to work with windows under VMWare using the Nokia standard 
software. Is there any way to sniff the bluetooth communication in this 
setup to get a hint about what the right PDU looks like?

Peter

--

-- 
Peter Valdemar Mørch
http://www.morch.com

Gmane