Common Issues When Working With Barry
Q: When I run btool, it hangs for 30 seconds and then times out on the USB read call.
A: To verify that you are experiencing the right issue, run "btool -vl" to get a verbose USB log. At the beginning the USB configuration and endpoint information is printed. If the last set of endpoints have 0's in the values, you are experiencing the problem. The proper set of endpoints will not be displayed with "lsusb -v" in this case either.
One workaround is to run bcharge twice like this:
bcharge bcharge -o
After the second bcharge, btool should work normally.
Q: I've installed Barry, and bcharge is set to run automatically, but as soon as I plug my device into the USB port, the device reboots.
A:Make sure you're running a recent version of Barry, at least 0.16 or 0.17.
Depending on the age of your kernel (older than 2.6.34?), you may have the berry_charge kernel module running, in which case you need to choose which method you wish to use. Do not run both berry_charge and bcharge.
Q: One of the Barry applications crashed, and now I keep getting a Desktop error message in hex.
A: If a Barry application crashes, that means the Desktop mode was not shutdown properly. Your device will likely appear to still be "busy" as well. Currently the only way to fix this is to reset the device, either by unplugging/replugging it, or by running the program "breset".
Q: Everytime I restore a backup with the backup GUI, the database I need does not get restored. What gives?
A: Both the backup and the restore are filtered based on your configuration. Check your Edit | Config... settings and make sure the needed database is turned on in both backup and restore.
Q: I ran the backup, but can't find my backup files! Where did they go?
A: The backup program saves all backup files as gzip'd tarballs under your home directory: ~/.barry/backup/pin_number/
Each backup session creates a new file, named with the pin number, date, and time.