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