Tuesday, December 17, 2013

ActiveSync issues resolved in Android 4.4 KitKat - PowerUser

 android-2010a

ActiveSync is a synchronization application mobile data developed by Microsoft, originally released in 1996. It synchronizes data with handheld devices and desktop computers. In Windows Task Manager, the process is called wcescomm.exe.

ActiveSync allows a mobile device to be synchronized with a desktop PC or a server with a software product compatible, including Microsoft Exchange Server, Atmail, Axigen, Horde, Kerio Connect, Kolab, MDaemon Messaging Server, Novell GroupWise, Tine 2.0 , Scalix, Zarafa, Zimbra or Z-Push.

desktop, ActiveSync synchronizes email, calendar, contacts and tasks with Microsoft Outlook, along with Internet bookmarks and files. ActiveSync does not support all the features of Outlook.

For instance, contacts grouped into subfolders are not transferred. Only contacts that are not in a subfolder are synchronized.

For Exchange Server, only emails, calendar, contacts and tasks can be synchronized.

ActiveSync also provides for the manual transfer of files to a mobile device, along with limited backup functionality, and the ability to install and uninstall mobile device applications.

Apple’s iOS has had a bad reputation for the implementation of Exchange ActiveSync. However, things seem to go steady with iOS 7.0.4.

Moreover, Google also decided to implement the EAS. In fact, for a while Android did not include the EAS, although some manufacturers did.

latest release, Android 4.4 KitKat, includes the EAS as part of the OS, but seems to have some flaws.

First, there seems to be a problem with client certificate authentication, ie, does not work at all. To Google’s credit, there is a system that detects failures where everyone can see proper reports.

Imagine a world where Microsoft and Apple are transparent about the flaws in their products.

Ok, back to reality; clear that Google does not do the same for their products, just for open source like Android

.

Moreover, this type of public reports allows people to show their ignorance, a given thread, a couple of engineers shows that the protocols did not read properly and there was total collapse

.

also been reported that in such cases the devices were bombarded with EAS commands over again. Although there are no identified causes, Google claims to have solved the problem in 4.4.1 update. Now, the question is whether people who claim to have made this problem because the upgrade.

the question now resides if the directors intend to start proactively block new OS releases.

Apple, Microsoft, Google, all of them offer access to new releases, usually months in advance, so one possibility is to establish a multitude of tests for new OS – something that many sites already do with OS releases computer.

can be a painful process, but avoid unpleasant surprises in the future.

text written according to the new orthographic agreement.

Tags: Android, Android 4.4, Android KitKat, Apple, Microsoft

No comments:

Post a Comment