Discussion:
[BitPim-devel] USTRING "encoding" behavior different from STRING's ?
Joe Pham
2006-04-19 22:34:08 UTC
Permalink
I'm in the process of writing support for my Motorola V3c (VZW), and
I mostly have the OBEX support complete.
I was just about to start doing that for the V710. If you're willing to contribute your code to the project, please post or email me your code and I'll roll it into the main trunk.
I still haven't figured out how to switch from mode OBEX back to
MODEM.
Not sure what you meant by that. Please be more specific.
I noticed that there's the V710 being added recently and it does
share a lot of common features that should possibly moved to a
superclass. com_motov.py maybe.
There's already a com_moto.

-Joe Pham



_____________________________________________________________________
Call Anyone, Anytime, Anywhere in the World - FREE!
Free Internet calling from NetZero Voice
Visit http://www.netzerovoice.com today!
Perry Nguyen
2006-04-20 17:07:44 UTC
Permalink
Post by Joe Pham
I'm in the process of writing support for my Motorola V3c (VZW), and
I mostly have the OBEX support complete.
I was just about to start doing that for the V710. If you're willing to contribute your code to the project, please post or email me your code and I'll roll it into the main trunk.
In fact, I am willing to contribute the code, I was just waiting for my
implementation to be more complete. For the OBEX portion, I have completed
folder listings and object retrieval. OBEX PUT and DELETE (variation of PUT)
have not been implemented yet. I would be glad to share my work.

Attached is the source of my modules. (my com_motov3cm.py is starting to
inherit from com_moto.py, but I actually haven't used anything from the
superclass yet).
Post by Joe Pham
I still haven't figured out how to switch from mode OBEX back to
MODEM.
Not sure what you meant by that. Please be more specific.
Once I do AT+MODE=22, switching to OBEX mode, I am no longer able to send AT
commands, the device will not respond; it only responds to OBEX requests, even
once disconnected. I have been doing port snoops of Motorola Phone tools on
Windows and seen that it simply closes, resets and re-opens the port. But I
have not been able to duplicate that behavior on Linux yet. (Then again, I
haven't been able to spend that much time on it).
Post by Joe Pham
I noticed that there's the V710 being added recently and it does
share a lot of common features that should possibly moved to a
superclass. com_motov.py maybe.
There's already a com_moto.
Right, but there is stuff in com_motov710.py that is common to my
com_motov3cm.py, e.g. groups.
Post by Joe Pham
-Joe Pham
Perry Nguyen
2006-04-20 17:38:31 UTC
Permalink
Post by Perry Nguyen
Post by Joe Pham
I still haven't figured out how to switch from mode OBEX back to MODEM.
Not sure what you meant by that. Please be more specific.
Once I do AT+MODE=22, switching to OBEX mode, I am no longer able to
send AT commands, the device will not respond; it only responds to OBEX
requests, even once disconnected. I have been doing port snoops of
Motorola Phone tools on Windows and seen that it simply closes, resets
and re-opens the port. But I have not been able to duplicate that
behavior on Linux yet. (Then again, I haven't been able to spend that
much time on it).
Oops, what I meant here is that no matter what I do from bitpim/python
(self.comm.close/ser.close(), etc.), the phone will no longer respond to AT
commands, unless I actually disconnect and reconnect the cable.

Loading...