Kristoffer Martin | 10 Nov 09:35 2007
Picon

Re: 1.0.3-20071102-test hanging

It sounds to me that you're using the wrong port configuration. That or you're trying to run this through usb 1.1 which will connect it but doesn't have sufficient connectivity to affectively use. I mean you're timing out the system which means its trying to get a whole host of information at one time and it can't. Imagine trying to run true high speed internet through an old telephone set modem that only does 2 kbps. It just won't work. My suggestion is connect it to a usb 2.0 port set the com port manually to match the USB device and try running the program again.

Other issues in this case is that you could be using a generic usb driver which will look like its connecting might even say its connected, but most likely isn't. (Windows Xp in general and Windows vista any of them have this problem.)

On 11/9/07, Peter <pjcreath+bitpim <at> gmail.com> wrote:
Here's the log:

22:14:19.788 usb::003::002-1004-6000-02-00::2: Opening port
usb::003::002-1004-6000-02-00::2, 115200 baud, timeout 3.000000,
hardwareflow 0, softwareflow 0
22:14:19.788 usb::003::002-1004-6000-02-00::2: Open of comm port succeeded
22:14:19.788 LG-VX6100: Attempting to contact phone
22:14:19.788 LG-VX6100: Getting Phone Info
22:14:19.788 LG-VX6100: Getting file contents 'brew/version.txt'
22:14:19.788 LG-VX6100: sendbrewcommand Data - 2 bytes
<#! phones.p_brew.memoryconfigrequest !#>
00000000 59 0c                                  Y.

22:14:25.800 usb::003::002-1004-6000-02-00::2: Timed out - flushing
and trying again
22:14:31.810 usb::003::002-1004-6000-02-00::2: Timed out waiting for
73, requested bytes -99999  - 0 bytes read
22:14:31.810 usb::003::002-1004-6000-02-00::2: Incomplete read was
Data - 0 bytes

22:14:31.811 LG-VX6100: sendbrewcommand Data - 2 bytes
<#! phones.p_brew.memoryconfigrequest !#>
00000000 59 0c                                  Y.
22:14:37.838 usb::003::002-1004-6000-02-00::2: Timed out - flushing
and trying again

And then it hangs...  Sometimes I can get it to try again and then
fiddle with baud rates, but it takes 6 minutes between each attempt
(and then it hangs after fiddling with the baud rates).

I would have thought it was a general connection problem (of the sort
whose discussion is banned) except the connection is working well
enough to see the USB device and its diagnostic interface.  Browsing
to the port shows:

(*) USB Device - Vendor LG Electroncs, Product VX Series Phone (Direct
USB connection), (Interface Diagnostics Interface):

This port is likely to be your phone. The port is available and can be selected.

PID: 0x6000
VID: 0x1004
active: True
available: True
description: USB Device - Vendor LG Electroncs, Product VX Series
Phone (Direct USB connection), (Interface Diagnostics Interface)
name: usb::003::002-1004-6000-02-00::2
protocol: Vendor Specific Class / Vendor Specific Subclass
usb-productstring: Qualcomm CDMA Technologies MSM

So the cable is functional, the USB system recognizes the device, etc.
It just fails when it tries to communicate.  For reference, 1.0.2
doesn't hang, but it also fails, with the following logs:

22:23:50.642 usb::003::002-1004-6000-02-00::2: Opening port
usb::003::002-1004-6000-02-00::2, 115200 baud, timeout 3.000000,
hardwareflow 0, softwareflow 0
22:23:50.695 usb::003::002-1004-6000-02-00::2: Open of comm port suceeded
22:23:50.695 LG-VX6100: Attempting to contact phone
22:23:50.695 LG-VX6100: Getting Phone Info
22:23:50.695 LG-VX6100: Getting file contents 'brew/version.txt'
22:23:50.695 LG-VX6100: sendbrewcommand Data - 2 bytes
<#! phones.p_brew.memoryconfigrequest !#>
00000000 59 0c                                               Y.

