Main page
NetMonitor in Nokia phones (6/7)
[Part 1][Part 2][Part 3][Part 4][Part 5][Part 6][Part 7]
- What is it ?
- Do I need it ?
- Does my phone use more power with NetMonitor enabled ?
- How to activate it ?
- Which NetMonitor version can be activated in my phone ?
- Does NetMonitor activation void warranty ?
- NetMonitor menu in my phone has different number than 10. Is it normal ?
- NetMonitor menu in my phone has 11 number, hovewer previous position has 9 number. Is it normal ?
- How to use it ?
- Can I damage my phone ?
- Glossary
- Description of the individual tests
- You can also use a program...
- Can I use NetMonitor without SIM card inserted, without PIN number entered or when SIM card is not active ?
- How can I disable NetMonitor ?
- Do I need to disable NetMonitor before sending my phone to the service ?
- Is it possible to re-activate NetMonitor after disabling it ?
- Is NetMonitor available in analog Nokia phones ?
- Does NetMonitor allow to use phone like broadcast station ?
- I don't have all described tests in my phone. Why ? Can I increase their number ?
- Does NetMonitor allow to identify place, where is my interlocutor ?
- Does NetMonitor allow to identify place, where am I ?
- What are NetMonitor codes ?
- Is it the truth, that in phones with additional hardware changing frequency band NetMonitor doesn't work correct ?
- Where can I find description of FBUS/MBUS protocol and commands connected with NetMonitor ?
- I have non existing networks on the list of forbidden networks...
- How to check frequency band (900 or 1800 Mhz), where phone work in this moment ?
- Can I use DLR-2/DLR-3 cables for activating netmonitor ?
- Can I activate netmonitor using Init File Editor (Nokia 9110) ?
- Can I force phone to use one frequency band (900 or 1800 Mhz) only ?
- How to change settings in tests ?
- My phone has very short snandby time - it is possible to see the reason of it ?
- Is netmonitor available in English version only ?
- Information sources
- Additional information
- Does using/activating netmonitor cost anything ?
- Does using netmonitor is legall ?
- Which entries on SIM card are used in netmonitor tests ?
- Can I activate netmonitor in 3310 using soft working with 3210 ?
- After activating netmonitor/BTS TEST my phone can't find network...
- Netmonitor shows different battery capacity than info on it...
- NetMonitor in Nokia 6310, 8310,...
Test 58
Test 59
Test 60
FIELD TEST
DISPLAY
COUNTERS
RESET |
|
Use menu to
reset field
test display
counters |
|
By direct enter to this test you can reset counters from
test 41 to test 43 and from
test 61 to test 66.
|
If you reset these counters at the beginning of each month, you can compare
the number of sent SMSes (test 65)
and made calls (test 63) with your billing.
Additionaly (in some prepaid cards - for example, in Polish Tak-Tak)
you pay to your operator for few SMS messages (in this example 10), when you
send first of them. When you will clear these counters in start of this period
(before first SMS), you will know, when another money will be taken from your account...
|
Test 61
NOPSW :aaaa
SYNCR :bbbb
RESELEC:cccc
|
|
PSWMesgCntr
SyncMeasCntr
CellReselCtr
|
|
-
aaaa - hexadecimal counter of MDI_NO_PSW_FOUND messages from
DSP
-
bbbb - decimal counter for synchronization measurement attempts.
If value is over 9999 then four x are shown
-
cccc - hexadecimal counter for cell reselections
Counters values are saved in EEPROM memory, when phone is disabled.
You can reset them using test 60. They're reset too, when
they exceed their maximal values.
In dual phones you will have such test 61:
aaaaa bbbbb
ccccc ddddd
eeeee fffff
ggggg hhhhh |
|
NOPswGSM DCS
Sync GSM DCS
reselG>G D>D
reselG>D D>G |
|
-
aaaaa - for GSM 900: counter (decimal) for MDI_NO_PSW_FOUND messages
from DSP
-
bbbb - for GSM 1800: counter (decimal) for MDI_NO_PSW_FOUND
from DSP
-
ccccc - for GSM 900: counter (decimal) for
synchronization measurement attempts.
If this value is over 99999, then five x are shown.
-
ddddd - for GSM 1800: counter (decimal) for
synchronization measurement attempts.
If this value is over 99999, then five x are shown.
-
eeeee - counter (decimal) for cell reselections GSM 900 - GSM 900
-
fffff - counter (decimal) for cell reselections GSM 1800 - GSM 1800
-
ggggg - counter (decimal) for cell reselections GSM 900 - GSM 1800
-
hhhhh - counter (decimal) for cell reselections GSM 1800 - GSM 900
Counters values are saved in EEPROM memory, when phone is disabled.
You can reset them using test 60.
They're reset too, when they exceed their maximal values.
In Nokia 6210/8210:
NOPSW: 008A
SYNCR: 766
RESELEC:872D
RmMonTO:0000
|
|
PSWMesgCntr
SyncMeasCntr
CellReselCtr
RM Mon TOuts
|
|
In Nokia 3310 help is like in models 6210/8210, but displayed values are different:
In Nokia 6185/6188 it's different:
V
aaaaaaaaaaaa
bbbbbbbbbb
ccccccc
|
- aaaaaaaaaaaa - version of phone's firmware
- bbbbbbbbbb - date of phone firmware
- ccccccc - phone's codename (NSD-3AX)
|
This phone displays this info too, when you enter *#837# code. For more
information about firmware in Nokia phones (including 6185/6188 models) click here. |
Test 62
PSW :aaaa
SYNCR:bbbb
BCCH :cccc
BCCHE:dddd |
|
NeghbrPSWCtr
SyncMeasCntr
BCCHMeasAtmp
BCCHExtMeAtm |
|
-
aaaa - counter for neighbour PSW measurement attempts
-
bbbb - counter for neighbour synchronization measurement attempts
-
cccc - counter for neighbour cells BCCH
(quality of trasmission with them) measurement attempts
(see description C1)
-
dddd - counter for extended neighbour cells BCCH
(quality of trasmission with them) measurement attempts
(see description C1)
Counters values are saved in EEPROM memory, when phone is disabled.
You can reset them using test 60.
They're reset too, when they exceed their maximal values.
In Nokia 3310 each counter is 5-digit number. Values are also aligned to right.
In Nokia 6185/6188 this test looks different:
DSP ROM 2
VERS 430
BETA 0014
|
Test 63
|
CalRel RelDi
MOCAtmp MOOK
AllMT MTOK
|
|
-
aa - you will find reason of last call release here (it's displayed in
test 2
and test 39 too (in this
last test you will find more explanations - see description of first
parameter))
-
bb - another information about end of last call:
-
UN: unknown (for example: you didn't make any calls after enabling phone)
-
IN: internal reason (for example: you enabled in
test 17 BTS test,
phone didn't find network on given channel and you tried to make call)
-
MT: broken by network
-
MO: disconnection (ending call) from one of the phones
-
ccc - how many times you tried to make outgoing call from your phone
-
ddd - number of succesfull outgoing calls (how many times calls were really
realised)
-
eee - number of all incoming calls (missed too)
-
fff - number of received incoming calls
When counters exceed their maximal values, they're reset (you can make it
using test 60 too). Their values (it's
about ccc and next counters only) are written to EEPRM, when phone is disabled.
In Nokia 3310 parameters are a little different located on the screen (when compare to info above).
In Nokia 6185/6188 this test looks different:
C1M 00
C1L 00
C2M 00
C2L 03
|
Test 64
It contains, for example, information, how many times you phone
informed network about position (see description of
test 10 too)
|
Nfai NL NLOK
PFai PL PLOK
Loc update
counters |
|
-
aaa - error code (reset after enabling phone) of last incorrect
Location Update
(it changes only then, when some error happened during it).
It can be found in test 39 too
- it's value of MM parameter (there are code values with their description too)
-
bbb - how many times phone tried to make
Location Update
-
ccc - how many times attempts of making
Location Update
were successfull
-
ddd - error during last PLU or IMSI Attach
(17 means probably network busy)
-
eee - how many times phone tried to make PLU
or IMSI Attach
-
fff - how many times attemps of making PLU
or IMSI Attach were successfull
Values of these counters (excluding error codes) are stored in EEPROM,
when phone is disabled. You can reset them using
test 60 (it's made too,
when they exceed their maximal values).
In Nokia 3310 parameters are a little different located on the screen (when compare to info above).
|
If you don't disable your phone and all time you are in
your network time range, in this menu you will find information (in
approximation), how long it's enabled (check in
test 10, how often
is reset T3212 counter (ccc parameter) and multiply that time by
eee parameter from this menu). You can use to make it counter from
test 82 too (it's more precise, but require
enabling some test) or service menu (in phones like Nokia 6130 or 3210).
|
In Nokia 6185/6188 this test looks different:
C3M 00
C3L 00
C4M 00
C4L 03
|
Test 65
Test connected with SMS messages (without reports)
aa bbb ccc
dd eee fff
gggg
|
|
SFai MO MOOK
RFai MT MTOK
Sched Msgs
SMS counters |
|
-
aaa - error code during sending last SMS message (reset after enabling phone):
-
1: 'Number not in use'
-
21: 'Message not sent this time'. This error happens, when
you try to send messages from prepaid card without this possibility,
when you send message for incorrect number (SMSC is correct), SMSC is blocked
on your network or when you send SMS with alphanumeric number over SMSC, which
doesn't support it.
-
28: 'Number not in use'
-
38: 'Message not sent this time'. Error with sending message during SMSC blocked on your network.
-
42: probably phone shows this error, when used SMSC
is overworked (too many sent messages in the same time) and can't send
your message in this moment
-
50: 'Check operator services'. Error displayed after sending
SMS from some prepaid cards without this possibility.
-
96: 'Nieudane wysłanie wiadomości' ('Message sending failed').
The reason is wrong number of SMSC (+1).
-
111: 'Message sending failed'.
The reason is wrong target number or wrong number of SMSC
-
166: 'Message sending failed'.
Displayed when SMSC number was wrong or SMSC is blocked for your network.
-
169: 'Message sending failed'.
No money on prepaid account.
-
178: 'Message sending failed'. Error displayed after sending
SMS from some prepaid cards without this possibility.
-
252: 'Message sending failed'. Displayed, when phone's transmitter
was disabled in test 45 or
phone can't find network (when BTS test
in test 17 was enabled on channel
without network)
-
253: 'Message sending failed'. Displayed, when SMSC number was wrong.
-
bbb - number of SMS sending attempts.
You should remember, that report about waiting for delivering SMS (pending)
isn't sent from your phone and is not taken into consederation in this parameter
(but information about success/defeat in its' delivering is taken - see description
for eee and fff parameters). For example: you enabled in phone's menu function
connected with SMS raports. You send SMS message now - phone increases this parameter.
If it showed, that sending of message was successfull, increases value of ccc
parameter too and phone saves report waiting for delivering sent SMS.
If SMSC delivered it (or not) and sents about it report (Failed or Delivered),
value of eee parameter increases too. If receiving or report was successfull,
increases value of fff parameter too (phone checks all saved reports now.
In majority of Nokia phones: if in some report with "pending" text SMSC and number,
where SMS was sent, is the same to SMSC and number from received report,
phone deletes "pending" report and saves received report into this place).
-
ccc - number of succesfull sent SMS messages (which were accepted by used
SMSC and you will pay for them). For more info see description of previous
parameter.
-
ddd - code of error during receiving last SMS message (reset, when phone is
enabled):
-
22: full memory for SMS messages (phone tried to receive message
- increased value of eee counter, fff value didn't change). Information about
it is on the top of phone's screen too (blinking envelope) and phone showed
'No space for new messages' message. When you save messages on SIM card,
their sum in 'Outbox' and 'Inbox' depends on it (card). The most often, different
networks gives SIM card with different space for SMS messages (for example,
for Polish Plus GSM it's 10, for
Era GSM
15 and for Idea 30). When you don't have
space for messages, you can't add new (message 'Message memory full').
You have to delete one of saved messages there - when you won't make it,
you can loose some incoming (remember, that sender of SMS message can set time,
when network will try to delivery it; after it it will be deleted and you won't
be able to receive it !).
-
eee - number of SMS messages receiving attempts. For more info see description of next
parameter.
-
fff - number of correctly received SMS messages. Of course, all raports
about success/defeat in SMS delivering, logos, ringtones, business cards and
picture messages are sent in this form too (like adequate coded SMS) and are
taken into consideration in this parameter (but each picture message sent, for example,
from Nokia 3210 is written in 3 SMS messages !)
-
gggg - number of received cell broadcast messages (if they're supported by actual
used BTS, you can check in test 7):
how many times your phone received cell-info (in Nokia 5110 it can be enabled in Menu 4-2-2)
and cell-broadcast (Menu 2-5 in Nokia 5110) messages
Values of these counters (excluding error codes) are written to EEPROM,
when phone is disabled. You can reset them using test 60
(it's made too, when they exceed their maximal values).
I received info, that in some (all ?) Nokia 6150 phones
with 4.13 firmware doesn't change value of gggg counter instead that they receive
cellinfo messages (is it bug in this firmware version ?)
In Nokia 3310 parameters are a little different located on the screen (when compare to info above).
In Nokia 9210 parameters are 4 digits long...
If you want to know a little more about sending SMS messages
(or find SMSC of different operators), visit
www.vdheyden.demon.nl/sms/index1.htm
site.
|
Majority of computer programs don't write to their users, if SMS message
sending was successfull - this test will be only way to check it.
|
In Nokia 3110 this test looks like test 64.
In Nokia 6185/6188 this test looks different:
C5M 00
C5L 00
C6M 00
C6L 03
|
Test 66
Timeout counters connected with SMS messages (as you know, when you send them,
you can set, how long network will try to delivery them - I suppose, that these
counters are connected with it).
|
TR1 TR2 TRA
TC1 TC2 SCH
SMS timeout
counters |
|
- aaa - timeout counter for TR1M
- bbb - timeout counter for TR2M
- cc - timeout counter for TRAM
- ddd - timeout counter for TC1M
- eee - timeout counter for TC2M
- ff - timeout counter for cell broadcast
Values of these counters are written to EEPROM, when phone is disabled.
You can reset them using test 60
(it's made too, when they exceed their maximal values).
In Nokia 6185/6188 this test looks different:
Test 67
REC 00
SEND 00
CTR 4C
STA 68
|
Test 68
Test 70
Temporary counters of DSP (contents of API memory locations
r_dsp2ftd+0, r_dsp2ftd+1, r_dsp2ftd+2, etc. in hex format)
aaaaa bbbbb
ccccc ddddd
eeeee fffff
ggggg hhhhh |
|
Temporary
DSP counters
R DSP2FTD
|
|
The display is to be used by special debugging DSP
software which can put some useful information to the memory locations on
API RAM. When this display is selected then MCU
copies the contents of those memory locations into display with format specified above.
In Nokia 3110 this test looks like test 80.
Test 71, 72
Both tests allow to set DSP settings.
When you will directly enter to one of them, in both of them number below AUDIO
ENHANCEMENT change - values depends on SIM card. You can now enter to one of them
using arrows - sound emited by phone will change then (you can hear
horrible noises and cracks). You can set values below AUDIO ENHANCEMENT too
- save them (in decimal - maximal value is 65536) in 31 or 32 position
in phonebook on SIM card (how to do it ? see description in
test 17).
Conf parameter from test 30
shows, what value was choosen here. You can back to normal sound, when
you will disable and enable phone. Connecting headset or cat kit don't change
sound effects with concrete values set here.
|
Use menu to
control DSP
audio
enhancements |
|
In Nokia 9210 these tests look like follows:
AUDIO
ENHANCEMENT
DISPLAY 1
aaaaa |
|
Display 1
DSP audio
enhancements |
|
In Nokia 3110 test 71 looks like test 81.
Test 73
Generic display for DSP Audio Enhancements
aaa bb aaa
cccc bb cccc
cccc bb cccc
cccc cccc |
|
DB1 B1 DB2
HEX1 B2 HEX2
HEX3 B3 HEX4
HEX5 HEX6 |
|
-
aaa - general dB value, e.g. signal level in dB. decimal point and sign is not shown, ie. -10.5 is show 105.
- bb - general byte value, used for combined flags. Value is in hex format.
- cccc - general hex value.
Some English sources write about this test:
"The display is reset and restarted when call is taken (if NetMonitor display
counters are enabled). When call is terminated the display is frozen to
show last values. Display values will not be saved to the EEPROM."
...but I haven't seen it my phone and they were equal 0 all the time (is something additionaly required to enable this test ?)
In Nokia 3110 this test looks like test 82.
Test 74
DSP audio enhancements 1 (DRC)
|
DSigL USigL
NseLvl
DTbl UTbl
|
|
- aaa - downlink (received by your phone) signal level.
- bbb - uplink (sent by your phone) signal level
- ccc - background noise (see description of DTX) signal level.
- dd - downlink (received by your phone) DRC table value, shown in decimal integer, two digits.
- ee - uplink (sent by your phone) DRC table value, decimal integer, two digits.
Three first parameters are in dB calculated using DRC level
measuring block. Decimal point and sign is not shown,
ie. -10.5 is show 105.
Some English sources write about this test:
"The display is reset and restarted when call is taken (if NetMonitor display
counters are enabled). When call is terminated the display is frozen to
show last values. Display values will not be saved to the EEPROM."
...but I haven't seen it my phone and they were equal 0 all the time (is something additionaly required to enable this test ?)
In Nokia 3110 this test looks like test 72.
Test 75
Audio path status
Mod:aaaaaaa
AudReq: bbbb
AccMod: cccc
H2Path: dddd |
|
ExtAudStatus
AudioRequest
AccAudMode
|
|
-
aaaaa - external audio status (for some phones possible values are: HP, HF, HEADSET, EXT and HP_OFFHO)
With Nokia 5110 these values vere observed:
| value |
normal state (nothing connected, cable MBUS/FBUS or changer connected) | HP |
headset (phone displays Headset)
You can simulate it
connecting pins 1-2 on the connector on the bottom of the phone
(when you see from the left side, when phone's screen is on the top)
In Nokia 9110 you can use to make it
test 92 too. |
HD (shortcut from HeaDset) |
car kit (phone displays Car)
You can simulate it
connecting pins 2-3 on the connector on the bottom of the phone
(when you see from the left side, when phone's screen is on the top)
| HFU 1 (shortcut from Hands Free Unit 1) |
Described above methods of simulating presence sound accesories are correct
for Nokia 5xxx, 6xxx and probably 9110 (but REMEMBER: you use them on YOUR OWN risk)
When you connect (simulate) both accesories you have in phone function
"Automatic answer" (Menu 4-1-6 in Nokia 5110) - it allows phone
to answer automatically (without pressing key) incoming calls. In Nokia 9110
you can activate it using test 92 too.
-
bbbb - audio_request bitmap in hex
-
cccc - accessory audio mode
-
dd - path for HFU-2 (Hands Free Unit-2)
In Nokia 9210 help looks like follows:
ExtAudStatus
AudioRequest
AccAudMode
HFU2Path |
In Nokia 3110 this test looks like test 73.
Test 76
Ear (= downlink) audio display
Vab Pccc
Cddd CAeee
PAfff
|
|
EVol PeakVal
CutOff COAve
PkAver
|
|
-
ab - volume level (below information are correct for Nokia 5110):
| a | b |
speaker disabled | 0 | F |
sound like after pressing key (volume level 1) |
0 | 8 |
sound like after pressing key (volume level 2) |
0 | 4 |
sound like after pressing key (volume level 3 or enable loud sounds)
|
0 | 0 |
During connection a parameter has "A" value, parameter b allows to
calculate set volume level (count it to the decimal value and substract 11 from it)
- this last parameter can be checked in
test 30 too. When you connect headset,
parameter a has "C" value (formula for counting volume level during call is
"10 - b" then). With car kit, a parameter is equal "2" and formula is "10 - b" too.
When somebody calls to you (you didn't receive it yet), phone doesn't
show volume of sound always (displayed valued are for disabled speaker) -
I don't know, if it's firmware bug (5.07) or something different.
Phone shows it (volume) only with some combinations of types of rings (Ringing, Asceding)
and volume ring (I write values for both of these parameters: level 1 - A7,
level 2 - A6, level 4 - A4, level 5 - A0).
-
ccc - peak value of downlink audio signal during last frame in dB,
decimal point and sign is not shown, ie. -10.5 is show 105.
-
ddd - cut off counter value of last frame. This counter counts
how many samples are saturated during last frame.
-
eee - moving average of cut off counter, decimal point and sign is
not shown, ie. -10.5 is show 105.
-
fff - moving average of peak levels
Some English sources write about this test:
"The display is reset and restarted when call is taken (if NetMonitor display
counters are enabled). When call is terminated the display is frozen to
show last values. Display values will not be saved to the EEPROM."
...but I haven't seen it my phone and they were equal 0 (without first) all the time
(is something additionaly required to enable this test ?)
Test 77
Microphone (= uplink) audio display
|
MicPeak MAve
CutOff COAve
|
|
-
aaa - peak value of uplink audio signal during last frame in dB,
decimal point and sign is not shown, ie. -10.5 is show 105.
-
bbb - moving average of peak levels, decimal point and sign is not
shown, ie. -10.5 is show 105..
-
ccc - cut off counter value of last frame. This counter counts
how many samples are saturated during last frame.
-
ddd - moving average of cut off counter
Some English sources write about this test:
"The display is reset and restarted when call is taken (if NetMonitor display
counters are enabled). When call is terminated the display is frozen to
show last values. Display values will not be saved to the EEPROM."
...but I haven't seen it my phone and they were equal 0 all the time
(is something additionaly required to enable this test ?)
In Nokia 3110 this test looks like test 75.
Test 78
DSP audio enhancements (AEC)
aaa bbb ccc
ddd eee fff
ggg h i jjj
kkkk llll |
|
EAA Ada ERL
RxG TxG GLi
TxN Sta Mod
RVAD TVAD |
|
-
aaa - electro-acoustic attenuation of echo from DSP point of view
in dB. Decimal point and sign is not shown. E.g. -10.5dB
would be displayed as "105", -0.5 dB would be displayed
as " 5". 20*log10( Q15 )
-
bbb - adaptive attenuation of echo. Decimal point is not shown. 20*log10( Q15 )
-
ccc - total echo return loss. Decimal point is not shown. 20*log10( Q15 )
-
ddd - RX (received) attenuator gain in dB. Decimal point and sign is not shown. 20*log10( Q15 aec_rx_gain )
-
eee - TX (sent) attenuator gain in dB. Decimal point and sign is not shown. 20*log10( Q15 aec_tx_gain )
-
fff - gain limit for RX and TX. Decimal point and sign is not shown. 20*log10( Q15 aec_gain_limit )
-
ggg - TX (sent) noise level (see DTX description for more info)
in dB. Decimal point and sign is not shown. 20*log10( Q15 aec_tx_noise)
-
h - adaptive filter status. (Q0 aec_nlms_state) (bit UPDATE << 2) | (bit NLMS2 << 1) | (bit NLMS1)
-
i - comfort noise (see DTX description for details)
generation (0 or 1) (Q0 AEC_TX_COMF_GEN)
-
jjj - AEC mode. (byte Q0 s_AEC_mode)
-
kkkk - shows 16 last RX VAD decisions in HEX format. Hex( Q0 aec_rx_vadreg )
-
llll - shows 16 last TX VAD decisions in HEX format. Hex( Q0 aec_tx_vadreg )
In my phone all these counters were equal 0 all the time
(is something additionaly required to enable this test ?)
In Nokia 3110 this test looks like test 76.
Test 79
Audio equalizer display
aaaaa bbbbb
ccccc ddddd
-ee.e -ff.f
|
|
MiCutB MiCTA
EpCutB EPCTA
MiCLev EarLv
|
|
- aaaaa - saturated samples before microphone equalizer in decimal 16 bit
- bbbbb - saturated samples after microphone equalizer in decimal 16 bit unsigned integer format.
- ccccc - saturated samples before earpiece equalizer in decimal 16 bit unsigned integer format.
- ddddd - saturated samples after earpiece equalizer in decimal 16 bit unsigned integer format.
- -ee.e - level of the microphone signal level detector in dB format. Requires log10 function in MCU.
16 bit signed value in DSP, 0 dB = 32768.
-
-ff.f - Level of the signal after earpiece equalizer in dB format. Requires log10 function in MCU.
16 bit signed value in DSP, 0 dB = 32768.
Some English sources write about this test:
"The display is reset and restarted when call is taken. When call is
terminated the display is frozen to show last values. Display will not be
saved to EEPROM. Saturated sample counters aaaaa - ddddd are counted in DSP
and only the new counter value is sent to MCU. The microphone and earpiece
signal levels are calculated in DSP and it sends the linear values to
MCU which makes the linear to dB transformation (20*log10(x)) for the level
values."
...but I haven't seen it my phone and they were equal 0 all the time (is something additionaly required to enable this test ?)
In Nokia 3110 this test looks like test 77.
Test 80
|
Use menu
to reset
field test
timers |
|
By direct enter to this test you can reset counters from
test 82. Phone makes it too, when you connect
charger. Some English descriptions write, that it's made too, when battery is full
(I didn't notice it).
In some new phones (like Nokia 3310 4.45) after using this test counters
from test 82
are reset AND enabled (so, this test works as
test 81 too).
In Nokia 3110 this test looks like test 83.
In Nokia 6185:
RLP RESET 00
RX 00 00 00
TX 00 00 00
FER 000
|
Test 81
|
Use menu to
control test
display
timers |
|
By direct enter to this test you enable (aaaaaaaa=ENABLED) or
disables (aaaaaaaa=DISABLED) counters from test 82.
In Nokia 3110 this test looks like test 84.
In Nokia 6185:
Test 82
aaaaa bbbbb
ccccc ddddd
TIMERS eee
|
|
PwrOn InServ
NSPS TxON
Timers
Status |
|
-
aaaaa - how long phone was enabled
-
bbbbb - how long phone was logged into network
-
ccccc - how long phone was in
NSPS state
-
ddddd - how long phone's transmitter was enabled
-
eee - information, whether counters are enabled (ON) or not (OFF) (you can set
it using test 81)
Each of these counters display time in aaabb format - bb changes in
range 0-60 units; when reaches 60 units, it's reset to 0 and
aaa increases by 1. In majority of models unit is 1 minute (each of counters
display time as minutes and hours). In Nokia 7110 unit is half of minute,
in some Nokia 3310 one minute and 7 seconds...
Some English descriptions write, that maximal value for counters is 99 h and 59 minutes.
When first of them (aaaaa) will have this value, all of them will stop.
Unfortunatelly, these counters work only, when you have some test in netmonitor
enabled (it means: when you will disable tests, values won't change even, when
counters are enabled). It means, that you can have information here,
how long you use netmonitor (first parameter), how long phone logged into network
during this time (next)...
|
You you still want to measure time using this test, in
test 83 select SHOW TASK MSG BUFS and enable
test 87 (display will be empty then).
Of course, there disadvantiges of it: you won't have identification incoming calls.
In service menu in Nokia 6130 (*#WARRANTY# code) and 3210
(*#WAR0ANTY# code) in "Life Timer" position you will find information,
how long you make calls - digits before ":" mean hours, digits after it minutes).
For example, 0001:35 means 1 h 35 minutes of calls.
In Nokia 3310 (*#WAR0ANTY# code too) on start there is shown value 65536 there,
and counter starts working, when calls were longer than 1 h.
|
In Nokia 3110 this test looks like test 85.
In Nokia 6185:
QU 00 DL000
NACK 00000
RC00 BR00000
W0000 C0000
|
Test 83
|
|
|
Use menu to
select shown
task info
|
|
By direct enter to this test you can make, that in
test 84, test 85, test 86 and test 87
are displayed values of different counters:
-
"STACKS" - shows free stack space in worst case
-
"MSG BUFS" - shows the peak number of pending messages
-
"FAST BUFS" - shows the peak number of pending fast messages
In Nokia 3110 this test looks like test 86.
In Nokia 6185:
S00000 DL000
N00000 00000
R00000 D0000
00000
|
Test 84, 85, 86
Here is generally view of these tests:
aaaa bbbb
cccc dddd
eeee ffff
gggg hhhh |
and here is their help:
IDLE DEV_IO
LOCAL MDISND
MDIRCV UI
TONE PN |
or (Nokia 6210/8210):
IDLE DEV_IO
LOCAL MDISND
MDIRCV UI
TONE PND |
or (Nokia 6250):
IDLE DEV?IO
LOCAL MDISND
MDIRCV UI
TONE PND |
or (Nokia 9210):
IDLE STRTUP
DEV_IO LOCAL
MDISND -RCV
UI TONE |
|
FBUS AUD
L1CTRL L1MEA
L1SYSP L2
CC MM |
or (Nokia 3210):
IRDA FBUS
AUD L1CTRL
L1MEA L1SYSP
L2 CC |
or (Nokia 6210/6250):
WMLS PN
IRDA IRDAMGR
FBUS AUD
PHCTRL L2
|
or (Nokia 8210):
IRDA IRDAMGR
FBUS AUD
PHCTRL L2
CC MM
|
or (Nokia 8810):
IRDA IRMGR
FBUS AUD
L1CTRL L1MEA
L1SYSP L2 |
or (Nokia 9210):
PN MBUS
FBUS AUD
AUDCOMM PH
L2 CC
|
|
RR RM
SMS EM
SIMUPL SIML2
DDI |
or (Nokia 3210):
MM RR
RM SMS
EM SIMUPL
SIML2 DDI |
or (Nokia 6210/6250):
CC MM RR
RMC SMS EM
SIM SIM2 DDI
DGC NTB FAX
|
or (Nokia 8210):
RR RM
SMS EM
SIMUPL SIML2
DDI DGC
|
or (Nokia 8810):
CC MM
RR RM
SMS EM
SIMUPL SIML2 |
or (Nokia 9110):
RR RM
SMS EM
SIMUPL SIML2
DGC DGNTB |
or (Nokia 9210):
MM RR
RM SMS
EM SIMUPL
SIML2 DGC
|
|
-
aaaa, bbbb,... - task 0, 1, ...
Numbers tell how many stack memory locations have been empty in the worst
case. So, if number is zero, stack has been full. Values are not written into
EEPROM, when phone is disabled.
In Nokia 3110 test 86 looks like follow:
MCUSW aaaaa
DATE cccccc
CHKSUM dddd
DSP eee |
|
MCUSWVersion
DateOfMCUSW
MCUSWChecksum
DSPSWVersion |
|
Meaning of parameters aaaaa,cccccc, dddd and eee you will find in test
88.
Test 87
In Nokia 8810 it looks different:
ffff gggg
eeee dddd
aaaa bbbb
|
|
DDI DGC
DGNTB DGFAX
FIQ IRQ
|
|
In Nokia 9110 this test is different:
In Nokia 9210:
DGNTB DGFAX
DCS PMMCLE
PMMWR HELPER
|
In Nokia 7110 looks like follows:
1040010363800
700 800
220
476 480
|
|
DGN DGF SCKT
PCL PWB
PPC
FIQ IRQ
|
|
and in Nokia 6210/6250:
SRVSCK PMMCL
PMMWR ND
PPC
FIQ IRQ
|
|
and in Nokia 8210:
Values of counters are not saved to EEPROM, when phone is disabled.
Test 88
aaaaa bbbbbb
Date cccccc
ChkSum dddd
eeeeeeeeeeee |
|
MCUSW PPM
MCUSW_Date
MCU_Checksum
DSP_Version |
|
-
aaaaa i cccccc - version and release date of MCU software
(codes for their checking and changes among their different versions are here)
-
bbbbbb - version of downloaded PPM (Post-programming Memory) packet:
Nokia Mobile Phones prepares different language versions
of firmware for phones. They're saved in "packets" - each of them contains messages and support
for few languages. Why is it done ? It's simple: internal memory in our phones is still
too small for all languages support. You will see version of PPM packet:
it's the same number as version of MCU firmware. After it
you have char (it can be "A", "B", etc. - for example, Polish language is in "B" packet).
For curious: in older models (like Nokia 2110i) nobody prepared PPM packets and
preparing another language version was connected with modyfing ALL firmware. I readed too,
that phones with "generic" firmware had normally disabled services for some languages
(for example, Greek) - it could be enabled with some Nokia service programs (like Pc-Locals 0.6).
-
dddd - MCU memory checksum
(when it's wrong, phone display CONTACT SERVICE)
-
eeeeeeeeeeee - DSP software version
Information from this test are displayed in some Nokia service programs
(like PC-Locals 1.3 or WinTesla) too.
In Nokia 6210 there are displayed "?" chars instead of "_" in help for this test...
In Nokia 9210:
Linda SW
aaaaa bbbbbb
ChkSum: cccc
HW: dddd
|
|
Linda SW
03.62 011009
ChkSum: 5324
HW: 4000
|
|
Linda SW
Version Date
Checksum
HW Version
|
|
- aaaaa - firmware in PDA
- bbbbbb - date of PDA firmware
- cccc - checksum
- dddd - hardware version
Test 89
-
aaaa - phone hardware version (for example, the nevest Nokia 5110 I saw, display
here 4220)
-
bbbbbb - information, when were prepared texts (probably operator names)
displayed by phone
In Nokia 9210:
CMT SW
aaaaa bbbbbb
PPM: cccccc
dddddddd
|
|
CMT SW
03.21 011009
PPM: 03.62A
40.1.501
|
|
CMT SW
Version Date
PPM Version
DSP Version
|
|
- aaaaa - version of firmware in phone module
- bbbbbb - date of firmware in phone module
- cccccc - PPM with firmware in phone module
- dddddddd - DSP firmware version
Back to the top
[Part 1][Part 2][Part 3][Part 4][Part 5][Part 6][Part 7]
Marcin Wiacek (WWW)
Last modification: 10 March 2002