Re: [Barry-devel] Using pppob with a brazilian provider (TIM)
This is my chatscript, don't know anything about your provider but if its a GSM based one you need the APN, eg vfinternet.au, you may also need a different phone "number", vodafone in Australia uses: ATD*99***1# ABORT ERROR '' AT&F OK ATZ OK ATI OK AT+CNUM OK AT+CSQ OK AT+CREG? OK AT+CGDCONT? OK AT+CGQREQ? OK AT+CGQMIN? OK AT+CGATT? OK AT+CGREG? OK AT+CGDCONT=1,"IP","vfinternet.au" OK ATD*99***1# CONNECT -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Using pppob with a brazilian provider (TIM)
Hah! I got it working last nite. It seems that my 8300 doesn't like the AT+CGDCONT=1 command UNTIL I send it a AT+CFUN=1, so my chatscript is now: ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR SAY "Initializing\n" '' ATZ OK-AT-OK AT+CFUN=1 OK-AT-OK AT+CGDCONT=1,"ip","tim.br" OK-AT-OK ATDT*99***1# CONNECT \d\c AND IT WORKS! The only bummer is, after a few minutes surfing teh internets my blackberry reboots (O_O). I guess it has something to do with the firmware that I need to upgrade. :/ Hey, Delta, by any chance do you know if there's a reference on the AT command set that the blackberry accepts ? (I see you have a lot of AT commands issued before dialing). Cheers, On Wed, Jan 7, 2009 at 7:09 AM, Delta Foxtrot wrote: > This is my chatscript, don't know anything about your provider but if its a > GSM > based one you need the APN, eg vfinternet.au, you may also need a different > phone "number", vodafone in Australia uses: ATD*99***1# > > ABORT ERROR > '' AT&F > OK ATZ > OK ATI > OK AT+CNUM > OK AT+CSQ > OK AT+CREG? > OK AT+CGDCONT? > OK AT+CGQREQ? > OK AT+CGQMIN? > OK AT+CGATT? > OK AT+CGREG? > OK AT+CGDCONT=1,"IP","vfinternet.au" > OK ATD*99***1# > CONNECT > > > > > > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel > -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] [Bulk] Re: Using pppob with a brazilian provider (TIM)
AT+CLAC will list all of the commands On Wed, 2009-01-07 at 09:30 -0200, Pablo Borges wrote: > Hah! I got it working last nite. It seems that my 8300 doesn't like > the AT+CGDCONT=1 command UNTIL I send it a AT+CFUN=1, so my chatscript > is now: > > ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT > 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED ABORT ERROR > SAY "Initializing\n" > '' ATZ > OK-AT-OK AT+CFUN=1 > OK-AT-OK AT+CGDCONT=1,"ip","tim.br" > OK-AT-OK ATDT*99***1# > CONNECT \d\c > > AND IT WORKS! > > The only bummer is, after a few minutes surfing teh internets my > blackberry reboots (O_O). I guess it has something to do with the > firmware that I need to upgrade. :/ > > Hey, Delta, by any chance do you know if there's a reference on the AT > command set that the blackberry accepts ? (I see you have a lot of AT > commands issued before dialing). > > Cheers, > > On Wed, Jan 7, 2009 at 7:09 AM, Delta Foxtrot > wrote: > This is my chatscript, don't know anything about your provider > but if its a GSM > based one you need the APN, eg vfinternet.au, you may also > need a different > phone "number", vodafone in Australia uses: ATD*99***1# > > ABORT ERROR > '' AT&F > OK ATZ > OK ATI > OK AT+CNUM > OK AT+CSQ > OK AT+CREG? > OK AT+CGDCONT? > OK AT+CGQREQ? > OK AT+CGQMIN? > OK AT+CGATT? > OK AT+CGREG? > OK AT+CGDCONT=1,"IP","vfinternet.au" > OK ATD*99***1# > CONNECT > > > > > > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] Errors communicating with modem
Any ideas on my errors below communicating with modem? Looks like it charges and I can do a reset but when I attempt to do pppob I get errors. System is Debian with following installed. dpkg -l|grep barry ii barry-util 0.14-2 Command line utilities for working with the RIM BlackBerry Handh ii barrybackup-gui 0.14-2 GTK+ based GUI for backing up the RIM BlackBerry Handheld ii libbarry0 0.14-2 Library for using the BlackBerry handheld on Linux == Charging == bcharge Scanning for Blackberry devices... Found device #008...already at 500mA...already in desired Pearl mode...no change == Reset == btool -X Blackberry devices found: Device ID: 0x84d5a08. PIN: 31800f4d, Description: RIM 8800 Series Colour CDMA Handheld Using device (PIN): 31800f4d = Test = pppob -p ## Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 : 00 00 1a 00 09 ff 00 07 52 49 4d 5f 55 73 62 53 RIM_UsbS 0010: 65 72 44 61 74 61 00 00 02 00 erData exception caught in main(): Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 = Verbose Test = pppob -p ## -v usb_set_debug: Setting debugging level to 9 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 002 usb_os_find_busses: Found 003 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 001 on 006 usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 002 on 004 usb_os_find_devices: Found 001 on 004 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 010 on 003 usb_os_find_devices: Found 006 on 003 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 005 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 003 usb_os_find_devices: Found 003 on 003 usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 002 usb_os_find_busses: Found 003 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 007 usb_os_find_devices: Found 001 on 006 usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 002 on 004 usb_os_find_devices: Found 001 on 004 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 010 on 003 usb_os_find_devices: Found 006 on 003 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 005 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 003 usb_os_find_devices: Found 003 on 003 usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 002 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device device_desc loaded bLength: 18 bDescriptorType: 1 bcdUSB: 272 bDeviceClass: 0 bDeviceSubClass: 0 bDeviceProtocol: 0 bMaxPacketSize0: 64 idVendor: 4042 idProduct: 4 bcdDevice: 262 iManufacturer: 1 iProduct: 5 iSerialNumber: 3 bNumConfigurations: 1 config_desc #0 loaded bLength: 9 bDescriptorType: 2 wTotalLength: 97 bNumInterfaces: 2 bConfigurationValue: 1 iConfiguration: 0 bmAttributes: 128 MaxPower: 250 interface_desc #0 loaded bLength: 9 bDescriptorType: 4 bInterfaceNumber: 0 bAlternateSetting: 0 bNumEndpoints: 8 bInterfaceClass: 255 bInterfaceSubClass: 1 bInterfaceProtocol: 255 iInterface: 2 endpoint_desc #0 loaded bLength: 7 bDescriptorType: 5 bEndpointAddress: 133 bmAttributes: 2 wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 endpoint added to map with bEndpointAddress: 133 pair.read = 133 pair.type = 2 endpoint_desc #1 loaded bLength: 7 bDescriptorType: 5 bEndpointAddress: 5 bmAttributes: 2 wMaxPacketSize: 64 bInterval: 0 bRefresh: 0 bSynchAddress: 0 endpoint added t
[Barry-devel] Questions about barry
I installed barry this morning on ubuntu 8.04 with out a hitch with my curve 8330, the backup utility works like a charm and so did accessing the internet, that is until i shut down the pc and rebooted. I can get a connection with the phone at least according to the scipt in the terminal window, gives me IP address and such but will not transfer data. The phone says it is in modem mode, but there is no little arrows blinking or anything. Does anyone have any suggestions? Thanks Greg -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Errors communicating with modem
Mallory, Danny wrote: > Any ideas on my errors below communicating with modem? Looks like it > charges and I can do a reset but when I attempt to do pppob I get > errors. System is Debian with following installed. > > dpkg -l|grep barry > ii barry-util0.14-2 Command line utilities for working with > the RIM BlackBerry Handh > ii barrybackup-gui 0.14-2 GTK+ based GUI for backing up the RIM > BlackBerry Handheld > ii libbarry0 0.14-2 Library for using the BlackBerry > handheld on Linux > > > == > Charging > == > bcharge > Scanning for Blackberry devices... > Found device #008...already at 500mA...already in desired Pearl > mode...no change > > > == > Reset > == > btool -X > Blackberry devices found: > Device ID: 0x84d5a08. PIN: 31800f4d, Description: RIM 8800 Series Colour > CDMA Handheld > Using device (PIN): 31800f4d > > = > Test > = > pppob -p ## > Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 > : 00 00 1a 00 09 ff 00 07 52 49 4d 5f 55 73 62 53 > RIM_UsbS > 0010: 65 72 44 61 74 61 00 00 02 00 > erData > > exception caught in main(): Bad packet size. Packet: 26. DataSize(): 26. > Required size: 44 > > > = > Verbose Test > = > pppob -p ## -v > usb_set_debug: Setting debugging level to 9 (on) > usb_os_init: Found USB VFS at /dev/bus/usb > usb_os_find_busses: Found 007 > usb_os_find_busses: Found 006 > usb_os_find_busses: Found 005 > usb_os_find_busses: Found 004 > usb_os_find_busses: Found 002 > usb_os_find_busses: Found 003 > usb_os_find_busses: Found 001 > usb_os_find_devices: Found 001 on 007 > usb_os_find_devices: Found 001 on 006 > usb_os_find_devices: Found 001 on 005 > usb_os_find_devices: Found 002 on 004 > usb_os_find_devices: Found 001 on 004 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 001 on 002 > usb_os_find_devices: Found 010 on 003 > usb_os_find_devices: Found 006 on 003 > skipped 1 class/vendor specific interface descriptors > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 005 on 003 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 004 on 003 > usb_os_find_devices: Found 003 on 003 > usb_os_find_devices: Found 001 on 003 > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 002 on 001 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 001 on 001 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_busses: Found 007 > usb_os_find_busses: Found 006 > usb_os_find_busses: Found 005 > usb_os_find_busses: Found 004 > usb_os_find_busses: Found 002 > usb_os_find_busses: Found 003 > usb_os_find_busses: Found 001 > usb_os_find_devices: Found 001 on 007 > usb_os_find_devices: Found 001 on 006 > usb_os_find_devices: Found 001 on 005 > usb_os_find_devices: Found 002 on 004 > usb_os_find_devices: Found 001 on 004 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 001 on 002 > usb_os_find_devices: Found 010 on 003 > usb_os_find_devices: Found 006 on 003 > skipped 1 class/vendor specific interface descriptors > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 005 on 003 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 004 on 003 > usb_os_find_devices: Found 003 on 003 > usb_os_find_devices: Found 001 on 003 > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 002 on 001 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 001 on 001 > error obtaining child information: Inappropriate ioctl for device > device_desc loaded > bLength: 18 > bDescriptorType: 1 > bcdUSB: 272 > bDeviceClass: 0 > bDeviceSubClass: 0 > bDeviceProtocol: 0 > bMaxPacketSize0: 64 > idVendor: 4042 > idProduct: 4 > bcdDevice: 262 > iManufacturer: 1 > iProduct: 5 > iSerialNumber: 3 > bNumConfigurations: 1 > > config_desc #0 loaded > bLength: 9 > bDescriptorType: 2 > wTotalLength: 97 > bNumInterfaces: 2 > bConfigurationValue: 1 > iConfiguration: 0 > bmAttributes: 128 > MaxPower: 250 > > interface_desc #0 loaded > bLength: 9 > bDescriptorType: 4 > bInterfaceNumber: 0 > bAlternateSetting: 0 > bNumEndpoints: 8 > bInterfaceClass: 255 > bInterfaceSubClass: 1 > bInterfaceProtocol: 255 > iInterface: 2 > > endpoint_desc #0 loaded > bLength: 7 > bDescriptorType: 5 > bEndpointAddress: 133 > bmAttributes: 2 > wMaxPacketS
Re: [Barry-devel] Questions about barry
On Wed, 2009-01-07 at 11:32 -0500, Greg Foster wrote: > I installed barry this morning on ubuntu 8.04 with out a hitch with my > curve 8330, the backup utility works like a charm and so did accessing > the internet, that is until i shut down the pc and rebooted. I can get > a connection with the phone at least according to the scipt in the > terminal window, gives me IP address and such but will not transfer > data. The phone says it is in modem mode, but there is no little > arrows blinking or anything. Does anyone have any suggestions? Check that usb_storage isn't loaded and interfering, that's caught me out before. Also check you actually have a route setup via the Blackberry interface, I guess networkmanager could be interfering, it likes to do that... -- adamw http://www.happyassassin.net -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Errors communicating with modem
Just fixed my problem. After grepping through I found a few different versions of libbarry as well as pppob in /usr/local/lib and /usr/local/sbin from previous installs of barry. After purging packages, manually removing the stale libraries/binary then reinstalled, All good now. Danny -Original Message- From: Shannon McMackin [mailto:smcmac...@gmail.com] Sent: Wednesday, January 07, 2009 11:10 AM To: barry-devel@lists.sourceforge.net Subject: Re: [Barry-devel] Errors communicating with modem Mallory, Danny wrote: > Any ideas on my errors below communicating with modem? Looks like it > charges and I can do a reset but when I attempt to do pppob I get > errors. System is Debian with following installed. > > dpkg -l|grep barry > ii barry-util0.14-2 Command line utilities for working with > the RIM BlackBerry Handh > ii barrybackup-gui 0.14-2 GTK+ based GUI for backing up the RIM > BlackBerry Handheld > ii libbarry0 0.14-2 Library for using the BlackBerry > handheld on Linux > > > == > Charging > == > bcharge > Scanning for Blackberry devices... > Found device #008...already at 500mA...already in desired Pearl > mode...no change > > > == > Reset > == > btool -X > Blackberry devices found: > Device ID: 0x84d5a08. PIN: 31800f4d, Description: RIM 8800 Series > Colour CDMA Handheld Using device (PIN): 31800f4d > > = > Test > = > pppob -p ## > Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 > : 00 00 1a 00 09 ff 00 07 52 49 4d 5f 55 73 62 53 > RIM_UsbS > 0010: 65 72 44 61 74 61 00 00 02 00 erData > > exception caught in main(): Bad packet size. Packet: 26. DataSize(): 26. > Required size: 44 > > > = > Verbose Test > = > pppob -p ## -v > usb_set_debug: Setting debugging level to 9 (on) > usb_os_init: Found USB VFS at /dev/bus/usb > usb_os_find_busses: Found 007 > usb_os_find_busses: Found 006 > usb_os_find_busses: Found 005 > usb_os_find_busses: Found 004 > usb_os_find_busses: Found 002 > usb_os_find_busses: Found 003 > usb_os_find_busses: Found 001 > usb_os_find_devices: Found 001 on 007 > usb_os_find_devices: Found 001 on 006 > usb_os_find_devices: Found 001 on 005 > usb_os_find_devices: Found 002 on 004 > usb_os_find_devices: Found 001 on 004 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 001 on 002 > usb_os_find_devices: Found 010 on 003 > usb_os_find_devices: Found 006 on 003 > skipped 1 class/vendor specific interface descriptors skipped 1 > class/vendor specific interface descriptors > usb_os_find_devices: Found 005 on 003 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 004 on 003 > usb_os_find_devices: Found 003 on 003 > usb_os_find_devices: Found 001 on 003 > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 002 on 001 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 001 on 001 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_busses: Found 007 > usb_os_find_busses: Found 006 > usb_os_find_busses: Found 005 > usb_os_find_busses: Found 004 > usb_os_find_busses: Found 002 > usb_os_find_busses: Found 003 > usb_os_find_busses: Found 001 > usb_os_find_devices: Found 001 on 007 > usb_os_find_devices: Found 001 on 006 > usb_os_find_devices: Found 001 on 005 > usb_os_find_devices: Found 002 on 004 > usb_os_find_devices: Found 001 on 004 > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 001 on 002 > usb_os_find_devices: Found 010 on 003 > usb_os_find_devices: Found 006 on 003 > skipped 1 class/vendor specific interface descriptors skipped 1 > class/vendor specific interface descriptors > usb_os_find_devices: Found 005 on 003 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 004 on 003 > usb_os_find_devices: Found 003 on 003 > usb_os_find_devices: Found 001 on 003 > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > error obtaining child information: Inappropriate ioctl for device > usb_os_find_devices: Found 002 on 001 > skipped 1 class/vendor specific interface descriptors > usb_os_find_devices: Found 001 on 001 > error obtaining child information: Inappropriate ioctl for device > device_desc loaded > bLength: 18 > bDescriptorType: 1 > bcdUSB: 272 > bDeviceClass: 0 > bDeviceSubClass: 0 > bDeviceProtocol: 0 > bMaxPacketSize0: 64 > idVendor: 4042 > idProduct: 4 > bcdDevice: 262 > iManufacturer: 1 > iProduct: 5 > iSerialNumber: 3 > bNumConfigurations: 1 > > con
Re: [Barry-devel] Errors communicating with modem
Mallory, Danny wrote: > Just fixed my problem. > > After grepping through I found a few different versions of libbarry as > well as pppob in /usr/local/lib and /usr/local/sbin from previous > installs of barry. After purging packages, manually removing the stale > libraries/binary then reinstalled, All good now. > > Danny > > -Original Message- > From: Shannon McMackin [mailto:smcmac...@gmail.com] > Sent: Wednesday, January 07, 2009 11:10 AM > To: barry-devel@lists.sourceforge.net > Subject: Re: [Barry-devel] Errors communicating with modem > > Mallory, Danny wrote: >> Any ideas on my errors below communicating with modem? Looks like it >> charges and I can do a reset but when I attempt to do pppob I get >> errors. System is Debian with following installed. >> >> dpkg -l|grep barry >> ii barry-util 0.14-2 Command line utilities for > working with >> the RIM BlackBerry Handh >> ii barrybackup-gui 0.14-2 GTK+ based GUI for backing up the RIM >> BlackBerry Handheld >> ii libbarry00.14-2 Library for using the BlackBerry >> handheld on Linux >> >> >> == >> Charging >> == >> bcharge >> Scanning for Blackberry devices... >> Found device #008...already at 500mA...already in desired Pearl >> mode...no change >> >> >> == >> Reset >> == >> btool -X >> Blackberry devices found: >> Device ID: 0x84d5a08. PIN: 31800f4d, Description: RIM 8800 Series >> Colour CDMA Handheld Using device (PIN): 31800f4d >> >> = >> Test >> = >> pppob -p ## >> Bad packet size. Packet: 26. DataSize(): 26. Required size: 44 >> : 00 00 1a 00 09 ff 00 07 52 49 4d 5f 55 73 62 53 >> RIM_UsbS >> 0010: 65 72 44 61 74 61 00 00 02 00 erData >> >> exception caught in main(): Bad packet size. Packet: 26. DataSize(): > 26. >> Required size: 44 >> >> >> = >> Verbose Test >> = >> pppob -p ## -v >> usb_set_debug: Setting debugging level to 9 (on) >> usb_os_init: Found USB VFS at /dev/bus/usb >> usb_os_find_busses: Found 007 >> usb_os_find_busses: Found 006 >> usb_os_find_busses: Found 005 >> usb_os_find_busses: Found 004 >> usb_os_find_busses: Found 002 >> usb_os_find_busses: Found 003 >> usb_os_find_busses: Found 001 >> usb_os_find_devices: Found 001 on 007 >> usb_os_find_devices: Found 001 on 006 >> usb_os_find_devices: Found 001 on 005 >> usb_os_find_devices: Found 002 on 004 >> usb_os_find_devices: Found 001 on 004 >> error obtaining child information: Inappropriate ioctl for device >> usb_os_find_devices: Found 001 on 002 >> usb_os_find_devices: Found 010 on 003 >> usb_os_find_devices: Found 006 on 003 >> skipped 1 class/vendor specific interface descriptors skipped 1 >> class/vendor specific interface descriptors >> usb_os_find_devices: Found 005 on 003 >> skipped 1 class/vendor specific interface descriptors >> usb_os_find_devices: Found 004 on 003 >> usb_os_find_devices: Found 003 on 003 >> usb_os_find_devices: Found 001 on 003 >> error obtaining child information: Inappropriate ioctl for device >> error obtaining child information: Inappropriate ioctl for device >> error obtaining child information: Inappropriate ioctl for device >> usb_os_find_devices: Found 002 on 001 >> skipped 1 class/vendor specific interface descriptors >> usb_os_find_devices: Found 001 on 001 >> error obtaining child information: Inappropriate ioctl for device >> usb_os_find_busses: Found 007 >> usb_os_find_busses: Found 006 >> usb_os_find_busses: Found 005 >> usb_os_find_busses: Found 004 >> usb_os_find_busses: Found 002 >> usb_os_find_busses: Found 003 >> usb_os_find_busses: Found 001 >> usb_os_find_devices: Found 001 on 007 >> usb_os_find_devices: Found 001 on 006 >> usb_os_find_devices: Found 001 on 005 >> usb_os_find_devices: Found 002 on 004 >> usb_os_find_devices: Found 001 on 004 >> error obtaining child information: Inappropriate ioctl for device >> usb_os_find_devices: Found 001 on 002 >> usb_os_find_devices: Found 010 on 003 >> usb_os_find_devices: Found 006 on 003 >> skipped 1 class/vendor specific interface descriptors skipped 1 >> class/vendor specific interface descriptors >> usb_os_find_devices: Found 005 on 003 >> skipped 1 class/vendor specific interface descriptors >> usb_os_find_devices: Found 004 on 003 >> usb_os_find_devices: Found 003 on 003 >> usb_os_find_devices: Found 001 on 003 >> error obtaining child information: Inappropriate ioctl for device >> error obtaining child information: Inappropriate ioctl for device >> error obtaining child information: Inappropriate ioctl for device >> usb_os_find_devices: Found 002 on 001 >> skipped 1 class/vendor specific interface descriptors >> usb_os_find_devices: Found 001 on 001 >> error obtaining child information: Inappropriate ioctl for device >> device_desc loaded >> bLength: 18 >> bDescriptorType: 1 >> bcdUSB: 272 >> bDeviceClass: 0 >> bDeviceSubClass: 0 >> bDevic
Re: [Barry-devel] Questions about barry
Greg Foster wrote: > I installed barry this morning on ubuntu 8.04 with out a hitch with my > curve 8330, the backup utility works like a charm and so did accessing > the internet, that is until i shut down the pc and rebooted. I can get a > connection with the phone at least according to the scipt in the > terminal window, gives me IP address and such but will not transfer > data. The phone says it is in modem mode, but there is no little arrows > blinking or anything. Does anyone have any suggestions? > Thanks > Greg > > > > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > > > > > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel I always make sure to turn off networking through NM. That tool is great for wi-fi, but not friendly for ppp. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Blackberries rebooting during tethering (was Re: Using pppob with a brazilian provider (TIM))
I notice a few weeks ago that my 8830 was crashing when I started up barry. I think it was actually the phone as all the components involved were the same (software, versions, hardware, etc), but the phone was having other issues not related to barry or tethering. It's since been replaced by a new unit, but I haven't had a reason to use Barry at all since then. Yeah, not much of a bug report, I know, just thought I throw in my $0.01 worth. BTW, it worked perfectly on a Sprint 8830 World Edition (CDMA & GSM) phone in Europe for about a month Chris. Adam Williamson wrote: > On Wed, 2009-01-07 at 09:30 -0200, Pablo Borges wrote: > > >> The only bummer is, after a few minutes surfing teh internets my >> blackberry reboots (O_O). I guess it has something to do with the >> firmware that I need to upgrade. :/ >> > > Someone reported something similar to me on my blog the other day: > > "Barry does show great potential, but has a show-stopping bug for me. > See my report on SF: Bug # 2480631…" > > http://www.happyassassin.net/2009/01/04/activity-and-blackberry-tethering-article/ > > and ISTR it's been reported to the list, too. This seems to be a general > bug...and at least for your case and the blog case, the offending model > is a Curve... > > The bug report referred to in the comment is: > > http://sourceforge.net/tracker/index.php?func=detail&aid=2480631&group_id=153722&atid=788904 > -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Blackberries rebooting during tethering (was Re: Using pppob with a brazilian provider (TIM))
I see the exact same behavior on my 8310 (AT&T Curve) using Ubunt 8.04 and pre 0.14 CVS packages. I haven't tried with the latest CVS. I haven't taken the time to play with things since it works good enough (tethering to EDGE is an emergency only situation--painfully slow). Besides my platform and version, I don't have any information to add that isn't in the bug report. However, if specific info will help I can try and provide it. Richard Esplin On Wednesday 07 January 2009 11:39:13 Adam Williamson wrote: > On Wed, 2009-01-07 at 09:30 -0200, Pablo Borges wrote: > > The only bummer is, after a few minutes surfing teh internets my > > blackberry reboots (O_O). I guess it has something to do with the > > firmware that I need to upgrade. :/ > > Someone reported something similar to me on my blog the other day: > > "Barry does show great potential, but has a show-stopping bug for me. > See my report on SF: Bug # 2480631…" > > http://www.happyassassin.net/2009/01/04/activity-and-blackberry-tethering-a >rticle/ > > and ISTR it's been reported to the list, too. This seems to be a general > bug...and at least for your case and the blog case, the offending model > is a Curve... > > The bug report referred to in the comment is: > > http://sourceforge.net/tracker/index.php?func=detail&aid=2480631&group_id=1 >53722&atid=788904 -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] Blackberries rebooting during tethering (was Re: Using pppob with a brazilian provider (TIM))
On Wed, 2009-01-07 at 09:30 -0200, Pablo Borges wrote: > The only bummer is, after a few minutes surfing teh internets my > blackberry reboots (O_O). I guess it has something to do with the > firmware that I need to upgrade. :/ Someone reported something similar to me on my blog the other day: "Barry does show great potential, but has a show-stopping bug for me. See my report on SF: Bug # 2480631…" http://www.happyassassin.net/2009/01/04/activity-and-blackberry-tethering-article/ and ISTR it's been reported to the list, too. This seems to be a general bug...and at least for your case and the blog case, the offending model is a Curve... The bug report referred to in the comment is: http://sourceforge.net/tracker/index.php?func=detail&aid=2480631&group_id=153722&atid=788904 -- adamw http://www.happyassassin.net -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] JDE, JavaLoader on Linux (alpha patch)
Hi, Before a clean patch with GIT and good integrated in barry project, you can try this : With this patch, I can load a Java application on my BlackBerry Storm. Test with severals applications (format COD files). Idea to improve the patch : - parse an ".alx" file to load an application - give an URL http:///app.alx to download application - get the list applications installed on the device - remove application - your suggestions ? (about patch or improvement) Regards, -- Nicolas VIVIEN barry-javaloader.tar.gz Description: application/compressed-tar -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] Questions about barry
Sorry I keep sending from the wrong email address I turned off the networking manager and it seemed to work fine. Also what is the proper way to quit the ppod script? I have been using ctrl-z to do it. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
[Barry-devel] File transfer to/from BlackBerry device memory
I found the Barry project in my quest to get file transfer to/from BlackBerry device memory working without using Roxio Media Manager. >From what I have read about Barry and the parts of the source I have looked at, it appears that Barry does not support this. From searching the web and RIM's site, there does not appear to be any lightweight program to do this and I'm not going to waste my time trying to contact RIM to ask them to write one since others have not found them very responsive. Sniffing the USB communication reveals that there is some initialization after which simple commands like GET and PUT and LIST are used to do transfers. I'm not much of a programmer and would like to see if anyone has or could write a utility that I could use to send packets to endpoint 0x4 or 0x3 (depending on BB model) and read from endpoint 0x83. I could then continue investigating and documenting the protocol. I've also been unable to get Barry to compile on my Debian system... Something about "no matching function for call to..." when compiling base64.cc. Thanks. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
Hi Robert, Linux should be able to access your bb as a USB Mass Storage device. Below is the output from my kernel when I connect my bb, on Debian sid. [1909612.689528] usb 2-1: new full speed USB device using uhci_hcd and address 10 [1909612.877830] usb 2-1: configuration #1 chosen from 1 choice [1909612.890095] scsi13 : SCSI emulation for USB Mass Storage devices [1909612.893632] usb-storage: device found at 10 [1909612.893635] usb-storage: waiting for device to settle before scanning [1909612.890095] usb 2-1: New USB device found, idVendor=0fca, idProduct=0004 [1909612.890095] usb 2-1: New USB device strings: Mfr=1, Product=5, SerialNumber=3 [1909612.890095] usb 2-1: Product: RIM Composite Device [1909612.890095] usb 2-1: Manufacturer: Research In Motion [1909612.890095] usb 2-1: SerialNumber: FE216BF928723656BAAF354554BE01110D6407F3 [1909618.163710] usb-storage: device scan complete [1909618.297134] scsi 13:0:0:0: Direct-Access RIM Blackberry SD 0001 PQ: 0 ANSI: 4 CCS [1909618.310404] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors (8169 MB) [1909618.311991] sd 13:0:0:0: [sdb] Write Protect is off [1909618.312000] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 [1909618.312004] sd 13:0:0:0: [sdb] Assuming drive cache: write through [1909618.324510] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors (8169 MB) [1909618.328093] sd 13:0:0:0: [sdb] Write Protect is off [1909618.328102] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 [1909618.328107] sd 13:0:0:0: [sdb] Assuming drive cache: write through [1909618.328113] sdb: sdb1 [1909618.336159] sd 13:0:0:0: [sdb] Attached SCSI removable disk [1909618.336159] sd 13:0:0:0: Attached scsi generic sg2 type 0 On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: > I found the Barry project in my quest to get file transfer to/from > BlackBerry device memory working without using Roxio Media Manager. > >From what I have read about Barry and the parts of the source I have > looked at, it appears that Barry does not support this. From searching > the web and RIM's site, there does not appear to be any lightweight > program to do this and I'm not going to waste my time trying to > contact RIM to ask them to write one since others have not found them > very responsive. > > Sniffing the USB communication reveals that there is some > initialization after which simple commands like GET and PUT and LIST > are used to do transfers. > > I'm not much of a programmer and would like to see if anyone has or > could write a utility that I could use to send packets to endpoint 0x4 > or 0x3 (depending on BB model) and read from endpoint 0x83. I could > then continue investigating and documenting the protocol. > > I've also been unable to get Barry to compile on my Debian system... > Something about "no matching function for call to..." when compiling > base64.cc. > > Thanks. > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel -- Jason Thomas -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
Mass storage only works for devices with an SD card, and then ONLY to transfer to/from the SD card. I've got older 7xxx and 8xxx series devices that do not have a memory card slot. On 1/7/09, Jason Thomas wrote: > Hi Robert, > > Linux should be able to access your bb as a USB Mass Storage device. > Below is the output from my kernel when I connect my bb, on Debian sid. > > > [1909612.689528] usb 2-1: new full speed USB device using uhci_hcd and > address 10 > [1909612.877830] usb 2-1: configuration #1 chosen from 1 choice > [1909612.890095] scsi13 : SCSI emulation for USB Mass Storage devices > [1909612.893632] usb-storage: device found at 10 > [1909612.893635] usb-storage: waiting for device to settle before > scanning > [1909612.890095] usb 2-1: New USB device found, idVendor=0fca, > idProduct=0004 > [1909612.890095] usb 2-1: New USB device strings: Mfr=1, Product=5, > SerialNumber=3 > [1909612.890095] usb 2-1: Product: RIM Composite Device > [1909612.890095] usb 2-1: Manufacturer: Research In Motion > [1909612.890095] usb 2-1: SerialNumber: > FE216BF928723656BAAF354554BE01110D6407F3 > [1909618.163710] usb-storage: device scan complete > [1909618.297134] scsi 13:0:0:0: Direct-Access RIM Blackberry SD > 0001 PQ: 0 ANSI: 4 CCS > [1909618.310404] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors > (8169 MB) > [1909618.311991] sd 13:0:0:0: [sdb] Write Protect is off > [1909618.312000] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 > [1909618.312004] sd 13:0:0:0: [sdb] Assuming drive cache: write through > [1909618.324510] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors > (8169 MB) > [1909618.328093] sd 13:0:0:0: [sdb] Write Protect is off > [1909618.328102] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 > [1909618.328107] sd 13:0:0:0: [sdb] Assuming drive cache: write through > [1909618.328113] sdb: sdb1 > [1909618.336159] sd 13:0:0:0: [sdb] Attached SCSI removable disk > [1909618.336159] sd 13:0:0:0: Attached scsi generic sg2 type 0 > > > On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: >> I found the Barry project in my quest to get file transfer to/from >> BlackBerry device memory working without using Roxio Media Manager. >> >From what I have read about Barry and the parts of the source I have >> looked at, it appears that Barry does not support this. From searching >> the web and RIM's site, there does not appear to be any lightweight >> program to do this and I'm not going to waste my time trying to >> contact RIM to ask them to write one since others have not found them >> very responsive. >> >> Sniffing the USB communication reveals that there is some >> initialization after which simple commands like GET and PUT and LIST >> are used to do transfers. >> >> I'm not much of a programmer and would like to see if anyone has or >> could write a utility that I could use to send packets to endpoint 0x4 >> or 0x3 (depending on BB model) and read from endpoint 0x83. I could >> then continue investigating and documenting the protocol. >> >> I've also been unable to get Barry to compile on my Debian system... >> Something about "no matching function for call to..." when compiling >> base64.cc. >> >> Thanks. >> >> -- >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> ___ >> Barry-devel mailing list >> Barry-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/barry-devel > -- > Jason Thomas > > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel > -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
I have also sniffed the communication when attempting to use BlackBerry Media Sync which does not support my devices but does send a LIST command...probably to get the filesystem size. I suspect that Media Sync may work with devices with 1GB or more of on-board device memory, but I don't have one and have not downloaded the emulator yet. On 1/7/09, Robert Yaklin wrote: > Mass storage only works for devices with an SD card, and then ONLY to > transfer to/from the SD card. I've got older 7xxx and 8xxx series > devices that do not have a memory card slot. > > On 1/7/09, Jason Thomas wrote: >> Hi Robert, >> >> Linux should be able to access your bb as a USB Mass Storage device. >> Below is the output from my kernel when I connect my bb, on Debian sid. >> >> >> [1909612.689528] usb 2-1: new full speed USB device using uhci_hcd and >> address 10 >> [1909612.877830] usb 2-1: configuration #1 chosen from 1 choice >> [1909612.890095] scsi13 : SCSI emulation for USB Mass Storage devices >> [1909612.893632] usb-storage: device found at 10 >> [1909612.893635] usb-storage: waiting for device to settle before >> scanning >> [1909612.890095] usb 2-1: New USB device found, idVendor=0fca, >> idProduct=0004 >> [1909612.890095] usb 2-1: New USB device strings: Mfr=1, Product=5, >> SerialNumber=3 >> [1909612.890095] usb 2-1: Product: RIM Composite Device >> [1909612.890095] usb 2-1: Manufacturer: Research In Motion >> [1909612.890095] usb 2-1: SerialNumber: >> FE216BF928723656BAAF354554BE01110D6407F3 >> [1909618.163710] usb-storage: device scan complete >> [1909618.297134] scsi 13:0:0:0: Direct-Access RIM Blackberry SD >> 0001 PQ: 0 ANSI: 4 CCS >> [1909618.310404] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors >> (8169 MB) >> [1909618.311991] sd 13:0:0:0: [sdb] Write Protect is off >> [1909618.312000] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 >> [1909618.312004] sd 13:0:0:0: [sdb] Assuming drive cache: write through >> [1909618.324510] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors >> (8169 MB) >> [1909618.328093] sd 13:0:0:0: [sdb] Write Protect is off >> [1909618.328102] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 >> [1909618.328107] sd 13:0:0:0: [sdb] Assuming drive cache: write through >> [1909618.328113] sdb: sdb1 >> [1909618.336159] sd 13:0:0:0: [sdb] Attached SCSI removable disk >> [1909618.336159] sd 13:0:0:0: Attached scsi generic sg2 type 0 >> >> >> On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: >>> I found the Barry project in my quest to get file transfer to/from >>> BlackBerry device memory working without using Roxio Media Manager. >>> >From what I have read about Barry and the parts of the source I have >>> looked at, it appears that Barry does not support this. From searching >>> the web and RIM's site, there does not appear to be any lightweight >>> program to do this and I'm not going to waste my time trying to >>> contact RIM to ask them to write one since others have not found them >>> very responsive. >>> >>> Sniffing the USB communication reveals that there is some >>> initialization after which simple commands like GET and PUT and LIST >>> are used to do transfers. >>> >>> I'm not much of a programmer and would like to see if anyone has or >>> could write a utility that I could use to send packets to endpoint 0x4 >>> or 0x3 (depending on BB model) and read from endpoint 0x83. I could >>> then continue investigating and documenting the protocol. >>> >>> I've also been unable to get Barry to compile on my Debian system... >>> Something about "no matching function for call to..." when compiling >>> base64.cc. >>> >>> Thanks. >>> >>> -- >>> Check out the new SourceForge.net Marketplace. >>> It is the best place to buy or sell services for >>> just about anything Open Source. >>> http://p.sf.net/sfu/Xq1LFB >>> ___ >>> Barry-devel mailing list >>> Barry-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/barry-devel >> -- >> Jason Thomas >> >> >> -- >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> ___ >> Barry-devel mailing list >> Barry-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/barry-devel >> > -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
On Wed, 2009-01-07 at 17:55 -0600, Robert Yaklin wrote: > I have also sniffed the communication when attempting to use > BlackBerry Media Sync which does not support my devices but does send That one could be helpful also > a LIST command...probably to get the filesystem size. I suspect that > Media Sync may work with devices with 1GB or more of on-board device > memory, but I don't have one and have not downloaded the emulator yet. > > On 1/7/09, Robert Yaklin wrote: > > Mass storage only works for devices with an SD card, and then ONLY to > > transfer to/from the SD card. I've got older 7xxx and 8xxx series > > devices that do not have a memory card slot. > > > > On 1/7/09, Jason Thomas wrote: > >> Hi Robert, > >> > >> Linux should be able to access your bb as a USB Mass Storage device. > >> Below is the output from my kernel when I connect my bb, on Debian sid. > >> > >> > >> [1909612.689528] usb 2-1: new full speed USB device using uhci_hcd and > >> address 10 > >> [1909612.877830] usb 2-1: configuration #1 chosen from 1 choice > >> [1909612.890095] scsi13 : SCSI emulation for USB Mass Storage devices > >> [1909612.893632] usb-storage: device found at 10 > >> [1909612.893635] usb-storage: waiting for device to settle before > >> scanning > >> [1909612.890095] usb 2-1: New USB device found, idVendor=0fca, > >> idProduct=0004 > >> [1909612.890095] usb 2-1: New USB device strings: Mfr=1, Product=5, > >> SerialNumber=3 > >> [1909612.890095] usb 2-1: Product: RIM Composite Device > >> [1909612.890095] usb 2-1: Manufacturer: Research In Motion > >> [1909612.890095] usb 2-1: SerialNumber: > >> FE216BF928723656BAAF354554BE01110D6407F3 > >> [1909618.163710] usb-storage: device scan complete > >> [1909618.297134] scsi 13:0:0:0: Direct-Access RIM Blackberry SD > >> 0001 PQ: 0 ANSI: 4 CCS > >> [1909618.310404] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors > >> (8169 MB) > >> [1909618.311991] sd 13:0:0:0: [sdb] Write Protect is off > >> [1909618.312000] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 > >> [1909618.312004] sd 13:0:0:0: [sdb] Assuming drive cache: write through > >> [1909618.324510] sd 13:0:0:0: [sdb] 15954944 512-byte hardware sectors > >> (8169 MB) > >> [1909618.328093] sd 13:0:0:0: [sdb] Write Protect is off > >> [1909618.328102] sd 13:0:0:0: [sdb] Mode Sense: 43 00 00 53 > >> [1909618.328107] sd 13:0:0:0: [sdb] Assuming drive cache: write through > >> [1909618.328113] sdb: sdb1 > >> [1909618.336159] sd 13:0:0:0: [sdb] Attached SCSI removable disk > >> [1909618.336159] sd 13:0:0:0: Attached scsi generic sg2 type 0 > >> > >> > >> On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: > >>> I found the Barry project in my quest to get file transfer to/from > >>> BlackBerry device memory working without using Roxio Media Manager. > >>> >From what I have read about Barry and the parts of the source I have > >>> looked at, it appears that Barry does not support this. From searching > >>> the web and RIM's site, there does not appear to be any lightweight > >>> program to do this and I'm not going to waste my time trying to > >>> contact RIM to ask them to write one since others have not found them > >>> very responsive. > >>> > >>> Sniffing the USB communication reveals that there is some > >>> initialization after which simple commands like GET and PUT and LIST > >>> are used to do transfers. > >>> > >>> I'm not much of a programmer and would like to see if anyone has or > >>> could write a utility that I could use to send packets to endpoint 0x4 > >>> or 0x3 (depending on BB model) and read from endpoint 0x83. I could > >>> then continue investigating and documenting the protocol. > >>> > >>> I've also been unable to get Barry to compile on my Debian system... > >>> Something about "no matching function for call to..." when compiling > >>> base64.cc. > >>> > >>> Thanks. > >>> > >>> -- > >>> Check out the new SourceForge.net Marketplace. > >>> It is the best place to buy or sell services for > >>> just about anything Open Source. > >>> http://p.sf.net/sfu/Xq1LFB > >>> ___ > >>> Barry-devel mailing list > >>> Barry-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/barry-devel > >> -- > >> Jason Thomas > >> > >> > >> -- > >> Check out the new SourceForge.net Marketplace. > >> It is the best place to buy or sell services for > >> just about anything Open Source. > >> http://p.sf.net/sfu/Xq1LFB > >> ___ > >> Barry-devel mailing list > >> Barry-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/barry-devel > >> > > > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services
Re: [Barry-devel] File transfer to/from BlackBerry device memory
On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: > I found the Barry project in my quest to get file transfer to/from > BlackBerry device memory working without using Roxio Media Manager. > >From what I have read about Barry and the parts of the source I have > looked at, it appears that Barry does not support this. From searching > the web and RIM's site, there does not appear to be any lightweight > program to do this and I'm not going to waste my time trying to > contact RIM to ask them to write one since others have not found them > very responsive. > > Sniffing the USB communication reveals that there is some > initialization after which simple commands like GET and PUT and LIST > are used to do transfers. I would be _very_ interested in seeing that sniff!! > > I'm not much of a programmer and would like to see if anyone has or > could write a utility that I could use to send packets to endpoint 0x4 > or 0x3 (depending on BB model) and read from endpoint 0x83. I could > then continue investigating and documenting the protocol. > > I've also been unable to get Barry to compile on my Debian system... > Something about "no matching function for call to..." when compiling > base64.cc. > > Thanks. > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: > I found the Barry project in my quest to get file transfer to/from > BlackBerry device memory working without using Roxio Media Manager. > >From what I have read about Barry and the parts of the source I have > looked at, it appears that Barry does not support this. From searching > the web and RIM's site, there does not appear to be any lightweight > program to do this and I'm not going to waste my time trying to > contact RIM to ask them to write one since others have not found them > very responsive. > > Sniffing the USB communication reveals that there is some > initialization after which simple commands like GET and PUT and LIST > are used to do transfers. I would be _very_ interested in seeing that sniff!!! I might be able to do something for you. > > I'm not much of a programmer and would like to see if anyone has or > could write a utility that I could use to send packets to endpoint 0x4 > or 0x3 (depending on BB model) and read from endpoint 0x83. I could > then continue investigating and documenting the protocol. > > I've also been unable to get Barry to compile on my Debian system... > Something about "no matching function for call to..." when compiling > base64.cc. > > Thanks. > > -- > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > ___ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] File transfer to/from BlackBerry device memory
On Wed, 2009-01-07 at 17:01 -0600, Robert Yaklin wrote: > I found the Barry project in my quest to get file transfer to/from > BlackBerry device memory working without using Roxio Media Manager. There is a file system embeded in the blackberry database access layer which I have documented (worked-out) and which could be an answer for you as well. The best way to tell is to look at what databases are available (if you can provide a link) I'm interested in getting a fusefs file system written which would access these files. If there is another protocol that can access these files, then that could do with documentation too. Best Regards, Martin Owens -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] JDE, JavaLoader on Linux (alpha patch)
Nicolas, Excellent work! I was able to use your javaloader to load a .cod file to my 8310. I am very excited to see the full set of features implemented (list .cod files on device, delete .cod files). I have a suggestion though to make compiling and testing easier for others. 1) put bjavaloader.cc into barry/tools directory 2) update barry/tools/Makefile.am to include bjavaloader -bin_PROGRAMS = btool bidentify upldif btranslate bktrans brecsum +bin_PROGRAMS = btool bidentify upldif btranslate bktrans brecsum bjavaloader +bjavaloader_SOURCES = bjavaloader.cc +bjavaloader_LDADD = ../src/libbarry.la $(LIBUSB_LIBS) -lpthread Regards, Josh On Wed, 07 Jan 2009 20:17:47 +0100 Nicolas wrote: > Hi, > > Before a clean patch with GIT and good integrated in barry project, > you can try this : > > With this patch, I can load a Java application on my BlackBerry Storm. > > Test with severals applications (format COD files). > > > Idea to improve the patch : > - parse an ".alx" file to load an application > - give an URL http:///app.alx to download application > - get the list applications installed on the device > - remove application > - your suggestions ? (about patch or improvement) > > > Regards, > > -- > Nicolas VIVIEN > -- Josh Kropf -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
Re: [Barry-devel] Using pppob with a brazilian provider (TIM)
--- Pablo Borges wrote: > Hey, Delta, by any chance do you know if there's a reference on the AT > command set that the blackberry accepts ? (I see you have a lot of AT > commands issued before dialing). Not my commands, I copied from one of the providers I knew was GSM ;) -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
