Comments on: Update / Solution for broken Android calendar syncing http://www.vijayp.ca/blog/2012/01/update-solution-for-broken-android-calendar-syncing/?utm_source=rss&utm_medium=rss&utm_campaign=update-solution-for-broken-android-calendar-syncing My thoughts about software and travel and other stuff... Wed, 20 Mar 2013 14:13:05 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Cliff Ansel http://www.vijayp.ca/blog/2012/01/update-solution-for-broken-android-calendar-syncing/comment-page-1/#comment-899 Cliff Ansel Wed, 29 Feb 2012 02:04:19 +0000 http://www.vijayp.ca/blog/?p=200#comment-899 I have the same crash problem. Every time I hit "Refresh" on my Galaxy Nexus calendar it crashes the calendar program. I searched for an event like you said above but ca't find anything remotely close. What part of that event string should I be looking for? I have the same crash problem. Every time I hit “Refresh” on my Galaxy Nexus calendar it crashes the calendar program. I searched for an event like you said above but ca’t find anything remotely close. What part of that event string should I be looking for?

]]> By: Jeremy http://www.vijayp.ca/blog/2012/01/update-solution-for-broken-android-calendar-syncing/comment-page-1/#comment-891 Jeremy Sat, 04 Feb 2012 21:01:58 +0000 http://www.vijayp.ca/blog/?p=200#comment-891 Thank you! Couldn't figure out why my calendar wasn't showing everything and this helped me track down the problem: a repeating event entered in Outlook. Deleted it and everything is showing up again. Come on, Google, fix this! Thank you! Couldn’t figure out why my calendar wasn’t showing everything and this helped me track down the problem: a repeating event entered in Outlook. Deleted it and everything is showing up again.

Come on, Google, fix this!

]]> By: Mike http://www.vijayp.ca/blog/2012/01/update-solution-for-broken-android-calendar-syncing/comment-page-1/#comment-869 Mike Wed, 18 Jan 2012 19:13:34 +0000 http://www.vijayp.ca/blog/?p=200#comment-869 Thanks for the info. It will be fixed in the next OTA. Thanks for the info. It will be fixed in the next OTA.

]]>