BirdieSync full changelog

Bug fixes:
· When started, BirdieSync could crash displaying 0xc0150002 error
· After BirdieSync has been updated to 2.3.5.0 and Thunderbird 6.0, BirdieSync menu could no longer appear in Thunderbird
· Using the tool to remove duplicates, enumeration of items during duplicate search could be very slow.

Changes:
· Support of Thunderbird 6.0

Bug fixes:
· Windows Mobile: Mail with an empty body synchronized from the mobile device could have an incorrect body.

Changes:
· Android: An error is now displayed if no event account was selected in BirdieSync settings on the Android device
· Android: A specific error is now displayed if a contact is placed in a group whose account is different from the contact one.

Bug fixes:
· Android: If an important number of contacts were modified in Thundebird, synchronization of contacts and events could lead to unresolved items.

· Support of Thunderbird 5.0
· Android: BirdieSync account is no longer used to store contacts
· Android: It is now possible to select which contact and event accounts should be synchronized
· Android: Display name is no longer synchronized because it cannot be edited with stock calendar application.
· Android: It is now possible to manually remove calendars in accounts where calendars can be created by the synchronization (Menu/Remove calendar)
· Android: System log and BirdieSync device preferences are now archived by log archiver to easy bug investigation.
· In order to allow Android users to still use the stock application to manage contacts, BirdieSync account is no longer used to synchronize contacts.
· To bring more flexibility and to solve some specific problems with some Android devices, it is now possible to choose which contact and event accounts you wish to synchronize in BirdieSync options on the Android device.

Bug fixes:
· If BirdieSync cannot listen to incoming connections because of a firewall, an explicit message is now displayed instead of an unexpected error
· If was not possible to launch help or log archiver from Thunderbird or Sunbird
· Android: A warning message could be displayed even if BirdieSync account was not empty if it had several calendars
· Android: Import of events could not propose to import events from accounts which had several calendars

Changes:
· To avoid problems with some specific Android devices, it was necessary to create an independant BirdieSync account to store contacts on the device. Contacts must be now created in BirdieSync account to be synchronized, and no longer in the default account of the Android device. Therefore, if your Android device had already been synchronized with BirdieSync, it will be necessary to synchronize again all the contacts from Thunderbird to the empty BirdieSync account. To avoid duplicates with contacts already synchronized in the default account, it is necessary to remove them. The option to remove them will be displayed at the first synchronization. You may choose this option if you want to avoid having duplicates (the same contact would be present in the default account and in BirdieSync account). You can also remove events in the default account later using the menu quot;Remove eventsquot; on the mobile device.

Bug corrections:
· Android: If USB debugging was not enabled, a warning was displayed when the mobile device was plugged. Application could crash when pressing the OK button.

· After having synchronized with quot;Combinequot; option, if duplicates were removed at the end of the synchronization, at next synchronization, an incorrect warning could be displayed mentioning that items would be deleleted on the desktop and the mobile device

Bug corrections:
· Icon displayed in error message could be incorrect
· Android: Over the air connection could be disrupted during the synchronization
· Android: If the mobile device was rotated, the synchronization status was set to quot;Not connected to hostquot;. Connecting could then display an error.
· Android: If a mobile device had been connected over the air, plugged and then unplugged, the connection was disrupted
· Android: If Wi-Fi and cellular networks were disabled, it was not possible to connect with a USB connection

Bug corrections:
· On Android devices, in some particular circumstances, calendar synchronization way could be incorrect.