bitpim-devel

Re: [Bitpim-devel] LG phonebook sync question - keeping original entry number

[Chris P. <dev...@te...>]

You wrote:
> 
> You can store the entry number as part of the serials.  The way the other LG
> phones work is that each entry has two serial numbers which are equal and never
> change for that entry.  Every time you create a new entry, a new serial is
allocated
> (the new serial being an ever increasing number).
> 
> When writing out to the phone, the existing entries and their serials are
> read, and the entries being written out are matched to those.  The
> software inside the phone maintains the speed dial pointers correctly.
> 
> Roger

I'm not sure I understand this, so let me re-state.
When you go a getphonebook, as part of the response, you get the entry number
(entrynumber), which I don't see the code stores in anywhere. When you need to
rewrite a modified entry, I take it that the phone will ignore whatever entry
number you put in the request and use the serial number as the key? For a
brand new entry, the serial should be automatically created, but the entry
number was filled in by an incremental counter - can anyone explain how BREW
handles it when you send a pbappendentryrequest? I know eventually I will
destroy my spare phone testing this, just wanted to know what to expect

Also, is the speed dial being kept at all? I don't see the code for VX4400
doing that currently and I assume you lose your speed dial or is that not
the case?

PS: next up, the LG4600 (VX4600 down in the states), once I justify paying
over $70USD for a data cable which it cost only $30USD (all the taxes, duties,
and shipping handling created a 100%+ overhead). I believe the LG4600 has
very similar phonebook structure, and I know the ringtone/wallpaper handling
already (at least I think I know).

Re: [Bitpim-devel] LG phonebook sync question - keeping original entry number

[Chris P. <dev...@te...>]

After more digging around in the code, I figure the best way to use
the speeddial key to store the entry number (and as part of discovery,
I have all fields identified for a phonebook entry). I totally forgot
that in the TM520 you have to choose a default phone number for each entry,
which is how the speed dial is assigned - and thus, the phonebook has a field
saying which is the default phone number. All I need to do is assign the
speed dial field with entrynumber for that particular number during
getphonebook, and reset the entrynumber to be the speed dial as well as the
default phone number field. Now I just need to understand fully what the
savephonebook function does (I partially understood it and made it modular
to support phone differences) before I go test it out

[Bitpim-devel] Speed dial

[Stephen W. <sa...@us...>]

Chris:

	I am not sure if it is a useful example for your phone, but the code
for the Sanyo phones saves and restores speed dial settings.

				Steve

Re: [Bitpim-devel] LG phonebook sync question - keeping original entry number

[Roger B. <ro...@ro...>]

Chris Poon wrote:
> After more digging around in the code, I figure the best way to use
> the speeddial key to store the entry number

No, that is a bad idea.  The speed dial field is used for storing the speed
dial. Remember that BitPim can work with multiple phones concurrently.

> I totally forgot
> that in the TM520 you have to choose a default phone number for each entry,

The phonebook format in BitPim is designed to work with that.  See the top
of phonebook.py.  In particular numbers are ordered, and hence the first
one is the default.  The 4400/6000 store 5 numbers in priority order,
with another 5 bytes storing each number type.

> default phone number field. Now I just need to understand fully what the
> savephonebook function does (I partially understood it and made it modular
> to support phone differences) before I go test it out

Run the analyser on examples\vx4400phonebookupdate.txt to see how the
code works.

Roger

Re: [Bitpim-devel] LG phonebook sync question - keeping original entry number

[A F <eat...@ho...>]

Hi Chris,

I'm already looking at the 4600, and already have a cable.  Perhaps it would
be better if we were to work together rather than have you purchase another
cable and work independently?

I'll email you everything I've mapped out already over the weekend.

Anthony

----- Original Message ----- 
From: "Chris Poon" <dev...@te...>
To: <bit...@li...>
Sent: Friday, February 20, 2004 9:59 AM
Subject: Re: [Bitpim-devel] LG phonebook sync question - keeping original
entry number


