[Bitpim-devel] 0.7 test1 notes

[Stephen Wood]

I have gotten some feedback on the Sanyo phone support from sprintusers
and howardforums readers who have tried BitPim 0.7test1.

1. Several windows users got stuck initially because BitPim didn't auto
detect their phone and they didn't know what to do. I can add some
notes to the help, but is there anything else that can be done help
users here? (On my XP system, the port browser shows COM1 and COM2, but
my phone is know to windows as a modem on COM4.)

2. A MacOS user was successfull using BitPim with an 8100.

3. While it is explained in the help that media are not supported for
the Sanyo phones, that is not clear from the application itself. A user
tried to download wallpaper and ringtones from his 4900 and got a python
error. Is there a way I can pop up an error, or can the
wallpaper/ringer items in the get and send be disabled when they are not
supported.

4. A user reported success with the phonebook for the SCP-7200. The
7200 is a newer Sprint Readylink (push to talk) phone. He also reported
that he got an error when trying to download the calendar.
Unfortunately, I have not be able to get a more descriptive error report
than that yet. But this gives hope to my suspicion that it will be easy
for BitPim to support at least the phonebook for most of Sanyo's phones.


I have tried to encourage people to report the experience on
bitpim-user, but I think without too much success.

Steve

[Roger Binns]

Post by Stephen Wood
1. Several windows users got stuck initially because BitPim didn't auto
detect their phone and they didn't know what to do. I can add some
notes to the help, but is there anything else that can be done help
users here? (On my XP system, the port browser shows COM1 and COM2, but
my phone is know to windows as a modem on COM4.)

Currently on Windows it only lists serial ports, not modems. I did
experiment with a one line change and the modems are detected as
well. However the modem is the wrong thing to pick for the LG phones.

The correct fix will be:

- In the listing of ports, add in a 'class' that shows if the
port is a com port or a modem
- In the code that selects the device, it should pay attention
to the class

Post by Stephen Wood
3. While it is explained in the help that media are not supported for
the Sanyo phones, that is not clear from the application itself. A user
tried to download wallpaper and ringtones from his 4900 and got a python
error. Is there a way I can pop up an error, or can the
wallpaper/ringer items in the get and send be disabled when they are not
supported.

My intention was to have the wallpaper/ringtone panes removed if the
currently selected phone didn't support it. It is actually going to
be considerably easier to just disable them, and the relevant portion
of the get/send dialogs. (I currently detest the get/send dialog
so if you want to make something better, please volunteer or make
a suggested screenshot). The per phone profile will then contain
information about what features the phone/bitpim supports.

Post by Stephen Wood
I have not be able to get a more descriptive error report
than that yet.

I have had a few of those :-) I did update the help for support
and now just point people at that.

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

Post by Stephen Wood
I have tried to encourage people to report the experience on
bitpim-user, but I think without too much success.

Yup, I have the same problem. I get very impressed by the non-LG
people who mail me at the SourceForge address as well as the
address from the vx4400 FAQ on my website.

These things just take time, and will correct themselves with
enough gentle persuasion. I always make sure I deal with stuff
on the bitpim groups first, and give more detailed and helpful
answers there. Often I refuse to answer stuff in personal email
unless they post to the lists. (If I am going to use my time
to answer stuff, it is way more beneficial for all involved
that everyone sees the answers, and can comment on the original
question and issues).

I will make an effort to fix both 1 & 3 before the next test
release (I would like to do them every two weeks or so).
However I may be out of action for up to a week. I am having
some "oral surgery" (it sounds really wierd to me) to correct
some British dentistry.

Roger

[Roger Binns]

Post by Stephen Wood
1. Several windows users got stuck initially because BitPim didn't auto
detect their phone and they didn't know what to do. I can add some
notes to the help, but is there anything else that can be done help
users here? (On my XP system, the port browser shows COM1 and COM2, but
my phone is know to windows as a modem on COM4.)

I have now implemented the fix for this. ports now have a "class" field
which is "serial" or "modem". (The LG phones are on serial, the Sanyo
on modem).

