3 <meta name="Author" content="Marcin Wiacek">
4 <meta name="Description" content="NOKIA NetMonitor description (English version)">
5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6 <meta name="language" content="us">
7 <meta name="revisit-after" content="15 days">
8 <meta name="Robots" content="all">
9 <meta name="KeyWords" content="3110, 9110, GSM, DCS, Nokia, 3210, 5110, 5130, 6110, 6130, 6150, 8810, FAQ, NetMonitor, Marcin, Wiacek, Marcin Wiacek">
10 <title>NetMonitor in Nokia phones (5/7)</title>
11 <link rel="stylesheet" href="../styl.css" type="text/css">
13 <body bgcolor="#FFFFFF" text="#2B2B69" link="#525FF5" vlink="#525FF5" alink="#2FA030">
16 <p align="RIGHT"><a class="autoremail" href="../index.html">Main page</a></p>
18 <center><font color="#1F409F" size=+2 class="tytul">NetMonitor in Nokia phones (5/7)</font>
20 <p><a href="faq_net0.html">[Part 1]</a><a href="faq_net1.html">[Part 2]</a><a href="faq_net2.html">[Part 3]</a><a href="faq_net3.html">[Part 4]</a><b>[Part 5]</b><a href="faq_net5.html">[Part 6]</a><a href="faq_net6.html">[Part 7]</a>
24 <hr noshade width="60%" style="color: #004080" align=center>
29 <li><a href="faq_net0.html#1"><b>What is it ?</b></a></li>
30 <li><a href="faq_net0.html#2"><b>Do I need it ?</b></a></li>
31 <li><a href="faq_net0.html#3"><b>Does my phone use more power with NetMonitor enabled ?</b></a></li>
32 <li><a href="faq_net0.html#4"><b>How to activate it ?</b></a></li>
33 <li><a href="faq_net0.html#5"><b>Which NetMonitor version can be activated in my phone ?</b></a></li>
34 <li><a href="faq_net0.html#6"><b>Does NetMonitor activation void warranty ?</b></a></li>
35 <li><a href="faq_net0.html#7"><b>NetMonitor menu in my phone has different number than 10. Is it normal ?</b></a></li>
36 <li><a href="faq_net0.html#8"><b>NetMonitor menu in my phone has 11 number, hovewer previous position has 9 number. Is it normal ?</b></a></li>
37 <li><a href="faq_net0.html#9"><b>How to use it ?</b></a></li>
38 <li><a href="faq_net0.html#10"><b>Can I damage my phone ?</b></a></li>
39 <li><a href="faq_net1.html#11"><b>Glossary</b></a></li>
40 <li><a href="faq_net2.html#12"><b>Description of the individual tests</b></a></li>
41 <li><a href="faq_net6.html#13"><b>You can also use a program...</b></a></li>
42 <li><a href="faq_net6.html#14"><b>Can I use NetMonitor without SIM card inserted, without PIN number entered or when SIM card is not active ?</b></a></li>
43 <li><a href="faq_net6.html#15"><b>How can I disable NetMonitor ?</b></a></li>
44 <li><a href="faq_net6.html#16"><b>Do I need to disable NetMonitor before sending my phone to the service ?</b></a></li>
45 <li><a href="faq_net6.html#17"><b>Is it possible to re-activate NetMonitor after disabling it ?</b></a></li>
46 <li><a href="faq_net6.html#18"><b>Is NetMonitor available in analog Nokia phones ?</b></a></li>
47 <li><a href="faq_net6.html#19"><b>Does NetMonitor allow to use phone like broadcast station ?</b></a></li>
48 <li><a href="faq_net6.html#20"><b>I don't have all described tests in my phone. Why ? Can I increase their number ?</b></a></li>
49 <li><a href="faq_net6.html#21"><b>Does NetMonitor allow to identify place, where is my interlocutor ?</b></a></li>
50 <li><a href="faq_net6.html#22"><b>Does NetMonitor allow to identify place, where am I ?</b></a></li>
51 <li><a href="faq_net6.html#23"><b>What are NetMonitor codes ?</b></a></li>
52 <li><a href="faq_net6.html#24"><b>Is it the truth, that in phones with additional hardware changing frequency band NetMonitor doesn't work correct ?</b></a></li>
53 <li><a href="faq_net6.html#25"><b>Where can I find description of FBUS/MBUS protocol and commands connected with NetMonitor ?</b></a></li>
54 <li><a href="faq_net6.html#Literatura"><b>Information sources</b></a></li>
55 <li><a href="faq_net6.html#27"><b>Additional information</b></a></li>
57 <hr size="2" noshade width="60%" align="center" style="color: #004080">
60 <p><a NAME="Menu30"></a><b>Menu 10-30</b>
61 <br>Audio API register display
64 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
67 <table BORDER CELLSPACING=0 CELLPADDING=0 >
69 <td><tt> aaaa bbbb<br>
72 gggg hhhh </tt></td>
78 <table BORDER CELLSPACING=0 CELLPADDING=0 >
80 <td><tt><b>A1Cnf A2Cnf<br>
81 ST AU3<br>
83 Conf HFVol</b></tt></td>
92 <li>aaaa - API_AUD1_CTRL</li>
93 <li>bbbb - API_AUD2_CTRL</li>
94 <li>cccc - API_SIDETONE</li>
95 <li>dddd - API_AU3</li>
96 <li>eeee and ffff - API_1_TONE and API_2_TONE (see description below)</li>
99 gggg - API_CONFIG: connected with sound setting from
100 <b><a href="faq_net5.html#Menu71_72">Menu 10-71 and 10-72</a></b>:
101 you will see here number (hexadecimal),
102 which was displayed there below AUDIO ENHANCEMENT (in last selected menu).
103 Here are some examples:
106 <table BORDER CELLSPACING=0 CELLPADDING=0 >
107 <tr ALIGN=CENTER><td><b>normally (for example during standby)</b></td><td><b>wybieranie numeru</b></td><td><b>call</b></td></tr>
108 <tr ALIGN=CENTER><td>5148 (cracks) - 20808 decimal</td><td>5149</td><td>5140</td></tr>
109 <tr ALIGN=CENTER><td>851A - 34074 decimal</td><td>851B</td><td>8512</td></tr>
110 <tr ALIGN=CENTER><td>C6A4 (cracks) - 50852 decimal</td><td>C6AD</td><td>C6A4</td></tr>
111 <tr ALIGN=CENTER><td>DB34 (cracks) - 56116 decimal</td><td>DB3D</td><td>DB34</td></tr>
112 <tr ALIGN=CENTER><td>DF29 (after enabling phone) - 57129 decimal</td><td>DF29</td><td>DF20</td></tr>
113 <tr ALIGN=CENTER><td>F436 - 62518 decimal</td><td>F43F</td><td>F436</td></tr>
114 <tr ALIGN=CENTER><td>F437 - 62519 decimal</td><td>F43F</td><td>F436</td>
121 <p>hhhh - API_HF_VOL: volume during call - you will count it from
122 the "110 - hhhh" formula (subtract value of this parameter from 110).
123 It's displayed too (during call only) in
124 <b><a href="faq_net5.html#Menu76">Menu 10-76</a></b>.
125 When you connect headset, values here change - volume can be count
126 from "510 - hhhh" formula then (for car kit use "2210 - hhhh").
127 Type of connected audio accesories can be checked in
128 <a href="faq_net5.html#Menu75"><b>Menu 10-75</b></a> too.
129 Phone remembers volume for each audio accesory separately.
133 <p>When you press any key, phone generates sound, which consist of two tones.
134 Parameters eeee and ffff change then. First tone is short, second is emited
135 all time, when you press key. When you press C, NaviKey, Up or Down
136 keys, change parameter eeee only (value 0E10 - 3600 decimal) -
137 sound consist of one tone only. And now the most important thing:
138 you will divide displayed in these parameters values by 4,
139 you will have frequencies in Hz conncected with pressing adequate keys in
140 DTMF (<b>D</b>ual <b>T</b>one <b>M</b>ulti <b>F</b>requency) system.
141 I think, you use DTMF very often - it's used in tone system in all
142 modern phones during calling number. Adequate values are in table (decimal)
143 - parameter eeee is connected with vertical values, ffff with horizontal:
146 <table BORDER CELLSPACING=0 CELLPADDING=0 >
147 <tr ALIGN=CENTER><td></td><td>1209 Hz</td><td>1336 Hz</td><td>1477 Hz</td></tr>
148 <tr ALIGN=CENTER><td>697 Hz</td><td>1</td><td>2</td><td>3</td></tr>
149 <tr ALIGN=CENTER><td>770 Hz</td><td>4</td><td>5</td><td>6</td></tr>
150 <tr ALIGN=CENTER><td>852 Hz</td><td>7</td><td>8</td><td>9</td></tr>
151 <tr ALIGN=CENTER><td>941 Hz</td><td>#</td><td>0</td><td>*</td></tr>
154 <p><a NAME="Menu34"></a><b>Menu 10-34</b>
155 <br>Information about FBUS connection between phone and computer.
158 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
161 <table BORDER CELLSPACING=0 CELLPADDING=0 >
163 <td><tt>aa bb cc dd<br>
165 hhh iii jjj <br>
172 <table BORDER CELLSPACING=0 CELLPADDING=0 >
174 <td><tt><b>CM LD LM NM <br>
176 ACC RXS TXS <br>
186 <li>aa - current fbus media in hex</li>
187 <li>bb - last sender dev in hex</li>
188 <li>cc - last sender media in hex</li>
189 <li>dd - next media to be connected. Same as aa if the connection is not pending</li>
190 <li>eee - fbus parity error counter</li>
191 <li>fff - fbus framing error counter</li>
192 <li>ggg - fbus overrun error counter</li>
193 <li>hhh - fbus alive check counter</li>
194 <li>iii - received sequence number</li>
195 <li>jjj - sent sequence number</li>
196 <li>k - phone mode: S=slave, H=host</li>
199 <p>Description above is from some English documents. As you can see in some phones
200 (like Nokia 5110) values in this test looks rather different, but help is the same.
201 But, when you make connection with FBUS cable and make transmission, first line of values
202 in this test changes to "1E0C1E -". When you will look into some
203 <a href="faq_net6.html#25">FBUS protocol descriptions</a>,
207 <li>"1E" could mean datas send with <a href="faq_net6.html#25">FBUS protocol</a> over cable</li>
208 <li>"0C" could mean, that FBUS cable is connected to phone</li>
211 <p>and it's the truth. So, it means, that this description is real (even, that
212 test looks a little different).
214 <p>In Nokia 9110 this menu looks different:
217 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
220 <table BORDER CELLSPACING=0 CELLPADDING=0 >
222 <td><tt>ll mm nn oo <br>
231 <table BORDER CELLSPACING=0 CELLPADDING=0 >
233 <td><tt><b>PA RS DR PR <br>
246 p and q are probably iii and jjj</li>
249 <p>Links to pages with FBUS (MBUS) protocol are in the <a href="faq_net6.html#25">question 25</a>.
252 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
254 <td><img SRC="tip.gif" height=36 width=27 align=LEFT></td>
256 <td>If values in this test changed after enabling phone, it means, that
257 it was connected to computer and datas were transmitted with
258 <a href="faq_net6.html#25">FBUS protocol</a> (not MBUS).</td>
262 <p><a NAME="Menu35"></a><b>Menu 10-35</b>
263 <br>Reason of last reboting internal firmware of phone.
266 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
269 <table BORDER CELLSPACING=0 CELLPADDING=0 >
271 <td><tt> aaaaa <br>
279 <table BORDER CELLSPACING=0 CELLPADDING=0 >
281 <td><tt><b>Reset reason<br>
296 <li>NORM: probably normal power up</li>
297 <li>UNKNO: default value, reset reason is unknown</li>
298 <li>SWSIM: SIM contact failure reset</li>
299 <li>STACK: task stack overflow</li>
300 <li>SWIDL: idle task not running reset</li>
301 <li>HW lub WD: <a href="faq_net1.html#ASIC">ASIC</a> watchdog timeout</li>
302 <li>SWDSP: restart <a href="faq_net1.html#DSP">DSP</a> recovery reset</li>
308 bbbbbbbb - name of running task before reset (for example,
309 <nobr>"AUD TASK"</nobr>,
310 <nobr>"CC TASK"</nobr> (confirmed),
311 <nobr>"DDI TASK"</nobr>,
312 <nobr>"DEV IO"</nobr> (confirmed),
313 <nobr>"EM TASK"</nobr>,
314 "FBUSTASK" (confirmed),
315 <nobr>"L1 CONTR"</nobr>,
316 <nobr>"L1 MEAS"</nobr>,
317 <nobr>"L1 SYSPA"</nobr> (confirmed),
318 <nobr>"L2 TASK"</nobr>,
319 "LOCAL" (potwierdzone),
320 <nobr>"MDI RECE"</nobr> (confirmed),
321 <nobr>"MDI SEND"</nobr> (confirmed),
322 <nobr>"MM TASK"</nobr> (confirmed),
323 <nobr>"OS IDLE"</nobr> (confirmed),
324 <nobr>"PN TASK"</nobr> (confirmed),
325 <nobr>"RR TASK"</nobr> (confirmed),
326 <nobr>"RM TASK"</nobr>,
327 <nobr>"SIM L2"</nobr> (confirmed),
328 <nobr>"SIM UPL"</nobr> (confirmed),
329 <nobr>"SMS TASK"</nobr> (confirmed),
331 <nobr>"UI TASK"</nobr> (confirmed)
332 or "UNKNOWN" (confirmed)). We can notice, that tasks names are similiar to
333 names in help to <a href="faq_net5.html#Menu84_86">tests 84-86</a>.</li>
336 <p><a NAME="Menu36"></a><b>Menu 10-36</b>
337 <br>Reasons of last reboting internal firmware of phone (you will
338 find here information, how many times phone made restarts because of reasons
342 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
345 <table BORDER CELLSPACING=0 CELLPADDING=0 >
347 <td><tt> aa bb cc <br>
348 dd ee ff<p>
355 <table BORDER CELLSPACING=0 CELLPADDING=0 >
357 <td><tt><b> UN WD DSP <br>
368 <li>aa - unknown resets</li>
369 <li>bb - <a href="faq_net1.html#ASIC">ASIC</a> watchdog timeout resets (in some
370 you can simulate it - see <a href="faq_net0.html#9">question 9</a> for details)</li>
371 <li>cc - <a href="faq_net1.html#DSP">DSP</a> recovery resets</li>
374 dd - some English descriptions say, that it's connected with
375 SIM contact failure reset (in some phones you can force reset because of this reason
376 - see <a href="faq_net0.html#9">question 9</a>). I noticed too, that this counter
377 increases when to try to enter mastercode connected with simlock level 1
378 using <b>#pw+2222222222+1#</b> code (where mastercode is instead of 2222222222).
381 <li>ee - idle task not running resets</li>
383 <li>ff - task stack overflow resets</li>
386 <p>Counters are stored to EEPROM.
389 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
391 <td><img SRC="tip.gif" height=36 width=27 align=LEFT></td>
393 <td>You can reset counters from this menu using some Nokia service programs
394 - for example, in Pc-Locals 1.3 enter to menu 8 ("Event Trace"),
395 menu 5 ("Permanent Counter Table...") and press F6 key ("Clear Counters").
396 Unfortunatelly :(, "real" counters connected with mastercode entering attempts
397 (Counter for example in WinTesla and WinLock) don't reset then...
402 <p><a NAME="Menu38"></a><b>Menu 10-38</b>
406 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
409 <table BORDER CELLSPACING=0 CELLPADDING=0 >
411 <td><tt>aaaaaaaaaaaa<br>
414 aaaaaaaaaaaa</tt></td>
420 <table BORDER CELLSPACING=0 CELLPADDING=0 >
422 <td><tt><b>Memory dump <br>
433 <li>aaaa.... - hex dump of 24 successive memory locations</li>
436 <p>The start address of the dump is entered as 6 digit address value
437 into location 30 into phonebook on SIM card (information, how to make it,
438 are in <b><a href="faq_net3.html#Menu17">Menu 10-17</a></b>).
439 An example: for address 0x0C89AB enter 0C2089AB value there...
440 Dump address is changed only when you directly enter to this menu.
442 <p>This display rather is not included in offcial firmware (I found only one
443 phone with it). It can be switched on by defining flag DEV_FT_MEMORY_DUMP_IN_USE in ftd_conf.h.
445 <p><a NAME="Menu39"></a><b>Menu 10-39</b>
446 <br>Reason of last connection end (asterisk means, that the diagnosis won't be sent to the
447 network - it'll be only shown in phone) and making
448 <a href="faq_net1.html#LocationUpdate">Location Update</a>:
451 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
454 <table BORDER CELLSPACING=0 CELLPADDING=0 >
456 <td><tt> CC: aaa <br>
457 MM: bbb<br>
458 RR: ccc<br>
465 <table BORDER CELLSPACING=0 CELLPADDING=0 >
467 <td><tt><b>CC CauseValu<br>
480 reason from the CallControl-Layer - it's displayed in
481 <b><a href="faq_net2.html#Menu2">Menu 10-2</a></b> and
482 <b><a href="faq_net5.html#Menu63">Menu 10-63</a></b> too:
487 from the GSM specifications (section 10.5.4.11/GSM 04.08):
492 <tt> 1</tt>: unassigned (unallocated) number</li>
495 <tt> 3</tt>: no route to destination</li>
498 <tt> 8</tt>: operator determined barring</li>
501 <tt>16</tt>: normal end of call (you were speaking or you heard some
502 text - that dialled number was busy or something similiar)
506 <tt>17</tt>: user busy
511 if it was outgoing call, dialled number was busy (phone even displayed
515 if it was incoming call, a man, who dialled to you, heard busy signal
516 - you were speaking or you rejected it (in Nokia 5110 or 5130 to make
517 it you have to press C key, in Nokia 6110, 6130 or 6150 red receiver)
524 <tt>18</tt>: no user responding</li>
527 <tt>19</tt>: user alerting (from specification - I had it
528 with normal connection too (phone displayed
529 'No answer' ('Nie odpowiada')) or when incoming call was diverted to
530 voice mailbox), no answer
534 <tt>21</tt>: call rejected
539 phone wasn't in network coverage (message 'No coverage network'), when you
544 you tried to call to non existing phone number or you heard busy signal
551 <tt>22</tt>: number changed</li>
554 <tt>27</tt>: destination out of order</li>
557 <tt>28</tt>: invalid number format/number incomplete</li>
560 <tt>31</tt>: unspecidied. It seems, that with this error connection
561 is end by network (for example, when it's overcharged)</li>
564 <tt>34</tt>: no circuit/channel available to make call. Phone displayed
565 'Network busy'. I noticed too, that in my network RR value changed to
566 1 with this error. More about situations, when network is busy, I write
567 in <a href="faq_net2.html#TS">TS description</a>.</li>
570 <tt>38</tt>: network out of order</li>
573 <tt>41</tt>: temporary failure</li>
576 <tt>42</tt>: switching equipment congestion</li>
579 <tt>44</tt>: requested channel not available</li>
582 <tt>47</tt>: ressource unavailable. I had it, when connection was "brutal" broken.
583 Concrete: during call phone of my interlocutor disabled because of empty battery.
584 My phone displayed 'Error in connection'</li>
587 <tt>50</tt>: requested facility not subscribed
588 (you must subscribe it to use it)</li>
591 <tt>65</tt>: bearer service not implemented</li>
594 <tt>68</tt>: ACM equal to or greater than ACMmax</li>
597 <tt>69</tt>: requested facility not implemented</li>
600 <tt>88</tt>: incompatible destination</li>
607 from mine (and not only) experiences:
613 <tt>79</tt>: error with message 'Check operator services'.
614 You have it, when you enable ALS (<b>A</b>lternative <b>L</b>ine <b>S</b>ervice) function,
615 don't have second number on SIM card, select it and try to make call
625 reason from the MobilityManagement-Layer
626 - it's shown in <b><a href="faq_net5.html#Menu64">Menu 10-64</a></b> too.
627 It's from GSM specification (section 10.5.3.6/GSM 04.08):
632 <tt> 2</tt>: <a href="faq_net1.html#IMSI">IMSI</a> unknown in <a href="faq_net1.html#HLR">HLR</a>
633 (SIM card not active in network)</li>
636 <tt> 3</tt>: illegal phone</li>
639 <tt> 4</tt>: <a href="faq_net1.html#IMSI">IMSI</a> unknown in <a href="faq_net1.html#VLR">VLR</a></li>
642 <tt> 5</tt>: phone's <a href="faq_net1.html#IMEI">IMEI</a> was not accepted</li>
645 <tt> 6</tt>: illegal ME</li>
648 <tt>11</tt>: <a href="faq_net1.html#PLMN">PLMN</a> not allowed (you tried to log into
649 network, which doesn't have roaming convention with your home network - your phone
650 displays 'No access', when you try to select it manually; I don't know only, if
651 this code is displayed only, when this network is saved on forbidden list on SIM
652 card (see <b><a href="faq_net2.html#Menu6">Menu 10-6</a></b>)</li>
655 <tt>12</tt>: Location Area not allowed. You can check it in <b><a href="faq_net3.html#Menu11">Menu 10-11</a></b>.</li>
658 <tt>13</tt>: roaming not allowed in this Location Area</li>
661 <tt>17</tt>: network failure</li>
664 <tt>22</tt>: network congestion</li>
667 <tt>32</tt>: service option not supported</li>
670 <tt>33</tt>: service option not subscribed</li>
673 <tt>34</tt>: service temporarily out of order</li>
676 <tt>38</tt>: call cannot be identified (call RE)<p></li>
681 reason from RadioRessourceManagement-Layer)
682 - see GSM specifications: section 10.5.2.31/GSM 04.08:
687 <tt> 0</tt>: normal release</li>
690 <tt> 1</tt>: unspecified</li>
693 <tt> 2</tt>: channel unacceptable</li>
696 <tt> 3</tt>: timer expired </li>
699 <tt> 4</tt>: no activity on the radio path</li>
702 <tt> 5</tt>: Pre-emptive release</li>
705 <tt> 8</tt>: <a href="#Handover">handover</a> impossible,
706 <a href="faq_net2.html#TA">TA</a> out of range</li>
709 <tt> 9</tt>: channel mode unacceptable</li>
712 <tt> 10</tt>: frequency not implemented</li>
715 <tt> 65</tt>: call already cleared</li>
718 <tt> 97</tt>: message type not compatible with protocol state</li>
721 <tt>101</tt>: no cell allocation available</li>
724 <tt>111</tt>: protocol error unspecified</li>
729 <p>When you will see "*" before third parameter from this test, it means
730 (the most often), that call is in progress. Sometimes phone displays different
731 values - I don't know their meaning :-(.
733 <p>Values of counters are not saved in EEPROM. When phone makes another measure,
734 doesn't reset them (changes only these values during next measure, which are connected
735 with it; doesn't change the rest of them).
738 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
740 <td><img SRC="tip.gif" height=36 width=27></td>
742 <td>This test allows to find, why exactly your phone doesn't want to work
743 - doesn't want to make calls.</td>
747 <p><a NAME="Menu40"></a><b>Menu 10-40</b>
748 <br>Resets <a href="#Handover">handover</a> counters (by direct enter)...
751 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
754 <table BORDER CELLSPACING=0 CELLPADDING=0 >
756 <td><tt> RESET<br>
757 HANDOVER <br>
765 <table BORDER CELLSPACING=0 CELLPADDING=0 >
767 <td><tt><b> Use menu <br>
770 counters</b></tt></td>
777 <p><a NAME="Menu41"></a><b>Menu 10-41</b>
778 <br>Information about <a href="#Handover">handover</a>
780 <p><a NAME="Handover"></a>Handover - it's transfer of radio connection
781 (between phone and cell) from one cell to another (without breaking call).
787 new radio connecting will give better quality (it's parameters are all the time
788 checked by phone and base station)
792 when phone is between few cells and can use "new" cells for him
793 (it frees some place for phones, which can use "old" cell only)
797 <p>When they're problems with transmission, decision about handover is made
798 by phone (otherwise it's made by <a href="faq_net1.html#BSC">BSC</a>).
799 If you enabled using one channel by phone (<b><a href="faq_net3.html#Menu17">Menu 10-17</a></b>),
800 handovers are not made.
802 <p>There are 4 types of handovers:
807 <a NAME="Intra"></a><b>Intra cell - Intra <a href="faq_net1.html#BSC">BSC</a>
808 handover</b> (called <b>handoff</b> too): it's the smallest handover
809 inside one cell. Receiver is "thrown over" from one channel to another
810 (gennerally to another frequency inside one cell). Decision, if it should
811 be done, is made by <a href="faq_net1.html#BSC">BSC</a>.</li>
814 <b>Inter cell - Intra <a href="faq_net1.html#BSC">BSC</a> handover</b>:
815 receiver is moved from one cell to another. Decision about it
816 is made by <a href="faq_net1.html#BSC">BSC</a>. Connection with first cell
817 is broken after moment, when connection with another is made (displacement
818 between two <a href="faq_net1.html#BTS">BTSes</a> inside one
819 <a href="faq_net1.html#BSC">BSC</a>).</li>
822 <b>Inter cell - Inter <a href="faq_net1.html#BSC">BSC</a> handover</b>:
823 displacement of connection between two cells, which are not served by
824 the same <a href="faq_net1.html#BSC">BSC</a>. In this case handover is moved
825 by <a href="faq_net1.html#MSC">MSC</a>, but decision about it made
826 by first <a href="faq_net1.html#BSC">BSC</a>. Connection with first
827 <a href="faq_net1.html#BSC">BSC</a> (and <a href="faq_net1.html#BTS">BTS</a>)
828 is broken before moment, when connection with another <a href="faq_net1.html#BSC">BSC</a>
829 (and <a href="faq_net1.html#BTS">BTS</a>) is made.
833 <b>Inter <a href="faq_net1.html#MSC">MSC</a> handover</b>: receiver moves from
834 cell served by <a href="faq_net1.html#MSC">MSC</a>/<a href="faq_net1.html#VLR">VLR</a>
835 to another controlled by another <a href="faq_net1.html#MSC">MSC</a>/<a href="faq_net1.html#VLR">VLR</a>.
836 It's more complicated situation. We can notice, that
837 <a href="faq_net1.html#MSC">MSC</a> is connected to GSMc over PSTN.
838 In this case is visible, that another <a href="faq_net1.html#MSC">MSC</a>
839 can't receive information from first normally.
841 <p>What will happen, when connection will be moved to target
842 <a href="faq_net1.html#MSC">MSC</a>/<a href="faq_net1.html#VLR">VLR</a> ?
844 <p>Because both <a href="faq_net1.html#MSC">MSC</a> belongs to the same network,
845 connection is kept. To move it from one to another <a href="faq_net1.html#MSC">MSC</a>
846 special number HON (HON=CC+NDC+SN, CC - country code, NDC - network code,
847 SN - subscriber's number) must be generated. It's similiar to roaming number
848 (it's connection between two <a href="faq_net1.html#MSC">MSC</a> too). During
849 handover between two <a href="faq_net1.html#MSC">MSC</a> connection can't be
850 broken (phone connection realised by network's subscriber).
854 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
857 <table BORDER CELLSPACING=0 CELLPADDING=0 >
859 <td><tt>HandOOk: aaa<br>
862 HOIntra: ddd</tt></td>
868 <table BORDER CELLSPACING=0 CELLPADDING=0 >
870 <td><tt><b>HandOvOKCntr<br>
873 HOIntraOKCnt</b></tt></td>
883 aaa - counter for successful <a href="#Handover">handovers</a></li>
886 bbb - counter for successful back to previous channel attempts
887 (number of actual used channel is displayed, for example, in
888 <b><a href="faq_net2.html#Menu1">Menu 10-1</a></b>)</li>
891 ccc - counter for failed <a href="#Handover">handovers</a></li>
893 <li>ddd - counter for successful <a href="#Intra">Intra cell - Intra BSC</a> <a href="#Handover">handovers</a>
897 <p>Counters will stop when they reach their maximum (999). To initialize them
898 to zero, use <b><a href="#Menu40">Menu 10-40</a></b> (or
899 <b><a href="faq_net5.html#Menu60">Menu 10-60</a></b>).
901 <p>In dual phones (like Nokia 6150 or 3210) <b>Menu 10-41</b> looks
902 different and is connected with Inter cell - Intra BSC,
903 Inter cell - Inter BSC and Inter MSC <a href="#Handover">handovers</a>:
906 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
909 <table BORDER CELLSPACING=0 CELLPADDING=0 >
911 <td><tt> aaaa bbbb<br>
912 cccc dddd<br>
914 iiijjjkkklll</tt></td>
920 <table BORDER CELLSPACING=0 CELLPADDING=0 >
922 <td><tt><b>G>G InterD>D<br>
923 G>D OK D>G<br>
925 BackToPrev</b></tt></td>
934 <li>aaa - counter of successful <a href="#Handover">handovers</a> from GSM 900 to GSM 900</li>
935 <li>bbb -counter of successful <a href="#Handover">handovers</a> from GSM 1800 to GSM 1800</li>
936 <li>ccc - counter of successful <a href="#Handover">handovers</a> from GSM 900 to GSM 1800</li>
937 <li>ddd - counter of successful <a href="#Handover">handovers</a> from GSM 1800 to GSM 900</li>
938 <li>eee - counter of failed <a href="#Handover">handovers</a> from GSM 900 to GSM 900</li>
939 <li>fff - counter of failed <a href="#Handover">handovers</a> from GSM 1800 to GSM 1800</li>
940 <li>ggg -counter of failed <a href="#Handover">handovers</a> from GSM 900 to GSM 1800</li>
941 <li>hhh - counter of failed <a href="#Handover">handovers</a> from GSM 1800 to GSM900</li>
944 iii - counter of successful back to previous channel attempts
945 (number of actual used channel is displayed, for example, in
946 <b><a href="faq_net2.html#Menu1">Menu 10-1</a></b>)
947 from GSM 900 to GSM 900</li>
949 <li>jjj - counter of successful back to previous channel attempts from GSM 1800 to GSM 1800</li>
951 <li>kkk - counter of successful back to previous channel attempts from GSM 900 to GSM 1800</li>
953 <li>lll - counter of successful back to previous channel attempts from GSM 1800 to GSM 900</li>
956 <p>Counters will stop when they reach their maximum (9999 dla dwóch pierwszych
957 linii, 999 dla dwóch ostatnich). To initialize them to zero, use <b><a href="#Menu40">Menu 10-40</a></b>
958 (or <b><a href="faq_net5.html#Menu60">Menu 10-60</a></b>).
960 <p>In Nokia 3110 this test looks like follows:
963 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
966 <table BORDER CELLSPACING=0 CELLPADDING=0 >
968 <td><tt>HandOOk: aaa <br>
969 PrevCh : bbb <br>
970 HONotOK: ccc <br>
977 <table BORDER CELLSPACING=0 CELLPADDING=0 >
979 <td><tt><b>HandOvOKCntr <br>
980 PrevChanCntr <br>
981 HandOvNOKCnt <br>
982 T200Cntr</b></tt></td>
992 eeee - I write about T200 counter in <b><a href="#Menu43">Menu 10-43</a></b></li>
995 <p>and here's for Nokia 6185/6188:
998 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1010 <li>VBAT - battery voltage (/100V)</li>
1011 <li>BTEMP - battery temperature in C</li>
1012 <li>CHG - battery charge status: 1 - charging, 0 - not charging</li>
1015 <p><a NAME="Menu42"></a><b>Menu 10-42</b>
1016 <br>This test is in dual phones (for example, Nokia 6150 or 3210) only
1017 and is connected with first kind of <a href="#Handover">handovers</a>
1018 (<a href="#Intra">Intra cell - Intra BSC</a>):
1021 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1024 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1026 <td><tt> aaaa bbbb<br>
1027 cccc dddd<br>
1029 iiijjjkkklll</tt></td>
1035 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1037 <td><tt><b>G>G IntraD>D<br>
1038 G>D OK D>G<br>
1040 BackToPrev</b></tt></td>
1049 <li>aaaa - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 900</li>
1050 <li>bbbb - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 1800</li>
1051 <li>cccc - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 1800</li>
1052 <li>dddd - counter of successful <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 900</li>
1053 <li>eee - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 900</li>
1054 <li>fff - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 1800</li>
1055 <li>ggg - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 900 to GSM 1800</li>
1056 <li>hhh - counter of failed <a href="#Intra">Intra cell - Intra BSC handovers</a> from GSM 1800 to GSM 900</li>
1059 iii - counter of successful back to previous normal channel
1060 (you can check number of actual used channel for example in
1061 <b><a href="faq_net2.html#Menu1">Menu 10-1</a></b>) attempts
1062 inside one cell (INTRA CELL) from GSM 900 to GSM 900
1066 jjj - counter of successful back to previous normal channel attempts
1067 inside one cell (INTRA CELL) from GSM 1800 to GSM 1800
1071 kkk - counter of successful back to previous normal channel attempts
1072 inside one cell (INTRA CELL) from GSM 900 to GSM 1800</li>
1075 lll - counter of successful back to previous normal channel attempts
1076 inside one cell (INTRA CELL) from GSM 1800 to GSM 900</li>
1079 <p>Counters will stop when they reach their maximum (9999 for two first lines,
1080 999 for two last). To initialize them
1081 to zero, use <b><a href="#Menu40">Menu 10-40</a></b>
1082 (or <b><a href="faq_net5.html#Menu60">Menu 10-60</a></b>).
1084 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.html#Menu20">Menu 10-20</a>.
1086 <p><a NAME="Menu43"></a><b>Menu 10-43</b>
1089 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1092 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1094 <td><tt>T200MS: aaaa<br>
1097 T200BS: dddd</tt></td>
1103 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1105 <td><tt><b>T200 MS GSM <br>
1108 T200 BS DCS</b></tt></td>
1118 aaaa - for GSM 900: counts how many times T200 in phone has expired and
1119 therefore L2 transmission has been repeated.</li>
1122 bbbb - for GSM 900: counts how many times T200 in <a href="faq_net1.html#BTS">BTS</a> (network) has expired
1123 and therefore L2 transmission has been repeated.
1127 cccc - for GSM 1800 called earlier DCS (in dual phones only): counts how many times T200 in phone
1128 has expired and therefore L2 transmission has been repeated.
1132 dddd - for GSM 1800 (in dual phone only): counts how many times T200 in <a href="faq_net1.html#BTS">BTSie</a>
1133 (network) has expired and therefore L2 transmission has been repeated.</li>
1136 <p>Counters will stop when they reach their maximum (9999 for two first lines,
1137 999 for two last). To initialize them to zero, use <b><a href="#Menu40">Menu
1138 10-40</a></b> (or <b><a href="faq_net5.html#Menu60">Menu 10-60</a></b>).
1140 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.html#Menu21">Menu 10-21</a>.
1142 <p><a NAME="Menu44"></a><b>Menu 10-44</b>
1143 <br>You change value from 01 (default) to 00 (or vice versa) by direct enter to this test.
1146 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1149 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1152 <br><tt> REVISION<br>
1153 LEVEL IS aa <br>
1160 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1162 <td><tt><b>Use menu to <br>
1163 change<br>
1165 Level</b></tt></td>
1172 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.html#Menu22">Menu 10-22</a>.
1174 <p><a NAME="Menu45"></a><b>Menu 10-45</b>
1175 <br>This test allows to simulate situations. when phone can normally
1176 receive network signal (but network can't receive any information from phone).
1177 It's very realistic (even in <b><a href="faq_net2.html#Menu1">Menu
1178 10-1</a></b> in ddd parameter an asterisk (*) is displayed, when
1179 you try to make connection), but not always (in
1180 <b><a href="faq_net3.html#Menu10">Menu 10-10</a></b> you will see
1181 'xxxxxxxx' instead of TMSI, when T3212 counter in first
1182 parameter will be expired).
1184 <p>You can change it by direct enter.
1187 <center><table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1190 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1193 <br><tt>TRANSMITTER <br>
1199 <p>(default setting)</td>
1202 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1205 <br><tt>TRANSMITTER <br>
1213 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1215 <td><tt><b>Use menu to <br>
1218 transmitter</b></tt></td>
1226 <table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1228 <td><img SRC="tip.gif" height=36 width=27></td>
1230 <td>When you enable it, phone won't be able, for example, to update
1231 location (see <b><a href="faq_net5.html#Menu64">Menu 10-64</a></b>) and
1232 make calls. It will allow to:
1235 <li>"blockade" phone to the moment of another enabling it (for example,
1236 when you want to observe network parameters, but you don't want to be
1237 accessible for others - when somebody will call to you, for network
1238 your phone will be outside range)
1242 fast remind you of number written to phonebook (it's written on leaf,
1243 but you don't remember name of person assigned to): simple call it.
1244 When phone will choose number, it will display this name; it will be written
1245 on list odf last dialed numbers too.
1252 <p>This test DOESN'T WORK CORRECTLY in Nokia 3210 and 7110 (you change setting,
1253 but it doesn't give described above results).
1255 <p>In Nokia 6185/6188 this test looks like <a href="faq_net3.html#Menu23">Menu 10-23</a>.
1257 <p><a NAME="Menu46"></a><b>Menu 10-46</b>
1260 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1271 <p><a NAME="Menu48"></a><b>Menu 10-48</b>
1272 <br>In Nokia 3110 this test looks like <b><a href="faq_net2.html#Menu7">Menu 10-7</a></b>.
1274 <p><a NAME="Menu51"></a><b>Menu 10-51</b>
1275 <br>Information about SIM card
1278 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1281 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1283 <td><tt>aaa bbb ccc <br>
1285 e f gg hh<br>
1286 i jjjj</tt></td>
1292 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1294 <td><tt><b>VSel Bau SAl<br>
1295 SCond CStop<br>
1296 PIN12 PUK12<br>
1297 ATR FE/PE</b></tt></td>
1307 aa - SIM voltage selection type (3, 3/5 or 5)</li>
1310 bbb - division coefficient, which define speed of communication phone with
1311 SIM card (372, 64, 32 or 0) saved in ATR (first sequence send by SIM card
1312 after reset - <b>A</b>nswer <b>T</b>o <b>R</b>eset).
1313 When you will divide clock frequency (maximal 3,25 MHz = 3 250 000 Hz)
1314 by it, you will have speed of transmission
1315 (for example, 3 250 000 Hz / 372 = 8736,5 bods)</li>
1318 ccc - information, whether SIM clock stop is allowed (it saves energy)
1319 during standby (YES or NOT - possible or not). This information is displayed
1320 (in Nokia phones and not only) using <b>*#SIM0CLOCK#</b> code
1321 - when you will see "SIM clock stop allowed", SIM card allows to make it.
1322 Some Nokia 6110 phones (it depeneds on their firmware) can not support
1323 correctly this code - they display, for example, "Result unknown".
1324 Phone disables SIM card clock automatically - you can't make it manually !
1328 dddd - information about clock stop condition:
1334 <li>DOWN(UP) - in tested by me SIM cards</li>
1342 e - number of left PIN1 code entering attempts. When it's bigger than 9,
1343 you will see only last digit of it (for example, I found some prepaid cards
1344 with 10 value). Maximal number of entering code attempts depends on concrete
1345 SIM card (it can be set to any value), but the most often it's equal 3. In some SIM cards
1346 you can disable answering for this code (for example, you can select it in
1347 <b>Menu 4-3-1</b> in Nokia 5110). When it's equal 0, phone shows
1348 "Sim card blocked" and asks for PUK1. If it was entered correctly, this counter
1349 is reset to maximal value. Disabling and enabling phone doesn't reset it !
1353 f - number of left PIN2 code entering attempts (when SIM card doesn't support
1354 PIN2 functions, you will see "x" here). You can check, if these functions are supported,
1355 using call cost function too (if they're not, phone displays "Not allowed").
1356 If you wanted to use them and your card doesn't support them (you will see "x"
1357 here), you (or your operator ;-) rather) have to change it.
1358 Maximal number of entering code attempts depends on concrete
1359 SIM card (it can be set to any value), but the most often it's equal 3. When this counter
1360 is equal 0, phone asks for PUK2. When this code was entered correctly, counter
1361 is reset to maximal value. Of course, even when it's equal 0, you can normally
1362 use SIM card (PIN2/PUK2 are independent of PIN1/PUK1), when you know PIN1.
1363 Disabling and enabling phone doesn't reset it !
1367 gg - number of left PUK1 code entering attempts.
1368 Maximal number of entering code attempts depends on concrete
1369 SIM card (it can be set to any value), but the most often it's equal 10.
1370 Phone asks for it, when counter of left PIN1 code entering attempts is equal 0
1371 (phone shows "Sim card blocked"). When this counter is equal 0 too, SIM card
1372 can be blocked (phone shows "Sim card rejected") or (it depends on card)
1373 asks for PUK2. When this code was entered correctly, counters of left PIN1 and
1374 PUK1 codes entering attempts are reset to maximal values.
1375 Disabling and enabling phone doesn't reset it !
1379 hh - number of left PUK2 code entering attempts (when SIM card doesn't support
1380 PIN2 functions, you will see "x" here).
1381 Maximal number of entering code attempts depends on concrete
1382 SIM card (it can be set to any value), but the most often it's equal 10.
1383 When it's equal 0, using PIN2 functions can be impossible on this SIM card (ask operator for help).
1384 Additionaly, when you were asked for PUK2, when counters of left PIN1 and
1385 PUK1 codes entering attempts were equal 0 and now left PUK2 code entering attempts
1386 is equal 0 too, using this SIM card can be impossible (you have to replace it to new).
1387 When it was entered correctly, counters for this code and PIN2 (when you entered
1388 PUK2, because PIN2 was blocked) are reset to maximal values or counters for this,
1389 PIN1 and PUK1 are reset (when you entered PUK2, because PIN1 and PUK1 were blocked).
1390 Disabling and enabling phone doesn't reset it !
1394 i - ATR repeat counter (ATR is first sequence sent by SIM card in answet to reset -
1395 <b>A</b>nswer <b>T</b>o <b>R</b>eset) (0-9)</li>
1398 jjjj - number of retransmissions/parity errors in transmission with SIM card
1399 (when the happen, two first chars are equals FE (<b>F</b>rame <b>E</b>rror) or
1400 PE (<b>P</b>arity <b>E</b>rror), two last number of retransmission/errors)</li>
1403 <p>CStop parameter (information, if SIM card clock is disabled in this moment)
1404 is displayed in help only. Why ? Probably somebody didn't remember about it...
1406 <p>Here are some observations for SIM voltage selection type (first parameter)
1407 Nokia 5110 and tested SIM cards:
1409 <p>After enabling phone reads some information from SIM card (for example,
1410 number saved on it SMS messages, numbers from phonebook) - when you try to read
1411 something, what is written there (for example, phonebook),
1412 "SIM card not ready" message is displayed then (and first parameter shows 3).
1413 I noticed, that phone can't display names assigned to numbers in phonebook too
1414 (for example, when you call somebody) and shows, that "Inbox" and "Outbox"
1415 are empty (even, when some messages are saved there).
1417 <p>Later value of parameter changes to 3/5 - I suppose, SIM card clock is
1420 <p>Phone disables it (in test value 3), when communicates with network
1421 (requesting services, sending or receiving SMS messages) because of saving
1422 energy (the same in <a href="faq_net2.html#NSPS">NSPS</a> state).
1424 <p>When you call to number assigned to name in phonebook (or phone
1425 recognizes incoming number), value to the end of call is equal 3/5
1426 (otherwise it changes to 3). After end of call is always equal 3. Logical
1427 conclusion: after enabling phone saves in own memory checksum for
1428 all numbers from phonebook (it's enought to make for 7 last digits - they're
1429 used to identify number in Nokia phones). If this checksum is the same to
1430 checksum for number, you're calling (or incoming number), phone reads name
1433 <p>And the last observation: without connection (see above) value of first
1434 parameter is equal 3/5 (is some energy loose ? Probably yes... But why counter from
1435 <b><a href="faq_net3.html#Menu20">Menu 10-20</a></b> doesn't show any change in their
1438 <p>When you try to open "Outbox" or "Inbox", phone doesn't enable clock,
1439 when they're empty (that's why I think, that phone saves into own memory
1440 number of saved SMS messages too).
1442 <p>Many information about SIM card are displayed by
1443 <a href="http://www.compelson.cz/simedit.htm">SIMedit</a> (unfortunatelly, in Czech language only :-( )...
1444 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>
1445 or <a href="http://members.tripod.com/~dejank/">http://members.tripod.com/~dejank/</a> pages). They both work with
1446 SIM card readers only...
1448 <p>In Nokia 6185/6188 this test looks like follows:
1451 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1454 TASK0 0134 <br>
1462 <p><a NAME="Menu52"></a><b>Menu 10-52</b>
1463 <br>Reads datafield from SIM card
1466 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1469 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1473 data field <br>
1481 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1484 Use menu to <br>
1487 to SIM-SCM</b></tt></td>
1494 <p>This display reads a binary datafield from SIM card to SIM SCM memory
1495 (SCM = <b>S</b>hort <b>C</b>ode <b>M</b>emory and it means phonebook on SIM card).
1497 <p>Prior using this display the identifier of datafield has to be stored as an
1498 alpha-identifier of SCM location number 34 of SIM memory. The datafield
1499 must be written in hexadecimal notation. The identifiers can be found from
1502 <p>The contents of datafield is stored as a data-identifier of SCM location
1503 number 35 of SIM memory. The contents are displayed in hexadecimal notation.
1504 The maximum length of the datafield is 10 bytes, but the length depends on
1505 the name length of the SIM memory. In case the datafield cannot be read the
1506 alpha-identifier of SCM location is NOT DONE.
1508 <p>The information of how the read succeeded can be read from the SCM location
1509 36 of SIM memory and on the display for a short period.
1511 <p>The following results are possible:
1514 <table cellspacing=4 cellpadding=0>
1515 <tr><td>OK</td><td>datafield was read correctly</td></tr>
1516 <tr><td>NOT BINARY</td><td>datafield is either formatted or cyclic</td></tr>
1517 <tr><td>NOT FOUND</td><td>datafield was not found from SIM card</td></tr>
1518 <tr><td>CARD ERROR</td><td>something weird happened, card did not respond as expected</td></tr>
1519 <tr><td>NO RIGHTS</td><td>not enough rights to read the datafield (PIN2,adm..)</td></tr>
1520 <tr><td>NOT STORED</td><td>could not store into the result memory place</td></tr>
1521 <tr><td>NO ADDRESS</td><td>could not read the address from the SCM-location</td></tr>
1522 <tr><td>UNKNOWN</td><td>unidentified error</td></tr>
1525 <p>For the time being following binary datafields exist in SIM. In future
1526 there could be more. All of these are not necessarily on all SIM cards.
1529 <table cellspacing=4 cellpadding=0>
1530 <tr><td>2FE2</td><td>ICC identification</td><td>(10 bytes)</td></tr>
1531 <tr><td>6F05</td><td>Language preference</td><td>(variable length)</td></tr>
1532 <tr><td>6F07</td><td><a href="faq_net1.html#IMSI">IMSI</a></td><td>(9 bytes)</td></tr>
1533 <tr><td>6F20</td><td>Ciphering key Kc (it's read from card after entering PIN)</td><td>(9 bytes)</td></tr>
1534 <tr><td>6F30</td><td><a href="faq_net1.html#PLMN">PLMN</a> selector</td><td>(variable length)</td></tr>
1535 <tr><td>6F31</td><td>HPLMN (home network ?) search period</td><td>(1 byte)</td></tr>
1536 <tr><td>6F37</td><td>ACM maximum value</td><td>(3 bytes)</td></tr>
1537 <tr><td>6F38</td><td>SIM service table</td><td>(2-4 bytes)</td></tr>
1538 <tr><td>6F41</td><td>Price per unit and currency table</td><td>(5 bytes)</td></tr>
1539 <tr><td>6F45</td><td>Cell broadcast message identifier selection</td><td>(variable length)</td></tr>
1540 <tr><td>6F74</td><td>Broadcast control channels</td><td>(16 bytes)</td></tr>
1541 <tr><td>6F78</td><td>Access control class</td><td>(2 bytes)</td></tr>
1542 <tr><td>6F7B</td><td>Forbidden <a href="faq_net1.html#PLMN">PLMNs</a> (see <a href="faq_net2.html#Menu7">Menu 10-7</a>)</td><td>(12 bytes)</td></tr>
1544 <tr><td>6F7E</td><td>Location information
1545 (<a href="faq_net3.html#Menu10">TMSI</a>,
1546 <b>L</b>ocal <b>A</b>rea <b>I</b>nformation (consist of MCC, MNC & LAC -
1547 see <a href="faq_net3.html#Menu11">Menu 10-11</a> for them),
1548 last <a href="faq_net1.html#LocationUpdate">Location Update</a> status)</td><td>(11 bytes)</td></tr>
1550 <tr><td>6FAD</td><td>Administrative data</td><td>(variable length)</td></tr>
1551 <tr><td>6FAE</td><td>Phase identification</td><td>(1 byte)</td></tr>
1552 <tr><td>6F43</td><td>SMS status</td><td>(variable length)</td></tr>
1553 <tr><td colspan=3> <p>Next two binary datafields are phase 2+ features which are not currently in use<p> </td></tr>
1554 <tr><td>6F3E</td><td>Group Identifier Level 1</td><td>(variable length)</td></tr>
1555 <tr><td>6F3F</td><td>Group Identifier Level 2</td><td>(variable length)</td></tr>
1558 <p>In Nokia 6185/6188 this test looks like follows:
1561 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1564 TASK4 0134 <br>
1572 <p><a NAME="Menu53"></a><b>Menu 10-53</b>
1573 <br>Writes datafield into SIM card
1576 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1579 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1582 Write<br>
1583 data field<br>
1585 to SIM</tt></td>
1591 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1605 <p>This display writes data for a binary datafield in SIM card by using data
1606 in SCM memory of SIM card.
1608 <p>Prior using this display the identifier of datafield has to be stored as an
1609 alpha-identifier of SCM location number 34 of SIM memory. The datafield
1610 must be written in hexadecimal notation. The identifiers can be found from
1611 the GSM 11.11. In addition the data to be stored into SIM card has to be
1612 entered as an alpha-identifier of SCM location number 35 of SIM memory.
1613 The data has to be stored in hexadecimal notation.
1615 <p>The result of write operation can be seen from the alpha-identifier of
1616 SCM-location 36 of SIM-memory and on the display for a short period.
1618 <p>The following results are possible:
1621 <table cellspacing=4 cellpadding=0>
1622 <tr><td>OK</td><td>datafield was read correctly</td></tr>
1623 <tr><td>NOT BINARY</td><td>datafield is either formatted or cyclic</td></tr>
1624 <tr><td>NOT FOUND</td><td>datafield was not found from SIM card</td></tr>
1625 <tr><td>CARD ERROR</td><td>something weird happened, card did not respond as expected</td></tr>
1626 <tr><td>NO RIGHTS</td><td>not enough rights to read the datafield (PIN2,adm..)</td></tr>
1627 <tr><td>DATA ERROR</td><td>the data contents in SCM location is coded wrongly</td></tr>
1628 <tr><td>NOT STORED</td><td>could not store into the result memory place</td></tr>
1629 <tr><td>NO ADDRESS</td><td>could not read the address from the SCM location</td></tr>
1630 <tr><td>UNKNOWN</td><td>unidentified error</td></tr>
1633 <p>If you want to see changes, often you have to restart your phone.
1635 <p>In Nokia 6185/6188 this test looks like follows:
1638 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1641 TASK8 0134 <br>
1649 <p><a NAME="Menu54"></a><b>Menu 10-54</b>
1650 <br>Information about memory blocks
1653 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1656 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1658 <td><tt>aa bb aa bb<br>
1659 aa bb aa bb<br>
1660 aa bb aa bb<br>
1661 aa bb aa bb</tt></td>
1667 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1669 <td><tt><b>ResF1 ResF2<br>
1670 ResF3 ResF4<br>
1671 ResF5 ResF6<br>
1672 ResF7 ResF8</b></tt></td>
1679 <p>Meaning of the individual lines (information about another blocks):
1691 <li>aa - number of reserved blocks</li>
1692 <li>bb - number of free blocks in worst case</li>
1695 <p>In Nokia 6185/6188 this test looks like follows:
1698 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1701 TASK12 0134 <br>
1709 <p><a NAME="Menu55"></a><b>Menu 10-55</b>
1710 <br>Information about memory blocks (some phones don't have this test -
1711 they don't have such big memory)
1714 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1717 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1719 <td><tt>aa bb aa bb<br>
1720 aa bb aa bb<br>
1721 aa bb aa bb<br>
1722 aa bb aa bb</tt></td>
1728 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1730 <td><tt><b>ResF9 ResF10<br>
1733 ResF15ResF16</b></tt></td>
1740 <p>Meaning of the individual lines (information about another blocks):
1752 <li>aa - number of reserved blocks</li>
1753 <li>bb - number of free blocks in worst case</li>
1756 <p>In Nokia 7110 counters end on ResF11.
1758 <p>In Nokia 3110 this test looks like <b><a href="#Menu56">Menu 10-56</a></b>.
1760 <p><a NAME="Menu56"></a><b>Menu 10-56</b>
1764 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1767 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1769 <td><tt> aaaaaa bbb <br>
1777 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1779 <td><tt><b> Ptr Cntr <br>
1781 </b></tt></td>
1791 aaaaaa - pointer to memory where double deallocation was called, in hex
1795 bbb - counter for failed deallocations.</li>
1798 cccccccc - name of task which last tried to double deallocate a block
1799 (you can find their list in <a href="#Menu35"><b>Menu 10-35</b></a> description).
1801 <!--(np. "OS IDLE", "UNKNOWN" (nieznane) albo "NONETASK" (dwa ostatnie
1802 pokazuj± siê po naci¶niêciu klawisza)) -->
1807 <p>This test has correct values only, when counter bbb is different from 0.
1809 <p>In Nokia 3110 it looks like <b><a href="#Menu57">Menu 10-57</a></b>.
1811 <p><a NAME="Menu57"></a><b>Menu 10-57</b>
1812 <br>Memory status before reset
1815 <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" >
1818 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1820 <td><tt>aaaaaaaaaaaa<br>
1829 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1831 <td><tt><b> Status of<br>
1833 Block sets <br>
1834 </b></tt></td>
1844 aaaaaa... - Status of each stack before reset. First position contains
1845 the status of stack 0, second position the status of
1846 stack 1 and so on. The last position contains the status
1847 of System stack. Number of stacks depends on the current
1848 configuration of software. Possible values for each stack are:
1852 <li>0: status OK, no overflow - <b>it's normally !</b></li>
1853 <li>1: status not OK, stack overflow</li>
1859 bbbbbbb - status of each block set before reset. First position
1860 contains the status of block set 1, second position the
1861 status of block set 2 and so on. Possible values for each
1866 <li>0: status OK</li>
1867 <li>1: block set full - <b>it's normally !</b></li>
1868 <li>2: (de)allocation error or total memory corruption</li>
1874 <p>This display is only valid when a unknown or
1875 a stack overflow interrupt has occured. In some phones you can make
1876 restart connected with stack overflow (see <a href="faq_net0.html#9">question 9</a>)
1877 and see this test in "action"...
1879 <p>In Nokia 6185/6188 this test is different:
1882 <table BORDER CELLSPACING=0 CELLPADDING=0 >
1895 <font class="drukuj">
1896 <br><a class="shref" href="#Top"><small><em>Back to the top</em></small></a><br>
1899 <p><a href="faq_net0.html">[Part 1]</a><a href="faq_net1.html">[Part 2]</a><a href="faq_net2.html">[Part 3]</a><a href="faq_net3.html">[Part 4]</a><b>[Part 5]</b><a href="faq_net5.html">[Part 6]</a><a href="faq_net6.html">[Part 7]</a>
1901 <hr size="2" noshade width="60%" align="center" style="color: #004080">
1904 <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>)
1905 <br>Last modifcation: 4 May 2000</font>