> You wrote:
> >
> > You can store the entry number as part of the serials.  The way the
other LG
> > phones work is that each entry has two serial numbers which are equal
and never
> > change for that entry.  Every time you create a new entry, a new serial
is
> allocated
> > (the new serial being an ever increasing number).
> >
> > When writing out to the phone, the existing entries and their serials
are
> > read, and the entries being written out are matched to those.  The
> > software inside the phone maintains the speed dial pointers correctly.
> >
> > Roger
>
> I'm not sure I understand this, so let me re-state.
> When you go a getphonebook, as part of the response, you get the entry
number
> (entrynumber), which I don't see the code stores in anywhere. When you
need to
> rewrite a modified entry, I take it that the phone will ignore whatever
entry
> number you put in the request and use the serial number as the key? For a
> brand new entry, the serial should be automatically created, but the entry
> number was filled in by an incremental counter - can anyone explain how
BREW
> handles it when you send a pbappendentryrequest? I know eventually I will
> destroy my spare phone testing this, just wanted to know what to expect
>
> Also, is the speed dial being kept at all? I don't see the code for VX4400
> doing that currently and I assume you lose your speed dial or is that not
> the case?
>
> PS: next up, the LG4600 (VX4600 down in the states), once I justify paying
> over $70USD for a data cable which it cost only $30USD (all the taxes,
duties,
> and shipping handling created a 100%+ overhead). I believe the LG4600 has
> very similar phonebook structure, and I know the ringtone/wallpaper
handling
> already (at least I think I know).
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Bitpim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>

Re: [Bitpim-devel] LG phonebook sync question - keeping original entry number

[Roger B. <ro...@ro...>]

> I'm not sure I understand this, so let me re-state.
> When you go a getphonebook, as part of the response, you get the entry number
> (entrynumber), which I don't see the code stores in anywhere. 

Correct.

> When you need to
> rewrite a modified entry, I take it that the phone will ignore whatever entry
> number you put in the request and use the serial number as the key? 

No.  Look at the savephonebook code.  That code re-reads the phonebook,
and matches up the serials of the data about to be written with what is
already on the phone.

The VX4400/4500/6000 require that you write out stuff in entry order,
but there can be holes due to entries being deleted, and then new entries
are appended.

It would be pointless storing the entry number in BitPim since the 
phonebook on the phone could change between BitPim reading it and
BitPim writing to it.

> For a
> brand new entry, the serial should be automatically created, but the entry
> number was filled in by an incremental counter - can anyone explain how BREW
> handles it when you send a pbappendentryrequest? 

This has nothing to do with Brew.  The LG phones store their phonebook in
files particular to them and have their own sync protocol.

The phone has a file containing the next counter number.  When you add an
entry, that number gets allocated.

> I know eventually I will
> destroy my spare phone testing this, just wanted to know what to expect

Just make sure you do a complete filesystem backup first and you should be
ok.  About the worst damage is if the phone gets into an infinite reboot
loop, in which case Verizon will replace the phone.

> Also, is the speed dial being kept at all? I don't see the code for VX4400
> doing that currently and I assume you lose your speed dial or is that not
> the case?

The speeddial is not read as it isn't included in the phonebook sync protocol
as far as I can tell.  It is on a file in the phone, but I haven't quite
figured out how it is stored.  The speed dials (and voice dials) are tied to 
particular serials, so providing the serials of entries are preserved the
speed/voice dials are preserved.

> PS: next up, the LG4600 (VX4600 down in the states), once I justify paying
> over $70USD for a data cable which it cost only $30USD (all the taxes, duties,
> and shipping handling created a 100%+ overhead). I believe the LG4600 has
> very similar phonebook structure, and I know the ringtone/wallpaper handling
> already (at least I think I know).

What a few weeks till bitfling is ready (I'll give more details when it is
closer to completion).  It will make development considerably quicker and
easier for phones not in front of you.

Roger