Difference between revisions of "Sync and connect with Windows Mobile"

From ArchWiki
Jump to: navigation, search
(New page: =Introduction= This page is a howto for connecting your Windows Mobile device with Archlinux. Afterwards you can sync and install cabs just like you can do with activesync in windows. It u...)
 
Line 10: Line 10:
  
 
2: Install sync-engine from AUR
 
2: Install sync-engine from AUR
[[Media:Example.ogg]]
+
If you have [[yaourt]] installed, this is done easily by  
If you have yaourt installed, this is done easily by  
+
 
  § yaourt -S sync-engine
 
  § yaourt -S sync-engine
  
Line 36: Line 35:
  
 
=Other problems=
 
=Other problems=
There is only one problem I have experienced with this. Sometimes it wil stop working, and you will get an eror report on your phone sayig device.exe had a problem and was teminated.
+
There is only one problem I have experienced with this. Sometimes it will stop working, and you will get an error report on your phone saying device.exe had a problem and was teminated.
 
To fix this, simply go to USB-connection setting, choose "mass storage device" and select Ok, and then select "active sync" and again ok.
 
To fix this, simply go to USB-connection setting, choose "mass storage device" and select Ok, and then select "active sync" and again ok.
  
If the above did not work, you might have to quit/kill sync-engine and odccm, and restart them. Start odccm first. This seems to be neccesary when sync-engine seems to be stuck at " Authorization pending - waiting for password on device" You will get output if you start sync-engine without the -d option.
+
If the above did not work, you might have to quit/kill sync-engine and odccm, and restart them. Start odccm first. This seems to be necessary when sync-engine is stuck at " Authorization pending - waiting for password on device" You will get output if you start sync-engine without the -d option.
  
 
I think this problem arises after the phone has suspended, but I'm not quite sure what really causes it.
 
I think this problem arises after the phone has suspended, but I'm not quite sure what really causes it.

Revision as of 21:51, 16 February 2009

Introduction

This page is a howto for connecting your Windows Mobile device with Archlinux. Afterwards you can sync and install cabs just like you can do with activesync in windows. It uses the kde app synce-kde, but gnome and *box users can relax, the only qt-deps are qscintilla-2.3.2-2 and pyqt-4.4.4-2. And they are small.

Installation

1: install synce-odccm and synce-kde (both in repos)

§  pacman -S synce-odccm and synce-kde

2: Install sync-engine from AUR If you have yaourt installed, this is done easily by

§ yaourt -S sync-engine


Connecting to your phone

1: Start odccm. It requires root privileges, so:

§ sudo odccm

or, as root, just

§ odccm

2: Start sync-engine. You can use "sync-engine -d" to have it running in the background as a daemon.

3: Start synce-kpm

4: Connect your WM phone.

Now you can sync your phone, install cabs and so on. Have fun.Before syncing you will have to crete a partnership with your phone. Just as with active sync in Windows.


Troubleshooting

If your phone does not show in synce-kpm, make sure the activesync-setting in your phone is set to "activesync", and not "mass storage device"" or similar. (Settings->Connections->USB connection settings)

Other problems

There is only one problem I have experienced with this. Sometimes it will stop working, and you will get an error report on your phone saying device.exe had a problem and was teminated. To fix this, simply go to USB-connection setting, choose "mass storage device" and select Ok, and then select "active sync" and again ok.

If the above did not work, you might have to quit/kill sync-engine and odccm, and restart them. Start odccm first. This seems to be necessary when sync-engine is stuck at " Authorization pending - waiting for password on device" You will get output if you start sync-engine without the -d option.

I think this problem arises after the phone has suspended, but I'm not quite sure what really causes it.