22:23:56.711 usb::003::002-1004-6000-02-00::2: Timed out - flushing
and trying again
22:24: 02.717 usb::003::002-1004-6000-02-00::2: Timed out waiting for
7e, requested bytes -99999  - 0 bytes read
22:24:02.718 usb::003::002-1004-6000-02-00::2: Incomplete read was
Data - 0 bytes

22:24:02.718 usb::003::002-1004-6000-02-00::2: Port speed 38400 not supported
22:24:02.718 usb::003::002-1004-6000-02-00::2: Port speed 115200 not supported
22:24:02.738 usb::003::002-1004-6000-02-00::2: Writing Data - 8 bytes
00000000 41 54 2b 47 4d 4d 0d 0a                             AT+GMM..

22:24:05.798 usb::003::002-1004-6000-02-00::2: Reading remaining data
Data - 0 bytes

22:24:05.799 LG-VX6100: No response to AT+GMM
22:25:36.055 usb::003::002-1004-6000-02-00::2: Writing Data - 10 bytes
00000000 41 54 24 51 43 44 4d 47 0d 0a                       AT$QCDMG..

22:25:36.056 usb::003::002-1004-6000-02-00::2: Write Exception:
usb_bulk_write: An error occured during write (see messages above)

Any ideas?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
Unsubscribe or change options at
https://lists.sourceforge.net/lists/listinfo/bitpim-user

There are several hundred people on this list.  Please be
courteous, on topic and follow the instructions before posting
http://www.bitpim.org/help/support.htm



--
Check out my online forums...
http://s13.invisionfree.com/EyesOnlyForums
And http://flipsidepress.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
Unsubscribe or change options at
https://lists.sourceforge.net/lists/listinfo/bitpim-user

There are several hundred people on this list.  Please be
courteous, on topic and follow the instructions before posting
http://www.bitpim.org/help/support.htm
Peter | 10 Nov 16:53 2007
Picon

Re: 1.0.3-20071102-test hanging

Thank you for the ideas!

I realized after I sent that message that I forgot to provide system
specifics.  This is on a Mac, which only has USB 2.0 ports and doesn't
(as near as I can tell) require any extra drivers.  A few other
details:

1) This is the behavior for ANY request to the phone: no response, no
matter how small the response ought to be.
2) This is a straight USB cable (as can be seen from the USB ID).  And
it is using the built-in USB drivers.  But I haven't seen anything
suggesting that Macs require specific drivers for this case.  (See
<http://www.bitpim.org/help/howto-macusb.htm>; Also libusb, as
mentioned in building for Mac here
<http://www.bitpim.org/developer.html>, is included in the distributed
.dmg.)
3) This same cable and phone and computer worked over a year ago,
using BitPim 0.7.something.

Any other ideas?

