Re: [Bitpim-devel] Sanyo Sprint phones

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

Stephen Wood wrote:
> The gist of this report is that hdlc packets
> 508 bytes long are used.

Looking at their protocol document, the actual packet formatting
is similar.  The CRC and \x7e on the end of each one is identical
as is the the AT$QCDMG.  LG also has AT$LGDMGO.
 
> view indeed works with the 4900.  The top directory contains the files:
> RDM_PORT_MAP, $SYS.FACTORY, $SYS_RMT, uivrState.dat, $USER_DIRS amd the
> directories nvm and VoiceDB. 

The joy of all of these phones is that the file system layouts are very
similar, but not identical.  It seems like they arbitrarily go out
of their way to be different even for different models from the
same manufacturer.

> The VoiceDB directory has files with dates
> that seem to corresond to when I recorded voice dial entries.  I don't
> know if they are digitized speech or just some meta information.

I believe they are purevoice files.  BitPim in cvs has some support
for them.

> Are there other Sanyo owners here that would like to work with me on
> adding Sanyo 4900 capability to Bitpim?

I will help you as much as I can, although I don't have the phone.  The
first step is to check out the code and prerequisites as in 
http://bitpim.sourceforge.net/developer.html

Note that the anonymous CVS stuff is at least 24 hours behind, and
doesn't seem to be working for me at all.  If you have issues, email
me and I can send you the latest source etc in a zip file.

You should now have a look at what the other phones do to read a phonebook.
From the main BitPim source directory, do this:

   c:\projects\bitpim> python analyser.py examples\vx4400phonebookread.txt
   c:\projects\bitpim> python analyser.py examples\tm520phonebookread.txt

The actual protocols are described in the various p_*.p files from which
.py files are generated.  Take a stab at making one for your phone.
I would then recommend doing a data dump of a simple session in the same
format as the above files, and check they can be read with your description.

At that point you are ready to move onto real code.  A simple example
to start with is com_lgtm520.py.  It should make sense while reading the
analyser file above.  com_lgvx4400.py has more stuff in it and is a more
detailed example.

Send me email if you want advice, comments, or someone to throw your
observations off while doing this stuff.

Also if you feel that some of the code could do with better documentation,
more comments etc, then please tell me.  I won't get upset!

There is always apidoc at http://bitpim.sourceforge.net/apidoc/ which is
normally at most 2 or 3 days old.

Welcome!

Roger