bitpim-devel — For bitpim developers

Re: [Bitpim-devel] Support for Kyocera 7135 (QC MSM5100)

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

> VX6000    FF 00 01 00
> CDM8900   FF 00 01 03  (last 03 is sometimes zero)
> VX4400    FF 00 01 00

> VX4500    FF 00 00 00    
> VX4500    FF 00 01 01    
> VX4500    FF 00 01 03

> SCP5500   FF 00 01 03 
> SCP5500   37 00 01 03 

I also had the CDM8900 have 37 as first byte of unknown1
after looking in several other directories.

So it doesn't look like unknown1 can be used as a useful predictor
of the extra byte for the Kyocera 7135 (incidentally Kyocera typically
just rebadge Qualcomm phones and hence are closest to the "real thing").

The second byte of unknown2 seems to be somewhat related to file
size.  (The protocol uses a block size of 256 bytes).

Hopefully Stephgen Marchant can figure out some form of indicator
since I really don't want to have variations on the brew protocol.
(I will do so if there is no choice).

Roger

[Bitpim-devel] bitpim 0.7test6 build

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

Stephen,

Have you managed to do the build yet?

Roger

Re: [Bitpim-devel] Support for Kyocera 7135 (QC MSM5100)

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

On Sun, 2004-03-14 at 18:07, Roger Binns wrote:
> ...  Can everyone who doesn't have
> one of the phones listed please turn on the protocol logging,
> list a directory, ...

I get a bit more variety in unknown1 and unknown2 with Sanyo phones. 
With the SCP-5500  in the top directory, with 6 files I get

FF 00 01 03	00 02 00 00 00	$USER_DIRS
37 00 01 03	00 02 00 00 00	$SYS.FACTORY
FF 00 01 00	00 02 00 00 00	uivrState.dat
FF 00 01 00	00 02 00 00 00	CLK_DB
FF 00 00 00	00 02 00 00 00	RDM_PORT_MAP
FF 00 01 00	00 02 00 00 00	$SYS_RMT

On the SCP-4900 which has all these files except CLK_DB.  The same
unknown codes match up with the same file names as the 5500.

Now if I go into a directory, say nvm on the 5500, it gets a little more
interesting.

37 00 01 03	00 02 00 00 04	nvm/$SYS.ESN
37 00 01 03	00 02 00 00 04	nvm/$SYS.INVAR1
37 00 01 03	00 02 00 00 04	nvm/$SYS.INVAR2
FF 00 01 03	00 02 00 00 04	nvm/$SYS.INVAR3

Now drilling down to down to nvm/nvm
                                                        file size
FF 00 01 03	00 04 00 00 08	nvm/nvm/nvm_0000	829
FF 00 01 03	00 82 00 00 08	nvm/nvm/nvm_0001	31976
FF 00 01 03	00 04 00 00 08	nvm/nvm/nvm_0002	716
FF 00 01 03	00 08 00 00 08	nvm/nvm/nvm_0003	1524
FF 00 01 03	00 02 00 00 08	nvm/nvm/nvm_0004	5
FF 00 01 03	00 10 00 00 08	nvm/nvm/nvm_0005	3809
FF 00 01 03	00 c4 00 00 08	nvm/nvm/nvm_0008	48200
FF 00 01 03	00 c4 00 00 08	nvm/nvm/nvm_0009	48200
FF 00 01 03	00 c4 00 00 08	nvm/nvm/nvm_0010	48200


So unknown 2 seems to be related to file size, but not by a nice power
of 2.

Then again, if I go into other directories, the second byte doesn't seem
connected to file size anymore??

I am sure this just adds more confusion.

					Stephen

Re: [Bitpim-devel] Support for Kyocera 7135 (QC MSM5100)

[Tom P. <mlp...@ea...>]

