Re: [Bitpim-devel] Samsung VGA-1000 phonebook notes

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

Stephen Wood wrote:
> It looks like it has a fairly full file system.  The wallpapers and
> ringers are in the filesystem, so media up/downloads won't be as much a
> pain as the Sanyo's.

It is usually the index files which are the pain.

> One of the AT commands is "AT#PCBIT?" which looks like it returns a
> bunch of useful information like number of entries in phonebook, field
> lengths etc.  This phone returns:

You should look at the GSM specs since the Samsung stuff seems to mostly
be the same.  You can download them from 
http://webapp.etsi.org/key/key.asp?GSMSpecPart1=27&GSMSpecPart2=007

(The required registration process is horrible.  I have the 1MB PDF
downloaded and will email you a copy.  If anyone else wants it, please
email me, or go through the registration crap yourselves.)

I think Motorola phones use a substantially similar protocol.

> #PCBIT: 1008,1,0,5,5,300,300,6,1,12,32,20,32,3,"URL",32,"Birthday",10,"Avatar",2

Well, since you got the new phone, you get to update the commport
code :-)  In particular it will need the following methods I think.

sendatcommand

  This would need to send an AT style command, and then peek at the
  first line returned and if it is an echo back of the command then
  throw the line away.  It could also throw an exception if the
  next line is ERROR and do nothing if it is OK (or return nothing,
  "OK" or "ERROR")

readline
  
  Read the next line of data

readlines

  (Dunno if this is needed)  Read all the lines up until the 
  next OK (or ERROR)

peekline

  Read the next line of data, but preserve it so that it can be 
  returned in the next call to readline

Once you have all that figured out and working, let me know and I
will put it into the BitFling code.

I think we will also need two new types for the protocol description
stuff.  One would be an integer specified in string form, and one
would be a string in CSV quoted form.  It would probably also make
sense to have a new list type as well that seperates entries with
commas.  I would suggest writing a description file, and then I'll
be happy to write the types for it.

It would be good if you can do some investigation of what happens to
string values that have double quotes, carriage returns, commas, backslashes
and other characters in them.  It would also be useful to know how
rigid the whitespace requirements are - for example is leading and
trailing whitespace of the string.

Roger