The new version of BirdieSync causes my mobile (XDA Orbit, WM2005) to freeze during synchronization. It's reacting so slow that the only way to get it working again is to take out the battery. It seems that there's something like an endless loop in BirdieSync that's consuming the CPU cycles.
Could you tell me which version you had installed before ?
Is it possible to copy DeviceProvider.log on the mobile in \Program Files\BirdieSync before reconnecting the mobile (to avoid overwritting it) and send it to support ?
Thanks.
Local 19/04/2007 10:14:59::0000 BirdieSync: version 1.5.2.0
Local 19/04/2007 10:14:59::0000 Operating system: PocketPC, version 5.1
Local 19/04/2007 10:15:16::0000 Count = 0
Local 19/04/2007 10:15:16::0000 Count = 150
Local 19/04/2007 10:15:18::0000 Count = 127
Local 19/04/2007 10:15:29::0000 Beginning of synchronization
Local 19/04/2007 10:15:30::0000 End of synchronization
Local 19/04/2007 10:15:31::0000 Beginning of synchronization
Local 19/04/2007 10:15:32::0000 End of synchronization
The log seems normal.
Did you see something special about the memory use of your mobile ? (Start/Parameters/System/Memory)
Do you have the same problem after soft reseting your mobile (rebooting it) ?
I just connected the mobile again (after the last reset) with the memory applet open. Synchronisation seems to run without problems and I can't see any unusual memory consumption. ActiveSync shows synchronisation of the selected BS elements (cards, events, tasks) two times and then says "synchronized". But the mobile freezes afterwards and becomes unusable.
With the new dll version the mobile hangs during synch already. DeviceProvider.log only contains the first two lines of the previously posted log. Or what do you mean with "log directory"? The BS dir on the mobile doesn't contain such a directory.
The problem seems to be solved: After completely uninstalling BS on the mobile the problem still persisted. I then rebooted my PC and now it works. Somehow the PC side of ActiveSync has managed to block the mobile even after disconnection without showing any error.