On Mar 14, 2004, at 6:07 PM, Roger Binns wrote:
> For unknown1, these are the values on the 3 phones I have:
>
> VX6000    FF 00 01 00
> CDM8900   FF 00 01 03  (last 03 is sometimes zero)
> VX4400    FF 00 01 00
>
> Unknown2 is almost always 00 followed by a four byte integer
> that is usally the same as the entry number.  It is always
> a small value, usually less than 10.
>
> So far it looks like we can use the first byte of unknown1 to
> detect what is happening.  Can everyone who doesn't have
> one of the phones listed please turn on the protocol logging,
> list a directory, and then press Ctrl-Alt-P in the protocol
> log pane.  Find a p_brew.listfileresponse, and expand it in
> the second pane and write down what the value of the unknown1
> field is.  Feel free to also try and figure out what unknown2
> is.

It looks like unknown1 isn't simply a phone-dependent constant.  After 
listing the root directory on my VX4500, I found at least three 
different values for unknown1 in different listfileresponse packets:

unknown1       unknown2
FF 00 00 00    00 02 00 00 00
FF 00 01 00    00 02 00 00 00
FF 00 01 03    00 02 00 00 00

Listing the ART directory, I get a few more variations:

FF 00 01 01    00 08 00 00 04
FF 00 01 01    00 06 00 00 04
FF 00 01 01    00 04 00 00 04
FF 00 01 01    00 30 00 00 04

Listing the OWS directory, I found:

FF 00 01 00    00 16 00 00 04
FF 00 01 00    00 02 00 00 04
FF 00 01 00    00 04 00 00 04

etc.  There were additional variations for unknown2 in other 
directories, but these are the only three values of unknown1 I've seen. 
  In all cases, the directory listing itself was successful.

Tom

Re: [Bitpim-devel] Support for Kyocera 7135 (QC MSM5100)

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

Stephen Marchant wrote:
> But this phone has 5 "UNKNOWN" bytes before the remaining fields
> (date,size,etc...)
> Would it be possible to add this option in to support this phone?

I would prefer something that works correctly against all models
(ie find the root cause of the problem).  (BTW the VX4400 is
also based on the MSM5100).

I was hoping that the first or second of unknowns would give 
some clue as to why the latter field is larger, but couldn't
find anything.  However I would appreciate it if you could
put some more work into trying to figure out what these
fields actually are.  

For unknown1, these are the values on the 3 phones I have:

VX6000    FF 00 01 00
CDM8900   FF 00 01 03  (last 03 is sometimes zero)
VX4400    FF 00 01 00

Unknown2 is almost always 00 followed by a four byte integer
that is usally the same as the entry number.  It is always
a small value, usually less than 10.

So far it looks like we can use the first byte of unknown1 to
detect what is happening.  Can everyone who doesn't have
one of the phones listed please turn on the protocol logging,
list a directory, and then press Ctrl-Alt-P in the protocol
log pane.  Find a p_brew.listfileresponse, and expand it in 
the second pane and write down what the value of the unknown1
field is.  Feel free to also try and figure out what unknown2
is.

Roger

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

[Steven P. <n9...@n9...>]

On Mar 14, 2004, at 4:41 PM, Roger Binns wrote:
> They day you find a perfect piece of software, let us know :-)

  Well, I certainly have never written or used one, so don't wait for 
that email. ;^)

> However the wxWidgets API doesn't provide a GetFonts API.  I
> dug into my old email and found that it does provide the
> settings as #defines which I quoted.
>
> However wxPython doesn't export those symbols, due to an oversight.
> I worked with Robin on this and he will be exporting them
> in the next wxPython release.

  I spent a good bit of time trying to figure out why I couldn't find 
them only to realize this myself this afternoon. :-)

> They are not arbitrary values in bphtml.  They are supposed to be
> *identical* to the ones in wxWidgets because of wxPython not
> exporting the values.

  I did a similar thing, then, and put in the values defined in 
wxMac:html/htmldefines.h. It seems to work well like that, so I'll 
leave it there.

  Sorry, it's been a terrible day and I ranted when I should have ducked 
out and coded some more. :-) Eventually I would have realized the 
bigger picture and now all is well.

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

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

>   Sorry to get pissy, but it's horribly frustrating when something is
> supposed to be "cross-platform" and you end up having to put in so many
> little exceptions for this that and the other thing. 

