comparison doc/User-oriented-commands @ 90:8a714fe98aa9

doc/User-oriented-commands: new lnd-* commands
author Mychaela Falconia <falcon@freecalypso.org>
date Wed, 17 Feb 2021 18:40:34 +0000
parents 629be330f92b
children d924e4b1387f
comparison
equal deleted inserted replaced
89:629be330f92b 90:8a714fe98aa9
300 answered or not. Because of the limitations of this SIM LND store, most phone 300 answered or not. Because of the limitations of this SIM LND store, most phone
301 designs do not use it, and instead go with their own implementation of call 301 designs do not use it, and instead go with their own implementation of call
302 history lists. 302 history lists.
303 303
304 Because this LND store is a cyclic file, not linear fixed like phonebooks, it 304 Because this LND store is a cyclic file, not linear fixed like phonebooks, it
305 can only be dumped - it cannot be freely edited. (The only update operation 305 does not allow random access writes: it allows random access reads like all
306 allowed on cyclic files is writing a new record that becomes the new #1, 306 regular record-based files, but the only write operation allowed by the SIM
307 shifting all previous records down and losing the oldest one - but it is an 307 interface protocol and the SIM file system architecture is writing a new record
308 operation to be performed by phones if they support this LND as envisioned by 308 that becomes the new #1, shifting all previous records down and losing the
309 ancient spec writers, not something we are in the business of with fc-simtool.) 309 oldest one. Because of this write access limitation, we do not provide the same
310 310 set of operations on LND as for regular phonebooks - but we still provide good
311 The command to dump the LND cyclic store is 'lnd-dump'. If you have had your 311 tinkering ability. The following commands are available:
312 SIM for a very long time, having used it in different phones with different 312
313 firmwares, it may be interesting to look at the output of lnd-dump - you may 313 lnd-dump
314 have LND records that were generated ages ago by other phones if your current 314
315 one does not write into SIM LND. 315 This command dumps the content of the LND store on the terminal, in the same
316 format as pb-dump for regular phonebooks.
317
318 If you have had your SIM for a very long time, having used it in different
319 phones with different firmwares, it may be interesting to look at the output of
320 lnd-dump - you may have LND records that were generated ages ago by other
321 phones if your current one does not write into SIM LND.
322
323 lnd-dump outfile
324
325 This form of the lnd-dump command produces the same dump format, but saves it
326 in the named file instead of sending it to the terminal.
327
328 lnd-restore filename
329
330 This command reads the named phonebook data file (presumably written previously
331 with lnd-dump) and writes it into EF_LND on the SIM. This command works by
332 first constructing a full binary image of the desired EF_LND content, then
333 writing every record in the reverse order from the last index to the first.
334
335 lnd-write phone-number [alpha-tag]
336
337 This command writes a new record into the LND cyclic store just like a standard
338 phone would do when making a record of a new outgoing call. The two arguments
339 (one required and one optional) are the same as for pb-update-imm.
340
341 lnd-erase
342
343 This command erases the EF_LND cyclic store, making it appear as if no outgoing
344 calls have ever been recorded. It works by writing a blank record (0xFF in
345 every byte) N times, where N is the size of the cyclic store in records.
316 346
317 Manipulating stored SMS 347 Manipulating stored SMS
318 ======================= 348 =======================
319 349
320 The fundamental operating model of all message stores for SMS (whether SIM or 350 The fundamental operating model of all message stores for SMS (whether SIM or