The usb information is now in the profile for each phone class. I put
the sanyo entry into com_sanyo, so you will need to update that if
it differs by model.

Steven, can you please update the comscanmac function in comscan.py
to note if the device is a serial or modem. I think the Mac uses
/dev/cu.usbserial and /dev/cu.usbmodem respectively. res["class"]
should be set the the right value in the loop.

Roger

[Stephen Wood]

Post by Roger Binns
The usb information is now in the profile for each phone class. I put
the sanyo entry into com_sanyo, so you will need to update that if
it differs by model.

Will the usbids in com_sanyo.py prevent a phone with different ID's from
working? If so, I should move the usbids to the 4900 specific code and
leave it blank for phones that I don't know the id's for.

Could one of the SCP-8100 owners get the USB id's for that phone.

Also, if there is anyone with a different Sanyo phone (5300 or the new
readylink or video phones), could you also post your USB ids along with
your phone model.

Steve

[Roger Binns]

Post by Stephen Wood
Will the usbids in com_sanyo.py prevent a phone with different ID's from
working?

They won't be selected as part of auto guessing and they won't have a (*)
next to them in the com port browser.

Post by Stephen Wood
If so, I should move the usbids to the 4900 specific code and
leave it blank for phones that I don't know the id's for.

Yup. The LG uses the same vid/pid for the 4400 and 6000. I haven't
heard from anyone with other models.

If any of the phones use usb to serial cables, you will need their
vid/pid in there as well.

Roger

[Steven Palm]

Post by Roger Binns
Steven, can you please update the comscanmac function in comscan.py
to note if the device is a serial or modem. I think the Mac uses
/dev/cu.usbserial and /dev/cu.usbmodem respectively. res["class"]
should be set the the right value in the loop.

I'm not sure if it is that simple... Maybe it is for the
drivers/cables commonly used for cell phones, but, for example, the
very popular USB<-->Serial adapters made by KeySpan show up like this:

- /dev/tty.KeyUSA28X<geo>1 -- or -- /dev/cu.KeyUSA28X<geo>1
- /dev/tty.KeyUSA28X<geo>2 -- or -- /dev/cu.KeyUSA28X<geo>2