They day you find a perfect piece of software, let us know :-)

> If there are
> platform differences, it SHOULD be handled transparently by the
> relevant libraries, not the end applications. With wxWidgets this is
> simply not the case, and it's infuriating at times.

It *IS* being handled transparently by wxWidgets.  wxWidgets even
goes so far as to correct the base sizes for each platform so
that the same HTML looks the same on all platforms.  (Quite frankly
if you ask for a 10 point font on the different platforms while
using a 17" monitor, you will get different physical sizes hence
the workaround in wxWidgets).

However the wxWidgets API doesn't provide a GetFonts API.  I
dug into my old email and found that it does provide the
settings as #defines which I quoted.

However wxPython doesn't export those symbols, due to an oversight.
I worked with Robin on this and he will be exporting them
in the next wxPython release.

>  Call me stupid, but if the base sizes are defined in a given
> platform's header file, why are they being redefined with arbitrary
> values in bphtml.py? Or is this something else entirely??

They are not arbitrary values in bphtml.  They are supposed to be
*identical* to the ones in wxWidgets because of wxPython not
exporting the values.

Roger

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

[Steven P. <n9...@n9...>]

On Mar 14, 2004, at 12:59 PM, Roger Binns wrote:
> Removing them is not the right fix for this.  Those listings of base
> size need to be exactly 7 items long and should correspond to the
> 7 sizes used in the wxWidgets code.  They are used in a call to
> wxHtmlWindow.SetFonts and are listed because there isn't a
> wxHtmlWindow.GetFonts.  Please read that documentation.

  Sorry to get pissy, but it's horribly frustrating when something is 
supposed to be "cross-platform" and you end up having to put in so many 
little exceptions for this that and the other thing. If there are 
platform differences, it SHOULD be handled transparently by the 
relevant libraries, not the end applications. With wxWidgets this is 
simply not the case, and it's infuriating at times.

> I think this is the list of base sizes for the Mac:
>
>     #define wxHTML_FONT_SIZE_1              9
>     #define wxHTML_FONT_SIZE_2             12
>     #define wxHTML_FONT_SIZE_3             14
>     #define wxHTML_FONT_SIZE_4             18
>     #define wxHTML_FONT_SIZE_5             24
>     #define wxHTML_FONT_SIZE_6             30
>     #define wxHTML_FONT_SIZE_7             36

  Call me stupid, but if the base sizes are defined in a given 
platform's header file, why are they being redefined with arbitrary 
values in bphtml.py? Or is this something else entirely??

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

[Tom P. <mlp...@ea...>]

On Mar 14, 2004, at 1:59 PM, Roger Binns wrote:
>> But, I found that if I just removed the smallest two font sizes from
>> the basefonts list in the SetFontScale method of bphtml, things looked
>> ok in the details view without affecting the appearance anywhere else,
>> as far as I could notice.  Here are the code changes I propose...
>
> Removing them is not the right fix for this.  Those listings of base
> size need to be exactly 7 items long and should correspond to the
> 7 sizes used in the wxWidgets code.  They are used in a call to
> wxHtmlWindow.SetFonts and are listed because there isn't a
> wxHtmlWindow.GetFonts.  Please read that documentation.
>
> I think this is the list of base sizes for the Mac:
>
>     #define wxHTML_FONT_SIZE_1              9
>     #define wxHTML_FONT_SIZE_2             12
>     #define wxHTML_FONT_SIZE_3             14
>     #define wxHTML_FONT_SIZE_4             18
>     #define wxHTML_FONT_SIZE_5             24
>     #define wxHTML_FONT_SIZE_6             30
>     #define wxHTML_FONT_SIZE_7             36

Ok, thanks.

> If Mac fonts are too small, then you need to change the
> default relative sizing in bphtml.HTMLWindow.__init__.
> I would suggest making relsize=None and then inside
> set it to 0.7 for non-Mac and whatever for Mac.