On Nov 10, 2007 3:35 AM, Kristoffer Martin <deyesonlya <at> gmail.com> wrote:
> It sounds to me that you're using the wrong port configuration. That or
> you're trying to run this through usb 1.1 which will connect it but doesn't
> have sufficient connectivity to affectively use. I mean you're timing out
> the system which means its trying to get a whole host of information at one
> time and it can't. Imagine trying to run true high speed internet through an
> old telephone set modem that only does 2 kbps. It just won't work. My
> suggestion is connect it to a usb 2.0 port set the com port manually to
> match the USB device and try running the program again.
>
> Other issues in this case is that you could be using a generic usb driver
> which will look like its connecting might even say its connected, but most
> likely isn't. (Windows Xp in general and Windows vista any of them have this
> problem.)
>
>
>
> On 11/9/07, Peter <pjcreath+bitpim <at> gmail.com> wrote:
> >
> >
> >
> > Here's the log:
> >
> > 22:14:19.788 usb::003::002-1004-6000-02-00::2: Opening port
> > usb::003::002-1004-6000-02-00::2, 115200 baud, timeout 3.000000,
> > hardwareflow 0, softwareflow 0
> > 22:14:19.788 usb::003::002-1004-6000-02-00::2: Open of comm port succeeded
> > 22:14:19.788 LG-VX6100: Attempting to contact phone
> > 22:14:19.788 LG-VX6100: Getting Phone Info
> > 22:14:19.788 LG-VX6100: Getting file contents 'brew/version.txt'
> > 22:14:19.788 LG-VX6100: sendbrewcommand Data - 2 bytes
> > <#! phones.p_brew.memoryconfigrequest !#>
> > 00000000 59 0c                                  Y.
> >
> > 22:14:25.800 usb::003::002-1004-6000-02-00::2: Timed out - flushing
> > and trying again
> > 22:14:31.810 usb::003::002-1004-6000-02-00::2: Timed out waiting for
> > 73, requested bytes -99999  - 0 bytes read
> > 22:14:31.810 usb::003::002-1004-6000-02-00::2: Incomplete read was
> > Data - 0 bytes
> >
> > 22:14:31.811 LG-VX6100: sendbrewcommand Data - 2 bytes
> > <#! phones.p_brew.memoryconfigrequest !#>
> > 00000000 59 0c                                  Y.
> > 22:14:37.838 usb::003::002-1004-6000-02-00::2: Timed out - flushing
> > and trying again
> >
> > And then it hangs...  Sometimes I can get it to try again and then
> > fiddle with baud rates, but it takes 6 minutes between each attempt
> > (and then it hangs after fiddling with the baud rates).
> >
> > I would have thought it was a general connection problem (of the sort
> > whose discussion is banned) except the connection is working well
> > enough to see the USB device and its diagnostic interface.  Browsing
> > to the port shows:
> >
> > (*) USB Device - Vendor LG Electroncs, Product VX Series Phone (Direct
> > USB connection), (Interface Diagnostics Interface):
> >
> > This port is likely to be your phone. The port is available and can be
> selected.
> >
> > PID: 0x6000
> > VID: 0x1004
> > active: True
> > available: True
> > description: USB Device - Vendor LG Electroncs, Product VX Series
> > Phone (Direct USB connection), (Interface Diagnostics Interface)
> > name: usb::003::002-1004-6000-02-00::2
> > protocol: Vendor Specific Class / Vendor Specific Subclass
> > usb-productstring: Qualcomm CDMA Technologies MSM
> >
> > So the cable is functional, the USB system recognizes the device, etc.
> > It just fails when it tries to communicate.  For reference, 1.0.2
> > doesn't hang, but it also fails, with the following logs:
> >
> > 22:23:50.642 usb::003::002-1004-6000-02-00::2: Opening port
> > usb::003::002-1004-6000-02-00::2, 115200 baud, timeout 3.000000,
> > hardwareflow 0, softwareflow 0
> > 22:23:50.695 usb::003::002-1004-6000-02-00::2: Open of comm port suceeded
> > 22:23:50.695 LG-VX6100: Attempting to contact phone
> > 22:23:50.695 LG-VX6100: Getting Phone Info
> > 22:23:50.695 LG-VX6100: Getting file contents 'brew/version.txt'
> > 22:23:50.695 LG-VX6100: sendbrewcommand Data - 2 bytes
> > <#! phones.p_brew.memoryconfigrequest !#>
> > 00000000 59 0c                                               Y.
> >
> > 22:23:56.711 usb::003::002-1004-6000-02-00::2: Timed out - flushing
> > and trying again
> > 22:24: 02.717 usb::003::002-1004-6000-02-00::2: Timed out waiting for
> > 7e, requested bytes -99999  - 0 bytes read
> > 22:24:02.718 usb::003::002-1004-6000-02-00::2: Incomplete read was
> > Data - 0 bytes
> >
> > 22:24:02.718 usb::003::002-1004-6000-02-00::2: Port speed 38400 not
> supported
> > 22:24:02.718 usb::003::002-1004-6000-02-00::2: Port speed 115200 not
> supported
> > 22:24:02.738 usb::003::002-1004-6000-02-00::2: Writing Data - 8 bytes
> > 00000000 41 54 2b 47 4d 4d 0d 0a                             AT+GMM..
> >
> > 22:24:05.798 usb::003::002-1004-6000-02-00::2: Reading remaining data
> > Data - 0 bytes
> >
> > 22:24:05.799 LG-VX6100: No response to AT+GMM
> > 22:25:36.055 usb::003::002-1004-6000-02-00::2: Writing Data - 10 bytes
> > 00000000 41 54 24 51 43 44 4d 47 0d 0a                       AT$QCDMG..
> >
> > 22:25:36.056 usb::003::002-1004-6000-02-00::2: Write Exception:
> > usb_bulk_write: An error occured during write (see messages above)
> >
> > Any ideas?
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
> > Unsubscribe or change options at
> > https://lists.sourceforge.net/lists/listinfo/bitpim-user
> >
> > There are several hundred people on this list.  Please be
> > courteous, on topic and follow the instructions before posting
> > http://www.bitpim.org/help/support.htm
> >
>
>
>
> --
> Check out my online forums...
> http://s13.invisionfree.com/EyesOnlyForums
> And http://flipsidepress.org
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
> Unsubscribe or change options at
> https://lists.sourceforge.net/lists/listinfo/bitpim-user
>
> There are several hundred people on this list.  Please be
> courteous, on topic and follow the instructions before posting
> http://www.bitpim.org/help/support.htm
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
Unsubscribe or change options at
https://lists.sourceforge.net/lists/listinfo/bitpim-user

