From ArchWiki
Revision as of 18:27, 24 March 2012 by (talk | contribs) (http ->
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی


BlackBerry is a line of mobile e-mail and smartphone devices developed by Canadian company Research In Motion (RIM). While including typical smartphone applications (address book, calendar, to-do lists, etc., and telephone capabilities), the BlackBerry is primarily known for its ability to send and receive Internet e-mail wherever it can access a mobile network of certain cellular phone carriers. It commands a 20.8% share of worldwide smartphone sales, making it the second most popular platform after Nokia's Symbian OS. The service is available in North America and in most European countries.

Synchronization Using barry

This example syncronizes your blackberrys contacts and calender with your evolution contacts and calender. In theory the same princible should be able to be applied to other mail and calander clients. Including kmail and Google calender.

Installing packages

evolution - from the extra repository
msynctool-stable - from the AUR -
libopensync-plugin-evolution2-stable - from the AUR -
barry - from the AUR

When building barry, the PKGBUILD must be edited to enable the barry opensync plugin to be built. This must be added to the configure line in the PKGBUILD as shown below.

./configure --prefix=/usr --enable-gui --enable-opensync-plugin

Currently the barry opensync plugin will only build against opensync-stable and msynctool-stable

Creating a Sync Pair

Setup evolution to use your liking if you have not done so already.

Create a sync group called evoberry

msynctool --addgroup evoberry

Add evolution and the blackberry to the sync group.

msynctool --addmember evoberry evo2-sync
msynctool --addmember evoberry barry-sync

Configure the evolution member

msynctool --configure evoberry 1

Change the defaults to the location of your evolution files as shown in the example


Configure the blackberry member

msynctool --configure evoberry 2

Change the device number to your blackberry pin number as shown in the example.

# This is the default configuration file for the barry-sync opensync plugin.
# Comments are preceded by a '#' mark at the beginning of a line.
# The config format is a set of lines of <keyword> <values>.
# Keywords available:
# DebugMode        - If present, verbose USB debug output will be enabled
# Device           - If present, it is followed by the following values:
#      PIN number    - PIN number of the device to sync with (in hex)
#      sync calendar - 1 to sync calendar, 0 to skip
#      sync contacts - 1 to sync contacts, 0 to skip
# Password secret  - If present, specifies the device's password in plaintext


Device 00000000 1 1

#Password secret

Sync and smile

Make sure evolution is closed and your blackberry is connected then issue the sync command.

msynctool --sync evoberry