Using the correct Mac font sizes, the smallest text in the phonebook 
details view is still readable.  So I don't think it's necessary to 
adjust the font scaling specially for Macs.  In case it's useful, I've 
attached an updated patch file below.

Tom

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

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

> But, I found that if I just removed the smallest two font sizes from
> the basefonts list in the SetFontScale method of bphtml, things looked
> ok in the details view without affecting the appearance anywhere else,
> as far as I could notice.  Here are the code changes I propose...

Removing them is not the right fix for this.  Those listings of base
size need to be exactly 7 items long and should correspond to the
7 sizes used in the wxWidgets code.  They are used in a call to
wxHtmlWindow.SetFonts and are listed because there isn't a
wxHtmlWindow.GetFonts.  Please read that documentation.

I think this is the list of base sizes for the Mac:
 
    #define wxHTML_FONT_SIZE_1              9
    #define wxHTML_FONT_SIZE_2             12
    #define wxHTML_FONT_SIZE_3             14
    #define wxHTML_FONT_SIZE_4             18
    #define wxHTML_FONT_SIZE_5             24
    #define wxHTML_FONT_SIZE_6             30
    #define wxHTML_FONT_SIZE_7             36

If Mac fonts are too small, then you need to change the
default relative sizing in bphtml.HTMLWindow.__init__.
I would suggest making relsize=None and then inside
set it to 0.7 for non-Mac and whatever for Mac.

Roger

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

[Tom P. <mlp...@ea...>]

On Mar 14, 2004, at 9:47 AM, Steven Palm wrote:
>> I found that if I just removed the smallest two font sizes from the 
>> basefonts list in the SetFontScale method of bphtml, things looked ok 
>> in the details view without affecting the appearance anywhere else, 
>> as far as I could notice.  Here are the code changes I propose...
>
>  Seems reasonable to me. I'll put that in for the next test release.

Thanks.  Wasn't this a problem on your machine, too?  Or, was there 
some other way you dealt with it?

Tom

Re: [Bitpim-devel] Phonebook display fonts on Macs too small

[Steven P. <n9...@n9...>]

On Mar 14, 2004, at 8:21 AM, Tom Pollard wrote:
> I found that if I just removed the smallest two font sizes from the 
> basefonts list in the SetFontScale method of bphtml, things looked ok 
> in the details view without affecting the appearance anywhere else, as 
> far as I could notice.  Here are the code changes I propose...

  Seems reasonable to me. I'll put that in for the next test release.

[Bitpim-devel] Phonebook display fonts on Macs too small

[Tom P. <mlp...@ea...>]

Hi,

Running the current CVS version of bitpim under MacOSX 10.3 with 
WxPython 2.4.2.4, I find that the phonebook entry-details view is 
unreadable, because the font sizes are too small.  First, is it really 
just me, or do other people suffer from this, too?  Second, it wasn't 
obvious to me where in the code (or .xy files) this should be fixed.  
But, I found that if I just removed the smallest two font sizes from 
the basefonts list in the SetFontScale method of bphtml, things looked 
ok in the details view without affecting the appearance anywhere else, 
as far as I could notice.  Here are the code changes I propose...

diff -w -c -r1.12 bphtml.py
*** bphtml.py   12 Mar 2004 19:42:34 -0000      1.12
--- bphtml.py   14 Mar 2004 13:42:09 -0000
***************
*** 43,53 ****
           self.SetFontScale(relsize)

       def SetFontScale(self, scale):
!         # default sizes on windows
!         basefonts=[7,8,10,12,16,22,30]
!         # defaults on linux
           if guihelper.IsGtk():
!             basefonts=[10,13,17,20,23,27,30]
           self.SetFonts("", "", [int(sz*scale) for sz in basefonts])
           # the html widget clears itself if you set the scale
           if len(self.thetext):
--- 43,55 ----
           self.SetFontScale(relsize)

       def SetFontScale(self, scale):
!         # default font sizes
           if guihelper.IsGtk():