There are several hundred people on this list.  Please be
courteous, on topic and follow the instructions before posting
http://www.bitpim.org/help/support.htm

Peter | 10 Nov 20:57 2007
Picon

Re: 1.0.3-20071102-test hanging

Sorry for the bad etiquette of replying twice, but I think I've solved
it, thanks to your pointers.

The key seems to be at <http://www.bitpim.org/help/lg6000-cables.htm>.
It's not the baud rate that's the problem.  It's that the phone
defaults to assigning the diagnostic port to be serial (UART1) and the
data port to be USB (USB CDC).  (It turns out it's more complicated
than this, but it's apparently specified by the wireless carrier.)

The way current versions of BitPim handle direct USB is to do
everything over direct USB (e.g. usb::id).  I think older versions
were using usbserialXXXX (which modern versions aren't, at least under
Mac OS X 10.4.10 and 10.5).  I don't know whether BitPim can reinstate
this old behavior?

In the interim, the solution is to go into the service menu (as
described in the help page above).  Then change PortMap Diag (2) to
"USB DIAG".  I found that this got reset if I did it before plugging
in the phone.  It also seemed to get reset if I left PortMap Data (1)
set to USB CDC.  So the reliable workaround is:

1) Plug the phone in to the USB cable.
2) Go to the service menu (0, 000000, 5)
3) Change PortMap Data to UART1.
4) Change PortMap Diag to USB DIAG.
5) Exit the service menu.  (Do NOT reboot.  This resets these settings too.)
6) Use BitPim.

I hope this helps others!

Does this serial vs. USB issue sound like a BitPim glitch in its Mac
support?  (Or does USBAppleCDCMDriver.kext simply no longer support LG
phones?)  In any event, how should I report this work-around so that
it makes its way into the help pages?

(And on a separate note, I can't seem to write SMS inbox/outbox or
camera pictures back to the phone.  They just get skipped.  Where
should I report this?)

On Nov 10, 2007 3:35 AM, Kristoffer Martin <deyesonlya <at> gmail.com> wrote:
> Other issues in this case is that you could be using a generic usb driver
> which will look like its connecting might even say its connected, but most
> likely isn't. (Windows Xp in general and Windows vista any of them have this
> problem.)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BitPim-user mailing list BitPim-user <at> lists.sourceforge.net
Unsubscribe or change options at
https://lists.sourceforge.net/lists/listinfo/bitpim-user

There are several hundred people on this list.  Please be
courteous, on topic and follow the instructions before posting
http://www.bitpim.org/help/support.htm


Gmane