[Bitpim-devel] Re: [bitpim-cvs-checkins] bitpim com_samsungscha620.py,1.8,1.9

[Roger Binns]

+ 'serial1': entry.slot, 'serial2': entry.slot,

Do you actually have two serials, or is that just copied from the LG
code?

For the serials you define whatever fields you want for the 'sourcetype'.
Optionally there can also be a 'sourceuniqueid' which distinguishes
between items of the same sourcetype (eg two phones of the same model).

The LG phones do all have two seperate serial fields. I have only
ever seen them have the same value, but dutifully record both in
case they are ever different.

Roger

[Stephen Wood]

It is copied from the Sanyo code which is copied from the LG code. The
Sanyo and Samsungs actually don't have serial numbers at all, just a
slot or memory location. For the A620 I was planning to do what Joe
did, namely use the internal slot and the visible # (or speed dial
number) as the two serial numbers.

The Samsung phones do have a time stamp. Not sure if that could be used
as a serial number. It will of course change if the user make any
change to an entry on the phone.

Stephen

Post by Roger Binns

+ 'serial1': entry.slot, 'serial2': entry.slot,

Do you actually have two serials, or is that just copied from the LG
code?
For the serials you define whatever fields you want for the 'sourcetype'.
Optionally there can also be a 'sourceuniqueid' which distinguishes
between items of the same sourcetype (eg two phones of the same model).
The LG phones do all have two seperate serial fields. I have only
ever seen them have the same value, but dutifully record both in
case they are ever different.
Roger
--
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bitpim-devel mailing list
https://lists.sourceforge.net/lists/listinfo/bitpim-devel

[Roger Binns]

Post by Stephen Wood
slot or memory location. For the A620 I was planning to do what Joe
did, namely use the internal slot and the visible # (or speed dial
number) as the two serial numbers.

Note that there is no requirement to have serial numbers, nor for there
to be two, nor for them to be called 'serial1'/'serial2'. Since it
is your sourcetype you should put in what is meaningful to you.
The phonebook import code uses it as a very strong correlation to mean
entries are the same.

For the Audiovox I only used the slot number:

res['serials']=[ {'sourcetype': self.serialsname, 'slot': slotnumber,
'sourceuniqueid': result['uniqueserial']} ]

Post by Stephen Wood
The Samsung phones do have a time stamp. Not sure if that could be used
as a serial number. It will of course change if the user make any
change to an entry on the phone.

That makes it an anti-serial :-) I guess knowing when the slot last changed
is vaguely useful but even more useful would be knowing if it was an edit
of what was there, or a delete and replace.

Roger

[Stephen Wood]

Post by Roger Binns

Post by Stephen Wood
The Samsung phones do have a time stamp. Not sure if that could be used
as a serial number. It will of course change if the user make any
change to an entry on the phone.

That makes it an anti-serial :-) I guess knowing when the slot last changed
is vaguely useful but even more useful would be knowing if it was an edit
of what was there, or a delete and replace.
Roger

A timestamp could be useful for a specific purpose on the VGA1000. I
don't believe that I will able to fully handle ringer and wallpaper
assignments. I could get the ringer assignment from the file system,
but it comes from files in the nvm directory and those files appear to
be locked. It does not seem like all ringers can be chosen through
the PBOKW command. If BitPim kept a timestamp on phonebook entries,
when writing the phonebook to the phone, I could compare the phone's
timestamp for a given entry to the timestamp in BitPim. If they are
identical, I could assume that that entry was not changed on the phone
or in BitPim since the phonebook was last read. In that case, I could
choose not to overwrite that entry. That way ringer and walllpaper
assignments won't get messed up for entries that have not changed.

I could also decide not to overwrite an entry by comparing every item
of the entry, but this is more work.

Stephen