!             basefonts=[10,13,17,20,23,27,30]  # Linux
!         elif guihelper.IsMac():
!             basefonts=[10,12,16,22,30]        # MacOS
!         else:
!             basefonts=[7,8,10,12,16,22,30]    # Windows
           self.SetFonts("", "", [int(sz*scale) for sz in basefonts])
           # the html widget clears itself if you set the scale
           if len(self.thetext):

Cheers,

Tom

[Bitpim-devel] Support for Kyocera 7135 (QC MSM5100)

[Stephen M. <mar...@ch...>]

Hello,
I found a slight BREW protocol difference with this phone...

Normally, you expect a file list response as below:
PACKET listfileresponse:
    * responseheader header
    4 UINT entrynumber
    4 UNKNOWN unknown1
    4 UINT date
    4 UINT size
    5 UNKNOWN unknown2
    * STRING {'terminator': None, 'pascal': True} filename # no terminator
for some reason

But this phone has 5 "UNKNOWN" bytes before the remaining fields
(date,size,etc...)
Would it be possible to add this option in to support this phone?

Thanks!
-- Steve

-------------------------------------------------------------------------
22:09:25.594 SCP-5300: Now in brew mode
22:09:25.594 SCP-5300: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 00 00 00 00 02 2f 00 Y....../.
22:09:25.664 SCP-5300: brew response Data - 37 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 00 00 00 00 01 1f 00 00 00 c1 83 1d 2c Y..............,
00000010 06 00 00 00 00 00 00 00 00 0b 75 69 62 75 69 6c ..........uibuil
00000020 64 2e 64 69 72                                  d.dir
-------------------------------------------------------------------------

Re: [Bitpim-devel] vx4500 update

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

> I've attached a copy of the com_lgvx4500.py file that's been updated
> with the correct builtin ringtones and images. I don't know if this is
> useful or not, but it can't hurt to have the correct lists.

I have updated the code with the lists.

> The builtinimagesEMS list is a list of additional images that are
> available as wallpaper on the VX4500.

It isn't a particularly useful list so I have left that out for
the moment.  The VX6000 places them in the EFS after a reboot
if the index file is empty (copying them from its internal ROM).
Basically you can't get rid of them, and they keep reappearing
if you have nothing else present.

Roger

[Bitpim-devel] Build time again ...

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

I've updated, built and committed the help.  I don't have any outstanding
changes so it is all go from my end.

Steven, you may want to ensure that the BitFling setting doesn't appear
in the settings dialog.  If you remove M2Crypto it should fail to import
and the setting won't appear.

Roger

Re: [Bitpim-devel] LG VX6000- RINGTONES

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

Please read ALL of the following links and then post your question
again.

   http://www.catb.org/~esr/faqs/smart-questions.html

   http://bitpim.sourceforge.net/testhelp/trouble-serial.htm

   http://bitpim.sourceforge.net/testhelp/support.htm

Roger

[Bitpim-devel] LG VX6000- RINGTONES

[<DRE...@ao...>]

Hi ya doing? I hope you are the expert in fixing issiues regarding the LG 
VX6000 phone.Be patient with me please. i recently bought a ringtones cd to work 
on my phone.i put the cd in. now what? dont laugh please.i think i got the 
songs i want to put on my phone, cause i got a list of about 6 on the panel 
involving BITPIM.i highlight the song then on the top where the dialog boxes are i 
clicked both GET PHONE DATA and SEND PHONE DATA,but get this error 
message.Failed to Auot-Detect the port to use.I couldnt detect any candidate ports. ok, i 
also went to the top again and checked my settings inthe BITPIM CONTROL. IT 
FOUND A COM 3 PORT but the phone settings said 4400. so i chaged it to of 
course the vx6000. When i try to get out of the settings and go back it keeps on 
saying the vx4400.I dont know and i am losing patience.PLEASE BE PATIENT with me 
and explain to me step by step from the beginning what i did wrong or have to 
do> PLEASE 
    
    
    
    
    

[Bitpim-devel] vx4500 update

[Tom P. <mlp...@ea...>]

Hi,