where <geo> is the 2 or more digit geographical name. (e.g. "913"
means USB bus #9, host hub port #1 and external hub port #3)

I did find a reference to the Prolific chipset and the driver they
have for MacOS X does, as far as I can tell, use usbserial.

Since this is so arbitrary, depending on the vendor's driver and
choice of text string they use when constructing the name, I'd hesitate
to code to it, it's not quite a standard. However, if there is a choice
that must be made to make things work properly I guess we can just punt
and hope for the best.

-. ----. -.-- - -.--
Steve Palm - ***@n9yty.com
-. ----. -.-- - -.--

[Roger Binns]

Post by Steven Palm
Since this is so arbitrary, depending on the vendor's driver and
choice of text string they use when constructing the name, I'd hesitate
to code to it, it's not quite a standard. However, if there is a choice
that must be made to make things work properly I guess we can just punt
and hope for the best.

Generally mark everything as serial unless you know it is a modem.

The Sanyo phones are only modem. The LG should present a modem and a
serial interface, and they should be marked as such (so the autodetect
code picks/excludes the right thing).

Roger

[Steven Palm]

Post by Roger Binns
Generally mark everything as serial unless you know it is a modem.
The Sanyo phones are only modem. The LG should present a modem and a
serial interface, and they should be marked as such (so the autodetect
code picks/excludes the right thing).

Maybe we're not on the same page here....

When I'm just scanning a list of devices that exist in the /dev
filesystem, how am I to know what is or is not a modem or serial
interface? That was my question. I can't be assured that the chosen
string by the vendor will be representative of the actual use of the
device.

The LG phone on my creates a /dev/cu.usbmodemXXX and a
/dev/tty.usbmodemXXX entry. There is no "serial" interface created as
such. Now, in the case of the KeySpan adapter (which you may have
connected and have found some way to plug your phone in to this using
some serial adapter cable combination), I have no idea what it is.

At any rate, what logic are you using on Linux and/or Windows to know
this information? Are you just guessing as well, or does the system
present more concrete information to you? How would the system tell me
that it *is* a modem so I would know it's not serial?

Sorry for the ignorance here, but I'm missing something.

-. ----. -.-- - -.--
Steve Palm - ***@n9yty.com
-. ----. -.-- - -.--

[Adit Panchal]

Hi all,

I have been monitoring this project for a little while and thought I
might share some input. I am not sure if this is the right place to do
so, since I am not a member of the development team. I know how to code,
but I have not dabbled in Python before. I downloaded the appropriate
libraries, and have fiddled around with the code a little.

Anyways, I have a Sanyo SCP-5500 (Readylink/video phone) and the USB
device ID shows up the same as the SCP-4900 listed in com_sanyo.py. I am
using the FutureDial drivers and the phone works in other programs. I
have been successful in getting the filesystem view to work, but I get
an error when trying to import any kind of data.

Here is the output of what USB View says for my phone:

Device Descriptor:
bcdUSB: 0x0101
bDeviceClass: 0x02
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 (8)
idVendor: 0x0474 (Sanyo Electric Co. Ltd.)
idProduct: 0x0701
bcdDevice: 0x0000
iManufacturer: 0x01
iProduct: 0x02
iSerialNumber: 0x03
bNumConfigurations: 0x01

Here is the error for example when trying to import the phonebook
(latest CVS checkout around 1AM 01/12/04):

Traceback (most recent call last):
File "C:\projects\bitpim\bitpim\gui.py", line 148, in run
res=call()
File "C:\projects\bitpim\bitpim\gui.py", line 89, in __call__
return apply(self.method, self.args+args, d)
File "C:\projects\bitpim\bitpim\gui.py", line 1037, in getdata
i[1](results)
File "C:\projects\bitpim\bitpim\com_sanyo.py", line 218, in getphonebook
buf=prototypes.buffer(self.getsanyobuffer(sortstuff.startcommand,
sortstuff.bufsize, "sort buffer"))
File "C:\projects\bitpim\bitpim\com_sanyo.py", line 98, in getsanyobuffer
res=self.sendpbcommand(req, p_sanyo.bufferpartresponse);
File "C:\projects\bitpim\bitpim\com_sanyo.py", line 133, in sendpbcommand
self.setmode(self.MODEPHONEBOOK)
File "C:\projects\bitpim\bitpim\com_phone.py", line 96, in setmode
res=getattr(self, func)()
File "C:\projects\bitpim\bitpim\com_sanyo.py", line 70, in
_setmodephonebook
self.sendpbcommand(req, respc, callsetmode=False)
File "C:\projects\bitpim\bitpim\com_sanyo.py", line 163, in sendpbcommand
res.readfrombuffer(buffer)
File "C:\projects\bitpim\bitpim\p_sanyo.py", line 213, in readfrombuffer
self.__field_date3.readfrombuffer(buf)
File "C:\projects\bitpim\bitpim\prototypes.py", line 320, in
readfrombuffer
self._value=buf.getnextbytes(self._sizeinbytes)
File "C:\projects\bitpim\bitpim\prototypes.py", line 766, in getnextbytes
raise IndexError("Trying to read "+`howmany`+" bytes starting at
"+`self._offset`+" which will go beyond end of "+`len(self._data)`+"
byte buffer")
IndexError: Trying to read 11 bytes starting at 48 which will go beyond
end of 55 byte buffer

Variables by last 6 frames, innermost last

Frame setmode in C:\projects\bitpim\bitpim\com_phone.py at line 98
desiredmode = 'modephonebook'
self = <com_sanyo8100.Phone instance at 0x019E0E68>
strmode = 'brew'
strdesiredmode = 'phonebook'
func = '_setmodephonebook'
v = 'writefile'

Frame _setmodephonebook in C:\projects\bitpim\bitpim\com_sanyo.py at line 73
self = <com_sanyo8100.Phone instance at 0x019E0E68>
req = <p_sanyo.firmwarerequest object at 0x019CE9B0>
respc = <class 'p_sanyo.firmwareresponse'>

Frame sendpbcommand in C:\projects\bitpim\bitpim\com_sanyo.py at line 163
writemode = False
d = -1
responseclass = <class 'p_sanyo.firmwareresponse'>
buffer = <prototypes.buffer instance at 0x019EADA0>
res = <p_sanyo.firmwareresponse object at 0x019CE1F0>
callsetmode = False
firsttwo = '\x00x'
request = <p_sanyo.firmwarerequest object at 0x019CE9B0>
data = '\x00Oct 30 200316:13:13Feb 17 200309:00:00SCP5500
j\x06\x16
self = <com_sanyo8100.Phone instance at 0x019E0E68>
numretry = 0

Frame readfrombuffer in C:\projects\bitpim\bitpim\p_sanyo.py at line 213
buf = <prototypes.buffer instance at 0x019EADA0>
self = <p_sanyo.firmwareresponse object at 0x019CE1F0>
dict = {'sizeinbytes': 11, 'terminator': None}

Frame readfrombuffer in C:\projects\bitpim\bitpim\prototypes.py at line 320
self = <prototypes.STRING object at 0x019CE390>
buf = <prototypes.buffer instance at 0x019EADA0>

Frame getnextbytes in C:\projects\bitpim\bitpim\prototypes.py at line 766
self = <prototypes.buffer instance at 0x019EADA0>
howmany = 11

I hope this helps for the project.

Adit

[Roger Binns]

I am not sure if this is the right place to do so,

Techie information is always welcome.

Anyways, I have a Sanyo SCP-5500 (Readylink/video phone) and the USB
device ID shows up the same as the SCP-4900 listed in com_sanyo.py.

It looks like they use the same pid for all Sanyo USB phones, which
is nice.

Here is the error for example when trying to import the phonebook

It will be more helpful if you also turn on the protocol logging.

Roger

[Adit Panchal]

Post by Roger Binns

Post by Adit Panchal
Here is the error for example when trying to import the phonebook

It will be more helpful if you also turn on the protocol logging.
Roger

Protocol log when I try to browse the file system of my SCP-5500:

15:27:14.427 COM5: USB support is not available
15:27:14.427 COM5: Opening port COM5, 115200 baud, timeout 3.000000,
hardwareflow 0, softwareflow 0
15:27:14.447 COM5: Open of comm port suceeded
15:27:14.447 SCP-8100: Attempting to contact phone
15:27:14.447 SCP-8100: Listing dir ''
15:27:14.457 SCP-8100: brew request Data - 2 bytes
<#! p_brew.memoryconfigrequest !#>
00000000 59 0c Y.

15:27:14.457 SCP-8100: brew response Data - 7 bytes
<#! p_brew.memoryconfigresponse !#>
00000000 59 0c 00 60 9a 12 00 Y..`...

15:27:14.467 SCP-8100: Now in brew mode
15:27:14.467 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 00 00 00 00 02 2f 00 Y....../.

15:27:14.486 SCP-8100: brew response Data - 35 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 00 00 00 00 ff 00 01 03 00 00 00 00 ea
Y...............
00000010 00 00 00 00 02 00 00 00 0a 24 55 53 45 52 5f 44
.........$USER_D
00000020 49 52 53 IRS

15:27:14.486 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 01 00 00 00 02 2f 00 Y....../.

15:27:14.506 SCP-8100: brew response Data - 37 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 01 00 00 00 37 00 01 03 00 00 00 00 ce
Y......7........
00000010 00 00 00 00 02 00 00 00 0c 24 53 59 53 2e 46 41
.........$SYS.FA
00000020 43 54 4f 52 59 CTORY

15:27:14.516 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 02 00 00 00 02 2f 00 Y....../.

15:27:14.536 SCP-8100: brew response Data - 38 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 02 00 00 00 ff 00 01 00 00 00 00 00 5a
Y..............Z
00000010 00 00 00 00 02 00 00 00 0d 75 69 76 72 53 74 61
.........uivrSta
00000020 74 65 2e 64 61 74 te.dat

15:27:14.546 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 03 00 00 00 02 2f 00 Y....../.

15:27:14.556 SCP-8100: brew response Data - 31 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 03 00 00 00 ff 00 01 00 00 00 00 00 40
Y..............@
00000010 00 00 00 00 02 00 00 00 06 43 4c 4b 5f 44 42 .........CLK_DB

15:27:14.556 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 04 00 00 00 02 2f 00 Y....../.

15:27:14.566 SCP-8100: brew response Data - 37 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 04 00 00 00 ff 00 00 00 00 00 00 00 06
Y...............
00000010 00 00 00 00 02 00 00 00 0c 52 44 4d 5f 50 4f 52
.........RDM_POR
00000020 54 5f 4d 41 50 T_MAP

15:27:14.566 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 05 00 00 00 02 2f 00 Y....../.

15:27:14.576 SCP-8100: brew response Data - 33 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 00 05 00 00 00 ff 00 01 00 00 00 00 00 bc
Y...............
00000010 00 00 00 00 02 00 00 00 08 24 53 59 53 5f 52 4d
.........$SYS_RM
00000020 54 T

15:27:14.586 SCP-8100: brew request Data - 9 bytes
<#! p_brew.listfilerequest !#>
00000000 59 0b 06 00 00 00 02 2f 00 Y....../.

15:27:14.596 SCP-8100: brew response Data - 3 bytes
<#! p_brew.listfileresponse !#>
00000000 59 0b 1c Y..

15:27:14.596 SCP-8100: brew request Data - 4 bytes
<#! p_brew.listdirectoriesrequest !#>
00000000 59 02 01 00 Y...

15:27:14.766 SCP-8100: brew response Data - 263 bytes
<#! p_brew.listdirectoriesresponse !#>
00000000 59 02 00 04 00 16 00 6e 76 6d 00 56 6f 69 63 65
Y......nvm.Voice
00000010 44 42 00 56 6f 69 63 65 00 43 4d 00 00 5f 52 4d
DB.Voice.CM.._RM
00000020 54 ad de 41 50 ad de de b0 1f 00 00 ff ff 00 00
T..AP...........
00000030 06 16 b8 01 02 f0 53 ad de ff ff ff ff ff ff ff
......S.........
00000040 ff ff ff ff ff ff ff ff 90 1f 00 00 ff ff 00 00
................
00000050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000060 15 68 79 56 8d 35 02 12 a5 ab 64 0d ff ff ff ff
.hyV.5....d.....
00000070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000100 ff ff ff ff ff ff ff .......


-----------------------------------------------------------------
-----------------------------------------------------------------

Protocol log when I try to import the phonebook from my SCP-5500 in the
same session of bitpim:

15:30:25.111 SCP-8100: Retrieving fundamental phone information
15:30:25.141 SCP-8100: Phone serial number
15:30:25.141 SCP-8100: Getting file contents 'nvm/$SYS.ESN'
15:30:25.141 SCP-8100: brew request Data - 17 bytes
<#! p_brew.readfilerequest !#>
00000000 59 04 00 0d 6e 76 6d 2f 24 53 59 53 2e 45 53 4e
Y...nvm/$SYS.ESN
00000010 00 .

15:30:25.151 SCP-8100: brew response Data - 267 bytes
<#! p_brew.readfileresponse !#>
00000000 59 04 00 00 00 61 00 00 00 61 00 ff ff ff ff ff
Y....a...a......
00000010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000060 15 68 79 56 8d 35 02 12 a5 ab 64 0d ff ff ff ff
.hyV.5....d.....
00000070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
000000f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
................
00000100 ff ff ff ff ff ff ff ad de ff ff ...........

15:30:25.151 SCP-8100: expected size 97 actual 97
15:30:25.151 SCP-8100: Fundamentals retrieved
15:30:25.151 SCP-8100: Sanyo phonebook request Data - 1 bytes
<#! p_sanyo.firmwarerequest !#>
00000000 00 .

15:30:25.151 SCP-8100: sanyo phonebook response Data - 55 bytes
<#! p_sanyo.firmwareresponse !#>
00000000 00 4f 63 74 20 33 30 20 32 30 30 33 31 36 3a 31 .Oct 30
200316:1
00000010 33 3a 31 33 46 65 62 20 31 37 20 32 30 30 33 30 3:13Feb 17
20030
00000020 39 3a 30 30 3a 30 30 53 43 50 35 35 30 30 20 6a
9:00:00SCP5500 j
00000030 06 16 b8 01 02 f0 53 ......S

15:30:25.171 Exception: An unexpected exception has occurred.
Please see the help for details on what to do.

Traceback (most recent call last):
File "gui.pyo", line 148, in run
File "gui.pyo", line 89, in __call__
File "gui.pyo", line 1036, in getdata
File "com_sanyo.pyo", line 218, in getphonebook
File "com_sanyo.pyo", line 98, in getsanyobuffer
File "com_sanyo.pyo", line 133, in sendpbcommand
File "com_phone.pyo", line 96, in setmode
File "com_sanyo.pyo", line 70, in _setmodephonebook
File "com_sanyo.pyo", line 163, in sendpbcommand
File "p_sanyo.pyo", line 213, in readfrombuffer
File "prototypes.pyo", line 320, in readfrombuffer
File "prototypes.pyo", line 766, in getnextbytes
IndexError: Trying to read 11 bytes starting at 48 which will go beyond
end of 55 byte buffer

Variables by last 6 frames, innermost last

Frame setmode in com_phone.pyo at line 98
desiredmode = 'modephonebook'
self = <com_sanyo8100.Phone instance at 0x01AB1940>
strmode = 'brew'
strdesiredmode = 'phonebook'
func = '_setmodephonebook'
v = 'writefile'

Frame _setmodephonebook in com_sanyo.pyo at line 73
self = <com_sanyo8100.Phone instance at 0x01AB1940>
req = <p_sanyo.firmwarerequest object at 0x01AC2C70>
respc = <class 'p_sanyo.firmwareresponse'>

Frame sendpbcommand in com_sanyo.pyo at line 163
writemode = False
d = -1
responseclass = <class 'p_sanyo.firmwareresponse'>
buffer = <prototypes.buffer instance at 0x00B09878>
res = <p_sanyo.firmwareresponse object at 0x01AC26D0>
callsetmode = False
firsttwo = '\x00x'
request = <p_sanyo.firmwarerequest object at 0x01AC2C70>
data = '\x00Oct 30 200316:13:13Feb 17 200309:00:00SCP5500
j\x06\x16
self = <com_sanyo8100.Phone instance at 0x01AB1940>
numretry = 0

Frame readfrombuffer in p_sanyo.pyo at line 213
buf = <prototypes.buffer instance at 0x00B09878>
self = <p_sanyo.firmwareresponse object at 0x01AC26D0>
dict = {'sizeinbytes': 11, 'terminator': None}

Frame readfrombuffer in prototypes.pyo at line 320
self = <prototypes.STRING object at 0x01AC2950>
buf = <prototypes.buffer instance at 0x00B09878>

Frame getnextbytes in prototypes.pyo at line 766
self = <prototypes.buffer instance at 0x00B09878>
howmany = 11

-----------------------------------------------------------------
-----------------------------------------------------------------

I hope this helps. I was using BitPim 0.7-test1 using a Gomadic USB
cable. I also wanted to add that I tried importing the phone book from
my dad's SCP-5300 and it works fine. It does not however import the
pictures or ringers.

Adit

[Adit Panchal]

I forgot to add that the filesystem view works fine. Sometimes the
program can't auto-detect my phone; other times it can.

Post by Adit Panchal
Protocol log when I try to import the phonebook from my SCP-5500 in the

The phonebook does not work at all it just gives an exception as I just
wrote before.

Adit

[Roger Binns]

Post by Adit Panchal
I hope this helps. I was using BitPim 0.7-test1 using a Gomadic USB
cable. I also wanted to add that I tried importing the phone book from
my dad's SCP-5300 and it works fine. It does not however import the
pictures or ringers.

Ok, Stephen is working on this. One of the packets is gratutiously
different on the 5500.

Roger

[Stephen Wood]

Post by Adit Panchal
...
<#! p_sanyo.firmwarerequest !#>
00000000 00 .
15:30:25.151 SCP-8100: sanyo phonebook response Data - 55 bytes
<#! p_sanyo.firmwareresponse !#>
00000000 00 4f 63 74 20 33 30 20 32 30 30 33 31 36 3a 31 .Oct 30
200316:1
00000010 33 3a 31 33 46 65 62 20 31 37 20 32 30 30 33 30 3:13Feb 17
20030
00000020 39 3a 30 30 3a 30 30 53 43 50 35 35 30 30 20 6a
9:00:00SCP5500 j
00000030 06 16 b8 01 02 f0 53 ......S
...

The cause of this exception has been found. It turns out that the 5500
returns a smaller firmware version packet than other Sanyo phones. I
have made a change that will get past this. Either the phone book read
will work or quickly fail on yet another difference. When 0.7 test 2
comes out, give it a try again. (If you are setup to run from the CVS
version, email me for a patch. The public CVS hasn't caught up with my
change yet.)

Post by Adit Panchal
I hope this helps. I was using BitPim 0.7-test1 using a Gomadic USB
cable. I also wanted to add that I tried importing the phone book from
my dad's SCP-5300 and it works fine. It does not however import the
pictures or ringers.

Thanks for testing the 5300. I thought it should work, but didn't know
for sure. There is no picture or ringer code for Sanyo phones.

Could you try reading or writing the calendar on the 5300? That
"should" also work, but again, I don't really know for sure.

Stephen

[Adit Panchal]

Post by Stephen Wood

Post by Adit Panchal
...
<#! p_sanyo.firmwarerequest !#>
00000000 00 .
15:30:25.151 SCP-8100: sanyo phonebook response Data - 55 bytes
<#! p_sanyo.firmwareresponse !#>
00000000 00 4f 63 74 20 33 30 20 32 30 30 33 31 36 3a 31 .Oct 30
200316:1
00000010 33 3a 31 33 46 65 62 20 31 37 20 32 30 30 33 30 3:13Feb 17
20030
00000020 39 3a 30 30 3a 30 30 53 43 50 35 35 30 30 20 6a
9:00:00SCP5500 j
00000030 06 16 b8 01 02 f0 53 ......S
...

The cause of this exception has been found. It turns out that the 5500
returns a smaller firmware version packet than other Sanyo phones. I
have made a change that will get past this. Either the phone book read
will work or quickly fail on yet another difference. When 0.7 test 2
comes out, give it a try again. (If you are setup to run from the CVS
version, email me for a patch. The public CVS hasn't caught up with my
change yet.)

Will give it a shot with the patch. Having problems running the latest
build from CVS though - it worked fine earlier (last week). Updated
today and it gives an exception on startup (unrelated to 5500 issues).

Post by Stephen Wood

Post by Adit Panchal
I hope this helps. I was using BitPim 0.7-test1 using a Gomadic USB
cable. I also wanted to add that I tried importing the phone book from
my dad's SCP-5300 and it works fine. It does not however import the
pictures or ringers.

Thanks for testing the 5300. I thought it should work, but didn't know
for sure. There is no picture or ringer code for Sanyo phones.
Could you try reading or writing the calendar on the 5300? That
"should" also work, but again, I don't really know for sure.
Stephen

I think the calendar works on the 5300. I forgot to mention that because
it didn't give an error like the picture or ringer code did. My dad's
phone didn't have any calendar information in it. I'll give it a shot
the next chance I get.

Adit

[John H.]

I know someone mentioned that sanyo 4900 media support would be added very soon.

Please post to the list when that is the case:)

_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com