BitPim and the RAZR V3c - Ubuntu

This is a discussion on BitPim and the RAZR V3c - Ubuntu ; When I first installed and ran the app, I didn't have the RAZR plugged in, so it naturally could not detect the phone. Also I got a message that said "Unauthorized charger" on the V3C display. I restarted the BitPim ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: BitPim and the RAZR V3c

  1. BitPim and the RAZR V3c

    When I first installed and ran the app, I didn't have the RAZR plugged in, so it naturally could not detect the phone. Also I got a message that said "Unauthorized charger" on the V3C display. I restarted the BitPim app and it failed to detect the phone but I was able to get it to recognize manually. But when I tried to access the phone's data, I got the following:

    BitPim version: 1.0.0-Debian
    An unexpected exception has occurred.
    Please see the help for details on what to do.

    Traceback (most recent call last):
      File "/usr/share/bitpim/code/gui.py", line 283, in run
        res=call()
      File "/usr/share/bitpim/code/gui.py", line 158, in __call__
        return apply(self.method, self.args+args, d)
      File "/usr/share/bitpim/code/gui.py", line 1979, in getphoneinfo
        self.setupcomm()
      File "/usr/share/bitpim/code/gui.py", line 1849, in setupcomm
        configparameters=comcfg)
      File "/usr/share/bitpim/code/commport.py", line 68, in __init__
        self._openport(self.port, *self.params)
      File "/usr/share/bitpim/code/commport.py", line 97, in _openport
        self.ser=self._openusb(port, timeout)
      File "/usr/share/bitpim/code/commport.py", line 129, in _openusb
        return _usbdevicewrapper(iface.openbulk(), timeout)
      File "/usr/lib/bitpim/native/usb/usb.py", line 165, in openbulk
        raise USBException()
    USBException: could not claim interface 1: Operation not permitted

    Variables by last 8 frames, innermost last

    Frame run in /usr/share/bitpim/code/gui.py at line 276
           resultcb =  <gui.Callback instance at 0xa8fbe2c>
                res =  None
               self =  <WorkerThread(BitPim helper, started daemon)>
               item =  (<gui.Request instance at 0xa8fbb2c>, <gui.Callback instance at 0xa8fbe2c>)
               call =  <gui.Request instance at 0xa8fbb2c>
                 ex =  USBException('could not claim interface 1: Operation not permitted',)
                  e =  USBException('could not claim interface 1: Operation not permitted',)
              first =  0

    Frame __call__ in /usr/share/bitpim/code/gui.py at line 158
               self =  <gui.Request instance at 0xa8fbb2c>

    Any assistance is gratefully appreciated.

    Fred
               args =  ()
                  d =  Keys []
                       {}
             kwargs =  Keys []
                       {}

    Frame getphoneinfo in /usr/share/bitpim/code/gui.py at line 1979
               self =  <WorkerThread(BitPim helper, started daemon)>

    Frame setupcomm in /usr/share/bitpim/code/gui.py at line 1849
               name =  'usb::003::031::1'
               self =  <WorkerThread(BitPim helper, started daemon)>
           autofunc =  None
             comcfg =  Keys ['baud', 'hardwareflow', 'retryontimeout', 'softwareflow', 'timeout']
                       {'baud': 115200, 'hardwareflow': False, 'softwareflow': False, 'retryontimeout':
              klass =  <class commport.CommConnection at 0x87bf02c>

    Frame __init__ in /usr/share/bitpim/code/commport.py at line 68
               baud =  115200
       autolistargs =  (<module 'phones.com_motov3c' from '/usr/share/bitpim/code/phones/com_motov3c.py
               self =  <commport.CommConnection instance at 0xa8fb82c>
       hardwareflow =  False
       autolistfunc =  None
            timeout =  3
          logtarget =  <WorkerThread(BitPim helper, started daemon)>
    configparameters =  Keys ['baud', 'hardwareflow', 'retryontimeout', 'softwareflow', 'timeout']
                       {'baud': 115200, 'hardwareflow': False, 'softwareflow': False, 'retryontimeout':
       softwareflow =  False
               port =  'usb::003::031::1'

    Frame _openport in /usr/share/bitpim/code/commport.py at line 110
               baud =  115200
              dummy =  0
        description =  None
               self =  <commport.CommConnection instance at 0xa8fb82c>
       hardwareflow =  False
            timeout =  3
       softwareflow =  False
               port =  'usb::003::031::1'

    Frame _openusb in /usr/share/bitpim/code/commport.py at line 129
              iface =  <native.usb.usb.USBInterface instance at 0xb336fcc>
          wantedbus =  '003'
               name =  'usb::003::031::1'
                bus =  <native.usb.usb.USBBus instance at 0xb336b0c>
               self =  <commport.CommConnection instance at 0xa8fb82c>
          wanteddev =  '031'
            timeout =  3
             device =  <native.usb.usb.USBDevice instance at 0xb336a6c>
        wantediface =  1
                  _ =  'usb'

    Frame openbulk in /usr/lib/bitpim/native/usb/usb.py at line 165
                res =  -1
               self =  <native.usb.usb.USBInterface instance at 0xb336fcc>
               epin =  <native.usb.usb.USBEndpoint instance at 0xb336f0c>
                  v =  1
              epout =  <native.usb.usb.USBEndpoint instance at 0xb3294cc>
                 ep =  <native.usb.usb.USBEndpoint instance at 0xb3294cc>


  2. Re: BitPim and the RAZR V3c

    On Thu, 27 Dec 2007 16:45:34 -0800, Fred Marsico wrote:

    > When I first installed and ran the app, I didn't have the RAZR plugged
    > in, so it naturally could not detect the phone. Also I got a message
    > that said "Unauthorized charger" on the V3C display. I restarted the
    > BitPim app and it failed to detect the phone but I was able to get it
    > to recognize manually. But when I tried to access the phone's data, I
    > got the following


    1. Get rid of the HTML in your posts.
    2. Bitpim doesn't work with my V3c.


  3. Re: BitPim and the RAZR V3c

    Apologies for the html, it was default for mail, never checked to see if
    it was also enabled in new. Thanks for the reply, I'' uninstall it and
    look for something else. In the meantime I somehow got the usb to charge
    the phone so I don't have to sacrifice a wall outlet.


    Meat Plow wrote:
    > On Thu, 27 Dec 2007 16:45:34 -0800, Fred Marsico wrote:
    >
    >> When I first installed and ran the app, I didn't have the RAZR plugged
    >> in, so it naturally could not detect the phone. Also I got a message
    >> that said "Unauthorized charger" on the V3C display. I restarted the
    >> BitPim app and it failed to detect the phone but I was able to get it
    >> to recognize manually. But when I tried to access the phone's data, I
    >> got the following

    >
    > 1. Get rid of the HTML in your posts.
    > 2. Bitpim doesn't work with my V3c.
    >


  4. Re: BitPim and the RAZR V3c

    Fred Marsico wrote: ** and top-posted. Fixed **
    > Meat Plow wrote:
    >> Fred Marsico wrote:
    >>
    >>> When I first installed and ran the app, I didn't have the RAZR
    >>> plugged in, so it naturally could not detect the phone. Also I
    >>> got a message that said "Unauthorized charger" on the V3C
    >>> display. I restarted the BitPim app and it failed to detect the
    >>> phone but I was able to get it to recognize manually. But when
    >>> I tried to access the phone's data, I got the following

    >>
    >> 1. Get rid of the HTML in your posts.
    >> 2. Bitpim doesn't work with my V3c.

    >
    > Apologies for the html, it was default for mail, never checked
    > to see if it was also enabled in new. Thanks for the reply, I''
    > uninstall it and look for something else. In the meantime I
    > somehow got the usb to charge the phone so I don't have to
    > sacrifice a wall outlet.


    Also please do not top-post. Your answer belongs after (or
    intermixed with) the quoted material to which you reply, after
    snipping all irrelevant material. I fixed this one. See the
    following links:

    --



    (taming google)
    (newusers)


    --
    Posted via a free Usenet account from http://www.teranews.com


  5. Re: BitPim and the RAZR V3c

    On Thu, 27 Dec 2007 21:11:27 -0800, Fred Marsico wrote:

    > Apologies for the html, it was default for mail, never checked to see if
    > it was also enabled in new. Thanks for the reply, I'' uninstall it and
    > look for something else. In the meantime I somehow got the usb to charge
    > the phone so I don't have to sacrifice a wall outlet.


    I've since tried Wammu and Moto4lin. Neither work with my V3C. As long as
    your kernel recognizes the phone as a USB device it will at least charge.
    You can do a lsusb and see it listed as a Motorola device.
    If you want to play with either app, the phone is /dev/ttyACM0. Moto4lin
    will communicate with the phone initially but disconnects with an error.
    Google didn't help except to show others who couldn't get the V3c to work
    either.



  6. Re: BitPim and the RAZR V3c



    Meat Plow wrote:
    > On Thu, 27 Dec 2007 21:11:27 -0800, Fred Marsico wrote:
    >
    >
    > I've since tried Wammu and Moto4lin. Neither work with my V3C. As long as
    > your kernel recognizes the phone as a USB device it will at least charge.
    > You can do a lsusb and see it listed as a Motorola device.
    > If you want to play with either app, the phone is /dev/ttyACM0. Moto4lin
    > will communicate with the phone initially but disconnects with an error.
    > Google didn't help except to show others who couldn't get the V3c to work
    > either.
    >

    I appreciate all of your assistance. I guess if I stop playing with so many
    different apps I may actually find a way to make what I have work.

  7. Re: BitPim and the RAZR V3c

    On Sat, 29 Dec 2007 13:11:52 -0800, Fred Marsico wrote:

    >
    >
    > Meat Plow wrote:
    >> On Thu, 27 Dec 2007 21:11:27 -0800, Fred Marsico wrote:
    >>
    >>
    >> I've since tried Wammu and Moto4lin. Neither work with my V3C. As long as
    >> your kernel recognizes the phone as a USB device it will at least charge.
    >> You can do a lsusb and see it listed as a Motorola device.
    >> If you want to play with either app, the phone is /dev/ttyACM0. Moto4lin
    >> will communicate with the phone initially but disconnects with an error.
    >> Google didn't help except to show others who couldn't get the V3c to work
    >> either.
    >>

    > I appreciate all of your assistance. I guess if I stop playing with so many
    > different apps I may actually find a way to make what I have work.


    If you do, update me please


+ Reply to Thread