I've attached a copy of the com_lgvx4500.py file that's been updated 
with the correct builtin ringtones and images. I don't know if this is 
useful or not, but it can't hurt to have the correct lists.

The builtinimagesEMS list is a list of additional images that are 
available as wallpaper on the VX4500.  I don't know how to reference 
them.  (I also don't know where any of these images and sounds are 
stored on the phone!)

Cheers,

Tom

[Bitpim-devel] Re: [Bitpim-user] Bitpim Ringers Tab display bug

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

[Please followup on the bitpim-devel mailling list]

Jeff Milstead wrote:
> Roger, just FYI, but I built BitPim 0.7-test6 OS X
> 10.2.8 from CVS today and noticed that although I have
> ringers loaded, the ringers tab only displays the
> ringer filenames momentarily after I drag-resize the
> BitPim window. Otherwise, the ringers tab remains
> blank.

A known problem with wxWidgets on Mac and Linux - 
see the download site.

That is why I rewrote the display used for media (wallpaper,
ringtones etc).  So far I have only had time to change the
wallpaper over to the new widgets which do work everywhere
correctly.

> The other thing I noticed on the Mac is that BitPim
> seems to quit when you put it into the background
> while it is doing a lengthy access of the phone - say,
> when you're dumping the filesystem.

My only guess as to what it may be caused by print statements,
especially ones that are not in the main thread.  You can
test this theory by commenting out all print statements
and seeing if that fixes it (a small sed script will do the trick).
Eventually all the print statements will be removed anyway.

Roger

Re: [Bitpim-devel] vx4500 phone

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

> If I can get you a vx4500 phone to use for development
> will you be able to do anything without activating the
> phone.  I talked to verizon and they tell me that the
> only way to activate this phone is with a 1 or 2 year
> contract... prepay wont work.

I can easily work with a phone that isn't activated.
What I do is the ESN swaps online if I need it active
for any period.  I would recommend holding off for a
few weeks to see how well my BitFling work goes.

These are the terms and conditions I send anyone who
does want to supply a phone:

========================================================

Responsibilities:

 - No money will change hands
 - You will ship me a phone, some sort of charging mechanism
   and a cable
 - When you want the phone back, I will return it, with you
   paying the shipping and insurance
 - You understand that I may make the phone non-functional and
   I will not be responsible should that happen
 - Should the phone be lost or damaged through no wilful action
   on my behalf (for example fire, theft) then I will not be
   financially responsible for it
 - The phone, cable and other accessories remain your property
 - The phone will be capable of being activated on the Verizon
   network.  I may chose to do so, and will deactivate it
   before returning the phone to you if I do.
 - All code I write is under my copyright, and you have no rights
   to it at all.  It will become a standard part of the BitPim
   source and be under the same license as the rest of BitPim
 - I will endeavour to add phone support to BitPim as my schedule
   and other commitments allow.  I would expect that the next
   major release of BitPim would contain the support
 - Either side can cancel this arrangement at any time
 - I will be under no obligation to provide you or your customers
   with support

Branding:

 - Upon receipt of the phone and some initial investigation I will
   add some text to the "Other phones" section of the BitPim website
   http://bitpim.sourceforge.net/#otherphones

   It will be substantially similar to:

    <Model> support is also being added.  This is helped by <You>
    providing me with the phone and cable while I work on
    the code.  You can thank them for their support by <buying
    from website etc>

   Similar text will be in the online help section on the phone.

 - The text will remain part of the BitPim website and online help
   for a period of time at my discretion

Software:

 - I will not produce a special version of BitPim.  You will be
   able to download standard versions from the BitPim website.
   Any distribution of the standard version or a special version
   you may produce has to be within the terms of the GNU GPL
   License: http://www.gnu.org/copyleft/gpl.html

   Please notice its requirements to do with distribution, fees
   and modified versions.

 - BitPim will not be limited to only working with your
   cable or phone, nor will there be a version that does so

========================================================

Roger

[Bitpim-devel] vx4500 phone

[greg c. <gre...@ya...>]

