USTRING "encoding" behavior different from STRING's?

Hi,

I was using the "encoding" kwarg for STRING to automatically encode my string 
to utf16_be, however, it seems when the packet is never written with the 
encoding when using USTRING.  STRING has been deprecated in favor of USTRING, 
is the behavior of encoding supposed to change?

I'm in the process of writing support for my Motorola V3c (VZW), and I mostly 
have the OBEX support complete.  The advantage of using OBEX is that I can use 
bitpim using the DUN/serial access over bluetooth rather than only USB. 
However I still haven't figured out how to switch from mode OBEX back to 
MODEM.  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.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642