X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from toaster.scconsult.com ([66.73.230.185] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.3.2) with ESMTP id 58659554 for CGatePro@mail.stalker.com; Thu, 04 Feb 2010 10:12:03 -0800 Received-SPF: pass receiver=mail.stalker.com; client-ip=66.73.230.185; envelope-from=cgp-2008@billmail.scconsult.com Received: from bigsky.scconsult.com (bigsky.scconsult.com [192.168.2.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id 1C405A2E889 for ; Thu, 4 Feb 2010 13:11:45 -0500 (EST) Message-ID: <4B6B0DDF.9040708@billmail.scconsult.com> Date: Thu, 04 Feb 2010 13:11:43 -0500 From: Bill Cole Organization: Solid Clues User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.4pre) Gecko/20100105 Eudora/3.0b4 MIME-Version: 1.0 To: CommuniGate Pro Discussions Subject: Re: Calendaring on Android phones References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dan Hedley wrote, On 2/2/10 9:16 AM: > Hello list, > > I hope I'm not bringing up something that has already been dealt with. I > couldn't find anything in the archive about this, so here goes: > > Has anyone had a successful experience providing calendar services to > Android phones? AirSync seems to be the way to go, but there are > numerous tools on the market, none of which are cheap, and all of which > have distinctly mixed reviews. Ideally, I'm looking for something with > an experience comparable to using an Android phone with Google calendar > i.e. pretty much set it and forget it. I have a very narrow data point. I have a Samsung Moment, which runs Android 1.5 ("Cupcake") and includes (free, part of the Sprint load) the Moxier Mail ActiveSync client. Setting it up with a CGP 5.2.18 server went without a hitch and it has been working well, although I do not make it work very hard. I have had an event invitation echo once, apparently an artifact of a sync loop between the phone, CGP, and iCal. I have yet to fully analyze what causes those incidents (also seen by iPhone users) but the published AirSync fixes in 5.3.x seem to address that area.