If I can get you a vx4500 phone to use for development
will you be able to do anything without activating the
phone.  I talked to verizon and they tell me that the
only way to activate this phone is with a 1 or 2 year
contract... prepay wont work.  

thanks
greg

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

Re: [Bitpim-devel] Code for TM520

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

> Seems that the pim/index.dat is more a checksum of the last 7 digits of each
> phone number rather than an actual index. Ran into a few speed bumps testing
> but I think the code is good to go except for moving speed dial.

Here is how the VX4400/VX6000 do it (and probably later models as well).

pim/pbentry.dat

   This contains information about all the entries with a fixed size
   record.  It doesn't however contain any phone numbers.

pim/pbnumber.dat

   This contains all the phone numbers.  I haven't looked too deeply
   into the format, and can't really tell if it uses fixed or variable
   length records.  The actual phone numbers are stored as binary
   coded decimal, with a nibble of 'e' marking the end of the
   number.  For example the number (123) 555-9812 is stored like
   this in hex:   12 35 55 98 12 e0

pim/pbspeed.dat

   This contains space for 100 speed dial numbers (2 bytes per number)
   and indexes into pbnumber.dat in some way I haven't determined.

Roger

[Bitpim-devel] Code for TM520

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

I know it has been expired while I was busy with other things, but I have
tested the code for writing out the phonebook. The only problem I have is
that I can't change the speed dial of an existing entry - I can move its
association to a different number within the same entry, and I can create
new speed dial entry, just couldn't move an existing one. There must be some
sort of magic done because the serial doesn't change when I perform the same
operation right on the phone (changing the speed dial). I think we just need
to put a few phone-specific hooks in the getphonebook and savephonebook
function in order to move those into com_lg and make them common routines.

Seems that the pim/index.dat is more a checksum of the last 7 digits of each
phone number rather than an actual index. Ran into a few speed bumps testing
but I think the code is good to go except for moving speed dial.

[Bitpim-devel] Re: [Bitpim-user] Samsung A620 - timeout issue?

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

> 0:21:34.217 Samsung A620: brew response Data - 6 bytes
> <#! p_brew.listdirectoriesresponse !#>
> 00000000 59 02 00 00 00 ff                                   Y.....

You can view this in the analyser.  

59 commandmode
02 command
00 errorcode

The next two bytes are the number of entries, in this case zero.
The next two bytes after that are the data length followed by
the subdirectories.

The A620 looks like it can have nonsense if there are zero entries.

I have changed the description so that if there are zero entries,
the rest of the packet is ignored.

Here is how I diagnosed and fixed this:

  - I looked at your file in the analyser (run analyser.py supplying
    filename with contents, or with no arguments and what you want to
    view in the clipboard).  You can also bring up the analyser in
    BitPim pressing Ctrl-Alt-P (if you have anything highlighted then
    only that is shown).

    That showed how far into the packet things were parsed.

  - I then looked at the description in p_brew.p which showed that the
    above is nonsense after numentries==0

  - I added an if statement so the rest of the packet is only looked
    at if there are more than zero entries

  - I verified that the code in com_brew.py did not look at the other
    fields (datalen, items) if numentries is zero (as they wouldn't
    exist).

  - I then checked the code still worked on two different phones on
    directories that did and did not contain subdirectories

  - Then I committed the whole lot back to CVS :-)

> I'm trying to come up to speed on the python language, how cell phone
> communication is performed, and how bitpim works, so please bear with me.

You may find the code cross referencer as well as API documentation quite
useful (programming language section on developer page).

> Is there any documentation on how to start adding support for a new phone?

web/phonespec.html

> My guess is that I'll need to cut-n-paste the brew communication code

Cut-n-paste of code is bad!  In general you override things in derived
classes.

> and
> add some sort of retry on the listdirectoriesresponse when this case occurs,
> but for all I know the retry might need to belong in the brew code too.

Although the subject says "timeout", the error you got didn't say timeout
and my investigation above shows it is a data formatting issue that
is now fixed.

> Is there any sort of existing documentation on the brew protocol?

Yes, the BitPim source code :-)

Roger