HowTo: Use bcharge to charge your BB under linux - BlackBerryForums.com : Your Number One BlackBerry Community

rivviepop · 01:11 PM

Barry Homepage:
Net Direct :: Open Solutions

SourceForge Project Downloads:
SourceForge.net: Files

'bcharge' is a utility that's part of the Barry project - which aims to be a complete desktop toolset for interfacing your BlackBerry with linux. The purpose of the bcharge tool is to detect when a BB has been plugged in and then alter the current to the USB port - it will increase the default 100mA flow up to 500mA, which is what the BlackBerry is expecting. This is exactly what the Windows driver does.

The 0.1 version currently available (2007-02-19) will work with any BlackBerry older than the Pearl 8100; for the 8100 (and presumably the 8800, unreleased at this time) you'll need to get the latest version of the code from CVS (only "bcharge.cc" is needed); the product ID internally has changed from '0x0001' to '0x0006' in this newer handset. The latest CVS version will recognize both older and newer devices, but the newer CVS code includes some special action to take when "seeing" an 8100 device.

CVS link for post-0.1 bcharge.cc:
SourceForge.net Repository - [barry] Index of /barry/tools

Compiling the code is beyond the scope of this HowTo, but it's extremely simple and uses all the standard linux-isms (autoconf, g++, etc.) -- if you can compile any generic application you should be able to compile bcharge; because this code interfaces with USB ports, make sure you have the 'libusb-devel' (exact name depends on your distro) installed so it'll find the headers and link libraries. There may already be installable packages available download as well (.deb/.rpm) - your need to compile may vary.

There are two parts to 'bcharge' - the main binary itself and a "udev" script. You can use the tool without doing anything, just plug in your BlackBerry to any USB port and type ./bcharge (substitute the path if needed). This will scan all the USB devices plugged in, find your BB handset, and adjust the current flow. It's that simple.

But, to automate the process you can copy a script from CVS (or the official downloads) to your /etc/udev/rules.d/ directory (location may vary depending on distro) to have everything done for you. First, copy the compiled binary (bcharge) to /usr/sbin/ and make sure it's at least mode 0755 (executable), owned by root (for security's sake). Now copy one of the scripts from here:

SourceForge.net Repository - [barry] Index of /barry/udev

...to the udev rules directory mentioned above. Obviously if you're using Debian (and maybe Ubuntu?) use the one called "Debian".

NOTE: if you have a newer Pearl device you will need to update the ProductID in this script. Replace this code:

Code:

SYSFS{idProduct}=="0001"

...with this code:

Code:

SYSFS{idProduct}=="0006"

It should make perfect sense why you're doing this. You could also just copy/paste the line to a new line and add both products at once -- the choice is yours. Maybe you have both an older and newer BB device and need it both ways.

Reboot. I say again, Reboot. 'udev' rules don't seem to work quite right unless they're loaded at startup (when udev runs), so just save yourself some hassle and sacrifice your uptime with a reboot. Now plug in your BB device and it should initially flash on the handset the error message about insifficient charge, but then the message will go away in 1sec (or so) when bcharge runs and performs the adjustment.

You can use the 'lsusb' tool to verify the current has been changed - run 'lsusb -v | less' as root, find the RIM BlackBerry section and it'll show the current USB port power flow. It should say 500mA and not 100mA.

edit: blogged.
bcharge: charge your BlackBerry under linux « rivviepop phantom

blakeatl · **OS:** 4.5.0.102

Very nice. I hope the option for the Pearl comes soon.

Glate · 02-21-2007, 07:30 PM

Wicked. I've been looking for this for years... You are officially my hero. Now to see if there's a Gentoo ebuild..

LunkHead · 02-23-2007, 02:20 PM

Got it! Sweet!!!! Working as advertised!

@rivviepop

Any luck getting the MicroSD card in the BB recognized?????

rivviepop · 02-23-2007, 03:02 PM

Quote:

Originally Posted by LunkHead

Any luck getting the MicroSD card in the BB recognized?????

Mine works like a champ -- start a new thread on this, and post the applicable contents of /var/log/messages from your system when you plug in the device. We'll address it in that thread then...

