3 <meta name="Author" content="Marcin Wiacek">
\r
4 <meta name="Description" content="NOKIA NetMonitor description (English version)">
\r
5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
\r
6 <meta name="language" content="us">
\r
7 <meta name="revisit-after" content="15 days">
\r
8 <meta name="Robots" content="all">
\r
9 <meta name="KeyWords" content="3110, 9110, GSM, DCS, Nokia, 3210, 5110, 5130, 6110, 6130, 6150, 8810, FAQ, NetMonitor, Marcin, Wiacek, Marcin Wiacek">
\r
10 <title>NetMonitor in Nokia phones (5/7)</title>
\r
11 <link rel="stylesheet" href="../../styl.css" type="text/css">
\r
13 <body bgcolor="#FFFFFF" text="#2B2B69" link="#525FF5" vlink="#525FF5" alink="#2FA030">
\r
15 <font class="drukuj">
\r
16 <p align="RIGHT"><a class="autoremail" href="../../index.htm">Main page</a></p>
\r
18 <center><font color="#1F409F" size=+2 class="tytul">NetMonitor in Nokia phones (5/7)</font>
\r
19 <font class="drukuj">
\r
20 <p><a href="faq_net0.htm">[Part 1]</a><a href="faq_net1.htm">[Part 2]</a><a href="faq_net2.htm">[Part 3]</a><a href="faq_net3.htm">[Part 4]</a><b>[Part 5]</b><a href="faq_net5.htm">[Part 6]</a><a href="faq_net6.htm">[Part 7]</a>
\r
24 <hr noshade width="60%" style="color: #004080" align=center>
\r
27 <font class="drukuj">
\r
29 <li><a href="faq_net0.htm#1"><b>What is it ?</b></a></li>
\r
30 <li><a href="faq_net0.htm#2"><b>Do I need it ?</b></a></li>
\r
31 <li><a href="faq_net0.htm#3"><b>Does my phone use more power with NetMonitor enabled ?</b></a></li>
\r
32 <li><a href="faq_net0.htm#4"><b>How to activate it ?</b></a></li>
\r
33 <li><a href="faq_net0.htm#5"><b>Which NetMonitor version can be activated in my phone ?</b></a></li>
\r
34 <li><a href="faq_net0.htm#6"><b>Does NetMonitor activation void warranty ?</b></a></li>
\r
35 <li><a href="faq_net0.htm#7"><b>NetMonitor menu in my phone has different number than 10. Is it normal ?</b></a></li>
\r
36 <li><a href="faq_net0.htm#8"><b>NetMonitor menu in my phone has 11 number, hovewer previous position has 9 number. Is it normal ?</b></a></li>
\r
37 <li><a href="faq_net0.htm#9"><b>How to use it ?</b></a></li>
\r
38 <li><a href="faq_net0.htm#10"><b>Can I damage my phone ?</b></a></li>
\r
39 <li><a href="faq_net1.htm#11"><b>Glossary</b></a></li>
\r
40 <li><a href="faq_net2.htm#12"><b>Description of the individual tests</b></a></li>
\r
41 <li><a href="faq_net6.htm#13"><b>You can also use a program...</b></a></li>
\r
42 <li><a href="faq_net6.htm#14"><b>Can I use NetMonitor without SIM card inserted, without PIN number entered or when SIM card is not active ?</b></a></li>
\r
43 <li><a href="faq_net6.htm#15"><b>How can I disable NetMonitor ?</b></a></li>
\r
44 <li><a href="faq_net6.htm#16"><b>Do I need to disable NetMonitor before sending my phone to the service ?</b></a></li>
\r
45 <li><a href="faq_net6.htm#17"><b>Is it possible to re-activate NetMonitor after disabling it ?</b></a></li>
\r
46 <li><a href="faq_net6.htm#18"><b>Is NetMonitor available in analog Nokia phones ?</b></a></li>
\r
47 <li><a href="faq_net6.htm#19"><b>Does NetMonitor allow to use phone like broadcast station ?</b></a></li>
\r
48 <li><a href="faq_net6.htm#20"><b>I don't have all described tests in my phone. Why ? Can I increase their number ?</b></a></li>
\r
49 <li><a href="faq_net6.htm#21"><b>Does NetMonitor allow to identify place, where is my interlocutor ?</b></a></li>
\r
50 <li><a href="faq_net6.htm#22"><b>Does NetMonitor allow to identify place, where am I ?</b></a></li>
\r
51 <li><a href="faq_net6.htm#23"><b>What are NetMonitor codes ?</b></a></li>
\r
52 <li><a href="faq_net6.htm#24"><b>Is it the truth, that in phones with additional hardware changing frequency band NetMonitor doesn't work correct ?</b></a></li>
\r
53 <li><a href="faq_net6.htm#25"><b>Where can I find description of FBUS/MBUS protocol and commands connected with NetMonitor ?</b></a></li>
\r
54 <li><a href="faq_net6.htm#26"><b>I have non existing networks on the list of forbidden networks...</b></a></li>
\r
55 <li><a href="faq_net6.htm#27"><b>How to check frequency band (900 or 1800 Mhz), where phone work in this moment ?</b></a></li>
\r
56 <li><a href="faq_net6.htm#28"><b>Can I use DLR-2/DLR-3 cables for activating netmonitor ?</b></a></li>
\r
57 <li><a href="faq_net6.htm#29"><b>Can I activate netmonitor using Init File Editor (Nokia 9110) ?</b></a></li>
\r
58 <li><a href="faq_net6.htm#30"><b>Can I force phone to use one frequency band (900 or 1800 Mhz) only ?</b></a></li>
\r
59 <li><a href="faq_net6.htm#31"><b>How to change settings in tests ?</b></a></li>
\r
60 <li><a href="faq_net6.htm#32"><b>My phone has very short snandby time - it is possible to see the reason of it ?</b></a></li>
\r
61 <li><a href="faq_net6.htm#33"><b>Is netmonitor available in English version only ?</b></a></li>
\r
62 <li><a href="faq_net6.htm#Literatura"><b>Information sources</b></a></li>
\r
63 <li><a href="faq_net6.htm#35"><b>Additional information</b></a></li>
\r
64 <li><a href="faq_net6.htm#36"><b>Does using/activating netmonitor cost anything ?</b></a></li>
\r
65 <li><a href="faq_net6.htm#37"><b>Does using netmonitor is legall ?</b></a></li>
\r
66 <li><a href="faq_net6.htm#38"><b>Which entries on SIM card are used in netmonitor tests ?</b></a></li>
\r
67 <li><a href="faq_net6.htm#39"><b>Can I activate netmonitor in 3310 using soft working with 3210 ?</b></a></li>
\r
68 <li><a href="faq_net6.htm#40"><b>After activating netmonitor/BTS TEST my phone can't find network...</b></a></li>
\r
69 <li><a href="faq_net6.htm#41"><b>Netmonitor shows different battery capacity than info on it...</b></a></li>
\r
71 <hr size="2" noshade width="60%" align="center" style="color: #004080">
\r
74 <p><a NAME="Menu30"></a><b>Test 30</b>
\r
75 <br>Audio API register display
\r
78 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
81 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
83 <td><tt> aaaa bbbb<br>
\r
86 gggg hhhh </tt></td>
\r
92 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
94 <td><tt><b>A1Cnf A2Cnf<br>
\r
95 ST AU3<br>
\r
96 1Tone 2Tone<br>
\r
97 Conf HFVol</b></tt></td>
\r
106 <li>aaaa - API_AUD1_CTRL</li>
\r
107 <li>bbbb - API_AUD2_CTRL</li>
\r
108 <li>cccc - API_SIDETONE</li>
\r
109 <li>dddd - API_AU3</li>
\r
110 <li>eeee and ffff - API_1_TONE and API_2_TONE (see description below)</li>
\r
113 gggg - API_CONFIG: connected with sound setting from
\r
114 <b><a href="faq_net5.htm#Menu71_72">test 71 and 72</a></b>:
\r
115 you will see here number (hexadecimal),
\r
116 which was displayed there below AUDIO ENHANCEMENT (in last selected menu).
\r
117 Here are some examples:
\r
120 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
121 <tr ALIGN=CENTER><td><b>normally (for example during standby)</b></td><td><b>wybieranie numeru</b></td><td><b>call</b></td></tr>
\r
122 <tr ALIGN=CENTER><td>5148 (cracks) - 20808 decimal</td><td>5149</td><td>5140</td></tr>
\r
123 <tr ALIGN=CENTER><td>851A - 34074 decimal</td><td>851B</td><td>8512</td></tr>
\r
124 <tr ALIGN=CENTER><td>C6A4 (cracks) - 50852 decimal</td><td>C6AD</td><td>C6A4</td></tr>
\r
125 <tr ALIGN=CENTER><td>DB34 (cracks) - 56116 decimal</td><td>DB3D</td><td>DB34</td></tr>
\r
126 <tr ALIGN=CENTER><td>DF29 (after enabling phone) - 57129 decimal</td><td>DF29</td><td>DF20</td></tr>
\r
127 <tr ALIGN=CENTER><td>F436 - 62518 decimal</td><td>F43F</td><td>F436</td></tr>
\r
128 <tr ALIGN=CENTER><td>F437 - 62519 decimal</td><td>F43F</td><td>F436</td>
\r
135 <p>hhhh - API_HF_VOL: volume during call - you will count it from
\r
136 the "110 - hhhh" formula (subtract value of this parameter from 110).
\r
137 It's displayed too (during call only) in
\r
138 <b><a href="faq_net5.htm#Menu76">test 76</a></b>.
\r
139 When you connect headset, values here change - volume can be count
\r
140 from "510 - hhhh" formula then (for car kit use "2210 - hhhh").
\r
141 Type of connected audio accesories can be checked in
\r
142 <a href="faq_net5.htm#Menu75"><b>test 75</b></a> too.
\r
143 Phone remembers volume for each audio accesory separately.
\r
147 <p>When you press any key, phone generates sound, which consist of two tones.
\r
148 Parameters eeee and ffff change then. First tone is short, second is emited
\r
149 all time, when you press key. When you press C, NaviKey, Up or Down
\r
150 keys, change parameter eeee only (value 0E10 - 3600 decimal) -
\r
151 sound consist of one tone only. And now the most important thing:
\r
152 you will divide displayed in these parameters values by 4,
\r
153 you will have frequencies in Hz conncected with pressing adequate keys in
\r
154 DTMF (<b>D</b>ual <b>T</b>one <b>M</b>ulti <b>F</b>requency) system.
\r
155 I think, you use DTMF very often - it's used in tone system in all
\r
156 modern phones during calling number. Adequate values are in table (decimal)
\r
157 - parameter eeee is connected with vertical values, ffff with horizontal:
\r
160 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
161 <tr ALIGN=CENTER><td></td><td>1209 Hz</td><td>1336 Hz</td><td>1477 Hz</td></tr>
\r
162 <tr ALIGN=CENTER><td>697 Hz</td><td>1</td><td>2</td><td>3</td></tr>
\r
163 <tr ALIGN=CENTER><td>770 Hz</td><td>4</td><td>5</td><td>6</td></tr>
\r
164 <tr ALIGN=CENTER><td>852 Hz</td><td>7</td><td>8</td><td>9</td></tr>
\r
165 <tr ALIGN=CENTER><td>941 Hz</td><td>#</td><td>0</td><td>*</td></tr>
\r
168 <p><a NAME="Menu32"></a><b>Test 32</b>
\r
170 <p>Test from Nokia 6250 (no help):
\r
173 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
176 0 <br>
\r
184 <p>In 4'th line there is clock. Example:
\r
185 0205714 means 20 hours 57 minutes 14 seconds of the day ...
\r
187 <p><a NAME="Menu34"></a><b>Test 34</b>
\r
188 <br>Information about FBUS connection between phone and computer.
\r
191 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
194 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
196 <td><tt>aa bb cc dd<br>
\r
198 hhh iii jjj <br>
\r
205 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
207 <td><tt><b>CM LD LM NM <br>
\r
209 ACC RXS TXS <br>
\r
219 <li>aa - current fbus media in hex</li>
\r
220 <li>bb - last sender dev in hex</li>
\r
221 <li>cc - last sender media in hex</li>
\r
222 <li>dd - next media to be connected. Same as aa if the connection is not pending</li>
\r
223 <li>eee - fbus parity error counter</li>
\r
224 <li>fff - fbus framing error counter</li>
\r
225 <li>ggg - fbus overrun error counter</li>
\r
226 <li>hhh - fbus alive check counter</li>
\r
227 <li>iii - received sequence number</li>
\r
228 <li>jjj - sent sequence number</li>
\r
229 <li>k - phone mode: S=slave, H=host</li>
\r
232 <p>Description above is from some English documents. As you can see in some phones
\r
233 (like Nokia 5110) values in this test looks rather different, but help is the same.
\r
234 But, when you make connection with FBUS cable and make transmission, first line of values
\r
235 in this test changes to "1E0C1E -". When you will look into some
\r
236 <a href="faq_net6.htm#25">FBUS protocol descriptions</a>,
\r
237 you will see, that:
\r
240 <li>"1E" could mean datas send with <a href="faq_net6.htm#25">FBUS protocol</a> over cable</li>
\r
241 <li>"0C" could mean, that FBUS cable is connected to phone</li>
\r
244 <p>and it's the truth. So, it means, that this description is real (even, that
\r
245 test looks a little different).
\r
247 <p>Observation from Nokia 6150:
\r
250 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
253 aabbccdd <br>
\r
264 <li>000000 - no transmission after enabling phone</li>
\r
265 <li>1E0C1E - there was FBUS transmission</li>
\r
266 <li>140000 - there was infrared connection using NBS (business card, calendar entry, etc.)</li>
\r
267 <li>1C7F1C - there was 2-players snake game (host)</li>
\r
268 <li>1C001C - there was 2-players snake game (slave)</li>
\r
271 <li>hh: 0 - no infrared transmission in this moment</li>
\r
272 <li>i: increases for example after each sending data using infrared and NBS or ending
\r
274 <li>j: P - infrared enabled, searching next device (blinking indicator in phone)</li>
\r
275 <li>l: H - host in infrared transmission; S - slave in infrared transmission</li>
\r
276 <li>m: T - infrared enabled, connection terminated (blinking indicator in phone)</li>
\r
279 <p>In Nokia 9110 this menu looks different:
\r
282 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
285 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
287 <td><tt>ll mm nn oo <br>
\r
296 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
298 <td><tt><b>PA RS DR PR <br>
\r
301 D U DC</b></tt></td>
\r
311 p and q are probably iii and jjj</li>
\r
314 <p>Links to pages with FBUS (MBUS) protocol are in the <a href="faq_net6.htm#25">question 25</a>.
\r
317 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
319 <td><img SRC="../tip.gif" height=36 width=27 align=LEFT></td>
\r
321 <td>If values in this test changed after enabling phone, it means, that
\r
322 it was connected to computer and datas were transmitted with
\r
323 <a href="faq_net6.htm#25">FBUS protocol</a> (not MBUS).</td>
\r
327 <p><a NAME="Menu35"></a><b>Test 35</b>
\r
328 <br>Reason of last reboting internal firmware of phone.
\r
331 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
334 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
336 <td><tt> aaaaa <br>
\r
344 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
346 <td><tt><b>Reset reason<br>
\r
348 </b></tt></td>
\r
361 <li>NORM: probably normal power up</li>
\r
362 <li>UNKNO: default value, reset reason is unknown</li>
\r
363 <li>SWSIM: SIM contact failure reset. Shown, when phone has simlock and wrong mastercode was entered.</li>
\r
364 <li>STACK: task stack overflow</li>
\r
365 <li>SWIDL: idle task not running reset</li>
\r
366 <li>HW lub WD: <a href="faq_net1.htm#ASIC">ASIC</a> watchdog timeout. SW WD in Nokia 3310 ?</li>
\r
367 <li>SWDSP: restart <a href="faq_net1.htm#DSP">DSP</a> recovery reset</li>
\r
373 bbbbbbbb - name of running task before reset (for example,
\r
374 <nobr>"AUD TASK"</nobr>,
\r
375 <nobr>"CC TASK"</nobr> (confirmed),
\r
376 <nobr>"DDI TASK"</nobr>,
\r
377 <nobr>"DEV IO"</nobr> (confirmed),
\r
378 <nobr>"EM TASK"</nobr>,
\r
379 "FBUSTASK" (confirmed - after errors in cable transmission),
\r
380 <nobr>"L1 CONTR"</nobr>,
\r
381 <nobr>"L1 MEAS"</nobr>,
\r
382 <nobr>"L1 SYSPA"</nobr> (confirmed),
\r
383 <nobr>"L2 TASK"</nobr>,
\r
384 "LOCAL" (confirmed - shown, for example, when phone had to restart because of error in firmware),
\r
385 <nobr>"MDI RECE"</nobr> (confirmed),
\r
386 <nobr>"MDI SEND"</nobr> (confirmed),
\r
387 <nobr>"MM TASK"</nobr> (confirmed),
\r
388 <nobr>"OS IDLE"</nobr> (confirmed),
\r
389 <nobr>"PN TASK"</nobr> (confirmed),
\r
390 <nobr>"RR TASK"</nobr> (confirmed),
\r
391 <nobr>"RM TASK"</nobr>,
\r
392 <nobr>"SIM L2"</nobr> (confirmed),
\r
393 <nobr>"SIM UPL"</nobr> (confirmed),
\r
394 <nobr>"SMS TASK"</nobr> (confirmed),
\r
396 <nobr>"UI TASK"</nobr> (confirmed)
\r
397 <nobr>"PND TASK"</nobr> (for example Nokia 6210),
\r
398 "WMLSTASK" (for example Nokia 6210),
\r
399 "IRDATASK" (for example Nokia 6210),
\r
400 <nobr>"IRDA MGR"</nobr> (for example Nokia 6210),
\r
401 <nobr>"PH TASK"</nobr> (for example Nokia 6210),
\r
402 <nobr>"DGC TASK"</nobr> (for example Nokia 6210),
\r
403 <nobr>"DGNTB TA"</nobr> (for example Nokia 6210),
\r
404 <nobr>"DGFAX TA"</nobr> (for example Nokia 6210),
\r
405 <nobr>"SCKT SRV"</nobr> (for example Nokia 6210),
\r
406 <nobr>"PMM CLUP"</nobr> (for example Nokia 6210),
\r
407 <nobr>"PMM WRBA"</nobr> (for example Nokia 6210),
\r
408 <nobr>"ND TASK"</nobr> (for example Nokia 6210),
\r
409 <nobr>"PPC TASK"</nobr> (for example Nokia 6210),
\r
410 <nobr>"No task!"</nobr> (for example Nokia 6210)
\r
411 or "UNKNOWN" (confirmed - after normal phone enabling)). We can notice, that tasks names are similiar to
\r
412 names in help to <a href="faq_net5.htm#Menu84_86">tests 84-86</a>.</li>
\r
415 <p><a NAME="Menu36"></a><b>Test 36</b>
\r
416 <br>Reasons of last reboting internal firmware of phone (you will
\r
417 find here information, how many times phone made restarts because of reasons
\r
418 from previous test).
\r
421 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
424 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
426 <td><tt> aa bb cc <br>
\r
427 dd ee ff<p>
\r
434 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
436 <td><tt><b> UN WD DSP <br>
\r
438 </b></tt></td>
\r
447 <li>aa - unknown resets</li>
\r
449 <li>bb - <a href="faq_net1.htm#ASIC">ASIC</a> watchdog timeout resets (in some
\r
450 you can simulate it - see <a href="faq_net0.htm#9">question 9</a> for details)</li>
\r
452 <li>cc - <a href="faq_net1.htm#DSP">DSP</a> recovery resets. In Nokia 3310 displayed also
\r
453 in <a href=faq_net6.htm#Menu130>test 130</a>.</li>
\r
456 dd - some English descriptions say, that it's connected with
\r
457 SIM contact failure reset (in some phones you can force reset because of this reason
\r
458 - see <a href="faq_net0.htm#9">question 9</a>). I noticed too, that this counter
\r
459 increases when to try to enter mastercode connected with simlock level 1
\r
460 using <b>#pw+2222222222+1#</b> code (where mastercode is instead of 2222222222), when
\r
461 your phone has simlock.
\r
464 <li>ee - idle task not running resets</li>
\r
466 <li>ff - task stack overflow resets</li>
\r
469 <p>Counters are stored to EEPROM.
\r
471 <p>In Nokia 3310 some counters (DSP only ?) are displayed from end (for example, 01 is displayed as 10,
\r
475 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
477 <td><img SRC="../tip.gif" height=36 width=27 align=LEFT></td>
\r
479 <td>You can reset counters from this menu using some Nokia service programs
\r
480 - for example, in Pc-Locals 1.3 enter to menu 8 ("Event Trace"),
\r
481 menu 5 ("Permanent Counter Table...") and press F6 key ("Clear Counters").
\r
482 Unfortunatelly :(, "real" counters connected with mastercode entering attempts
\r
483 (Counter for example in WinTesla and WinLock) don't reset then...
\r
488 <p><a NAME="Menu38"></a><b>Test 38</b>
\r
492 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
495 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
497 <td><tt>aaaaaaaaaaaa<br>
\r
500 aaaaaaaaaaaa</tt></td>
\r
506 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
508 <td><tt><b>Memory dump <br>
\r
510 </b></tt></td>
\r
519 <li>aaaa.... - hex dump of 24 successive memory locations</li>
\r
522 <p>The start address of the dump is entered as 6 digit address value
\r
523 into location 30 into phonebook on SIM card (information, how to make it,
\r
524 are in <b><a href="faq_net3.htm#Menu17">test 17</a></b>).
\r
525 An example: for address 0x0C89AB enter 0C2089AB value there...
\r
526 Dump address is changed only when you directly enter to this menu.
\r
528 <p>This display rather is not included in offcial firmware (I found only one
\r
529 phone with it). It can be switched on by defining flag DEV_FT_MEMORY_DUMP_IN_USE in ftd_conf.h.
\r
531 <p><a NAME="Menu39"></a><b>Test 39</b>
\r
532 <br>Reason of last connection end (asterisk means, that the diagnosis won't be sent to the
\r
533 network - it'll be only shown in phone) and making
\r
534 <a href="faq_net1.htm#LocationUpdate">Location Update</a>:
\r
537 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
540 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
542 <td><tt> CC: aaa <br>
\r
543 MM: bbb<br>
\r
544 RR: ccc<br>
\r
551 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
553 <td><tt><b>CC CauseValu<br>
\r
556 </b></tt></td>
\r
566 reason from the CallControl-Layer - it's displayed in
\r
567 <b><a href="faq_net2.htm#Menu2">test 2</a></b> and
\r
568 <b><a href="faq_net5.htm#Menu63">test 63</a></b> too:
\r
573 from the GSM specifications (section 10.5.4.11/GSM 04.08):
\r
578 <tt> 1</tt>: unassigned (unallocated) number</li>
\r
581 <tt> 3</tt>: no route to destination</li>
\r
584 <tt> 8</tt>: operator determined barring</li>
\r
587 <tt>16</tt>: normal end of call (you were speaking or you heard some
\r
588 text - that dialled number was busy or something similiar)
\r
592 <tt>17</tt>: user busy
\r
597 if it was outgoing call, dialled number was busy (phone even displayed
\r
598 'Number busy')</li>
\r
601 if it was incoming call, a man, who dialled to you, heard busy signal
\r
602 - you were speaking or you rejected it (in Nokia 5110 or 5130 to make
\r
603 it you have to press C key, in Nokia 6110, 6130 or 6150 red receiver)
\r
610 <tt>18</tt>: no user responding</li>
\r
613 <tt>19</tt>: user alerting (from specification - I had it
\r
614 with normal connection too (phone displayed
\r
615 'No answer' ('Nie odpowiada')) or when incoming call was diverted to
\r
616 voice mailbox), no answer
\r
620 <tt>21</tt>: call rejected
\r
625 phone wasn't in network coverage (message 'No coverage network'), when you
\r
630 you tried to call to non existing phone number or you heard busy signal
\r
637 <tt>22</tt>: number changed</li>
\r
640 <tt>27</tt>: destination out of order</li>
\r
643 <tt>28</tt>: invalid number format/number incomplete. Phone displayed
\r
644 'Invalid phone number'</li>
\r
647 <tt>31</tt>: unspecidied. It seems, that with this error connection
\r
648 is end by network (for example, when it's overcharged).
\r
649 Shown sometimes too, when you call for not supported for some tariffs numbers.
\r
653 <tt>34</tt>: no circuit/channel available to make call. Phone displayed
\r
654 'Network busy'. I noticed too, that in my network RR value changed to
\r
655 1 with this error. More about situations, when network is busy, I write
\r
656 in <a href="faq_net1.htm#TS">TS description</a>.</li>
\r
659 <tt>38</tt>: network out of order</li>
\r
662 <tt>41</tt>: temporary failure</li>
\r
665 <tt>42</tt>: switching equipment congestion
\r
666 (message "Network busy")
\r
670 <tt>44</tt>: requested channel not available</li>
\r
673 <tt>47</tt>: ressource unavailable. I had it, when connection was "brutal" broken.
\r
674 Concrete: during call phone of my interlocutor disabled because of empty battery.
\r
675 My phone displayed 'Error in connection'</li>
\r
678 <tt>50</tt>: requested facility not subscribed
\r
679 (you must subscribe it to use it)
\r
680 In some networks shown too, when you set not supported by network function
\r
681 (for example, "Own number sending" in Era-GSM network).
\r
682 Message "Check operator services".
\r
686 <tt>65</tt>: bearer service not implemented</li>
\r
689 <tt>68</tt>: ACM equal to or greater than ACMmax</li>
\r
692 <tt>69</tt>: requested facility not implemented</li>
\r
695 <tt>88</tt>: incompatible destination</li>
\r
702 from mine (and not only) experiences:
\r
707 <li><tt> 28</tt>: I had it, when phone number was too long</li>
\r
709 <li><tt> 57</tt>: no asynchronous data transmission allowed (concrete:
\r
710 phone wasn't able to connect to WAP from this concrete SIM card)</li>
\r
712 <li><tt> 63</tt>: "Poza zasiêgiem sieci"</li>
\r
715 <tt>79</tt>: error with message 'Check operator services'.
\r
716 You have it, when you enable ALS (<b>A</b>lternative <b>L</b>ine <b>S</b>ervice) function,
\r
717 don't have second number on SIM card, select it and try to make call
\r
721 <tt>111</tt>:'Error in connection'</li>
\r
730 reason from the MobilityManagement-Layer
\r
731 - it's shown in <b><a href="faq_net5.htm#Menu64">test 64</a></b> too.
\r
732 It's from GSM specification (section 10.5.3.6/GSM 04.08):
\r
737 <tt> 2</tt>: <a href="faq_net1.htm#IMSI">IMSI</a> unknown in <a href="faq_net1.htm#HLR">HLR</a>
\r
738 (SIM card not active in network)</li>
\r
741 <tt> 3</tt>: illegal phone</li>
\r
744 <tt> 4</tt>: <a href="faq_net1.htm#IMSI">IMSI</a> unknown in <a href="faq_net1.htm#VLR">VLR</a></li>
\r
747 <tt> 5</tt>: phone's <a href="faq_net1.htm#IMEI">IMEI</a> was not accepted</li>
\r
750 <tt> 6</tt>: illegal ME</li>
\r
753 <tt>11</tt>: <a href="faq_net1.htm#PLMN">PLMN</a> not allowed (you tried to log into
\r
754 network, which doesn't have roaming convention with your home network - your phone
\r
755 displays 'No access', when you try to select it manually; I don't know only, if
\r
756 this code is displayed only, when this network is saved on forbidden list on SIM
\r
757 card (see <b><a href="faq_net2.htm#Menu6">test 6</a></b>)</li>
\r
760 <tt>12</tt>: Location Area not allowed. You can check it in <b><a href="faq_net3.htm#Menu11">test 11</a></b>.</li>
\r
763 <tt>13</tt>: roaming not allowed in this Location Area</li>
\r
766 <tt>17</tt>: network failure</li>
\r
769 <tt>22</tt>: network congestion</li>
\r
772 <tt>32</tt>: service option not supported</li>
\r
775 <tt>33</tt>: service option not subscribed</li>
\r
778 <tt>34</tt>: service temporarily out of order</li>
\r
781 <tt>38</tt>: call cannot be identified (call RE)<p></li>
\r
786 reason from RadioRessourceManagement-Layer)
\r
787 - see GSM specifications: section 10.5.2.31/GSM 04.08:
\r
792 <tt> 0</tt>: normal release</li>
\r
795 <tt> 1</tt>: unspecified</li>
\r
798 <tt> 2</tt>: channel unacceptable</li>
\r
801 <tt> 3</tt>: timer expired </li>
\r
804 <tt> 4</tt>: no activity on the radio path</li>
\r
807 <tt> 5</tt>: Pre-emptive release</li>
\r
810 <tt> 8</tt>: <a href="#Handover">handover</a> impossible,
\r
811 <a href="faq_net2.htm#TA">TA</a> out of range</li>
\r
814 <tt> 9</tt>: channel mode unacceptable</li>
\r
817 <tt> 10</tt>: frequency not implemented</li>
\r
820 <tt> 65</tt>: call already cleared</li>
\r
823 <tt> 97</tt>: message type not compatible with protocol state</li>
\r
826 <tt>101</tt>: no cell allocation available</li>
\r
829 <tt>111</tt>: protocol error unspecified</li>
\r
834 <p>When you will see "*" before third parameter from this test, it means
\r
835 (the most often), that call is in progress. Sometimes phone displays different
\r
836 values - I don't know their meaning :-(.
\r
838 <p>Values of counters are not saved in EEPROM. When phone makes another measure,
\r
839 doesn't reset them (changes only these values during next measure, which are connected
\r
840 with it; doesn't change the rest of them).
\r
843 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
845 <td><img SRC="../tip.gif" height=36 width=27></td>
\r
847 <td>This test allows to find, why exactly your phone doesn't want to work
\r
848 - doesn't want to make calls.</td>
\r
852 <p><a NAME="Menu40"></a><b>Test 40</b>
\r
853 <br>Resets <a href="#Handover">handover</a> counters (by direct enter)...
\r
856 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
859 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
861 <td><tt> RESET<br>
\r
862 HANDOVER <br>
\r
863 COUNTERS<br>
\r
870 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
872 <td><tt><b> Use menu <br>
\r
873 to reset<br>
\r
874 handover<br>
\r
875 counters</b></tt></td>
\r
882 <p><a NAME="Menu41"></a><b>Test 41</b>
\r
883 <br>Information about <a href="#Handover">handover</a>
\r
885 <p><a NAME="Handover"></a>Handover - it's transfer of radio connection
\r
886 (between phone and cell) from one cell to another (without breaking call).
\r
892 new radio connecting will give better quality (it's parameters are all the time
\r
893 checked by phone and base station)
\r
897 when phone is between few cells and can use "new" cells for him
\r
898 (it frees some place for phones, which can use "old" cell only)
\r
902 <p>When they're problems with transmission, decision about handover is made
\r
903 by phone (otherwise it's made by <a href="faq_net1.htm#BSC">BSC</a>).
\r
904 If you enabled using one channel by phone (<b><a href="faq_net3.htm#Menu17">test 17</a></b>),
\r
905 handovers are not made.
\r
907 <p>There are 4 types of handovers:
\r
912 <a NAME="Intra"></a><b>Intra cell - Intra <a href="faq_net1.htm#BSC">BSC</a>
\r
913 handover</b> (called <b>handoff</b> too): it's the smallest handover
\r
914 inside one cell. Receiver is "thrown over" from one channel to another
\r
915 (gennerally to another frequency inside one cell). Decision, if it should
\r
916 be done, is made by <a href="faq_net1.htm#BSC">BSC</a>.</li>
\r
919 <b>Inter cell - Intra <a href="faq_net1.htm#BSC">BSC</a> handover</b>:
\r
920 receiver is moved from one cell to another. Decision about it
\r
921 is made by <a href="faq_net1.htm#BSC">BSC</a>. Connection with first cell
\r
922 is broken after moment, when connection with another is made (displacement
\r
923 between two <a href="faq_net1.htm#BTS">BTSes</a> inside one
\r
924 <a href="faq_net1.htm#BSC">BSC</a>).</li>
\r
927 <b>Inter cell - Inter <a href="faq_net1.htm#BSC">BSC</a> handover</b>:
\r
928 displacement of connection between two cells, which are not served by
\r
929 the same <a href="faq_net1.htm#BSC">BSC</a>. In this case handover is moved
\r
930 by <a href="faq_net1.htm#MSC">MSC</a>, but decision about it made
\r
931 by first <a href="faq_net1.htm#BSC">BSC</a>. Connection with first
\r
932 <a href="faq_net1.htm#BSC">BSC</a> (and <a href="faq_net1.htm#BTS">BTS</a>)
\r
933 is broken before moment, when connection with another <a href="faq_net1.htm#BSC">BSC</a>
\r
934 (and <a href="faq_net1.htm#BTS">BTS</a>) is made.
\r
938 <b>Inter <a href="faq_net1.htm#MSC">MSC</a> handover</b>: receiver moves from
\r
939 cell served by <a href="faq_net1.htm#MSC">MSC</a>/<a href="faq_net1.htm#VLR">VLR</a>
\r
940 to another controlled by another <a href="faq_net1.htm#MSC">MSC</a>/<a href="faq_net1.htm#VLR">VLR</a>.
\r
941 It's more complicated situation. We can notice, that
\r
942 <a href="faq_net1.htm#MSC">MSC</a> is connected to GSMc over PSTN.
\r
943 In this case is visible, that another <a href="faq_net1.htm#MSC">MSC</a>
\r
944 can't receive information from first normally.
\r
946 <p>What will happen, when connection will be moved to target
\r
947 <a href="faq_net1.htm#MSC">MSC</a>/<a href="faq_net1.htm#VLR">VLR</a> ?
\r
949 <p>Because both <a href="faq_net1.htm#MSC">MSC</a> belongs to the same network,
\r
950 connection is kept. To move it from one to another <a href="faq_net1.htm#MSC">MSC</a>
\r
951 special number HON (HON=CC+NDC+SN, CC - country code, NDC - network code,
\r
952 SN - subscriber's number) must be generated. It's similiar to roaming number
\r
953 (it's connection between two <a href="faq_net1.htm#MSC">MSC</a> too). During
\r
954 handover between two <a href="faq_net1.htm#MSC">MSC</a> connection can't be
\r
955 broken (phone connection realised by network's subscriber).
\r
959 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
962 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
964 <td><tt>HandOOk: aaa<br>
\r
967 HOIntra: ddd</tt></td>
\r
973 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
975 <td><tt><b>HandOvOKCntr<br>
\r
978 HOIntraOKCnt</b></tt></td>
\r
988 aaa - counter for successful <a href="#Handover">handovers</a></li>
\r
991 bbb - counter for successful back to previous channel attempts
\r
992 (number of actual used channel is displayed, for example, in
\r
993 <b><a href="faq_net2.htm#Menu1">test 1</a></b>)</li>
\r
996 ccc - counter for failed <a href="#Handover">handovers</a></li>
\r
998 <li>ddd - counter for successful <a href="#Intra">Intra cell - Intra BSC</a> <a href="#Handover">handovers</a>
\r
999 or assignments</li>
\r
1002 <p>Counters will stop when they reach their maximum (999). To initialize them
\r
1003 to zero, use <b><a href="#Menu40">test 40</a></b> (or
\r
1004 <b><a href="faq_net5.htm#Menu60">test 60</a></b>).
\r
1006 <p>In dual phones (like Nokia 6150 or 3210) <b>test 41</b> looks
\r
1007 different and is connected with Inter cell - Intra BSC,
\r
1008 Inter cell - Inter BSC and Inter MSC <a href="#Handover">handovers</a>:
\r
1011 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1014 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1016 <td><tt> aaaa bbbb<br>
\r
1017 cccc dddd<br>
\r
1019 iiijjjkkklll</tt></td>
\r
1025 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1027 <td><tt><b>G>G InterD>D<br>
\r
1028 G>D OK D>G<br>
\r
1030 BackToPrev</b></tt></td>
\r
1039 <li>aaa - counter of successful <a href="#Handover">handovers</a> from GSM 900 to GSM 900</li>
\r
1040 <li>bbb -counter of successful <a href="#Handover">handovers</a> from GSM 1800 to GSM 1800</li>
\r
1041 <li>ccc - counter of successful <a href="#Handover">handovers</a> from GSM 900 to GSM 1800</li>
\r
1042 <li>ddd - counter of successful <a href="#Handover">handovers</a> from GSM 1800 to GSM 900</li>
\r
1043 <li>eee - counter of failed <a href="#Handover">handovers</a> from GSM 900 to GSM 900</li>
\r
1044 <li>fff - counter of failed <a href="#Handover">handovers</a> from GSM 1800 to GSM 1800</li>
\r
1045 <li>ggg -counter of failed <a href="#Handover">handovers</a> from GSM 900 to GSM 1800</li>
\r
1046 <li>hhh - counter of failed <a href="#Handover">handovers</a> from GSM 1800 to GSM900</li>
\r
1049 iii - counter of successful back to previous channel attempts
\r
1050 (number of actual used channel is displayed, for example, in
\r
1051 <b><a href="faq_net2.htm#Menu1">test 1</a></b>)
\r
1052 from GSM 900 to GSM 900</li>
\r
1054 <li>jjj - counter of successful back to previous channel attempts from GSM 1800 to GSM 1800</li>
\r
1056 <li>kkk - counter of successful back to previous channel attempts from GSM 900 to GSM 1800</li>
\r
1058 <li>lll - counter of successful back to previous channel attempts from GSM 1800 to GSM 900</li>
\r
1061 <p>Counters will stop when they reach their maximum (9999 dla dwóch pierwszych
\r
1062 linii, 999 dla dwóch ostatnich). To initialize them to zero, use <b><a href="#Menu40">test 40</a></b>
\r
1063 (or <b><a href="faq_net5.htm#Menu60">test 60</a></b>).
\r
1065 <p>In Nokia 3310 sum of all <a href=faq_net4.htm#handover>handovers</a> is also
\r
1066 displayed in <a href=faq_net6.htm#Menu131>test 131</a> (?).
\r
1068 <p>In Nokia 3110 this test looks like follows:
\r
1071 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1074 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1076 <td><tt>HandOOk: aaa <br>
\r
1077 PrevCh : bbb <br>
\r
1078 HONotOK: ccc <br>
\r
1079 T200: eeee</tt></td>
\r
1085 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1087 <td><tt><b>HandOvOKCntr <br>
\r
1088 PrevChanCntr <br>
\r
1089 HandOvNOKCnt <br>
\r
1090 T200Cntr</b></tt></td>
\r
1100 eeee - I write about T200 counter in <b><a href="#Menu43">test 43</a></b></li>
\r
1103 <p>and here's for Nokia 6185/6188:
\r
1106 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1118 <li>VBAT - battery voltage (/100V)</li>
\r
1119 <li>BTEMP - battery temperature in C</li>
\r
1120 <li>CHG - battery charge status: 1 - charging, 0 - not charging</li>
\r
1123 <p><a NAME="Menu42"></a><b>Test 42</b>
\r
1124 <br>This test is in dual phones (for example, Nokia 6150 or 3210) only
\r
1125 and is connected with first kind of <a href="#Handover">handovers</a>
\r
1126 (<a href="#Intra">Intra cell - Intra BSC</a>):
\r
1129 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1132 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1134 <td><tt> aaaa bbbb<br>
\r
1135 cccc dddd<br>
\r
1137 iiijjjkkklll</tt></td>
\r
1143 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1145 <td><tt><b>G>G IntraD>D<br>
\r
1146 G>D OK D>G<br>
\r
1148 BackToPrev</b></tt></td>
\r
1157 <li>aaaa - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 900</li>
\r
1158 <li>bbbb - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 1800</li>
\r
1159 <li>cccc - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 1800</li>
\r
1160 <li>dddd - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 900</li>
\r
1161 <li>eee - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 900</li>
\r
1162 <li>fff - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 1800</li>
\r
1163 <li>ggg - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 1800</li>
\r
1164 <li>hhh - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 900</li>
\r
1167 iii - counter of successful back to previous normal channel
\r
1168 (you can check number of actual used channel for example in
\r
1169 <b><a href="faq_net2.htm#Menu1">test 1</a></b>) attempts
\r
1170 inside one cell (INTRA CELL) from GSM 900 to GSM 900
\r
1174 jjj - counter of successful back to previous normal channel attempts
\r
1175 inside one cell (INTRA CELL) from GSM 1800 to GSM 1800
\r
1179 kkk - counter of successful back to previous normal channel attempts
\r
1180 inside one cell (INTRA CELL) from GSM 900 to GSM 1800</li>
\r
1183 lll - counter of successful back to previous normal channel attempts
\r
1184 inside one cell (INTRA CELL) from GSM 1800 to GSM 900</li>
\r
1187 <p>Counters will stop when they reach their maximum (9999 for two first lines,
\r
1188 999 for two last). To initialize them
\r
1189 to zero, use <b><a href="#Menu40">test 40</a></b>
\r
1190 (or <b><a href="faq_net5.htm#Menu60">test 60</a></b>).
\r
1192 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.htm#Menu20">test 20</a>.
\r
1194 <p><a NAME="Menu43"></a><b>Test 43</b>
\r
1196 <p>Some English descriptions write about this test:
\r
1199 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1202 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1204 <td><tt>T200MS: aaaa<br>
\r
1207 T200BS: dddd</tt></td>
\r
1213 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1215 <td><tt><b>T200 MS GSM <br>
\r
1218 T200 BS DCS</b></tt></td>
\r
1228 aaaa - for GSM 900: counts how many times T200 in phone has expired and
\r
1229 therefore L2 transmission has been repeated.</li>
\r
1232 bbbb - for GSM 900: counts how many times T200 in <a href="faq_net1.htm#BTS">BTS</a> (network) has expired
\r
1233 and therefore L2 transmission has been repeated.
\r
1237 cccc - for GSM 1800 called earlier DCS (in dual phones only): counts how many times T200 in phone
\r
1238 has expired and therefore L2 transmission has been repeated.
\r
1242 dddd - for GSM 1800 (in dual phone only): counts how many times T200 in <a href="faq_net1.htm#BTS">BTSie</a>
\r
1243 (network) has expired and therefore L2 transmission has been repeated.</li>
\r
1246 <p>Counters will stop when they reach their maximum (9999 for two first lines,
\r
1247 999 for two last). To initialize them to zero, use <b><a href="#Menu40">test
\r
1248 40</a></b> (or <b><a href="faq_net5.htm#Menu60">test 60</a></b>).
\r
1250 <p>I noticed, that some things are a little different: in all 900, 1800, 900/1800 MHz
\r
1251 phones, I saw, info is displayed ONLY in two first lines. Help is a little different too:
\r
1254 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1257 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1260 T200 MS <br>
\r
1273 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1289 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1303 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.htm#Menu21">test 21</a>.
\r
1305 <p><a NAME="Menu44"></a><b>Test 44</b>
\r
1306 <br>You change value from 01 (default) to 00 (or vice versa) by direct enter to this test.
\r
1309 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1312 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1315 <br><tt> REVISION<br>
\r
1316 LEVEL IS aa <br>
\r
1323 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1325 <td><tt><b>Use menu to <br>
\r
1326 change<br>
\r
1327 Revision<br>
\r
1328 Level</b></tt></td>
\r
1335 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.htm#Menu22">test 22</a>.
\r
1337 <p><a NAME="Menu45"></a><b>Test 45</b>
\r
1338 <br>This test allows to simulate situations. when phone can normally
\r
1339 receive network signal (but network can't receive any information from phone).
\r
1340 It's very realistic (even in <b><a href="faq_net2.htm#Menu1">test
\r
1341 1</a></b> in ddd parameter an asterisk (*) is displayed, when
\r
1342 you try to make connection), but not always (in
\r
1343 <b><a href="faq_net3.htm#Menu10">test 10</a></b> you will see
\r
1344 'xxxxxxxx' instead of TMSI, when T3212 counter in first
\r
1345 parameter will be expired).
\r
1347 <p>You can change it by direct enter.
\r
1350 <center><table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1353 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1356 <br><tt>TRANSMITTER <br>
\r
1357 ENABLED<br>
\r
1362 <p>(default setting)</td>
\r
1365 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1368 <br><tt>TRANSMITTER <br>
\r
1369 DISABLED<br>
\r
1376 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1378 <td><tt><b>Use menu to <br>
\r
1379 enable or<br>
\r
1380 disable<br>
\r
1381 transmitter</b></tt></td>
\r
1389 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1391 <td><img SRC="../tip.gif" height=36 width=27></td>
\r
1393 <td>When you enable it, phone won't be able, for example, to update
\r
1394 location (see <b><a href="faq_net5.htm#Menu64">test 64</a></b>) and
\r
1395 make calls. It will allow to:
\r
1398 <li>"blockade" phone to the moment of another enabling it (for example,
\r
1399 when you want to observe network parameters, but you don't want to be
\r
1400 accessible for others - when somebody will call to you, for network
\r
1401 your phone will be outside range)
\r
1405 fast remind you of number written to phonebook (it's written on leaf,
\r
1406 but you don't remember name of person assigned to): simple call it.
\r
1407 When phone will choose number, it will display this name; it will be written
\r
1408 on list odf last dialed numbers too.
\r
1415 <p>This test DOESN'T WORK CORRECTLY in Nokia 3210, 3310 and 7110 (you change setting,
\r
1416 but it doesn't give described above results).
\r
1418 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.htm#Menu23">test 23</a>.
\r
1420 <p><a NAME="Menu46"></a><b>Test 46</b>
\r
1423 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1426 <b>BAND CLASS a<br>
\r
1434 <p><a NAME="Menu48"></a><b>Test 48</b>
\r
1435 <br>In Nokia 3110 this test looks like <b><a href="faq_net2.htm#Menu7">test 7</a></b>.
\r
1437 <p><a NAME="Menu51"></a><b>Test 51</b>
\r
1438 <br>Information about SIM card
\r
1441 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1444 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1446 <td><tt>aaa bbb ccc <br>
\r
1447 dddddddd<br>
\r
1448 e f gg hh<br>
\r
1449 i jjjj</tt></td>
\r
1455 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1457 <td><tt><b>VSel Bau SAl<br>
\r
1458 SCond CStop<br>
\r
1459 PIN12 PUK12<br>
\r
1460 ATR FE/PE</b></tt></td>
\r
1470 aa - SIM voltage selection type (3, 3/5 or 5)</li>
\r
1473 bbb - division coefficient, which define speed of communication phone with
\r
1474 SIM card (372, 64, 32 or 0) saved in ATR (first sequence send by SIM card
\r
1475 after reset - <b>A</b>nswer <b>T</b>o <b>R</b>eset).
\r
1476 When you will divide clock frequency (maximal 3,25 MHz = 3 250 000 Hz)
\r
1477 by it, you will have speed of transmission
\r
1478 (for example, 3 250 000 Hz / 372 = 8736,5 bods)
\r
1479 WARNING ! YOU CAN'T CHANGE SPEED OF COMMUNICATION PHONE WITH SIM CARD
\r
1480 AND VALUE OF THIS PARAMETER !
\r
1484 ccc - information, whether SIM clock stop is allowed (it saves energy)
\r
1485 during standby (YES or NOT - possible or not). This information is displayed
\r
1486 (in Nokia phones and not only) using <b>*#SIM0CLOCK#</b> code
\r
1487 - when you will see "SIM clock stop allowed", SIM card allows to make it.
\r
1488 Some Nokia 6110 phones (it depeneds on their firmware) can not support
\r
1489 correctly this code - they display, for example, "Result unknown".
\r
1490 Phone disables SIM card clock automatically - you can't make it manually !
\r
1494 dddd - information about clock stop condition:
\r
1500 <li>DOWN(UP) - in tested by me SIM cards</li>
\r
1508 e - number of left PIN1 code entering attempts. When it's bigger than 9,
\r
1509 you will see only last digit of it (for example, I found some prepaid cards
\r
1510 with 10 value). Maximal number of entering code attempts depends on concrete
\r
1511 SIM card (it can be set to any value), but the most often it's equal 3. In some SIM cards
\r
1512 you can disable answering for this code (for example, you can select it in
\r
1513 <b>Menu 4-3-1</b> in Nokia 5110). When it's equal 0, phone shows
\r
1514 "Sim card blocked" and asks for PUK1. If it was entered correctly, this counter
\r
1515 is reset to maximal value. Disabling and enabling phone doesn't reset it !
\r
1519 f - number of left PIN2 code entering attempts (when SIM card doesn't support
\r
1520 PIN2 functions, you will see "x" here). You can check, if these functions are supported,
\r
1521 using call cost function too (if they're not, phone displays "Not allowed").
\r
1522 If you wanted to use them and your card doesn't support them (you will see "x"
\r
1523 here), you (or your operator ;-) rather) have to change it.
\r
1524 Maximal number of entering code attempts depends on concrete
\r
1525 SIM card (it can be set to any value), but the most often it's equal 3. When this counter
\r
1526 is equal 0, phone asks for PUK2. When this code was entered correctly, counter
\r
1527 is reset to maximal value. Of course, even when it's equal 0, you can normally
\r
1528 use SIM card (PIN2/PUK2 are independent of PIN1/PUK1), when you know PIN1.
\r
1529 Disabling and enabling phone doesn't reset it !
\r
1530 If SIM card has blocked PIN2/PUK2 codes, you can enter to the menus contains supported
\r
1531 by these codes functions (but after changing next settings you will see error).
\r
1535 gg - number of left PUK1 code entering attempts.
\r
1536 Maximal number of entering code attempts depends on concrete
\r
1537 SIM card (it can be set to any value), but the most often it's equal 10.
\r
1538 Phone asks for it, when counter of left PIN1 code entering attempts is equal 0
\r
1539 (phone shows "Sim card blocked"). When this counter is equal 0 too, SIM card
\r
1540 can be blocked (phone shows "Sim card rejected") or (it depends on card)
\r
1541 asks for PUK2. When this code was entered correctly, counters of left PIN1 and
\r
1542 PUK1 codes entering attempts are reset to maximal values.
\r
1543 Disabling and enabling phone doesn't reset it !
\r
1547 hh - number of left PUK2 code entering attempts (when SIM card doesn't support
\r
1548 PIN2 functions, you will see "x" here).
\r
1549 Maximal number of entering code attempts depends on concrete
\r
1550 SIM card (it can be set to any value), but the most often it's equal 10.
\r
1551 When it's equal 0, using PIN2 functions can be impossible on this SIM card (ask operator for help).
\r
1552 Additionaly, when you were asked for PUK2, when counters of left PIN1 and
\r
1553 PUK1 codes entering attempts were equal 0 and now left PUK2 code entering attempts
\r
1554 is equal 0 too, using this SIM card can be impossible (you have to replace it to new).
\r
1555 When it was entered correctly, counters for this code and PIN2 (when you entered
\r
1556 PUK2, because PIN2 was blocked) are reset to maximal values or counters for this,
\r
1557 PIN1 and PUK1 are reset (when you entered PUK2, because PIN1 and PUK1 were blocked).
\r
1558 Disabling and enabling phone doesn't reset it !
\r
1562 i - ATR repeat counter (ATR is first sequence sent by SIM card in answet to reset -
\r
1563 <b>A</b>nswer <b>T</b>o <b>R</b>eset) (0-9)</li>
\r
1566 jjjj - number of retransmissions/parity errors in transmission with SIM card
\r
1567 (when the happen, two first chars are equals FE (<b>F</b>rame <b>E</b>rror) or
\r
1568 PE (<b>P</b>arity <b>E</b>rror), two last number of retransmission/errors)</li>
\r
1571 <p>If you don't have SIM card in the phone, you will see "ERROR1" in this test.
\r
1573 <p>If phone has problems with communication with SIM card, this test can look like
\r
1574 follows (i and jjjj parameters are described above):
\r
1577 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1580 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1582 <td><tt>ERROR1 5 55<br>
\r
1584 i jjjj<br>
\r
1594 <p>CStop parameter (information, if SIM card clock is disabled in this moment)
\r
1595 is displayed in help only. Why ? Probably somebody didn't remember about it...
\r
1597 <p>Here are some observations for SIM voltage selection type (first parameter)
\r
1598 Nokia 5110 and tested SIM cards:
\r
1600 <p>After enabling phone reads some information from SIM card (for example,
\r
1601 number saved on it SMS messages, numbers from phonebook) - when you try to read
\r
1602 something, what is written there (for example, phonebook),
\r
1603 "SIM card not ready" message is displayed then (and first parameter shows 3).
\r
1604 I noticed, that phone can't display names assigned to numbers in phonebook too
\r
1605 (for example, when you call somebody) and shows, that "Inbox" and "Outbox"
\r
1606 are empty (even, when some messages are saved there).
\r
1608 <p>Later value of parameter changes to 3/5 - I suppose, SIM card clock is
\r
1611 <p>Phone disables it (in test value 3), when communicates with network
\r
1612 (requesting services, sending or receiving SMS messages) because of saving
\r
1613 energy (the same in <a href="faq_net2.htm#NSPS">NSPS</a> state).
\r
1615 <p>When you call to number assigned to name in phonebook (or phone
\r
1616 recognizes incoming number), value to the end of call is equal 3/5
\r
1617 (otherwise it changes to 3). After end of call is always equal 3. Logical
\r
1618 conclusion: after enabling phone saves in own memory checksum for
\r
1619 all numbers from phonebook (it's enought to make for 7 last digits - they're
\r
1620 used to identify number in Nokia phones). If this checksum is the same to
\r
1621 checksum for number, you're calling (or incoming number), phone reads name
\r
1624 <p>And the last observation: without connection (see above) value of first
\r
1625 parameter is equal 3/5 (is some energy loose ? Probably yes... But why counter from
\r
1626 <b><a href="faq_net3.htm#Menu20">test 20</a></b> doesn't show any change in their
\r
1629 <p>When you try to open "Outbox" or "Inbox", phone doesn't enable clock,
\r
1630 when they're empty (that's why I think, that phone saves into own memory
\r
1631 number of saved SMS messages too).
\r
1633 <p>Many information about SIM card are displayed by
\r
1634 <a href="http://www.compelson.cz/simedit.htm">SIMedit</a> (unfortunatelly, in Czech language only :-( )...
\r
1635 Parameters like ATR you can study using SIM Scan (it's on the <a href="http://www.net.yu/~dejan">www.net.yu/~dejan</a>
\r
1636 or <a href="http://members.tripod.com/~dejank/">http://members.tripod.com/~dejank/</a> pages). They both work with
\r
1637 SIM card readers only...
\r
1640 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1642 <td><img SRC="../tip.gif" height=36 width=27></td>
\r
1645 If you want to see "Insert SIM card" and (sometimes) "SIM card rejected"
\r
1646 messaeges, try to make such activities (checked for Nokia 5110):
\r
1648 <p>Press very delicately the locking catch of the battery and start to slide the battery
\r
1649 downwards very slowly (stop, when you will hear silently crack).
\r
1651 <p>In this moment you should see first message and phone will start to inform
\r
1652 about problems with communication with SIM card (you will see "ERROR1" here)...
\r
1657 <p>In Nokia 6185/6188 this test looks like follows:
\r
1660 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1663 TASK0 0134 <br>
\r
1671 <p><a NAME="Menu52"></a><b>Test 52</b>
\r
1672 <br>Reads datafield from SIM card
\r
1675 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1678 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1682 data field <br>
\r
1690 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1693 Use menu to <br>
\r
1696 to SIM-SCM</b></tt></td>
\r
1703 <p>This display reads a binary datafield from SIM card to SIM SCM memory
\r
1704 (SCM = <b>S</b>hort <b>C</b>ode <b>M</b>emory and it means phonebook on SIM card).
\r
1706 <p>Prior using this display the identifier of datafield has to be stored as an
\r
1707 alpha-identifier of SCM location number 34 of SIM memory. The datafield
\r
1708 must be written in hexadecimal notation. The identifiers can be found from
\r
1711 <p>The contents of datafield is stored as a data-identifier of SCM location
\r
1712 number 35 of SIM memory. The contents are displayed in hexadecimal notation.
\r
1713 The maximum length of the datafield is 10 bytes, but the length depends on
\r
1714 the name length of the SIM memory. In case the datafield cannot be read the
\r
1715 alpha-identifier of SCM location is NOT DONE.
\r
1717 <p>The information of how the read succeeded can be read from the SCM location
\r
1718 36 of SIM memory and on the display for a short period.
\r
1720 <p>The following results are possible:
\r
1723 <table cellspacing=4 cellpadding=0>
\r
1724 <tr><td>OK</td><td>datafield was read correctly</td></tr>
\r
1725 <tr><td>NOT BINARY</td><td>datafield is either formatted or cyclic</td></tr>
\r
1726 <tr><td>NOT FOUND</td><td>datafield was not found from SIM card</td></tr>
\r
1727 <tr><td>CARD ERROR</td><td>something weird happened, card did not respond as expected</td></tr>
\r
1728 <tr><td>NO RIGHTS</td><td>not enough rights to read the datafield (PIN2,adm..)</td></tr>
\r
1729 <tr><td>NOT STORED</td><td>could not store into the result memory place</td></tr>
\r
1730 <tr><td>NO ADDRESS</td><td>could not read the address from the SCM-location</td></tr>
\r
1731 <tr><td>UNKNOWN</td><td>unidentified error</td></tr>
\r
1734 <p>For the time being following binary datafields exist in SIM. In future
\r
1735 there could be more. All of these are not necessarily on all SIM cards.
\r
1738 <table cellspacing=4 cellpadding=0>
\r
1739 <tr><td>2FE2</td><td>ICC identification</td><td>(10 bytes)</td></tr>
\r
1740 <tr><td>6F05</td><td>Language preference</td><td>(variable length)</td></tr>
\r
1741 <tr><td>6F07</td><td><a href="faq_net1.htm#IMSI">IMSI</a></td><td>(9 bytes)</td></tr>
\r
1742 <tr><td>6F20</td><td>Ciphering key Kc (it's read from card after entering PIN)</td><td>(9 bytes)</td></tr>
\r
1743 <tr><td>6F30</td><td><a href="faq_net1.htm#PLMN">PLMN</a> selector</td><td>(variable length)</td></tr>
\r
1744 <tr><td>6F31</td><td>HPLMN (home network ?) search period</td><td>(1 byte)</td></tr>
\r
1745 <tr><td>6F37</td><td>ACM maximum value</td><td>(3 bytes)</td></tr>
\r
1746 <tr><td>6F38</td><td>SIM service table</td><td>(2-4 bytes)</td></tr>
\r
1747 <tr><td>6F41</td><td>Price per unit and currency table</td><td>(5 bytes)</td></tr>
\r
1748 <tr><td>6F45</td><td>Cell broadcast message identifier selection</td><td>(variable length)</td></tr>
\r
1749 <tr><td>6F74</td><td>Broadcast control channels</td><td>(16 bytes)</td></tr>
\r
1750 <tr><td>6F78</td><td>Access control class</td><td>(2 bytes)</td></tr>
\r
1751 <tr><td>6F7B</td><td>Forbidden <a href="faq_net1.htm#PLMN">PLMNs</a> (see <a href="faq_net2.htm#Menu7">test 7</a>)</td><td>(12 bytes)</td></tr>
\r
1753 <tr><td>6F7E</td><td>Location information
\r
1754 (<a href="faq_net3.htm#Menu10">TMSI</a>,
\r
1755 <b>L</b>ocal <b>A</b>rea <b>I</b>nformation (consist of MCC, MNC & LAC -
\r
1756 see <a href="faq_net3.htm#Menu11">test 11</a> for them),
\r
1757 last <a href="faq_net1.htm#LocationUpdate">Location Update</a> status)</td><td>(11 bytes)</td></tr>
\r
1759 <tr><td>6FAD</td><td>Administrative data</td><td>(variable length)</td></tr>
\r
1760 <tr><td>6FAE</td><td>Phase identification</td><td>(1 byte)</td></tr>
\r
1761 <tr><td>6F43</td><td>SMS status</td><td>(variable length)</td></tr>
\r
1762 <tr><td colspan=3> <p>Next two binary datafields are phase 2+ features which are not currently in use<p> </td></tr>
\r
1763 <tr><td>6F3E</td><td>Group Identifier Level 1</td><td>(variable length)</td></tr>
\r
1764 <tr><td>6F3F</td><td>Group Identifier Level 2</td><td>(variable length)</td></tr>
\r
1767 <p>In Nokia 6185/6188 this test looks like follows:
\r
1770 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1773 TASK4 0134 <br>
\r
1781 <p><a NAME="Menu53"></a><b>Test 53</b>
\r
1782 <br>Writes datafield into SIM card
\r
1785 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1788 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1791 Write<br>
\r
1792 data field<br>
\r
1794 to SIM</tt></td>
\r
1800 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1814 <p>This display writes data for a binary datafield in SIM card by using data
\r
1815 in SCM memory of SIM card.
\r
1817 <p>Prior using this display the identifier of datafield has to be stored as an
\r
1818 alpha-identifier of SCM location number 34 of SIM memory. The datafield
\r
1819 must be written in hexadecimal notation. The identifiers can be found from
\r
1820 the GSM 11.11. In addition the data to be stored into SIM card has to be
\r
1821 entered as an alpha-identifier of SCM location number 35 of SIM memory.
\r
1822 The data has to be stored in hexadecimal notation.
\r
1824 <p>The result of write operation can be seen from the alpha-identifier of
\r
1825 SCM-location 36 of SIM-memory and on the display for a short period.
\r
1827 <p>The following results are possible:
\r
1830 <table cellspacing=4 cellpadding=0>
\r
1831 <tr><td>OK</td><td>datafield was read correctly</td></tr>
\r
1832 <tr><td>NOT BINARY</td><td>datafield is either formatted or cyclic</td></tr>
\r
1833 <tr><td>NOT FOUND</td><td>datafield was not found from SIM card</td></tr>
\r
1834 <tr><td>CARD ERROR</td><td>something weird happened, card did not respond as expected</td></tr>
\r
1835 <tr><td>NO RIGHTS</td><td>not enough rights to read the datafield (PIN2,adm..)</td></tr>
\r
1836 <tr><td>DATA ERROR</td><td>the data contents in SCM location is coded wrongly</td></tr>
\r
1837 <tr><td>NOT STORED</td><td>could not store into the result memory place</td></tr>
\r
1838 <tr><td>NO ADDRESS</td><td>could not read the address from the SCM location</td></tr>
\r
1839 <tr><td>UNKNOWN</td><td>unidentified error</td></tr>
\r
1842 <p>If you want to see changes, often you have to restart your phone.
\r
1844 <p>In Nokia 6185/6188 this test looks like follows:
\r
1847 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1850 TASK8 0134 <br>
\r
1858 <p><a NAME="Menu54"></a><b>Test 54</b>
\r
1859 <br>Information about memory blocks
\r
1862 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1865 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1867 <td><tt>aa bb aa bb<br>
\r
1868 aa bb aa bb<br>
\r
1869 aa bb aa bb<br>
\r
1870 aa bb aa bb</tt></td>
\r
1876 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1878 <td><tt><b>ResF1 ResF2<br>
\r
1879 ResF3 ResF4<br>
\r
1880 ResF5 ResF6<br>
\r
1881 ResF7 ResF8</b></tt></td>
\r
1888 <p>Meaning of the individual lines (information about another blocks):
\r
1900 <li>aa - number of reserved blocks</li>
\r
1901 <li>bb - number of free blocks in worst case</li>
\r
1904 <p>In Nokia 6185/6188 this test looks like follows:
\r
1907 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1910 TASK12 0134 <br>
\r
1918 <p><a NAME="Menu55"></a><b>Test 55</b>
\r
1919 <br>Information about memory blocks (some phones don't have this test -
\r
1920 they don't have such big memory)
\r
1923 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1926 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1928 <td><tt>aa bb aa bb<br>
\r
1929 aa bb aa bb<br>
\r
1930 aa bb aa bb<br>
\r
1931 aa bb aa bb</tt></td>
\r
1937 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1939 <td><tt><b>ResF9 ResF10<br>
\r
1942 ResF15ResF16</b></tt></td>
\r
1949 <p>Meaning of the individual lines (information about another blocks):
\r
1961 <li>aa - number of reserved blocks</li>
\r
1962 <li>bb - number of free blocks in worst case</li>
\r
1965 <p>In Nokia 7110 counters end on ResF11, in 6210/6250 on ResF15.
\r
1967 <p>In Nokia 3110 this test looks like <b><a href="#Menu56">test 56</a></b>.
\r
1969 <p>In Nokia 8210/3310 help to this test is a little
\r
1970 different (another firmware "bug" ? ;-))):
\r
1973 <center><table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
1976 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
1990 </tr></table></center>
\r
1992 <p>and values are displayed in first line only...
\r
1994 <p><a NAME="Menu56"></a><b>Test 56</b>
\r
1998 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
2001 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
2003 <td><tt> aaaaaa bbb <br>
\r
2011 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
2013 <td><tt><b> Ptr Cntr <br>
\r
2015 </b></tt></td>
\r
2025 aaaaaa - pointer to memory where double deallocation was called, in hex
\r
2029 bbb - counter for failed deallocations.</li>
\r
2032 cccccccc - name of task which last tried to double deallocate a block
\r
2033 (you can find their list in <a href="#Menu35"><b>test 35</b></a> description).
\r
2035 <!--(np. "OS IDLE", "UNKNOWN" (nieznane) albo "NONETASK" (dwa ostatnie
\r
2036 pokazuj± siê po naci¶niêciu klawisza)) -->
\r
2041 <p>This test has correct values only, when counter bbb is different from 0.
\r
2043 <p>In Nokia 3110 it looks like <b><a href="#Menu57">test 57</a></b>.
\r
2045 <p><a NAME="Menu57"></a><b>Test 57</b>
\r
2046 <br>Memory status before reset
\r
2049 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
\r
2052 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
2054 <td><tt>aaaaaaaaaaaa<br>
\r
2063 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
2065 <td><tt><b> Status of<br>
\r
2067 Block sets <br>
\r
2068 </b></tt></td>
\r
2078 aaaaaa... - Status of each stack before reset. First position contains
\r
2079 the status of stack 0, second position the status of
\r
2080 stack 1 and so on. The last position contains the status
\r
2081 of System stack. Number of stacks depends on the current
\r
2082 configuration of software. Possible values for each stack are:
\r
2086 <li>0: status OK, no overflow - <b>it's normally !</b></li>
\r
2087 <li>1: status not OK, stack overflow</li>
\r
2093 bbbbbbb - status of each block set before reset. First position
\r
2094 contains the status of block set 1, second position the
\r
2095 status of block set 2 and so on. Possible values for each
\r
2100 <li>0: status OK</li>
\r
2101 <li>1: block set full - <b>it's normally !</b></li>
\r
2102 <li>2: (de)allocation error or total memory corruption</li>
\r
2108 <p>This display is only valid when a unknown or
\r
2109 a stack overflow interrupt has occured. In some phones you can make
\r
2110 restart connected with stack overflow (see <a href="faq_net0.htm#9">question 9</a>)
\r
2111 and see this test in "action"...
\r
2113 <p>In Nokia 6210 this test is bigger and displayed on full screen...
\r
2115 <p>In Nokia 6185/6188 this test is different:
\r
2118 <table BORDER CELLSPACING=0 CELLPADDING=0 >
\r
2131 <font class="drukuj">
\r
2132 <br><a class="shref" href="#Top"><small><em>Back to the top</em></small></a><br>
\r
2135 <p><a href="faq_net0.htm">[Part 1]</a><a href="faq_net1.htm">[Part 2]</a><a href="faq_net2.htm">[Part 3]</a><a href="faq_net3.htm">[Part 4]</a><b>[Part 5]</b><a href="faq_net5.htm">[Part 6]</a><a href="faq_net6.htm">[Part 7]</a>
\r
2137 <hr size="2" noshade width="60%" align="center" style="color: #004080">
\r
2140 <br><p align="RIGHT"><font class='autor' size='1'><a class="autoremail" href="mailto:Marcin Wiacek<Marcin-Wiacek@topnet.pl>">Marcin Wiacek</a> (<a class="autoremail" href="http://marcin-wiacek.topnet.pl">WWW</a>)
\r
2141 <br>Last modifcation: 5 January 2002</font>
\r
git://git.jankratochvil.net / gnokii.git / blob