LunkHead · 02-23-2007, 05:32 PM

This could also use a sticky! Mods? Thanks!

LunkHead · 12:13 PM

Here is the bcharge RPM(*)... I had to add the .zip at the end of the file to get the forums to take the upload... Just rename it by removing the .zip at the end of the filename...

(*)From RPM.Pbone.net

You will need to satisfy the following:
libusb-0.1.so.4
rpmlib <= 3.0.4-1
libstdc++.so.6
libgcc_s.so.1
libc.so.6
rtld(GNU_HASH)
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
config(bcharge) = 1.0-1
libstdc++.so.6
libc.so.6
libm.so.6

rivviepop · 02-25-2007, 03:35 PM

Just a note (trying to tie these two threads together) -- the above RPM is old (I think?) and doesn't use the fancy new CVS code from the Barry project; I do have a RPM for FC6 that I'll give out personally (PM me), but I don't want to share it publically. I made my own tarball and called it "0.2", it's entirely unofficial code -- I don't wish to disrespect the Barry project by accident, hence not releasing it.

It's not hard to do yourself, though.

I'll at least post my SPEC file here to get you started; it's an enhancement of the one from the Barry project, and is intended to use the latest bcharge.cc and a patched udev ruleset (see the Barry patches page if it's not in CVS yet) to support both old and new device IDs.

Code:

Summary: BlackBerry (tm) Desktop for Linux  - bcharge utility
Name: bcharge
License: GPL
Version: 0.2
Release: 1.cvs20070219
Group: Applications/Productivity
Source: bcharge-0.2.tar.gz
URL: http://www.netdirect.ca/downloads/barry
Vendor: Net Direct Inc.
BuildRoot: /var/tmp/%{name}-buildroot
Requires: libusb
BuildRequires: libusb-devel, gcc-c++

%description
Barry is a desktop tool for managing your BlackBerry (tm) device. (BlackBerry
is a registered trademark of Research in Motion Limited.)

This packages contains the USB charge utility, bcharge.

%prep
%setup

%build
g++ -Wall -g -o bcharge bcharge.cc -lusb

%install
%{__mkdir_p} %{buildroot}%{_sbindir} %{buildroot}%{_sysconfdir}/udev/rules.d
%{__cp} bcharge %{buildroot}%{_sbindir}
%{__cp} 10-blackberry.rules %{buildroot}%{_sysconfdir}/udev/rules.d

%clean
%{__rm} -rf %{buildroot}

%files
%attr(0755,root,root) %{_sbindir}/bcharge       
%attr(0644,root,root) %config %{_sysconfdir}/udev/rules.d/10-blackberry.rules

erroneus · 02-26-2007, 10:05 AM

Let me just add an important note regarding the use of bbcharge.

With bbcharge active, I can use vmware+winxp and the blackberry software to perform the sync operations. Without it, I cannot. bbcharge is a necessary component to make it work.

LunkHead · 02-27-2007, 08:32 PM

Note: I do not have winxp....

BUT... You are able to do a complete sync with vmware after installing bcharge?

Kewl!

LunkHead · 02-27-2007, 10:04 PM

Quote:

Originally Posted by rivviepop

Just a note (trying to tie these two threads together) -- the above RPM is old (I think?) and doesn't use the fancy new CVS code from the Barry project;

You are correct Sir, it does not use the *new* cvs coding from barry....

godzilla8nj · 02-28-2007, 03:57 PM

Hope this isn't off-topic, but are there any Ubuntu 6.10 users who have already compiled Barry who could give me a hand? I'm trying to get a tethered Blackberry as a modem and would hate to get too sidetracked learning how to compile for my distro. Thanks in advance for any assistance.

LunkHead · 04:57 PM

It's never a bad idea, and it's actually not hard, to do... I'd say read up on how to compile and give it a shot.... You get to learn and play with the BB at the same time!

How To Compile A Kernel - The Ubuntu Way | HowtoForge - Linux Howtos and Tutorials

rivviepop · 03-01-2007, 11:54 PM

Ladies & Gents:

SourceForge.net: Detail: 1672178 - RPM spec file to build barry-bcharge

You can use that now to build a 'barry-bcharge' RPM (for Fedora/Red Hat) right out of the official tarball. The udev rule patch isn't in CVS, so you also have to download it as well (outlined in the above link).

jfanaian · 03-28-2007, 01:18 PM

I'm trying to install bcharge for my Pearl 8100 but it keeps saying it isn't a perl when I run it. I found out (through lsusb) that my iProduct is actually 4 not 5. I tried changing the constant acordingly but it does not seem to modify the Max Power to 500mA instead of 100mA, even though there seem to be no error.

Here is the output I get after changing the constant to 4:

Code:

Scanning for Blackberry devices...
Found device #005...adjusting charge setting...adjusting Pearl mode to dual...done

rivviepop · 03-28-2007, 01:48 PM

Quote:

Originally Posted by jfanaian

I'm trying to install bcharge for my Pearl 8100 but it keeps saying it isn't a perl when I run it.

Yeah, it's a problem in the code - it adjusts your current to 500mA just fine, but then running it again says "no Pearl found".

See:
http://sourceforge.net/tracker/index...& atid=788906

and

http://sourceforge.net/mailarchive/f...me=barry-devel

HTH.

jfanaian · 03-28-2007, 02:01 PM

Hrm... I tried looking at the patch and ti seems to have similar changes that the patch adds. I have the latest CVS version which already has a detection for 0x0004 which is what seemed to be in the patch so that didn't work, and I didn't find anything useful while reading through the mailing list archive. I sent an email to the mailing list and I will keep playing to see what the cause of this is.
Thanks

rivviepop · 03-28-2007, 02:07 PM

Quote:

Originally Posted by jfanaian

Hrm... I tried looking at the patch and ti seems to have similar changes that the patch adds. I have the latest CVS version which already has a detection for 0x0004 which is what seemed to be in the patch so that didn't work, and I didn't find anything useful while reading through the mailing list archive. I sent an email to the mailing list and I will keep playing to see what the cause of this is.

Basically, CVS is just plain broken. If you download the released 0.6 code then apply the patch, it will add the 0x0004 support and just work; Chris did a lot of re-working with the CVS code and it's actually worse than 0.6 code was; he said he might just undo everything he did in CVS, but I don't know.

jfanaian · 03-28-2007, 02:13 PM

Ah! Alright I will do that then! Thanks for the tip... I will let you know how it works out.

jfanaian · 03-28-2007, 02:21 PM

I tried using 0.6 with the patch and it seems to actually do some thinking in the execution unlike before. The only problem is that MaxPower is still 100mA :(

This is the output from running bcharge:

Code:

Scanning for Blackberry devices...
Found...attempting to adjust charge setting.
1 device adjusted.

This is what lsusb -v says under the pearl device section:

Code:

Bus 001 Device 011: ID 0fca:0006 Research In Motion, Ltd. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        16
  idVendor           0x0fca Research In Motion, Ltd.
  idProduct          0x0006 
  bcdDevice            1.06
  iManufacturer           1 
  iProduct                4 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              4 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0

Thanks again

rivviepop · 03-28-2007, 02:59 PM

Quote:

Originally Posted by jfanaian

The only problem is that MaxPower is still 100mA :(

Code:

  idProduct          0x0006

Well that's no fun -- ok. the first clue here is that the idProduct is still 0x0006, when after bcharge is run it should be 0x0004. So, lemme ask some questions about your setup:

- what OS version is on your Pearl?
- have you tried this as root user (maybe it's a permissions problem)?
- do you see anything in /var/log/messages that might provide a clue?

I don't know specifically what's wrong, but we can try and find out...

jfanaian · 03-28-2007, 03:03 PM

Quote:

Originally Posted by rivviepop

- have you tried this as root user (maybe it's a permissions problem)?

That did the trick! Works perfect. Thank you so much.

What I did notice is that mass storage is disabled (I'm assuming because I can no longer access it) so does that mean that I can't access the device while charging? I have no problem with this as I can just unplug and plug it back in to access files, and I really don't need to while I'm charging all that often. Just for simplicity of not having to replug it everytime.

Thanks again, it works great!

rivviepop · 03-28-2007, 03:42 PM

Quote:

Originally Posted by jfanaian

That did the trick! Works perfect. Thank you so much.

Sweet, I like easy answers.

Quote:

What I did notice is that mass storage is disabled (I'm assuming because I can no longer access it) so does that mean that I can't access the device while charging?

Mine works just fine -- do you actually have mass storage enabled on the Pearl and all that jazz? Also, I have another thread here on the forums where sometimes my mass storage doesn't mount -- I figured out it's because things "went too fast" with bcharge around.

My solution:
- put device mass storage into Prompt mode to mount
- plug in device, wait.
- Initial "not enough charge" screen flashes the goes away (indicating bcharge has run), then the "do you want to enable mass storage?" screen.
- *wait* a second or two, *then* press Yes.

Sometimes if it's the first time I've plugged in the Pearl since a reboot it doesn't work on the first try. I unplug, wait a second or two, then plug it back in; my guess is in this situation 'usb-storage.o' (kernel module) hasn't ever been loaded before, so it doesn't happen fast enough (remember, it has to load vfat, usb-storage, etc.) before the Pearl kicks in; the 2nd time you plug it in all these modules are loaded already in memory, so stuff Just Works(tm).

jfanaian · 03-28-2007, 04:05 PM

I tried that, except the message doesn't show up anymore but its still at 100mA. What I do is plug it in, wait a few seconds. It prompts me to enable media support. I execute bcharge, verify that its at 500mA. Then tell it yes. It stays at 500mA but it does not mount the device.

Its no big deal though, I don't often use the storage so I don't mind switching out. Its nothing to waste your time on. I'm just glad I can charge it. Thanks so much!

HuwSy · 08:59 AM

Im having a problem with my lowly old 7100t, i connect it and it doesnt seam to run bcharge automatically (during boot it says the UDEV rule is invalid and iv tried both forms within the rule file to no avail. but im using ubuntu 7.04 feisty fawn so i can expect a few strangnesses). But when i run bcharge manually as root it says its changed the charge state and looking in lsusb -v it says its at 500mA but the charge icon on my Bb vanishes after a second or so of connection regardless. The only way i can get any form of charge process is by leaving barrybackup open/connected, even then tho its only a slow charge. Any ideas?

Heres what lsusb gives:

Code:

Bus 001 Device 003: ID 0fca:0001 Research In Motion, Ltd. Blackberry Handheld
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0fca Research In Motion, Ltd.
  idProduct          0x0001 Blackberry Handheld
  bcdDevice            1.04
  iManufacturer           1 Research In Motion
  iProduct                2 Terminal mobile RIM
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           46
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

then this is what it gives when connected to by barry backup:

EDIT: removed as its identical...

rivviepop · 03-28-2007, 05:32 PM

Quote:

Originally Posted by HuwSy

But when i run bcharge manually as root it says its changed the charge state and looking in lsusb -v it says its at 500mA but the charge icon on my Bb vanishes after a second or so of connection regardless. The only way i can get any form of charge process is by leaving barrybackup open/connected, even then tho its only a slow charge.

Heres what lsusb gives:

The two outputs are identical; and according to them the computer is sending 500mA out the port as desired. So, if your 7100 is empty (out of battery), you plug it in and run bcharge -- does it actually charge up after an hour or two? Or, are you saying if you leave it plugged in for 2 hours that nothing happens, you get no charge at all?

According to your lsusb output, the computer is attempting to charge the device -- you sure the 7100 doesn't have some sort of OS flaw with the charging icon?

HuwSy · 03-29-2007, 08:58 AM

I can get it to charge through windows or on the mains adaptor fine, but under linux it doesnt charge even after several hours of being connected with supposidly 500mA going to it. Is there any other way to check the usb output without cutting into some cables.

rivviepop · 03-29-2007, 12:57 PM

Quote:

Originally Posted by HuwSy

Is there any other way to check the usb output without cutting into some cables.

I bet there is using a multimeter (or something like that?), but I'll admit I'm a n00b when it comes to things like this, sorry. I have never been very good at the electrical engineering aspect of life (or differnential equations, while we're at it :-/).

rivviepop · 04-03-2007, 04:50 PM

A crosspost/note from another thread -- we've got a kernel module in the works!

Linux Headquarters - Kernel v2.6.21-rc5 /drivers/usb/misc/berry_charge.c

ubuntuthinking · 04-11-2007, 07:27 AM

Wirelessly posted (BlackBerry8700/4.1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

I installed bcharge from the files on Sourceforge. It runs for about a second then charging stops?? I'm on ub untu fiesty fawn.

HuwSy · 04-11-2007, 07:44 AM

Im thinking its something to do with Fiesty Fawn, cos it happens to me ever since i upgraded. I knnow the udev version is newer than expected which might have an effect. The .deb version sometimes charges if i connect the bb then remove it straight away remove it then connect it again straight away. How fast this is done effects the chances of this working in my experience. The CVS version doesnt seam to work atall for me at the moment. When i have more time il look into it more.

ubuntuthinking · 04-11-2007, 07:06 PM

Thanks HuSwy,

I'm stuck on the fence with M$ due to the Blackberry issues. If I can:

a) Charge it via USB &
b) Load applications

I would delete Windows off my drive. Right now, I've got an XP Guest on a Ubuntu host...and no connection.

HuwSy · 04-12-2007, 05:40 AM

Barry Tools works in backing up and restoring under Feisty, however bcharge stopped working after I moved from Edgy to Feisty. The only way to load apps via computer is under windows, this cant even be done under mac yet, and syncronising with something like evolution is in progress but not there yet under linux. Best dual booting for the time being.

ubuntuthinking · 04-12-2007, 08:06 PM

Thanks for the help. I can survive with .jad files for now. But how do you do a backup and restore? I have not located that in the documentation...yet.

HuwSy · 04-13-2007, 03:27 AM

You have to build btool then barrybackup from the sorce code available off sf.net then run barrybackup as root (or atleast sudo) Hopefully there will be .deb and .rpm versions of these when the next version is released.

rivviepop · 04-19-2007, 06:21 PM

News from the mailing list:

Quote:

Originally Posted by Chris Frey

I recently got my hands on a new 8800 Pearl, and tweaked the CVS version
of bcharge to work better with the Pearl. The CVS version of bcharge
has been broken for a while now, and I believe it is now fixed.

There are 3 ways to run bcharge now, with the Pearl:

bcharge
Will change to 500mA, and switch idProduct mode from 0006 to 0004 (dual).
bcharge -o
Will change to 500mA and switch from 0006 to 0001 (classic)
bcharge -d
Will change to 500mA and switch from 0001 to 0004 (dual).

This is the behaviour I had hoped for earlier, but I tried to do it
automatically, which seems impossible, from just the USB data. I'm sure
if I talked to the device to get manufacturer, product strings, etc
I could do more checks, but that would make bcharge more complicated
than necessary. I think the above command line switches are a good balance.

I personally haven't had a chance to test the new code yet.

erroneus · 04-20-2007, 01:39 PM

Don't forget those of us who hangs on every word from you, Rivviepop! If there's an RPM somewhere, I hope you will make it available to us!

HuwSy · 05-07-2007, 11:38 AM

Yey BCharge works again for me. Not sure if its due to recent compilation from CVS (as i know v0.7 didnt work for me) or if its due to my move to Ubuntu Gutsy Gibbon (cos Iv never got it to charge under Feisty Fawn)

foczq · 05-12-2007, 02:21 AM

Quote:

Originally Posted by ubuntuthinking

Wirelessly posted (BlackBerry8700/4.1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

I installed bcharge from the files on Sourceforge. It runs for about a second then charging stops?? I'm on ub untu fiesty fawn.

I have the same situation...

breakerfall · **OS:** 4.7.0.90

Quote:

Originally Posted by foczq

I have the same situation...

dammit, i hate me-too-ing...

ME TOO!

feisty, charge icon stays on for about 2 seconds...